Hi guys,
I relocked the bootloader and did the OTA to the latest Telstra 1.89
So now that I have played with it, wanting to see how the stock ROM worked / looked I am wanting to go back to 1.81 so I can root and flash some of the great ROMs coming out.
However when I run the RUU (exe version) 1.81 to downgrade its coming up saying ERROR [140]: Bootloader version error.
I have been able to run this RUU before and go back with my XL but not now?
Any ideas.
Anyway I found away around this.
I unlocked the bootloader again (which I thought u needed root to do but turns out u dont), installed TWRP then booted to TWRP and loaded a new ROM!!!
awesome.
Related
hello guys i'm trying to go back to stock im on tmobile usa
but the thread if [ROM]Shipped Pyramid ROM
has two version of tmous and i dont know witch one is newest
RUU_Pyramid_TMOUS_1.27.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_192098_signed
or
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
and do i need to flash the stock radio or it already comes with the rom?
now i see some people are having new update
my friend from tmous is testing a sensation with the update. he said it dont have 2.3.5+
that the update is just to have better battery life and gps lock faster.
ok i know i need to be stock and maybe not rooted to get this update, but im concern of losing my s-off root
and cant root back
1.29 Is the correct Ruu, after flashing, the phone will boot up then check for update. After you install the update you will be on 2.3.4.
You will loose root but keep s-off. Just reroot, it's easy once you have s-off.
Sent from my HTC Sensation 4G using Tapatalk
The one you should run is the 1.29 and it already comes with the radio included.
You will loose recovery and root but will keep s-off and your phone will be 100% stock and ready to accept whatever updates are available.
Sent from my HTC Sensation 4G using XDA App
thanks guys my concern was i could root the same way i did if i update
one thing guys i download the file and its a exe format!
im on macbook
do i need windows?
or how do i extract the file
ok i download the fille to my pc ran all the instruction on the set up it recognize my phone but the phone didnt reboot or nothing
and it says fail now i try to do it again and this time it wont recognize my phone
after it reads my phone and i click update i get this error[155] unknown error
the rom update utility cannot update your android phone.
please get the correct rom update utility and try again.
i download the RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
What are ROM do you have on your phone before running the RUU? Do you have a Nandroid backup from before you flashed something custom? I had a similar error occur when I tried to run the RUU when I was running one of the 1.78 leaks, I had to restore my Nandroid from before I flashed the 1.78 leak and then the RUU worked.
Can i just run the RUU.exe without doing the CID on adb? I just want to confirm because I have read on the other thread that I have to run CID on adb before i run the RUU.exe from my computer in order to revert back to stock tmous rom.
disregard ---------
So which is current 2.3.4 or 2.3.5?
Yes, I am a newb to the Sensation, but not flashing in general. I have previously had hacked SamVibrant, HD2, and most recently, the G2x, so I know from a constant flasher's POV generally what Im doing.
I've been searching for answers to this for days now, and nothing really seems to work, so let me just start with what is going on.
CURRENT STATS:
-PHONE-TMO Sensation 4g
-S-OFF
-ROOTED
-BOOTLOADER-1.23.0000
-RADIO-10.14.9035.01_M
At the top of the bootloader screen it says ****LOCKED**** Which I am guessing is obviously in refrence to the bootloader itself.
Also I currently have the latest 4EXT recovery flashed. When I got the phone it had CWM 5.00.2 or whatever the latest was.
Just bought a Sensation from a guy on Craigslist, and when I got it, it had a CM7 AOSP ROM running on it. I definitely wanted ICS, so I started reading and trying to get it.
So I started here:
http://forum.xda-developers.com/showthread.php?t=1192300&highlight=hboot+1+23
I tried the PG58IMG.zip install via the bootloader, but kept getting errors and security fails. So I researched more and found a post about how to fix that, but the problem is that there is almost always a need to use Revolutionary, and I can't because it doesn't support the 1.23 bootloader.
I have also tried the PG58DIAG via bootloader, and still got mismatch and security errors.
I also just recently tried flashing back to the "REALSTOCKEXPERIENCE" stock ROM which was successful, but it didn't fix my bootloader or unlock woes. Lastly I tried the HTC dev Unlock, and it would not work, because When I got to the part where it attempts to connect to the phone via USB to do get the identifier token it would not connect. It just kept waiting. I tried resetting my phone and reloading the BL but it would not work.
Also I have noticed that I cannot get my phone to connect VIA USB to the PC when in FASTBOOT or Bootloader. Is that normal?
Please help a brother get some ICS on my new phone! I loved my HD2, although it was a bi#$% to flash sometimes, I loved it, and that is why I went with HTC again. This all makes me miss my Vibrant, where you could flash all day long and root without a computer... Good times....
You're already s-off, so most of the work has already been done for you. Make sure you have fast boot unchecked in power options in your current rom. After that, all that's left to do is check your cid. If you're supercid, then grab any 3.32 base firmware from one of the many rom threads in our dev forum, install it via bootloader, remove the firmware file from sd card (do it from pc after you power down the phone), then flash a rom. This will also upgrade your bootloader to 1.27 unlocked and change your radio to the latest. Don't forget to check md5!
If you're not supercid, then you'll need to find kohr-ah's firmware thread because he has corresponding firmware for all cids. Then grab any rom and enjoy.
As for connecting fastboot via USB, you need the htc sync drivers installed on your PC.
Sorry for lack of links. I'm on mobile and searching is a PITA on the phone.
/edit
Make a nandroid backup before you do any of this.
Thanks a bunch. I will give it a go a third time, but that is one of the problems that I am having, is that I can't flash anything via bootloader. I just get tons of errors...
Lets see if the third time is a charm.
EDIT: I still can't use revolutionary for Super CID because the bootloader is 1.23, but I used a Terminal window and the getprop ro.cid/mid and got this:
Cid-T-MOB010.... is this super CID'd?? I was looking for a reference post, but cant remember where I found it before.
no you are not super cid, it would say 111111. But your good everything is already done really.... Go to kor ah's noob friendly firmware thread, find the 3.32 firmware from T-Mobile with the tmobo10 included. Put it on the root if your SD and there you go flash an ics rom. Just remember to delete it after.
Sent from my HTC Sensation Z710e using xda premium
delete this please
wadill said:
no you are not super cid, it would say 111111. But your good everything is already done really.... Go to kor ah's noob friendly firmware thread, find the 3.32 firmware from T-Mobile with the tmobo10 included. Put it on the root if your SD and there you go flash an ics rom. Just remember to delete it after.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
^^ This. Kohr-Ah's thread is the way to go then.
On a side note, you might be able to write supercid after flashing the 1.27 bootloader because the one floating around is already unlocked by revolutionary. Why bother? Because it'll make things easier if we have to upgrade our firmware again in the future.
antiparadigm said:
Thanks a bunch. I will give it a go a third time, but that is one of the problems that I am having, is that I can't flash anything via bootloader. I just get tons of errors...
Lets see if the third time is a charm.
EDIT: I still can't use revolutionary for Super CID because the bootloader is 1.23, but I used a Terminal window and the getprop ro.cid/mid and got this:
Cid-T-MOB010.... is this super CID'd?? I was looking for a reference post, but cant remember where I found it before.
Click to expand...
Click to collapse
Forget Revolutionary. You are already S-OFF so you don't need the tool any more. All you need to do is flash the 3.32 firmware (it comes with HBOOT 1.27, ICS won't boot on 1.23) from >here<, and SuperCID (look here at step 4: http://forum.xda-developers.com/showthread.php?t=1192300).
Okay, I am on the right track now. I hunted and hunted, and finally found a PG58IMG that would flash on my bootloader. That put me on the 1.27 bootloader which allowed me to flash the unlocked 1.17 Bootloader which previously would not flash. now I am trying to get the RUU to flash me back to a non-Rooted ROM so I can reflash the 3.32 and then ICS... Once again, I miss my Vibrant's flashing simplicity... but it will all be worth it.
Thanks for your assistance, everyone with positive non-flaming comments. Expect your thanks buttons to get some love!
Someone else correct me if I'm wrong here due to misunderstanding that last post...
But if you're on the 1.17 bootloader unlocked and everything is smooth there, you should be able to flash the 3.32 firmware right not, then flash whatever ICS ROM you want. The current ROM should have no bearing on this. There is no reason to flash to a non rooted ROM just so you can immediately flash a new ROM.
You just need to have either Clockwork or 4EXT recovery installed to flash the ROM. (And you'll need 4EXT to flash a couple of them. Not all will work with Clockwork)
antiparadigm said:
Okay, I am on the right track now. I hunted and hunted, and finally found a PG58IMG that would flash on my bootloader. That put me on the 1.27 bootloader which allowed me to flash the unlocked 1.17 Bootloader which previously would not flash. now I am trying to get the RUU to flash me back to a non-Rooted ROM so I can reflash the 3.32 and then ICS... Once again, I miss my Vibrant's flashing simplicity... but it will all be worth it.
Thanks for your assistance, everyone with positive non-flaming comments. Expect your thanks buttons to get some love!
Click to expand...
Click to collapse
Thanks for the thanks.
Though once you had the 1.27 revolutionary bootloader, you could've just flashed an ICS rom right then and there and been done with the whole thing. The 1.27 bootloader that's floating around actually comes from the 3.32 (rom base) firmware so you would have been good to go. You really didn't need to revert to 1.17 hboot and flash a non rooted rom.
Don't worry, it really is easy flashing a Sensation, you'll see. It's just that a lot of our guides are outdated and end up confusing people who come into the scene post gingerbread.
/edit
Skipjacks is right. You can go from 1.17 hboot to 1.27 hboot (3.32 rom base firmware) without worrying about your current rom.
I had tried to flash the ICS Rom several times, only to have Boot loops and get stuck. I was following several guides posted here that say that you have to be on a non-rooted rom. I will give it another go to see if there is any change.
That's really weird. Which ICS rom are you trying to flash?
Did you get the T-MOB010 3.32 firmware from here and make sure md5 was correct? This firmware is really the only prerequisite for flashing a 3.32 base ICS rom.
Just keep in mind that 3.32 firmware only works for ICS and will bootloop a gingerbread rom.
There's a really good and simple step by step on how to flash ICS in the first post on the link. Check it out.
OMG It Works! I was boot looping like crazy and could not get anything to boot!
I am not sure but I think the problem may have been the radio, or the wrong Firmware for my CID. My phone would not work with the adb Radio.imgthough so I left it alone.
Correct me if I am wrong on the radio idea, but I flashed the 3.32 and I would get stuck at the White HTC screen. Tried SuperWiping and Flashing three different Roms and no-go.
Then I found this thread:
http://forum.xda-developers.com/showthread.php?t=1459767
I downloaded the right one per my TMO CID and was able to flash it, which also updated the Radio. After another superwipe and Rom Flashing, it worked!
THanks again for all of the help. You are all really appreciated. ALong with this whole community.
Haha that's Kohr-Ah's thread where we were telling you to go to for 3.32 firmware.
Honestly, I'm not really sure what was causing your bootlooping. There's so many little things that could cause a bootloop, it's hard to pinpoint. But hey you've got it running now so it's all good.
Welcome to ICS and welcome to the Sensation community.
I'm a Noob with a problem. I believe this is what happen i updated the one s via OTA 1.84.531 gave me hboot 1.140004 and radio 1.08ts.50.02.16 then i decided to Root. when I rooted i flashed to a rom that apparently broke my wifi. I did not have a nandroid backup (epic FAIL) so i found the 1.53 stock nadroid on a forum inorder to unroot and flash RUU 1.53 which should re flash the One s to stock and fix wifi. After re locking boot loader and trying RUU 1.53.531 and 1.84 get error "155" from RUU, so i tried OTA, OTA downloaded but fails on install. what i believe i need is a non rooted 1.84.531 nandroid backup to match my baseband and hboot. because my radio is most recent and Hboot is 1.14.0004 havent been able to flash radios. Please HELP hope i was clear
HTC one S TMO US
stock non root-1.53.531.16 710RD
base-band 1.08ts.50.02.16_10.08e.50.04l
hboot-1.14.0004
[fixed] one step missing when i was trying to unroot with RUU I needed to flash STOCK RECOVERY before updating. didnt even have to OEM lock. after that OTA worked fine fully updated One s and most importantly fixed WIFI.
Okay so i recently did a noob mistake and wiped the whole phone.
I'm a little frustrated now because TWRP wouldn't mount the sd card so i couldn't flash through there, and fastboot wasn't co-operating.
I then tried to RUU with the only rogers RUU i could find.. only to find out that it won't work because my version is like 1.93 something and the ruu is 1.73.
Anyways to make a long story short i finally got the sd card to mount, and flashed a rom that works for the moment.
But i still want to go back to the stock rom.
so far i tried flashing the 1.73 ruu with fastboot, and twrp (i don't even know if your supposed to but nothing was working anyways)
then i tried using ARUWizard to do it for me, which also failed.
So now i'm kinda stuck.
Any ideas how i can RUU with a different version?
I know Rogers just released JB which i did not upgrade to before screwing up.. so perhaps that will work in my favour.
Any help would be great! thanks
Asjoc said:
Okay so i recently did a noob mistake and wiped the whole phone.
I'm a little frustrated now because TWRP wouldn't mount the sd card so i couldn't flash through there, and fastboot wasn't co-operating.
I then tried to RUU with the only rogers RUU i could find.. only to find out that it won't work because my version is like 1.93 something and the ruu is 1.73.
Anyways to make a long story short i finally got the sd card to mount, and flashed a rom that works for the moment.
But i still want to go back to the stock rom.
so far i tried flashing the 1.73 ruu with fastboot, and twrp (i don't even know if your supposed to but nothing was working anyways)
then i tried using ARUWizard to do it for me, which also failed.
So now i'm kinda stuck.
Any ideas how i can RUU with a different version?
I know Rogers just released JB which i did not upgrade to before screwing up.. so perhaps that will work in my favour.
Any help would be great! thanks
Click to expand...
Click to collapse
Are you wanting to be rooted or not? If no then you have to fastboot oem lock
You need to flash 1.94 ruu you can dl it here. Run fastboot oem lock in fastboot then run the ruu.
http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Background story:
I was trying to unlock and s-off 1.73 at&t one x phone with 1.09 hboot so that i could install a custom rom... Having experience with some other phones I prepared myself, software, drivers and everything else and plunged into action... I successfully unlocked the phone using a compilation of tutorials since it's so old bootloader and all, as for root i'm not sure I actually managed to get it work, it complained most of the time of missing bin files although I flashed su through recovery again and it settled down. I couldn't s-off it in any of the way tutorials were suggesting, gathering that i would have to update with some newer RUU, so I quit and phone is still s-on. And then I did an incredibly stupid thing, i didn't do nandroid backup, i just wiped system and tried to flash a new rom to no avail... None of the roms won't get flashed, i tryed sense and cm based ones, i'm getting some partition error, something about 2,14 and 2,15, not sure since error reporting is not consistent... Now I'm stuck within recovery and bootloader, i'm unlocked but s-on, i can't flash system img through fastboot nor a custom rom through adb sideload it says that partition is too small.
So question is what am I to do? What is my safest way out? Should i try flashing RUU (the one that should be the original one 1.73.502) or could I run some newer RUU and which would be preferable? If I'm to run RUU 1.73, should I run it as an exe or should I try to flash it as a zip file? Does it matter that the phone is unlocked and s-on? Why won't the smaller cm roms flash, how small could the partition be and does it have something to do with android version (4.1, 4.2 etc)?
To get a working ROM on your phone you can download an old build of cm and flash that. The new builds require updated firmware but the older builds don't. Go here and download the bottom build (stable cm10), and you'll need to get the 4.1 gapps package from here.
Sent from my Evita
What recovery and version number? I have a feeling this is recovery related, more than anything.
Also, newer builds of CM10.2 require hboot 2.14 or 2.15, so that is probably what the error message you mentioned is about.
We should be able to get you back up in and running on the custom ROM of your choice. But if you do decide to go the RUU route, in order to run an RUU, you must relock the bootloader in fastboot. Then you should be able to run the RUU. 1.73 RUU is fine. DO NOT run the 3.18, as there is a bug where with SuperCID and S-on (and you now have both) will BRICK THE PHONE. But the 1.73 or 1.85 RUUs will be fine.
Run the RUU as an .exe. I don't see the point in extracting and running the ROM.zip. You would just be making the process harder than it should be, and also removing some of the safeguards, if I remember properly.
S-off should work on any hboot version. I believe I got s-off while on hboot 1.09.
I'm running twrp 2.5.0.0 recovery, is there newer version? It never crossed my mind that it could something to do with recovery, so I never looked it up... Perhaps I could change it, it's not like that's gonna ruin chance of restoring any previous backups i didn't make...But i'd rather update the phone's firmware just to get those hboot glitches off the way because it, i'm quite sure, obstructed the s-off process (i was getting few 9x errors during s-offing, mostly 99).
So I'd be safe running 1.85 RUU. Is there some other RUU you would recommend, preferably some which will make the whole process of rooting, SuperCIDing and s-offing easier?
Thank you for helping me out!
edit> I tried flashing oldest CM and it worked! Then, feeling safe and all, I flashed newest twrp recovery and then, to my utter amazement, it flashed other rom I was aiming for... So thanks, for that recovery tip, it saved me a lot of pain! Now all is left for me is to figure out that s-off thing...