[Q] HTC One M9 Dev edition update question - One (M9) Q&A, Help & Troubleshooting

Hey guys, I just received notification about update my htc to 5.1. However my htc one m9 is currrently rooted, unlocked, and s-on. If I update my htc without unrooted and locked my phone, will it be bricked? And if it works, after i update it, will root be lost ?

kamocheng said:
Hey guys, I just received notification about update my htc to 5.1. However my htc one m9 is currrently rooted, unlocked, and s-on. If I update my htc without unrooted and locked my phone, will it be bricked? And if it works, after i update it, will root be lost ?
Click to expand...
Click to collapse
You can't take an OTA when rooted. You won't brick your phone but it just won't work. Did you follow the instructions in the TWRP thread when you installed it to make a system IMAGE backup prior to rooting?
See post #3 here:
http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
Otherwise, you will need to run the Dev Edition RUU to return to stock (caution: this will wipe your internal storage) before you can take the OTA.
Or, you might do a search to see if anyone has a system image backup you can restore using Captain Throwback's instructions in post #3 above.

jollywhitefoot said:
You can't take an OTA when rooted. You won't brick your phone but it just won't work. Did you follow the instructions in the TWRP thread when you installed it to make a system IMAGE backup prior to rooting?
See post #3 here:
http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
Otherwise, you will need to run the Dev Edition RUU to return to stock (caution: this will wipe your internal storage) before you can take the OTA.
Or, you might do a search to see if anyone has a system image backup you can restore using Captain Throwback's instructions in post #3 above.
Click to expand...
Click to collapse
Thanks for the reply, no I didnt follow the instructions because I followed youtube video on how to root and unlocked my phone. Do you mind explaining to me how to run the Dev Edition RUU to return to stock? Thanks

kamocheng said:
Thanks for the reply, no I didnt follow the instructions because I followed youtube video on how to root and unlocked my phone. Do you mind explaining to me how to run the Dev Edition RUU to return to stock? Thanks
Click to expand...
Click to collapse
1) Download dev edition RUU.zip
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32 .617.30_Radio_01.01_U11440221_62.05.50320G_F_relea se_427069_signed.zip
link locate here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
2) Download htc_fastboot.exe and place it in your adb fastboot folder
the link to this file is also in the above link
3) backup everything on INTERNAL STORAGE - this WILL be wiped during this process
4) make nandroid backup just in case something goes wrong
5) reboot phone to download mode
6) connect computer to phone
7) type "htc_fastboot flash zip <NAME OF ZIP.zip>"
8) Wait until the process completes
You are now back to stock, but will have an unlocked bootloader
Boot into system and try to download and install OTA. If it fails to install, i think that means you need to re-lock bootloader (boot to download, "fastboot OEM lock"), then try to download and install the OTA again.
Once the OTA starts to install, be patient. It takes a very long time (maybe 30 minutes or more).
After the update completes, you should follow the instructions in post #3 of this thread to make a system image backup so you don't have to wipe everything to take the next OTA. If you ahve any questions about that process, you should ask them in the TWRP thread (http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720)

jollywhitefoot said:
1) Download dev edition RUU.zip
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32 .617.30_Radio_01.01_U11440221_62.05.50320G_F_relea se_427069_signed.zip
link locate here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
2) Download htc_fastboot.exe and place it in your adb fastboot folder
the link to this file is also in the above link
3) backup everything on INTERNAL STORAGE - this WILL be wiped during this process
4) make nandroid backup just in case something goes wrong
5) reboot phone to download mode
6) connect computer to phone
7) type "htc_fastboot flash zip <NAME OF ZIP.zip>"
8) Wait until the process completes
You are now back to stock, but will have an unlocked bootloader
Boot into system and try to download and install OTA. If it fails to install, i think that means you need to re-lock bootloader (boot to download, "fastboot OEM lock"), then try to download and install the OTA again.
Once the OTA starts to install, be patient. It takes a very long time (maybe 30 minutes or more).
After the update completes, you should follow the instructions in post #3 of this thread to make a system image backup so you don't have to wipe everything to take the next OTA. If you ahve any questions about that process, you should ask them in the TWRP thread (http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720)
Click to expand...
Click to collapse
Thanks a lot man !! If I could give you cookie, I totally would !! I'll be back, I'm gonna try it now

