Develop Bugs

[TUT] Re-flash stock ROM (RUU) after bricking a rooted device (for noobs)

Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU (ROM Update Utility) for your device from androidfiles.org. Make sure you download a Primo_C RUU for a CDMA device (no sim card) or a Primo_U RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!

Hi
Thanks for that perfect decsription exactly when I needed it
I just had a weired effect with my new windows 7 laptop that I want to share.
I installed the USB drivers and "fastboot devices" showed my HTC fine
but even flashing the stock recovery image was not working.
So it was stucking in the "Sending" part and never continued.
I then moved to my old laptop with Vista did exactly the same things
and there it worked without problems.
I disabled virus scanner, checked for htsync and used the original USB cable
without success.
But now I know why I normally never touch Windows and only
work on linux
Regards
max
---------- Post added at 11:19 PM ---------- Previous post was at 10:33 PM ----------
Hi
CafeKampuchia said:
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
I have done that now - compared to my first "try"
Regards
max

hi. thanks for the tips.
however when i do this, i get an error "FAILED <remote: signature verify fail>
Any suggestions?

ur RUU and CID is diff...

ryanlow134 said:
ur RUU and CID is diff...
Click to expand...
Click to collapse
and... how do i make them the same?

lcavada said:
and... how do i make them the same?
Click to expand...
Click to collapse
Use the correct RUU package for your device
regards
max

Another way of saying it is that you downloaded the wrong RUU for your device.

not working
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out

I use fastboot flasher for this.. this tool is good .

sush93 said:
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out
Click to expand...
Click to collapse
"Waiting for Device" at fastboot usually related to bootloader driver. You need Android USB Driver
See : http://developer.android.com/sdk/win-usb.html

Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!

run the ruu in hboot..
Sent from my HTC One V

thevilish said:
Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!
Click to expand...
Click to collapse
Flashing RUU to revert to stock
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
NOTE: There is no boot/reboot and enter pin in between.

paarthdesai said:
run the ruu in hboot..
Sent from my HTC One V
Click to expand...
Click to collapse
I've done this before and didn't succeeded, but now it works! Magic
Thanks a lot!

help
CafeKampuchia said:
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
PLEASE HELP!
The 5th point does not work for me. I can not run the code.
What can i do?

what do you mean by navigate to the folder where you installed sdk?

brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
It means that if you installed SDK in c:/android, then u must type.in the command prompt: cd c:/android and hit enter
Cheers
Sent from my HTC One V using xda app-developers app

brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
where the fastboot.exe is located and stock recovery must be in the same folder for the command to work

[ask] Error 155
hey guys, ive been reading all tutorial for reverting to stock RUU.
the first time i tried, it works prefectly.
then after a few weeks, i tried to revert to stock RUU, it failed .
it show error 155.
i already flash the boot , recovery that i found inside the stock RUU, also I've relock the phone.
but when i relock the phone, it show "info Lock successfully , status read failed no such file / directory"
when i enter bootloader, it show that my device already "relocked"
does the relocked proses is successfully ?
iam running PrimoU 2.09.707.1 with stock bootloader, CWM recovery, and rooted ..

I did exactly as it is mentioned but at the end where there is vertical progress bar it gives me an error of customer Id... Failed to update. What shud i do. How do I check what my customer Id is I can't Download it from play store coz can't boot into normal screen... How do I make ruu and cid same.
Sent from my Galaxy Nexus using xda app-developers app

[Q] Completely wiped my One X, cannot mount usb, no backups, need backups

