I have no experience with adb or fastboot using a Windows machine but these two threads may be of help.
… are the master keys for your problem.
Your phone should prompt you to authorize your computer to connect with ADB.
Also, please see https://doc.e.foundation/pages/unauthorized-device
This too may be of help as it was written using a Windows machine.
I was working on this last night and had similar problems. I got my G7+ unlocked but was stuck at the sideload step with the signing.
To get around the adb server problem I booted into the application and re-enabled developer mode and USB debugging. The previous temp .img and/or the unlocking of the bootloader wiped the settings.
But I am still stuck trying to sideload the A/B copy step (mandatory). The adb sideload completed with no errors on the screen (ubuntu 20) but there were signature errors and a failure code on the device. I don’t see anywhere to Continue.
Any help or suggestions welcome.
Are the errors you describe coming during these steps?
In some cases slot
b can be unpopulated or contain much older firmware than slot
a, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of slot
a to slot
This step is
To do this, sideload the
copy-partitions-20200903_1329.zip package by doing the following:
- Download the
copy-partitions-20200903_1329.zipfile from here.
- Sideload the
- On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload
- On the host machine, sideload the package using:
adb sideload copy-partitions-20200903_1329.zip
Once you complete the sideload of
sideload copy-partitions-20200903_1329.zip you stay in TWRP and simply proceed to these steps👇. Because within TWRP you were in Advanced > ADB Sideload you will need to press the back button to get back the the main TWRP menu where you can proceed with these steps. Be sure you have the /e/OS build for your device downloaded to your computer so you can sideload it just like you you did with the
copy-partitions-20200903_1329.zip in the previous step.
- In TWRP return to main menu, then tap
- Now tap
Format Dataand continue with the formatting process.Here a new screen may show where you will have to type
Yesand confirm the action by clicking a button.
3.Caution:* Format Data will remove encryption as well as delete all files stored on the internal storage. Remember to take a backup first. Check Requirements section above.
- Return to the previous menu and tap
- Select the
Systempartitions to be wiped and then
Swipe to Wipe
- Sideload the /e/ .zip package.
7.Tip:* Sideload requires actions in two places to be done. One on your phone in the TWRP UI and secondly on the connected PC which should have adb enabled. Also note the sideload process while running may stop abruptly around 50%. The console would show a message
Total xfer: 1.00x. This would mean that the transfer has successfully completed.
- On the device in TWRP,
ADB Sideload, then swipe to begin sideload.
- On the host machine, in the console , start the sideload of the package by typing
adb sideload filename.zip
8.Tip:* Change the filename to the name of the file you downloaded
- Once installation has finished, return to the main menu, tap Reboot, and then System
This is not well documented.
You think you got everything right, then you send a message from the PC to the device …
The device quietly responds “wot”
but you don’t see the device screen!
It is a two way thing, when you “send” on the PC, watch the mobile - it just wants you to say that it is ok to talk to the PC. You can usually tick a box to say, “it’s always ok to accept stuff from this PC”
Thanks everyone! Yes, according to egx470 sounds like the sideload might have worked but I was confused for a “continue” and seeing the errors on the device. I will try it again tonight with the more detailed instructions for the sideload of the copy-partitions.
What @aibd has stated is totally correct. Looking back on these directions now that I am more experienced, I agree they could be confusing for someone flashing this phone for the first time.
I have seen this when flashing other phones. I just proceed and haven’t had additional problems after the OS is flashed and booted.
was stuck at side load. re reading now I was using the /e/ recovery and not TWRP. I couldn’t get into the sideload on the device. I did it once before but not I am stuck at the “NO COMMAND” droid screen.
Maybe I should go back and install TWRP and try again?
Also is there a clear set of steps here? Especially how to get the phone to the right place for the sideload. Being new to this I googled and found some other instructions for sideloading that are tangential to installing /e/.
Thanks again for the help, I am real close to chasing the pig into the stye…
this is where I was stuck last night. How do I get to this selection?
Yes, when I flashed my G7+s the temporary recovery.img I used was TWRP. Then I moved to the next step which is side loading the patch file for the slot and finally e-0.17-q-20210529117214-dev-river.zip
This e0.17.zip also will flash over TWRP with the /e/recovery image so in the end TWRP will be gone and you will have /e/OS and /e/recovery. The TWRP step is just a temporary flash to patch the slots and /e/OS (/e/Recovery is contained in that final zip you flash).
If you go back to TWRP this is the screen where you hit “
Install” - Advanced.
the next screen will include ADB sideload.
@aibd and I may have different versions of TWRP installed. In my version you go to “Advanced” on the screen posted then “ADB Sideload”. It might vary but should say “ADB Sideload” in either circumstance.
Sorry, more a case or wearing the wrong glasses! “Advanced” it is.
MANY thanks for aibd and egx470! With you clues I was able to crack this nut and got /e/ installed and am configuring away!
It is confusing the main thing I learned is use TWRP. I did that and then things made sense.
Having a supportive community is what led me to choose /e/ over some other alternatives.
Happy for you @newts . Lots of good folks here to help. Ive only been here a few months but @aibd has taught me a TON as well as many others. FYI, if you put a “@” symbol before someone’s name it will tag them and help link through the community. Enjoy your new device!
Just got a XT1962-1 in the mail. Unlocked OEM and enabled USB debugging in settings. Ran adb reboot bootloader successfully, but fastboot does not see the device. Did I miss a step?
You did adb devices and got a “seen”? but then fastboot devices was a " no show"?
This thread will probably be worth checking