Related
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
splayer7 said:
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
Click to expand...
Click to collapse
Exactly what has been said. There is no unrooting or S-On restoring at this time. I would just wait if you haven't already. HTC Released their source codes today. Its only a matter of time before an easier root is available with unroot, and S-on.
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
kevinliu2336 said:
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
Click to expand...
Click to collapse
do we have any confirmation on this working correctly
Tried it, resets your ROM but doesn't reset s-off
Guys.. There is about a 25% chance at best that HTC will actually check the boot loader status before providing warranty service. Even if you are unlucky and they do, if you make enough noise they might make an exception and let you off the hook. I think that as long as the issue that you are trying to resolve isn't a direct result of s-off or root, it should be fine.
splayer7 said:
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
Click to expand...
Click to collapse
Flash an official RUU, and the device will be S-ON! TESTED!
lge73 said:
Flash an official RUU, and the device will be S-ON! TESTED!
Click to expand...
Click to collapse
Are you sure man? Somebody else above tested and found the opposite..
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
smoochiezz24 said:
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
Click to expand...
Click to collapse
I used the rom.zip file included in an untouched RUU, and I checked it includes HBOOT, also saw version change when I went into HBOOT.
It does NOT reset S-OFF back to S-ON.
I dont know if when you flash it reads S-OFF so keeps it, for users who genuinely had S-OFF?
I have personally tested this, and can confirm that using HTC's stock RUU does not return the phone to S-ON. However, it did remove the top area that says revolutionary, so now it appears as though I have a factory S-OFF device
Sent from my HTC Sensation 4G using XDA App
bummer.. I really hope there is a way to reverse s-off, just in case. but then again, I do have insurance so I guess I could say it was 'stolen' if I really need to get it replaced
prank1 said:
For those worrying about warranty issues..
You can try flashing the correct RUU for your phone.
IF that doesn't get rid of -revolutionary- s-off, then you can flash the ENG HBOOT (which gets rid of -revolutionary- but gives you ENG S-OFF) then you can flash the correct RUU for your region (which will definitely get rid of ENG S-OFF, and make you official stock HBOOT S-ON)
Click to expand...
Click to collapse
Try flashing ENG HBOOT, then the RUU afterwards.
I am going to try to get my phone back to S-ON now, just to test everything
EDIT
Hmm, very odd indeed, after flashing the RUU I have 'stock' Radio S-OFF (no -Revolutionary-) , I tried fastboot oem write secuflag 1 and fastboot oem writecid HTC__001 but I am still Radio S-OFF.
Just so people know, flashing full RUUs, even HBOOTs do NOT get rid of Radio S-OFF. Thats why it is favored by people, it can only be turned S-ON specifically by tools which may be released for the Sensation in the near future. I thought these tools only sent the commands that I tried to change the Radio security status. It would appear not.
However
There is no need to worry, Radio S-OFF probably won't void your warranty (if you sent it to a HTC repair center), as long as you have the correct CID and ROM installed you should be fine.
If I remember correctly, with the past Android phones, some people randomly got S-OFF (like sensation users did) out of the box. The HTC repair center didn't care. They don't like custom ROMs, custom HBOOTs, rooted ROMs, etc
**VIDEO AT THE BOTTOM!!**
Requirements
ADB: Click here for windows or Linux or download from) Sensation S-off guide
You Will Need HTC Drivers http://forum.xda-developers.com/atta...7&d=1312092669
*DO NOT ADD "" TO COMMANDS!!!
1. On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
2. Create a new folder called "adb" and extract the files from adb.zip (link above) into it. Make sure it doesn't create another folder in the adb folder when extracting
3. Install HTC USB Driver 3.0.0.007.
4. Press Windows + R, it will open Run. (linux users ignore this)
5. Type "cmd". (or open terminal on linux)
6. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode
7. On your phone, Go to Settings > Applications > Development > Enable USB Debugging
8. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
9. If it is recognized, then download your official RUU, please get the same/similar version that came with your phone. If you fail then you might Brick your Device!
10. Start RUU.exe and follow on screen commands.
11. After reboot, turn phone off without fastboot on, or, take out battery and then Hold Volume down button and power on.
12. Bootloader should now read Pyramid PVT Ship S-OFF RL.
13. Remove and reinsert the battery. Press power on as normal
Optional To change to stock S-ON
PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A SMALL RISK OF BRICKING
15. Boot up into the new ROM and On your phone, Follow steps 4-8 above then continue here
16. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja who came up with this)
17. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
18. Bootloader should now read Pyramid PVT Ship S-ON RL.
19. Remove and reinsert the battery. Press power on as normal
USE IF SEMI BRICKED
20. IF IT DOESN'T REBOOT and bootloader says ***Security Warning**
Remove and re-insert the battery and go back into bootloader and holding Volume Down +power button select fastboot
21. Run RUU.exe to reflash stock rom. (the one u just downloaded in step 1) and then reboot. It should work now
*NOTE*
This removes ROOT and custom recovery!!
I take No Credit for the Idea!
I am in no way responsible if YOU brick your phone!
If you want to add stock SuperCID AFTER you installed RUU.exe, Then Go Here For CID's, They Must Be Your Mobile Carriers... Ex: T-Mobile USA = (Carrier"TMUS") (CID"T-MOB010")
CID CANNOT BE CHANGED AFTER S-ON, it must be done while S-off
I added a video to download! you may need to re-record
http://www.mediafire.com/?ibn7168nd2ywr5d
Good Day to You and Good Luck!
Feel free to Comment for Help
If you need any help feel free to post comments
well thanks for this guide, but we're all hoping to never send our beloved Sensation in warranty return
Yeah, I would hate to send it in.
Read Me!
Everyone should do this and then reinstall custom recovery and root. Only because if sent to warranty and they see Revolution, you are screwed.
plocri said:
well thanks for this guide, but we're all hoping to never send our beloved Sensation in warranty return
Click to expand...
Click to collapse
Nice write up and VERY Noob friendly! I was reading through and in my head, half the time, going well duh. Then it clicked, you said Noob friendly. I think it will help almost all Noobs but there will be at least ONE that F's it up!
Again, nice write up!
setzer715 said:
Nice write up and VERY Noob friendly! I was reading through and in my head, half the time, going well duh. Then it clicked, you said Noob friendly. I think it will help almost all Noobs but there will be at least ONE that F's it up!
Again, nice write up!
Click to expand...
Click to collapse
Thanks, Its funny cause im a junior member and im writing NOOB friendly threads
Well was a junior member when i wrote this lol
Just to let you know if you stay with S-OFF HTC will now...
Hboot is a different version from HTC, it ends in 10xx rather than 00xx
So even if it doesnt say revolution, they still can tell
Best to restore to S-ON which is a bit risky if you dont follow instructions to the t..
Cheers
P.S. Also why are you giving SuperCid since everyone will need to flash their Stock RUU anyway?
broncogr said:
Just to let you know if you stay with S-OFF HTC will now...
Hboot is a different version from HTC, it ends in 10xx rather than 00xx
So even if it doesnt say revolution, they still can tell
Best to restore to S-ON which is a bit risky if you dont follow instructions to the t..
Cheers
P.S. Also why are you giving SuperCid since everyone will need to flash their Stock RUU anyway?
Click to expand...
Click to collapse
nope my hboot is 1.17.0008, which is stock T-Mobile HBoot. And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
alphadog32 said:
nope my hboot is 1.17.0008, which is stock T-Mobile HBoot. And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
Click to expand...
Click to collapse
If it is stock hboot then you have missed all fastboot flash functionality that alpharev has put in their hboot.
Can you flash radio, splash and so on with this hboot you have now?
broncogr said:
If it is stock hboot then you have missed all fastboot flash functionality that alpharev has put in their hboot.
Can you flash radio, splash and so on with this hboot you have now?
Click to expand...
Click to collapse
Yes I can flash.
alphadog32 said:
And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
Click to expand...
Click to collapse
By encouraging people to install SuperCID, all you are doing is making their phone more traceable for tampering if it goes back for warranty, and allowing them to install the wrong RUU. If they don't have SuperCID, they'll get 'ERROR[131]: CUSTOMER ID ERROR' if they try to flash the wrong RUU and it will stop without flashing anything to the phone.
I know you're just trying to help, but all they have to do is run the latest released RUU for their region. Nothing more.
alphadog32 said:
Yes I can flash.
Click to expand...
Click to collapse
He means use 'fastboot flash' commands which you can't with the stock hboot.
Oh. I thought he meant ROM installing and installing root. Thank You.
Sent from my HTC Sensation 4G using XDA App
How do i know if CWM is removed?
Hi,
i did all the steps and get s-on back with stock rom.
my question is how do i know whether i have removed CWM as well? when i vol down + power, it went into bootloader. it's the same screen as when i have CWM installed. the only difference is the S-on, at least the ones i can recognize is different.
thx
here is what i need to know... i am actually getting and exchange and have to send this back in because the vibration stopped working. It as TMOUSA Sensation. So far here is what i have gathered about my phone:
Baseband/radio version: 10.42.9007.00u_10.11.9007.15_m
Build number: 1.35.401.1 cl84734
hboot: 1.17.1011
CID: T-MOB010
I looked at the http://forum.xda-developers.com/showthread.php?t=1074559 page and they listed two RUU for TMOUSA:
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
and
RUU_Pyramid_TMOUS_1.27.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_192098_signed
which one of these am i suppose to use? Will my baseband/radio be updated to a different band/radio?
radiikal said:
Hi,
i did all the steps and get s-on back with stock rom.
my question is how do i know whether i have removed CWM as well? when i vol down + power
thx
Click to expand...
Click to collapse
i will try to answer ur question.. after u went thru all the process to get s-off with the idea of installing custom roms using CWM, u will get into recovery with the steps power+vol down them u scroll down and pick recovery taking u to CWM..try now and it should take u to stock recovey, after u finally figure it this out by ur self..im pretty sure u will feel like u can conquer the android world..
Pick 1.29.xxx.x for TMOBILEUSA
HTC Sensation
RESTORED TO S-ON
STOCK HBOOT
STOCK ROM
ROOTED
Is this safe?? im planning to remove my superuser,root,CWM but keep S-OFF because im tired of worrying that my phone will die when i'm out and i won't be able to charge it
If you mess up, you may brick your device!
AFTER i DL the RUU, where do i paste it at?
Hi folks,
I've got a T-Mobile branded Sensation, no idea how long they will take to get the 2.3.4 update out, probably months.
I want to S-OFF, Super CID etc and flash something else or just use a Euro RUU.
Problem is, for warranty purposes, I need to back up my current rom or obtain the T-Mobile RUU.
Is there anyway I can dump this rom first?
I've checked the big list of roms for the Sensation, lots of US ones there but nothing for T-Mobile Uk.
Thanks
Backup stock ROM:
1. S-OFF
2. Install CWM
3. Backup with CWM
Job Done!
Restore stock ROM:
1. Restore backup
2. Flash stock recovery
3. Flash stock HBOOT
4. Run S-ON command via adb
Obviously the ROM you restore will have all your personal data so a hard reset after making sure it boots up would be wise to go back to a 100% 'out the box' state
i,m uploading the official TMO uk 1.34 RUU now link to follow
link
http://dl.dropbox.com/u/38694724/RU...0U_10.51.9007.27_M3_release_196473_signed.exe
Where'd you get that?
west2cool said:
i,m uploading the official TMO uk 1.34 RUU now link to follow
Click to expand...
Click to collapse
That's excellent, cheers!!! Definately UK?
It would have to be as the T-Mobile US ones are 1.27/1.29
EddyOS said:
It would have to be as the T-Mobile US ones are 1.27/1.29
Click to expand...
Click to collapse
Would make life alot easier if it is the real deal.
Very true but I'd still backup your ROM as it stands anyway before flashing anything new
EddyOS said:
Where'd you get that?
Click to expand...
Click to collapse
got it off a chinese website, i was hunting around
One i'm specifically after is 1.34.110.1
If you give me a link I can re-host it pretty quick, i've got an 8Mbit upload speed.
Arthur Hucksake said:
One i'm specifically after is 1.34.110.1
If you give me a link I can re-host it pretty quick, i've got an 8Mbit upload speed.
Click to expand...
Click to collapse
link in my first post, dont forget thank
Thanks dude.
If this is the real deal, legit one, then we're onto a winner.
I got a "communications were interrupted" error when using Revolutionary.
Rebooted with vol down, it's showing me as SHIP S-OFF
Ok to assume that it's all ok anyway?
I had this too, run it 3 times and eventually it will say it's done. I did report this on their feedback on the website as well
When I boot up with vol down, it is showing Revolutionary at the top and S-OFF.
Copied the PG58IMG 4.0.1.4 updated over, went into HBoot and it flashed.
Reboot, deleted the PG58IMG off the SD card.
Reboot, back into the bootloader screen and it's allowed me to run clockwork, so now done a full back up which has just finished.
All I want to do next is install the stock European 2.3.4 rom (RUU_Pyramid_HTC_Europe_1.45.401.2), so I assume the next step is to change CID?
Thing is, I want to be able to use future OTA updates with this rom. Am I right in saying that whatever ID I set it to is what updates I will get?
Cheers
Yeah, change CID to HTC__001 and then you're completely unbranded. OTA's should also go through without issue too
Awesome. Job done. CiD change, installed the european rom and i'm now 2.3.4
Bootloader is showing ***locked*** but I aint worried about that.
That's the new HBOOT, you can still use Revolutionary to S-OFF it again if need be (I personally re-flashed the 1.17.0011 HBOOT back as I didn't like the LOCKED message)
EddyOS said:
That's the new HBOOT, you can still use Revolutionary to S-OFF it again if need be (I personally re-flashed the 1.17.0011 HBOOT back as I didn't like the LOCKED message)
Click to expand...
Click to collapse
I don't understand why it still says S-OFF at the top. lol
Because it does, but it's not technically S-OFF - I tried to flash a different HBOOT and it didn't work until I re-ran Revo
i was wondering if there is a way to do this. ??
im tired of my MTS4G, i want to install a good rom!
Amen to that
Sent from my myTouch_4G_Slide using Tapatalk
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
ac3theone said:
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
i hope!! i dont care about the warranty, i hate the stock the sence , is so slow and i hate the interface, im comming from a vibrant runing ics passion v12, you can only imagine my frustration .
Limewirelord said:
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
Click to expand...
Click to collapse
I think we can start shelving the idea that there's a lack of dev for the device - some definite strides being made in that direction now.
We could always use more people helping make stuff, though.
----
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Nlarge got his unlocked S-ON bootloader added to that thread, now we need some regular S-ON ones to compare them to. If anyone can figure out how to get one to us it would be helpful.
We are trying to work the S-ON issue, but it's not exactly an easy nut to crack and we've mostly just started.
Thanks for any help that can be provided. This may not be all we need, but it's a start.
Hasn't anyone been able to flash the original PG59IMG.zip via the OTAbootloader patch?
Delivered via candygram for Mr. Mongo.
Blue6IX said:
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Click to expand...
Click to collapse
I'll see if I can figure out how to get that to you. If I can't code, at least I can help with other things.
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Blue6IX said:
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Click to expand...
Click to collapse
I tried to copy it with (adb shell <command>) but it says I have permission denied.
Limewirelord said:
I tried to copy it with (adb shell ) but it says I have permission denied.
Click to expand...
Click to collapse
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Edit - didn't work
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
I'm going to try this asap
Sent from my myTouch_4G_Slide using Tapatalk
Blue6IX said:
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Stock_Retail_OTA_1-55-531-3_downgrade_PG59IMG.zip
Download link
MD5: c7ea224be738b14824a003fd9c9b4b19
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
Click to expand...
Click to collapse
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Blue6IX said:
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Click to expand...
Click to collapse
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
Okay thanks, it was pretty much an 'it will do it or it won't' situation, so we'll have to try something else.
I wish I could get an s-on device in my hands that I could try stuff on - for now it's test and test and test on the s-off, then try on the s-on ...
Sorry it didn't work, we'll have to try another way.
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Limewirelord said:
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Click to expand...
Click to collapse
If this flashes it should revert the phone back to retail launch - but it's probably not going to. Finding a way to force it could have a less then desirable outcome.
If it doesn't take, don't try to force the issue with it unless you know what you're doing and why.
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Limewirelord said:
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Click to expand...
Click to collapse
When it checks and oks it go to recovery in hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
so i unlocked my device via HTCDev.com thinking since its htc device and all they said was i had to unlock bootloader to flash custon OS's i already knew about S-OFF but being the site didn't talk about it(why would it) i went and flash virtouous ROM and got stuck at the HTC screen. i wasnt thinking so i never backed up the stock HTC Rom!!
now i tried 2 of those RUU's in the shipped rom thread the tmous ones with 29 and 50 both saying wrong version.
my question here is there anyway to get at least one RUU to work or get s-off from HBOOT?
my reason of doing this after going back to completely stock is i cant wait any longer for HTC/Tmobile to get us ICS so i tried the custom way and failed lol
I am sure unless you super SID you will have to find ROMs specific for the country the phone came from.
Eg my phone was from Asia region and I could not flash Euro ROMs
ok from the Shipped rom thread in the dev section for the sensation i was trying to go back to stock to gain s-off but the tmous(USA) which is where i am from said wrong version.
futty said:
ok from the Shipped rom thread in the dev section for the sensation i was trying to go back to stock to gain s-off but the tmous(USA) which is where i am from said wrong version.
Click to expand...
Click to collapse
What h boot version do you have?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Hboot: 1.18.0000
Check your CID using fastboot getvar cid to see if these still match the ROM you were trying to flash.
says for cid is t-mob010
i guess out of the 2 stock ruu"s from the post doesnt match that?
edit: ok from what i learned in another post i opened up the rom.zip file and looked at android-info.txt both the cid and mid matched my phones from the RUU file "RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed" buuuuttttt it tried to update it but fails saying i need to correct version :\
futty said:
Hboot: 1.18.0000
Click to expand...
Click to collapse
Are you on t mous us?
Also you can s off and super cid and flash any ruu.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Yes i am. the 2 Ruu's i am using seem to have matching info to my phone when i went to get the rom.zip it uses to send to my phone and looked in the android-info.txt but tell me to get the correct RUU and try again. i got the from here:http://forum.xda-developers.com/showthread.php?t=1074559 under the tmous RUU one with 29 and the other 50.
so i am just stuck at the white screen with the word HTC. if i could get s-off and SuperCID through fastboot that would be awesome but googling it shows up that i cant s-off via fastboot ughhh
still no luck cant seem to flash anything without s-off or supercid
so looks like i am jumping the boat going to sprint this thursday and geting the iphone 4s...byebye android
If you can get into fastboot you should be able to flash RUU from there. Just download the RUU.exe and run it as administrator. Follow the prompts in the exe program while your phone is in fastboot mode.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
futty said:
still no luck cant seem to flash anything without s-off or supercid
so looks like i am jumping the boat going to sprint this thursday and geting the iphone 4s...byebye android
Click to expand...
Click to collapse
Maybe iCrap is better for you. When you use Android phones and want to complete unlock them for flashing customroms aso you shoud realy learn to read before you do something. I hate it when people are not able to read about the stuff they want to do and when something goes wrong they blaim Android for it.
To get s-off, super CID and root on a HTC Android device is realy easy if you read the how-to threads and normaly takes about 15 minutes.
Have fun with your iCrap 4S and please don't try to jailbreak it before you read some stuff.
Sent from my Revolver powered ICS Asus Transformer TF101
first off let me say i have rooted and flashed roms on my sensation before just fine. i was unlocking via htcdev.com and figured their method didnt require s-off since it didnt say anything about it. it just talked about unlocking it to put customs os's on it. 2nd i always had a love hate thing for IOS since i had the 3G and ipod touch.
far as using the RUU'ss it tells me i need the correct Ruu version or something like that. maybe because i didnt run as admin but i have all that stuff turned off due to the theme i used for windows 7 required it off.
If I were you I would Super CID your device. That is what I had to do. A great guide that I used was http://forum.xda-developers.com/showthread.php?t=1472298
i tried and i get this error
vreg_set: request is duplicated id 14
pyramid_init_sd, SD card power on ok
sdcc_init_memory_device done
[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
[JAVACARD_ERR] SMART_IO.CRD cann't find
Click to expand...
Click to collapse
and my cid remains the same as t-mb010
how can i fix it? would love to get mt device back up and running
You can recover this. Firstly read this guide, regarding downgrading hboot and getting s-off.
http://forum.xda-developers.com/showthread.php?p=23222794
The problems are due to HTC.dev not unlocking all parts of the boot loader - you can't flash radio.img or boot.img so nothing is working.
Sent from my Pyramid-T
stringer7 said:
You can recover this. Firstly read this guide, regarding downgrading hboot and getting s-off.
http://forum.xda-developers.com/showthread.php?p=23222794
The problems are due to HTC.dev not unlocking all parts of the boot loader - you can't flash radio.img or boot.img so nothing is working.
Sent from my Pyramid-T
Click to expand...
Click to collapse
thanks for your help. i went to your link and i flashed a stock tmobile rom as suggested and before i could take out boot.img and send it over fastboot my sensation booted to the home screen. i went ahead and s-off'd and SuperCID. just need to create a backup before i screw up again.
again thanks for the help everyone.