[Q] How to i change my CID and allow OTA updates - HTC One S

Hi,
i recently got an HTC One S phone (used, no warranty). The phone seems to have been "played with" as it had Super User installed. However it was acting wierd so i did a factory recovery using the boot menu. This meant Super User was gone.
I am totally new to the updating an HTC phone, i found doing firmware changes to Sony and Samsung phones to be pretty much more easier!
My needs are pretty basic ! which is i want to achieve the following
I want to change my phone to have a normal CID without depending on carrier delays for updates (my CID is ORANG1)
I do not want to install a custom ROM, i want OTA updates to happen
I want to have my phone get the OTA update for Jelly Bean
When i boot into the phone (volume - + restart), i see the following,
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.3150S.19_2
OpenDSP-v21.1.0.32.0314
eMMC-boot
Mar 15 2012, 23:37:23
Other facts
My CID - ORANG1 (using CID getter app)
Phone model - S4 Z520e
I hear the Jelly Bean update sorts the helicopter issue with the HOME button, though i am not sure if the restart issue when browsing with the stock browser has been resolved. The helicopter HOME issue is driving me nuts.
Appreciate if someone can provide me the steps about how i can go about getting my phone CID changed and the OTA udpates working for the new CID, as searching the forums have not really helped me nail the way i can go about doing this.

Before we get started I'd like to know your home country (sorry I don't know your flag) and whether you're on stock or custom recovery.
As I'm on this device from the very beginning and know almost any corner in this forum I'll point you out where to find the things and information you'll need and some advantages as well as some disadvantages of what you want. Also I'll point out an alternative.

rootrider said:
Before we get started I'd like to know your home country (sorry I don't know your flag) and whether you're on stock or custom recovery.
As I'm on this device from the very beginning and know almost any corner in this forum I'll point you out where to find the things and information you'll need and some advantages as well as some disadvantages of what you want. Also I'll point out an alternative.
Click to expand...
Click to collapse
Wonderful to hear a quick response.
I live in Sri Lanka (small Island nation located at the bottom part of India, last colonized by the British!). The situation is that i think i am in stock, as i got this phone used and though everything is functional the helicopter home button issue, phone freezing when i use the stock browser for over a few minutes, connection looses (all reported errors with 4.0.3 and even 0.4) means i need to get this to Jelly Bean to make the phone more usable as i love the size and speed of the phone.
To start of is there any way i can see if my phone is in stock or custom recovery? I just searched and found http://forum.xda-developers.com/showthread.php?t=2124349, does the instructions "Fastboot getvar version-main" work?
Another twist is that i have the much loved Windows 8 running on my PC, i am not sure if that will have any effect on any command executions.

Wait you got 1.06 Hboot I would not flash RUU or OTA if you got that because you can update what is needed or if needed for roms plus you don't have to piss about when flashing roms so if I was you don't do it.

Thank you and welcome to this forum!
Your bootloader is still at version 1.06. Which is very good, as yours and version 1.09 allow you to flash nearly everything (kernels, radios, etc.) from within your device. Bootloader versions higher than 1.09 don't allow this anymore. For flashing kernels and radios you then will need to get into the phones fastboot mode and use the Android SDK on your pc, typing things like 'fastboot flash boot boot.img'.
Let's get started with recovery. To root your phone you usually need to flash a custom recovery. TWRP is the only one working bugfree atm. You can download it here.
To flash it and doing other usefull things try to get comfortable with the HTC One S All-in-one-toolkit.
So why do I mention this, also you wrote that the only thing you want to do is udating straightly to JB?
After the OTA update you'll be on bootloader version 2.15. It's just one more thing from htc to lock their devices even more, as at this time they don't behave very friendly to the dev community. Downgrading the bootloader is kind of pain and not easy so, unless you're familiar with linux (I did it succesfully several times).
Also stock JB from htc has one more surprise: Your system folder will be kind of write protected, which means, also you seem to have full root, after a reboot your formerly deleted (you thought so) files wil be back. Also added files in that folder won't be present any more. That crap is hardcoded into htc's JB kernel and sources are not available atm. But this problem was solved by flar2, who wrote a kernel module to bypass this.
So your hardware issues are left. As I'm not concerned by this I can only summarize what I read about these in the forum. They are obviously hardware related and therefore independant from software. Somebody wrote, a new radio had helped, others write different. In summary you'll have to check this out for your device.
Let's resume at this point:
Your device is unlocked and at 1.06. It needs to be relocked for the JB update and it will have a less comfortable bootloader version afterwards and it will be hard to get rid of the crapware in your system folder, as you'll have to unlock and root again for doing so. And it's questionable the JB OTA update will fix your hardware issues.
So I'd recommend the following procedure (you could still do the OTA update at any time, I'll help you then):
- use the all-in-one-toolkit, flash latest TWRP
- Flash latest EU radio 1.11 from here with twrp
- restore JB from my nandroid backup (download 3.16)
- if you experience troubles with your wifi connection, flash these wifi partitions
- check if your hardware troubles have been resolved
- to get root use all-in-one-toolkit again and flash elemental kernel (by flar2)
It seems a lot of work, but it's worth it. PM me, if you need additional help or decide to do the OTA update.

wow, thanks so much for all the info. I will give this a try tonight as i have the phone @ home, using my One X as the regular phone until i get the One S sorted. Then i will hope push out the One X and keep the One S as my regular phone. I prefer the One S size which is more ideal for one handed operation, shame that HTC opted for a pentile display that took out the sharpness.
Also based on your suggestions would it be better for me to opt for a custom ROM than HTC standard to resolve my issues?

Related

