Develop Bugs

Could use a hand getting back to Stock

HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.

bump
Anyone know what this error might mean?
QUOTE=requiem11;30025087]HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.[/QUOTE]

have u tried to install the RUU in fastboot mode?

GUARDIANBD said:
have u tried to install the RUU in fastboot mode?
Click to expand...
Click to collapse
Thanks for the reply. It's a good point that is occasionally not mentioned. I've always assumed that the RUU is to be run while in bootloader with fastboot command window open and RUU exe located within the fastboot directory. I used "fastboot devices" to confirm that the pc has recognized the HOX. I also disconnected everything and tried to run the RUU exe file on its own in order to manually flash the exe file contents, but the RUU does not run properly giving me the 0x80070002 windows error message.
three things I have yet to try:
1 install the stock recovery tool (still relying on CMW)
2 run the RUU on another computer (read somewhere that this helped someone's RUU issue when they tried it on an XP)
3 try to download the RUU again
not sure if any of these would help.
By chance, did you mean that the RUU can be somehow executed as a fastboot command? If so I haven't seen anything about it and would appreciate a detailed description of how to do that.
tanks

I think you have to flash stock recovery and lock the bootloader to flash ruu. Don't quote me though. Worth a try.
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom

smidgeox said:
I think you have to flash stock recovery and lock the bootloader to flash ruu. Don't quote me though. Worth a try.
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom
Click to expand...
Click to collapse
I've tried with the bootloader locked but not with the stock recovery flashed. I'll try it and report back. Any other suggestions are welcome.
thanks for replying.

Partial success
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again

requiem11 said:
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again
Click to expand...
Click to collapse
I should imagine that the bootloader needs to be unlocked to be able to flash any sort of .img file.
Have you flashed the ruu with stock recovery yet? I suggest you try this if you haven't already, if this fails. Ensure you have the correct matching RUU, then flash stock recovery, lock bootloader and try that.

Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Look on YouTube cursed4eva has an easy to follow video about going back to stock ROM

nixey55 said:
Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Look on YouTube cursed4eva has an easy to follow video about going back to stock ROM
Click to expand...
Click to collapse
Indeed, the boot.img contains the kernel & with s-on devices, boot.img's aren't flashed through recovery so it needs to be done on a computer with fastboot (fastboot flash boot boot.img).
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
requiem11 said:
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again
Click to expand...
Click to collapse
Also, i forgot to mention. MAKE sure you hold the power and down volume key down to enter the bootloader, then enter 'fastboot' to be able to flash the boot.img in fastboot , i thik that might be the reason you're getting the failed error.

smidgeox said:
Indeed, the boot.img contains the kernel & with s-on devices, boot.img's aren't flashed through recovery so it needs to be done on a computer with fastboot (fastboot flash boot boot.img).
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
As a point of clarification, the RUU contains the associated boot.img and system.img required to get back to stock. If your RUU fails for some reason, there are instructions in the HTC One X wiki for extracting the RUU file and manually flashing the boot.img and system.img
Also, i forgot to mention. MAKE sure you hold the power and down volume key down to enter the bootloader, then enter 'fastboot' to be able to flash the boot.img in fastboot , i thik that might be the reason you're getting the failed error.
Click to expand...
Click to collapse
Yes, I did enter the bootloader correctly.

nixey55 said:
Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Click to expand...
Click to collapse
You're right as to the point that each ROM has a matching boot.img, but in which order you flash them doesnt matter at all.

Unlock the bootloader again and flash a custom ROM, it's usually the easiest way out. Don't bother using the boot.img root method as custom ROMs are pre rooted almost 99 percent of the time.
Sent from my Inspire 4G using Tapatalk 2

requiem11 said:
HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.
Click to expand...
Click to collapse
Can you upload the file RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350 I can't download it form filefactory !

Not sure where I'd upload it for you to get it, but I followed some instructions that I found here and it worked using Safari
http://o-ogy.blogspot.com.au/2012/02/how-to-use-filefactory-premium-cookie.html
There are a lot of steps, but follow them carefully and it should work.

[Q] Bricked One X (Black screen with silver htc logo)

I have searching for a solution here for last 2 days but couldn't find one
Problem :
My one x is displaying black screen with silver "htc" logo. It does not boot in bootloader or recovery. Although fastboot commands are still running on this blackscreen.
What I did
I successfully unlocked my one x and installed paranoiandroid but when I started using it my phone began to hang and the touch was disable.
Then I read the post for getting bavk to stock using RUU. I followed these step.
- checked my phone version using "fastboot getvar version-main"
- downloaded "RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed"
- unlocked the bootloader "fastboot oem lock"
- Ran the RUU exe file.
Now the RUU is giving an error the RUU is not correct but it is the same version which I get from "fastboot getvar version-main" and now my phone is only displaying the black screen with sliver "htc" logo.
I shall be grateful if someone can provide a solution to my problem. Thank you.

try 'fastboot reboot-bootloader' or 'fastboot oem reboot-bootloader' (forgot which one).
Then try find a correct RUU to flash or just flash a custom ROM.

tomascus said:
try 'fastboot reboot-bootloader' or 'fastboot oem reboot-bootloader' (forgot which one).
Then try find a correct RUU to flash or just flash a custom ROM.
Click to expand...
Click to collapse
Thank you for the reply.
I have tried it. The command executes but the phone again boots in blackscreen with silver "htc" logo. It is not going in bootloader.

If you re-run the command fastboot getvar version-main, will it give you the same no. 2.17.707.3 ?

ckpv5 said:
If you re-run the command fastboot getvar version-main, will it give you the same no. 2.17.707.3 ?
Click to expand...
Click to collapse
Yes it is giving the same version and I have downloaded the exact RUU version still RUU fails to complete its setup stating "not correct RUU, download the correct file"

I was searching for a solution and found that RUU setup also works if the RUU version is an updated version with same region e.g x.xx.707.x.
I have downloaded RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed. Should I try this?

sherwaniusman said:
I was searching for a solution and found that RUU setup also works if the RUU version is an updated version with same region e.g x.xx.707.x.
I have downloaded RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed. Should I try this?
Click to expand...
Click to collapse
Good luck! :laugh:

tomascus said:
Good luck! :laugh:
Click to expand...
Click to collapse
No luck same error occurred.

Mind if i asking? Do u just run the RUU or u flash boot_signed.img etc etc first?
Sent from my HTC One X using xda premium

serwan said:
Mind if i asking? Do u just run the RUU or u flash boot_signed.img etc etc first?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I unlocked the bootloader and ran RUU.exe file from my computer. The setup begins and error occurs while flashing the rom image

I think you should reinstall the HBoot manually...
What CID do you have?
Is your Bootloader "relocked" ??

andyoso said:
I think you should reinstall the HBoot manually...
What CID do you have?
Click to expand...
Click to collapse
How to reinstall the Hboot?

sherwaniusman said:
I unlocked the bootloader and ran RUU.exe file from my computer. The setup begins and error occurs while flashing the rom image
Click to expand...
Click to collapse
U need to RELOCKED your bootloader.
Please google how to extract boot_signed.img , recovery_signed.img and rom.zip from RUU. After u've extract those, flash boot_signed and recovery_signed first. Then boot to recovery, flash your rom.zip and only after that u run the RUU. Give it a try.
Sent from my HTC One X using xda premium

sherwaniusman said:
How to reinstall the Hboot?
Click to expand...
Click to collapse
You should download it before...if you give me your CID pass you the correct link to download the correct "firmware.zip" that contains the HBoot.
After the downloading you should type this command twice:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse

andyoso said:
You should download it before...if you give me your CID pass you the correct link to download the correct "firmware.zip" that contains the HBoot.
After the downloading you should type this command:
Click to expand...
Click to collapse
Thank you. My cidread returns HTC_044. Also I have logged into bootloader screen again. I just ran the Unlock_bin file I received during rooting my device and now my phone isn't displaying the black screen and finally entered bootloader.
The problem I figured out was my bootloader was relocked and my RUU setup failed, so I had a custom rom installed with locked bootloader. That's why the phone was bricked I wan't entering bootloader.
Now I can access my recovery as well.

serwan said:
U need to RELOCKED your bootloader.
Please google how to extract boot_signed.img , recovery_signed.img and rom.zip from RUU. After u've extract those, flash boot_signed and recovery_signed first. Then boot to recovery, flash your rom.zip and only after that u run the RUU. Give it a try.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
You don't need to extract anything from the ruu, if you have the right ruu just lock the bootloader and leave the phone there ... Start the ruu from pc with admin rights.....

Im speakung from my experiance. I have face this problem before. RUU program cant install the rom. So i have to flash everything extracted from RUU first. Only after that the RUU can install the rom. But maybe im just got lucky though.
Sent from my HTC One X using xda premium

[Q] OTA JB Update will not flash

Hi All,
This is my very first post, I received 2 updates for my device yesterday, 1 being the updated Hboot and the other the JB rom (about time HTC)
I have a rooted One X CID 001 and previously tried flashing a custom rom and failed (got caught in a horrible bootloop) and managed to flash back to stock.
Now this is where I think I have the problem; I have CWM installed, and every time I try to flash the OTA it fails and reboots the phone, yes I have installed the HBoot update before trying to flash in case you are wondering.
I downloaded the RUU today and spun up a windows VM (I am on Mac) which would allow me to adb/fastboot but failed to start anything saying there is no USB device connected. So I tried something else;
I then copied the .zip from the RUU doing the %temp% trick in windows, and copied it to the SD and then ran CWM and tried to install - failed again.
I then tried something else; fastboot flash the zip - fastboot flash zip rom.zip which failed (in Windows) and on my mac I get this error;
sending 'zip' (653640 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Im running out of ideas! Please help!
:crying:

The official update won't install with clockwork recovery
Sent from my HTC One X using xda premium

JB
danton11 said:
The official update won't install with clockwork recovery
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks for your response, confirmed my suspicion, so as I cant seem to get my windows VM to install the RUU, what would be the best way to remove clockwork?

relock your bootloader in fastboot with this command:
fastboot oem lock
Now run the ruu!
But more importand. You should read everything related to flashing modding of the HTC One X and also the Forum Rules.

nitrous² said:
relock your bootloader in fastboot with this command:
fastboot oem lock
Now run the ruu!
But more importand. You should read everything related to flashing modding of the HTC One X and also the Forum Rules.
Click to expand...
Click to collapse
Thanks but I already tried that.

ExiLeDSoRcEreR said:
Thanks but I already tried that.
Click to expand...
Click to collapse
i had the same problem,if you made a nand back up of your stock rom and thats what you are running now-you need to flash the stock recovery there is a link somewhere by clyde.
thats what was stopping me,flashed the stock recovery with the onex all in one tool,re locked boot,flashed the two apk's to force the ota.downloaded and it installed.
you can also do this by adb or download the jb ruu for your device,i was also on 001 cid

markb63 said:
i had the same problem,if you made a nand back up of your stock rom and thats what you are running now-you need to flash the stock recovery there is a link somewhere by clyde.
thats what was stopping me,flashed the stock recovery with the onex all in one tool,re locked boot,flashed the two apk's to force the ota.downloaded and it installed.
you can also do this by adb or download the jb ruu for your device,i was also on 001 cid
Click to expand...
Click to collapse
Ta mate! will give that a try when I get out the office and let you know.

[Q] Q: Firmware Package HTC One X

I'm going to update my htc one x to jelly bean from ICS, using custom ROM (ARHD), it was noted that I need a firmware package, and now that I found the package for my CID because took sometime before I found it, is it really required to flash it? TIA

For JB roms you need a JB hboot those are the 1.31 and higher up. Except for the aosp JB roms, those run also on the lower ics hboots.
So if you are on a lower hboot then 1.31 then yes you need to upgrade the hboot

Now I think everything's messed up and I badly need help here, so stupid with I did.
At one moment, my phone is stuck at One tm screen, after I flash the boot.img and installed the custom ROM. I tried to restore my phone using CWM but it still stucked. It was too late before I realized how to flash the firmware package that I need to rename what I downloaded to firmware.zip. I tried flashing the firmware without knowing that I have to relocked my phone before I flash it. Now I relocked my phone and I'm stucked with hboot and I can't do anything at the moment.

With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zip
Once completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zipOnce completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cannot load "firmware.zip" always shows up. My CID is HTC_044, and as far as I know I downloaded the correct firmware package for my phone according to ARHD forum. Thanks in advance.

Did you have the firmware.zip in your fastboot folder?

Yes. And I downloaded it 3 times just to make sure it is the right firmware.

Oh and sometimes you need to flash it 3 or 4 times to succeed. I had to do the command 3 times when I flashed my firmware.
So try it multiple times in a row.
Sent from my One X

Sorry but I tried several times and "error: cannot load 'firmware.zip' all the time. What could be the problem?
During at work. I thought if is it possible just to return to stock ROM? But I just can't find the proper RUU yet.
cid: htc_044
version-main: 1.29.707.11

I'm currently charging my phone using the batch file I found here in xda. I saw a lot of posts regarding flashing the current version of CWM so you can charge your battery, I think my CWM is in version 5.8.1.0, and as far as I know you have to unlock your hboot before you can flash recovery, so it's impossible for me to flash 5.8.4.0? Am I correct here or I can just proceed to the other steps?

I can check tonight if i have your RUU !

Mr Hofs said:
I can check tonight if i have your RUU !
Click to expand...
Click to collapse
Thank you Mr Hofs! And, should my battery level is 30% or higher before I can flash the RUU?

Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked

Mr Hofs said:
Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked
Click to expand...
Click to collapse
I was done in re-unlocking my bootloader, but then I still can't flash cwm recovery because it says low battery, then I tried to use the batt script again and of course it cannot work since I just re-unlocked my bootloader.

I never tried it with a unlocked bootloader, have you tried it ?

Yes, I tried it and it doesn't work.
What I did for the past hours, I tried to restore my phone again using cwm recovery, still nothing changed, still stucked at htc one logo, then I turned it off trying to charge it using the main charger and it does have light in its LED, left it for a while and now it doesn't turn on.

Try it with phone connected to the pc, it seems to make a difference sometimes....and if you are capable again to run the bat script then leave it for 2.hours or so !

Now it's working. The first time I used the batt script, I thought it could charge more than 3681mV but It didn't work as it didn't get higher than 3681mV. I HOPE it's enough just to flash the cwm recovery. Thanks Mr Hofs, will update asap.

[SOLVED] Hboot upgrade attempt failed

I'm trying to help a friend remotely fix his current brick of a HOX and would like some pro advice to ensure im telling him the right thing. Info I have:
Its S-On UK T Mobile CID T-MOB005.
He obtained a 1.39 firmware from somewhere that matched his CID
At some point in the process the firmware flash failed or partially flashed
His Custom Recovery is gone
His HBoot version has not increased (i think 1.12)
He has a security warning under the 'relocked' message in bootloader
Before he tried the firmware upgrade he flashed viper x 3.4.0 + boot.img so the phone wont boot up normally now
He has a nandroid backup from before the process.
Im going to recommend to him to download the 1.36 firmware from Mikes thread here http://forum.xda-developers.com/showthread.php?t=1957376 (i notice there is no 1.39 available for his CID so im suspicious this was a duff file he had for 1.39)
If he cant flash it because of low power then he should use the charging batch script first or re-unlock, flash CWM, restore nandroid and flash the boot.img from it so he can boot phone and charge it normally or from cwm.
I guess after that start to look at an RUU or a stock nandroid backup download to be able to do the firmware OTA ?
My own HOX is S-Off so im not as familiar with the process as i never worried about the correct firmware or had to flash boot.img separately from roms or nandroids.
Any tips appreciated.
Cheers

Re: Hboot upgrade attempt failed
Yeah that's about it.....only flashing the rom is not going to work because of the low hboot.
Just charge the battery and and unlock the bootloader, then reflash a custom recovery and charge the battery up in there.
With enough power he can relock the bootloader and flash the firmware
Fastboot oem lock
Fastboot rebootRUU (watch the capital letters)
Fastboot flash zip firmware.zip
Unlock the bootloader
Fastboot flash unlocktoken unlock_code.bin
Then flash the custom recovery again and install a new rom ! :thumbup:

Cheers, so out of interest what causes the Security Warning in the bootloader ? Is it because the phone knows there is a screwed up firmware flash or knows it cant boot\has low power ? It must have done something as his custom recovery was wiped even though the Hboot ver didnt change.

how does the security warning look like exactly.....i know there is a warning because the bootloader is relocked. don't know if we are talking about the same picture now

Re: Hboot upgrade attempt failed
You have to relock the boot loader to flash an updated firmware which is the point you are at and why you are seeing the security warning.
The first time you flash the updated firmware it flashes everything else.
Stock recovery, boot.IMG and sometimes other partitions.
Then it tries to flash the hboot and fails.
All you usually have to do is tell it to flash a second time and then in succeeds in updating boot.
Obviously he stopped after the first attempt which is why only the recovery changed and not the hboot.
I doubt he has a bogus firmware as the phone will not attempt to flash anything that isn't signed and cid matched.
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
You have to relock the boot loader to flash an updated firmware which is the point you are at and why you are seeing the security warning.
The first time you flash the updated firmware it flashes everything else.
Stock recovery, boot.IMG and sometimes other partitions.
Then it tries to flash the hboot and fails.
All you usually have to do is tell it to flash a second time and then in succeeds in updating boot.
Obviously he stopped after the first attempt which is why only the recovery changed and not the hboot.
I doubt he has a bogus firmware as the phone will not attempt to flash anything that isn't signed and cid matched.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Great will check, just assumed he had tried it twice as all instructions I've seen state that you must but then again i dont know what instructions he followed - maybe he didnt ! Ive not seen this explanation of whats being flashed and in what order before - cheers.

Mr Hofs said:
how does the security warning look like exactly.....i know there is a warning because the bootloader is relocked. don't know if we are talking about the same picture now
Click to expand...
Click to collapse
Ive not seen it but i assume its something like this
*** RELOCKED ***
*** Security Warning ***
Then all the usual bootloader stuff
based on images ive seen before on web. can find them with a quick google of images.

Re: Hboot upgrade attempt failed
Yeah that's normal :thumbup:

Re: Hboot upgrade attempt failed
Ok it lives ! Was a combination of the firmware file and his battery being too low to flash so he put cwm back on, charged and then followed my instructions. Cheers for help
This is the what I sent him incase anyone else finds them useful. Assumes you know roughly what your doing and that you must get back to fastboot usb for the commands .
-----------------------------
So get phone into fastboot mode by power plus vol and choose it in bootloader., plug usb in so it says fastboot usb, then get command prompt in directory with fastboot in on pc.
1. Lock bootloader with: fastboot oem lock
2. Vol and power down to get into bootloader again
3.fastboot oem rebootRUU
4. Should now get phone with silver HTC in middle on black
5. fastboot flash zip firmware.zip where this is the new firmware for your cid.
6. Might fail first time. Do it again and it works
7. Should now see green bar completed under the htc
8. Power and vol to get to bootloader. The hboot should now be updated.
9. Now to unlock bootloader again
. fastboot flash unlocktoken unlockcode.bin (where unlockcode.bin is the file you got from htcdev)
10. Now on the phone select yes and it reboots.
11. Don't wait just use power and vol to get into bootloader.
12. Flash custom recovery again. fastboot flash recovery recovery.img where recovery.img is the cwm 5.8.4.0
13. You can now flash your chosen Rom boot.img. fastboot flash boot boot.img
14. fastboot erase cache
15. Now use recovery to flash the Rom.
16. Done
Sent from my HTC One X

Very good :thumbup:
CASE CLOSED !

I have to say that the OP did a great job at providing the needed information. I wish everyone would describe their problems as good as the OP of this thread, it would make helping people out hell of a lot easier.
Sent from my HTC One X using xda app-developers app

ViktorN said:
I have to say that the OP did a great job at providing the needed information. I wish everyone would describe their problems as good as the OP of this thread, it would make helping people out hell of a lot easier.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So true !

Indeed. Not very often you can tell exactly where a problem is without having to ask for more info. In fact. A thanks to the op for providing a very detailed diagnosis without even having the device to hand
Sent from my HTC One X using xda app-developers app