Develop Bugs

[Q] FML...Should have left well enough alone.

So i somehow went hiroshima on my one x. I'll keep it short and simple. Had my BL unlocked but was running CWM recovery and the stock rom. Tried installing the cyanogenmod 9 and things went to hell after i flashed the boot.img. Now I am stuck at the white HTC screen. I read the disaster recovery but I am still having no luck. I relocked the bootloader and reflashed stock recovery then i tried using the ruu utility but it said that it didnt match and then rebooted with some developer text on the boot screen. I used the getvar command and it says:
version-main: 1.28.720.10
Before the blowup I had ran the OTA.I was on 1.26.720.10. This is the ruu i tried to reflash. I cant seem to find the 1.28.720.10. I also tried pulling the sys and boot img files from the temp directory and manually flashing, it gave an error.
as of right now i have the bootloader unlocked again and CWM recovery reinstalled so i can charge.
please help! $20 reward via paypal to the person that helps me get back to complete stock!
The worst part is i dont even want this damn phone...lol

Try this mate. If you can still get to bootloader and recovery it recoverable. I'd go back to stock so its as if you bought the phone, just to be safe. So...
Open cmd and CD to your fastboot file location. Plug phone in and...
First flash a stock boot.img from your stock.zip
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
Then relock your bootloader.
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
Then run the RUU.
But make sure you have the correct one. So that includes region. If you started on 1.26 and you haven't done any OTA updates then you need 1.26 but with your region code.
Good luck!
Sent from my HTC One X using xda premium

i did do the ota to 1.28 before i blew it up. also, how do i find the right region code? WHen i searched google for the results of my getvar version-main i found a bunch of threads referring to that being the ota for india, so thats the ruu i downloaded from the fileshare. i was working off a hunch though.
Will I be able to use a 1.26 RUU if I updated to 1.28, seeeing as how my getvar says 1.28?

applejoos said:
i did do the ota to 1.28 before i blew it up. also, how do i find the right region code? WHen i searched google for the results of my getvar version-main i found a bunch of threads referring to that being the ota for india, so thats the ruu i downloaded from the fileshare. i was working off a hunch though.
Will I be able to use a 1.26 RUU if I updated to 1.28, seeeing as how my getvar says 1.28?
Click to expand...
Click to collapse
Yeah if you did the OTA you need to use the 1.28 RUU as your hboot will have updated along with either things so 1.26 won't work.
Sent from my HTC One X using xda premium

benjamin.j.goodwin said:
Yeah if you did the OTA you need to use the 1.28 RUU as your hboot will have updated along with either things so 1.26 won't work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
So since there is no RUU matching my version number I am screwed now right?

Use the 1.29 ruu?

backfromthestorm said:
Use the 1.29 ruu?
Click to expand...
Click to collapse
there is no 1.29 for my region code.

applejoos said:
So since there is no RUU matching my version number I am screwed now right?
Click to expand...
Click to collapse
Do you know how to push a ROM.zip on to your SD card via command prompt?
Try downloading a custom ROM and flash the boot.img then, clear cache, then boot to recovery and flash the ROM. Then reboot. Should work.
Sent from my HTC One X using xda premium

Back to Stock, but how exactly?

Hello togehter,
i found this to-do-list:
1. Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
2. Clear fastboot cache
Code:
fastboot clear cache
3. Boot your phone
4. Charge you phone completely
5. Download stock recovery
6. Flash stock recovery
Code:
fastboot flash recovery endeavoru_recovery_signed.img
7. Relock bootloader
Code:
fastboot oem lock
8. Run 1.26 RUU
Click to expand...
Click to collapse
so not that big deal at all. i got the vodafone 1.26 ruu
but i dont find i 1.26.x rom. could i doo this from a 1.29 rom too? normaly the ruu should override everthing right?
one x got wlan problems, signal jumping like hell, nothing helps (reboot, reflash, router reboot, other router...). SO back to stock for warrenty exchance.
greetings and thanks

Hello neighbour..xD
Should be no problem like you posted it, flash 1.29 and you are good to go..

thanks
downloading ruu... takes 2 hours. to premium @ filefactory^^
greetings

ah, just one more question
which recovery to flash?
stock 1.26 for 1,26 ruu right?
or 1.29 for running 1.29 rom in the back
greetings

This video might help...

bigoliver said:
This video might help...
Click to expand...
Click to collapse
That's a good guide, but btw...
Make sure your phone is AT LEAST 50% charge.
Because, during the updating process, it will not charge with the usb cable and therefore not going to charge the phone.
If it shuts off during updating, you cannot charge the phone even if it's off.

NitNav said:
That's a good guide, but btw...
Make sure your phone is AT LEAST 50% charge.
Because, during the updating process, it will not charge with the usb cable and therefore not going to charge the phone.
If it shuts off during updating, you cannot charge the phone even if it's off.
Click to expand...
Click to collapse
Good advice, you should always flash with plenty of battery.
Sent from my HTC Desire using xda premium