[Q] Flashing Generic Firmware with S-off

Hi Guys,
Apologies if this has been discussed before. I have looked for answers everywhere and i could not find any.
Ok, I have a Desire S which is branded to Telstra (Australia), I was sick of all the useless app that Telstra had put in and wanted to get rid of all those.
I used revolutionary method to get it s-off and install Generic Firmware. After that i was happy not having any of Telstra's bloatware on the phone. Then came the update of 2.3.5 and as usual downloaded the firmware and used RRU to Update. Big mistake on my part, i didn't read anything and just tried to push RRU on the phone, the result was White screen with HTC logo and nothing past that. Tried everything no luck, then looking for answers, i found a solution to remove revolutionary, I could see revolutionary gone in HBOOT but the phone would not start.
to solve this i went to telstra to send it to repair, warranty was there and when telstra asked what happened, i said i was updating an app and it went to this screen, Tech guys said this is the similar 3rd problem in a day. so after 5 days the phone got repaired, New IMEI number and logic board had to be replaced.
Now all over again i have bunch of telstra bloatware on the phone. I want to get Generic 2.3.5 with sense 3.0. what is the process to follow so that i don't make the same mistake again?
All i want to do is get it s-off and install generic Firmware, the easiest way possible something like revolutionary. I tried going with ADB but found a bit risky.
Any advice in getting Generic HTC Desire S (2.3.5 with Sense 3.0) the easiest way would be helpful. Thanks in advance.
HBOOT info:
SAGA PVT SHIP s-ON RL
HBOOT-0.98.0002
RADIO-3805.04.02.01_M
eMMC-boot
Mar 30 2011,17:29:31
Thanks
To get a generic firmware from some other area, you need to get Super CID. I don't know much about it, just that CID's like a region code, Super CID enables you to get generic ROMs from any region. Only XTC Clip can do that on a Desire S as far as i know. Flashing a custom ROM after Revolutionary S-OFF is a better option....
Listen, I really recommend you to use a Custom ROM based on the update if you are ready to S-OFF. Hyperion is much faster and has a lot more features. Hell, if you do S-OFF, why settle for Sense 3? Get Sense 3.5. I recommend endymion.
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
zryvffn said:
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
Click to expand...
Click to collapse
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
ben_pyett said:
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
Click to expand...
Click to collapse
Hey Ben, Thanks for this, I went ahead and got the ROM as you suggested. Installed the base verison, then the add-on and the update. I have been palying around with it and so far loving it.
Only problem tough, I cannot use Market. I can open market look for apps and download, but when it starts to install, the phone re-boots. any known issues with this and is there a workaround to sort this out.
Ok, so here is what i did, Flashed Base version again and market started working again with no issues. Another issue which is not so much of an issue but only at night, why does the soft keys don't lit up on Desire S?. any way to fix these. Thanks guys.
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
sadsac said:
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Thanks for that, I did a search for the issue and did the same thing as you had advised, but didn't work. Then I flashed the base version again and then the update, which worked. Don't know what had happened there.
But yeah loving the new rom and i would say was a better move to be on a custom ROM and getting rid of Carrier's junk installed.
Cheers!
Ok, so instead of creating a new post i have decided to post it here since it is already been discussed.
I was happy with rooted phone and endymion Rom and was happy until my phone started heating up and restarted on its own as if it had a mind of its own, I called HTC and they advised to send it for repair, i had to unroot the phone and sent for repair. Got the phone back with updated version and i need help rooting the phone.
when i boot the phone in fast boot this is what i get:
****LOCKED****
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-BOOT
Aug 22 2011, 15:22:13
Android Version 2.3.5
HTC Sense Verison 3.0
Software Number: 2.14.841.4
Baseband Version: 2.14.841.4 CL 184593 Release-Keys
Now i need to Root the phone again so i can be another happy user of endymion.
I am looking at this guide and needed help.
http://forum.xda-developers.com/showthread.php?t=1443636&page=1
The oldest RUU i can find for my provider is RUU_Saga_Telstra_WWE_1.36.841.3_Radio_20.28d.30.0805U_3805.04.02.01_M_release_184558_signed.exe
I was reading the guide and this is where i am confused.
6.This command will gets you out of adb shell.. so we need to get back to adb shell and you will see "#" sign..meaning you are temp rooted and we can then proceed to changing MISC_VERSION:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.27.405.6 .
./misc_version -s 1.27.405.6 do i change this to 1.36.841.3 or leave it as it is?
Any help will be greatly appreciated.
Thanks.
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
chninkel said:
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
Click to expand...
Click to collapse
Thanks for that, yes i did follow the guide, and then got stuck again. The problem i am facing is after pushing all the files as of the guide, i run tacoroot the phone restarts and all i get is a red triangle with exclamation mark in it and nothing else happens.
then to get rid of it, i pull out the battery and do a complete factory reset. I have done this about 5 times now but still the same.
Also tried using super one click but that dint work either and freezes on waiting for device.
anything i have missed or is there any other solutions, any GUI programs or video to help if i am missing something.
any help is appreciated.
Thanks
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
chninkel said:
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
+1
You can pull it out as often as you want..but at least you should know the risk.
Sent by my fingers to your head
chninkel said:
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
I don't understand,"boot into original recovery". To try i booted the phone in HBOOT and pressed recovery and same thing the triangle shows. am i missing something here.
EDIT: I went till the last step and this is what i get "Patching and backing up partition 17...
Error Opening backup file.
#"
any idea
zryvffn said:
To try i booted the phone in HBOOT and pressed recovery
Click to expand...
Click to collapse
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
chninkel said:
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
Click to expand...
Click to collapse
Thanks dude, this worked and going thru revolutionary. i did some changes in the steps and will update what i did in a while after i get a rom installed.
Thank you everyone for help and support. i was able to downgrade my HBOOT and install a custom ROM. It would not have been possible if you guys had not supported.
one thing i have learnt is the more you read the more you find things useful and you actually learn how ti weigh your risk and benefits and avoid ending up with an expensive paper weight.
so this is what i did.
after using universal misc version file i was getting 140 error in RUU, boot loader version error, tried 3 time but would not let me get past that, then out of frustration i thought about giving it a last try for good or for worse, in the misc version section i changed a bit.
adb shell
cd /data/local/tmp
./misc_version -s 1.36.841.3 (Same number as my RUU)
then RUU went fine and then revolutionary.
well, if any kind of newbie person in trying to root the phone i would suggest to read and if you think you have read enough, its probably you haven't.
special thanks to @chninkel, @eyahl. Thanks Guys for all the support.
Cheers!

