Related
I bought an att htc one x from someone else. The phone is rooted,and the bootloader in unlocked. it is running:
Nocturnal xi40 115
4.0.3 Android v
3.0.8-01158-g3d3f08d [email protected] #1
smp preempt (Kernel)
0.17a.32.09.24_2_10.91.32.19L (baseband)
1.88.707.2 cl64928 (build)
How do i get this phone back to stock? I want the phone to be on stock sense. I have searched but, i cant figure out how to revert back. Thank you for your help.
lakas187 said:
I bought an att htc one x from someone else. The phone is rooted,and the bootloader in unlocked. it is running:
Nocturnal xi40 115
4.0.3 Android v
3.0.8-01158-g3d3f08d [email protected] #1
smp preempt (Kernel)
0.17a.32.09.24_2_10.91.32.19L (baseband)
1.88.707.2 cl64928 (build)
How do i get this phone back to stock? I want the phone to be on stock sense. I have searched but, i cant figure out how to revert back. Thank you for your help.
Click to expand...
Click to collapse
1. Go to Settings -> Power and disable Fastboot.
2. Reboot the phone into the bootloader
3. Relock the bootloader by using the command "fastboot oem lock" from cmd (this is assuming you have the Android sdk on your computer, if you don't, go get it). I believe this causes your phone to reboot as well. If it does, just get back to the bootloader once it's done booting up again.
4. Enter Fastboot
5. Install HTC Sync on your PC (for drivers and such)
6. Connect your phone to your PC and let it install the drivers and what whatever Windows needs to do. You should see the text on your phone read FASTBOOT USB when it's done
7. Download the latest RUU from here: http://forum.xda-developers.com/showthread.php?t=1670238
8. Run the RUU (it's an exe, just run it like normal)
9. Follow the instructions and you'll be back to stock. The process takes like 10-15 minutes
Can I downgrade to 1.85?
lakas187 said:
Can I downgrade to 1.85?
Click to expand...
Click to collapse
You can if you have superCID, you can check by typing "fastboot getvar cid" and making sure it's 11111111 (uhhh...I think it's 8 digits, don't remember, it just has to be all 1's).
stnguyen09 said:
1. Go to Settings -> Power and disable Fastboot.
2. Reboot the phone into the bootloader
3. Relock the bootloader by using the command "fastboot oem lock" from cmd (this is assuming you have the Android sdk on your computer, if you don't, go get it). I believe this causes your phone to reboot as well. If it does, just get back to the bootloader once it's done booting up again.
4. Enter Fastboot
5. Install HTC Sync on your PC (for drivers and such)
6. Connect your phone to your PC and let it install the drivers and what whatever Windows needs to do. You should see the text on your phone read FASTBOOT USB when it's done
7. Download the latest RUU from here: http://forum.xda-developers.com/showthread.php?t=1670238
8. Run the RUU (it's an exe, just run it like normal)
9. Follow the instructions and you'll be back to stock. The process takes like 10-15 minutes
Click to expand...
Click to collapse
Is the process the same if you're on CleanROM 4.1 SE (1.85) or any other Custom ROM for that matter?
phishie said:
Is the process the same if you're on CleanROM 4.1 SE (1.85) or any other Custom ROM for that matter?
Click to expand...
Click to collapse
Yes, this are the instructions for returning to stock from any custom rom. Though, if you're on an AOSP based rom, you don't have to disable Fastboot in Settings -> Power (it's not there)
I don't have cid. Can I just flash it to the phone as is?
lakas187 said:
I don't have cid. Can I just flash it to the phone as is?
Click to expand...
Click to collapse
You mean you don't have superCID or you can't find your cid? Everyone phone has one (it's sort of an id number of sorts).
Go ahead and just run the RUU, it'll yell at you if you don't have superCID and try to downgrade. If it goes fine, then you're good.
I meant that i don't have supercid.
lakas187 said:
I meant that i don't have supercid.
Click to expand...
Click to collapse
Just curious, what is your CID then?
Here's the one-click for superCID http://forum.xda-developers.com/showthread.php?t=1672284
I'll try to run the 1.85 ruu. I just don't want to brick it.
lakas187 said:
I'll try to run the 1.85 ruu. I just don't want to brick it.
Click to expand...
Click to collapse
You won't brick it by running the RUU.
..d
I'll just follow the steps you posted above and see if i can fix it.
Thanks for your help! I was able to flash back to stock :good:
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
I have at&t inspire 4g and I unlocked the bootlaoder by EasyAceRootTool and I have read many guides how to downgrade to 1.3 and how to get s-off and eng-off to instill leedroid
and these are the sites which I tried
http://www.addictivetips.com/mobile/install-leedroid-android-rom-on-the-htc-desire-hd-inspire-4g/
http://forum.xda-developers.com/showthread.php?t=905003
http://androidforums.com/inspire-4g...ally-downgrade-root-inspire-4g-desire-hd.html.
I attached the information about my at&t inspire 4g in the attachment files
You don't need S-Off to flash a custom ROM; an unlocked bootloader and a custom recovery is sufficient. More details instructions in the Ace Think Tank thread linked in my signature.
EDIT: why did you start two threads within a couple hours??
thanx but
bananagranola said:
You don't need S-Off to flash a custom ROM; an unlocked bootloader and a custom recovery is sufficient. More details instructions in the Ace Think Tank thread linked in my signature.
EDIT: why did you start two threads within a couple hours??
Click to expand...
Click to collapse
I'm lost cuz I read alot in many sites about how can I flash a custom rom and I faild to do it cuz almost pf the sites I read them . there are many missing files.and I'm new in theses things
plz
1- I have downloaded this rom and I want to instill it in my fone leedroid 2.2.2 in my fone
Can I download it
if so plz tell me the steps to do it
2- how can I make my fone works in another carrier
I will be thankful for you
I will delete the other thread
Like I said. Read the Ace Think Tank thread.
Hint: you need to flash a recovery from fastboot, then flash a ROM from recovery, then flash a boot.img from fastboot. And for carrier compatibility, you need to read the manual S-Off portion.
Inspire 4g update problem
Hello, I have an htc inspire 4g running OS 2.3.3 Gingerbread and I want to root it so I can flash custom rom but I need to downgrade the firmware first or else it wont work.
Other problem facing me is this that I need to flash in pd98img but when unfortunately bootloader is locked in my opinion because it is not detecting the img file.
When I tried to unlock the bootloader it says hboot update needed.
I need to know that how can I update the hboot of HTC inspire 4g.
I would be really thankful if I get a solution
rafayahmed said:
Hello, I have an htc inspire 4g running OS 2.3.3 Gingerbread and I want to root it so I can flash custom rom but I need to downgrade the firmware first or else it wont work.
Other problem facing me is this that I need to flash in pd98img but when unfortunately bootloader is locked in my opinion because it is not detecting the img file.
When I tried to unlock the bootloader it says hboot update needed.
I need to know that how can I update the hboot of HTC inspire 4g.
I would be really thankful if I get a solution
Click to expand...
Click to collapse
Run a RUU that supports bootloader unlocking. If you do this with a PD98IMG.zip you need to put the file in the root of the SD card and name the zip exactly that.
Thanks for the reply.
I really appreciate it but please can you provide me with the link of the RUU because I was unable to find such RUU after several attempts.
thanx but
bananagranola said:
Like I said. Read the Ace Think Tank thread.
Hint: you need to flash a recovery from fastboot, then flash a ROM from recovery, then flash a boot.img from fastboot. And for carrier compatibility, you need to read the manual S-Off portion.
Click to expand...
Click to collapse
this manual for high level and I'm new .could you plz help me with s-off
and I have to tell ya that I'ev tried to flash the the rom which I told ya and it says its 2.0.0
I want 2 ask ya f I flash it after I do adb fast boot for the boot.img of course before I do s-off that wont brick the fone
2- when I tried to flash the rom and it stuck in the splash screen so I did restore and I noticed that bettery is 10% from 100%
what does that mean?
rafayahmed said:
Thanks for the reply.
I really appreciate it but please can you provide me with the link of the RUU because I was unable to find such RUU after several attempts.
Click to expand...
Click to collapse
Your RUU depends on which DHD software version you are running. If you can't find one you need to make s gold card and flash another version's RUU.
sicoooo0 said:
this manual for high level and I'm new .could you plz help me with s-off
and I have to tell ya that I'ev tried to flash the the rom which I told ya and it says its 2.0.0
I want 2 ask ya f I flash it after I do adb fast boot for the boot.img of course before I do s-off that wont brick the fone
2- when I tried to flash the rom and it stuck in the splash screen so I did restore and I noticed that bettery is 10% from 100%
what does that mean?
Click to expand...
Click to collapse
Why are you trying to get S-Off? I'm not willing to help other people with the manual S-Off method because I haven't done it personally and it's a method meant for advanced users who don't need help anyway; if you need help I advise that you stick to just unlocking your bootloader.
ADB and fastboot are two separate things. You can fastboot flash the boot.img without bricking the phone, yes. My signature has instructions for flashing the boot.img.
If the battery level fell, it fell...flashing stuff takes a lot of power. If you let it hang on the splash for awhile I could see it dropping 90%.
bananagranola said:
Your RUU depends on which DHD software version you are running. If you can't find one you need to make s gold card and flash another version's RUU.
Why are you trying to get S-Off? I'm not willing to help other people with the manual S-Off method because I haven't done it personally and it's a method meant for advanced users who don't need help anyway; if you need help I advise that you stick to just unlocking your bootloader.
ADB and fastboot are two separate things. You can fastboot flash the boot.img without bricking the phone, yes. My signature has instructions for flashing the boot.img.
If the battery level fell, it fell...flashing stuff takes a lot of power. If you let it hang on the splash for awhile I could see it dropping 90%.
Click to expand...
Click to collapse
how minutes it takes in the first boot after flashin the new rom
and why ya didnt answer me about this rom leedroid ,can I instill it without downgrade or anything else
sicoooo0 said:
how minutes it takes in the first boot after flashin the new rom
and why ya didnt answer me about this rom leedroid ,can I instill it without downgrade or anything else
Click to expand...
Click to collapse
If it takes more than a minute, you probably didn't flash the boot.img.
Because I didn't understand the question. And still don't. With an unlocked bootloader and a custom recovery, the procedure for flashing all ROMs is the same.
thanx
bananagranola said:
If it takes more than a minute, you probably didn't flash the boot.img.
Because I didn't understand the question. And still don't. With an unlocked bootloader and a custom recovery, the procedure for flashing all ROMs is the same.
Click to expand...
Click to collapse
forget what I asked . I have instilled leedroid2.2.2 and there is no network
sicoooo0 said:
forget what I asked . I have instilled leedroid2.2.2 and there is no network
Click to expand...
Click to collapse
Um...LeeDroid has network. Did you full wipe?
Another Problem
Hello, Now I am facing another problem.
The AAHK says that I have to downgrade my radio through flashing PD98IMG.ZIP but my bootloader is not detecting the file.
The effen-manual says that I have to relock my bootloader.
Now I am not sure that currently my bootloader is locked or unlocked? or else should I have to unlock it first through HTCDev and then relock it?
Please it has been 4 months I am trying to root but I couldnt find a solution.
rafayahmed said:
Hello, Now I am facing another problem.
The AAHK says that I have to downgrade my radio through flashing PD98IMG.ZIP but my bootloader is not detecting the file.
The effen-manual says that I have to relock my bootloader.
Now I am not sure that currently my bootloader is locked or unlocked? or else should I have to unlock it first through HTCDev and then relock it?
Please it has been 4 months I am trying to root but I couldnt find a solution.
Click to expand...
Click to collapse
AAHK is retired and unsupported. Just unlock the bootloader and fastboot flash a recovery. Then flash a ROM from recovery.
I have recently restored my phone back to stock rom due to a soft-brick.
I need a step by step approach to help me install CleanROM 6.5 into my HTC One X (AT&T).
The CleanROM 6.5 thread is here: http://forum.xda-developers.com/showthread.php?t=1655011
The steps in the thread are too vague and general for me.
This is my phone's software information:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.85.502.3 710RD
HTC SDK API level: 4.11
HTC Extension version: HTC Extension_403_1_GA_4
More: Baseband, Kernel version, etc.
-I have CleanROM 6.5.zip downloaded
-I have my phone rooted using the approach from here: http://forum.xda-developers.com/showthread.php?t=1709424
-I have tried following the steps from threads in the Development section and I'm not entirely sure whether what to do next in my case
What are my next steps to installing CleanROM 6.5? Please provide step-by-step instructions as I don't want to mess up. Thanks!
synconclick said:
I have recently restored my phone back to stock rom due to a soft-brick.
I need a step by step approach to help me install CleanROM 6.5 into my HTC One X (AT&T).
The CleanROM 6.5 thread is here: http://forum.xda-developers.com/showthread.php?t=1655011
This is my phone's software information:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.85.502.3 710RD
HTC SDK API level: 4.11
HTC Extension version: HTC Extension_403_1_GA_4
More: Baseband, Kernel version, etc.
-I have CleanROM 6.5.zip downloaded
-I have my phone rooted using the approach from here: http://forum.xda-developers.com/showthread.php?t=1709424
-I have tried following the steps from threads in the Development section and I'm not entirely sure whether what to do next in my case
What are my next steps to installing CleanROM 6.5? Please provide step-by-step instructions as I don't want to mess up. Thanks!
Click to expand...
Click to collapse
Troll?
exad said:
Troll?
Click to expand...
Click to collapse
I'm not trolling. I seriously need help. Tell me what I'm doing inappropriate and I will fix it.
synconclick said:
I'm not trolling. I seriously need help. Tell me what I'm doing inappropriate and I will fix it.
Click to expand...
Click to collapse
Is your bootloader locked or unlocked?
S-ON or S-OFF?
Before we continue, I will advise you that the fact you need me to make out a step by step guide for you means you should remain stock. Please do not take this advice lightly. I am very serious and I am not trying to insult you or make myself seem superior to you or keep the XDA community exclusive (all of which I've been accused of when offering this advice). You should really read and understand before you do something like this because when something goes wrong, and something WILL go wrong, there's no guaranty anyone will be around to help you.
If you want to continue, just answer those two questions above. I'll help you but just remember, I warned you
exad said:
Is your bootloader locked or unlocked?
S-ON or S-OFF?
Before we continue, I will advise you that the fact you need me to make out a step by step guide for you means you should remain stock. Please do not take this advice lightly. I am very serious and I am not trying to insult you or make myself seem superior to you or keep the XDA community exclusive (all of which I've been accused of when offering this advice). You should really read and understand before you do something like this because when something goes wrong, and something WILL go wrong, there's no guaranty anyone will be around to help you.
If you want to continue, just answer those two questions above. I'll help you but just remember, I warned you
Click to expand...
Click to collapse
bootloader is relocked
as for S-ON or S-OFF, I don't understand. How do I check?
I've been trying to read and understand all this, but I have a feeling I've been reading wrong threads. If there's any links for a complete understanding of all this, that'd be nice.
synconclick said:
bootloader is relocked
as for S-ON or S-OFF, I don't understand. How do I check?
I've been trying to read and understand all this, but I have a feeling I've been reading wrong threads. If there's any links for a complete understanding of all this, that'd be nice.
Click to expand...
Click to collapse
S-On or S-oFF will be in your bootloader screen.
SInce you're relocked you'll have to unlock the bootloader again first. the unlock_code.bin should work again if you still have the one you got when you first unlocked the bootloader. Do you still have the unlock_code.bin?
exad said:
S-On or S-oFF will be in your bootloader screen.
SInce you're relocked you'll have to unlock the bootloader again first. the unlock_code.bin should work again if you still have the one you got when you first unlocked the bootloader. Do you still have the unlock_code.bin?
Click to expand...
Click to collapse
It says EVITA PVT SHIP S-ON RL.
No, I do not have the unlock_code.bin
synconclick said:
It says EVITA PVT SHIP S-ON RL.
No, I do not have the unlock_code.bin
Click to expand...
Click to collapse
Ok.. is your CID still 11111111
if you don't know boot to bootloader/fastboot and do:
fastboot oem readcid
Or
fastboot getvar cid
exad said:
Ok.. is your CID still 11111111
if you don't know boot to bootloader/fastboot and do:
fastboot oem readcid
Or
fastboot getvar cid
Click to expand...
Click to collapse
Yes
So the first step is to go to htcdev.com and get a new unlock_code.bin so you can unlock the bootloader.
Htcdev.com has all the instructions to get the unlock_code.bin
Once you receive it you'll want to put the unlock_code.bin in your fastboot folder, boot your phone to bootloader/fastboot and do:
fastboot flash unlocktoken Unlock_code.bin
Then select unlock bootloader in your phones screen.
Then verify that it worked in bootloader. If it didn't (sometimes it doesn't work right away) press and hold power to simulate a battery pull, when the screen goes black after capacitive buttons blink a bunch of times, let go of power, press and hold volume down until the bootloader comes up and the try again. It should work that time.
Once the bootloader is unlocked post here and I'll guide you through the rest.
Sent from my HTC One X using xda app-developers app
exad said:
So the first step is to go to htcdev.com and get a new unlock_code.bin so you can unlock the bootloader.
Htcdev.com has all the instructions to get the unlock_code.bin
Once you receive it you'll want to put the unlock_code.bin in your fastboot folder, boot your phone to bootloader/fastboot and do:
fastboot flash unlocktoken Unlock_code.bin
Then select unlock bootloader in your phones screen.
Then verify that it worked in bootloader. If it didn't (sometimes it doesn't work right away) press and hold power to simulate a battery pull, when the screen goes black after capacitive buttons blink a bunch of times, let go of power, press and hold volume down until the bootloader comes up and the try again. It should work that time.
Once the bootloader is unlocked post here and I'll guide you through the rest.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Do I select All Other Supported Models on this page? http://www.htcdev.com/bootloader/
Yes
Sent from my HTC One X using xda app-developers app
Got it. Successfully unlocked
Good. Next you'll want to download twrp 2.3.3.1 from goo.Im
Then check md5 to make sure the download is not corrupt. Google md5 checker if you need one.
Then put it in your fastboot folder. Boot to bootloader/fastboot
Fastboot flash recovery twrp2.3.3.1filename.img
Fastboot erase cache
Fastboot reboot bootloader
Select recovery from bootloader screen on your phone.
Mount usb storage in twrp with your phone connected to the pc.
Copy your Rom to your phone
Unmount your phone usb storage
Select wipe in twrp
Wipe cache, dalvik, system, factory reset
Go to install in twrp
Select your Rom.
Follow procedure on phone screen
Reboot phone when flash successful.
Because your hboot is under 1.14 that is all. If it was 1.14 or higher you would have to extract the boot.img from the Rom and fastboot flash boot boot.img
Also with s-on never ruu or ota to 3.18 or you will brick. Installing roms based on 3.18 is fine though.
Sent from my HTC One X using xda app-developers app
exad said:
Good. Next you'll want to download twrp 2.3.3.1 from goo.Im
Then check md5 to make sure the download is not corrupt. Google md5 checker if you need one.
Then put it in your fastboot folder. Boot to bootloader/fastboot
Fastboot flash recovery twrp2.3.3.1filename.img
Fastboot erase cache
Fastboot reboot bootloader
Select recovery from bootloader screen on your phone.
Mount usb storage in twrp with your phone connected to the pc.
Copy your Rom to your phone
Unmount your phone usb storage
Select wipe in twrp
Wipe cache, dalvik, system, factory reset
Go to install in twrp
Select your Rom.
Follow procedure on phone screen
Reboot phone when flash successful.
Because your hboot is under 1.14 that is all. If it was 1.14 or higher you would have to extract the boot.img from the Rom and fastboot flash boot boot.img
Also with s-on never ruu or ota to 3.18 or you will brick. Installing roms based on 3.18 is fine though.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which TWRP is correct to download. I searched up twrp 2.3.3.1 from goo.lm and got a list of options
synconclick said:
I'm not sure which TWRP is correct to download. I searched up twrp 2.3.3.1 from goo.lm and got a list of options
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
mebyUni can
ronnie498 said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Click to expand...
Click to collapse
I tried verifying with MD5 Check and it says the codes do not match.
Also, when I tried downloading from the link, I get
"We are currently experiencing difficulties with one or more of our distribution servers. Please hang tight for this to get resolved"
synconclick said:
I tried verifying with MD5 Check and it says the codes do not match.
Also, when I tried downloading from the link, I get
"We are currently experiencing difficulties with one or more of our distribution servers. Please hang tight for this to get resolved"
Click to expand...
Click to collapse
You have a message
Goo.Im link seems to be up right now
Sent from my HTC One X using xda app-developers app
ronnie498 said:
You have a message
Click to expand...
Click to collapse
Thank you! I downloaded the file now. But what about the problem from MD5 Check?
WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware
Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553
One more just in case
rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!
rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!
thank you!
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?
rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:
vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse
forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good: