[Q] Relocked bootloader, won't boot into Rom - AT&T, Rogers HTC One X, Telstra One XL

This is going to sound like an odd problem but all I can get to is the bootloader and fastboot. Haha. I feel like that's different from most threads here.
I'm selling my One X (AT&T) soon and wanted to get rid of my custom rom (CM10) and put it back to stock. I a stock rooted 2.20 rom (flashed boot.img then the zip) and thought everything would be fine. I locked the bootloader through fastboot (fastboot oem lock) and rebooted. Here's my problem: the phone won't ever actually boot into the rom installed after relocking the bootloader.
As far as I have read, I can't run the RUU if I can't boot into the rom. Every time I try to reboot or shut down then power on again, I just end up back at the bootloader. I can access fastboot but I don't think any of the commands can help me.
Btw, I can't get to recovery either, if that's any help. It just goes back to the bootloader again.
Any help would be great. Thank you and have a nice day!

You actually need to be in the bootloader to run the ruu, that is normal behaviour.
Sent from my HTC One XL using xda premium

johnnywendy said:
I locked the bootloader through fastboot (fastboot oem lock) and rebooted. Here's my problem: the phone won't ever actually boot into the rom installed after relocking the bootloader.
Click to expand...
Click to collapse
That is what is supposed to happen. Once you relock, you have to run the RUU.

Tried it, it won't work
iElvis said:
That is what is supposed to happen. Once you relock, you have to run the RUU.
Click to expand...
Click to collapse
Thanks for the input! I've tried running the RUU on my Windows PC while the phone is both in fastboot and bootloader yet the RUU failed to connect to my One X. In some of the videos that I've found, once they relocked their bootloader, their phone would reboot into the rom. So is that not what's supposed to happen?
I've also seen some threads where people flash the RUU but it's for other devices. Is there a way I can do that? So while I'm in fastboot or something, I can just use the command line.
Thanks again!

I was able to just run the ruu on my pc while connected via fastboot usb. I'm not sure that the ruu is intended to be run from any command line, so you'll probably want to double check that your phone is connecting to your pc properly before you run the ruu. That's the only thing I can think of at this point.
Sent from my HTC One X using xda app-developers app

Error[170]: USB Connection Error
Skeeterdrums said:
I was able to just run the ruu on my pc while connected via fastboot usb. I'm not sure that the ruu is intended to be run from any command line, so you'll probably want to double check that your phone is connecting to your pc properly before you run the ruu. That's the only thing I can think of at this point.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
When I run the RUU, I run in to this error:
"Error[170]: USB Connection Error. The Rom Update Utility cannot connect to your Android device." I'm not sure why I'm getting that.
I was on 2.20 before I rooted my phone, not sure if that changes anything.
I'm not sure if this is what you're talking about but when I go to the command line and type "fastboot devices" it acknowledges my phone so I feel like it is connected. Right?
Thanks!

IT'S ALIVE
I just wanted to say that I got it to work. In case anybody has the same problem as me, all you need to do is install the latest HTC Sync on your computer. Plug in your phone and go into fasboot mode. From there, just run the RUU on your phone and everything should work.
Thanks for everybody's help!

johnnywendy said:
I just wanted to say that I got it to work. In case anybody has the same problem as me, all you need to do is install the latest HTC Sync on your computer. Plug in your phone and go into fasboot mode. From there, just run the RUU on your phone and everything should work!
Click to expand...
Click to collapse
That's correct. Your PC has to have the latest HTC drivers installed in order to communicate with your phone.

Do you have to flash the boot.img separately like when flashing a rom? Or does the RUU take care of the whole thing?

The RUU basically puts your phone back to exactly how it was when you bought it

Related

Broken One X

