So I guess I just don't know what I'm doing anymore, and I need some help getting S-OFF on my One. I installed a 4.3 ROM and wanted to upgrade my firmware to 3.06.1700.10. To do this though, I saw I needed to have S-OFF.
I attempted S-OFF with both methods posted in the sticky. The revone method gave me "error code = 1", and the moonshine method fails to connect to ADB.
So I figured maybe I needed to revert to a compatible ROM to be able to get S-OFF. So I tried running the appropriate AT&T RUU utility, and it tells me the update failed and freezes on the HTC logo.
So both S-OFF methods failed, and the RUU failed. What do I need to do in order to get S-OFF so I can upgrade my firmware?
Forget it.
Mike
Hi at all,
I am writing here to ask for help, I've latest version of Android Revolution HD on my Unlocked UK HTC One with CID 001, and i need to go back to stock for warranty, Amazon waiting my device for fully refound me, so I want go back to stock and re-lock my HTC One.
I read a tons of thread around here regarding how to revert stock on HTC One, and download a lot of RUU, Nandroid and other stuff, but nothing works!
I have some errors when try to flash a RUU, like "signature verify fail", or :
. ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Click to expand...
Click to collapse
I get right RUU version, if I send ./fastboot getvar version-main the result is: version-main: 2.24.401.8
so I'm sure I downloaded the correct version of RUU, I try also to re-download but same error...
I'm sure that I've re-locked my bootloader...
I'm sure that I'm using right drivers,
I'm sure that I'm using right command and target file to flash...
so where is the problem ?
anyone can help me?
Thanks a lot!
Did you try Mike's guide?
http://forum.xda-developers.com/showthread.php?t=2265618
L0rdNels0n said:
Did you try Mike's guide?
http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
yes man
SOLVED flashing http://www.htc1guru.com/dld/guru_res...-24-401-8-zip/ from custom recovery solved partially my problem
now I have only to unroot my device manually and cross finger for warranty
I bought a used htc desire c declared as not working.
The smartphone will start in bootloader mode but it does not handle the factory reset and recovery, only fastboot and bootloader.
fastboot command works but does not allow to flash recovery, boot, etc. with 'image update error' message.
If I try to load a official RUU ROM, it detects the installed version, asks to update but then it stops when it has to reboot into bootloader
If I try:
fastboot flash recovery recovery.img
sending 'recovery' (8368 KB)... OKAY [ 2.310s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 2.404s
fastboot oem boot
... INFO[SD_HW_ERR] read data fail in CMD18
INFOCMD18: cmd failed
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(735): error 2
INFO[DISPLAY_ERR] read sp1 partition fail!!!
INFO[SD_HW_ERR] read data fail in CMD17
INFOCMD17: cmd failed
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(735): error 2
INFO[SD_HW_ERR] read data fail in CMD17
INFOCMD17: cmd failed
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(735): error 2
INFO[ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.413s]
finished. total time: 0.413s
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.28.0000
INFOversion-baseband: 1.06.98.13M2
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.45.401.4
INFOserialno: HT25XW517002
INFOimei: XXXXXXXXXXXXXX (omitted)
INFOproduct: golfu
INFOplatform: HBOOT-7225A
INFOmodelid: PL0110000
INFOcidnum: HTC__405
INFObattery-status: good
INFObattery-voltage: 4166mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
Is irrimediable brick? :crying:
Any suggestions?
Thanks
By how that reads and the fact it actually can pick up the installed version it gives one of two possibilitys...
1. SD or eMMC (same thing) has failed or corrupted, the fact it detects the installed system to me says possibly not all is lost.
2. If (I'm guessing it's been HTC unlocked bootloader) someone has written in the wrong thing to the SD/eMMC they could have wiped the partitions hence it still picks up your installed system.
I would have a search (as I'm not in the know) into what the errors surely mean, on that basis if it's recoverable or not
Bashing away at my HTC Desire C
Antagonist42 said:
By how that reads and the fact it actually can pick up the installed version it gives one of two possibilitys...
1. SD or eMMC (same thing) has failed or corrupted, the fact it detects the installed system to me says possibly not all is lost.
2. If (I'm guessing it's been HTC unlocked bootloader) someone has written in the wrong thing to the SD/eMMC they could have wiped the partitions hence it still picks up your installed system.
I would have a search (as I'm not in the know) into what the errors surely mean, on that basis if it's recoverable or not
Bashing away at my HTC Desire C
Click to expand...
Click to collapse
Yes, bootloader is unlocked and security flag is S-ON.
Any idea to restore original partition without riff box ?
Is there any command to try to reformat the partition with fastboot?
I've not got my pc up and running atm so I'm unable to check all I'd need to but I would have a search on forums for partition info and what you can, can't and should NOT do.
If as I'm guessing you've got HBOOT loading and screen output (?) then the primary partitions are still there so it may only be a case of getting spl1 / 2 (if they've altered these) rewritten and see what's needed after that if anything.
Sent from my HTC Desire C using xda app-developers app
One possibility is to try flashing PL01DIAG from SDCard, I had mine fail on booting and recovery but HBOOT wasn't affected, placed it in the .zip with Stock ROM Perfect for Recovery, placed on SDCard and turned it on and let it get on with it, took a while but recovered phone, this option may work
You have a valid PL01DIAG.NBH to try?
I'll drop it on a site and link it today, try it by all means.
As with any ROM/BOOT/RECOVERY anybody flashing the software, you do so at your own risk, I accept no responsibility for a failing device, unbootable unit, kids with sticky chocolate fingers and my luck for it working for me
If it works hit a Thanks button
Bashing away at my HTC Desire C
WARNING : THIS IS NOT FOR htc Desire C Cricket!!!!
As with any ROM/BOOT/RECOVERY anybody flashing the software, you do so at your own risk, I accept no responsibility for a failing device, unbootable unit, kids with sticky chocolate fingers and my luck for it working for me
Here is the DIAG ...and again!!if site works?!?! ... extract and make a new DIAG.zip (using same name) for updating with, to include Boot, Recovery, system folder and META-INF folders, a good stock ROM is This here {all contained in ROM apart from DIAG}
Hopefully this will work for more than just me
One thing I am not 100% sure on is the HBOOT version!!! I am currently on 1.31 and unsure if this is from htc Bootloader Unlocking/Orange update (doubtful)/or a much later production model and to date have not looked at reverting if possible to 1.28, needless to say, if a ROM or update uses 1.28 it may need 1.31 extracting from phone (there are 2 partitions HBOOT resides in and both are slightly different for what is being flashed by which part of phone) and the .img replacing the ROMS 1.28 version...
Moto for the day : If you can't fix it....make sure you dissect it before you kill it!
If you find that the same errors are still happening we'll see about possibly getting the required .img's and see if we can get them flashed and working
Sorry, but link for DIAG files is broken ...
In Italy anonfiles.com is banned !!
EDIT:
Ok now it's work with a little modify on DNS network card!!
Thanks for all.
Now try and send you a response.
Comodo browser won't download but Firefox does.
Similar problem with HTC DEV site as well
Procedure
I have done the following steps:
1) Create a PL01DIAG.ZIP with PL01DIAG.NBH inside and put it into SD card.
2) Create a PL01IMG.ZIP with stock ROM inside (ROM.ZIP extrated from RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed.exe and reanmed PL01IMG.ZIP) and put it into SD card.
3) Boot a device in bootloader mode.
See first image (step 1) and second image (step 2) for the result.
View attachment 2572476
View attachment 2572475
something wrong?
Thanks
Second Image: Bootloader - FAIL-PU
My guess is the partition info is corrupt if it can't or won't update it, this is something I'm not sure that can be Re-Written, especially as with this device being S-ON. This would leave all the partitions intact but the partition info maybe pointing to the wrong places making it unable to write a partition (as with the system - it is there but unable to alter it) and giving failures as the images are what it believes are too large, small etc. even if it reads the boot/recovery/system partition and images.
Also - ***RELOCKED***
Was it showing this previous to trying DIAG?
If so then I don't think you can flash the Boot/Recovery.images whilst it is Locked.
If it was stated as being Unlocked then it's been Relocked for definite (mine is still unlocked after using DIAG+.img's so I'm inclined not to think DIAG has relocked it as it requires a TOKEN ID from htc not included in DIAG), possibly making it (from public standpoint) unrecoverable without sending to htc or possibly using JTAG etc.
I would be inclined to contact htc and see how it stands on gaining Bootloader Unlocked in it's current state as you need the Unlock Token which I think you need the system up and running but they could hold the Token ID with Serial# IMEI etc when you request the Bootloader Unlock Token but I suspect they'll not want us knowing how
Antagonist42 said:
Second Image: Bootloader - FAIL-PU
My guess is the partition info is corrupt if it can't or won't update it, this is something I'm not sure that can be Re-Written, especially as with this device being S-ON. This would leave all the partitions intact but the partition info maybe pointing to the wrong places making it unable to write a partition (as with the system - it is there but unable to alter it) and giving failures as the images are what it believes are too large, small etc. even if it reads the boot/recovery/system partition and images.
Also - ***RELOCKED***
Was it showing this previous to trying DIAG?
If so then I don't think you can flash the Boot/Recovery.images whilst it is Locked.
If it was stated as being Unlocked then it's been Relocked for definite (mine is still unlocked after using DIAG+.img's so I'm inclined not to think DIAG has relocked it as it requires a TOKEN ID from htc not included in DIAG), possibly making it (from public standpoint) unrecoverable without sending to htc or possibly using JTAG etc.
I would be inclined to contact htc and see how it stands on gaining Bootloader Unlocked in it's current state as you need the Unlock Token which I think you need the system up and running but they could hold the Token ID with Serial# IMEI etc when you request the Bootloader Unlock Token but I suspect they'll not want us knowing how
Click to expand...
Click to collapse
I' have a unlocked token (unlock_code.bin) but i relocked the device because otherwise it does not accept stock rom from SD or RUU.
I need to try again unlocking the bootloader?
Thanks
EDIT:
Ok I've tried to unlock the bootloader but the result is the same.
It may be worth an email to htc to see if it can be unlocked in it's current state, you'll know for sure then and probably no alteration with flashing after you Relocked so would be in the same state as it was before.
Let us know either way as it's something worth knowing
Bashing away at my HTC Desire C
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
Hey guys, I've messed up my phone and I'm trying to RUU it back to stock. The problem is that it isn't working for me. I keep getting the error message "htc_fastboot.exe has stopped working" and it's driving me nuts. Im using the latest RUU and my firmware is up to date.
I relocked my bootloader even though Im S-OFF in a deperate attempt but nothing is working. THis isn't my first RUU and I don't know what Im doing wrong
EmSeeMAC said:
Hey guys, I've messed up my phone and I'm trying to RUU it back to stock. The problem is that it isn't working for me. I keep getting the error message "htc_fastboot.exe has stopped working" and it's driving me nuts. Im using the latest RUU and my firmware is up to date.
I relocked my bootloader even though Im S-OFF in a deperate attempt but nothing is working. THis isn't my first RUU and I don't know what Im doing wrong
Click to expand...
Click to collapse
Try using a computer that's running Windows 7.
Had same problem - how I fixed it.
I was having the exact same problem last night when trying to run my yearly RUU cleanup. I tried Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update. I'm suspecting that the rumrunner hboot I used was causing the issue, but I'm not sure. I'm assuming that you already have the drivers installed in Windows and that the PC can see your phone when you connect it.
0. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader. Since I'm s-off, I am not including how here.
1. Download the Full Firmware from RUU here. While you're there, get the RUU as well.
2. Flash the firmware file using fastboot following the directions in the OP. It failed for me the first time so I had to run it twice. The only thing I did differently was fastboot reboot-bootloader instead of just fastboot reboot at the end. The strange thing is that I ran it last night and it didn't work, but maybe I did something incorrectly.
3. While in (hopefully stock from step 2) bootloader, run the RUU as stated in the OP. I ran the RUU as an administrator and this time htc_fastboot.exe did not crash.
I'm now running pure stock (not for long I'm sure), still s-off. Good luck!
coal686 said:
I was having the exact same problem last night when trying to run my yearly RUU cleanup. I tried Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update. I'm suspecting that the rumrunner hboot I used was causing the issue, but I'm not sure. I'm assuming that you already have the drivers installed in Windows and that the PC can see your phone when you connect it.
0. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader. Since I'm s-off, I am not including how here.
1. Download the Full Firmware from RUU here. While you're there, get the RUU as well.
2. Flash the firmware file using fastboot following the directions in the OP. It failed for me the first time so I had to run it twice. The only thing I did differently was fastboot reboot-bootloader instead of just fastboot reboot at the end. The strange thing is that I ran it last night and it didn't work, but maybe I did something incorrectly.
3. While in (hopefully stock from step 2) bootloader, run the RUU as stated in the OP. I ran the RUU as an administrator and this time htc_fastboot.exe did not crash.
I'm now running pure stock (not for long I'm sure), still s-off. Good luck!
Click to expand...
Click to collapse
Haha, I just saw this after I fixed the problem using this exact solution!
thanks for the reply though!