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!
Related
Hi everyone! I'm new here so apologies for any mistakes, wrongs etc.
I needed some help with my HTC desire S, I'm new to all this rooting, flashing stuff, but i'm not too thick so understand some things. So heres the story/problem.
About a month ago I S-OFF my phone to try out some awesome custom ROMS, Granted i had some fun with them, I installed an unofficial 2.3.5 gingerbread with sense 3.0, just to see what the new sense was like, As I didn't receive the OTA update on my phone. But now i'd like to restore my phone back to the original ROM that came on the phone. I'm not to fused weather its S-OFF, all I really wanted was my original ROM as Sense 3.0 is running so slow on my phone, and its made a big difference in performance. I'm one of these guys who says please search the forum and google for help. And I did just this and found some great information yet of which i have had no luck with.
I've tried running an RUU whilst my phone is switch on and connected via HTC Sync, No luck. Model ID error 130....Please use the correct ROM (or something along those lines) So i found that u could flash the RUU after extracting the rom.zip and renaming it to PG88IMG.zip. So i did just this, still no luck, Updating was being processed and at the end of the update I got the message Wrong model ID and again Please use correct ROM (something like that anyway!)
Now your probably laughing at me by now thinking rialcniS you thick so and so, your using the wrong RUU. Which to anyone else sounds correct. But surely if i'm trying to convert back to the original stock ROM then 2.3.3 Gingerbread is the one to go for? as this was what my phone was running from the box!
So I did a little bit more research and found out that maybe its to do with my Hboot version. Below are my phones detail.
SAGA PVT ENG S-OFF
HBOOT-6.98.2000 (PG8810000)
RADIO-3822.09.08.20_M
eMMC-BOOT
FEB 24 2011,21:19:05
Software Information:
Android version - 2.3.5
HTC Sense Version - 3.0
Software Number - Desire S 2.10.401.4 [PROXUSER]
Kernel version - 2.6.35.10-g9ac6c7a
Baseband version - 20.48.30.0922U_3822.09.08.20_M
Build Number 2.10.401.4 CL156318 release-keys
Browser version - WebKit/533.1
From my research I found (or at least this is how it translates in my brain) is that I cant install an original stock ROM on Hboot 6.98.2000. Is this correct?
Anyway, for some more information to you guys when I load my phone up in fastboot, it starts searching for the PG88IMG.zip and also something along the lines of PG88DIAG, yet all it says underneath is Wrong or no image?
Am I being a complete idiot, or does this seem strange to some of you more advanced android rooters
If anyone can point me in the right direction to where i might be going wrong, id much appreciate it!
Thanks in advanced
Rialcnis!
rialcnis said:
Hi everyone! I'm new here so apologies for any mistakes, wrongs etc.
I needed some help with my HTC desire S, I'm new to all this rooting, flashing stuff, but i'm not too thick so understand some things. So heres the story/problem.
About a month ago I S-OFF my phone to try out some awesome custom ROMS, Granted i had some fun with them, I installed an unofficial 2.3.5 gingerbread with sense 3.0, just to see what the new sense was like, As I didn't receive the OTA update on my phone. But now i'd like to restore my phone back to the original ROM that came on the phone. I'm not to fused weather its S-OFF, all I really wanted was my original ROM as Sense 3.0 is running so slow on my phone, and its made a big difference in performance. I'm one of these guys who says please search the forum and google for help. And I did just this and found some great information yet of which i have had no luck with.
I've tried running an RUU whilst my phone is switch on and connected via HTC Sync, No luck. Model ID error 130....Please use the correct ROM (or something along those lines) So i found that u could flash the RUU after extracting the rom.zip and renaming it to PG88IMG.zip. So i did just this, still no luck, Updating was being processed and at the end of the update I got the message Wrong model ID and again Please use correct ROM (something like that anyway!)
Now your probably laughing at me by now thinking rialcniS you thick so and so, your using the wrong RUU. Which to anyone else sounds correct. But surely if i'm trying to convert back to the original stock ROM then 2.3.3 Gingerbread is the one to go for? as this was what my phone was running from the box!
So I did a little bit more research and found out that maybe its to do with my Hboot version. Below are my phones detail.
SAGA PVT ENG S-OFF
HBOOT-6.98.2000 (PG8810000)
RADIO-3822.09.08.20_M
eMMC-BOOT
FEB 24 2011,21:19:05
Software Information:
Android version - 2.3.5
HTC Sense Version - 3.0
Software Number - Desire S 2.10.401.4 [PROXUSER]
Kernel version - 2.6.35.10-g9ac6c7a
Baseband version - 20.48.30.0922U_3822.09.08.20_M
Build Number 2.10.401.4 CL156318 release-keys
Browser version - WebKit/533.1
From my research I found (or at least this is how it translates in my brain) is that I cant install an original stock ROM on Hboot 6.98.2000. Is this correct?
Anyway, for some more information to you guys when I load my phone up in fastboot, it starts searching for the PG88IMG.zip and also something along the lines of PG88DIAG, yet all it says underneath is Wrong or no image?
Am I being a complete idiot, or does this seem strange to some of you more advanced android rooters
If anyone can point me in the right direction to where i might be going wrong, id much appreciate it!
Thanks in advanced
Rialcnis!
Click to expand...
Click to collapse
Can't say much but I will point you to see this guide if it helps .
www.freeyourandroid.com/guide/flashing-ruu-htc
Sent from a darkly dreaming freak named Ray with a hTC Desire S in his hand which's rom is changed by the owner more than his clothes !
More useful info will be not the current state of your device, but what it was before the S-Off and customizing.
Setup the adb and fastboot commands on your PC /there is guide in my signature.
Then connect the device and type the following commands:
Code:
adb devices ([I]your device serial number should be displayed[/I])
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes[/I])
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img ([I]this will create a misc.img file on your SDcard[/I])
Then copy the misc.img to your PC and open it with HEX editor (XVI32 is free, you can google it)
Open the misc.img with HEX Editor. There will be a number like 1.28.401.1 on line 6. This is the number of your original software.
Search in this thread for the proper RUU and install it.
Important! Before flashing the RUU change your hboot with this one
Maybe sounds complicated but nothing scary about it, just follow the steps carefully.
Good luck
use search there is a whole thread about downgrading the hboot ON THE FIRST PAGE.
Sorry, I had searched and searched everywhere for about 3 hours straight, and every time I found something that seemed promising i would get errors and have no luck.
@amidabuddha, Thankyou so much, this seems very promising. I'll give it ago tonight and keep you posted on the progress!
Thanks again!!
look for a thread called downgrading the new hboot.theres a guide ,it works fine as i have used it myself.
djisgod said:
use search there is a whole thread about downgrading the hboot ON THE FIRST PAGE.
Click to expand...
Click to collapse
djisgod said:
look for a thread called downgrading the new hboot.theres a guide ,it works fine as i have used it myself.
Click to expand...
Click to collapse
Hey, his problem is not the hboot, he needs his Stock configuration for his region (which is wise in order to keep the warranty). The only thing he needs for this is the proper RUU and overwrittable hboot, no downgrades, no other stuff
amidabuddha said:
Hey, his problem is not the hboot, he needs his Stock configuration for his region (which is wise in order to keep the warranty). The only thing he needs for this is the proper RUU and overwrittable hboot, no downgrades, no other stuff
Click to expand...
Click to collapse
So, thanks to you mate i've got it all back to stock! Fantastic! Thankyou very much for your help and keep up the good work!
rialcnis said:
So, thanks to you mate i've got it all back to stock! Fantastic! Thankyou very much for your help and keep up the good work!
Click to expand...
Click to collapse
Glad that you solved your issue.
Just out of curiosity - which one was your RUU?
And for your information (there was a complain in your first post about sense 3 performance) - if you receive the 2.10.x.x OTA update notification, the stock sense 3 runs pretty good on my device, no lagging, no bugs so far. So maybe you can give it a try when the time comes.
Enjoy your "new" phone
amidabuddha said:
Glad that you solved your issue.
Just out of curiosity - which one was your RUU?
And for your information (there was a complain in your first post about sense 3 performance) - if you receive the 2.10.x.x OTA update notification, the stock sense 3 runs pretty good on my device, no lagging, no bugs so far. So maybe you can give it a try when the time comes.
Enjoy your "new" phone
Click to expand...
Click to collapse
Yeah I'm not to sure, it was running slow and not nice and fresh like it is now! but i reckon now i know how to solve the problem if it occurs again i might give it a try my original RUU was the one u listed in your post 1.28.401.1. Nice and simple instructions you gave, so thanks very much again!!
Which stock Sensation XE rom has the least amount of bloatware?
The question pretty much sums it up. I just got a Sensation XE, Hong Kong model. It has a lot of crap software on it: youni sms, xda assistant, 通通电话，baidu, kuwo player, and all this other Chinese crap. I hate Chinese software with passion. If skynet was/is real, I believe it would be running a Chinese OS. Chinese software naturally tries to take over your computer or phone.
I want to switch to the stock rom with the least amount of junk on it. If it also has a good Chinese/English keyboard with handwriting input that is a plus.
Also, just to make sure I'm on the right track, this is what should be done before I can change roms, right?
1) Get S-off
2) Install Clockwork Mod
3) Get permanent root
4) Write super cid
5) Change Stock Rom
typci said:
Which stock Sensation XE rom has the least amount of bloatware?
The question pretty much sums it up. I just got a Sensation XE, Hong Kong model. It has a lot of crap software on it: youni sms, xda assistant, 通通电话，baidu, kuwo player, and all this other Chinese crap. I hate Chinese software with passion. If skynet was/is real, I believe it would be running a Chinese OS. Chinese software naturally tries to take over your computer or phone.
I want to switch to the stock rom with the least amount of junk on it. If it also has a good Chinese/English keyboard with handwriting input that is a plus.
Also, just to make sure I'm on the right track, this is what should be done before I can change roms, right?
1) Get S-off
2) Install Clockwork Mod
3) Get permanent root
4) Write super cid
5) Change Stock Rom
Click to expand...
Click to collapse
the steps are fine ..but 3rd step is not required ...and 2)better have 4EXT recovery ..its better imho and between 4 and 5 there might be one more step ..which can only be decided after you told the current rom you are having (if running gb now ..for ICS you need to flash 3.32/3.33 firmware ..then ROM)
as for the ROM ..for simple STOCK like and fully customized with bloat removed ..try ARHD, insert coin or Elegancia
Hi,
If you go through the steps you mentioned:
1) Get S-off
2) Install Clockwork Mod (Try to get a PG58IMG.zip version of it, saves having to fastboot flash it)
3) Get permanent root
4) Write super cid
5) Change Stock Rom
You could stop at step3 and manuall delete stuff off the ROM you have. OR, what I'd probably do), and as mentioned you can skip step 3 if you're installing a new ROM. Go for a WWE (World Wide English) RUU if you want to keep completely Stock, you can then run ROMcleaner to remove some redundant crap.
Look for something like: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69. 3504.00U_11.22.3504.07_M_release_246089_signed.exe
It's ICS with Sense 3.6. The 401 in the above means it's WWE and will either need SuperCID (11111111) or HTC__001, it's completely unbranded.
You can find ROMcleaner at: http://forum.xda-developers.com/showthread.php?t=1217664
Thanks for the replies. I know I can root and then uninstall system apps. I don't really like doing that because you just don't know what else has been done to the rom. This Hong Kong rom won't let me use stock SMS (I know how to select default SMS program, it doesn't work on this rom) and doesn't have stock browser (it has some chinese version of Opera), is asking me if I want to invite my contacts to join all kinds of stupid networks, gets involved with my text messages, has some Chinese antivirus that keeps complaining, and all kinds of other crap. It's the worst rom I've ever seen. The WWE appears to be what I'm looking for. It's unbranded and shouldn't have carrier or region specific stuff. Youtube and other apps that don't ask me questions I can deal with.
I want root, for all of it's obvious benefits. I usually run stock, rooted and custom kernal with GPU overclock. But I'm not so sure I like sense, but I want to try a cleaner rom before I decide on sense.
I'm guessing I don't need to do the OTA update before I start the process. I also saw there were some special procedures for the latest ICS. I'll deal with that bridge when I get there. For now I just need a clean rom that doesn't bombard me with useless Chinese crap.
typci said:
Thanks for the replies. I know I can root and then uninstall system apps. I don't really like doing that because you just don't know what else has been done to the rom. This Hong Kong rom won't let me use stock SMS (I know how to select default SMS program, it doesn't work on this rom) or doesn't have stock browser (it has some chinese version of Opera), is asking me if I want to invite my contacts to join all kinds of stupid networks, gets involved with my text messages, has some Chinese antivirus that keeps complaining, and all kinds of other crap. It's the worst rom I've ever seen. The WWE appears to be what I'm looking for. It's unbranded and shouldn't have carrier or region specific stuff. Youtube and other apps that don't ask me questions I can deal with.
I want root, for all of it's obvious benefits. I usually run stock, rooted and custom kernal with GPU overclock. But I'm not so sure I like sense, but I want to try a cleaner rom before I decide on sense.
I'm guessing I don't need to do the OTA update before I start the process. I saw there were some special procedures for the latest ICS. I'll deal with that bridge when I get there. For now I just need a clean gingerbread that doesn't bombard me with useless Chinese crap.
Click to expand...
Click to collapse
There are a few WWE GB ROMs out there, the one I mentioned is pretty slick as it's ICS which seems to work better IMHO.
The following is mentioned in post 1776 and there abouts in the following thread: http://forum.xda-developers.com/showthread.php?t=1074559
http://shipped-roms.com/index.php?category=android&model=Pyramid
The OP has filefactory as the repository but it never worked for me so I gave up on it, looks like others had the same issue.
Just get a Europe one xxx.401.xxx. Avoid 1.24 if you want to go through OTA updates, I had issues with that, might have been me but .....
The ROMcleaner thing I mentioned is pretty good at removing the HTC extra stuff.
Of course, there are a few very nice custom ROMs out there. I was using Virtuous Inquisition (AOSP look and feel based on Sense but de-sensed as much as possible). I've not tried ARHD/IC and some of the others for a long time so can't comment on them.
Have fun and GL on your quest.
EDIT:
P.S. after applying the RUU you'll need to re-install CWM (again easiest was is if you have a PG58IMG.zip version of it) and then apply the root. It looks like the best root at the moment is SuperSU (reading some posts here from EddyOS).
Thanks again. I'm downloading:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504.07_M_release_253443_signed.exe
Now that I look again the 3.33 version is available, I probably should have downloaded that.
I've already got: ADB drivers, HTC Sync, HTC driver, java, pg58img(recovery.img), CMW 5.0.2.0, revolutionary-0.4pre4, su-2.3.63-efgh, and the unbrick stuff in case something goes wrong. Once I finished downloading the firmware I should be ready to go. I'll double check that all the files are good, re-read all the instructional threads, and then get started. My phone doesn't have a warranty, so I have to make sure everything is done correctly the first time.
I also found this:
http://forum.xda-developers.com/showthread.php?t=1459767
Will I need to flash this as well?
HTC phones are so much more complicated compared to the other phones I've rooted and flashed. On my Huawei phone you plugged the phone in to the computer, copied two files, and you were rooted and had CWM installed.
typci said:
Thanks again. I'm downloading:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504.07_M_release_253443_signed.exe
Now that I look again the 3.33 version is available, I probably should have downloaded that.
Click to expand...
Click to collapse
The 3.32 contains the 1.27.0000 HBOOT which can be unlocked (just done it myself). The 3.33 contains 1.29.0000 which at the moment cannot be unlocked.
As you're already S-OFF it probably doesn't make much difference. I'm on 3.32 at the moment, I don't know what the differences are between 3.32 & 3.33, I assume minor bug fixes.
I've already got: ADB drivers, HTC Sync, HTC driver, java, pg58img(recovery.img), CMW 5.0.2.0, revolutionary-0.4pre4, su-2.3.63-efgh, and the unbrick stuff in case something goes wrong. Once I finished downloading the firmware I should be ready to go. I'll double check that all the files are good, re-read all the instructional threads, and then get started. My phone doesn't have a warranty, so I have to make sure everything is done correctly the first time.
Click to expand...
Click to collapse
Unless you go back to HBOOT 1.18.00 or earlier revolutionary can't help to S-OFF, as you're already S-OFF you shouldn't need it.
Does the PG58IMG.zip you mention contain CWM 5.0.2.0 ?, I usually keep a copy about called PG58IMG-CWM5020.zip, then change the name when I want to install it. The reason I ask is that PG58IMG.zip is a generic name and can be used for many things. You'll need to pop the uSD card when it asks you to reboot.
As far as SU is concerned, look at: http://forum.xda-developers.com/showthread.php?t=1538053
I also found this:
http://forum.xda-developers.com/showthread.php?t=1459767
Will I need to flash this as well?
Click to expand...
Click to collapse
No the RUU is self contained and includes the firmware/radio. You might want to install HBOOT 1.27.0011 afterwards, IRC it allows fastboot commands. I think it's in that thread.
HTC phones are so much more complicated compared to the other phones I've rooted and flashed. On my Huawei phone you plugged the phone in to the computer, copied two files, and you were rooted and had CWM installed.
Click to expand...
Click to collapse
I know HTC seemed to have created hassles. I had an early Sensation and waiting for someone to work out how to S-OFF was a real pain.
GL
EDIT
REMEMBER to take a nandroid backup before you start, just in case ! Also remember that nandroid backups don't include HBOOT or Radio so if you need to revert you'd need to get them. Take a note of the existing baseband/radio & HBOOT.
gol_n_dal said:
Does the PG58IMG.zip you mention contain CWM 5.0.2.0 ?, I usually keep a copy about called PG58IMG-CWM5020.zip, then change the name when I want to install it. The reason I ask is that PG58IMG.zip is a generic name and can be used for many things. You'll need to pop the uSD card when it asks you to reboot
Click to expand...
Click to collapse
I found the PG58IMG-CWM5020.zip file you were talking about. I like that idea better.
gol_n_dal said:
REMEMBER to take a nandroid backup before you start, just in case ! Also remember that nandroid backups don't include HBOOT or Radio so if you need to revert you'd need to get them. Take a note of the existing baseband/radio & HBOOT.
Click to expand...
Click to collapse
Good point. I'll add that to the list of steps so I don't forget.
1) Setup ADB/fastboot
2) Get S-off
3) Install Clockwork Mod
4) Backup via CWM!!!!
5) Get permanent root
6) Write super cid
7) Change Stock Rom
Unfortunately the rom didn't download correctly, so looks like I won't be installing the rom tonight.
typci said:
I found the PG58IMG-CWM5020.zip file you were talking about. I like that idea better.
Good point. I'll add that to the list of steps so I don't forget.
1) Setup ADB/fastboot
2) Backup via ADB!!!!
3) Get S-off
4) Install Clockwork Mod
5) Backup via CWM!!!!
6) Get permanent root
7) Write super cid
8) Change Stock Rom
Unfortunately the rom didn't download correctly, so looks like I won't be installing the rom tonight.
Click to expand...
Click to collapse
The nandroid backup is via ClockworkMod, not certain what you're backing up through ADB/fastboot. Guess you could get Radio/Recovery etc. Never tried it myself, I like a simple life
There is no point applying SuperSU until after you have installed the new Stock ROM. You can change the CID directly with fastboot, it doesn't need root for that.
Shame about the download, at least the steps look about right.
Eek, I thought you already had S-OFF ? What HBOOT are you on at the moment ? If it's 1.18.0000 or earlier revolutionary.io is perfect, if it's later it's a different process.
Note that when you install the new stock rom via RUUxxxx.exe, it'll splat the custom recovery so it'll need to be re-applied.
Umm, I booted into HBOOT to get my HBOOT version and at the top of the screen it says:
PYRAMID PVT SHIP S-OFF RL
HBOOT 1.17.008
RADIO-10.11.9007.15_M
That mean I already had S-OFF, right? Well that was easy.
Actually the phone was smuggled into China to avoid taxes. The sellers probably had to get S-OFF to put a Chinese language rom on there. Which also would explain all the extra bloatware, probably was installed by the same people.
Also, I wasn't able to pull the images through ADB. Have to wait until after rooted.
UPDATE: Installed CWM, backing up now, then root. So far so good. I'll probably have to settle for using Titanium Backup to remove the unwanted apps for now. The second try at downloading the RUU also failed.
UPDATE: Rooted, through it probably was already rooted. Also checked the CID and it was already 11111111. Thanks Chinese smugglers. You did all the work for me. Now to finish uninstalling all the crap you put on my phone.
So actually, the only work I did was install the SU and backup my system.
Nice to see it going smoothly for you, and remember if you want to install ics, you need to flash a ics firmware 3.32 or 3.33. Or you'll be in a boot loop.
Sent from my HTC Sensation 4G using xda app-developers app
typci said:
Umm, I booted into HBOOT to get my HBOOT version and at the top of the screen it says:
PYRAMID PVT SHIP S-OFF RL
HBOOT 1.17.008
RADIO-10.11.9007.15_M
That mean I already had S-OFF, right? Well that was easy.
Actually the phone was smuggled into China to avoid taxes. The sellers probably had to get S-OFF to put a Chinese language rom on there. Which also would explain all the extra bloatware, probably was installed by the same people.
Also, I wasn't able to pull the images through ADB. Have to wait until after rooted.
UPDATE: Installed CWM, backing up now, then root. So far so good. I'll probably have to settle for using Titanium Backup to remove the unwanted apps for now. The second try at downloading the RUU also failed.
UPDATE: Rooted, through it probably was already rooted. Also checked the CID and it was already 11111111. Thanks Chinese smugglers. You did all the work for me. Now to finish uninstalling all the crap you put on my phone.
So actually, the only work I did was install the SU and backup my system.
Click to expand...
Click to collapse
LOL
As you say that was easy.
There are other sites that you can download 3.32.401 from as it's fairly common, have a look.
As you have a nandroid backup that you can recover back to if needed you can also try ROMcleaner.
I'm going to try a Jelly Bean ROM tomorrow so my nandroid backup will be vital )
A really nice fairly lightweight ROM is Virtuous Inquisition. As I said it's AOSP look and feel but has Sense backend, it's been de-sensed as much as possible.
Anyway Have Fun.
flare4000 said:
Nice to see it going smoothly for you, and remember if you want to install ics, you need to flash a ics firmware 3.32 or 3.33. Or you'll be in a boot loop.
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
I downloaded 3.32 Europe RUU. I plan to install that tonight after work.
typci said:
I downloaded 3.32 Europe RUU. I plan to install that tonight after work.
Click to expand...
Click to collapse
The RUU will contain everything you need and update firmware, Radio, Recovery, HBOOT, ..... and of course the ROM.
Remember it'll flatten the ROM so all saved messages, WiFi details etc. will be lost.
If for some reason you need to revert back to your existing ROM you'll need to downgrade the firmware to 1.17.0008, including the radio. I doubt you'll bother though when you're on 3.32.
help
Does Anyone Have
RUU PYRAMID hTC Asia WWE 1.77.708.148
???
rafael1369 said:
Does Anyone Have
RUU PYRAMID hTC Asia WWE 1.77.708.148
???
Click to expand...
Click to collapse
1. Don't double post, you posted this somewhere else as well.
2. Go and look in Football's Shipped ROM Collection thread.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
help
I know but it's urgent
how I can upgrade my frimware to3.33.x???
I have install dark forest without upgrade my frimware but my device still in htc logo
s-on
with touch recovery
and rooted
please help mee
If it's that urgent you should spend time familiarize yourself with the search button. There is Asskicker's guide how to flash roms with s-on in the general forum. Plus I gave you a link to RUU's in the other thread you posted in.
Sent from my HTC Sensation Z710e
matekaneve said:
If it's that urgent you should spend time familiarize yourself with the search button. There is Asskicker's guide how to flash roms with s-on in the general forum. Plus I gave you a link to RUU's in the other thread you posted in.
Sent from my HTC Sensation Z710e
Click to expand...
Click to collapse
Hi
I dont understand what u saied??
What can I do?
First android phone it's a AT&T One X, i'll be using it on the Bell network. Got a good deal on Kijiji and I didn't ask enough questions apparently, lol.
The phone is clearly not stock, took me several hours to piece that together. I get it, I'm a noob. I can tell it's running Cleanrom 4.5. I want to get it back to something close to stock. I plan to learn all about rooting/roms but I want to do it from a vanilla phone so that I get to actually do it myself.
I googled and found a tutorial (link). I deleted the 'su' file and superuser.apk. I followed the rest of the steps and it didn't seem to do anything, just rebooted back into cleanrom.
I kept googling and now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1859714
I guess i'm going to flash from an RUU now ? My CID is 11111111, so I've read that means I have superCID and any RUU will work. I want to get to JB eventually, so can I just flash direct to the Europe 3.14 JB from HTCRUU? Or go with one of the ICS versions?
Am I doing this right?
No no no!
Edit: still writing but wanted to say don't flash that ruu
If you want completely stock you need to use fast boot and boot into hboot and run fastboot OEM lock
(You may need to search around to learn how do that)
Then run this ruu. http://beta.androidfilehost.com/?fid=9390077933525139511
Sent from my One X using Tapatalk 2
that is for the wrong phone
only place you should look at is here AT&T, Rogers HTC One X, Telstra One XL
Its good your asking the questions now if you want to go completely stock run an ruu which means relicking the bootloader and running it ill link you to some guides in a sec
---------- Post added at 07:43 AM ---------- Previous post was at 07:43 AM ----------
Oh and like others said don't use that ruu! We have the one XL
cleanrom 4.5 is pretty good and close to stock but adds quick settings, debloated, power menu and some other tweaks. i would keep it how it is and just learn about how custom roms work. you can learn how to use twrp in its current state and maybe learn how to use some root apps.
just so you know your phone is the evita not the endeavoru.
Thanks for the replies.
I haven't tried flashing anything yet so don't worry. I'm taking it slow.
I've already been into fastboot. Figured that out because it was a required step in the guides I said I was trying to use. I have all the drivers installed and I'm able to talk to the phone via fastboot at the comand prompt.
LOL, thanks for letting me know my phone is Evita. I guess I can delete the 600mb RUU I downloaded
I'm a little unclear about HBOOT vs. fastboot. I can get into the bootloader and go to the fastboot USB mode... is this analogous to HBOOT?
So my steps right now are:
1) Download correct RUU, Evita 2.20 ICS - I've also seen people discussing 1.85 vs 2.20, why chose one over another?
2) fastboot oem lock
3) Install RUU while phone is in bootloader mode
That right?
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit. You lose the ability to do all sorts of mods to your phone, flash custom ROMs, use apps that require root like Adaway and Titanium Backup (and many others), remove carrier bloatware, activate tethering, and much more.
People have gone through great pains to find root methods for our device (and other Android devices). Many come on here looking for these root methods, for the awesome benefits that root means. I've seen very few, if any, people before you that have said "crap I accidentally got a rooted device, and don't want root". Think about that one for a while.
Plus, CleanROM 4.5 is already based on a more updated firmware version than any of the official AT&T RUUs. Plus it includes a lot of cool features and optimizations. Again, going from CleanROM to stock is a step backwards, not forwards, and you are gaining nothing, and losing quite a bit. Another thing about CleanROM, is that it is devoid of the AT&T bloatware (and there is a lot). Keep in mind that on the stock AT&T ROM, the bloat is not removable without root, so you are stuck with quite a few crappy apps that you will never use. That alone is a huge reason to have a rooted device. Also bear in mind that stock AT&T does not allow tethering (unless you have a data plan that allows it) and has other stock HTC apps (like FM radio) disabled. These cannot be enabled unless you have root.
Another thing, is that you will not get Jellybean any faster on stock than rooted. While its true that rooted, this phone will not be able to take the OTA when it rolls out (hasn't happened yet). But a stock rooted JB firmware will almost certainly be posted here on XDA, that is safely flashable on a rooted device. This often happens within a couple days of the OTA starting to roll out, if not faster. Sometimes even before the OTA, as sometimes the official RUUs get leaked before the OTA. All it takes is for a dev to get his hands on the files, apply root, and upload it here. Learning how to flash such a file to your device is very simple. Not much more than: download the file to your phone, boot into recovery, and press "install". So yet again, stock gains nothing over being rooted.
While its true that root is not for everyone. But if you've already found this place, and learned what things like RUU, bootloader, and fastboot are, then you probably already know more than most folks do about Android. You may feel in over your head, but it really just takes a few hours of reading to learn the fundamentals. And with that knowledge, you can do so much more with your phone than you can without root.
redpoint73 said:
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit....
Click to expand...
Click to collapse
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Sent from my HTC One X using xda app-developers app
echoboomer said:
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Click to expand...
Click to collapse
You should have said so from the start, then. This pretty much negates everything I just typed above.
Its admirable that you want to learn the process from scratch, and its the opposite attitude of most n00bs here.
My advice, as another mentioned above, is stick to XDA, and don't follow instructions from random Googled sites. Most of those sites don't clearly delineate between our phone (Snapdragon S4) and the international (Tegra3) version, and following instructions for the international version is a great way to brick your phone.
Other than that, lock the bootloader, run the RUU, and have fun. Also check your hboot version. If its anything but 1.14, don't run the 2.20 RUU. You will want the 1.73 or 1.85 RUU instead, as the 2.20 RUU will update the hboot to 1.14, which plugs the holes by which boot.img and radios can be flashed from recovery. Unless you want to create ever MORE work for yourself, as the hboot can be downgraded using a Linux computer, lol!
Be sure to check out my index thread, as most anything you will need is here: http://forum.xda-developers.com/showthread.php?t=1671237
Thanks, sounds like I'm on the right track.
Also check back to my OP, I did say that I wanted to learn the whole process but I wanted to do it from stock. sorry you typed all that out but in sure it will help some other noob down the line.
Last thing, 1.85 vs 2.20?
Sent from my HTC One X using xda app-developers app
ChummyDays said:
2.20 has the new hboot, and that means that you have to extract the boot.IMG out of the ROM and flash it through fast boot. With 1.85 you just flash the ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Cool thanks, I found a tutorial last night on how to extract boot.IMG from the ruu exe. I think I'm good to go.
Sent from my HTC One X using xda app-developers app
You might be confused. You shouldn't have to pull a boot.img from an RUU typically, only from a custom ROM zip. And only if you are on boot 1.14.
Sent from my HTC One X using xda app-developers app
Probably confused. Here's what I see in the boot loader.
***
Tampered
Unlocked
Evita PVT Ship S-ON RL
HBOOT-1.09.0000
Radio-0.19as.32.09.09_L
OpenDSP-v28.1.0.32.0504
eMMC-boot
***
Sent from my HTC One X using xda app-developers app
echoboomer said:
HBOOT-1.09.0000
Click to expand...
Click to collapse
This is what you want to see, and why you need to be sure to use the 1.85 RUU.
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.
Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.
Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita
So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.
Did you check the md5 of the recovery download?
Sent from my Evita
timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.