jollywhitefoot said:
1) Download dev edition RUU.zip
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32 .617.30_Radio_01.01_U11440221_62.05.50320G_F_relea se_427069_signed.zip
link locate here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
2) Download htc_fastboot.exe and place it in your adb fastboot folder
the link to this file is also in the above link
3) backup everything on INTERNAL STORAGE - this WILL be wiped during this process
4) make nandroid backup just in case something goes wrong
5) reboot phone to download mode
6) connect computer to phone
7) type "htc_fastboot flash zip <NAME OF ZIP.zip>"
8) Wait until the process completes
You are now back to stock, but will have an unlocked bootloader
Boot into system and try to download and install OTA. If it fails to install, i think that means you need to re-lock bootloader (boot to download, "fastboot OEM lock"), then try to download and install the OTA again.
Once the OTA starts to install, be patient. It takes a very long time (maybe 30 minutes or more).
After the update completes, you should follow the instructions in post #3 of this thread to make a system image backup so you don't have to wipe everything to take the next OTA. If you ahve any questions about that process, you should ask them in the TWRP thread (http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720)
Click to expand...
Click to collapse
Hey dude, I have a bit of problem, when I type in "fastboot flash zip <name.zip>" it says, fastboot.exe has stopped working. I changed the name of the file into 0PJAIMG.ZIP and I copy htc_fastboot.exe to fastboot folder. Could you help me?

kamocheng said:
Hey dude, I have a bit of problem, when I type in "fastboot flash zip <name.zip>" it says, fastboot.exe has stopped working. I changed the name of the file into 0PJAIMG.ZIP and I copy htc_fastboot.exe to fastboot folder. Could you help me?
Click to expand...
Click to collapse
Type "htc_fastboot flash zip 0PJAIMG.ZIP"

jollywhitefoot said:
Type "htc_fastboot flash zip 0PJAIMG.ZIP"
Click to expand...
Click to collapse
Do I need to double click htc_fastboot.exe first? Or I just click open cmd window here?

kamocheng said:
Do I need to double click htc_fastboot.exe first? Or I just click open cmd window here?
Click to expand...
Click to collapse
Command window here.
Can we keep everything in the same thread? Just pick one. Thanks.

jollywhitefoot said:
Command window here.
Can we keep everything in the same thread? Just pick one. Thanks.
Click to expand...
Click to collapse
Sorry about double threat, I tried it again and it seems to be half work
C:\Users\Andre\Downloads\ANDROID\TEST 2\fastboot_adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\Users\Andre\Downloads\ANDROID\TEST 2\fastboot_adb>fastboot oem rebootRUU
...
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Users\Andre\Downloads\ANDROID\TEST 2\fastboot_adb>htc_fastboot flash zip 0PJA
IMG.ZIP
sending 'zip'... (93262 KB) OKAY
sending time = 8.239 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
FAILFAIL90 hboot pre-update! please flush image again immediate
FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)
For "hboot-preupdate" response, restart the same procedure for device FA53PYJ024
93...
sending 'zip'... (93262 KB) FAILED (status read failed (Unknown error))
Execution time is 5(s)
C:\Users\Andre\Downloads\ANDROID\TEST 2\fastboot_adb>
I stuck, again in fastboot.exe has stopped working, any idea?

kamocheng said:
Sorry about double threat, I tried it again and it seems to be half work
C:\Users\Andre\Downloads\ANDROID\TEST 2\fastboot_adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\Users\Andre\Downloads\ANDROID\TEST 2\fastboot_adb>fastboot oem rebootRUU
...
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Users\Andre\Downloads\ANDROID\TEST 2\fastboot_adb>htc_fastboot flash zip 0PJA
IMG.ZIP
sending 'zip'... (93262 KB) OKAY
sending time = 8.239 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
FAILFAIL90 hboot pre-update! please flush image again immediate
FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)
For "hboot-preupdate" response, restart the same procedure for device FA53PYJ024
93...
sending 'zip'... (93262 KB) FAILED (status read failed (Unknown error))
Execution time is 5(s)
C:\Users\Andre\Downloads\ANDROID\TEST 2\fastboot_adb>
I stuck, again in fastboot.exe has stopped working, any idea?
Click to expand...
Click to collapse
First, what file is that? You need to flash "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32 .617.30_Radio_01.01_U11440221_62.05.50320G_F_relea se_427069_signed.zip" first. It's OK to rename it, but make sure you know what you're flashing.
Second, flash in download mode, not ruu mode. "Adb reboot download"

