I bought a Desire S off eBay. It had Froyo Orange UK on it.
Yesterday I started flashing it (whilst having a couple of drinks!)
I got it to S-OFF, got Revolutionary working and had a rooted Gingerbread ROM on it, but I cant remember which variant.
I don't have an Orange SIM so I started using various methods to unlock the SIM, getting more frustrated and drinking more.
I read hudreds of threads (not too methodically) and eventually decided I needed S-ON so I have got it back to an S-ON state.
By this time I was drunk and cannot remember if it booted after I S-ON'ed it and therefore cant tell if I have USB Debugging enabled.
I think the bootloader may be locked but it boots into the white HBOOT screen. There is no Recovery that works so I am stuck with a blank page.
If I try to RUU Orange UK or any stock ROM on it I get different errors half way through.
I have tried to flash a new HBoot onto it but get a signatire error in fastboot utility. Revolutionary no longer works.
I'm lost. I'm going for a walk!
You tried HTC unlock bootloader ? Then flashing a new recovery?
Sent from my HTC Desire S using Tapatalk
Maybe unlock it via htcdev.com, flash new recovery with fastboot
fastbooot flash recovery PathToRecoveryImg
...do it sober dude ^^
Well....first dont drink n flash.
Then try the following:
Flash a new recovery via android flasher.I suggest the 4ext touch.For me is the best out there.
Then wipe the device ccompleteley including cache ,data,system etc.
Then flash the rom you want.
After that reboot into bootloader and choose fastboot.
Extract the.same rom that you flash somewere in your pc.Copy the boot.img and paste it in you platform tools in sdk dir.
Open cmd.
Connect your device.
Assuming your sdk is to c:/ and named for ex android-sdk-windows then type.
Cd c:/android-sdk-windows/platform-tools
Fastboot devices(see if the device identified)
Fastboot flash boot boot.img
Done.
Then reboot your device
Hope that helps
don't drink and driv... ehm flash your phone! (or post in the wrong forum )
[email protected] said:
don't drink and driv... ehm flash your phone! (or post in the wrong forum )
Click to expand...
Click to collapse
+1 for that @apx
While i have all the sympathy for you @Nezbert, this is the wrong place to put your questions.
In case the alcohol hasn't metabolized completely, let me put it in clear loud words - "This is the Development forum... NOT the Question and Answer Forum. Your thread does not belong here. The Q&A thread is custom built for exactly these kind of threads"
Thread reported for relocation. I hope you understand.
Probably why he thinks he had froyo on it...
Sent from my HTC Desire S using xda premium
dan-fish said:
Probably why he thinks he had froyo on it...
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Might have been a super secret prototype by HTC R&D
Haha. All jokes aside, does the phone actually work? Maybe he pulled battery?
Sent from my HTC Desire S using xda premium
This sounds like exactly what I did mate, I believe it was a combination of incorrect goldcard and trying to install a foreign RUU -- which Revolutionary bootloader with S-OFF will allow.
check this thread: http://forum.xda-developers.com/showthread.php?t=1464513
I managed to solve it, but I needed to borrow a phone to do it. Check out my solution post on Page 2
Actually I might as well just tell you what I think will work here.
1. Borrow a friends android phone, any phone should do I believe.
2. Download Goldcard Helper from the market, use it to get the CIDs of the memory on your phone. One of these is the SD card, you might as well copy both down but for me MMC2 was my SD card. The app by default copies the other one when you use the Menu > Copy function, so don't use that. Go to the website and generate the goldcard.img file.
3. Use GoldCardTool (attached) to patch your SD card.
4. Pop it into the phone and boot to HBOOT and select fastboot again
5. If you've unlocked the HBOOT via HTCDev.com, lock it again before trying an RUU! If you don't have fastboot.exe it's in the ADB-Windows.zip attached... type "Fastboot oem lock" to lock the HBOOT.
6. Run the RUU for Europe - RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed worked for me
That should do it. Hope it does mate!
I just tried using the HTC Dev unlock bootloader site and at the first fastboot command I get:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.007s
The command was for 'fastboot oem get_identifier_token'
I know fastboot is connected because if I issue 'fastboot reboot' the phone reboots.
Looking at your other posts now. Thanks.
I'm gonna use my Sony Ericsson Xperia to download the goldcard app and try that. I'll report back in a bit. Fingers crossed!
FrakEarth, thank you!! Your advice worked to the letter!!
The only thing I didn't do was the fastboot oem lock part, as I couldn't get fastboot to work.
Now I am kind of back to square one. I have a working OS on an Orange UK phone but when I put my giffgaff/o2 SIM in there isa no prompt to enter an unlock code. I have bought a code that goes with my IMEI but I dont know how to enter it.
Is there an easy way to SIM unlock this?? I will search the site.
Thanks again FrakEarth!!
One more question...
Now that Android has booted and created all it's driectories on my SD card will it still be a Goldcard, or will it have been overwritten into a standard SD?
One more question!
Where do I click to edit the thread title to [SOLVED]?
Nezbert said:
One more question...
Now that Android has booted and created all it's driectories on my SD card will it still be a Goldcard, or will it have been overwritten into a standard SD?
Click to expand...
Click to collapse
I think that you still have the files needed for the GoldCard but don't bother, it's not something that will create any problems. As I recall my old SD Card when I used it as a Goldcard, I installed my desired Android RUU but there were still some files in the SD from the Goldcard utility.
Nezbert said:
One more question!
Where do I click to edit the thread title to [SOLVED]?
Click to expand...
Click to collapse
You select "edit post" in your 1st post and then select "Go advanced" and there you have it.
Drink less!
Are u sure? How possible u buy a desire s with froyo? It have gingerbread at first!
Related
**VIDEO AT THE BOTTOM!!**
Requirements
ADB: Click here for windows or Linux or download from) Sensation S-off guide
You Will Need HTC Drivers http://forum.xda-developers.com/atta...7&d=1312092669
*DO NOT ADD "" TO COMMANDS!!!
1. On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
2. Create a new folder called "adb" and extract the files from adb.zip (link above) into it. Make sure it doesn't create another folder in the adb folder when extracting
3. Install HTC USB Driver 3.0.0.007.
4. Press Windows + R, it will open Run. (linux users ignore this)
5. Type "cmd". (or open terminal on linux)
6. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode
7. On your phone, Go to Settings > Applications > Development > Enable USB Debugging
8. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
9. If it is recognized, then download your official RUU, please get the same/similar version that came with your phone. If you fail then you might Brick your Device!
10. Start RUU.exe and follow on screen commands.
11. After reboot, turn phone off without fastboot on, or, take out battery and then Hold Volume down button and power on.
12. Bootloader should now read Pyramid PVT Ship S-OFF RL.
13. Remove and reinsert the battery. Press power on as normal
Optional To change to stock S-ON
PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A SMALL RISK OF BRICKING
15. Boot up into the new ROM and On your phone, Follow steps 4-8 above then continue here
16. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja who came up with this)
17. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
18. Bootloader should now read Pyramid PVT Ship S-ON RL.
19. Remove and reinsert the battery. Press power on as normal
USE IF SEMI BRICKED
20. IF IT DOESN'T REBOOT and bootloader says ***Security Warning**
Remove and re-insert the battery and go back into bootloader and holding Volume Down +power button select fastboot
21. Run RUU.exe to reflash stock rom. (the one u just downloaded in step 1) and then reboot. It should work now
*NOTE*
This removes ROOT and custom recovery!!
I take No Credit for the Idea!
I am in no way responsible if YOU brick your phone!
If you want to add stock SuperCID AFTER you installed RUU.exe, Then Go Here For CID's, They Must Be Your Mobile Carriers... Ex: T-Mobile USA = (Carrier"TMUS") (CID"T-MOB010")
CID CANNOT BE CHANGED AFTER S-ON, it must be done while S-off
I added a video to download! you may need to re-record
http://www.mediafire.com/?ibn7168nd2ywr5d
Good Day to You and Good Luck!
Feel free to Comment for Help
If you need any help feel free to post comments
well thanks for this guide, but we're all hoping to never send our beloved Sensation in warranty return
Yeah, I would hate to send it in.
Read Me!
Everyone should do this and then reinstall custom recovery and root. Only because if sent to warranty and they see Revolution, you are screwed.
plocri said:
well thanks for this guide, but we're all hoping to never send our beloved Sensation in warranty return
Click to expand...
Click to collapse
Nice write up and VERY Noob friendly! I was reading through and in my head, half the time, going well duh. Then it clicked, you said Noob friendly. I think it will help almost all Noobs but there will be at least ONE that F's it up!
Again, nice write up!
setzer715 said:
Nice write up and VERY Noob friendly! I was reading through and in my head, half the time, going well duh. Then it clicked, you said Noob friendly. I think it will help almost all Noobs but there will be at least ONE that F's it up!
Again, nice write up!
Click to expand...
Click to collapse
Thanks, Its funny cause im a junior member and im writing NOOB friendly threads
Well was a junior member when i wrote this lol
Just to let you know if you stay with S-OFF HTC will now...
Hboot is a different version from HTC, it ends in 10xx rather than 00xx
So even if it doesnt say revolution, they still can tell
Best to restore to S-ON which is a bit risky if you dont follow instructions to the t..
Cheers
P.S. Also why are you giving SuperCid since everyone will need to flash their Stock RUU anyway?
broncogr said:
Just to let you know if you stay with S-OFF HTC will now...
Hboot is a different version from HTC, it ends in 10xx rather than 00xx
So even if it doesnt say revolution, they still can tell
Best to restore to S-ON which is a bit risky if you dont follow instructions to the t..
Cheers
P.S. Also why are you giving SuperCid since everyone will need to flash their Stock RUU anyway?
Click to expand...
Click to collapse
nope my hboot is 1.17.0008, which is stock T-Mobile HBoot. And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
alphadog32 said:
nope my hboot is 1.17.0008, which is stock T-Mobile HBoot. And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
Click to expand...
Click to collapse
If it is stock hboot then you have missed all fastboot flash functionality that alpharev has put in their hboot.
Can you flash radio, splash and so on with this hboot you have now?
broncogr said:
If it is stock hboot then you have missed all fastboot flash functionality that alpharev has put in their hboot.
Can you flash radio, splash and so on with this hboot you have now?
Click to expand...
Click to collapse
Yes I can flash.
alphadog32 said:
And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
Click to expand...
Click to collapse
By encouraging people to install SuperCID, all you are doing is making their phone more traceable for tampering if it goes back for warranty, and allowing them to install the wrong RUU. If they don't have SuperCID, they'll get 'ERROR[131]: CUSTOMER ID ERROR' if they try to flash the wrong RUU and it will stop without flashing anything to the phone.
I know you're just trying to help, but all they have to do is run the latest released RUU for their region. Nothing more.
alphadog32 said:
Yes I can flash.
Click to expand...
Click to collapse
He means use 'fastboot flash' commands which you can't with the stock hboot.
Oh. I thought he meant ROM installing and installing root. Thank You.
Sent from my HTC Sensation 4G using XDA App
How do i know if CWM is removed?
Hi,
i did all the steps and get s-on back with stock rom.
my question is how do i know whether i have removed CWM as well? when i vol down + power, it went into bootloader. it's the same screen as when i have CWM installed. the only difference is the S-on, at least the ones i can recognize is different.
thx
here is what i need to know... i am actually getting and exchange and have to send this back in because the vibration stopped working. It as TMOUSA Sensation. So far here is what i have gathered about my phone:
Baseband/radio version: 10.42.9007.00u_10.11.9007.15_m
Build number: 1.35.401.1 cl84734
hboot: 1.17.1011
CID: T-MOB010
I looked at the http://forum.xda-developers.com/showthread.php?t=1074559 page and they listed two RUU for TMOUSA:
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
and
RUU_Pyramid_TMOUS_1.27.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_192098_signed
which one of these am i suppose to use? Will my baseband/radio be updated to a different band/radio?
radiikal said:
Hi,
i did all the steps and get s-on back with stock rom.
my question is how do i know whether i have removed CWM as well? when i vol down + power
thx
Click to expand...
Click to collapse
i will try to answer ur question.. after u went thru all the process to get s-off with the idea of installing custom roms using CWM, u will get into recovery with the steps power+vol down them u scroll down and pick recovery taking u to CWM..try now and it should take u to stock recovey, after u finally figure it this out by ur self..im pretty sure u will feel like u can conquer the android world..
Pick 1.29.xxx.x for TMOBILEUSA
HTC Sensation
RESTORED TO S-ON
STOCK HBOOT
STOCK ROM
ROOTED
Is this safe?? im planning to remove my superuser,root,CWM but keep S-OFF because im tired of worrying that my phone will die when i'm out and i won't be able to charge it
If you mess up, you may brick your device!
AFTER i DL the RUU, where do i paste it at?
CWM/S-Off/Root/Supercid for HTC Sensation making
problems with T-Mobile Branding
The procedure made it necessary to unlock the boot loader at the page HTC Dev.
The unlocker for HTC Dev boot loader and a fine step-by-step instruction can be found
here:
http://htcdev.com/bootloader/
unlock: fastboot flash unlocktoken Unlock_code.bin
lock: fastboot oem lock
After unlocking the boot loader, you have to deploy Clockworkmod Recovery.
I deployed the CWM-Image in fastboot mode. Boot the mobile in the boot loader and
choose fastboot (switch off the mobile, press and keep pressed Vol down, switch on the
mobile and keep both of them pressed until you are in the boot loader).
To keep things simple, copy the file https://rapidshare.com/files/3526334....4-
pyramid.img into the folder Android SDK containing the fastboot file on your PC, open
the window ‚execute‘ using the keys windows+R, there type in cmd and press the enter
key to start a Dos-Box, and type in the command fastboot flash recovery cwm-4.0.1.4-
pyramid.img into the Dos-Box.
As the boot loader now is unlocked and CWM is deployed, now we can store back a
backup using CWM restore. I used this one:
https://www.rapidshare.com/files/171...2.32_GRJ22.rar
My heartfelt thanks to FlolB and HD2neuling for creating and uploading this and to
JamSam for this bright idea! =)
After downloading the backup you copy the unzipped folder to the SD card into the
folder \clockworkmod\backup\ you find on the SD card. If it is not already present you
might have to create it manually. On my device this looked as follows:
\clockworkmod\backup\2011-12-27.11.02.32_GRJ22
Please make sure to use the unzipped file! The zipped one won’t do!
Reboot the mobile into the boot loader and there choose Recovery. The mobile will start
into the CWM. First we execute a Superwipe. Install the zip file (
https://www.rapidshare.com/files/413..._Sensation.zip ) as you do with a CustomRom.
All bothersome remaindes of the old OS should be gone now. Then open „Backup and
Restore“ and choose the option Restore and as destination the backup folder on your SD
card.
CWM now is loading the backup to the mobile. Once CWM has finished loading, you
can boot the Android. The first start however does take some time. Don’t panick.
If so, and if I did not totally lose track with all that troubles, you can get S-off as before
using the Revolutionary tool, root the mobile, and write a supercid.
Detailed instructions you can find here:
[Anleitung] Root | S-OFF | flashen eines Custom Rom für's Sensation (German version)
Special THX to teivos and androidsense from pocketpc.ch
We worked a view days together to manage and solve this small problem, caused of that f...ing T-Mobile-Branding....
In our Forum, we checked some T-Mobile-Sensations and there were all glad to see, that this Howto functions very well
Over 220 visits, and no reaction??
tapatraced with Sensation XL
I've have never ran the super cid to change it to ones or something but I've never had a problem installing any Rom on here. I am s off from the revolutionary way. I have a tmobile branded sensation.
Happy New Year XDA members.
Which Stockrom did you had?
TapaSwyped with SGT
I had got it with 2.3.3 then upgraded to 2.3.4 then rooted and s off after that.
Sent from my GT-i9100 using xda premium
I will have to look at my girls phone cause she has the same phone and just did the recent update but other than that she isn't s offed. I don't know how to adb so I didn't even mess with that.
Sent from my GT-i9100 using xda premium
I wonder, that you have S-Offed....cause thats not possible these days...
I have ship S-off, cause its a pre-release phone....
tapatraced with Sensa XL
Thanks interesting method how to do it.
jammysunny said:
Over 220 visits, and no reaction??
tapatraced with Sensation XL
Click to expand...
Click to collapse
Thank you for your effort it help me a lot. Normal method doesn't work for me.
Finaly I rooted that bastard...
Your talking about the xl I just have the 4g. Oops
Sent from my HTC Sensation XE with Beats Audio using xda premium
Yeah, oops
In our Forum, we helped lot of users with this method....
Tapaswyped with Galaxy Note
Honestly, most users here are already s off that's why there is so little buzz on this thread.
Yeah, I had no problem s-offing and flashing ROM's to my t-mobile branded sensation the revolutionary way.
Sent from my HTC Sensation 4G using XDA App
I think, only the newest Sensations have Problems...
Tapaswyped with Galaxy Note
CWM actually worked! But the links are not working... Forum shows just a cuted version and rapid says there's no such of file. Plz give me full links.
I check it after work...
Tapaswyped with Galaxy Note
The links from the first post are not working
Here are working links:
https://rapidshare.com/files/3526334401/cwm-4.0.1.4-pyramid.img
https://www.rapidshare.com/files/1710868136/2011-12-27.11.02.32_GRJ22.rar
https://www.rapidshare.com/files/4137058150/Android_Revolution_HD_Super_Wipe_Sensation.zip
http://www.pocketpc.ch/htc-sensatio...s-off-flashen-custom-rom-fuers-sensation.html
when i wanna install the asia rom, the power down, and i reboot my phone , now is all black screen, i cant open my phone now, i m with rogers htc one x, how can i do ?anyone can help? Now my phone has no any ROM inside
help
Power on and hold volume down. Select fastboot. Install new Rom.
Also I would suggest not using SuperPatchef as it is not completely stable yet.
Sent from my HTC One X using xda premium
ForcedZucchini said:
Power on and hold volume down. Select fastboot. Install new Rom.
Also I would suggest not using SuperPatchef as it is not completely stable yet.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
how to install new ROM in fast boot ? any ROM i can flash?
Look in Development forum for a Rogers RUU. Just follow the instructions in the . exe.
Sent from my HTC One X using xda premium
ForcedZucchini said:
Look in Development forum for a Rogers RUU. Just follow the instructions in the . exe.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
But i cant get into the system to open the usb debugging, so i cant use superpatch , i can only use fastboot. Can it be using in fast boot?
In fastboot, execute the RUU.
lilhyper said:
In fastboot, execute the RUU.
Click to expand...
Click to collapse
i dont know how to do it, could u show me how to ?thx very much
when the phone is off...
hold VOLUME DOWN, then press the power botton
then run RUU, it should work
ytwytw said:
when the phone is off...
hold VOLUME DOWN, then press the power botton
then run RUU, it should work
Click to expand...
Click to collapse
any RUU file i can download this forum?
I love how people leap before they look. Christ, always have a way back to stock plan before jacking with your $600 toy
Sent from my HTC One XL using Tapatalk 2
help needed.
cao0215 said:
help needed.
Click to expand...
Click to collapse
There's an entire dev section you could have read by now. Stop looking for handouts and fix your [email protected]#
Sent from my HTC One XL using Tapatalk 2
cao0215 said:
Click to expand...
Click to collapse
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
OT, but it is good to see you with a One XL PG. From someone who remembers the Craptivate days...
Sent from my HTC One X using XDA Premium HD app
Pirateghost said:
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
/excited standing ovation!
Pirateghost said:
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
i just flash recovery into my phone , and use superpatch to flash asia ROM, but the power is dead, so the rom is not install completly, and then i get into the recovery and format the /system. Now my phone is only allowed to fast boot, and i m wondering to get the STOCK ROGERS RUU,but it's .zip , is there any way i can flash stock rom ? i m searching and go to dev section for the whole day, i m still not get the anwser.
cao0215 said:
i just flash recovery into my phone , and use superpatch to flash asia ROM, but the power is dead, so the rom is not install completly, and then i get into the recovery and format the /system. Now my phone is only allowed to fast boot, and i m wondering to get the STOCK ROGERS RUU,but it's .zip , is there any way i can flash stock rom ? i m searching and go to dev section for the whole day, i m still not get the anwser.
Click to expand...
Click to collapse
a whole day? really?
know what i found in about 2 minutes?
http://forum.xda-developers.com/showpost.php?p=25926794&postcount=39
Total recovery - flashing a RUU to completely restore your phone
If all else fails, this is your last resort.
This process will also erase all your data. But hey, beats having a dead phone, right?
First, ensure you have enough battery (more than 30%) to run an RUU.
Next, boot your phone into fastboot bootloader and open a command prompt window on your computer in the platform-tools folder.
Use the command:
fastboot getvar version-main
You now need to find the RUU that corresponds to this version. Start here. If you have problems visit #htc-one-x on freenode.
Now you must re-lock the bootloader using:
fastboot oem lock
It won't hurt to use the clear cache command as well
fastboot erase cache
Finally, run the RUU.exe that you have downloaded (must be used in Windows, and requires HTC drivers, which will have been installed whilst using HTCDev to unlock your phone).
This will write the /recovery, /boot, and /system to stock. You will need to start from scratch to unlock.
[edit]Extracting RUU if you have errors with the above method - Originally by torxx
Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working.
Many people have issues with flashing RUU's etc. having a bootlop.
Download a RUU (make sure you get the correct RUU, please see above)
Now open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
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)
Plug in your One X, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
fastboot flash boot boot_signed.img
fastboot flash system system.img
If everything worked, just reboot:
adb reboot
Click to expand...
Click to collapse
http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
seriously man....if you arent ready to LEARN what you are doing to your phone then you need to back the hell off.
3 options:
stay stock
learn what you are doing
buy an iphone
Pirateghost said:
a whole day? really?
3 options:
stay stock
learn what you are doing
buy an iphone
Click to expand...
Click to collapse
Could not agree more. Please READ the dev forums in detail before trying to do ANYTHING to your phone. Understand what you are doing before diving in.
Staying stock seems to be the best option for you. I know English is not your first language, which is fine; it's not my first language either. Reading all the development stuff can be challenging, but it's more dangerous to venture in this world unprepared.
The HTC One X is really very usable out of the box. Just use it and don't try anything funny.
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
you are lucky to have white screen
You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium
xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.
vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...
xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.
can anyone please help
Where can I get stock recovery, stock boot for the phone?
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^
thanks for the reply, however ur link is broken.
And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??
Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though
xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up
I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app
Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.
So I've read a few things on the forum about signal drops and have tried a few solutions but I wanted to get some additional feedback before I go the ATT:
Just in the past few days, I have had increasingly frequent signal drops. This has become really annoying for me, as it always seems to happen when I am using mobile data or sending a text message. The signal drop is transient and only lasts about 30 seconds before it re-connects to my network. I haven't noticed much correlation with when it actually happens but I have attached a picture just so you all can see how frequent these signal drops are. Happens when phone is asleep or in use. These are the things I have tried:
1) Originally was running KingCobra 1.5 and thought it may have been the ROM so I flashed CM10
2) Flashed radio 2.09 for ATT - this showed no improvement / did not make it worse
3) Wiped cache / Dalvik - no improvement
My next course of action was to go to ATT and get a new SIM card. Is it possible that a faulty SIM over time could cause this? And would replacing the SIM likely help in the experience of this community?
Thanks a lot for the input, and if there is something else I can do that I haven't already tried please let me know!
Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.
redpoint73 said:
Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.
Click to expand...
Click to collapse
Can this sort of thing spontaneously happen? One day the SIM just starts getting derpy?
I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app
area51avenger said:
I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Well I got a new SIM from AT&T and I'm still dropping signal. They did say that they just put up LTE towers here where I'm at 2 days ago, which, coincidentally is when I started getting signal drops. I suppose all that is left is for me to RUU? I don't know how to so it should be fun reading up lol
Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Edit: Could someone enlighten me a little bit on the process of the RUU -- The only thing that is cloudy here is that I am currently running CM10, would I be able to run the executable RUU if I was running a stock odexed/deodexed ROM after re-locking the bootloader? I have looked at this (http://forum.xda-developers.com/showthread.php?t=1814217&highlight=ruu) and the associated guide but this all assumes that I'm already on a stock image right? I've tried doing some reading but I am drawing a blank on the RUU process
TheEmpyre said:
Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Click to expand...
Click to collapse
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2
superchilpil said:
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?
TheEmpyre said:
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?
Click to expand...
Click to collapse
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2
superchilpil said:
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Edit: Forgot that when you unlock bootloader you do it through fastboot with "fastboot flash unlocktoken Unlock_code.bin so ultimately I would be able to re-flash my recovery etc
TheEmpyre said:
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Click to expand...
Click to collapse
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token, flash twrp, and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2
superchilpil said:
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file
TheEmpyre said:
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file
Click to expand...
Click to collapse
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2
superchilpil said:
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen
TheEmpyre said:
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen
Click to expand...
Click to collapse
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2
superchilpil said:
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?
What my screen looks like here before and after selecting bootloader with the power button
Sent from my Nexus 10 using Tapatalk 2
TheEmpyre said:
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?
Click to expand...
Click to collapse
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
alright, in fastboot run fastboot oem rebootRUU
then run the ruu.exe
superchilpil said:
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
Click to expand...
Click to collapse
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected
TheEmpyre said:
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected
Click to expand...
Click to collapse
try my method above, ive tried it with fastboot... the ruu just ignores it
That method should work, the ruu should pick it up and wipe it clean