Hello everybody,
This is my first post on XDA, although I've visited the site oftne
Anyways:
Yesterday I successfully rooted my One X and unlocked its bootloader. I also installed CWM recovery.
As the day came to a close I tried to install LC_MOD in an attempt to change the multitasking softkey to a menu button.
I did not make a backup, and the phone had no backups.
Needless to say the phone wouldnt boot. I panicked and in blind fear sortof erased everything off of my phone. everything. What I basically did was i went into advanced settings and formatted my /sdcard and all those other folders, hoping that would solve the issue (a simple data/cache wipe didnt work). So much data has been erased from the phone that I cannot even mount usb storage through CWM because im missing a file.
So, I come to you all, you gods of the tech world, with my head bowed, to ask for your help. I have literally tried everything in my power to fix the issue. I tried to install custom roms manually, that didnt work. I tried to install an RUU, and even that didnt work (the software could not detect my device). This was all made even more difficult because I myself have a mac, and much of the software I had to use was windows based, which led me on a journey to create a virtual machine.
I know i messed up, and what I'm really hoping someone out there cn do is upload one of their own backups of their One X's software, and show me how to use that to restore my phone.
Somebody out there please please help me :'(

Hi;
There is a reason all developers here shout out loud:
1- BACKUP YOUR PHONE BEFORE YOU F*** IT UP
2- DO NOT DO ANYTHING UNLESS YOU ABSOLUTELY KNOW HOW TO
But anyways, you ruined it, you should get it back, Hopefully you did not drain the battery below 30%, in that case keep on reading the next paragraph, but if you dropped the battery below 30, you should go to CWM Recovery, connect your phone to charger, and wait until it's charged properly...
After charging the phone, you need the correct RUU for your phone... As it seems, you don't know what you're doing, so go to fastboot, type this command:
Code:
fastboot oem readcid
Then post the code here in this topic, so someone can help you find the correct RUU for your phone...
After that go to THIS topic and follow the part where it says "If you DON'T have custom rom or Nandroid backup on internal SD card"

Thanks
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before

Xial649 said:
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Click to expand...
Click to collapse
Don't worry, with the correct version of RUU you can restore your phone...
Sent from my HTC One X using XDA

Next?
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?

Xial649 said:
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Click to expand...
Click to collapse
Your phone is from Voda Germany, and most probabely your correct RUU is this:
Code:
http://www.filefactory.com/file/t7qugfd3ey9/n/RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed.exe
Download it. Hopefully it would be the correct RUU for your phone.
1- Now open the exe file you just downloaded and make sure that it fully started.
2- Don't click anything, just open "Computer" (formerly known as my computer) in windows and enter %temp% in your address bar.
3- You will now see some folders, just search through these folders for the ROM.zip (using windows search function)
4- When you found it, copy it to your desktop.
5- Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
6- Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
7- Go to your One X, go into the bootloader and go into fastboot mode. then connect your phone to computer.
8- Open CMD and navigate to the folder in which you have the two images and the fastboot file. (using cd command and after that the address you want to go to)
9- Now type in that
Code:
fastboot flash boot boot_signed.img
10- Now this one
Code:
fastboot flash system system.img
if all this is successful, you can just reboot your phone and everything is OK.
If you can't do any of these, let us now, we will help you through it...
Good lock
---------- Post added at 03:52 PM ---------- Previous post was at 03:41 PM ----------
In other note, RUUs are build to do an stand alone recovery of your phone. So you can first try, just running the RUU application and following the instruction given in the RUU. it may work correctly

This is good
Alright so i got everything going after downloading the RUU and it was in the process of restoring my phone, but then it said my battery went below 30% so i needed to recharge. At that point i had to leave, and so I noticed that if i left my phone in the booting animation (HTC logo) the LED light indicated that the phone was charging. Since I wasnt entirely convinced that my CWM recovery was actually charging the phone, i left it on booting while connected to my pc and hopefully itll be fully charged and ready to be restored tomorrow..... I really appreciate all the help you've given me man you've practically saved my life here , and I'd like to say that you've made my first cry for help a simple and smooth one.... Thank you very much my friend :victory: :highfive:

Problem
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3