jollywhitefoot said:
First, what file is that? You need to flash "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32 .617.30_Radio_01.01_U11440221_62.05.50320G_F_relea se_427069_signed.zip" first. It's OK to rename it, but make sure you know what you're flashing.
Second, flash in download mode, not ruu mode. "Adb reboot download"
Click to expand...
Click to collapse
Yes i downloaded "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32 .617.30_Radio_01.01_U11440221_62.05.50320G_F_relea se_427069_signed.zip" then i rename it into "0PJAIMG.ZIP"
Still it failed. Here is the log:
C:\adb>adb reboot bootloader
C:\adb>htc_fastboot flash zip 0PJAIMG.ZIP
sending 'zip'... (93262 KB) OKAY
sending time = 5.447 secs
writing 'zip'... (bootloader) HOSD CL#506785
FAIL9: SD_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
Execution time is 7(s)
C:\adb>

kamocheng said:
Yes i downloaded "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32 .617.30_Radio_01.01_U11440221_62.05.50320G_F_relea se_427069_signed.zip" then i rename it into "0PJAIMG.ZIP"
Still it failed. Here is the log:
C:\adb>adb reboot bootloader
C:\adb>htc_fastboot flash zip 0PJAIMG.ZIP
sending 'zip'... (93262 KB) OKAY
sending time = 5.447 secs
writing 'zip'... (bootloader) HOSD CL#506785
FAIL9: SD_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
Execution time is 7(s)
C:\adb>
Click to expand...
Click to collapse
Bro. Put your phone in download mode. I feel like I've said that like ten times. Is even in the error you received.

jollywhitefoot said:
Bro. Put your phone in download mode. I feel like I've said that like ten times. Is even in the error you received.
Click to expand...
Click to collapse
I did, last log I posted was in download mode. No longer fastboot.exe has stopped working tho. Anyway the state of this phone is relocked.

kamocheng said:
I did, last log I posted was in download mode. No longer fastboot.exe has stopped working tho. Anyway the state of this phone is relocked.
Click to expand...
Click to collapse
Unlock bootloader.

jollywhitefoot said:
Unlock bootloader.
Click to expand...
Click to collapse
I just unlocked my phone and when I tried it, still I failed. Here is the log:
C:\adb>adb reboot bootloader
C:\adb>htc_fastboot flash zip 0PJAIMG.ZIP
sending 'zip'... (93262 KB) OKAY
sending time = 7.981 secs
writing 'zip'... (bootloader) HOSD CL#506785
FAIL9: SD_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
Execution time is 9(s)
C:\adb>
Here is what on my HTC screen
hTC download mode
End flashing, Press power key to contin
Security checking failed NOT_FIND SMART
IO
SD NOT MOUNTED
Under flash
I really regret I root my phone

kamocheng said:
I just unlocked my phone and when I tried it, still I failed. Here is the log:
C:\adb>adb reboot bootloader
C:\adb>htc_fastboot flash zip 0PJAIMG.ZIP
sending 'zip'... (93262 KB) OKAY
sending time = 7.981 secs
writing 'zip'... (bootloader) HOSD CL#506785
FAIL9: SD_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
Execution time is 9(s)
C:\adb>
Here is what on my HTC screen
hTC download mode
End flashing, Press power key to contin
Security checking failed NOT_FIND SMART
IO
SD NOT MOUNTED
Under flash
I really regret I root my phone
Click to expand...
Click to collapse
Does it boot into system right now?
Sorry, I know it's frustrating and my device is a-off so it's not exactly the same.
I just researched that last error and I think I was wrong about using download mode. I think if you're S-on you so in fact need to use ruu mode. And I went back and looked at the error you ran in ruu mode and that's a normal message and you just needed to rerun the flash command.
htc_fastboot oem rebootRUU
htc_fastboot flash zip 0PJAIMG.ZIP
(If you get error 90, repeat the last command)
I think last time you repeated the flash command before the device was back in ruu mode.
Edit: but this would be so easy if you just get sunshine and S-off

jollywhitefoot said:
Does it boot into system right now?
Sorry, I know it's frustrating and my device is a-off so it's not exactly the same.
I just researched that last error and I think I was wrong about using download mode. I think if you're S-on you so in fact need to use ruu mode. And I went back and looked at the error you ran in ruu mode and that's a normal message and you just needed to rerun the flash command.
htc_fastboot oem rebootRUU
htc_fastboot flash zip 0PJAIMG.ZIP
(If you get error 90, repeat the last command)
I think last time you repeated the flash command before the device was back in ruu mode.
Edit: but this would be so easy if you just get sunshine and S-off
Click to expand...
Click to collapse
Just tried it again using oem rebootRUU, and as usual failed again. Here is the log:
C:\adb>adb reboot bootloader
C:\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 14(ms)
C:\adb>htc_fastboot flash zip 0PJAIMG.ZIP
< waiting for device >
sending 'zip'... (93262 KB) FAILED (status read failed (Invalid argument))
Execution time is 8(s)
then I type last command again
C:\adb>htc_fastboot flash zip 0PJAIMG.ZIP
sending 'zip'... (93262 KB) FAILED (data size is too large(93262 KB) for device
to download ZIP file '0PJAIMG.ZIP'
)
Execution time is 4(ms)
C:\adb>
However in my htc's screen it seems to work it just that half bar is full and stuck in half