[ruu] [stock] att 2.20 ota

Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Issues:*
1. If you update you will get a newer hboot, you may not be able to use other older ruu's such as 1.85, etc. Recommend immediately making a backup once rooted, unlocked, etc.*
2. Updating results in boot.IMG from custom roms not being flashed again. Have to flash the boot.IMG of custom Rom in fastboot as before.*
3. Radio.img will not flash on new hboot either must be done in fastboot same as boot.img.
HTC One X for AT&T ROM Update | 8.02.2012
Starting August 2nd 2012, HTC will be rolling out a system update for the HTC One X.
This update will only be available for AT&T HTC One X customers and will be sent to the device over the air. Once the release is ready, users will receive a notification on their device advising them of this update and provide instructions to receive and install it. Users can proactively check for this update by going to Home > All Apps > Settings > AT&T Software Update > Check for updates.
As an alternative solution, the system update can be downloaded to a PC and manually applied to the device. See the section at the bottom of these instructions for more information.
This system update includes:
New features:
NFC Capabilities
Additional content added to HTC Hub
Third party music applications accessible from the Car application.
Fixes/Updates:
Wi-Fi connectivity fixes
Improved Bluetooth automobile compatibility
3G/4G connectivity improvements
HTC Sense fixes
Contacts synchronization fix
Network time fix (clock displays 30 minutes off)
WARNING: During the upgrade process the device will reboot multiple times and show software upgrade screens. Do not remove the battery as this will stop the update and your device may be rendered inoperable!
Getting Started
Before you proceed with the update, make sure you have done the following:
Set aside approximately 20 minutes to allow the device to update, possibly longer based on Wi-Fi network speed
Connect the device to a charger
Ensure the battery is charged to at least 30%
Connect to a stable Wi-Fi network to download the software file.
Installation instructions
To manually perform the update, follow these steps below:
From the Home screen, tap All apps and then tap Settings.
Tap AT&T Software Update.
Tap Check for updates.
Tap OK to download the update.
After you select your method of download, you will be prompted with a Wi-Fi or Data fee warning message. If this is acceptable, tap OK to start the upgrade process.
Status of the download can be viewed in the Notifications pull down.
Once the download is complete, the user will be prompted to install from the Notifications pull down. Tap the System update to begin the upgrade process.
Tap OK to begin the update process to software version 2.20.502.7.
Device will reboot and begin installation. Users will not be able to use their device during the installation process (approximately 10 minutes).
System update complete. Tap OK to continue
Manual system update instructions:
If you are outside of AT&T/Wi-Fi coverage, or the update is not found, you may perform a manual system update.
Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
Download and save the HTC One X™ for AT&T ROM update to your PC.
Connect your device to your PC via the supplied USB cable. NOTE: You must have HTC Sync Manager installed on your PC in order to run the update.
NOTE: If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/us/support/.
Ensure the device is properly recognized on the PC, then locate the HTC One X™ for AT&T ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
Follow all of the system update wizard instructions shown on your PC.
Once the update is complete, click Finish in the Wizard and the device will reboot.
Once the device reboots, the initial setup wizard will appear.
Once the initial setup process is complete, the device is ready for use.
Download
portions of this post copyright HTC 2012. All rights reserved to them.
kewl
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
.
Third party music applications accessible from the Car application.
Click to expand...
Click to collapse
WOOT.
Thank you for not using File Factory haha
"NFC capabilities"????
Sent from my HTC One X
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yeah if you know what you're doing, but damn I'm going to miss the one stop flashing we used to have.
eraste said:
Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Click to expand...
Click to collapse
I thought that was good?
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
This was to be helpful for us that already did OTA. I agree tho if one isint literate in the world of android wait to use this until all the things above are worked out.
scribed on my 2.20 HOX
slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yea thats fine if you know how, but why make everyones life harder when this upgrade is older then the asia 2.23.
its just going to make a lot of un needed posts to developers asking why the rom dont boot and so on. Run this ruu and it will cause more problems then anyone needs. As well as set you back from any S-Off development.
But that is my warning. Just saying, i cant see it from my house, my phone flashes
kernels just fine and always will. One Stop flashing.
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I know i am, Ive been down this road several times in the past and i know what to flash and not to flash. That being said, I,m just trying to warn anyone that thinks the ruu is better then the rom alone...
gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Nrod0784 said:
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Anytime
scribed on my 2.20 HOX
eraste said:
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
Click to expand...
Click to collapse
Well I'm in america too! but i thought a warning would be nice, But what do i know
i think his warning was sufficient enough. he stated no benefits of flashing. unless you already did it prior. plus there are other threads who state warnings as well. people dont care or dont read and will flash anyway :laugh:
not taking sides i see what people do here that go against there better judgments or even when told not too :laugh:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
eraste said:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
Click to expand...
Click to collapse
whoa and i just downloaded too lol. just in time add to the RUU collection lol