Xial649 said:
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Click to expand...
Click to collapse
That's another method you can try, boot_signed is the stock kernel (and yes it's that small) and the recovery_signed is the stock recovery...
Since my previously mentioned method didn't work, do this:
1- flash the boot_signed.img into your device (fastboot flash boot boot_signed.img)
2- flash the recovery_signed.img in the device (fastboot flash recovery recovery_signed.img)
3- erase cache (fastboot erase cache)
4- lock your phone (fastboot oem lock)
5- now try again to flash the system image (fastboot flash system system.img)
And also, try having around 40% battery to do all this, don't let the battery drops under 30%

ALRIGHT!!!!
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....

Xial649 said:
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Click to expand...
Click to collapse
Your phone is "Vodafone Germany" version and the link I gave you is the "Voda DE" which seems right, but you can try that as well, doesn't heart...
No, for original ROM (RUU) you should have a locked boot-loader, unlocking is just for custom ROMs.

ok
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?

Xial649 said:
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Click to expand...
Click to collapse
The two first commands should work on a LOCKED boot-loader, so I think step 1 would not be necessary... If your phone is locked you should be able to do all steps 2, 3, 5 without problem (step 1 and 4 are the exact opposite of each other and if the phone is locked already I think can be skipped)

ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??

Xial649 said:
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Click to expand...
Click to collapse
Any luck in running the RUU itself directly?

i gave up
alright so nothig worked. Not the manual flash, and not the RUU itself. So ive resolved to visit my local help center for HTC devices, and see what they can do, if they cant fix it the least they can do is send it to the german branch for repairs. Thanks for all your help mate, you've really proven to be a great guide, but I guess something just isnt clicking in this case :/.......... i love u man

I'm not sure if this would work.
If you are still htcdev unlocked:
1. Enter bootloader in fastboot usb
2. Fasboot flash recovery -your recovery .img here"
3. Boot into recovery
4. Go to "mounts and storage"
5. Mount SD(I think this is right) and your sd should show up in your pc
6. Copy your rom zips and other zips you need/want
7. Unmount SD
8. By this time you should be able to flash your rom
9. Make sure you flash boot.img again in bootloader.
Hope this helps
Sent from my HTC One X using xda app-developers app

Isn't it mount usb storage?
Sent from my HTC One X using XDA Premium App

You couldn't mount the USB storage / sdcard because you were running CWM from the bootloader. If you connect it to the pc you can put the recovery file you flashed into the fastboot folder and do:
fastboot boot *recoveryfilename*.img
Then you can mount the sdcard etc.
If you have photos and things you don't want an ruu to get ride of, you can fix the ROM. You broke it by trying to install an deodrexed mod for an odexed Rom. If you're interested I can tell you how to fix it.

You could also take this opportunity to install a custom Rom, with which I can also help.

Need help updating to JB on HTC One X (HBOOT 0.43) [SOLVED]

