Related
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
GreyhoundX said:
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
Click to expand...
Click to collapse
I would flash an ruu thru hboot and then do a factory rest from hboot. Then if it boots fine flash cwm recovery thru hboot and then the su binaty thru recovery to regain root. Once you have recovery working again then flash back to cm7 or another rom of your choice thru recovery.
Or you could try to just reflash cwm recovery thru hboot, and then if you can access recovery wipe everything in mounts and storage except sdcard and emmc, and then restore a nandroid or flash a new rom.
RUU's - http://pvillecomp.com/?page_id=22
Latest cwm recovery - http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
Latest su binary - http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
How to flash with hboot - http://pvillecomp.com/?page_id=79
You may also want to upgrade to the newest radio 2.15.10.07.07 - http://pvillecomp.com/?page_id=18
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
GreyhoundX said:
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
Click to expand...
Click to collapse
Try flashing the recovery and then see if you can access it.
If you have adb setup and have fastboot, you can try to erase the recovery partition by typing " fastboot erase recovery " without quotes into a cmd prompt on your pc. And then flash the recovery from above. Sounds like something is either messed up with your boot or recovery partition or img.
You can also try to use fastboot to erase the boot partition " fastboot erase boot " and then try an ruu again.
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
GreyhoundX said:
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
Click to expand...
Click to collapse
That red triangle is the stock recovery, try to do a factory reset now or try the sugestions i added to the post above.
Factory reset doesn't work. It shows me a phone with a green circle then goes into the boot loop.
I'll try the ADB stuff later today when I'm back from work. I've never used it before. Thanks so much for helping.
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
GreyhoundX said:
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
Click to expand...
Click to collapse
Adb will not work in hboot but fastboot will. You can use adb in recovery though, not just booted to the os. The error device not found is probably because you were trying adb from hboot, or because you dont have the correct drivers on your pc. Adb and fastboot are 2 different programs, fastboot is not an adb command. If you need the fastboot.exe file or the drivers you can get them here. http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip
I ran "fastboot erase boot" and it said "erasing 'boot'...FAILED (remote: not allowed)". Can I try running or flashing something else?
If I run "fastboot devices" it shows my device ID with fastboot next to it so I know it's connecting.
Thanks for putting up with this, can't imagine what caused this.
Hmm not sure, seems it may be some sort of hardware issue or disk failure. If you cant get it to boot after an ruu, and you cant factory reset or access a custom recovery or get fastboot to erase or flash, im not sure what else you could do. My only other sugestion would be to try the ruu.exe that you do from your pc with the phone connected. Flash the stock recovery PB31IMG.zip first before doing so as i believe its required for the ruu.exe. It may work and it may not im not exactly sure how the ruu.exe works as i have never used one, but i believe you just boot into hboot and then run the exe on your pc.
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
GreyhoundX said:
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
Click to expand...
Click to collapse
Take a PB31IMG.zip ruu ( http://pvillecomp.com/?page_id=22 ) and rename it update.zip
Put the update.zip file on your pc in the same folder as the fastboot.exe file. (Where adb is installed)
Boot into hboot with the phone pluged in to the pc. Make sure it says fastboot in red at the top of the hboot screen.
Open a cmd prompt to the directory where fastboot.exe is (eg C:\ADB\)
Type without quotes " fastboot update update.zip " and hit enter.
Here is some good info on fastboot.
http://wiki.cyanogenmod.com/wiki/Fastboot
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
GreyhoundX said:
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
Click to expand...
Click to collapse
Use 7-zip, winzip and winrar dont work the best for android files.
Think I'm just going to give up on this one since the flashing doesn't work...what a hassle. I wish there was some diagnostics tool that would just tell me if the phone is physically broken.
I have followed the instructions carefully and have unlocked my phone etc all the way down to
In cmd:
•fastboot recovery1.img
5.boot into recovery through bootloader and Install the ROM you placed on the SD card, (via install zip fileselect the rom zip)
6.Reboot the phone, ensure the rom is working fine and you have root access you can test this by turning on usb debugging then:
Now If I enter the bootloader and choose " recovery" the phone restarts, then I am presented with a black screen and an icon of the phone and an exclamation mark in a triangle.
I have searched the forums but am not finding anything useful in there, except a guy who was stuck even more than me.
BTW i am still unsure why I had to open cmd and run recovery1img ???
I take it recovery mode must allow me to install the ROM .. mainly DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00 which the guide said ?? since I tried doing this while the phone was on and it's just a zip file which opens up with a few files inside, non of which seems to be an installer? I presume that recovery mode will actually manage to install right from the zip?
Please help with this as I have totally hit a wall and cannot understand the icon with the exclamation mark I mentioned! am just totally stuck.
What guide?
pontypool said:
I have followed the instructions carefully and have unlocked my phone etc all the way down to
In cmd:
•fastboot recovery1.img
5.boot into recovery through bootloader and Install the ROM you placed on the SD card, (via install zip fileselect the rom zip)
6.Reboot the phone, ensure the rom is working fine and you have root access you can test this by turning on usb debugging then:
Now If I enter the bootloader and choose " recovery" the phone restarts, then I am presented with a black screen and an icon of the phone and an exclamation mark in a triangle.
I have searched the forums but am not finding anything useful in there, except a guy who was stuck even more than me.
BTW i am still unsure why I had to open cmd and run recovery1img ???
I take it recovery mode must allow me to install the ROM .. mainly DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00 which the guide said ?? since I tried doing this while the phone was on and it's just a zip file which opens up with a few files inside, non of which seems to be an installer? I presume that recovery mode will actually manage to install right from the zip?
Please help with this as I have totally hit a wall and cannot understand the icon with the exclamation mark I mentioned! am just totally stuck.
Click to expand...
Click to collapse
That is stock recovery...that means that you are still on the stock recovery and if you already unlocked the device you should flash a custom recovery.
glevitan said:
That is stock recovery...that means that you are still on the stock recovery and if you already unlocked the device you should flash a custom recovery.
Click to expand...
Click to collapse
am i correct in thinking the instructions for flashing a new recovery aren't in the guide? could you point me in the right direction please?
Here is what i did with my device "noobie here"
1. Unlock my bootloader via htc dev
2. Once my bootloader is unlock i use "easy ace root tool"
tool link is here http://forum.xda-developers.com/showthread.php?t=2169518
3. Run the tool as administrator
4. Phone is rooted
hope it helps :fingers-crossed:
pontypool said:
am i correct in thinking the instructions for flashing a new recovery aren't in the guide? could you point me in the right direction please?
Click to expand...
Click to collapse
the command is wrong, it should be fastboot boot recovery1.img, you'll use fastboot flash later onwards
Steam. said:
the command is wrong, it should be fastboot boot recovery1.img, you'll use fastboot flash later onwards
Click to expand...
Click to collapse
Neither response helps i'm sorry. The easy root tool is an app that performs the same function as the guide, but is no longer supported and this:
*Quote:
Originally Posted by pontypool View Post
am i correct in thinking the instructions for flashing a new recovery aren't in the guide? could you point me in the right direction please?
the command is wrong, it should be fastboot boot recovery1.img, you'll use fastboot flash later onwards
* Only helps with that one aspect of the problem. not the fact that Typing Su results in a response saying you do not have permission. Which is what the topic of the thread was.
pontypool said:
Neither response helps i'm sorry. The easy root tool is an app that performs the same function as the guide, but is no longer supported and this:
*Quote:
Originally Posted by pontypool View Post
am i correct in thinking the instructions for flashing a new recovery aren't in the guide? could you point me in the right direction please?
the command is wrong, it should be fastboot boot recovery1.img, you'll use fastboot flash later onwards
* Only helps with that one aspect of the problem. not the fact that Typing Su results in a response saying you do not have permission. Which is what the topic of the thread was.
Click to expand...
Click to collapse
what exactly are you trying to do?If you have an unlocked bootloader, just flash a custom ROM and a boot.img.
pontypool said:
Neither response helps i'm sorry. The easy root tool is an app that performs the same function as the guide, but is no longer supported and this:
*Quote:
Originally Posted by pontypool View Post
am i correct in thinking the instructions for flashing a new recovery aren't in the guide? could you point me in the right direction please?
the command is wrong, it should be fastboot boot recovery1.img, you'll use fastboot flash later onwards
* Only helps with that one aspect of the problem. not the fact that Typing Su results in a response saying you do not have permission. Which is what the topic of the thread was.
Click to expand...
Click to collapse
Have root access/confirm I have root access using the commands (as per the dev guide) which i don't , because despite following the guide, when i type Su it says permission denied.
pontypool said:
Have root access/confirm I have root access using the commands (as per the dev guide) which i don't , because despite following the guide, when i type Su it says permission denied.
Click to expand...
Click to collapse
anyone?
Take a look at this
http://forum.xda-developers.com/showthread.php?t=2367322
pontypool said:
I have followed the instructions carefully and have unlocked my phone etc all the way down to
In cmd:
•fastboot recovery1.img
5.boot into recovery through bootloader and Install the ROM you placed on the SD card, (via install zip fileselect the rom zip)
6.Reboot the phone, ensure the rom is working fine and you have root access you can test this by turning on usb debugging then:
Now If I enter the bootloader and choose " recovery" the phone restarts, then I am presented with a black screen and an icon of the phone and an exclamation mark in a triangle.
I have searched the forums but am not finding anything useful in there, except a guy who was stuck even more than me.
BTW i am still unsure why I had to open cmd and run recovery1img ???
I take it recovery mode must allow me to install the ROM .. mainly DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00 which the guide said ?? since I tried doing this while the phone was on and it's just a zip file which opens up with a few files inside, non of which seems to be an installer? I presume that recovery mode will actually manage to install right from the zip?
Please help with this as I have totally hit a wall and cannot understand the icon with the exclamation mark I mentioned! am just totally stuck.
Click to expand...
Click to collapse
i followed the same steps and basically recovery1.img is the new ClockWorkMod Touch Recovery and recovery.img is an old version of CWM modded specifically for the tools given to you in the guide. The guy who made the guide is really lazy so he made a typo and didn't bother to correct it. Instead of 'fastboot recovery1.img' it should be 'fastboot flash recovery recovery1.img'. This flashes CWM to your phone and from then on you can choose whether you want to S-OFF or just leave as S-On and flash boot.img everytime you want a new custom ROM. I had a bad experience with that guide so if i was you i would just flash the boot.img and then install the ROM given through recovery.
Hello I have HTC One X, which I have bought second hand (unfortunately). Turns out it was rooted, and ran on a custom rom. I wanted to revert to stock rom, but I think I have messed up. Now I am stuck in bootloader. I think I already have all the files I need, but it seems I have no longer access to my phone on the PC, so I can not transfer files to the (non-removable)'SD Card'. When trying to flash using cmd, I get the error FAILED <remote: not allowed>
I have used the factory reset in the bootloader, and have unrooted the phone, and re-locked the bootloader.(at the time I thought I had the right RUU but I only have a CWM backup)
Can anyone help me?
CID: O2__102
HBOOT: 1.36.0000
Radio: 5.1204.162.29
version: 3.14.207.27
If you have the specific nandroid backup you need, then you can use THIS TUTORIAL.
unikulkiss said:
If you have the specific nandroid backup you need, then you can use THIS TUTORIAL.
Click to expand...
Click to collapse
The problem is, when I try to flash I get the above mentioned error FAILED <remote: not allowed>
Bozso46 said:
The problem is, when I try to flash I get the above mentioned error FAILED <remote: not allowed>
Click to expand...
Click to collapse
Have you done everything the tutorial says?
At what exact step did you get this error? You have to be more precise.
If you are stuck at bootloader, you should be able to flash recovery (after you re-unlock the bootloader) and then, from recovey, you can mount your internal sd card to be accessed from the PC via USB cable.
You also have to have the required drivers installed to properly run fastboot commands, as explained in the tutorial.
Bozso46 said:
Hello I have HTC One X, which I have bought second hand (unfortunately). Turns out it was rooted, and ran on a custom rom. I wanted to revert to stock rom, but I think I have messed up. Now I am stuck in bootloader. I think I already have all the files I need, but it seems I have no longer access to my phone on the PC, so I can not transfer files to the (non-removable)'SD Card'. When trying to flash using cmd, I get the error FAILED <remote: not allowed>
I have used the factory reset in the bootloader, and have unrooted the phone, and re-locked the bootloader.(at the time I thought I had the right RUU but I only have a CWM backup)
Can anyone help me?
CID: O2__102
HBOOT: 1.36.0000
Radio: 5.1204.162.29
version: 3.14.207.27
Click to expand...
Click to collapse
It's quite easy btw,
Download nandroid backup for your CID from here &
Just flash any recovery like CWM or TWRP which will mount ur device's USB Storage to pc.
now, just follow the steps to restore that backup into the phone, u'll be on complete stock!
Also, you can flash the particular RUU for your device, if available can be found here
Installing RUU doesn't require anything to be done on phone, just connect it to pc, it'll take care of the rest.
arun6106 said:
It's quite easy btw,
Download nandroid backup for your CID from here &
Just flash any recovery like CWM or TWRP which will mount ur device's USB Storage to pc.
now, just follow the steps to restore that backup into the phone, u'll be on complete stock!
Also, you can flash the particular RUU for your device, if available can be found here
Installing RUU doesn't require anything to be done on phone, just connect it to pc, it'll take care of the rest. Just match ur CID
Click to expand...
Click to collapse
How exactly do you match the RUU CID? I don't see the cid on the filenames there. Mine is HTC_203
unikulkiss said:
Have you done everything the tutorial says?
At what exact step did you get this error? You have to be more precise.
If you are stuck at bootloader, you should be able to flash recovery (after you re-unlock the bootloader) and then, from recovey, you can mount your internal sd card to be accessed from the PC via USB cable.
You also have to have the required drivers installed to properly run fastboot commands, as explained in the tutorial.
Click to expand...
Click to collapse
This seems like it should work. How do I re-unlock the bootloader? Because my only problem is, that I can not mount my internal sd card, and I think it is because the phone in re-locked...
Bozso46 said:
This seems like it should work. How do I re-unlock the bootloader? Because my only problem is, that I can not mount my internal sd card, and I think it is because the phone in re-locked...
Click to expand...
Click to collapse
Get your unlock token from htcdev,
and use fastboot flash unlocktoken Unlock_Code.bin command in fastboot.
Then just look at ur phone, use volume up key to move up and power button to select.
Phone will reboot and bootloader will be unlocked, also it will factory reset the phone!
Bozso46 said:
This seems like it should work. How do I re-unlock the bootloader? Because my only problem is, that I can not mount my internal sd card, and I think it is because the phone in re-locked...
Click to expand...
Click to collapse
You can unlock your bootloader by using THIS TUTORIAL or with THIS TOOL which does the same thing basically.
After installing CM12, I got a random reboot and it asked me to enter my password. It accepted my password and said that my files were corrupt. I rebooted into recovery, and was unable to install any zip files or wipe anything. I tried installing stock recovery, locking bootloader, and installing the RUU (via the .exe and the .zip in hboot) and now I cannot get to a ROM or recovery. I also tried installing TWRP and was unable to boot that as well. I do have HTC Sync manager installed. I also tried the Windroid Universal Android Toolkit, which did not seem to do anything either.
If you have the proper drivers, and followed all the instructions in the RUU thread, and you still can't boot to system or recovery, your beyond screwed.
There's more than likely no hope. Maybe some other brilliant mind on XDA can figure something out.
FoxyDrew said:
If you have the proper drivers, and followed all the instructions in the RUU thread, and you still can't boot to system or recovery, your beyond screwed.
There's more than likely no hope. Maybe some other brilliant mind on XDA can figure something out.
Click to expand...
Click to collapse
It claims that installing recoveries and zips through fastboot is successful. Is there some kind of OEM recovery thing like there is with other phones? (i.e. what the OEM's use to initially flash the device)
EDIT: Here's a post on reddit that is exactly what is happening for me: http://www.reddit.com/r/AndroidQues..._recovery_wont_start_stuck_in_bootloader_htc/
When trying to flash an RUU through fastboot I get: sending 'zip' (size) ...OKAY [time]
writing 'zip" ... FAILED: Remote not allowed
When doing fastboot update I get: Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '`√'
FroyoShark said:
It claims that installing recoveries and zips through fastboot is successful. Is there some kind of OEM recovery thing like there is with other phones? (i.e. what the OEM's use to initially flash the device)
EDIT: Here's a post on reddit that is exactly what is happening for me: http://www.reddit.com/r/AndroidQues..._recovery_wont_start_stuck_in_bootloader_htc/
Click to expand...
Click to collapse
A RUU is from the OEM, it's what they use.
In the RUU thread I linked you too try the download link from the original HTC site, and screenshots of the errors your getting would help.
[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.