kamocheng said:
Just tried it again using oem rebootRUU, and as usual failed again. Here is the log:
C:\adb>adb reboot bootloader
C:\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 14(ms)
C:\adb>htc_fastboot flash zip 0PJAIMG.ZIP
< waiting for device >
sending 'zip'... (93262 KB) FAILED (status read failed (Invalid argument))
Execution time is 8(s)
then I type last command again
C:\adb>htc_fastboot flash zip 0PJAIMG.ZIP
sending 'zip'... (93262 KB) FAILED (data size is too large(93262 KB) for device
to download ZIP file '0PJAIMG.ZIP'
)
Execution time is 4(ms)
C:\adb>
However in my htc's screen it seems to work it just that half bar is full and stuck in half
Click to expand...
Click to collapse
I'm out of ideas. I think your best bet is to run the ruu exe found here: http://www.htc.com/us/support/htc-one-m9/news/

jollywhitefoot said:
I'm out of ideas. I think your best bet is to run the ruu exe found here: http://www.htc.com/us/support/htc-one-m9/news/
Click to expand...
Click to collapse
Thanks for bearing with me man

Related

[Q] stuck on htc quietly brilliant screen

Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.
You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium
Thanks sir, I'll try.
sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.
See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command
sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA
Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!
Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.
Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!
I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?
All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?
When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
Nobody can help me?!! ((

JB OTA for HTC_044 not working // manual firmware also not working (SOLVED)

I've been trying to update my HOX to JB since yesterday but to no avail:
Im on everything stock (ROM, Recovery etc) and phone is un-rooted. I relocked the bootloader too. but when the update downloads and the phone restarts after a few while, a red triangle with exclamation marks appear and phone restarts.
I've tried to do this 3 times now with no avail.
alternately i've been trying to follow this and when i reach the flashing firmware part, it fails after 2 tries and after the 3rd it just stucks:
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
OKAY [ 1.683s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.886s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
after 3rd attempt it just stays in sending 'zip' state
anyone got a clue how i can solve either problem?! :/
note my camera app is a modified version. rest all ROM is stock. could this be the issue?! if so, then any way to resolve this other than RUU method?
The last method you tried will not work if the bootloader is still locked !
The red triangle is normally an indication that you do not have the stock recovery. Try to reflash recovery and then fastboot erase cache before trying again, You would need to unlock bootloader in order to fastboot flash recovery. As pointed out in my other reply to you, you would probably need to revert to the stock camera app as well.
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Ah like that ! Thanks clyde :thumbup:
I did not read carefully... was kinda busy with my mac & cheese !!!
MarcelHofs said:
Ah like that ! Thanks clyde :thumbup:
I did not read carefully... was kinda busy with my mac & cheese !!!
Click to expand...
Click to collapse
ClydeB1 said:
Click to expand...
Click to collapse
LOL !
ClydeB1 said:
The red triangle is normally an indication that you do not have the stock recovery. Try to reflash recovery and then fastboot erase cache before trying again, You would need to unlock bootloader in order to fastboot flash recovery. As pointed out in my other reply to you, you would probably need to revert to the stock camera app as well.
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Click to expand...
Click to collapse
thanks, will try the OTA method 1st by installing the RUU. if that works then brilliant! otherwise try the 2nd
ClydeB1 said:
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Click to expand...
Click to collapse
worked like a charm, thnx mate! :good:
Didnt work for me
Asad_612 said:
worked like a charm, thnx mate! :good:
Click to expand...
Click to collapse
I get to the rebootRUU step and that works, but when I try to flash the firmware.zip it always comes up with "error: cannot load "fastboot.zip" : Unknown error" do you know what the problem might be?
mewazhere said:
I get to the rebootRUU step and that works, but when I try to flash the firmware.zip it always comes up with "error: cannot load "fastboot.zip" : Unknown error" do you know what the problem might be?
Click to expand...
Click to collapse
Fastboot.zip ..... Yeah that's wrong
Fastboot flash zip firmware.zip
And the firmware file need to be named firmware.zip !

[Q] HBoot Relocked, S-ON, Root, trying to upload stock ROM

Hello,
Im having reallly big problem with my Desire HD device and unfortunately,I realize this is only my fault and inadvertence. Im hoping that someone will help me with my problem...
First of all, I've had stock 2.3.5 on my device and every possible blockade. I've used Downgrade_v2 files (with adb and Gingerbreak and 1.32 stock android) but it wasn't working as it supossed to do. I've found nice tool to unblock DHD, called EasyAceRootTool. Everything went OK, new H-Boot was uploaded, unblock process went smoothly, Revovery Touch was uploaded to DHD as well, Superuser was installed too.
And at this level I've hurried too much, because I've installed by recovery new rom on Android 4.0.4 , this one : http://forum.xda-developers.com/showthread.php?t=1839004
And of course... I know now iVe forgot to make S-OFF, android doesn't start, nothing happens at all....
My Hboot now says :
Hboot :
***Relocked***
ACE PVT SHIP S-ON RL
HBOOT-2.0020029
RADIO -26.14.04.28_M
Ive tried a lot of soutions
1)Install PD98IMG.zip on sdcard (2 different stock roms) but when Bootlader is checking image, it says, that newer android is already on device
2)Install RUU, It says that there is a problem with Hboot and i need to wait for upgrade
3)Install PD98IMG.zip (pulled out from stock RUU) by recovery, it says that this image is "bad"
4)Restore backed up adnroid from this thread http://forum.xda-developers.com/showthread.php?t=920876&highlight=hboot, from section "Install stock Vodafone ROM", but it didn't helped as well, it says MD5 checksum failed...
5) When im trying to unlock Hboot in EasyAceRootTool, it communicating with device, but then it says : "Your device is not recognized"
Please guys... what else should I do ??
ps. I know there's a lot of grammatic mistakes, sorry for that. I was trying to check what I was writing
You've relocked your bootloader. You need to re-unlock it. Also, each time after you flash a ROM, you need to extract the boot.img from the ROM zip and
Code:
fastboot flash boot boot.img
bananagranola said:
You've relocked your bootloader. You need to re-unlock it. Also, each time after you flash a ROM, you need to extract the boot.img from the ROM zip and
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
tried to do that in bootloader is fastboot mode, and it says :
C:\win>fastboot flash boot boot.img
sending 'boot' (2932 KB)... OKAY [ 0.496s]
writing 'boot'... INFOsignature checking..
FAILED (remote: signature verify fail)
finished. total time: 0.973s
peanek said:
tried to do that in bootloader is fastboot mode, and it says :
C:\win>fastboot flash boot boot.img
sending 'boot' (2932 KB)... OKAY [ 0.496s]
writing 'boot'... INFOsignature checking..
FAILED (remote: signature verify fail)
finished. total time: 0.973s
Click to expand...
Click to collapse
Like I said, you relocked your bootloader. First you need to re-unlock your bootloader.
bananagranola said:
Like I said, you relocked your bootloader. First you need to re-unlock your bootloader.
Click to expand...
Click to collapse
Sorry, I haven't read properly
C:\win>fastboot flash unlocktocken Unlock_code.bin
sending 'unlocktocken' (0 KB)... OKAY [ 0.014s]
writing 'unlocktocken'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.019s
It's an unlock coode made in HTCDev.com, with a signature of my handset...
Is your phone in fastboot mode?
bananagranola said:
Is your phone in fastboot mode?
Click to expand...
Click to collapse
OK, there was a trivial bug, I've wrote unlocktocken instead of unlocktoken it is working now !!
Thanks man, I was fighting with this device for more than whole week, thanks for your help
peanek said:
OK, there was a trivial bug, I've wrote unlocktocken instead of unlocktoken it is working now !!
Thanks man, I was fighting with this device for more than whole week, thanks for your help
Click to expand...
Click to collapse
Ok, Im having other problem, tried to use fastboot flash boot boot.img, everything went OK, file was sended, but nothing happens, Hboot is still 2.00.0029, tried to use RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed, but after reboot, when i see HTC on black screen, when RUU should send new update, error is occured.
PD98IMG.zip on sdcard can't install too.
peanek said:
Ok, Im having other problem, tried to use fastboot flash boot boot.img, everything went OK, file was sended, but nothing happens, Hboot is still 2.00.0029, tried to use RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed, but after reboot, when i see HTC on black screen, when RUU should send new update, error is occured.
PD98IMG.zip on sdcard can't install too.
Click to expand...
Click to collapse
The boot.img isn't the bootloader. You need to flash the ROM (not RUU), then fastboot flash the boot.img.
bananagranola said:
The boot.img isn't the bootloader. You need to flash the ROM (not RUU), then fastboot flash the boot.img.
Click to expand...
Click to collapse
C:\win>fastboot flash zip UPDATE.zip
sending 'zip' (336097 KB)... OKAY [ 57.277s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 62.750s
or 2 others zip with ROM I've downloaded. Hboot is unblocked for 100%
Wait, no. Flash the ROM from recovery. You can't flash zips like that in fastboot. You can flash ROM images, but it makes more sense for you to get a recovery and flash zips instead.
If you don't have a recovery, first you need to install one. If you have a rooted ROM, you can install a recovery from apps: ROM Manager for ClockworkMod, 4ext Updater apk (from 4ext's website) for 4ext, and GooManager for TWRP. If you don't, download a recovery.img and flash it from fastboot:
Code:
fastboot flash recovery recovery.img
.
If you do, just go straight to flashing the zip from recovery. Then,
Code:
fastboot flash boot boot.img
.
bananagranola said:
Wait, no. Flash the ROM from recovery. You can't flash zips like that in fastboot. You can flash ROM images, but it makes more sense for you to get a recovery and flash zips instead.
If you don't have a recovery, first you need to install one. If you have a rooted ROM, you can install a recovery from apps: ROM Manager for ClockworkMod, 4ext Updater apk (from 4ext's website) for 4ext, and GooManager for TWRP. If you don't, download a recovery.img and flash it from fastboot:
Code:
fastboot flash recovery recovery.img
.
If you do, just go straight to flashing the zip from recovery. Then,
Code:
fastboot flash boot boot.img
.
Click to expand...
Click to collapse
OK, first of all, I'm having recovery, 5.8.7.2 Touch version that was installed with EasyAceRootTool.
I can't install any .apk, because I have now installed 4.0.4 rom, and because of S-ON, it will not start. I was trying to install few roms from recovery of course (Stock versions downloaded from xda, 1.32 versions and 2.3.5.), but every time I am doing this, revovery give me a error "installation aborted (bad)" it's from a PD98IMG zip downloaded from xda and rom.zip pulled out from "RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed"
When I am trying to do in fastboot mode :
Code:
fastboot flash system system.img
(system.img from stock roms, they are uploading, says OK for writing, but when I reboot phone, I see green HTC on white screen, then black screen, and then everytime phone reboots in recovery.
Few minutes a go i tried :
Code:
fastboot eease cache
fastboot oem rebootRUU
fastboot flash zip PD98IMG.zip
but every time it says :
Code:
C:\win>fastboot flash zip UPDATE.zip
sending 'zip' (336097 KB)... OKAY [ 57.215s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 62.713s
peanek said:
OK, first of all, I'm having recovery, 5.8.7.2 Touch version that was installed with EasyAceRootTool.
I can't install any .apk, because I have now installed 4.0.4 rom, and because of S-ON, it will not start. I was trying to install few roms from recovery of course (Stock versions downloaded from xda, 1.32 versions and 2.3.5.), but every time I am doing this, revovery give me a error "installation aborted (bad)" it's from a PD98IMG zip downloaded from xda and rom.zip pulled out from "RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed"
When I am trying to do in fastboot mode :
Code:
fastboot flash system system.img
(system.img from stock roms, they are uploading, says OK for writing, but when I reboot phone, I see green HTC on white screen, then black screen, and then everytime phone reboots in recovery.
Few minutes a go i tried :
Code:
fastboot eease cache
fastboot oem rebootRUU
fastboot flash zip PD98IMG.zip
but every time it says :
Code:
C:\win>fastboot flash zip UPDATE.zip
sending 'zip' (336097 KB)... OKAY [ 57.215s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 62.713s
Click to expand...
Click to collapse
What are you trying to do?? If you have an unlocked bootloader a RUU will never flash. Besides, being S-ON requires the specific RUU for your device.
If you have CWM and an unlocked bootloader, you can flash any custom rom in recovery but need to flash boot.img after flashing the rom.
You can't flash apks in recovery, only zips. Then fastboot flash the boot.img.
bananagranola said:
You can't flash apks in recovery, only zips. Then fastboot flash the boot.img.
Click to expand...
Click to collapse
glevitan said:
What are you trying to do?? If you have an unlocked bootloader a RUU will never flash. Besides, being S-ON requires the specific RUU for your device.
If you have CWM and an unlocked bootloader, you can flash any custom rom in recovery but need to flash boot.img after flashing the rom.
Click to expand...
Click to collapse
Ok, I was trying to put this device on feet, because it wasn't load any ROM I was flashing. There's a lot of tools and tutorials that I was reading before flashing DHD on xda and other forums. I was convinced, that I need S-OFF to use custom ROM. Few minutes a go I flashed Sabsa-Prime ROM by Recovery, then i searched for boot.img in Sabsa_Prime_v16.0_By_AlirezaB.zip, flashed it in fastboot, anddddd tadaaam...Everythings working perfectly
Thank You gyus, I really appreciate your help !! I was really stuck on this device...
Best Regards !
I need help...NOOB!!!
Hi there i need help.. my phone is stuck on a relocked screen and i cant get it tp power up... i will post a pic so maybe someone can help me out asap...
good
hiii please help mee!!
peanek said:
Hello,
Im having reallly big problem with my Desire HD device and unfortunately,I realize this is only my fault and inadvertence. Im hoping that someone will help me with my problem...
First of all, I've had stock 2.3.5 on my device and every possible blockade. I've used Downgrade_v2 files (with adb and Gingerbreak and 1.32 stock android) but it wasn't working as it supossed to do. I've found nice tool to unblock DHD, called EasyAceRootTool. Everything went OK, new H-Boot was uploaded, unblock process went smoothly, Revovery Touch was uploaded to DHD as well, Superuser was installed too.
And at this level I've hurried too much, because I've installed by recovery new rom on Android 4.0.4 , this one : http://forum.xda-developers.com/showthread.php?t=1839004
And of course... I know now iVe forgot to make S-OFF, android doesn't start, nothing happens at all....
My Hboot now says :
Hboot :
***Relocked***
ACE PVT SHIP S-ON RL
HBOOT-2.0020029
RADIO -26.14.04.28_M
Ive tried a lot of soutions
1)Install PD98IMG.zip on sdcard (2 different stock roms) but when Bootlader is checking image, it says, that newer android is already on device
2)Install RUU, It says that there is a problem with Hboot and i need to wait for upgrade
3)Install PD98IMG.zip (pulled out from stock RUU) by recovery, it says that this image is "bad"
4)Restore backed up adnroid from this thread http://forum.xda-developers.com/showthread.php?t=920876&highlight=hboot, from section "Install stock Vodafone ROM", but it didn't helped as well, it says MD5 checksum failed...
5) When im trying to unlock Hboot in EasyAceRootTool, it communicating with device, but then it says : "Your device is not recognized"
Please guys... what else should I do ??
ps. I know there's a lot of grammatic mistakes, sorry for that. I was trying to check what I was writing
Click to expand...
Click to collapse