[Q] need help where to go next

I have ATT HOX 2.20, unlocked, rooted, superCID, S-off, latest TWRP (thanks to all of you). I'm prett lost as to where to go next. I'd like to keep all of this and update to the latest stock ota Jellybean. However, when I check for ATT updates on the phone, nothing happens, even when I manually check in.
I would like the latest and greatest on this phone but more important is full functionality and full stability. If I could hit a button, return this phone to original, and download the latest ota, I would. I would then just use Titanium Backup to remove any bloatware that I didn't like. But I (and I suspect many others) spent weeks unlocking this phone because it was unclear when, or if, an official JB would ever arrive. So here I am, stuck in an inbetween moment. The part where this site offers way too many options with unclear results. I am looking for the least complicated, way to get the most fully functional and stable JB onto this phone and I'll be done. And, I can't figure out if it's the official update or one of a thousand offered Roms, kernels, radios, etc. Any and all specific advice would be appreciated. And, as always, thank you to all who post here. I've had a lot of fun (and a few scary moments).
runaway said:
I have ATT HOX 2.20, unlocked, rooted, superCID, S-off, latest TWRP (thanks to all of you). I'm prett lost as to where to go next. I'd like to keep all of this and update to the latest stock ota Jellybean. However, when I check for ATT updates on the phone, nothing happens, even when I manually check in.
I would like the latest and greatest on this phone but more important is full functionality and full stability. If I could hit a button, return this phone to original, and download the latest ota, I would. I would then just use Titanium Backup to remove any bloatware that I didn't like. But I (and I suspect many others) spent weeks unlocking this phone because it was unclear when, or if, an official JB would ever arrive. So here I am, stuck in an inbetween moment. The part where this site offers way too many options with unclear results. I am looking for the least complicated, way to get the most fully functional and stable JB onto this phone and I'll be done. And, I can't figure out if it's the official update or one of a thousand offered Roms, kernels, radios, etc. Any and all specific advice would be appreciated. And, as always, thank you to all who post here. I've had a lot of fun (and a few scary moments).
Click to expand...
Click to collapse
Why do you want to go stock? Stock currently has only 4.1.1. There are various ROMs on the XDA, if you want a sense one try out the Viper XL and also there are various options for non-sense ROMs.
Anyways if you do want to flash the stock ROM here is the link: -
http://forum.xda-developers.com/showthread.php?t=2181399
Make sure you rea carefully before you flash the stock one from anywhere. There have been bricks. Also check out the FAQs. Hope this helped
runaway said:
I have ATT HOX 2.20, unlocked, rooted, superCID, S-off, latest TWRP (thanks to all of you). I'm prett lost as to where to go next. I'd like to keep all of this and update to the latest stock ota Jellybean. However, when I check for ATT updates on the phone, nothing happens, even when I manually check in.
I would like the latest and greatest on this phone but more important is full functionality and full stability. If I could hit a button, return this phone to original, and download the latest ota, I would. I would then just use Titanium Backup to remove any bloatware that I didn't like. But I (and I suspect many others) spent weeks unlocking this phone because it was unclear when, or if, an official JB would ever arrive. So here I am, stuck in an inbetween moment. The part where this site offers way too many options with unclear results. I am looking for the least complicated, way to get the most fully functional and stable JB onto this phone and I'll be done. And, I can't figure out if it's the official update or one of a thousand offered Roms, kernels, radios, etc. Any and all specific advice would be appreciated. And, as always, thank you to all who post here. I've had a lot of fun (and a few scary moments).
Click to expand...
Click to collapse
I think pretty much everybody here will tell you to stay away from the new ota. It offers nothing new and some people have even bricked their phones while updating. My suggestion would be to install one of the custom roms as they're better optimissed and don't have all the bloat and are more customizable. I've found viperxl to be as stable as stock while adding a load of tweaks to highly personalize it. Cleanrom on the other hand doesn't have all the tweaks but is a stripped down Rom that's fast and stable. But you'll have to try you like best but I advise you not to ota. The ota will also update your touchscreen firmware that causes a lot of problems for cm users. If you think you might want to install cm10 don't update.
Sent from Xparent Red using my Venomized Evita
If you want stock flash CleanROM 6 r2. In fact, just flash everything in my signature + turge's WiFi fix. That will give you the latest "stock" experience for AT&T.
Sent from my HTC One XL
There's no need to "stay away" from the OTA if you know what you're doing. It contains some updates that are not in any of the Sense ROMs. If you want to update everything on your phone, it's easy and safe to do so since you're s-off. The only people who bricked were SuperCID and s-on. Here's what to do:
-Confirm that you're s-off (just to be safe)
-Make a full backup and copy it off your phone.
-Run 2.20 ruu. You need this to restore stock recovery.
-Download the ota, rename update.zip, and copy to internal storage.
-Reboot to bootloader, select recovery, press power and vol+ to get to recovery dialog.
-Ignore errors that come up. Select install from internal storage, select update.zip. Your phone may reboot a couple of times. Return to bootloader when done.
-Push custom recovery back on.
-Flash rooted rom
-Restore backups as necessary
I did all this a couple of weeks ago, and my phone is running faster and more smoothly than ever.
You will need to downgrade your touchscreen firmware if you ever plan to use an AOSP rom.
I'll try this
iElvis said:
There's no need to "stay away" from the OTA if you know what you're doing. It contains some updates that are not in any of the Sense ROMs. If you want to update everything on your phone, it's easy and safe to do so since you're s-off. The only people who bricked were SuperCID and s-on. Here's what to do:
-Confirm that you're s-off (just to be safe)
-Make a full backup and copy it off your phone.
-Run 2.20 ruu. You need this to restore stock recovery.
-Download the ota, rename update.zip, and copy to internal storage.
-Reboot to bootloader, select recovery, press power and vol+ to get to recovery dialog.
-Ignore errors that come up. Select install from internal storage, select update.zip. Your phone may reboot a couple of times. Return to bootloader when done.
-Push custom recovery back on.
-Flash rooted rom
-Restore backups as necessary
I did all this a couple of weeks ago, and my phone is running faster and more smoothly than ever.
You will need to downgrade your touchscreen firmware if you ever plan to use an AOSP rom.
Click to expand...
Click to collapse
This is what I'm looking for. My second choice would be the highly recommended Viper Rom, and thirdly a CleanRom. I tried the CleanRom once and softbricked my phone so I'm a little shy now. I like the HTC Sense and don't mind keeping it. I just want a ROM designed specifically for this phone where everything works, is updated, and is stable. I feel like the official ota is the answer. The info on this site gets quite scattered when you get to this point. Do I stay locked, or do I re-lock? Do I keep TWRP or not? Do I flash or update? Boot image extract or no? S-off ok or no? etc. etc. I'll try your way first. Provided I come out the other side ok, I'll post the results here. Thank you for your help.
runaway said:
This is what I'm looking for. My second choice would be the highly recommended Viper Rom, and thirdly a CleanRom. I tried the CleanRom once and softbricked my phone so I'm a little shy now. I like the HTC Sense and don't mind keeping it. I just want a ROM designed specifically for this phone where everything works, is updated, and is stable. I feel like the official ota is the answer. The info on this site gets quite scattered when you get to this point. Do I stay locked, or do I re-lock? Do I keep TWRP or not? Do I flash or update? Boot image extract or no? S-off ok or no? etc. etc. I'll try your way first. Provided I come out the other side ok, I'll post the results here. Thank you for your help.
Click to expand...
Click to collapse
Also, to clarify, by "backup" I meant both a nandroid (always a good idea when making changes), and your user apps+data.
When restoring, only restore user apps. A nandroid will put you back where you were. Don't restore system apps+data either, as this can cause problems, esp when upgrading your base.
iElvis said:
Also, to clarify, by "backup" I meant both a nandroid (always a good idea when making changes), and your user apps+data.
When restoring, only restore user apps. A nandroid will put you back where you were. Don't restore system apps+data either, as this can cause problems, esp when upgrading your base.
Click to expand...
Click to collapse
Just to confirm, After downloading OTA and doing my backups, I need to find the original 2.20 file for this phone and restore stock recovery? (I'll have to admit, I'm a bit lost on this site and overwhelmed by all of the files I've downloaded to get this far. If anyone can post a link here to this file, and or, instructions, I'd appreciate it)
Here is where I stand right now:
Andriod 4.04, HTC Sense 4.0, Software number 2.20.502.7 710RD, HTC SDK API level 4.23
Tampered
Unlocked
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as32.09.11-2
OpenDSP-v29.1.0.45.0622
eMMc-boot
Jun 11 2012 14:36:28
runaway said:
Just to confirm, After downloading OTA and doing my backups, I need to find the original 2.20 file for this phone and restore stock recovery? (I'll have to admit, I'm a bit lost on this site and overwhelmed by all of the files I've downloaded to get this far. If anyone can post a link here to this file, and or, instructions, I'd appreciate it)
Click to expand...
Click to collapse
Yes, there is a link to the 2.20 ruu in the development section roll-up thread.

