Hi there.
I have tried several custom Roms this in the past (5 years ago) and everything worked fine and then reversed it and put back the original rom. Now I need this device for a backup and wanted to try the latest Lineage 17.1 ROM I have soft briked my device. Since I´ve wiped my data I dont have a ROM to boot to.... :crying:
When following this Lineage installation guide https://wiki.lineageos.org/devices/m8/install I am stucked on the ADB Sideload procedure.
Every time I try the "adb sideload filename.zip" command I get the "no devices/emulators found" warning.
I have the latest TWRP (3.4.0.1) for my device, i tried installing HTC M8 drivers, Google ADB drivers, HTC Sync, nothing works, I can seem to make TWRP to connect to my PC.
Can someone please help me?
Thanks in advance
Badelhas said:
Hi there.
I have tried several custom Roms this in the past (5 years ago) and everything worked fine and then reversed it and put back the original rom. Now I need this device for a backup and wanted to try the latest Lineage 17.1 ROM I have soft briked my device. Since I´ve wiped my data I dont have a ROM to boot to.... :crying:
When following this Lineage installation guide https://wiki.lineageos.org/devices/m8/install I am stucked on the ADB Sideload procedure.
Every time I try the "adb sideload filename.zip" command I get the "no devices/emulators found" warning.
I have the latest TWRP (3.4.0.1) for my device, i tried installing HTC M8 drivers, Google ADB drivers, HTC Sync, nothing works, I can seem to make TWRP to connect to my PC.
Can someone please help me?
Thanks in advance
Click to expand...
Click to collapse
I had a similar problem a few days ago, and uninstalling HTC Sync and HTC drivers from my PC solved it for me.
beeewell said:
I had a similar problem a few days ago, and uninstalling HTC Sync and HTC drivers from my PC solved it for me.
Click to expand...
Click to collapse
Thanks a lot! That worked indeed. Sideloading Lineage a Gapps as we speak
Cheers
Hi folks,
can someone helps me? i'm having the same problem and i'm on this since 11 hours and nothing that i do make the adb sideload work. I have my Htc one m8 since it was out on 2014 and never root it. I manage to root it with the lineage installation guide because i didn't know anything about rooting. Now root is done, and twrp-3.5.2_9-0-m8 the latest version is intalled and i'm stuck on the command 'Sideload the LineageOS .zip package': it seems like the device is not found. This is the message that i got.
adb server version (31) doesn't match this client (41); killing...
error: failed to read response from server
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I have unnistall HTC Syn and its drivers many times then retry than reinstall them then retry but nothing work. My device is found and its sd card when i'm not on ADB sideload on TWRP. This is making me crazy!!!! I'm on windows 7. Thanks if someone can help
FINALLY!!!!
i manage to make the installation working!
Lineage team need to explain more precisely the installation process by giving where is needed some examples and give some other alternative methods. All the people don't understand the geecky language so you need to think like end users like us who didn't know anything about coding, command prompt expressions ect.... For exemple here:
"5 - Flash recovery onto your device:
fastboot flash recovery <recovery_filename>.img"
I thought doing this command " fastboot flash recovery <twrp-3.5.2_9-0-m8>.img " instead of " fastboot flash recovery twrp-3.5.2_9-0-m8.img " anyway...
For those in the same case like me in the future, the "adb sideload" stage didn't work for me. After some resarch sideloading is not nessessary. Just move or copy the LineageOS and Gapp into your phone or sd card then in TWRP choose install and select the files were you have put them and they will be installed like normal installation.
ADB Sideload stuck at 47%
Hi all I'm starting to suspect that the partition my recovery uses as temp storage is full. It gets stuck in the flashing process, I just tried side-loading with adb and it is now stuck, and has been for 1 hour. Latest message from ADB says...
forum.xda-developers.com
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Jpdel said:
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Click to expand...
Click to collapse
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
5.1 said:
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Click to expand...
Click to collapse
Jpdel said:
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
Click to expand...
Click to collapse
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
5.1 said:
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Jpdel said:
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
JarMagic said:
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
Click to expand...
Click to collapse
Hi,
This is not a "shime in if you have a similar issue" thread. You may open your own thread. But well, do you have the proper factory image for taimen? Is your USB cable ok? Is your ADB / Fastboot up to date? In the message above yours i posted a link with the latest version. Try this...
Sébastien.
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
JarMagic said:
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
Click to expand...
Click to collapse
Hello,
Do you have acces to recovery? Tried to sideload: https://dl.google.com/dl/android/aosp/taimen-ota-rp1a.201005.004-b5dff51e.zip
Good luck...
Sébastien.
5.1 said:
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Click to expand...
Click to collapse
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Jpdel said:
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Click to expand...
Click to collapse
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
5.1 said:
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Jpdel said:
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Click to expand...
Click to collapse
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
5.1 said:
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Jpdel said:
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Click to expand...
Click to collapse
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
5.1 said:
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Jpdel said:
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Click to expand...
Click to collapse
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
5.1 said:
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
Click to expand...
Click to collapse
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Jpdel said:
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Click to expand...
Click to collapse
Update: I finally was able to make the phone work!!!
In a last-ditch effort, I wiped the device, ran the Deuce Script, Reboot, Ran the flash-all.bat, Reboot, went to Recovery Mode > Enable ADB Update > Tried Sideload again of the OTA file, and there you go, I now again have a working device!!!
Thank you Sebastien @5.1 again for all your super kind support and knowledge! Truly am really grateful for your helpfulness!
From what I understand, the REVVLRY is just the Moto G7 Play rebranded. From that, I assumed that the method of using Magisk to root Moto devices would also work for the device (Unlocking bootloader, patching a file with Magisk using the stock firmware [learned that the hard way, ty sd_shadow], flashing that file with ADB, rebooting).
However, when finishing this and rebooting the phone, instead of "bad key" or "N/A" showing up, a serial code-like text is in its place. I hadn't taken the time to figure out what it actually is or means, but all I know is that it gets stuck on that screen, forcing me to use LMSA again which successfully returns the phone back to normal.
I am not a professional in development or code, but one thing I can point out is that the final number of the build number is different from my current one (file QPYS30.85-18-9-8 vs device QPYS30.85-18-9-10). Maybe this could be the issue? Although I have seen threads that managed to root even with a different version. Is there any potential reason that this happens? And what guide should I follow to root the REVVLRY if it is possible?
A question I probably should have asked from the start; about how long should I wait for the phone to reboot after Magisk is flashed? I may have just been impatient with the phone and not given it enough time to finish whatever it needed to.
Try this method instead:
Reflash stock and boot normally > (unlock bootloader if you haven't already) > reboot into bootloader > fastboot boot twrp > adb sideload magisk zip > reboot into system > install magisk apk
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
This is what I get when doing sideload with the magisk.zip. Is this normal, or is this already a sign of doing something wrong?
Thfaro said:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
This is what I get when doing sideload with the magisk.zip. Is this normal, or is this already a sign of doing something wrong?
Click to expand...
Click to collapse
Looks like the ADB connection isn't getting established. In TWRP, make sure to go into the Options (I think) mention and select the "ADB Sideload" option.
It seems to have worked, neither TWRP nor the Command returned any bad results. From here, do I continue as normal from the Magisk method?
Thfaro said:
It seems to have worked, neither TWRP nor the Command returned any bad results. From here, do I continue as normal from the Magisk method?
Click to expand...
Click to collapse
Yeah, after you flash the Magisk.zip, reboot back into the OS, rename Magisk.zip into Magisk.apk, and then install it like a normal app. Open it up and it'll detect root.
Flashing the zip went well, so I opened the app after renaming it and the "Installed" says N/A. Do I continue from there? I am sorry about all the questions by the way, it's my first go at rooting, and I haven't proven successful so far lol
Just to rule out the possibility of using Magisk to then patch the file like normal, sure enough, I get the same text. This time I managed to get a picture of it, though, not very clear.
The second picture is what happens after I wait for a bit. I'm going to put the phone back to the state after the zip flash with TWRP though.
Edit: Redoing all the step and not continuing forward, the string of text also seems to happen anyways, but I do manage to get past it and start the phone like normal. Magisk still says N/A however.
I'm trying to install LineageOS via fastbootd, since TWRP can't mount the super partition. I can flash most images with a method similar to this post, but "fastboot flash product product.img" fails with "FAILED (remote: 'No such file or directory')". "fastboot erase product" gives a slightly more helpful "FAILED (remote: 'Partition doesn't exist')". The only solution I was able to find was apparently for 32bit Windows systems, neither applies to my computer.
How can I create this partition or, if it exists, make fastbootd see it? Or do I have to enter something other than "product"?
"adb sideload lineageos.zip" while in Los recovery
HueyT said:
"adb sideload lineageos.zip" while in Los recovery
Click to expand...
Click to collapse
Yeah, that was the first plan, it's also what the official instructions say. But neither the LOS recovery, nor TWRP can mount the super partition, so sideload, flash, wipe, file explorer etc. all fail. At this point I think that TWRP for the OnePlus 7T (with or without "Pro") might just be unfinished software and not usable for ROM installation, but if you think it can work, please help here, it's my older thread about trying to get that to work: https://forum.xda-developers.com/t/recovery-unable-to-mount-storage.4378801/
Fabian R�ling said:
Yeah, that was the first plan, it's also what the official instructions say. But neither the LOS recovery, nor TWRP can mount the super partition, so sideload, flash, wipe, file explorer etc. all fail. At this point I think that TWRP for the OnePlus 7T (with or without "Pro") might just be unfinished software and not usable for ROM installation, but if you think it can work, please help here, it's my older thread about trying to get that to work: https://forum.xda-developers.com/t/recovery-unable-to-mount-storage.4378801/
Click to expand...
Click to collapse
MSMtool to go to last oos10, ota to latest oos11, install Los recovery, sideload los18.1 zip
HueyT said:
MSMtool to go to last oos10, ota to latest oos11, install Los recovery, sideload los18.1 zip
Click to expand...
Click to collapse
I just found this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
That's a Windows tool. Wine can launch it, but I don't even know if it would work, because if I do "adb reboot edl", the phone just shows a black screen, almost as if it was off (but not really, because then it would show something when charged).
Can EDL mode break? Or this ADB command? How else would I enter that mode? I've also read to hold volume up and volume down, but I've done that for some time and nothing happened.
Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…
I did not do the bootloader-based installation with that, so I'm not sure if I should mark this thread as solved.