Quite recently I received HTC One X at&t, I unblocked the loader this way http://forum.xda-developers.com/showthread.php?t=1734558, but there was a failure and I lost the original files. Phone ceased to be loaded, and only was in cyclic reset. I tried to stitch an original insertion, it was established, but phone everything also reboots. Then I thought that a problem in CID and the unblocked loader. I replaced the CID back with CWS __ 001, and blocked the loader. Tried to stitch once again, but changed nothing. Now I have phone which only enters into fastboot and I can't make anything with it.
Can prompt something? Thanks.
I think you should try a RUU
Sent from my unknown using xda premium
JakeOcn said:
I think you should try a RUU
Click to expand...
Click to collapse
I tried to flash successfully, but nothing changed, still does not boot
http://forum.xda-developers.com/member.php?u=4623496
Dromych said:
Quite recently I received HTC One X at&t, I unblocked the loader this way http://forum.xda-developers.com/showthread.php?t=1734558, but there was a failure and I lost the original files. Phone ceased to be loaded, and only was in cyclic reset. I tried to stitch an original insertion, it was established, but phone everything also reboots. Then I thought that a problem in CID and the unblocked loader. I replaced the CID back with CWS __ 001, and blocked the loader. Tried to stitch once again, but changed nothing. Now I have phone which only enters into fastboot and I can't make anything with it.
Can prompt something? Thanks.
Click to expand...
Click to collapse
can u even reach Hboot? i am sure u know how to. if u can reach that screen.. its fixable
if u cant ..mssg niceppl with u r problem .. talk to him .. he can help you out.. hopefully
i suggest you to claim warranty.. if u have it
Ruu will work just fine.
Change your cid back to 11111111 and relock your bootloader, fastboot oem lock, ruu:beer: pm me once Ruu is done and we get your imei n sn fixed up
Added- you probably have to change your imei, s/n back to factory also before inserting simcard. Get the info off the box and pm me
Sent from my EVO using xda premium
18th.abn said:
Ruu will work just fine.
Change your cid back to 11111111 and relock your bootloader, fastboot oem lock, ruu:beer: pm me once Ruu is done and we get your imei n sn fixed up
Added- you probably have to change your imei, s/n back to factory also before inserting simcard. Get the info off the box and pm me
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I do not have access to adb, do this: (
Dromych said:
I do not have access to adb, do this: (
Click to expand...
Click to collapse
Get adb then.
atticusmas said:
Get adb then.
Click to expand...
Click to collapse
How I can receive it?, I have the blocked loader, fastboot, native CID and native recovery, the RUU installation gives of nothing.
U need the ruu.exe that matches your device branding and firmware version. E.g. evita 1.85 or rogers 1.73. Download it to pc, turn phone to fastboot USB in bootloader, plug in to USB and double click ruu.exe file. Follow on screen directions.
Sent from my EVO using xda premium
Dromych said:
How I can receive it?, I have the blocked loader, fastboot, native CID and native recovery, the RUU installation gives of nothing.
Click to expand...
Click to collapse
Install the android sdk on your computer. Then you have adb
Sent from my One X using xda premium
atticusmas said:
Install the android sdk on your computer. Then you have adb
Sent from my One X using xda premium
Click to expand...
Click to collapse
I have not loaded the firmware, you know? Cyclic reboot, reinstall the RUU does not fix this problem
I installed this firmware RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed.exe, all going well, but the result is your phone does not boot. After an unsuccessful unlock
Have u tried booting after ruu, without unlocking bootloader?
Sent from my EVO using xda premium
I didn't understand exactly what you did..but if you can boot to hboot you can fix this..
1. first you need to have adb and fastboot installed and working correctly.
2. take out your simcard.
3. relock your bootloader, run command fastboot oem lock
4. run the at&t ruu since you changed your cid back to cws__001.
5. after ruu just let it boot, it should boot. if ruu ran correctly...
6. if you are able to boot, now go to the bootloader again check your imei sn and mb.
7. if above information are correct(matching your box), root your phone and supercid it.
8. run the tool again. follow instructions
niceppl said:
I didn't understand exactly what you did..but if you can boot to hboot you can fix this..
1. first you need to have adb and fastboot installed and working correctly.
2. take out your simcard.
3. relock your bootloader, run command fastboot oem lock
4. run the at&t ruu since you changed your cid back to cws__001.
5. after ruu just let it boot, it should boot. if ruu ran correctly...
6. if you are able to boot, now go to the bootloader again check your imei sn and mb.
7. if above information are correct(matching your box), root your phone and supercid it.
8. run the tool again. follow instructions
Click to expand...
Click to collapse
1 point. - I can not get access to adb
3-4. I locked the boot loader, and returned to the cid CWS_001
5. I flashed RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe
6. in the hboot, all my data is displayed correctly
7. ooops... phone restarts all the time on a white logo HTC, I can not boot system
Why can't you get access to adb?
You say your info is correct in hboot. So boot into hboot, plug your phone into your computer and run adb. Easy no?
cmaxwe said:
Why can't you get access to adb?
You say your info is correct in hboot. So boot into hboot, plug your phone into your computer and run adb. Easy no?
Click to expand...
Click to collapse
adb does not work in hboot.
Dromych said:
1 point. - I can not get access to adb
3-4. I locked the boot loader, and returned to the cid CWS_001
5. I flashed RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe
6. in the hboot, all my data is displayed correctly
7. ooops... phone restarts all the time on a white logo HTC, I can not boot system
Click to expand...
Click to collapse
the cid is cws__001 not cws_001
are you sure the ruu flashed without any problems?
did you installed htc_sync if not install it and ruu again
Sent from my HTC PH39100 using xda app-developers app
niceppl said:
the cid is cws__001 not cws_001
are you sure the ruu flashed without any problems?
did you installed htc_sync if not install it and ruu again
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes, Cid CWS__001, RUU flashed without problems, but does not fix the problem
drivers are installed
Dromych said:
Yes, Cid CWS__001, RUU flashed without problems, but does not fix the problem
drivers are installed
Click to expand...
Click to collapse
unlock recovery and flash a custom rom see if it can boot
Sent from my HTC One XL using xda app-developers app
niceppl said:
unlock recovery and flash a custom rom see if it can boot
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
How can I unlock the recovery? I have locked bootloader
I can not flash a custom recovery via fastboot

Help Please I can't get any T-mobile U.S, RUUs to work ?

followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
kirkcody said:
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
Click to expand...
Click to collapse
That's a tough one to nail down. Below is the stock recovery from the 1.84 t-mobile OTA. Maybe flash that and try the clear storage option.
Also, you might try doing the the Mainver Fix in the all in one tool kit. It's an option in the box in the lower right hand corner.
https://dl.dropbox.com/s/g4r0ryvjy6oce9k/recovery.img?dl=1
Thankyou my friend ill give it a go
unfortunately that didn't work either...i don't know why this wont work for me
kirkcody said:
unfortunately that didn't work either...i don't know why this wont work for me
Click to expand...
Click to collapse
This same thing happened to me at some point. I would suggest just starting over and redoing all the steps.
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
If that doesn't work use a hammer and smash the thing =)
Actually instead of using a hammer I would change to super cid and use a different RUU that had the same hboot as the one your on.
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
@usaf22 really? Did that method work for you?(thought it may not work because we don't have s-off) Did it also remove the tampered and relocked banners? Thanks for both of you guys help will give it a go.
(Edit Hboot wont detect the PJ40IMG.zip )
usaff22 said:
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
No that won't work. Has it ever worked on the One S?
Didn't work Hboot didn't detect PJIMG.zip :crying:
kirkcody said:
Didn't work Hboot didn't detect PJIMG.zip :crying:
Click to expand...
Click to collapse
Did you try all this?
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
kirkcody said:
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
Click to expand...
Click to collapse
link no good-deleted
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Fixter said:
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Click to expand...
Click to collapse
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
dc211 said:
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
Click to expand...
Click to collapse
I got it working guys, but I know why. I was using the incorrect RUU. The link said it was the one for 1.83 but it was for the 1.5 version. I download it again and sure enough it's the 1.83 one. I guess I'm back to work now.
One question and this may save a big headache lol... did you LOCK your bootloader back? I had a couple RUU's that didn't work for me either, but I didn't follow the step of locking the bootloader I was just trying to flash over. Once I relocked I was good to go.
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
kirkcody said:
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
Click to expand...
Click to collapse
Your problem is that there is only 1 RUU you can use. Only 2 exist for T-mobile US and one you can't use because the hboot is lower then yours. But you're kinda lucky that a new OTA came out today. So a newer T-mobile US RUU should be out in a few days, that's normally how long it takes football to get them.
Here's a link to eh 1.83 RUU that should be fast. https://dl.dropbox.com/u/76257867/RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
Our you can try to get the OTA. You should be able to see it now if you check for software updates but it should fail to install. I saw you're using the 1.06es radio. You'd have to go back to the original radio, recovery, lock the booloader and factory reset. For it to work.
I know you should be able to get it working I was stuck where you're at but my Hboot also said "Security Warning" and RUU's & OTA's wouldn't run which I really haven't seen anyone else get.

[Q] Relock, RUU, Start Over?

Hi everyone,
I feel kind of bad for asking such a generic question like this, and I assure you that I have read around and done my research, but before I do potentially dangerous, irreversible, things to my device, I just want to make sure that I will perform the necessary steps correctly.
Basically, I have owned my HOX since launch date, and it came with either 1.73 or 1.85 base. As such, I rooted and unlocked the bootloader as soon as the exploits were available, and have been comfortably flashing ROMs and kernels every since. However, I have been experiencing some issues with data connectivity and stuff, issues that remain with any ROM, kernel, or radio that I flash. The details aren't important...
Now, I want to basically "start over" with my HOX. As if it was a brand new, unmodified, fresh device. So basically, unroot, relock bootloader, RUU, etc... And then start all over, root, unlock bootloader, install recovery, etc.....
Basically, what exact steps do I need to take to accomplish the "starting over"? As in the methods to use, the RUU to use, etc... ?
An outline of the steps, basically. My biggest fear is restoring to the wrong thing and losing my old HBOOT.
Again, I know this question probably gets asked often, but please bear with me through this.
I ruu'd my wife a and it was about 3 weeks before att sent her the next update lol. As long as you don't accept it you'll be fine. I'm sure you'd prolly root as soon as its finished anyway..
But you got it right. No need to unroot, just fire up fastboot and enter "fastboot oem lock". (Without quotes)
Figure out which ruu you need, most likely 1.85. Make sure you have the right HTC drivers updated, and make sure HTC sync is working right. Download ruu, which is an executable application, and run it. It should factory restore your phone like the day you bought it.
As far as restoring to the "bad" hboot, it shouldn't let you complete an ruu that's for another firmware other than what you had on it when you got root... So you'll be safe. Good luck bro, come back and let us know how it went :thumbup:
Sent from my One X using Tapatalk 2
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone?
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me?
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally?
And also, once I relock my boot loader, should I immediately RUU?
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
?
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU?
And after I relock the bootloader, will the phone reboot out of fastboot or anything? Or should I go immediately from the relock phase to the RUU phase?
Thanks
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Yep.. Run it from anywhere, as long as your computer recognizes your device let us know how it goes
Sent from my One X using Tapatalk 2
Ok, thanks a lot.
I don't have a PC with me right now (mac user) but once I get the opportunity I will go through with this. Thanks again!
Im hoping this thread may help me to solve my problem (I'm a total noob too lol)
I rooted and flashed a Rom on my HTC One S, and I had the same issues as OP
Im with Fido, but I was told that both Fido and Rogers use the same RUU
Trying to go back to stock, I relocked the bootloader.
1. then I ran the RUU (found a tutorial online), but I got an error message (155: wrong RUU or file cant be larger or something like that)
2. then I tried an alternative method : extract 2 files from the RUU, move them to another folder and from there run a cmd; didnt work either
(By the way, in method number 1, I also had to flash a recovery file (stock recovery) during the bootloader unlock process)
Did I do it the right way?
Can some Senior member give me a detailed step by step method?
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
Yeah.
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
I did ???
Hey what do you know :laugh:
I have tried to do this multiple times, but no matter how many times a run the 2.2 exploit, and flash the unlock code bootloader continues to say relocked? any ideas
Yes, you need to check your pm. You need to hard reset the device. Hold power until device reboots, capacitive keys will flash during the process. Then run the unlock and you're device will unlock. I spent a full day to figure this out... Lol
Sent from my HTC One XL using Tapatalk 2
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Behemyth said:
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Click to expand...
Click to collapse
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
ECEXCURSION said:
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
Click to expand...
Click to collapse
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Behemyth said:
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
scroll down to the stock ruu section and look up the firmware 2.2 not the hboot 1.14
Well, I'm the OP, and I ended up figuring out what RUU to use, which was 1.73. Basically, I ran 'fastboot oem lock' , then ran the RUU right afterwards, then booted up and ran the root exploit, rooted, and then ran 'fastboot oem unlock' using my old Unlock.bin file that I had from the very first time I unlocked the bootloader. From there, I installed a custom recovery and was good to go.
Yah, if your using 2.20 firmware, run the below link, works like a charm. Must make sure you re-lock the bootloader before, or it will error out. Just hold down the power button until it turns off if this happens.
possible brick
Skeeterdrums said:
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Click to expand...
Click to collapse
I did this, but my phone never boots. It just stays at the bootloader after i run the RUU. Any ideas? :/
Also, i get the "this build is for development purposes only" message under the HTC logo before the phone enters the bootloader.
EDIT: managed to get the bootloadr unlocked again via HTCDev.com and flashed recovery and ROM. Guess Im not starting fresh after all lol

[Q] RUU question

Going to RUU to 3.18 but I need to make sure of some things.
From what i've gathered since I'm S-Off I do not have to relock the bootloader. But since I'm running Vanilla Root-Box do I RUN the RUU while in fastboot or do I just run it while fully booted up or do I wipe everything in recovery then do it through fastboot?
c0d_fish said:
Going to RUU to 3.18 but I need to make sure of some things.
From what i've gathered since I'm S-Off I do not have to relock the bootloader. But since I'm running Vanilla Root-Box do I RUN the RUU while in fastboot or do I just run it while fully booted up or do I wipe everything in recovery then do it through fastboot?
Click to expand...
Click to collapse
run while in fastboot. nothing else is required.
exad said:
run while in fastboot. nothing else is required.
Click to expand...
Click to collapse
Thanks exactly what I needed to know
You will need to downgrade the TP firmware and reflash recovery afterwards.
GaBuzz said:
You will need to downgrade the TP firmware and reflash recovery afterwards.
Click to expand...
Click to collapse
Yeah I'm all set thanks, I just needed to know about the fastboot thing. Already finished doing everything.
You don't have to be in fastboot to run the RUU. As long as the screen of the phone is on, it doesn't matter what mode (bootloader, flastboot, fully booted), the RUU will run. This is by design, as the RUU is intended as a recovery tool.
Ruu never works for me unless I'm in fastboot.
I always get a random generic error.
Sent from my HTC One X using xda app-developers app
That's odd. I don't think I've ever had to go into fastboot to run the RUU.

[Q] Desire S flash without Fastboot USB

Hello xda-developers Boardusers ,
ive got an HTC Desire S and wanted to flash it..
The CWM is installed but since then i cant conntect it to the PC anymore.
Maybe its the USB-Port of the Phone..
Is it possible to update my ROM without Fastboot.. The Phone is S-ON and got an T-Mobile Branding.
I tried to update the ROM but then it stops booting at the T-Mobilelogo.
And if i extract the RUU 4.0.4 and rename it on the SdCard to PG88IMG.. It starts to load but.. But it wont let me flash it because when its finished with loading it just go back to the Mainmenu.
I would really appreciate your help.
Silberpfote said:
Hello xda-developers Boardusers ,
ive got an HTC Desire S and wanted to flash it..
The CWM is installed but since then i cant conntect it to the PC anymore.
Maybe its the USB-Port of the Phone..
Is it possible to update my ROM without Fastboot.. The Phone is S-ON and got an T-Mobile Branding.
I tried to update the ROM but then it stops booting at the T-Mobilelogo.
And if i extract the RUU 4.0.4 and rename it on the SdCard to PG88IMG.. It starts to load but.. But it wont let me flash it because when its finished with loading it just go back to the Mainmenu.
I would really appreciate your help.
Click to expand...
Click to collapse
I think you have to be s off for that or unlocked boot loader which requires PC connection.
Sent from my Desire S using XDA Free mobile app
lilsafbig said:
I think you have to be s off for that or unlocked boot loader which requires PC connection.
Forgot to say that my Bootloader is unlocked too
Click to expand...
Click to collapse
Silberpfote said:
Forgot to say that my Bootloader is unlocked too
Click to expand...
Click to collapse
the ruu dont work Because ur bootloader is unlocked. u need to relock ur bootloader using fastboot commands before a ruu will run.
how do u charge ur phone if usb dont work??
jmcclue said:
the ruu dont work Because ur bootloader is unlocked. u need to relock ur bootloader using fastboot commands before a ruu will run.
how do u charge ur phone if usb dont work??
Click to expand...
Click to collapse
Charging accually works.. But the Phone wont go into "Fastboot USB".. So im unable to Relock it. Or is there a posibility to Relock it using the CWM?
A Custom Rom would be fine too.. And i tried on and installed it with the CWM. But it stops booting at the Tmobilelogo.
I tried a Goldcard to with the CID TMOB101 but that didnt worked as well.
But dont know if this acually the right CID. I found this one on the internet.. Is there a way to find the CID without fastboot?
Silberpfote said:
Charging accually works.. But the Phone wont go into "Fastboot USB".. So im unable to Relock it. Or is there a posibility to Relock it using the CWM?
A Custom Rom would be fine too.. And i tried on and installed it with the CWM. But it stops booting at the Tmobilelogo.
I tried a Goldcard to with the CID TMOB101 but that didnt worked as well.
But dont know if this acually the right CID. I found this one on the internet.. Is there a way to find the CID without fastboot?
Click to expand...
Click to collapse
Oh rite. So use link below to setup fastboot and install drivers.
http://forum.xda-developers.com/showthread.php?t=2588979
Once thats done, reboot pc. Then boot ur phone into fastboot mode and plug it into pc, hopefully will say fastboot usb.
The reason a custom rom does not boot is because ur s-on u need to flash the boot.img inside the rom via fastboot commands. So either way we need fastboot working!! That tool above is very good
Make sure its not ur USB cable thats gone.
Sent from my Desire S using XDA Free mobile app
I tried it but i still only get "Fastboot AC".. I will try it later with a Linux
How about flashing the boot.img with the Backup option from the CWM --> http://forum.xda-developers.com/showthread.php?t=1991168
Does it work?
Would like to install the "Desire XS 1.1" Custom Rom..
And another Question.. Can i always enter the Recovery.. Because after i flashed this Custom Rom it asked me at the end to flash the boot.img if im not S-Off so i was a little bit scard and flashed my backup without turning off

Categories

Resources