[Q] Yes, another but documented Boot Loop - Sensation 4G

I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Micalee said:
I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Click to expand...
Click to collapse
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
astar26 said:
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
Click to expand...
Click to collapse
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Micalee said:
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Click to expand...
Click to collapse
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
astar26 said:
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
Click to expand...
Click to collapse
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Micalee said:
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
Click to expand...
Click to collapse
If you want you should backup via recovery, but wiping the phone after is necessary. if you managed to push the ROM to the SD-card, you can normally flash. but use a ICS (or newer) ROM, that supports the firmware.
In contrast to what heavy_metal_man said, you can do a nandroid backup as it is, as the files are still there. but you don't have much to do with it.
Edit - If you need any help doing it step by step - I'm here to help, just say where you are stuck on the guide (or just explain)
heavy_metal_man said:
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29.2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011.12:14:25
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Micalee said:
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29.2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011.12:14:25
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Click to expand...
Click to collapse
you just used a ruu.exe from pc and restored everything to stock condition
but how you were able to keep custom recovery(cwm V4.0.1.4)
when you flashed the 3.33 firmware you could just install a custom ics rom
because with 3.33 firmware the gb rom you had it would never booted
about OTA i assume nothing will happen as long as you have cwm recovery installed
you must have the stock recovery
Well, since you flashed a new rom you can disregard my first suggestion and go straight for running the ics ruu you have. Ota updates will not work if you dont have the stock recovery. But the ruu will give you it so ota will work, but the updates will be for the cid of the rom you flashed. So flash a WWE rom to make sure you get any updates, but at this point their will be few if any.
Aside from that you will be all sorted pal
Sent from my Nexus 7 using Tapatalk 4
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Micalee said:
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Click to expand...
Click to collapse
ah sorry, getting ahead of myself with terminology here WWE stand for world wide English. most unbranded phones run on world wide English roms, and if people are downgrading/upgrading they tend to want unbranded as they will get official htc updates faster
as far as cid`s are concerned they dont really matter as you are s-off and the phone will accept any ruu (rom update utility) you give it. one note of caution though is you have select a t-mobileus ruu and they are ment to be for the tmobile sensation 4g. if you dont have the tmobus 4g it may give you some issues with the radio, meaning you may lose phone signal. ( im not 100% sure but caution is advised )
if you dont have a sensation 4g then download and run this one here. im pretty confident that its a stock ice cream sandwich unbranded rom
Running the RUU is simple enough, just boot the phone into your stock 2.3.4 rom and turn on usb debugging from settings for good measure. Then connect the phone to the pc via the usb cable and then run the RUU. it will connnect to the phone and confirm the phone is the correct model i believe, then it will confirm this is what you want to do. select yes and let it work its magic. its pretty straight forward they phone may reboot several times, this is normal. just dont disconnect the battery or the usb cable and you will be fine. should be done in ten minutes tops
good luck pal
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
I'm glad your sorted pal the threads can be a bit out of date, maintenance of information is not really regulated but as always if people are unsure just ask, quoting the info you have and what you think is the case
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Micalee said:
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
Click to expand...
Click to collapse
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
rzr86 said:
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
Click to expand...
Click to collapse
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Micalee said:
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Click to expand...
Click to collapse
exactly the firmware 3.33 and the 1.27.1100 hboot version are from 3.33 universal firmware zip(from the thread you mentioned)
but as long as you are on S-OFF you can use any ruu.exe if you are also supercid
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Micalee said:
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Click to expand...
Click to collapse
A factory reset only deletes the data partition and cache, not any other partition. There are ROMs that are based on stock (and even stock). By fully legitimate 'stock' situation I believe you mean S-On and every thing stock. There are guies for that in the general and development forums.

[Q] Need some serious advice about roms! Been away for loooong

So, i was here back when the phone came out, unlocked the bootloader and got a few Roms in the start, and ended up with Paranoid Android V2.54 i believe, and never really cared about looking for anything new since i thought it was pretty good, and i enjoy as close to stock as possible. But now my phone is getting really slow, and i need a change. And getting back onto the forums here im just really intimidated by the amount of Roms, the term S-OFF and Kernel. I generally know the basics i suppose, but when i was installing Roms back in the early days of the HTC one S it was as easy as getting the rom on the SD card an flashing it. Im probably coming off as a bit stupid here, but i dont wanna brick this phone just because i did one thing wrong.
So where im getting at is, what Rom should i go for? I just need something easy to install, and nothing super flashy. As said earlier, i enjoy the stock android, and i wouldnt mind getting the newer version of android aswell. So give me some pointers, and feel free to give me the details on how to flash it as i havent done this in a while
Jahrern said:
So, i was here back when the phone came out, unlocked the bootloader and got a few Roms in the start, and ended up with Paranoid Android V2.54 i believe, and never really cared about looking for anything new since i thought it was pretty good, and i enjoy as close to stock as possible. But now my phone is getting really slow, and i need a change. And getting back onto the forums here im just really intimidated by the amount of Roms, the term S-OFF and Kernel. I generally know the basics i suppose, but when i was installing Roms back in the early days of the HTC one S it was as easy as getting the rom on the SD card an flashing it. Im probably coming off as a bit stupid here, but i dont wanna brick this phone just because i did one thing wrong.
So where im getting at is, what Rom should i go for? I just need something easy to install, and nothing super flashy. As said earlier, i enjoy the stock android, and i wouldnt mind getting the newer version of android aswell. So give me some pointers, and feel free to give me the details on how to flash it as i havent done this in a while
Click to expand...
Click to collapse
First thing you should tell us some more info about your phone, just to know better what guides and adices we should give you:
1. Phone model: S4 or S3 (is it with dual core krait 1.5 Ghz or with older dual core 1.7 Ghz processor?)
2. What hboot/firmware do you have, what radio, are your bootloader locked or not (at HTC Dev site)...in fact we need all the info that you have on your bootloader screen (power off phone then keep pressed VOLUME DOWN while pressing POWER)
3. What recovery do you use (CWM or TWRP) and what version?
4. Finally but not least....WHAT DO YOU WANT? A Sense ROM, an AOSP ROM, do you want latest Android version (4.4.2 KitKat) or it doesn't matter to you...things like this. You said something about this but maybe give more details
Then we might have some guides for you and some advices and you could choose among them based on your pers preference :good:
Rapier said:
First thing you should tell us some more info about your phone, just to know better what guides and adices we should give you:
1. Phone model: S4 or S3 (is it with dual core krait 1.5 Ghz or with older dual core 1.7 Ghz processor?)
2. What hboot/firmware do you have, what radio, are your bootloader locked or not (at HTC Dev site)...in fact we need all the info that you have on your bootloader screen (power off phone then keep pressed VOLUME DOWN while pressing POWER)
3. What recovery do you use (CWM or TWRP) and what version?
4. Finally but not least....WHAT DO YOU WANT? A Sense ROM, an AOSP ROM, do you want latest Android version (4.4.2 KitKat) or it doesn't matter to you...things like this. You said something about this but maybe give more details
Then we might have some guides for you and some advices and you could choose among them based on your pers preference :good:
Click to expand...
Click to collapse
1. According to Quadrant i have a CPU Frequency of 1512MHz, so by definition that should make it a S4
2. For recovery, im almost 100 percent sure its SuperSU, and heres the details from my bootloader:
VLE PVT SHIP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.315018.19
OpenDSP-v21.1.0.32.0314
eMMC boot
Mar 15 2012.23:37;23
And yes i used HTC Dev website to unlock it. got some sort of key and everything.
3. The recovery i use atm is CWM 5.8.3.1 the none touch version. Tried the touch version a few times, but it doesnt seem to work for me.
4. For ROM as i mentioned i really like AOSP, and can't really see myself going for a Sense ROM unless there's something really awesome out there. Ive used CM 9 and 10, AOKP, ParanoidAndroid and one of those Pac-man ROMs before, and they have all been decent. But now i want something newer. Preferably something over 4.1.2 as ive had that for probably a year now, and i need SOMETHING new. I dont particularly want anything that isn't as complete as possible. The ROM im rocking now reboots my phone ATLEAST 1-2 times a day, and have some minor Wi-Fi issues. (not really that bad anymore after buying an expensive new ASUS Router)
So those are like my only things when it comes to ROMs. Doesnt need to be as flashy as coming with a completly themed interface and that sorts
I like CM11. It seems to running ok, but better check the latest in the thread.
http://forum.xda-developers.com/showthread.php?t=2528113&page=367
Jahrern said:
1. According to Quadrant i have a CPU Frequency of 1512MHz, so by definition that should make it a S4
2. For recovery, im almost 100 percent sure its SuperSU, and heres the details from my bootloader:
VLE PVT SHIP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.315018.19
OpenDSP-v21.1.0.32.0314
eMMC boot
Mar 15 2012.23:37;23
And yes i used HTC Dev website to unlock it. got some sort of key and everything.
3. The recovery i use atm is CWM 5.8.3.1 the none touch version. Tried the touch version a few times, but it doesnt seem to work for me.
4. For ROM as i mentioned i really like AOSP, and can't really see myself going for a Sense ROM unless there's something really awesome out there. Ive used CM 9 and 10, AOKP, ParanoidAndroid and one of those Pac-man ROMs before, and they have all been decent. But now i want something newer. Preferably something over 4.1.2 as ive had that for probably a year now, and i need SOMETHING new. I dont particularly want anything that isn't as complete as possible. The ROM im rocking now reboots my phone ATLEAST 1-2 times a day, and have some minor Wi-Fi issues. (not really that bad anymore after buying an expensive new ASUS Router)
So those are like my only things when it comes to ROMs. Doesnt need to be as flashy as coming with a completly themed interface and that sorts
Click to expand...
Click to collapse
OK, I got more info now, maybe some others will step in and give you their opinions and advices. What I can tell
1. SuperSU is not a recovery (you already said you're using CWM)...it's the root program.
2. You have hboot 1.06 the same I had on my device some time ago (not too long ago). It has some advantages and some disadvantages. I'll try to be brief and prsent you all and you can decide what you wanna do.
First some background: S-Of basically means you are able to write to certain partitions on your device, partitions that are normally locked. Most important are the firmware/hboot partition, radio partition and kernel partition. If you are S-On, you cannot write/flash radio or firmware and you MUST flash any kernel via a separate command in fastboot.
Now what makes 1.06 hboot so special...it is behaving like a partial S-Off device even if you are not S-Off. What does this mean? You will be able to flash radios and kernels as any other S-Off user. Only thing you won't be able to flash is the firmware/hboot. On the other hand, all new ROMs require hboot 2.13/2.15 or the leaked 2.16. That means that IF your current hboot allows you to run such a ROM, you won't be able to flash it unless you're editting EVERY TIME the updater-script in the ROM ZIP you're flashing to bypass the hboot check. So things will become little bit complicated.
To avoid all these you should first S-Off then you should upgrade to hboot 2.15. This is the last official firmware and it is supported by all new KitKat ROMs. DO NOT flash 2.16 firmware unless you would like to flash and use Sense based ROMs like MaximusHD.
I made S-Off by using Rummrunner because I found it the simplest way to do it...it's like a one-press-S-Off. If that doesn't work for you, you can try other methods like Facepalm or Moonshine. You can find separate threads for each in Dev section and I'll also link them below
Rummrunner
Facepalm
Moonshine
After you made S-Off, next step will be to upgrade your hboot/firmware to 2.15. You can use the flashable ZIP from THIS thread and you'll find info on how to do it in the thread. I would suggest you to choose the Unbranded 2.15 hboot and that has also the red warning gone (the one you see when start up the device with "This device is for development purposes only...bla bla bla")
For all the above you might also want to check/try a tool that incorporates most of them. You can find it in THIS thread.
Now that you have S-Off and upgraded your hboot, you might want to flash a newer radio. Hint:If you're satisfied with your current signal strength, mobile data and so on, don't flash another radio. Even if in a ROM thread it is recommended or mandatory a certain radio, my advice is to first try the ROM with your current one and only if performance is not satisfactory, flash another radio.You can find radios in tecardo's thread HERE or if you want the newer radios you can find radio 1.20 HERE or 1.35a HERE. One more note regarding tecardo's thread with the radio collection...that thread is old and some info is not updated. Just remember that you must flash ONLY the V6 Sense Radio installer for any ROM you'll be using, being it sense based or AOSP. Also ignore that warning that the procedure is only for hboots below 1.3...at that time there was no S-Off (remember what I've said about the particularities of 1.06 hboot earlier). Now things are different, you're S-Off so you will just need to flash it
Before flashing, you might consider upgrading to a newer recovery. I would recommend you the latest official TWRP 2.7.0.0 that will support flashing anything made for hboot 2.15. If and only if you decide to try sense ROMs based on hboot 2.16, you'll need a different recovery specific for 2.16 and that you'll get from that specific ROM thread. Official TWRP downloads for Ville S4 are HERE
Now youre almost done. You just need to pick your ROM and flash it...pretty difficult task considering how many they are. I tested most of AOSP ones and also some Sense based ones (not the ones for hboot 2.16 tho). I don't want to advice too much here since it could be considered I favour one or another...the truth is I do and that's normal, but I'd like to be objective
First, all KitKat ROMs are pretty stable. On CM11 there are regular nightlies and there are also less stable or bugged builds but this is expected. So you might try several ROMs to see which suits you most and you can decide by reading each ROM's thread. I'll list some ROMs (not all), the ones that are updated most often and I've tested, in no particular order...in fact I'll list them alphabetically to avoid interpretations
AOSP based
Beanstalk
CandyKat
CM11
Infamous (IOAP)
PAC-Man
TwistedKat
Vanir
Sense based
Viper ROM 3.1.3
Liberty ROM
Sorry for the long post but I wanted to get most in a single place and if you'll have more questions we'll detail them later. Just try something... READ READ READ...each thread contains valuable info about each procedure and step and also the experience of the users. I know it is easier to ask but don't forget it's YOUR PHONE and YOUR INTEREST to see things working on it. So you should make some effort to read and search also
Good luck
I've read the entirety of your post now, and it's definetly helpful!
As it's pretty late here atm, i will come back to the tread tomorrow and S-Off and all that jazz. Im not a complete moron on this area, allthough thats what it probably seemed like Im glad i asked before i did anything, cause this was alot more complicated then when i was flashing ROMs when the phone came out.
I will definetly try to hold on to my current Radio as i have had no complaints ever on connection and service. So thanks for telling me about that, otherwise i would probably have flashed a new one each time.
Ill be sure to keep you posted on my progress tomorrow, just incase i totally **** up or something, or just cant get myself to understand something. If it is as easy to flash ROMs as it used to be once im ready to flash again, ill figure out my Next ROM, so im grateful that you listed a few of them that i can try out.
Again i wanna thank you for taking the time to explain a total Noob how to go about doing this, i really appreciate it!
rapier's post just about expresses all the basic info you need, couldnt have been put better!!
as far as going on to the newer sense based roms i'd suggest not to take that road yet as they require hboot 2.16 and it can get fairly tricky to go back to the previous hboot.
also for hboot 2.15 also you have more choice for roms available... just a point of view!!
happy flashing!!
So, now im totally lost. did the S-off, and now im trying to do the firmware, but im clueless here as i cant find the folder adb/fastboot in my platfomr-tools sdk folder or whatever you wanna call it. It wants me to place the firmware inside the adb folder, and i cant find any folder with that name.
I followed a guide on how to get adb working on my computer as i did not have that anymore on my PC, so had to redo it.
was following the guide, and did not see this "2. Now place the Firmware_named_something.zip into your adb/fastboot folder" at first, and tried to flash and was welcomed with cannot open "named file here" for obvious reasons when i saw step 2.
but this step 2 is what is confusing me, as ive mentioned, there is no adb/fastboot folder. is this a folder i make somewhere in my sdk? or what am i missing here. to give you the full info, i used this guide:
http://forum.xda-developers.com/showthread.php?t=1752270
the second post.
i remember having fastboot in that sdk folder on my old PC, but did not get it this time around when following these instructions, maybe thats what im missing
Jahrern said:
So, now im totally lost. did the S-off, and now im trying to do the firmware, but im clueless here as i cant find the folder adb/fastboot in my platfomr-tools sdk folder or whatever you wanna call it. It wants me to place the firmware inside the adb folder, and i cant find any folder with that name.
I followed a guide on how to get adb working on my computer as i did not have that anymore on my PC, so had to redo it.
was following the guide, and did not see this "2. Now place the Firmware_named_something.zip into your adb/fastboot folder" at first, and tried to flash and was welcomed with cannot open "named file here" for obvious reasons when i saw step 2.
but this step 2 is what is confusing me, as ive mentioned, there is no adb/fastboot folder. is this a folder i make somewhere in my sdk? or what am i missing here. to give you the full info, i used this guide:
http://forum.xda-developers.com/showthread.php?t=1752270
the second post.
i remember having fastboot in that sdk folder on my old PC, but did not get it this time around when following these instructions, maybe thats what im missing
Click to expand...
Click to collapse
ADB/fastboot are not folders, are commands. What that instruction meant was to place the firmware zip in the same folder where your ADB/fastboot executable is. Usually this is in "android-sdk/platform-tools". You'll notice there the ADB and fastboot executables
Rapier said:
ADB/fastboot are not folders, are commands. What that instruction meant was to place the firmware zip in the same folder where your ADB/fastboot executable is. Usually this is in "android-sdk/platform-tools". You'll notice there the ADB and fastboot executables
Click to expand...
Click to collapse
OMG! That makes more sense, still that sentence he used in the guide was pretty misleading though. literally tried making a fastboot folder with the .exe in alot of different folders xD
Will try that one out and see if it works! Thanks, AGAIN!
EDIT:
Just tried to put the firmware inside C:/android/sdk/platform-tools/ folder, but still i got
"Error: Can not open 'Fuu_Downgrade2.15_Unbranded.zip'
EDIT:
Turns out there was a program instead of a .exe :s just tried though, and it failed.
"FAILED (rempote: 99 unknown fail)
EDIT:
Apparently the S-OFF didnt work. Tried Rumrunner, as i didnt understand jack **** about the alternatives
EDIT:
Tried Facepalm aswell, not 100 percent sure if i did it right though, as there was no confirmation anywhere, but still no S-OFF

Categories

Resources