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

[Q] Boot Loop and not entering recovery!

I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!

Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?

AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!

Am on windows and i had fastboot_adb(1.0.32) already installed.

Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.

[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.

Help! TWRP "cant mount .*" boot loop

Hi all.
After OTA upgrade to android 6 of unlocked unrooted nexus 7 2013 WiFi i decided to unlock and install twrp.
I used adb and fastboot to flash version 2.8.7.
It went smooth but after reboot to recovery, twrp shell returns "can't mount *" for all partitions. And the device is bootlooping into this state (unless I boot into bootloader).
The worst part is that my pc wont recognise the tablet when connected. Adb devices returns an empty list. So i cant even flash stock recovery or do anything uing adb/fastboot.
HELP!!!!

[solved] falshed factory image manually using fastboot
It seems fastboot recognized the device while adb/pc couldn't.
I downloaded Android 6 factory image from google and flashed-all that.
Just updating in case some other noob who doesn't fully understand adb/fastboot relations.

Stuck in TWRP and fastboot not working

Hello. I decided today to clean install the Pixel Experience 10 rom. I previously had a Pixel Experience 9.0 Pie. I did the following:
1. Booted into TWRP and selected Format Data
2. Everything is deleted, so it's time to flash a new rom. The guide says to go Advanced/ADB sideload and enter a command.
3. Command is not working. My phone is connected to the computer but it's not recognized. I can't even manually transfer it to the phone so i can install it via TWRP.
So i enter fastboot. Phone is recognized. When i type fastboot devices i get this:
Code:
C:\adb>fastboot devices
42abad9b fastboot
If i try to flash again a TWRP, my phone disconnects and it asks to reboot the phone by pressing a volume button. And i am stuck here. Nothing i can do. Any suggestions? I haven't done anything unusual. I am truly desperate. Any help will be appreciated.

naruto14 said:
Hello. I decided today to clean install the Pixel Experience 10 rom. I previously had a Pixel Experience 9.0 Pie. I did the following:
1. Booted into TWRP and selected Format Data
2. Everything is deleted, so it's time to flash a new rom. The guide says to go Advanced/ADB sideload and enter a command.
3. Command is not working. My phone is connected to the computer but it's not recognized. I can't even manually transfer it to the phone so i can install it via TWRP.
So i enter fastboot. Phone is recognized. When i type fastboot devices i get this:
If i try to flash again a TWRP, my phone disconnects and it asks to reboot the phone by pressing a volume button. And i am stuck here. Nothing i can do. Any suggestions? I haven't done anything unusual. I am truly desperate. Any help will be appreciated.
Click to expand...
Click to collapse
Hi !
Did you bypass ARB with dummy.img before you flashed TWRP?
Do you use win 10, if you are change usb or use usb hub. If that doesn't help use win 7.
follow the link for details
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Good luck and stay safe.

drnightshadow said:
Hi !
Did you bypass ARB with dummy.img before you flashed TWRP?
Click to expand...
Click to collapse
I already had TWRP from long ago. And i didn't even try to flash a new ROM. I just formatted Data. I have the TWRP version 3.3.1-0. But as i said, PC does not recognize phone in TWRP and i can't adb sideload any ROM because of it.

naruto14 said:
I already had TWRP from long ago. And i didn't even try to flash a new ROM. I just formatted Data. I have the TWRP version 3.3.1-0. But as i said, PC does not recognize phone in TWRP and i can't adb sideload any ROM because of it.
Click to expand...
Click to collapse
Go back to previous version of TWRP(latest is buggy) or use OrangeFox recovery.
But still if you lose custom recovery you need again start over and bypass ARB.
And check if your bootloader is still unlock.

drnightshadow said:
Go back to previous version of TWRP(latest is buggy) or use OrangeFox recovery.
But still if you lose custom recovery you need again start over and bypass ARB.
And check if your bootloader is still unlock.
Click to expand...
Click to collapse
I can't go to a previous version of TWRP. I can't flash any recovery via fastboot because of the problem i said at the first post. I somehow managed to boot into some previous versions of TWRP via a tool called TOOL_ALL_IN_ONE, but nothing changed. I had the same exact problems.
How will i check in my current status if bootloader is still unlocked?

naruto14 said:
I can't go to a previous version of TWRP. I can't flash any recovery via fastboot because of the problem i said at the first post. I somehow managed to boot into some previous versions of TWRP via a tool called TOOL_ALL_IN_ONE, but nothing changed. I had the same exact problems.
How will i check in my current status if bootloader is still unlocked?
Click to expand...
Click to collapse
Use this and post the result...
Code:
fastboot oem device-info
So you managed to get TWRP via TOOL_ALL_IN_ONE, ... when you are in TWRP flash TWRP again via TWRP or better flash OrangeFox Recovery(use SD CARD or adb push - for more info google it for adb commands), than reboot it directly into recovery again by TWRP option reboot to recovery... and now you can flash your ROM.
So make it simple
1st time you'll boot in TWRP by TOOL_ALL_IN_ONE,
than you'll flash recovery via TWRP and make it permanent,
Than you'll directly reboot to recovery via TWRP,
now you can wipe and flash your ROM.
Happy ending :highfive:

The problem was that i couldn't use ADB sideload because the phone wasn't recognized by the computer. And i fixed it in a very weird way, by connecting the phone to the PC monitor's USB hub and that way the phone was discovered by the computer. So i fastbootted the latest TWRP and then easily transferred the ROM i wanted to flash via TWRP. It's crazy that i spent all day just to connect the phone to a USB hub so it could work...

naruto14 said:
The problem was that i couldn't use ADB sideload because the phone wasn't recognized by the computer. And i fixed it in a very weird way, by connecting the phone to the PC monitor's USB hub and that way the phone was discovered by the computer. So i fastbootted the latest TWRP and then easily transferred the ROM i wanted to flash via TWRP. It's crazy that i spent all day just to connect the phone to a USB hub so it could work...
Click to expand...
Click to collapse
I'm glad that you fixed your phone :highfive:
I told you usb hub is the solution :laugh: yeah win10 sh*t mess with usb and all other stuff :crying: its a total [email protected]'ll never gonna use it.
nicee your phone is alive now ....
Good luck and stay safe.