Develop Bugs

[HELP] Phone in bootloop, adb can't connect

Just a moment ago I pushed my own custom framework-res to the phone. I had only edited some picture files inside it. After rebooting it worked correctly so I edited some more images, booted into clockworkmod recovery and tried to push in a new framework. But this time my adb just gave me an error "error: device offline".
After rebooting into revoked recovery I tried using adb again but with the same result. I also noticed that my computer suddenly installed all of the Android related drivers again, there were four different drivers it installed.
I thought it was because of my custom framework so I decided to flash my custom rom again. I didn't do a full wipe and after rebooting I got stuck in a bootloop.
So currently the only way I can access the phone is in fastboot. My computer recognizes the phone when it's in recovery but I can't use any adb commands. When I type adb devices it lists my devices but says it's offline. I tried doing the first step of the rooting process and it worked fine but after booting into recovery I tried doing the step2 but the device was still offline.
Is this because of my Windows drivers or did I screw up the Android system somehow?

You should have made a backup using nandroid. I though think you need to wipe.
Sent from something using the internet.

[Q] Galaxy Nexus Root and Fastboot not working

My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!

sonshadsil94 said:
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
Click to expand...
Click to collapse
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.

Petrovski80 said:
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Click to expand...
Click to collapse
I know where the files are, but how am I supposed to remove or rename them without root access?

sonshadsil94 said:
I know where the files are, but how am I supposed to remove or rename them without root access?
Click to expand...
Click to collapse
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250

bk201doesntexist said:
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
Click to expand...
Click to collapse
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?

sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.

sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
whats the exact fastboot command you're using to flash twrp?
problem was you made a backup of stock, which has files that restore, on boot, the stock recovery.
sent from my i9250

efrant said:
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
Click to expand...
Click to collapse
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.

sonshadsil94 said:
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
Click to expand...
Click to collapse
Try using a different USB cable, and try using a different port on the back of your PC.

efrant said:
Try using a different USB cable, and try using a different port on the back of your PC.
Click to expand...
Click to collapse
I tried both of those just now, with the same error message as before.

sonshadsil94 said:
I tried both of those just now, with the same error message as before.
Click to expand...
Click to collapse
The only thing I can think of is flash the LC03 bootloader. Try flashing that first, and make sure you have the latest version of fastboot. Then try again.

would running terminal in windows with admin privileges help?
sent from my i9250

Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2

deeren said:
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks deeren, i asked him what was the exact command he was using, that error had to be syntax error.
sent from my i9250

Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.

sonshadsil94 said:
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
Click to expand...
Click to collapse
please edit the title of the thread to include the tag "[SOLVED]".

bk201doesntexist said:
please edit the title of the thread to include the tag "[SOLVED]".
Click to expand...
Click to collapse
How do you edit the title?

I have same problem to...

sonshadsil94 said:
How do you edit the title?
Click to expand...
Click to collapse
Edit first post?
Sent from my i9250

How to recover my phone

I didn't to a NANDROID backup before trying to flash a new ROM (fail I know). I had factory reset my phone before flashing the new ROM, but the ROM that was flashed hasn't installed correctly and the phone no longer powers completely on. I would like to just throw a different ROM/gapps on the SD card, but I can no longer access it on my computer since the phone will not completely boot up.
Someone suggested somewhere that I mount the USB Storage from recovery, but in the mount + storage recovery section all I see is mount /data, mount /system, and mount /cache, none of which make the GNEX storage available on my computer.
Any suggestions for fixing this problem, or for simply accessing the SD card on my computer without the phone turning completely on?
Thank you.

You can adb push a ROM while booted in a custom recovery. You should check out the stickies in this forum & the general forum.

Download the factory image from google for your phone. Extract it and get system.img from it (you have to extract it a few times). Get adb/fastboot setup by installing the correct drivers and the android sdk (there may be files posted here at xda with just the files needed for adb/fastboot). Then put system.img in the same folder as fastboot.exe (assuming you use windows).
Connect your phone while in bootloader (both volume keys + power) and from a command prompt in that directory, type:
1) fastboot flash system system.img
2) fastboot reboot
It won't wipe anything other than /system.