holy.......
RUU won't run
i think its because the blank cid number.
what RUU will work? device just boot in fastbook mode, nothing else possible now
greetings and HELP

Havoc2k said:
holy.......
RUU won't run
i think its because the blank cid number.
what RUU will work? device just boot in fastbook mode, nothing else possible now
greetings and HELP
Click to expand...
Click to collapse
I had this problem, I was trying to flash the original rom that came with the phone, but, because I had, at some point, officially ota updated the software I needed to revert back to the updated software. Hope this helps,
Oliver
Sent from my HTC Desire using xda premium

sy i dont get the point.
so what to do?
phone was running at 1.29.xx (latest FW from htc)
ruu is for 1.26.xx
recovery img is 1.26 too
can't flash anything right now cause the phone is relocked now
greetings
edit: fault msg:
Error [131] CUSTOMER ID ERROR
The ROM Update Utility cannot update your Android phone
please get the correct rom update utility and try again.
Click to expand...
Click to collapse
so its because the CID, but hmm what to do now :/
greetings

Havoc2k said:
sy i dont get the point.
so what to do?
phone was running at 1.29.xx (latest FW from htc)
ruu is for 1.26.xx
recovery img is 1.26 too
can't flash anything right now cause the phone is relocked now
greetings
Click to expand...
Click to collapse
When RUU 1.26 didn't work for me I tried RUU 1.28 (latest three branded RUU) And that worked.
I think you might be trying to flash the wrong RUU you need the latest version of your RUU that you have previously ran on your phone.
It sounds to me from your posts that you need the 1.29 RUU but it's your responsibility to make sure you use the correct RUU.
Sent from my HTC Desire using xda premium

[Q] Cant find my boot loop answer on search

I understand the n00b rules but for the last 3 days I cant find anything on here that helps me specifically
tried to update to Android Revolution 18.0 using youtube video, I personally think the bootloop comes from not updating hboot;
*Unlocked*
Endeavoru pvt ship s-on rl
HBOOT-0.95.0000
CPLD-None
Radio-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Modem path : OFF
CWM v5.8.2.7
I'm trying to charge highest i get to is 3664V
When i charge from wall red light dies after about 30 mins
When I charge from usb after fastboot powerdown red light dies after about 30 mins
When I leave at "Quietly brilliant" red light dies after about 30 mins
When I leave on CWM screen goes to black after 30 mins
In any of these 4 instances is is still charging?
If I get higher what should I do specifically if I want to return to original stock?
Sorry if this stoopid but cant find anything about the redlights turning off.
My last idea was this;
powerdown from fastboot after unplugging usb,
then plug in usb
after 20 minutes long press power till "Quietly brilliant" comes on
then power and volume up to fastboot mode and repeat
This worked for a little while but then I get flashing red light and cant enter "Quietly brilliant" for about 10 minutes :/
Someone please help this N00b

Flash cwm 5.8.4.0
Fixes charging problem
It will charge in recovery but won't have light.
If too low battery to flash,
Try this
When you have enough juice you can probably flash the Rom if compatible
maXimus One X

you didnt upgrade the hboot you need an hboot above 1.31(preferably the latest) to prevent bootloops. and also you have to flash the boot.img from the rom zip file this is extremely important.
If you cant flash anything because of low battery read the post before me, and flash a custom recovery. then charge from the recovery with screen off to boost.
here is the link for both scripts.

Thanks for the reply
evo1rs said:
Flash cwm 5.8.4.0
Fixes charging problem
It will charge in recovery but won't have light.
If too low battery to flash,
Try this
When you have enough juice you can probably flash the Rom if compatible
maXimus One X
Click to expand...
Click to collapse
I'll have to try and flash that version and get back to you, thanks.
What is the maxium voltage this phone will hold and what voltage will it go through with a flash?
Vcek said:
you didnt upgrade the hboot you need an hboot above 1.31(preferably the latest) to prevent bootloops. and also you have to flash the boot.img from the rom zip file this is extremely important.
If you cant flash anything because of low battery read the post before me, and flash a custom recovery. then charge from the recovery with screen off to boost.
here is the link for both scripts.
Click to expand...
Click to collapse
I wanted to try this but my phone is unlocked, shall I still try it? Do I need to re-lock my phone?

Mikeyfish90210 said:
I'll have to try and flash that version and get back to you, thanks.
What is the maxium voltage this phone will hold and what voltage will it go through with a flash?
I wanted to try this but my phone is unlocked, shall I still try it? Do I need to re-lock my phone?
Click to expand...
Click to collapse
Yes you have to relock the bootloader then update it then unlock it again.
Sent from my EndeavorU using xda app-developers app

Vcek said:
Yes you have to relock the bootloader then update it then unlock it again.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
If I didn't relock it but CWM updated after flashing is it charging in the recovery? I just heard a lot of bad things from relocking but it seems to have successfully installed cwm 5.8.4.0 anyway and its currently sitting in recovery mode now.

100% should be about 4.2v
I managed to fastboot flash recovery img at about 10% I think, the bootloader screen warns you if battery too low to flash anyway
maXimus One X

