How to apply OTA update on Rooted At&t One X - AT&T, Rogers HTC One X, Telstra One XL

Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.

Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460

redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.

abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172

If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app

Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right

a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded

abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update

Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.

iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.

By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.

iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock

abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.

iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image

I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.

iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update

abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.

iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.

I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261

The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.

Related

[Q] Help, boot loop here?

I wanted to flash to ARHD 6.3
This is my first time.. I managed to S off.. But then the bootloop began after I flashed PG58IMG.zip via fastboot.
Step 1. To S-OFF your Sensation - (You do not need to do this if you have S-off already or done this before) - WORKING NOW for TMOUS users
Visit
download the application for your operating System. AND EXTRACT IT TO A FOLDER
YOU MAY NEED TO DISABLE YOUR ANTIVIRUS PROGRAM- Norton is flagging up Revolutionary as a Virus when it isn't
IMPORTANT
Fill out the form under the download links with your OS, Device, Hboot Version and Serial number. This will give your beta key to enable you to S - OFF. Make a note of this.
How To get your Hboot Version - 3 methods below
1. [/url] and if it has found your device it should read
"Found your Device: HTC Sensation Z710* Applications -> Development)
4. With the phone switched on (not in HBOOT, just the regular home screen), plug in your USB cable and select HTC sync mode.(IGNORE any warning messages on your phone telling you it cannot find HTC Sync )
5. Launch revolutionary.exe. It should detect the phone and ask for your beta key. Type it (BE CAREFUL, as its case sensitive) or copy and paste it in.
If Revolutionary fails to find your phone verify you have all the drivers installed, try disk drive mode or charging mode (Linux users can use disk drive mode. Confirmed to be working by others)
6. Once you have entered your beta key correctly, follow any on screen prompts or actions from revolutionary and wait for it to S-Off,
7. You're done. Your Device will Successfully have S-OFF....if it hangs on method 3 and doesn't S-Off. See post 2 below for solutions.
IF REVOLUTIONARY SAYS FAILED YOUR PHONE IS NOT SUPPORTED. Go back and check hboot using the methods above. some users are told its failed and they still have S off now. If you have S-off your hboot will now be 1.17.1011 and revolutionary will tell you now your device is not supported
8. Revolutionary will now ask you to Install clockwork recovery mod after S OFF. Type N and install it manually below (the recovery provided is v4.0.1.4 doesn't charge when device is switched off, the one below v5.0.0.1 does charge)
9. Your Device now is S-off.
To install clockwork recovery for the sensation. Follow step 2!
STEP 2. To INSTALL Recovery - v5.0.0.8
1. Download recovery v5.0.0.8 for the Sensation HERE: or Multiupload
2. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
3. Turn off your phone FUlly and reboot into the Bootloader/HBOOT screen (see post above on how to get to hboot screen)
4. Press Volume up to Accept when it asks" Do you want to start the update"
5. Press Power Off to Reboot back to android after installation is successful (normal screen with homescreen)
Click to expand...
Click to collapse
I got stuck at step 2.5.. Pls help me out. Actually I used to flash ROM for i9000 a couple of times but for sensation this is my first time. I'm using sensation unlocked. I lived in Malaysia so most probably its asians version.
ethanmars said:
I wanted to flash to ARHD 6.3
This is my first time.. I managed to S off.. But then the bootloop began after I flashed PG58IMG.zip via fastboot.
I got stuck at step 2.5.. Pls help me out. Actually I used to flash ROM for i9000 a couple of times but for sensation this is my first time. I'm using sensation unlocked. I lived in Malaysia so most probably its asians version.
Click to expand...
Click to collapse
Hi,
Try loading 5.0.2.0 HERE
Then follow THIS GUIDE to install 6.3.0
thank you so much for your reply!
i've downloaded that. Now how do i install it? fastboot only accept .zip files right? or is the instruction is in the 2nd link you gave me?
ethanmars said:
thank you so much for your reply!
i've downloaded that. Now how do i install it? fastboot only accept .zip files right? or is the instruction is in the 2nd link you gave me?
Click to expand...
Click to collapse
Hi,
Just rename 5.0.2.0 to PG58IMG.zip
Power off
Power on holding volume- and power button.
When it has finished,delete PG58IMG.zip
malybru said:
Hi,
Just rename 5.0.2.0 to PG58IMG.zip
Power off
Power on holding volume- and power button.
When it has finished,delete PG58IMG.zip
Click to expand...
Click to collapse
just pressed thanks, hehe..
i was wandering alone while waiting for your reply n managed to install ext4 touch recovery.. lol.. but still bootloop when pressed reboot.
now I wanna know will the 5.0.2.0 help me to access android again coz i haven't backup my contacts n sms yet..
let's say the answer is no, will it help if i make a nandroid backup now? or is it too late considering i cant access android anymore?
ethanmars said:
just pressed thanks, hehe..
i was wandering alone while waiting for your reply n managed to install ext4 touch recovery.. lol.. but still bootloop when pressed reboot.
now I wanna know will the 5.0.2.0 help me to access android again coz i haven't backup my contacts n sms yet..
let's say the answer is no, will it help if i make a nandroid backup now? or is it too late considering i cant access android anymore?
Click to expand...
Click to collapse
Hi,
Lesson for the future...
Always backup(nandroid,Titanium Backup,google) BEFORE starting anything major.
If you have 4EXT installed,then follow THIS GUIDE to install 6.3.0
malybru said:
Hi,
Lesson for the future...
Always backup(nandroid,Titanium Backup,google) BEFORE starting anything major.
If you have 4EXT installed,then follow THIS GUIDE to install 6.3.0
Click to expand...
Click to collapse
thanks again ..
so that means there's no way to access my phone like it was before eh?
btw, i thought it wasnt anything major coz it was just gaining an s off n then installing recovery.. then this happened.. i dont know what went wrong.. hmm
so i shall proceed with installing 6.3.0 since its like the only option i have left i believe?
ethanmars said:
thanks again ..
so that means there's no way to access my phone like it was before eh?
btw, i thought it wasnt anything major coz it was just gaining an s off n then installing recovery.. then this happened.. i dont know what went wrong.. hmm
so i shall proceed with installing 6.3.0 since its like the only option i have left i believe?
Click to expand...
Click to collapse
Hi,
Just as a matter of interest.
Do you still have a PG58IMG.zip on your sd card?
If so ,delete it.
Then it may boot into your ROM...
malybru said:
Hi,
Just as a matter of interest.
Do you still have a PG58IMG.zip on your sd card?
If so ,delete it.
Then it may boot into your ROM...
Click to expand...
Click to collapse
oh i've read that as well so i have deleted it manually by using sd adapter.. then reinserted it back n tried to boot normally.. but to no avail.. what's the root cause of this eh?
when i gained s off, i still can boot into my ROM.. however disaster happens when i flashed the .zip files obtained as per instructions..
oh but directly after i've flashed it, i didn't remove the .zip files n tried to immediately reboot into ROM.. does this make a difference?
ethanmars said:
oh i've read that as well so i have deleted it manually by using sd adapter.. then reinserted it back n tried to boot normally.. but to no avail.. what's the root cause of this eh?
when i gained s off, i still can boot into my ROM.. however disaster happens when i flashed the .zip files obtained as per instructions..
Click to expand...
Click to collapse
Hi,
Did you complete the s-off thread by rooting and getting SuperCID?
malybru said:
Hi,
Did you complete the s-off thread by rooting and getting SuperCID?
Click to expand...
Click to collapse
good question..
immediately after s off, i boot into my ROM and tried to install busybox and other apps that requires superuser or root but failed and stating that my device was still not rooted..
so i proceed to install a recovery (in this case its ext4 recovery) but failed to find a .zip installer (but managed to find the .apk and .img version but afraid to proceed considering the extension wasn't the same as per guide's PG5...ZIP). so i tried to simply install cwm as per stated in the guide. coz i know after recovery is installed, only then i would be able to install the su zip files.
then it boot looped.. n here we are trying to shoot all of these troubles.. XD
and if my understanding was wrong, pls correct me. thanks!
only after you sent me the links i managed to install ext4 recovery via a much easier method using cmd.exe..
n that also means that i wasn't even able to follow through the supercid part of the guide..
ethanmars said:
good question..
immediately after s off, i boot into my ROM and tried to install busybox and other apps that requires superuser or root but failed and stating that my device was still not rooted..
so i proceed to install a recovery (in this case its ext4 recovery) but failed to find a .zip installer (but managed to find the .apk and .img version but afraid to proceed considering the extension wasn't the same as per guide's PG5...ZIP). so i tried to simply install cwm as per stated in the guide. coz i know after recovery is installed, only then i would be able to install the su zip files.
then it boot looped.. n here we are trying to shoot all of these troubles.. XD
and if my understanding was wrong, pls correct me. thanks!
only after you sent me the links i managed to install ext4 recovery via a much easier method using cmd.exe..
Click to expand...
Click to collapse
Hi,
I follow THIS GUIDE
If you have 4EXT installed ,then you should be able to boot into recovery and make a nandroid,then root,then supercid...
malybru said:
Hi,
I follow THIS GUIDE
If you have 4EXT installed ,then you should be able to boot into recovery and make a nandroid,then root,then supercid...
Click to expand...
Click to collapse
wait a moment, i dont know if things are making more sense to me but, is it possible that this was caused by a wrong firmware? i just figured out my cid and its htc_044 and there are 4 different version of firmware for this cid, so should i try each of it until my phone boots to my original ROM?
Update: Oh God, I'm in such a relief! Thank God it works now. I flashed the firmware 1.17 n now am able to boot back into my ROM. Now i'm gonna get things backed up n will proceed. phew thanks so much for helping me out. The cause was maybe the zip files werent compatible with mine. So i check my cid n mid, n downloaded what might be the original one. so now its fixed..

Recommendations on OTA (ATT 4.0.3/4.0/1.73)

Hey all,
I rooted my HOX (1.73, 4.0.3) with the kpenn ne-Click a few days after I got it for the Tether and to de-bloat. Since then I haven't read anything on the One X till I heard Jelly Bean coming along. Anyhoo my question is what the upside of getting the new OTA (4.0.4) would be and how I would go about it if I wanted to (I've never updated before and ATT has stopped asking me to update, also I get nothing when I try to check for an update).
I've been reading around and it seems like most people are on to 1.85 and are flashing 4.1/2.2. My primary uses of my phone are for the media applications/web browsing and I haven't noticed any real drop in performance but I have heard the new updates have sped up the HOX considerably which is something I'm always interested in.
Thanks!
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Shaddy-Z. said:
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Click to expand...
Click to collapse
i one-clicked unrooted my phone earlier and freaked out (and the new updates didn't work out on my phone anyway). i ended up getting kpenn's one click again and putting SU back into my phone. Do you have any links that can take me on a step by step process of unlocking my phone and flashing those roms on it? I just love being able to control my phone and pushing it to its absolute limits.
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Pbdeng said:
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Click to expand...
Click to collapse
it's UNLOCKED?
you're lucky then.
just push a recovery like twrp then push root. Then you can debloat.
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Pbdeng said:
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Click to expand...
Click to collapse
make sure you have your unlock token and then go to http://www.htcdev.com/bootloader/unlock-instructions/page-4/
and follow the directions.
after that look at this thread to install twrp http://forum.xda-developers.com/showthread.php?t=1777773
then this one to re-root
http://forum.xda-developers.com/showthread.php?t=1673935
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Pbdeng said:
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Click to expand...
Click to collapse
no those pages just tell you how to manually install root and recovery.
your bootloader is still unlockable
unlock it
then install a recovery
then install root via that recovery
Ahh, thanks a bunch man.
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Pbdeng said:
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Click to expand...
Click to collapse
yeah unlock the boot loader. set up the phone again
then install the recovery then root.
to make your unlock stick, turn off fastboot in power options, then power down phone completely then restart it to the bootloader.
Hmm, so my phone is definitely unlocked now. I installed the recovery and I manually flashedthe new SuperSU in that link you posted for me. As far as I can tell nothing is happening.
Note: It says that it installs the recovery but there is no reboot that occurs. I've done this both with the android app and manually and nothing is happening.
I don't see SuperSU and rootchecker is confirming that my phone isn't rooted yet.
so you reboot to recovery, choose the superSU package to install then what happens?
I know this works I've done it quite a few times myself.
Presently I installed the latest img file with TWRP with the app. There is not reboot that occurs (unless I'm suppose to reboot on my own?). If that's the case then I've been a total idiot.
I've just been installing the openrecovery and then I press "Flash Roms" to flash the supersu. I get a little notification that says "Preparing to Flash" and then nada.
After you install twrp recovery you reboot. Then you boot to recovery and flash the super su zip manually
Wooh! I got it to work! Thank you so much!
Pbdeng said:
Wooh! I got it to work! Thank you so much!
Click to expand...
Click to collapse
No problemmo.
Does this also mean that I can flash any ROMs I want on my phone now?
Yes. But you will have to flash kernels aka boot.img separately using fast boot.

[Q] deleted htc framework file and phone doesnot start

deleted htc framework file and phone doesnot start.
After rooted my htc One X. In the process of removing at&t crap ware I accidentally deleted something that said htc frame work.
From then on my phone would not start. I unlocked my phone as well. How ever I didnot have any custom ROM installed or didnot have any back up done.
When I tried to reboot my phone after deleting the htc frame work file, it would not start. HTC icon would show up and it would not go further.
These are the things I did.
1. I flashed CWM.
2.I flashed TWRP.
3.I finally flashed CWM. 5.8.3
Then I went to fastboot mode and
removed Dalvik Cache, Erased the sd card
and tried to 'mount usb storage' but it would say
"unable to open ums lunfile(no such file or directory)SD card space free:10169MB"
My phone though shows as a removable disk , when i click on the icon it would say " Please insert disk into removable disk." I tried to save a custom ROM on my memory card and flash it but my system doesnot detect my phone.
Can some one please help me?
Thank you.
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Lock bootloader run ruu start over. Next time the very first thing you do is make a nandroid back up.
redpoint73 said:
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Thanks for the quick reply.
When I tried to mount my phone as usb it would not. I mentioned that as well.
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online. Without installing a custom ROM and run RUU , do you think my phone works
Adding a note to it. my phone is s-on and did not have android sdk installed on my machine. i tried all this using fastboot files and twrp img.
Thank You
in00b said:
When I tried to mount my phone as usb it would not.
Click to expand...
Click to collapse
You mentioned you tried to mount USB using fastboot (I've never mounted USB using fastboot, so I can't comment on that). Try mounting USB within TWRP, and see if that works. FYI, the USB mount feature in CWM does not work, and CWM does not really support our device, and has major issues. That's why its strongly recommended you use TWRP and not CWM.
in00b said:
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online.
Click to expand...
Click to collapse
Website seems to be too busy now. As long as its not 2.20, it should be okay. Normally, I would caution against randomly searching around the internet for things and flashing them, and instead getting them here instead. But briefmobile is Kenneth Penn's website, and he is a known developer on XDA.
in00b said:
Without installing a custom ROM and run RUU , do you think my phone works
Click to expand...
Click to collapse
You deleted part of the OS, so I'd say no. It doesn't boot does it? Then it doesn't work.
Also, please click "Thanks" to the post that help you.
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
No, you can only have one recovery. Flash one, you overwrite whatever you had before.
in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
I'd stay away from CWM. I know it used to cause problems, but I don't know if it does anymore.
Most everybody here (in the One XL forums) prefer TWRP anyways.
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
in00b said:
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
Click to expand...
Click to collapse
Did you lock your bootloader before running the RUU?
Butters619 said:
Did you lock your bootloader before running the RUU?
Click to expand...
Click to collapse
nope my phone was boot loader unlocked and s-on.
in00b said:
nope my phone was boot loader unlocked and s-on.
Click to expand...
Click to collapse
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Butters619 said:
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Click to expand...
Click to collapse
thanks i will try unlocking my phone and get back to you.
in00b said:
how do i relock my phone.that doesnt turn on at all. all i see is htc screen and it wouldnt go any further.
Click to expand...
Click to collapse
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
qwertyaas said:
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
Click to expand...
Click to collapse
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
But in almost every thread things have to be said 2-3 times which is ridiculous
Butters619 said:
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Click to expand...
Click to collapse
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
in00b said:
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
Click to expand...
Click to collapse
See that thanks button. Go through this entire thread and press it for everyone who helped you (aka everyone). Especially gunny.
And remember, things that sound important (framework, build., etc...) typically are important random assassinations typically get the shooter in trouble
18th.abn said:
random assassinations typically get the shooter in trouble
Click to expand...
Click to collapse
lol
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
Butters619 said:
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
Click to expand...
Click to collapse
Maybe he's more a fan of the Butters cartoon character than he is Totoro?

[Q] HTC One S Root OTA Update Questions

Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app
ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.
Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped
Wouldn't an RUU fix any of those problems?
Yes it would
Sent from my HTC One S using xda app-developers app

[q] htc inspire 4g root white screen

Hi- i'm tyring to root my HTC Inspire 4G. I've downloaded alot of the programs aahk, oneclick, root rescue, etc. not having any luck. one click program gets to #7 and hangs. my rom recovery might be corrupt b/c i cant get into recovery. even when i do a factory reset in settings it hangs on the white htc screen on boot up forever. than need to take battery out. i did manage to unlock the bootloader fine with htcdev.i tried the PD98IMG in my sdcard. but i guess i need to have S-Off which i still have S-On b/c my phone isnt rooted yet, any ideas what i can try.? thanks
mikk65 said:
Hi- i'm tyring to root my HTC Inspire 4G. I've downloaded alot of the programs aahk, oneclick, root rescue, etc. not having any luck. one click program gets to #7 and hangs. my rom recovery might be corrupt b/c i cant get into recovery. even when i do a factory reset in settings it hangs on the white htc screen on boot up forever. than need to take battery out. i did manage to unlock the bootloader fine with htcdev.i tried the PD98IMG in my sdcard. but i guess i need to have S-Off which i still have S-On b/c my phone isnt rooted yet, any ideas what i can try.? thanks
Click to expand...
Click to collapse
If you've unlocked the bootloader you can't do any of that other stuff. You need to fastboot flash a recovery.img. Then flash a ROM from there. Instructions in the Ace Think Tank in the Desire HD General section. Note that the DHD and the I4G are essentially the same phone and have the same rooting instructions, and they can use each others' ROMs.
bananagranola said:
If you've unlocked the bootloader you can't do any of that other stuff. You need to fastboot flash a recovery.img. Then flash a ROM from there. Instructions in the Ace Think Tank in the Desire HD General section. Note that the DHD and the I4G are essentially the same phone and have the same rooting instructions, and they can use each others' ROMs.
Click to expand...
Click to collapse
oh really? I thought i had to first unlock the bootloader to root the phone or is that to jus use a custom rom? i can relock like i did earlier. is that what i need to do? Yes i realize the Desire HD/Inspire 4G same phone. was waiting for ICS and than HTC said too bad.So do you recommend i lock the bootloader back up? I'm new today here. wondering if i posted in right category after i posted. i see a development one to..
There are two ways to root and flash a custom ROM. One is S-Off. The other is unlocking the bootloader. S-off's tool has been retired, so you can only do it manually. You can still root and flash custom ROMs with an unlocked bootloader, though.
bananagranola said:
There are two ways to root and flash a custom ROM. One is S-Off. The other is unlocking the bootloader. S-off's tool has been retired, so you can only do it manually. You can still root and flash custom ROMs with an unlocked bootloader, though.
Click to expand...
Click to collapse
I went to this think tank link below like you mentioned and flashed the recovery. i even flashed a XGS Rom from sdcard.phone is booting up or its stuck on the white screen still but it installed.On #6 i got an error but the install went thru.might have to pull battery and restart it i think.this procedure didnt root my phone right? My phone stuck on the white screen.Might have to redo but like the 4ext recovery. Thanks for the great info!
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
What's an XGS ROM? You're hanging on the boot splash because #6 had an error. Fastboot flashing the ROM zip's boot.img is essential because you are S-On.
mikk65 said:
I went to this think tank link below like you mentioned and flashed the recovery. i even flashed a XGS Rom from sdcard.phone is booting up or its stuck on the white screen still but it installed.On #6 i got an error but the install went thru.might have to pull battery and restart it i think.this procedure didnt root my phone right? My phone stuck on the white screen.Might have to redo but like the 4ext recovery. Thanks for the great info!
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
Click to expand...
Click to collapse
I dont understand #6 theres no boot.img file in that folder. do i have to put one in or rename a file to flash?
Unzip the ROM zip. It'sinside the folders. If the ROM is missing one you need to find a new ROM zip.
bananagranola said:
Unzip the ROM zip. It'sinside the folders. If the ROM is missing one you need to find a new ROM zip.
Click to expand...
Click to collapse
That was the missing link. boot up fine. Thanks again!!. dont know if i need to root my phone or not now.yours rooted? XGS Rom link below. Cool Rom check it out if you like.
http://forum.xda-developers.com/showthread.php?t=1829764
I respect existz too much to use a downstream ROM. Yes, my phone is rooted. But all custom ROMs are rooted, so with XGS you probably are rooted as well.
bananagranola said:
I respect existz too much to use a downstream ROM. Yes, my phone is rooted. But all custom ROMs are rooted, so with XGS you probably are rooted as well.
Click to expand...
Click to collapse
I'll have to check out others avail with my phone. Root checker shows rooted phone. bootloader menu shows S-On still thought it would be S-Off. might run superoneclick root program on it. noticed the music files didnt play. battery drain about the same. Wondering if i can flash a Rom with LTE? unless that is a hardware issue.
mikk65 said:
I'll have to check out others avail with my phone. Root checker shows rooted phone. bootloader menu shows S-On still thought it would be S-Off. might run superoneclick root program on it. noticed the music files didnt play. battery drain about the same. Wondering if i can flash a Rom with LTE? unless that is a hardware issue.
Click to expand...
Click to collapse
Like I said earlier, there are two ways you can root and flash custom ROMs, S-On with unlocked bootloader and S-Off, and you can't have both. If you want S-Off, you would need to relock. And since AAHK (the S-Off tool) is retired, you can only manually S-Off now (which is something I would only recommend for advanced users). Using outdated tools, like AAHK and SuperOneClick, can get you in very bad predicaments very quickly (and I should note that you will probably not find support for those cases). You can look into other ROMs though, and note that the Inspire 4G and the Desire HD are basically the same phone and can use each others' ROMs. Since you are now rooted and can flash custom ROMs through recovery anyway, I would strongly advise that you stick to flashing ROMs now and not try to get S-Off.
LTE is a hardware issue. I4G and DHD don't support it.
bananagranola said:
Like I said earlier, there are two ways you can root and flash custom ROMs, S-On with unlocked bootloader and S-Off, and you can't have both. If you want S-Off, you would need to relock. And since AAHK (the S-Off tool) is retired, you can only manually S-Off now (which is something I would only recommend for advanced users). Using outdated tools, like AAHK and SuperOneClick, can get you in very bad predicaments very quickly (and I should note that you will probably not find support for those cases). You can look into other ROMs though, and note that the Inspire 4G and the Desire HD are basically the same phone and can use each others' ROMs. Since you are now rooted and can flash custom ROMs through recovery anyway, I would strongly advise that you stick to flashing ROMs now and not try to get S-Off.
LTE is a hardware issue. I4G and DHD don't support it.
Click to expand...
Click to collapse
Yeah just want to be able to flash Roms really. dont really need to have phone in S-Off. I'm looking at the Jellybean Rom think by codefirex i want to use. i want the latest ver. think its the 4.2.2 version. do know where can download it? Guess no LTE for awhile then or til my contracts up.
mikk65 said:
Yeah just want to be able to flash Roms really. dont really need to have phone in S-Off. I'm looking at the Jellybean Rom think by codefirex i want to use. i want the latest ver. think its the 4.2.2 version. do know where can download it? Guess no LTE for awhile then or til my contracts up.
Click to expand...
Click to collapse
The OP should have a link.
bananagranola said:
The OP should have a link.
Click to expand...
Click to collapse
Well i found it and flashed it on there. flashed fine and installed. but i dont see but i dont see google store.?
mikk65 said:
Well i found it and flashed it on there. flashed fine and installed. but i dont see but i dont see google store.?
Click to expand...
Click to collapse
When you flash ROMs and/or do anything else with your phone, make sure you read thoroughly. In the case of ROMs, read the OP carefully. It will tell you that you need to flash gapps.
bananagranola said:
When you flash ROMs and/or do anything else with your phone, make sure you read thoroughly. In the case of ROMs, read the OP carefully. It will tell you that you need to flash gapps.
Click to expand...
Click to collapse
Whats "OP"? i found a google play 3.10.14.apk latest ver. i guess and installed it on sdcard but it doesnt stay open. closes right up. probably need to flash it on there.right?
mikk65 said:
Whats "OP"? i found a google play 3.10.14.apk latest ver. i guess and installed it on sdcard but it doesnt stay open. closes right up. probably need to flash it on there.right?
Click to expand...
Click to collapse
I need to start over wipe it out b/c followed below instructions now phone not booting up...keep getting setup wizard has stopped ok button than comes back on.
http://yagyagaire.blogspot.com/2011/12/how-to-flash-google-apps-on-your.html#.UVziMEqmVuQ
.
mikk65 said:
I need to start over wipe it out b/c followed below instructions now phone not booting up...keep getting setup wizard has stopped ok button than comes back on.
http://yagyagaire.blogspot.com/2011/12/how-to-flash-google-apps-on-your.html#.UVziMEqmVuQ
.
Click to expand...
Click to collapse
Found the gapps file i need to flash just dont know when to do it. after i flash the jellybean rom?
OP is the original post in a thread, so post #1. Yes, just flash the gapps zip after the ROM.

Categories

Resources