I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.

Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.

mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
I have the same problem. Going to take a look at what mwalt suggested tomorrow. Paybacks, if you find a solution, can you please post it here? Thanks.

mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
I was finally able to flash the system.img from Google, but see no change. What is expected to happen once this .img has been pushed?
EDIT: Ended up flashing the entire .zip installation instead of just the system.img file and I have a stock install atm. Thank you for the help!
To Man_Utd, I ended up just re-executing the superboot r5 while in bootloader and it seemed to help recognize the phone..-shrug-.

[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix

[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix
Hey,
I have a ZE551ML and want to install CM. I am following the guide here. I have run into a problem on the first step which points to the guide here. At step 7 of this guide it has me use the command: fastboot flash system system.img. This fails with the error in the title of this post: FAILED <remote: Permission denied>. I have been googling this and no one has a concrete solution. Currently my phone will not even boot as the three fastboot commands before this one worked just fine and replaced the files. Any help would be greatly appreciated!
Cheers,
Eric.

Even though it'll say permission denied, flashing recovery WILL work. From there you can either flash a custom ROM (from twrp) or reflash stock firmware (through stock recovery).
That's the only fix I've found. To flash a usable ROM and boot into it. May need to turn on USB debugging in dev options. But after doing those two things, fastboot will stop with the permission denied issues.

Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.

eric_lensherr said:
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
Click to expand...
Click to collapse
Found a guide here dealing with this error, working on it.

Hey,
So I got my phone unbricked by flashing the recovery with the stock ASUS firmware "ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V2.19.40.22 for WW SKU only" available at the ASUS official website and following a guide at an outside link that I can't post.
Now, I have enabled developer mode and turned on USB debugging but am now getting the permission denied on all fastboot commands of the OTA guide, step 7.
Does anyone know a good next step?

Hey, managed to root the phone with: Temporary CWM

After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!

rlaw said:
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
Click to expand...
Click to collapse
Yes, I did do this but I have now checked the check mark to make it always trust my computer. I then booted into fastboot but still get permission denied despite having root through CWM and having this checked off.
When I got root through CWM by the fastboot tethered recovery it gave me permission denied on all steps but it still booted into CWM recovery. I was then able to install SuperSU to root it, though it gave me an error, and I used Root Checkerr to see if the phone was rooted. It says it is but I am still unable to flash any images onto the phone since I re-installed the stock firmware.
I'm super confused about this whole thing, IDK what to do now.

Flash stock recovery again and adb sideload the stock firmware all over.
This is the latest up-to-date 2.20.40.59 firmware: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.59-user.zip
If that doesn't work then idk. You can Google the permission denied errors for fastboot like I did and there are various possible problems/solutions.

So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.

eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.

rlaw said:
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
Click to expand...
Click to collapse
How can i tell if twrp recovery is successfully installed?

Hey, took a few days to cool off.
So it does seem I can replace recovery even though it says permission denied. I do this by using fastboot to flash the recovery, then from the bootloader on the phone I select restart bootloader and then when the bootloader re-appears I enter recovery mode ( I do this to prevent the possible replacing of the custom recovery by the stock OS). However recovery mode never boots when the latest twrp recovery is on the phone, I just end up back in the bootloader. When I flash the stock recovery back on this method successfully enters recovery mode. This also occurs if I just directly enter recovery mode after flashing twrp recovery.
Any thoughts?

eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
Same here. I'm using elevated cmd, and fastboot is recognizing my device. But I can't flash anything, can't erase cahce, can't reformat partitions. Always failed due to permissions. And I'm stuck in a bootloop, and can't get to recovery (it just goes back into the bootloop when I try). Literally the only avenue I have to interact with this phone is fastboot, and I can't do anything with it.

Yet another OTA softbrick thread. How screwed am I?

Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about

I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...

adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.

adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...

Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient

badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...

adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery

Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!