Help: Bricked Htc one M8 GPe

Hello everyone, I started to play around with all the diff things you can do with a rooted phone had plans for getting a custom ROM for my phone. Let me stat by saying that I am very new to all this.
I day ago i was getting ready to install the custom ROM for viper (ViperOneM8_1.7.1) reason being is coming from a htc one m7 with sense i wanted to get back to sense from my stock GPe m8.
I was able to unlock my bootloader and get my phone rooted I fallowed this video (How to Root your HTC One M8 - Full Guide) From Sakitech... or least I think im rooted still... I'll come back to you as to why I say "I think I'm rooted".
I thought it would be very simple just fire up the custom recovery and flash the ROM and sit back while it flashed, well everything went down hill from this point. Let me tell you what i did.
First i got to the custom recovery and I did a wipe I did advanced wipe and checked the boxes this is where I think I deleted the OS(after this I could not get back on the phone to do anything only will boot to recovery and it say no OS installed then asks if I want to get SuperSU installed this is where I already thought I was rooted but maybe on not??? I'm very confused about that
Then I used the sideload method to push the rom zip and try to flash the rom at this point I cant get it to flash. First I was getting the MD5 error I checked that off now it will just fail either saying error executing the binary from the zip or that zip is corrupted. (I tried re-downloading the ROM even from mirror link)
At this point I am very frustrated and feel helpless. I tried my best to keep from posting this and try to research to see if i can find the solution myself but I'm having no luck I have my days off from work to get my phone up and running or ill just have to go but another phone. At this point I really need some help. All I want is a working phone if i can get back to GPe stock that would be fine or make the ViperOne work.
Attempts to solve my problem: I tried flashing GPE4.4.3_m8.zip and other stock GPe ROMs nothing works
Thanks for reading and all your help I will sit nest to my comp and answer anything to try make everything as clear as possible. Thank you again
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Demonwarrior said:
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Click to expand...
Click to collapse
no offense, buy you need to read before you continue anything else.
rbouza1 said:
no offense, buy you need to read before you continue anything else.
Click to expand...
Click to collapse
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Demonwarrior said:
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Click to expand...
Click to collapse
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Mr Hofs said:
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Click to expand...
Click to collapse
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
fastboot flash img boot.img
---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------
try that command, and what model did you have originally and did you convert to gpe or flash a gpe ROM.
gave me an error
Code:
FAILED (remote: signature verify fail)
Its a stock Google play edition I bought from the Google paly store, I didnt flash any other rom the ViperOne rom was going to be the first flash on the phone
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
iHagbani said:
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
Click to expand...
Click to collapse
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
ckpv5 said:
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Demonwarrior said:
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Click to expand...
Click to collapse
I know, but I told you this way in case that the adb didn't flash the whole zip file!
Demonwarrior said:
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Click to expand...
Click to collapse
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
j to the 4n said:
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
Click to expand...
Click to collapse
I tried the instruction on the thread it didnt work... I think its because i have s-on
Code:
C:\Users\owner\Desktop\htc one\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.058s]
finished. total time: 0.061s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.483s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.846s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.484s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.665s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.479s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.662s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.478s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.661s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.458s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.641s
C:\Users\owner\Desktop\htc one\platform-tools>
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.470s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.650s
C:\Users\owner\Desktop\htc one\platform-tools>
The post says to try it a few times but still giving me the say error

