I Dev_unlocked my sensation and installed the 1010 nightly of CM10 using 4ext. Worked swimmingly (with the exception of BT volume). Did the the OTA for the 1024 nightly. Killed my camera. I have wiped, formatted, flashed other JBs and ICSs, even the 1010 CM10, flashed 4.2 camera. I give up on trying to get the camera working. So I want to install the stock ICS that was on my phone. No, I did not do a Nandroid backup. (Lesson learned)
I know some of you are laughing about the Nandroid, I understand. But I think I have something almost as good, another Sensation! Is there an easy way to flash it over, or do I need to unlock (which I would hope to avoid doing), do a Nandroid from that , and then flash that in? In the end, all I want to do is put the phone the way it was for warranty repair.
Thank you in advance for any and all help.
Also, since I am on Cincinnati Bell, is a CID or RUU needed?
You could try Android revolution HD. That's the nearest to a stock rom. Or if you really want to go back to complete stock, then you need to relock your bootloader, then flash the appropriate ruu. For that, see HERE
matekaneve said:
You could try Android revolution HD. That's the nearest to a stock rom. Or if you really want to go back to complete stock, then you need to relock your bootloader, then flash the appropriate ruu. For that, see HERE
Click to expand...
Click to collapse
I want to return to actual stock for warranty service, and my CID is not on the list for the nor does that RUU seem to exist.
Have you had a look HERE or HERE and HERE as well?
matekaneve said:
Have you had a look HERE or HERE and HERE as well?
Click to expand...
Click to collapse
Yes I have. It's got a different skin because of it being with Cincinnati Bell Wireless, well, at least it has a Cincinnati Bell logo during the boot. The CID is HTC__017, which isn't on any list I have seen. That is also why I was asking about a RUU from my wife's phone if it was needed.
Related
Hello,
Wondering if anyone has got an Australian Vodafone stock rom (RUU) for my Sensation in case something goes wrong, and I need to un-root, un-flash etc.
I didn't backup my rom, when i initially flashed a custom rom -.-
Thanks in advance!
AND yes, I have used the search function and Googled.
Me too! Keen to root and explore the goodies available but would like the stock rom just in case....
Any suggestions for an alternative rom which I might subsitutue (perhaps UK Vodafone?) would be appreciated. BTW my phone: Build 1.45.862.3 CL157335 Radio 10.56.9035.00U_10.14.9035.01
OMG EPIC SAUCE! Please could you make a backup of your current ROM! Your my only hope of getting a stock rom, you'll need to follow the guide in this link until it tells you to make a backup of your current ROM using CWM (ClockWorkMod)
http://forum.xda-developers.com/showthread.php?t=1192300
This is your mission, if you choose to accept it. Backing up is crucial, you might end up in the same boat as me!
If you have ANY questions ask me or Google it, do not continue unless you know exactly what your doing.
It may seem a bit daunting but just follow the steps, word for word, and you'll get there easily. Thank you!
Don't let me down
Sent from my TripNiCE Pyramid using xda premium
Jikstah said:
OMG EPIC SAUCE! Please could you make a backup of your current ROM! Your my only hope of getting a stock rom
Click to expand...
Click to collapse
Jitkstah, the ease of backing up my current rom is not my concern, its being able to put things back the way they are if I have a warranty issue. Backing up my current rom after s-off and installing a custom recovery looks like a walk in the park compared to the process I went through rooting my last phone - a Legend...
AFAIK I'm not able to get back to s-on without the stock RUU for Vodafone Australia (or a rom which is similar). So I'll keep looking and asking for a bit longer... I may just bite the bullet and root, in which case I'll be happy to share my backed up stock rom but I don't think this will help you if you are trying to get back to s-on.
Cheers
EpicSauce said:
Jitkstah, the ease of backing up my current rom is not my concern, its being able to put things back the way they are if I have a warranty issue. Backing up my current rom after s-off and installing a custom recovery looks like a walk in the park compared to the process I went through rooting my last phone - a Legend...
AFAIK I'm not able to get back to s-on without the stock RUU for Vodafone Australia (or a rom which is similar). So I'll keep looking and asking for a bit longer... I may just bite the bullet and root, in which case I'll be happy to share my backed up stock rom but I don't think this will help you if you are trying to get back to s-on.
Cheers
Click to expand...
Click to collapse
Hmm, I didn't realize we needed the actual RUU to get back to S-ON. Thanks for pointing that out! Although I have been approached by one person, who shall not be named, who has offered me an official Vodafone RUU in exchange for the IMEI number the phone shipped with and a price of 11 Euros, I had to turn it down as I am not able to pay through PayPal. Perhaps you are able to do this? And hopefully be generous one day, to maybe, hand it on to me?
IF you are interested contact me via PM and i'll get you in contact with the "dealer".
You don't need the RUU at all. Once you've restored your backup you just run the command for S-ON via fastboot.
The reason an RUU is helpful is it flashes the complete ROM to the phone so the bootloader and recovery are also replaced with stock versions. Without an RUU you have to do it all manually and then S-ON again
Beautiful, thanks Eddy! So I just have to find the stock boot loader and recovery. Any ideas where? And EpicSauce are you able to backup your ROM or do you still want to continue finding an RUU, which is impossible
Sent from my TripNiCE Pyramid using xda premium
EddyOS said:
The reason an RUU is helpful is it flashes the complete ROM to the phone so the bootloader and recovery are also replaced with stock versions. Without an RUU you have to do it all manually and then S-ON again
Click to expand...
Click to collapse
Thanks EddyOS, I didn't realise you could S-ON after restoring a nandroid backup... but that makes sense. As you say, after restoring the stock ROM you would be left with a different bootloader and custom recovery. How difficult (and risky) is it to restore the stock bootloader and recovery manually?
If I needed to return the phone for warranty I would want to remove all evidence the phone had been rooted. Jikstah - if I go this route I'm happy to share my backed up ROM.
EpicSauce said:
Thanks EddyOS, I didn't realise you could S-ON after restoring a nandroid backup... but that makes sense. As you say, after restoring the stock ROM you would be left with a different bootloader and custom recovery. How difficult (and risky) is it to restore the stock bootloader and recovery manually?
If I needed to return the phone for warranty I would want to remove all evidence the phone had been rooted. Jikstah - if I go this route I'm happy to share my backed up ROM.
Click to expand...
Click to collapse
Okay then, keep in contact for the meanwhile!
Thanks man
EddyOS said:
You don't need the RUU at all. Once you've restored your backup you just run the command for S-ON via fastboot.
The reason an RUU is helpful is it flashes the complete ROM to the phone so the bootloader and recovery are also replaced with stock versions. Without an RUU you have to do it all manually and then S-ON again
Click to expand...
Click to collapse
But will the Vodafone Australia know that it has been rooted that way?
This might sound like a stupid question, but I really hope it is not.
I decided to test the waters with ICS and tried a couple of ROMs (Sense and Virtuous) that run the latest version of Google's OS. Sadly, in my opinion ICS is still not fully ready for our devices, as everything seems too slow in my opinion, and I also don't like the fact that we do not have access to some of the best kernels yet.
So, I decided to go back. Flashed a 2.3.x ROM and... I got a boot loop?
I made sure I was not making a mistake, so I wiped everything and tried again. Same issue. Wiped again and tried a different 2.3.x ROM and again, I got boot loops.
Then I decided to go back to ICS Virtuous Inquisition and everything worked.
Is this a known issue? Do I have to do something in order to return to 2.3.x? For example like flashing a previous firmware/Radio combo?
I would appreciate any help you can give me.
I have done it a couple of times. Once on my Droid 3 and again on my Galaxy tab 10.1. So it will depend on what you have. But in both cases. I was able to find an original ROM update. With the Galaxy tab I found it on the Samsung website, that took it right back to original condition, and with the droid 3, I found it hear in the forums.
I did it too. I didn't back up my ROM. But if you back up your ROM in the future, you wont have this issue. I'm still careless and don't back up my ROM, but I don't go backwards to often.
What Phone do you have? There can be other options as well.
John Phillips
Please click thanks
I'm having the same problem. I get to the HTC logo then the phone reboots indefinitely. I'm trying to learn on downgrading the firmware and see if it solves the problem.
Yes, you'll need to downgrade your HBOOT.
If you have supercid, or a T-Mobile handset, this will take you back to 1.17: (I used it myself to go back to a GB rom after trying out ICS) http://www.mediafire.com/?4t9pep3e5hx6ljm
Rough instructions on how to flash it if you're not familiar: Rename it PG58IMG.zip and put it on the root of your sdcard, and boot into the bootloader. It will ask you to flash the file, choose yes and let it go.
And of course, you can then restore any nandroid backup of a GB rom, or install a fresh one, etc.
(if you're not supercid, just edit the android-info.txt file inside the zip and add your CID)
p.s. don't worry about downgrading the radio; I went back to a GB rom without downgrading the radio and everything is fine. Just downgrading the HBOOT is enough.
Downgraded to 1.17 and it still reboots, though I did a restore instead. I'll a fresh flash now.
Still doesn't work. How do I get to 1.23 again? I'm so confused now.
phantomblu said:
Downgraded to 1.17 and it still reboots, though I did a restore instead. I'll a fresh flash now.
Still doesn't work. How do I get to 1.23 again? I'm so confused now.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1459767
Use the 3.12 firmware and you can run both ICS and GB based roms, I run, CM7 (GB) and V Inquisition or V Quattro (both ICS).
I'm surprised you didn't like ICS, they're all alphas but pretty slick considering.
Yea man try inquisition from virtuous. Its extremely stable and able to be used as a daily. It feels like a finished rom.
Sent From My steak using A1 steak sauce app (Sensation)
Downgrade ur firmware and flash any gb rom.
(Hopefully) my last question. I have SuperCID (set to 11111111 as specified in that other instruction topic). Does this mean I can flash any previous firmware and even downgrade? I was not aware that this is what it does.
If I revert back to 1.17, will I lose S-OFF and have to repeat things?
Also:
gol_n_dal said:
http://forum.xda-developers.com/showthread.php?t=1459767
I'm surprised you didn't like ICS, they're all alphas but pretty slick considering.
Click to expand...
Click to collapse
Well, either I am extremely picky (which I am), or I did something wrong. But I do not consider these ROMs 'pretty slick'. I have owned far too many Android phones and tablets up until today, and given the dual-core CPU and advanced GPU inside Sensation XE, I was expecting the fastest, best, most fluid and slick experience yet, and... it does not deliver. I thought ICS allow the OS to use the second core, but again, something must be wrong because it certainly doesn't feel like it.
I am not saying that the experience is bad, by any means. Things are slick and fluid most of the time. But you do get occassional split-second hicc-ups, and I also have this 'feeling' that the framerate while moving around in Nova is below the best I have seen. So there you have it.
Many thanks is in order to all that helped.
gol_n_dal said:
http://forum.xda-developers.com/showthread.php?t=1459767
Use the 3.12 firmware and you can run both ICS and GB based roms, I run, CM7 (GB) and V Inquisition or V Quattro (both ICS).
I'm surprised you didn't like ICS, they're all alphas but pretty slick considering.
Click to expand...
Click to collapse
I do like it. It's just I can't get rid of the wakelocks no matter what I do.
Can I use 1.17 hboot for quattro or do I need a different hboot and where do I get it?
Sent from my Sensation using xda premium
grcd said:
(Hopefully) my last question. I have SuperCID (set to 11111111 as specified in that other instruction topic). Does this mean I can flash any previous firmware and even downgrade? I was not aware that this is what it does.
Click to expand...
Click to collapse
Yeah, it means you can flash any firmware without worrying about which operator it's for. Downgrade should be no problem either.
grcd said:
If I revert back to 1.17, will I lose S-OFF and have to repeat things?
Click to expand...
Click to collapse
No, you won't lose S-OFF.
Have u tried inquisition yet before u go back? Its amazing
Sent From My steak using A1 steak sauce app (Sensation)
hardrockinandroid said:
Can I use 1.17 hboot for quattro or do I need a different hboot and where do I get it?
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
For that you need 3.12 or 3.24, you can get them from mike1984's firmware sticky.
As the title states, I have a possible brick on my hands, the phone isn't mine and the person who uses it doesn't really mess with overclocking and such, it was running Miks rom GSM, and not overclocked (running at 1.18ghz) No overvolt either, it is an s-off device, before this it was a fully functional sensation.
Basically what i'm told is that the phone was in use and it just switched off.
No lights, no power, have tried three batteries, about 10 chargers, different usb cables, can't get to bootloader or recovery, adb won't recognise it, it appears to be just a dead phone, personally i'm guessing it's the mainboard but i thought i'd ask anyway, there are no signs of water damage or major droppage.
Popped over to dexters unbricking project but as i said the phone won't come on so it won't work.
As i said before it's not my phone, but i'd like to do a friend a favour if i could.
Any ideas?
Before anyone asks, I cannot get to the bootloader or recovery.
Many thanks.
Hope you get it working..but it's becoming quite common and no one seems to have any ideas. Mine did the same thing...and I just had the motherboard repaired!
Yeah, here is the other thread.
http://forum.xda-developers.com/showthread.php?t=1624293
On such a popular Rom it is a bit unsettling.
Is it firmware, radio, kernel, or rom?
I hadn't seen this many Sensations die like this back on Gingerbread.
I am not sure...seems to have happened on a few different ROMs...so maybe it's not a specific ROM? I just got mine back and rooted and S-off as I needed the root to unlock the simlock...but I am scared of installing any custom ROMs or radio etc....I am thinking maybe I'll just wait for the official t-mobile ICS update...
gustav30 said:
Yeah, here is the other thread.
http://forum.xda-developers.com/showthread.php?t=1624293
On such a popular Rom it is a bit unsettling.
Is it firmware, radio, kernel, or rom?
I hadn't seen this many Sensations die like this back on Gingerbread.
Click to expand...
Click to collapse
I'll be starting a thread to determine just that... I have my suspicions, but I'd like to know in one place what everyone was running.
I was running ARHD 6.6.2 Just flashed the ROM.. and seem to flash fine, able to boot up. Even reinstalled all the apps...then while calling...had this long tone from the phone...and phone was unresponsive...I pressed power button.. and it turned off.
The first time..it actually turned back on....so I thought maybe it's an issue with reinstalling the apps. Then when I called again...after 30sec-1 min...same tone again...then phone turned off and never turned on again...Battery was 100% charged.
I updated the correct firmware since I was already using insertcoin ICS ROM for a while before changing to ARHD 6.6.2
I am scared of installing a custom ROM now....I have rooted the phone again, S-off, Clockwork, superCID....but I am thinking maybe I should just wait for teh official update for ICS and leave it as that.
Can I just to OTA update when it comes out?
newr said:
Can I just to OTA update when it comes out?
Click to expand...
Click to collapse
Change your CID back to T-MOB010 and you can...
FWIW, what kernel were you running when it took a dump?
I didn't install any custom kernel...I just installed the firmware as suggested.. and also the radio file that ARHD page says we should flash for T-mobile phones....
then flash the ROM as usual. Everything worked...the phone died while running the ROM.
So I need to change CID again to do OTA update? It's ok to leave it rooted, Clockwork, and S-off? Maybe I shouldn't have changed to super CID then?
newr said:
I didn't install any custom kernel...I just installed the firmware as suggested.. and also the radio file that ARHD page says we should flash for T-mobile phones....
then flash the ROM as usual. Everything worked...the phone died while running the ROM.
So I need to change CID again to do OTA update? It's ok to leave it rooted, Clockwork, and S-off? Maybe I shouldn't have changed to super CID then?
Click to expand...
Click to collapse
You can leave it rooted and s-off (in fact you WANT to keep s-off), make sure your stock rom is un-modified, and you need to go back to stock recovery. If you leave superCID then it will not detect the update. It needs to refer to CID to find the correct update package for your device...
I haven't modify the Rom that's on here now. So stock recovery means removing clockwork ? And changing CID...is there a tutorial to do that?..
newr said:
I was running ARHD 6.6.2 Just flashed the ROM.. and seem to flash fine, able to boot up. Even reinstalled all the apps...then while calling...had this long tone from the phone...and phone was unresponsive...I pressed power button.. and it turned off.
The first time..it actually turned back on....so I thought maybe it's an issue with reinstalling the apps. Then when I called again...after 30sec-1 min...same tone again...then phone turned off and never turned on again...Battery was 100% charged.
I updated the correct firmware since I was already using insertcoin ICS ROM for a while before changing to ARHD 6.6.2
I am scared of installing a custom ROM now....I have rooted the phone again, S-off, Clockwork, superCID....but I am thinking maybe I should just wait for teh official update for ICS and leave it as that.
Can I just to OTA update when it comes out?
Click to expand...
Click to collapse
Did you try flashing the new 6.6.4 ARID? Came out on May 6th
Sent w/ HTC Sensation 4G (Z710a) XDA Premium
another one with the same problem :S
namila007 said:
another one with the same problem :S
Click to expand...
Click to collapse
But is it a HTC problem or a flashing custom stuff problem?
I don't know what I should do now...if I should just wait for ICS update...but now I'll have to remove superCID and somehow flash stock recovery or something
Hi.
So I am T-Mobile US. I am running GB with ROOT.
I want to update to ICS update which just came out.
I can't do OTA since it won't let me (since i am rooted?).
I went ahead and downloaded this official one from here:
http://forum.xda-developers.com/showthread.php?t=1654347
Now here is my Q:
Should I just flash this ROM after putting it in my SD Card?
Should I wipe? Or can I keep all the data (which I prefer)?
Thanks a million!
You can't just flash that. You'll need the 3.32 firmware, preferably the T-Mobile version.
sshede said:
You can't just flash that. You'll need the 3.32 firmware, preferably the T-Mobile version.
Click to expand...
Click to collapse
Thanks so much. Will I find this here in the forums, or at T-Mobile site? Thanks
benyben123 said:
Thanks so much. Will I find this here in the forums, or at T-Mobile site? Thanks
Click to expand...
Click to collapse
IF you want to do OTA update...you need to make sure your recovery, CID, and your current software is the one that's supported by T-mobile OTA. Not sure if you are running a custom GB or a stock one. But basically, if you're on stock but you just rooted it...it's fine to have it rooted...in fact you want to have it rooted and S-off before doing the update
Read this http://www.htcsensationforum.com/ht...to-downgrade-upgrade-gb-lt-gt-ics-a-tutorial/
There are also several post about it here. But bascially you need the software version that's supported by T-mobile for the update (they list those in their update info). So either you run a RUU to bring you to the stock version of these software...including stock recovery...and also change your CID back to T-mobile one...TMOB010 I think..but just double check.
IF all you've change is root and CID...then you just flash the stock recovery that's for the version of the stock software you have now and change the CID back to t-mobile..then it should work.
I had trouble initially but turns out the recovery file I had was probably not the correct version so it kept aborting. Worked fine after I flashed the right recovery.
newr said:
IF you want to do OTA update...you need to make sure your recovery, CID, and your current software is the one that's supported by T-mobile OTA. Not sure if you are running a custom GB or a stock one. But basically, if you're on stock but you just rooted it...it's fine to have it rooted...in fact you want to have it rooted and S-off before doing the update
Read this http://www.htcsensationforum.com/ht...to-downgrade-upgrade-gb-lt-gt-ics-a-tutorial/
There are also several post about it here. But bascially you need the software version that's supported by T-mobile for the update (they list those in their update info). So either you run a RUU to bring you to the stock version of these software...including stock recovery...and also change your CID back to T-mobile one...TMOB010 I think..but just double check.
IF all you've change is root and CID...then you just flash the stock recovery that's for the version of the stock software you have now and change the CID back to t-mobile..then it should work.
I had trouble initially but turns out the recovery file I had was probably not the correct version so it kept aborting. Worked fine after I flashed the right recovery.
Click to expand...
Click to collapse
Wow thanks for your time. Too many things i here i don't even know what they mean. I guess I will just pass and stick to my GB. Safe way.
Thanks a lot
all you have to do is flash this file from recovery. it could not be any simpler. http://www.4shared.com/zip/34Y1RPQf/Sensation_33253114.html
you will lose some things like your settings but you will keep all your backed up apps and contacts.
If this is covered somewhere else please post a link. I can't find one.
I've got a locked non-rooted phone and the 1.84 update fubar'd my radio. Is there a way that I can reflash the 1.53 ruu without unlocking my phone? That version worked fine for me (yeah, I know, why did I apply the update? I'm an update whore. I admit it).
I'd like to keep it as stock as possible in case I have to return the phone but I'd also like to try going back to 1.53 while (if) tmo fixes the problems with the 1.84 update.
I've got lots of experience flashing custom and stock roms on my Vibrant but I've only had the One for a couple of weeks.
I'm starting to think I might have to unlock, flash the ruu and relock.
Sound about right to those who have done this kind of dance?
If your talking about the bootloader then it needs to be locked and also a stock recovery, im about to do this once my RUU has finished downloading
Contact T-Mobile and let then know it borked you're radio. They'll have you contact technical support and they will walk you through a Master Reset. This will put you back on 1.53.
Sent from my HTC One S using XDA Premium
A master reset doesn't roll back the ROM. I've just discovered that first-hand.
After a MR I still have 1.84.x
On the other hand, it's a factory new 1.84.x except that my SD card contents are still there
i cant seem to find the stock US tmobile ruu 1.53. does anyone have it?
If you've got 1.84 the 1.53 ruu won't help you. It'll refuse to load
michaelh99 said:
If you've got 1.84 the 1.53 ruu won't help you. It'll refuse to load
Click to expand...
Click to collapse
well im using the 1.53 now but i want to get rid of the tampered thing on the bootloader or whatever. but the ruu i have is this 1.53.531.16_R2 CL47441 release-keys and someone said the STOCK ROM for original TMOUS is 1.53.531.16 CL47441 release-keys. notice there is a R2 in my ruu and it doesnt have that on the stock tmobile rom which is weird.