Yes for flashing recovery's and boot.img files you need an unlocked bootloader, fot flashing firmwares you need a locked bootloader
And yes the phone should charge in the cwm 5.8.4.0 recovery ....

Mr Hofs said:
Yes for flashing recovery's and boot.img files you need an unlocked bootloader, fot flashing firmwares you need a locked bootloader
And yes the phone should charge in the cwm 5.8.4.0 recovery ....
Click to expand...
Click to collapse
so going forward from I here I;
>Charge phone 100%
>Lock bootloader
>Update hboot firmware
>Unlockbootloader
>Flash boot.img of new rom
>Then flash rom
Do i have to worry about kernels? I checked the CID for my phone and know which firmware to install.
P.S. Thankyou so much for this guys you really are amazing, my fiance has been so pissed at me for the last few days!

Mikeyfish90210 said:
so going forward from I here I;
>Charge phone 100%
>Lock bootloader
>Update hboot firmware
>Unlockbootloader
>Flash boot.img of new rom
>Then flash rom
Do i have to worry about kernels? I checked the CID for my phone and know which firmware to install.
P.S. Thankyou so much for this guys you really are amazing, my fiance has been so pissed at me for the last few days!
Click to expand...
Click to collapse
No kernels are not cid related, only the firmware. But as you said you have the right one so that's fine.
Rule 1 : always flash the kernel that comes with the rom
Rule 2 : always do a FULL WIPE if you are coming from another rom
:thumbup:

Mr Hofs said:
No kernels are not cid related, only the firmware. But as you said you have the right one so that's fine.
Rule 1 : always flash the kernel that comes with the rom
Rule 2 : always do a FULL WIPE if you are coming from another rom
:thumbup:
Click to expand...
Click to collapse
this'll seem like a thick question but kernel= boot.img?

Correct.

So atm my phone is bubbling away getting more battery life in the meanwhile;
what sort of voltage am I looking at before it will install the firmware, I need to get this fixed fairly quickly, atm its on 3677mV
Also once I update the firmware I noticed you've previously told people this;
"fastboot oem unlock unlock_code.bin"
Do i use my origional unlock code or generate a new one?

Don't know about the voltage thing but yes you can use the code.bin file again
Fastboot flash unlocktoken unlock_code.bin
Is the right command

Mr Hofs said:
Don't know about the voltage thing but yes you can use the code.bin file again
Fastboot flash unlocktoken unlock_code.bin
Is the right command
Click to expand...
Click to collapse
It is probably better using the real code instead of making it up
Do you know if it recharges quicker in CWM mode or by using the recharging batch file?

Cwm is a bit faster as far as i know ! And its better for the phone because its not rebooting continuously !

So finally fully updated and squeeky clean phone thank you so much Mr Hoff and other users, absolute legends

Glad it worked out ! Have fun with your clean and fully working handset
CASE CLOSED !

[Solved] Boot loop on every ROM

Hello.
I currently have SlimBean 3.0.0 installed, and I'm trying to get Sense back. I've tried countless ROMs, but on every single one of them, I get boot loop and then I have to install Slim again.
Yes, I do all the wipes, including dalvik cache, but nothing seems to help.
Thanks in advance.

Have you flashed the boot.img of each rom?

Re: Boot loop on every ROM
And what is your hboot number ?

Yes, I've always flashed the boot.img that comes with each one.
Now that you mentioned hboot, that might be an issue. It's 0.94.000, I've tried to search, but I can't find any instructions on how to upgrade it.

Re: Boot loop on every ROM
Yeah the old hboot is the issue
Get the main version, lets get back to stock and update the phone with official ota ! I bet there is a matching ruu for you with that old hboot
Do
Fastboot getvar version-main
Post the result please

Mr Hofs said:
Yeah the old hboot is the issue
Get the main version, lets get back to stock and update the phone with official ota ! I bet there is a matching ruu for you with that old hboot
Do
Fastboot getvar version-main
Post the result please
Click to expand...
Click to collapse
Here:
version-main: 1.28.401.9

Re: Boot loop on every ROM
Oke download this file
http://androidfiles.org/ruu/securek...Radio_2.1204.135.20_release_274900_signed.exe
Charge the battery before you do this :
Put the phone in the bootloader and relock the bootloader
Fastboot oem lock
After that you keep the phone in the bootloader and execute the ruu.exe from the pc with admin rights (right click the ruu.exe)
This will flash the phone to original android 4.0.4. When the ruu flashed with succes you boot the phone and update the phone with the original OtA to JB

Alright, I'll do that when the phone is charged. Many thanks.

Now this is just horrible... I got it to 4.1, but now I can't select it to charge only when connected, so I can't root it.

Re: Boot loop on every ROM
Just set usb debugging enabled and you're good to go.

TToivanen said:
Just set usb debugging enabled and you're good to go.
Click to expand...
Click to collapse
I was able to flash the recovery via fastboot. Next I'll try to install JB Remix ROM.
EDIT: The issue has been solved.

Glad it worked ! :thumbup:
CASE CLOSED !

[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