Trying to return my one back to stock (unlocked, s-off) to send in for purple tint repair.
I tried a few different methods involving the RUUs but never had any luck:
1. The RUU.exe for my specific phone (telus), always crashed when htc_fastboot.exe stopped responding.
2. Since there was no RUU.zip for the Telus version I extracted it out of the exe and tried flashing manually, but again fastboot stops responding.
3. Tried changing the CID to CWS__001 and using the matching RUU.exe, and while fastboot didn't crash it wasn't able to complete either (can't remember the exact error).
So I decided to use the Telus Guru Reset from htc1guru, which worked fine.
Now I need to get rid of the tampered flag and lock bootloader/s-on, but I can't boot a custom recovery with fastboot boot recovery.img.
I need to boot into recovery to either use the guru bootloader reset tool or to temporarily install superuser, so that I can manually remove the tampered flag.
Tried the latest version of both TWRP and CWM Touch, and also tried fastboot erase cache before each.
Every time fastboot succesfully pushes the img to the phone and outputs booting..., OKAY, and finished, but the phone gets stuck at the bootloader and never actually boots to the recovery (have to force power off).
Any ideas/help would be greatly appreciated.
xerockz said:
Trying to return my one back to stock (unlocked, s-off) to send in for purple tint repair.
I tried a few different methods involving the RUUs but never had any luck:
1. The RUU.exe for my specific phone (telus), always crashed when htc_fastboot.exe stopped responding.
2. Since there was no RUU.zip for the Telus version I extracted it out of the exe and tried flashing manually, but again fastboot stops responding.
3. Tried changing the CID to CWS__001 and using the matching RUU.exe, and while fastboot didn't crash it wasn't able to complete either (can't remember the exact error).
So I decided to use the Telus Guru Reset from htc1guru, which worked fine.
Now I need to get rid of the tampered flag and lock bootloader/s-on, but I can't boot a custom recovery with fastboot boot recovery.img.
I need to boot into recovery to either use the guru bootloader reset tool or to temporarily install superuser, so that I can manually remove the tampered flag.
Tried the latest version of both TWRP and CWM Touch, and also tried fastboot erase cache before each.
Every time fastboot succesfully pushes the img to the phone and outputs booting..., OKAY, and finished, but the phone gets stuck at the bootloader and never actually boots to the recovery (have to force power off).
Any ideas/help would be greatly appreciated.
Click to expand...
Click to collapse
boot recover has not worked sense hboot 1.44
clsA said:
boot recover has not worked sense hboot 1.44
Click to expand...
Click to collapse
I guess that explains the problem as I am on 1.57. Just re-flashed that guru reset, and checked the option to install superuser and busybox this time so now I should be able to fix the tampered flag and lock, without having to worry about booting to a custom recovery.
Okay so I got it locked and tampered removed, however I cannot remove Superuser.apk, the su binary, or busybox now that my bootloader is locked (using adb shell, su, rm -r /system/app/Superuser.apk). Tried factory reseting and the files are still there, not sure how I can get rid of them!
edit: I've found this old post, not sure if it's still relevant, or exactly what it's doing.
xerockz said:
Okay so I got it locked and tampered removed, however I cannot remove Superuser.apk, the su binary, or busybox now that my bootloader is locked (using adb shell, su, rm -r /system/app/Superuser.apk). Tried factory reseting and the files are still there, not sure how I can get rid of them!
edit: I've found this old post, not sure if it's still relevant, or exactly what it's doing.
Click to expand...
Click to collapse
Why not just run the Guru Reset again and select stock recovery and no root.
@xerockz try to install SuperSU app from Play Store. Open it and let update the binaries (normal!) and if successfull, you will after reboot get able to unroot for good in the app.
tetakpatalked from N7100
Hey guys, thanks for the suggestions. I ended up getting it all back to stock.
I believe the reason the RUUs weren't working was because I was on hboot 1.57.
I flashed 1.44 and then was unable to get fastboot to recognize the device under windows 8.1 (common driver issue apparently). I couldn't be bothered to try to fix the driver issue so I booted into a live Fedora usb which then let me use fastboot and flash the appropriate ruu.zip.
Now the ruu had hboot 1.55 so I was once again unable to fastboot boot recovery.img.
I ended up flashing TWRP again, trying the guru bootloader reset over and over, (for tampered and lock) wiped cache/dalvik, still wouldn't work.
Finally got it to work after fastboot format cache.
Now I was locked and no tampered flag, but still had TWRP flashed.
Tried pulling the signed_recovery.img out of the RUU zip and flashing it but obviously that doesn't work since I was locked at this point.
So I just flashed the entire RUU again, which fortunately worked even though I was locked.
Now I just had to S-ON, update OTA, and factory reset (through sense settings) and I'm completely back to stock.
14 hours of headache later and I finally got this thing reset.
It's unfortunate the return to stock guides fail to mention the RUUs don't work if you are on a newer hboot, and also that you need/can flash the RUU AFTER fixing tampered/locking.
xerockz said:
It's unfortunate the return to stock guides fail to mention the RUUs don't work if you are on a newer hboot, and also that you need/can flash the RUU AFTER fixing tampered/locking.
Click to expand...
Click to collapse
beg to differ [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
but glad you got everything sorted out :good: :good:
Related
Hi
I went to update my firmware earlier so went to update the firmware, but first had to relock the bootloader.
I typed fastboot oem lock and got ... underneath it and it stuck there for hours. The screen on the phone had frozen too.
In the end I pulled the cable to go back into bootloader. The CMD prompt then said it had relocked it and then some read error.
I think the system is now wiped as all it does is boot into bootloader or fastboot. I tried to send the stock recovery img from ARHD site but get a signature error.
What should I do?
I have tampered and relocked at the top of the bootloader screens and fastbootoem lock does confirm it is locked
Thanks!
I have done the exact same thing! I am kinda freaking out.
TheMathMan said:
Hi
I went to update my firmware earlier so went to update the firmware, but first had to relock the bootloader.
I typed fastboot oem lock and got ... underneath it and it stuck there for hours. The screen on the phone had frozen too.
In the end I pulled the cable to go back into bootloader. The CMD prompt then said it had relocked it and then some read error.
I think the system is now wiped as all it does is boot into bootloader or fastboot. I tried to send the stock recovery img from ARHD site but get a signature error.
What should I do?
I have tampered and relocked at the top of the bootloader screens and fastbootoem lock does confirm it is locked
Thanks!
Click to expand...
Click to collapse
1. try and unlock the bootloader again
2. flash custom recovery twrp or cwm
3. adb sideload rom.zip within custom recovery.
hopefully that will get you up and running again.
i had a similar problem where system got completely wiped, i couldnt adb sideload though. just couldn't get it to work. luckily i have an otg cable, so i mounted a flash stick in twrp and flashed custom rom via otg and everything fine again.
hope this helps
dazbutler1 said:
1. try and unlock the bootloader again
2. flash custom recovery twrp or cwm
3. adb sideload rom.zip within custom recovery.
hopefully that will get you up and running again.
i had a similar problem where system got completely wiped, i couldnt adb sideload though. just couldn't get it to work. luckily i have an otg cable, so i mounted a flash stick in twrp and flashed custom rom via otg and everything fine again.
hope this helps
Click to expand...
Click to collapse
OK. Phew!!!
Unlocked bootloader again with the unlock token. Then it rebooted straight into ARHD 4.6 that was on there, so it obviously hadn't been wiped but some sort of odd issue.
Now a bit concerned about trying to update firmware again, as when it had "security warning" fastboot oem rebootRUU didn't work at all.
Would love some more info about this and how to do it better next time!
TheMathMan said:
OK. Phew!!!
Unlocked bootloader again with the unlock token. Then it rebooted straight into ARHD 4.6 that was on there, so it obviously hadn't been wiped but some sort of odd issue.
Now a bit concerned about trying to update firmware again, as when it had "security warning" fastboot oem rebootRUU didn't work at all.
Would love some more info about this and how to do it better next time!
Click to expand...
Click to collapse
Glad you got it running again. are you talking about flashing the new firmware.zip ota file that contains new radio. If so i can't really shed any light on this for you as my cid is h3g_001 so currently i can't update my firmware
dazbutler1 said:
Glad you got it running again. are you talking about flashing the new firmware.zip ota file that contains new radio. If so i can't really shed any light on this for you as my cid is h3g_001 so currently i can't update my firmware
Click to expand...
Click to collapse
Yep thats right, the firmware.zip. CID is HTC__001 on mine. Assume that it is anyway, and that reading it from within ARHD doesn't show it differently? Never looked before flashing the custom rom.
TheMathMan said:
Yep thats right, the firmware.zip. CID is HTC__001 on mine. Assume that it is anyway, and that reading it from within ARHD doesn't show it differently? Never looked before flashing the custom rom.
Click to expand...
Click to collapse
easiest way to confirm cid is download cid getter from play store. if its HTC_001 you should be fine.
Yep, done that and confirmed with getvar all so should be fine. Now I just need to relock the bootloader so it lets me rebootRUU. Last time it refused and froze.
TheMathMan said:
Yep, done that and confirmed with getvar all so should be fine. Now I just need to relock the bootloader so it lets me rebootRUU. Last time it refused and froze.
Click to expand...
Click to collapse
hope you have more luck this time then.
Odd. Worked perfectly second time around. Done and dusted within minutes. No idea what went wrong!?!?
I am trying to return my HTC One to stock (practice run just in case). I have an all stock rom and recovery. I try booting into CWM temporarily with
Code:
fastboot boot recovery.img
where recovery.img is the CWM recovery partition image. This should allow me to flash a root zip for temp root.
It indicates that flashing was successful and that the device will reboot. It doesn't reboot however and also no longer responds to the physical buttons (volume up/down and power). I can reset the device and it then goes on as if nothing happened.
I have HBOOT 1.54 and OS 2.24.401.3. I suspect it has something to do with the HBOOT version. This would also explain the segfaults with revone I'm getting.
Can I downgrade my bootloader to a lower version so it becomes vulnerable for revone?
bloodsplatter said:
I am trying to return my HTC One to stock (practice run just in case). I have an all stock rom and recovery. I try booting into CWM temporarily with
Code:
fastboot boot recovery.img
where recovery.img is the CWM recovery partition image. This should allow me to flash a root zip for temp root.
It indicates that flashing was successful and that the device will reboot. It doesn't reboot however and also no longer responds to the physical buttons (volume up/down and power). I can reset the device and it then goes on as if nothing happened.
I have HBOOT 1.54 and OS 2.24.401.3. I suspect it has something to do with the HBOOT version. This would also explain the segfaults with revone I'm getting.
Can I downgrade my bootloader to a lower version so it becomes vulnerable for revone?
Click to expand...
Click to collapse
1- "fastboot boot recovery.img" no longer works in hboot 1.54, HTC remove that
2- when it hangs, to "unhang" it, just unplug the USB cable and bootloader should return to normal (did for me)
3- downgrading is only possible if you're S-Off
nkk71 said:
1- "fastboot boot recovery.img" no longer works in hboot 1.54, HTC remove that
2- when it hangs, to "unhang" it, just unplug the USB cable and bootloader should return to normal (did for me)
3- downgrading is only possible if you're S-Off
Click to expand...
Click to collapse
****e
I tried a hard reset, will try that as well
Can I get S-Off? Moonshine didn't work because it couldn't reboot from fastboot
bloodsplatter said:
****e
I tried a hard reset, will try that as well
Can I get S-Off? Moonshine didn't work because it couldn't reboot from fastboot
Click to expand...
Click to collapse
Unfortunately, for 1.54 there is no s-off atm, hopefully in the future, but nobody knows.
So I'm stuck at the moment? Crud
bloodsplatter said:
So I'm stuck at the moment? Crud
Click to expand...
Click to collapse
For S-Off, yes.
But you can still flash stock rom (since you have a nandroid), and then flash the corresponding stock recovery, and finally relock bootloader.
Though be careful with the stock rom, if it's 1.xx and your firmware is already on 2.x that render your touchscreen unresponsive and you'll have to use an OTG cable + mouse to get the OTAs to 2.x
nkk71 said:
For S-Off, yes.
But you can still flash stock rom (since you have a nandroid), and then flash the corresponding stock recovery, and finally relock bootloader.
Though be careful with the stock rom, if it's 1.xx and your firmware is already on 2.x that render your touchscreen unresponsive and you'll have to use an OTG cable + mouse to get the OTAs to 2.x
Click to expand...
Click to collapse
I already flashed stock rom through nandroid, one with all the OTA's in it, but I can't remove the tampered mark in the bootloader? Or am I still getting it because I'm using the wrong RUU? My CID is HTC_E11, I always picked one of the RUU's that goes for WWE, but recently S-On is preventing me from flashing them since all of them are older than the software version of the phone.
To remove the Tampered warning you need to install stock recovery.
Sent from my HTC One using XDA Premium 4 mobile app
I was following Vomer's guide on my One, which has been working great. I had HBOOT 1.54, S-Off, SuperCID, and pushed the firmware twice, got the success message, and waited and when it says finished used adb to tell it to reboot. Now I get the splash, with the lock gone, as expected, and then the screen goes black. If I hold power, or power and down, the hardware keys start blinking and then nothing. A few seconds later I get the splash again, then blank again.
It appears to be communicating briefly over USB because my laptop starts trying to install a HTC MTP device (drive is already on the PC and has been fine) before it looses comms and drops out. I can't seem to get adb device to recognize it....
PLEASE tell me someone can help me recover my phone!!! I will be immensely grateful.
And what the HBOOT version you wanted to downgrade to?
Ivanovic said:
And what the HBOOT version you wanted to downgrade to?
Click to expand...
Click to collapse
I wasn't trying to downgrade HBOOT, just rather ensure my firmware was up to date. I'd had mine set up as a GPE and was flashing the DE (after supercid).
By way of an update, I've been able to get into bootloader and I'm a bit scared on what to do next so I dont screw this up. I notice that I still have S-OFF, but HBOOT is now showing 1.56 and it says RELOCKED at the top. My plan was to use rumrunner (just because of the HBOOT, but it is erroring anyway) to unlock bootloader, and then to look up the fastboot commands to push a ROM and recovery. Any advice?
Downgrade to 1.44 and change cid according to the Rom you want. Then unlock or set your bootloader to LOCKED
Here is the file for 1.44 http://www69.zippyshare.com/v/95229262/file.html
Sent from my HTC One using Tapatalk
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
vettejock99 said:
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
Click to expand...
Click to collapse
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Ivanovic said:
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Click to expand...
Click to collapse
Awesome. So I've got HBOOT 1.44, S-OFF, bootloader unlocked, supercid, and TWRP 2.6.3.3 flashed again, and I tried sideloading ARHD rom. It all looked good but same thing for the moment, I get the splash and then black......I can't figure out why I can't boot into a rom right now. About to try flashing ROM again.
Okay, so didnt' work. After sideload flashing gets to 100% it just does nothing. Manually rebooting gets me back into the splash then blackness bootloop......
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
The former didn't get me anywhere, but I did follow your thinking and decided to use the RUU and start over. I'm happy to report that got me going, and then I was able to get AR HD on. I probably had to do that all along once I wiped the ROM and recovery, as sideloading clearly wasn't going to work (in retrospect) as it has an AROMA installer.
Thanks so much everyone!!
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
Nice that everything is solved now.
Verstuurd van mijn HTC One
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
KoalaSuccess said:
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
Click to expand...
Click to collapse
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
7ftnick said:
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
Click to expand...
Click to collapse
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
KoalaSuccess said:
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
Click to expand...
Click to collapse
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
I took a look and I'll try it! Do you know if my device is Bell? I'm not sure how to tell.
SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
KoalaSuccess said:
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
Click to expand...
Click to collapse
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
alray said:
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
Click to expand...
Click to collapse
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
KoalaSuccess said:
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
Click to expand...
Click to collapse
well that is strange, you should have kept s-off and try other things first but well, its to late. At least your phone is working now
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
OfficialLocdoGg said:
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
Click to expand...
Click to collapse
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
alray said:
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse
OfficialLocdoGg said:
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
Click to expand...
Click to collapse
its fine to flash a ruu with phone booted in bootloader btw.
alray said:
its fine to flash a ruu with phone booted in bootloader btw.
Click to expand...
Click to collapse
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
OfficialLocdoGg said:
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
Click to expand...
Click to collapse
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Boot into bootloader/FASTBOOT USB
Type:
Code:
[B][I]fastboot oem lock[/I][/B]
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
majmoz said:
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
Click to expand...
Click to collapse
Thanks. This restored the phone to a usable state. I'm going to try firewater now.