Develop Bugs

[Q] Stuck in recovery with Fastboot and ADB failure

Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,

solved
I used another laptop with a fresh skipnote nexus toolkit and everything worked just fine.
shakrooph said:
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
Click to expand...
Click to collapse

Potential brick after update, need help with ADB

Hi,
I put CM11 on my fire phone successfully. After the 8/29 update I decided I wanted to be up to date so I went to the recovery but instead of adding both zips (CM11 and GAPPS) I only added GAPPS. Now the phone just hangs on that first Amazon screen,
I can go to the fire system recovery screen by holding down the UP key and powering the button on. I tried to load the stock Fire firmware using that method and I get the following message:
assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") E:Error in /tmp/update.zip (status 7) Installation aborted
Any ideas what I should do from here?
Thanks

I'm not familiar with installing ADB on windows(if you use that), but I'm sure there is a thread somewhere. Once you have everything in place it's a simple matter of connecting your phone to the pc via the usb chord and selecting the "update using ADB" option in amazon recovery. Instructions are at the bottom of the screen. In linux you use the command sudo adb sideload "FilePathGoesHere". <-- that file is the update.bin you download from amazon. I'm guessing in windows you open the command prompt as administrator and use the same command without the sudo part attached. wiping data and factory resetting is always a good practice before making changes as well. Hopefully someone can give you a more precise description of what to do if this does not help.

I went through the same issue and realized that the version of fire os which I can sideload is specified somewhere. I had to try a few different update.bin until finally it worked with the unlocked gsm version downloaded from the Amazon site. I can't post links so just append the following to amazon.com
/gp/help/customer/display.html?nodeId=201607550

MrLumpkins said:
I went through the same issue and realized that the version of fire os which I can sideload is specified somewhere. I had to try a few different update.bin until finally it worked with the unlocked gsm version downloaded from the Amazon site. I can't post links so just append the following to amazon.com
/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
This was my problem. The ROM I had was for factory unlocked but the phone I have is AT&T Unlocked. After some googling I found the right .bin file.
Thanks for your help!

Same issue
I am having the same issue, ATT Fire phone, but i just found out my /system/ is wiped.. I can boot TWRP but i cannot mount it to my PC.. I tried doing an adb sideload and my PC wont even recognize it.. It did before this happened, but now it does not.. When i try to boot the phone, no animations or anything, just black screen after Safestrap loads.

ADB wont recognize my HTC M8 (no devices error), cant sideload a rom, please help!

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

Question PocoF3 bricked. Please help.

I've googled and read posts for hours but nothing I tried works.
I was on Miui.eu V12.5.4.0 and decided to update to V12.5.5.0 using Twrp. It updated fine. However, I was not able to get my phone to root with magisk. So I dirty flashed back to V12.5.4.0 but for some reason when I tried to reboot to system, it prompted that no os is installed and I accidentally tapped reboot.
So now my phone is stuck on a boot loop on fastboot.
I tried Miflash tool. It ran for a few minutes but eventually got an error:Sending sparse 'userdata' 1/*3 (741188 KB) FAILED (Error reading sparse file).
I tried to use OTG on twrp but it seems like I can't access internal storage anymore. It shows up empty.
I tried to use adb sideload to push V12.5.4.0 rom into the phone but it says
loading: 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip' *
I did more digging and found this https://forum.xda-developers.com/t/q-adb-cant-read-sideload.1990405/page-3#post-69648733.
I tried to allow large address aware on adb and got this error instead
adb: failed to read command: No error
And the final method I tried was to use adb push to /sdcard/.
From the guides I saw online, after you typed in the command and press enter, a text stating the progress of the transfer should appear but mine did not. After a few minutes, this error appeared
"failed to copy 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip' to '/sdcard//xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip': write failed: No space left on device"
Any advice will really help. Thanks.

Zythol said:
I've googled and read posts for hours but nothing I tried works.
I was on Miui.eu V12.5.4.0 and decided to update to V12.5.5.0 using Twrp. It updated fine. However, I was not able to get my phone to root with magisk. So I dirty flashed back to V12.5.4.0 but for some reason when I tried to reboot to system, it prompted that no os is installed and I accidentally tapped reboot.
So now my phone is stuck on a boot loop on fastboot.
I tried Miflash tool. It ran for a few minutes but eventually got an error:Sending sparse 'userdata' 1/*3 (741188 KB) FAILED (Error reading sparse file).
I tried to use OTG on twrp but it seems like I can't access internal storage anymore. It shows up empty.
I tried to use adb sideload to push V12.5.4.0 rom into the phone but it says
loading: 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip' *
I did more digging and found this https://forum.xda-developers.com/t/q-adb-cant-read-sideload.1990405/page-3#post-69648733.
I tried to allow large address aware on adb and got this error instead
adb: failed to read command: No error
And the final method I tried was to use adb push to /sdcard/.
From the guides I saw online, after you typed in the command and press enter, a text stating the progress of the transfer should appear but mine did not. After a few minutes, this error appeared
"failed to copy 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip' to '/sdcard//xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip': write failed: No space left on device"
Any advice will really help. Thanks.
Click to expand...
Click to collapse
Press Power+Volume Down and go to fastboot and flash a fastboot rom. Should work

did you try fastboot format userdata ?

soneji said:
Press Power+Volume Down and go to fastboot and flash a fastboot rom. Should work
Click to expand...
Click to collapse
Do this to avoid actual bricking of your phone.
Safer ways always better

Thanks for the responses. I managed to fixed it with MiFlash Tool. The issue I had was that the Tool was using an older version of fastboot somewhere in my computer and not the latest that it came with. And that caused the flashing to fail because some commands didn't exist. I deleted the older version and it works. Thanks again!

Magisk Method for my phone, XT1952-T, doesn't seem to be working

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.