Hey all, I dont usually post questions, cause I usually am able to find all my answers, but this time i really hit a stump. not sure if its just cause my case is unique.
I have a HTC__622 (so JB compatible), with HBOOT 0.43 running Android Revolution 9.7.2, and im looking to upgrade to JB. However, despite many guides and tutorials, I can't seem to get past updating my HBOOT. Let me list out what I've done (I was following http://forum.xda-developers.com/showthread.php?t=1660807, following method 2/3, cause i haven't cooked a rom since windows mobile LOL)
1-downloaded "RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.29.708.15_Radio_2.1204.122.17_release_268338_signed" (my original one was 1.29.708.2)
2-extracted rom.zip from the RUU, and copied over boot-signed.img, system.img, recovery-signed.img
3-flashed boot-signed.img, and recovery-signed.img. system.img failed.
4-relocked bootloader
5-this is where i get stuck, the RUU cannot detect my phone in fastboot mode and so I cant run the RUU.exe.
anyone got any ideas as to why i can't run RUU.exe from my comp while my phone is in fastboot mode? thanks in advance!

I have no idea what you are doing. To install an RUU:
fastboot oem lock
Run RUU.
All this extracting and flashing is madness.
When you boot into bootloader, what does it say on the screen?

BenPope said:
I have no idea what you are doing. To install an RUU:
fastboot oem lock
Run RUU.
All this extracting and flashing is madness.
When you boot into bootloader, what does it say on the screen?
Click to expand...
Click to collapse
I can relock but I can't boot back into my rom. im stuck in the bootloader. The RUU only detects my phone from normal phone mode.
The first lines on the screen are relocked, security warning, and then my hboot info.
Sent from my HTC One X using xda premium

I have done it yesterday and opend a thread http://forum.xda-developers.com/showthread.php?t=2048646
Only relock stay in fastboot mode and run ruu with admin rights... Than the setup will so the rest for u
Sent from my HTC One X using xda app-developers app

ngy said:
I can relock but I can't boot back into my rom. im stuck in the bootloader. The RUU only detects my phone from normal phone mode.
Click to expand...
Click to collapse
What error do you get in fastboot mode?

zottel1993 said:
I have done it yesterday and opend a thread http://forum.xda-developers.com/showthread.php?t=2048646
Only relock stay in fastboot mode and run ruu with admin rights... Than the setup will so the rest for u
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks man, i've looked at that thread though, i dont see what i'm missing. how did you run the ruu in fastboot mode?
BenPope said:
What error do you get in fastboot mode?
Click to expand...
Click to collapse
the error i get is the ruu cannot detect the phone through usb (while phone is in fastboot mode). and i cannot run the ruu while phone is in normal mode because i can't boot in normal mode when i lock my bootloader.

Does the phone say fastboot USB when you have it in fastboot/bootloader
Then try fastboot devices first to see if your serial comes up ! If it does you can run the ruu.exe from the pc with admin rights.....
Should do the trick

Ok I would try to do everything from the beginning.
To make it easier and faster you can use the script form that thread:
http://forum.xda-developers.com/showthread.php?t=1924003&highlight=jbfwflasher
Then you don't need to install RUU.
Remember to place in the folder boot.img from the rom which you want to flash later.
Have a good fun

Follow this it might give you an idea where to start and what to do
http://forum.xda-developers.com/showthread.php?t=2018040
say thanks if i helped you

MarcelHofs said:
Does the phone say fastboot USB when you have it in fastboot/bootloader
Then try fastboot devices first to see if your serial comes up ! If it does you can run the ruu.exe from the pc with admin rights.....
Should do the trick
Click to expand...
Click to collapse
i already have, i always fastboot devices first to check to make sure my device is connected. on my phone it does say fastboot usb, and i can run fastboot commands on it. and i've ran RUU.exe with admin rights, but still does not detect the phone and gives me a usb connection error.
mrdelook said:
Ok I would try to do everything from the beginning.
To make it easier and faster you can use the script form that thread:
http://forum.xda-developers.com/showthread.php?t=1924003&highlight=jbfwflasher
Then you don't need to install RUU.
Remember to place in the folder boot.img from the rom which you want to flash later.
Have a good fun
Click to expand...
Click to collapse
au contraire, i also have tried using this tool, but if you look carefully, its meant for hboot versions higher than 0.43, which i have. it just points me to download an RUU.exe for my phone (which I already have)
Onexed said:
Follow this it might give you an idea where to start and what to do
http://forum.xda-developers.com/showthread.php?t=2018040
say thanks if i helped you
Click to expand...
Click to collapse
hmm, so you're saying I just need to flash firmware.zip (for my HTC__622 of course), to get the hboot 1.36? i'll give that a shot and report back.
--update 1--
alright so after trying to just flash the new hboot 1.36 (from firmware.zip), i am met with this:
E:\Utilities\Android\One X\JBFWTOOL20>fastboot flash zip firmware-622.zip
sending 'zip' (12875 KB)...
OKAY [ 1.647s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.130s
how did you flash it and make it work?
--update 2--
I must've downloaded the wrong (or renamed the wrong) firmware.zip file, i just redownloaded and bam everything works. thanks a lot onexed, that did help. basically, even if you're on 0.43, just flash the firmware.zip for your phone, and get onto a newer hboot, and all is well. thanks!

Welcome i'm glad it worked out for you enjoy jellybean

[Q] anyone can help me ?

hi, i just got my htc one x and i want to update my software but unfortunately there is no sooftware update option in my htc one x setting-about-?? anyone can help??

It's always been the first item in the about menu on my phone.
In the settings->about-> software information menu, can you tell us what's listed there?

requiem11 said:
It's always been the first item in the about menu on my phone.
In the settings->about-> software information menu, can you tell us what's listed there?
Click to expand...
Click to collapse
bro i got 6 options in setting--about--1.help 2.network 3.phone identity 4.hardware information 5. software information 6.legal information

and in my software information there is :
android version 4.0.4
htc sense version 4.0
software number android revolution hd 7.2.2
htc sdk api level 4.23
htc extension version htcextension_403_1_ga_20
more

You're on a custom ROM mate!
Sent from my One X

You just got this phone, so presumably you have not unlocked the bootloader, or obtained root access, right? It could be that your provider just hasn't gotten around to getting the update to it's users yet (as is the case currently for some providers in NZ, but not all). Your android version is the lastest iteration of Ice Cream Sandwich (ICS) just before Jelly Bean http://en.wikipedia.org/wiki/Android_version_history#Android_4.0.3-4.0.4_Ice_Cream_Sandwich_.28API_level_15.29
Didn't even notice the custom ROM, DOH!
Titanium backup your apps and data, save onto PC, flash back to stock ROM, flash back to stock recovery, update software, flash custom recovery, create nandroid backup of new stock setup, check for custom ROM that supports the new JB and flash it (if you screw this up you'll appreciate the nandroid backup), see if you can use your Titanium backup to restore your apps and data.

Do these fastboot commands
Fastboot oem readcid
Fastboot getvar version-main
Lets see what we can do !

bro really appreciate your reply but to be very honest am just beginner as far as android is concerned and literally i didnt get what you said :s can you please kindly tell me step by step please. and one more thing its there any chance for demage or something if i go for flash or something, its my 1st android cell

m19990 said:
bro really appreciate your reply but to be very honest am just beginner as far as android is concerned and literally i didnt get what you said :s can you please kindly tell me step by step please. and one more thing its there any chance for demage or something if i go for flash or something, its my 1st android cell
Click to expand...
Click to collapse
If you follow us the chance of breaking things are very . . very small
Oke install the HTC drivers
http://db.tt/gXVxa3Dp
Download these fastboot files
http://db.tt/ldx3qOOU
Put the fastboot files in a folder like this
C;\fastboot\fastboot files from my link
Now hold the power button and the volume - button together untill it restarts into the bootloader. Don't let go of the two buttons untill you are in it !
Connect the phone to the pc and check if you see on the phone
FASTBOOT USB
then open a command prompt inside the fastboot folder on the pc (right click in the folder and open command prompt here)
Type this
Fastboot devices
If your serial pops up its good and then you also do the 2 other commands i gave you a post earlier
Edit: the chance of damage is so small because there is no s-off for our devices. Practically the only way to brick the device is if you flash stuff that is not ment for out HTC one x !

yes i performed all 3 commands but first tell me how to reopen my cell from fastboot usb

You can type
Fastboot reboot
Or unplug the cable and navigate with the volume buttons to REBOOT .... maybe you have to press HBOOT once to see the REBOOT option on screen
Confirm with the power button the action you choose
What was the outcome of the commands

ok what i get
fastboot devices
ht241w125067 fastboot
oem
<bootloader> debug: cid: htc__001
okay <0.016s>
finished. total time .016s
now tell me i did it fine ?

m19990 said:
ok what i get
fastboot devices
ht241w125067 fastboot
oem
<bootloader> debug: cid: htc__001
okay <0.016s>
finished. total time .016s
now tell me i did it fine ?
Click to expand...
Click to collapse
Yes fantastic and the
Fastboot getvar version-main
What comes out from that ?

Mr Hofs said:
Yes fantastic and the
Fastboot getvar version-main
What comes out from that ?
Click to expand...
Click to collapse
its same finished in .016s

A number should come out like
2.17.***.** if you do that command

Mr Hofs said:
A number should come out like
2.17.***.** if you do that command
Click to expand...
Click to collapse
1.29.***.**

m19990 said:
1.29.***.**
Click to expand...
Click to collapse
Lol ... Tell me the whole number

Mr Hofs said:
Lol ... Tell me the whole number
Click to expand...
Click to collapse
bro i got restarted and unfortunately close my prompt so as far as i remember is 1.29.40----- something

should i perform again ???

Download this RUU
http://androidfiles.org/ruu/securek...Radio_2.1204.135.20_release_274900_signed.exe
charge the batt to 100% before you start this
Put the phone in fastboot usb mode and open the fastboot prompt on the pc, relock the bootloader
Fastboot oem lock
Keep the phone in fastboot usb mode with the locked bootloader and right click the RUU.exe file on the pc and select
Run with administrator permissions (or a similar option)
It will flash your phone to completely stock ICS android. Then you can manually check for the JB update and install that too !
Note : it will wipe the entire phone. Do backup things if you need it !!!!

[Q] Red Triangle and Exclamation point - won't boot and PC won't recognize

I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you

Look at the following thread, may be this can help
http://forum.xda-developers.com/showthread.php?t=2662787
Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse

Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2

Just a little more info Gizmoe please
Gizmoe said:
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2
Click to expand...
Click to collapse
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.

Dugoutdog said:
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.
Click to expand...
Click to collapse
Can you send fastboot commands like
Code:
Fastboot devices
And see your device listed?

PS: to above
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).

Dugoutdog said:
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).
Click to expand...
Click to collapse
Did you read my other post. Can you confirm if you have fastboot connectivity? RUU mode is a command not a list option.

gizmoe
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.

Dugoutdog said:
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.
Click to expand...
Click to collapse
You have connectivity then. It's not going to list it in " my computer" unless its booted into Rom. Just use this thread
http://forum.xda-developers.com/showthread.php?p=46286588
To flash RUU. Don't do relock or s on just flash the stock RUU.

This is where I'm lost again
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.

Dugoutdog said:
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.
Click to expand...
Click to collapse
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.

my sub-directory
Gizmoe said:
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.
Click to expand...
Click to collapse
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.

Dugoutdog said:
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.
Click to expand...
Click to collapse
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621

now waiting
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Waiting for download to finish and getting ready for work. It will be close to see if I get it done before I have to leave. If not will finish at 3:00am when I get home and get back to you either way.

almost home
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.

Dugoutdog said:
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.
Click to expand...
Click to collapse
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.

Command Error
Gizmoe said:
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.
Click to expand...
Click to collapse
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.

Dugoutdog said:
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.
Click to expand...
Click to collapse
First type fastboot devices and make sure its connected. Phone needs to be in fast boot mode. Screen should read fastboot usb in red letters. Then type exactly
Fastboot oem rebootRUU
Then
Fastboot flash zip RUU.zip
RUU.zip needs to be in the same directory cmd is reading.

Something is happening . . . . . "sending zip"

resent as failed like you said.
failed as you stated . . . resent. It also said failed resend immediately. something is gyrating.
OK. at bottom of command prompt it says "Successful OKAY 249.248s" Finished total time 312.192 sec.
My phone has HTC in white small letters and a solid green bar below it.
Before I screw anything from this point, what do I do now? Just press the power button?