[GUIDE][FIX]Cant unlock bootloader? Read here for a Fix

Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
I'm on 2.18 and rooted. Problem is, I uninstalled or disabled a bunch of ASUS apps, will I have an issue if I use SuperSU to unroot and try to restore or upgrade my phone to 2.19?
Also, I have model number ASUS_Z00AD. Is this firmware OK to install on my phone?
cmendonc2 said:
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Fixed.
edit: nvm...
Both download links link to the same file. splashscreen.img
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
jpacleb85 said:
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
Click to expand...
Click to collapse
LOL... Gotta love the devs who tinker on here... Now we might actually get a recovery that will do nandroid backups in case of those "little" mistakes/problems that crop up from time to time...
MiCmAsTa said:
Both download links link to the same file. splashscreen.img
Click to expand...
Click to collapse
Fixed.
This is probably a silly question, but I have the ZE550ML and the latest update is 2.18, meaning that unlocking the bootloader it is still not possible can I install droidboot.img(fastboot img) from the 2.19 ZE551ML on my device? Or that will just hard brick my device?
Let me know your thoughts on this.
Continue the great work XDA crew =)
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
PsychoKilla666 said:
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
Click to expand...
Click to collapse
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
rafyvitto said:
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
Click to expand...
Click to collapse
Link please? and how to?
error
rafyvitto said:
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
Click to expand...
Click to collapse
I follow this method and received the following error on CMD
writing 'fastboot'....
FAILED (remote: falsh_cmds error!
Finished. total time: 0.830
im on 2.20 and it wont let me do anything.. i get the white boot screen instead of black but bootloader doesnt exist and it wont download twrp any suggestions?
Success
My phone's recovery stopped working, and the bootloader was locked, but I found this thread. I think I was able to get it working.
I extracted the droidboot.img from the file in the OP.
I copied the droidboot.img to my working directory, and tried to flash it.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.826s
Ok, I got the error. Maybe the "unlock" command will work.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.203s]
finished. total time: 0.204s
Same output as the last hundred times I tried to run it.
I rebooted the phone.
Code:
C:\myworkingdirectory>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
I put the phone into the bootloader mode. (For anyone reading, to get into the bootloader, turn the phone completely off. Hold the power button until it vibrates. Then hold the volume up key.)
I ran the unlock command twice.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.291s]
finished. total time: 0.326s
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.216s]
finished. total time: 0.216s
Then I tried to flash the image again.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.690s]
writing 'fastboot'...
OKAY [ 0.692s]
finished. total time: 1.384s
No error?! I have progress!
------
I believe my bootloader is unlocked. Let me try to flash the recovery. (My recovery was corrupted longggg before doing this.)
Code:
C:\myworkingdirectory>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11676 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.571s]
finished. total time: 1.153s
No permission error! (Before this, I would usually have gotten an error that says "FAILED (remote: Permission denied".)
---- Important Notes ----
NO WHITE BACKGROUND IN BOOTLOADER.
Many people have reported seeing an inverted background in the bootloader. I don't have that.
TRIPLE DOTS IN COMMAND PROMPT
The triple dots you see when I run the unlock command are actually there. They are not placeholders.
------------
Right now I'm booting into recovery mode to flash a ROM to the phone. I'll update if I get the phone working.

Categories

Resources