Related
UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....
Thanks op.
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!
Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!
Well, worry even less! Special thanks to Calkulin!
thankssssss
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
I'm getting error 155 running Ava Froyo and trying to go back.
blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.
tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.
Yes. I have .79, thanks!
Sent from my PC36100 using XDA App
Hi XDA
I have posted a new thread after reading various guides and threads to S-off the sensation.
My problem is that i dont understand some parts in some guides so i cant use that guide.
1 st problem
Unlock bootloader : I have a Htc sensation Orange UK but it isnt listed on the HTC dev website so what do i do ?
2nd problem : I would prefer not to unlock my bootloader via HTC dev because i dont want to void my warranty.
3rd problem : I am running windows 7 32 bit and control bear support has been stopped for it .
4th problem : I dont have any wires to use for control bear so i want to use a paper clip but i dont know if this is correct so can someone verify please ? : (Image attached to this post)
5th problem : I dont know if the method i am understanding for S - off is correct
What i think i need to do ,
Htc dev :
Unlock using htc dev
root using temp toot .bat
run control bear
do wire trick
install h boot
Install recovery
Ganeshp ver
Run temp root
run control bear
do wire trick
install H boot.
Install recovery
6th problem :
I believe you can flash roms with only unlocked bootloader but there is only 1 guide for it and its not very clear.
7th problem : Im afraid about bricking my device
Thanks for helping guys !
Hi, all the questions you have can pretty much be answered with this guide: http://forum.xda-developers.com/showthread.php?p=26280760
S-off by ganesh's guide does not require an unlocked bootloader.
Concerning the wire trick... I used one piece of paperclip so I can verify that it works (I never insulated the paperclip with anything either, so it was just a naked paperclip)
By the way, you never mentioned your bootloader details, but if you have 1.2x bootloader you can use the guide that ganesh wrote about, but if you have an hboot that is a lower version, then you have to use revolutionary's s-off guide.
You can flash ROMs and a custom recovery both s-on and s-off, but if you don't want to unlock your bootloader like you said, then I would try to s-off your device.
Since you are running windows, you probably need the windows version of controlbear.exe. pm me and ask about it, otherwise, ask someone else who has the file.
Good luck! And I hope I answered the questions
I wouldn't worry that much about bricking your device. Just flash the right ROMs and you'll be fine. If you follow all the instructions step by step, then there's nothing that can go wrong.
After you finish tinkering with your phone, I would flash albino's ROM: http://forum.xda-developers.com/showthread.php?p=37121632
It's silky smooth, has basically no major bugs, and I think the battery is better compared to other ROMs.
Sent from my HTC Sensation
Be careful and do more research on unlocking the bootloader via HTC Dev.
It is not the complete unlocking sollution that HTC leads you to believe it is. It unlocks the bootloader in a very limited fashion, and prevents some full s-off methods from working at all without starting completely over and flashing an RUU (which wipes everything and restores the phone to the way it left the factory)
Meanwhile if you run into warrenty issues later, having used the HTC Dev website tells HTC that you messed with the phone and they could actually deny warrenty service based on that. But if you use other means to unlcoked the bootloader HTC wouldn't know anything about it, so if you flashed an RUU later to return it to bone stock it would be an S-On phone with a locked bootloader again. Warrenty shouldn't be affected.
Also keep in mind that you've got a 2 year old device. The warrenty probably isn't going to last much longer on it anway.
Heloooo said:
Hi XDA
I have posted a new thread after reading various guides and threads to S-off the sensation.
My problem is that i dont understand some parts in some guides so i cant use that guide.
1 st problem
Unlock bootloader : I have a Htc sensation Orange UK but it isnt listed on the HTC dev website so what do i do ?
2nd problem : I would prefer not to unlock my bootloader via HTC dev because i dont want to void my warranty.
3rd problem : I am running windows 7 32 bit and control bear support has been stopped for it .
4th problem : I dont have any wires to use for control bear so i want to use a paper clip but i dont know if this is correct so can someone verify please ? : (Image attached to this post)
5th problem : I dont know if the method i am understanding for S - off is correct
What i think i need to do ,
Htc dev :
Unlock using htc dev
root using temp toot .bat
run control bear
do wire trick
install h boot
Install recovery
Ganeshp ver
Run temp root
run control bear
do wire trick
install H boot.
Install recovery
6th problem :
I believe you can flash roms with only unlocked bootloader but there is only 1 guide for it and its not very clear.
7th problem : Im afraid about bricking my device
Thanks for helping guys !
Click to expand...
Click to collapse
1. I am on 3 mobile and my phone is also not listed on HTCDev. But I chose Sensation (EU) which worked fine. I believe its for all devices issued in Europe.
2. HTCDev voids the warranty as well as wipes off the data. But if you are gonna flash custom ROM or overclock then I guess you would eventually say good bye to your warranty anyway!
3. Burn a live CD for Ubuntu 12.04 and use it for Controlbear wire trick method. You dont need to install Ubuntu if you dont want to. There are guides here which give you controlbear tool for windows but word of advice... use the live CD and follow unlimited.io website only. They have made their tool safer over the time. Trust me its worth every hassle.
4. I am sure you would have a spare network ethernet cable lying somewhere at your place, use that one. Otherwise, people have reported the paper clip to be working but make sure you insulate it properly.
5. Here are the overall steps for everything.
- Unlock bootloader via HTCDev
- Use controlbear tool and wire trick to gain S-OFF (the tool downloaded from unlimited.io for Ubuntu will install custom hboot itself)
- Install custom recovery
- Obtain Root by flashing the zip package via this custom recovery
- Flash custom ROM for ICS (Try Androidrevolution HD... its good)
- You can download apps from the market to overclock your cpu.
(Ofcourse you can install custom ROM without being S-OFF.. use Asskicker's guide, its comprehensive and easy to understand)
6. Read through Ganesh's guide properly and you may be able to flash custom ROM without unlocking bootloader.
7. Everyone should be afraid of bricking their device, I was too. But if you do everything as it has been mentioned in the guide, then you should be confident that everything will be fine.
A few days ago I S-OFFed my device and was scared to my bones that I would brick my device but once I did it, I am feeling so good about it now. The guys here have helped me so much.
I presume you are on 1.2x hboot version.
aaaaannnnndddd read this post if you have time
the post explains everything regarding sensation you need to know
IM ****ting it!
ganeshp said:
aaaaannnnndddd read this post if you have time
the post explains everything regarding sensation you need to know
Click to expand...
Click to collapse
Ok so i tried it , What i did :
I plugged in my phone and then i clicked root.bat
after temp root i clicked on control bear and it backed up my device etc
Then it told me to do wire trick so i tried my best and the phone went off
I then **** it and looked for flowolfs video on youtube , (the phone plugged in and control bear still running)
Control bear was telling me to check adb drivers and that it was waiting for my device .
I looked at flowolfs video and i unplugged my phone and then i plugged battery back in .
The phone works fine but i had to format sd card.
I went into bootloader but unfortunalty it shows s-on.
Heloooo said:
Ok so i tried it , What i did :
I plugged in my phone and then i clicked root.bat
after temp root i clicked on control bear and it backed up my device etc
Then it told me to do wire trick so i tried my best and the phone went off
I then **** it and looked for flowolfs video on youtube , (the phone plugged in and control bear still running)
Control bear was telling me to check adb drivers and that it was waiting for my device .
I looked at flowolfs video and i unplugged my phone and then i plugged battery back in .
The phone works fine but i had to format sd card.
I went into bootloader but unfortunalty it shows s-on.
Click to expand...
Click to collapse
well you havent even done the wire-trick
the controlbear is throwing driver errors means problem in connection ..check troubleshoot #1 in my soff guide
Troubleshooting
ganeshp said:
well you havent even done the wire-trick
the controlbear is throwing driver errors means problem in connection ..check troubleshoot #1 in my soff guide
Click to expand...
Click to collapse
Well control bear did say loading sixpacks to device but when it said do wire trick now the jupunutbear screen wasnt on ?
I dont have htc sync on laptop but i did have default htc sync on my phone as connection as i thought you needed it like this for temp root but after temp root UI isnt usable?
Heloooo said:
Well control bear did say loading sixpacks to device but when it said do wire trick now the jupunutbear screen wasnt on ?
I dont have htc sync on laptop but i did have default htc sync on my phone as connection as i thought you needed it like this for temp root but after temp root UI isnt usable?
Click to expand...
Click to collapse
put it in charging mode and try again
Rooting + s off
rzr86 said:
put it in charging mode and try again
Click to expand...
Click to collapse
I will try again but i hope i dont Brick it.
Thanks guys!
Thanks alot guys !!!!!!!!!!!!!!!!!!!!!!
I have now attained S - off on my 4th try at wire trick!
I thank , Ganesh for helping me out alot , and i also thank auggie 2k as i used his s-off troubleshoots and the gif image helped ! i also thank AndroidSupporter318 for all the help on the thread and my thanks also go out to Skip jacks for all the help on the thread!
I now need help again , my bootloader is locked but i have s - off does it matter? (i didnt htc dev unlock )
Also what are my next steps ?
Heloooo said:
Thanks alot guys !!!!!!!!!!!!!!!!!!!!!!
I have now attained S - off on my 4th try at wire trick!
I thank , Ganesh for helping me out alot , and i also thank auggie 2k as i used his s-off troubleshoots and the gif image helped ! i also thank AndroidSupporter318 for all the help on the thread and my thanks also go out to Skip jacks for all the help on the thread!
I now need help again , my bootloader is locked but i have s - off does it matter? (i didnt htc dev unlock )
Also what are my next steps ?
Click to expand...
Click to collapse
flash 3.33 universal from firmware's thread in development section
it will give you also patched hboot which is unlocked
follow the instructions carefully
and before flashing check md5 sums(important)
don't do htcdev unlock.it is unecessary
How?
rzr86 said:
flash 3.33 universal from firmware's thread in development section
it will give you also patched hboot which is unlocked
follow the instructions carefully
and before flashing check md5 sums(important)
don't do htcdev unlock.it is unecessary
Click to expand...
Click to collapse
How do i flash it ? I dont have recovery installed .
1 more thing i cant find it
Here is 4ext recovery. I think the directions are in the thread: http://forum.xda-developers.com/showthread.php?t=1377759
Sent from my HTC Sensation
Heloooo said:
How do i flash it ? I dont have recovery installed .
1 more thing i cant find it
Click to expand...
Click to collapse
Slow down a second, buddy. You're 1 step ahead of yourself. Though I respect your excitment fro this process!
You don't flash firmware in recovery. You flash firmware in bootloader.
Read this thread.
http://forum.xda-developers.com/showthread.php?t=1459767&highlight=firmware
In it you will find the how to flash firmware (it's REALLY easy. Just make sure to follow the directions.) And you will be able to download the firmware files.
Short version is that you download the firmware file which will be caleld PM58IMG.zip, put it on your SD Card, and reboot into bootloader. Bootlaoder will install the new firmware for you. Don't watch it. Just walk away for 5 minutes, or you are liable to freak out when the screen goes blank during the process. More than one person has gotten scared when that happened and pulled the battey to stop it...which WILL brick the phone. So let it do it's thing in peace. It takes 2 mintues.
When it reboots you will have a shiny new firmware with a fancy updated bootloader as well.
And someone else please answer this...do Kohr-Ah's firmware packages have 4EXT recovery already included? Or perhaps CWM? So that they flash with the firmware? It's been too long sinc eI used one I can't remember.
@Skipjacks
I don't think kohr-ah's firmwares have a recovery installed. Just the radio, adsp.IMG, hboot patch and other stuff that I don't know about. I don't see a recovery.IMG in the zip file. Unless the recovery is rcdata.IMG...
Sent from my HTC Sensation
AndroidSupporter318 said:
@Skipjacks
I don't think kohr-ah's firmwares have a recovery installed. Just the radio, adsp.IMG, hboot patch and other stuff that I don't know about. I don't see a recovery.IMG in the zip file. Unless the recovery is rcdata.IMG...
Sent from my HTC Sensation
Click to expand...
Click to collapse
No I don't think that's it either. It must have been the firmwares for my old MyTouch 4G that had recovery included. Like I said, it's been a while.
Just see the 4EXT recovery thread AndroidSupporter posted earlier. It has the recovery download links.
Ok that thread says things such a cid do what is that ? , it also says check md5 what is that ?
Thanks guys !
Sent from my HTC Sensation Z710e using xda app-developers app
Which version
I also dont understand which version is right for my phone , some one said 3.33 but which 3.33 there are two packs?
Heloooo said:
Ok that thread says things such a cid do what is that ? , it also says check md5 what is that ?
Thanks guys !
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
The CID is how HTC locks down the phone so it can only get the updates that they want your phone to get. Each region and carrier has different CIDs, so you can't use a Europe firmware or official ROM on an America phone. Each firmware file contains a list of the CIDs it will install on. If your CID isn't on the list it won't install. But there is a super CID as well that is like a master key. With the superCID on your phone all firmware packages will install.
Read this.
http://forum.xda-developers.com/showthread.php?t=1192300
See Step 4 to get Super CID. It's insanely simple as long as you have ADB installed.
Also the 3.33 firmware package may already include your CID. If it does you don't need to get Super CID. But it's easy, so why not?
An MD5 is a code that is generated that shows if 2 files match. If they match, the codes will be the same. If they don't, the files are different. With Firmware, ANY variation in the file can brick your phone. So you ALWAYS want to check to make sure the MD5 of the firmware file you downlaoded matches what it's supposed to be. That's why Kohr-Ah has the MD5 written under each download link.
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
Heloooo said:
I also dont understand which version is right for my phone , some one said 3.33 but which 3.33 there are two packs?
Click to expand...
Click to collapse
Say what now?
This post.
http://forum.xda-developers.com/showpost.php?p=21711303&postcount=2
First link at the top. It's the only 3.33 firmware there for download. (The one at the bottom is just the same file from a different download location)
Here is the same thing cut and pasted from that post. This is what you want.
Firmware 3.33 Universal:
DOWNLOAD:http://d-h.st/SuC
MD5: 07cc2a2ea4473e8fe8d6fe844c4020a1
Just put it on the root directory of the SD Card (don't put it in a folder) and boot into recovery. See if that works. If it doesn't then you have to Super CID. If it works, great. You're done. Flash recovery next.
I have a one SV on cricket (US)
K2_PLC_CL (s-on) still
Ok so it was all stock from store. Tan I did this in order:
1.) Unlocked bootloader from HTC dev...
2.) (flashed) Installed CMW v6.0.2.8 via ADB
3.) MADE BACKUP with CWM
4.) Rooted by flashing a zip via CMW (worked great)
5.) tried moonshine.io for s-off tried twice. Failed
-program (distiller) closed after saying "moonshining 1...2...3...to 10)
-now on boot it gets to "Htc
I booted into CMW and retored that backup i had before any rooting or s-off etc... but it still hangs :silly:
Should I try the hboot option to restore? (I thought CMW backup was like a complete nand backup. Which should be bullet proof right?)
Thanks for looking guys! I have no communication as of now I just want to make calls at least
This is my first android device and I always like getting to know my devices from the inside, the iphone BS was too much haha. I gues i dont really need s off or super cid if it means no phone. but why not if it works.
Did you have ICS or JB, when you have tried S-off?
Please remember, as long as you are S-on you must flash the boot.img with fastboot commands (also, if you are restoring a backup and you did a full wipe)! If you have a cwm backup, boot.img should be inside of your backup folder.
Did you wipe everything before your restore? Maybe fragments of moonshine still there.
Did you try TWRP recovery?
[HTC oneSV boot hang, FIXED] THANKS!!
LOL I had no idea the boot.img had to to be manually flashed, thank you very much it work s great now!
This time I cleared/wiped data AND cache. it still hanged and wont boot. Than I re tried using CWM again to restore (still hangs). than I flashed boot.img THAT DID THE TRICK after "fastboot reboot".
BTW major fail on my part; I was rooting and moonshining for JB it turns out I have ICS (i forgot to update) now that you mentioned it hehehe
I had 4.0.4 sense 4.1. I think that is why everything went to hell...
Alright Ill try moonshine after the update to JB 4.1.2 if that fails than Ill try the facepalm.
One last question; if i do update to JB 4.1.2 and achieve s-off could I use that CMW backup to always go back to ICS 4.0.4? (just incase I ever wanted to get SUPER CID and get JB 4.2.2) I wonder if super cid works with k2-PLC-cl.... Ill try it when I get find the funds a better phone to risk a brick
-Thank you sir!
Ok, lets bring a bit light into these darkness:
- Facepalm S-Off only works, as long as you did not achieve the JB update!
- You can restore a ics cwm backup, also when you are on JB and S-Off, but
- Restoring ics from a backup is not the same, as you where on ics before the update.
Thats because of the updated hboot (ics-> hboot 1.0; jb-> hboot 2.0). In hboot 2.0 the Supercid/Facepalm exploit is fixed. You can still get Supercid under hboot 2.0, but you must do moonshine S-Off before.
So, at all you must think about, what you want and whats the best way to get, before updating to jb.
If this was to difficult to understand, ask again and i will try my best to explain it for you to understand.
Ok
Hum they creators of these phones really enjoy making puzzles for us don't they...
Alright so my options are:
1.) [stay on ICS]
-get super cid
-facepalm for s-off
(can I still update to JB after this and still have super cid and s-off? But that would install hbot2 wouldnt it? so....)
I think I want method 2↓
2.) [update to JB]
-use moonshine to get s-off
-some how get super cid? (I dont really need super cid but it would be nice to know I have it just in case)
-profit
//edit//(ohh yes, once on JB hboot v2, if i have s off and on hboot2 could I go back to hboot1 along with ICS should i need to)
Any ways thank you again
1. Right, you can update and both will stay.
2. Right, after S-Off you should be able to change SuperCid. But it should be said, that its a very risky operation and phone can be bricked very easily if you are doing something wrong.
And for your edit: You can restore a ics backup, but without a RUU it is difficult to bring back hboot 1. Only a backup of it will solve this. Recoveries usually don't backup hboot.
SV ICS super cid
I know this thread : http://forum.xda-developers.com/showthread.php?t=2264322
says to do super cid on original stock, but could I just go ahead and HEX my cid with my ICS that is unlocked/rooted/custom-recovery?
Do I have to un-do all of that to change the CID? or is that just good technique? [im also on cricket ics 4.0.4 if it matters, k2_plc_cl]
Thank you very much! I wish to change my cid right now but ill wait and see what you say if it saves me from a brick
than I'm off to s-off for all the goodies that follow haha.
I don't think, that this will be important, because SuperCid is located in a partition which has nothing to do with root or recovery.
alrighty than
haha wrong link in previous post I meant this one: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
Click to expand...
Click to collapse
I was reading his link and somehow posted your link, Ill use your link actually now that I read it... I thought it wouldn't matter, better safe than sorry. Ill try it out and see how it goes.
Thanks for helping
Questions about hexing CID
old.splatterhand said:
I don't think, that this will be important, because SuperCid is located in a partition which has nothing to do with root or recovery.
Click to expand...
Click to collapse
Alright its late and I'm not going to flash it yet ill wait to see what you make of this:
I have used hxd many times for xbox/psp/etc so i know how it works... it found 3 instances of my CID
(some info omitted as the 'x' char)
Code:
maincid=CRICK001xx.xx.cidlist=CRICK001.xx.xx.rid=105.xx.xx.modelid=PL8xxxxxx.xx.xx.report=com.xx.xx.skulist=1xxx.xx.xx.taskid=30xxxx.xx.xx.mainsku=1xxx.xx.onecid=1.xx.cwkey=CRICK001.ro.com.google.clientidbase=android-htc //more stuff after........
Im assuming only the first instance "maincid=CRICK001" needs to be 11111111
(or should all 3 instances of "CRICK001" be changed to 11111111)
Ill give it a go after work tomorrow when Im confident that my modifications wont render my phone as a door stop.
I need to buy you a beer, but the donation is in german, ill have to translate it when I get done
Gain_Medium said:
Alright its late and I'm not going to flash it yet ill wait to see what you make of this:
I have used hxd many times for xbox/psp/etc so i know how it works... it found 3 instances of my CID
(some info omitted as the 'x' char)
Code:
maincid=CRICK001xx.xx.cidlist=CRICK001.xx.xx.rid=105.xx.xx.modelid=PL8xxxxxx.xx.xx.report=com.xx.xx.skulist=1xxx.xx.xx.taskid=30xxxx.xx.xx.mainsku=1xxx.xx.onecid=1.xx.cwkey=CRICK001.ro.com.google.clientidbase=android-htc //more stuff after........
Im assuming only the first instance "maincid=CRICK001" needs to be 11111111
(or should all 3 instances of "CRICK001" be changed to 11111111)
Ill give it a go after work tomorrow when Im confident that my modifications wont render my phone as a door stop.
I need to buy you a beer, but the donation is in german, ill have to translate it when I get done
Click to expand...
Click to collapse
At this point i only can tell you about my guide and the picture inside. To be honest, i only noticed only one cid, together with imei. So maybe this helps you.
Edit:
Please, really be careful if your file/block is different than in my guide!
I'm on mobile and can't look at your code completely.
My guide for sure works for k2u & k2ul cause i did it myself at two different phones but i don't know, if cricket has changed more and i don't want your phone bricked.
Edit2:
I really not sure, if changing CID will work. Maybe you'll try the S-Off step by Moonshine after update to JB, would be better than a bricked phone!
You must also think, what do i profit from SuperCID?
K2u & k2ul can be unbranded this way, maybe they also profit from earlier updates.
But you can't use k2u/l Software on US phones, different network, so this point is useless for you. And i don't think, cricket will release their updates earlier for phones with SuperCID.
Just my two cents, now its on you to make your decision...
What i also want to say, i had help the first time i did.
It was @jmz who helped me, maybe he reads that and know more about cricket cid.
I think ill give it a go
I actually tried to contact him and others, but since im so new I can't send PMs (they send but nothing is in my sent box. link it never happened) so I guess unless JMZ stumbles upon this thread thats it.
As for me I don't think it would brick my phone (like a real brick) if all else I could just boot into recovery and flash back my backup stuff right?
Or if i screw up would it not even allow recovery / shell? Although a brick would permit me to buy a better popular phone
If i try it all post more details on it for other cricket users.
This is modifying the bootloader. If you do something wrong, the phone wont boot. Not in recovery, not in OS, bricked.
PS. @Gain_Medium
If you write a xda username with an @ before, the one will be notified, the he is mentioned somewhere
Side note: I don't believe that there is any reason for super cid on a cricket us carrier, unless you plan on traveling to Europe, Asia, or anywhere out of the continent.
Yes, it's cool to have accomplished superCID. But there is really no benefit here in the US, if you plan on maybe using a different service plan provider, you'll still need to unlock your SIM, even if you do achieve superCID without bricking.
Good luck with your decision. I hope to read your updates on what you have chosen. And how everything goes for you.
THESE ARE ONLY MY THOUGHTS AND OPINIONS. NOT TRYING TO SWAY YOU AWAY FROM ATTEMPTING ANYTHING.
but please research superCID for cricket mobile and see what you find.
Pros vs Cons
Hi,
I'm trying to get a One S back to stock for a friend but failing...
The phone is unlocked, S-ON, hboot 1.14, 02_01 CID, has CWM recovery and rooted Cyanogenmod 10.1 installed, battery 100% and runs fine as is...
So, first of all I re-lock ready to run this RUU:
RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed
but every time half way through it fails with the following errors in the attached screen shots...
A point to add is as soon as I re-lock the phone, it then will not boot but goes straight into hboot every time which I thought was strange..?
Anyway, some guidance would be very welcome to get this One S back to stock,
EDIT: Just flashed S4 Stock Recovery and the RUU still fails half way through, any ideas..?
Can anyone give me links to O2__01 HTC One S RUU files, can't find any live one anywhere..??
Thanks
Getting a RUU to run correctly is very hit and miss. The page below is a useful guide to double check the basics:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Post 9 details that with s-on you can't flash a RUU with a radio version older than the one you are on already. This may be your problem as I think your radio version will be 1.06 and the one in the RUU you are trying to run is 0.16. The problem with s-on is you can't flash radio's to do anything about that.
The RUU that should work is the one listed below, but I can't find any decent download links for it, like you said. Just try googling it and see if anything turns up.
RUU_Ville_U_ICS_40_S_O2_UK_2.38.206.2_Radio_1.08es.50.02.16_10.09b.50.04L_release_278818_signed.exe
rosswhite said:
Getting a RUU to run correctly is very hit and miss. The page below is a useful guide to double check the basics:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Post 9 details that with s-on you can't flash a RUU with a radio version older than the one you are on already. This may be your problem as I think your radio version will be 1.06 and the one in the RUU you are trying to run is 0.16. The problem with s-on is you can't flash radio's to do anything about that.
The RUU that should work is the one listed below, but I can't find any decent download links for it, like you said. Just try googling it and see if anything turns up.
RUU_Ville_U_ICS_40_S_O2_UK_2.38.206.2_Radio_1.08es.50.02.16_10.09b.50.04L_release_278818_signed.exe
Click to expand...
Click to collapse
Thanks rosswhite, I think you are right about the radio and no I can't find any download links that work either...
Another thought, does anyone have or know where to get a nandroid backup of O2_01..?
topcat888 said:
Thanks rosswhite, I think you are right about the radio and no I can't find any download links that work either...
Another thought, does anyone have or know where to get a nandroid backup of O2_01..?
Click to expand...
Click to collapse
Your other option of course is to S-OFF the device. You can then flash any radio or RUU you want.
hi everyone
i havebeen struggling with this for 2 years now. i have HTC sensation with hboot 1.18.xxxx that i bought in 2011. after the first year i have been keen to move to a newer rom. i have tried to look up inf in xda and elsewhere and got no where with this.
i have been worried about bricking so much that i didnt try to many weird procedures. i had even tried to go through with the android revolution installation procedure but failed right on. because revolutionary does not with with my device even though thr hboot is supported.
i badly need to move to a newer jelly bean based rom or later else my device is like a stone-age crap. i sincerely request some straight forward process / guidance of getting through this without weird, wire trick etc.
i really want to keep this device instead of buying a new device for no reason. but i dont know how to start and how to end. kindly help me out.
rajdeeprath said:
hi everyone
i havebeen struggling with this for 2 years now. i have HTC sensation with hboot 1.18.xxxx that i bought in 2011. after the first year i have been keen to move to a newer rom. i have tried to look up inf in xda and elsewhere and got no where with this.
i have been worried about bricking so much that i didnt try to many weird procedures. i had even tried to go through with the android revolution installation procedure but failed right on. because revolutionary does not with with my device even though thr hboot is supported.
i badly need to move to a newer jelly bean based rom or later else my device is like a stone-age crap. i sincerely request some straight forward process / guidance of getting through this without weird, wire trick etc.
i really want to keep this device instead of buying a new device for no reason. but i dont know how to start and how to end. kindly help me out.
Click to expand...
Click to collapse
1st
This is definately not the place to ask for "all inclusive help".
You should at least do some own basic researches or leave your phone as it is,
especially when you're worried about bricking your device.
There are so many excellent descriptions here, that could guide you to flash a custom rom.
2nd
If you are on hboot 1.18 you don't need to do the wire trick for s-off, just have a look at this.
If you searched a little bit, you'd find out yourself.
But even the wire trick is nothing "bad", I did it on 6 devices till now.
I'd like to encourage you to simply read/search a little bit more here in the forums before coming back and asking for help.
tom0769 said:
1st
This is definately not the place to ask for "all inclusive help".
You should at least do some own basic researches or leave your phone as it is,
especially when you're worried about bricking your device.
There are so many excellent descriptions here, that could guide you to flash a custom rom.
2nd
If you are on hboot 1.18 you don't need to do the wire trick for s-off, just have a look at this.
If you searched a little bit, you'd find out yourself.
But even the wire trick is nothing "bad", I did it on 6 devices till now.
I'd like to encourage you to simply read/search a little bit more here in the forums before coming back and asking for help.
Click to expand...
Click to collapse
thanks for the reply. as i mentioned revolutionary does NOT work for me. it says failed to get root. i have already tried those things about 8 times now and it didnt work for me. thats why i have posted here for help.
using htcdev i know i can try to unlock but it wont soff. so i dont know if that will help me or not.
rajdeeprath said:
thanks for the reply. as i mentioned revolutionary does NOT work for me. it says failed to get root. i have already tried those things about 8 times now and it didnt work for me. thats why i have posted here for help.
using htcdev i know i can try to unlock but it wont soff. so i dont know if that will help me or not.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.
Sajito said:
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.
Click to expand...
Click to collapse
thanks i will try to read up and post back if needed. Admin please move the thread to appropriate category.
Sajito said:
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.
Click to expand...
Click to collapse
i went through the thread again and again but still find it somewhat confusing. I cant seem to separate the temproot process start and end in there. can someone outline just the temproot procedure and the pre-requisite for it ?
Does temproot require controlbear files ? rumrunner site says it requires a htc dev unlocked device. is that a must ?
rajdeeprath said:
i went through the thread again and again but still find it somewhat confusing. I cant seem to separate the temproot process start and end in there. can someone outline just the temproot procedure and the pre-requisite for it ?
Does temproot require controlbear files ? rumrunner site says it requires a htc dev unlocked device. is that a must ?
Click to expand...
Click to collapse
I'm not 100% sure about the exact steps anymore, but you don't need Controlbear, you just need the temp root.
When you have temp root, run rumrunner and follow the instructions.
I said read the thread, cause it might be possible that you get the message that it didn't work, while it actually did work.
You'll get everything needed in the thread. Otherwise just ask.
Sajito said:
I'm not 100% sure about the exact steps anymore, but you don't need Controlbear, you just need the temp root.
When you have temp root, run rumrunner and follow the instructions.
I said read the thread, cause it might be possible that you get the message that it didn't work, while it actually did work.
You'll get everything needed in the thread. Otherwise just ask.
Click to expand...
Click to collapse
Seriously dont know if i am plain unlucky or topic are not very useful for a newbie.
1. Revolutionary failed
2. i did temp root + rumrunner - failed (image attached)
I wonder if my device was not made on this earth or something. Just simply soff. Also dont know if i cant install a JB rom on this without soff safely.
rajdeeprath said:
Seriously dont know if i am plain unlucky or topic are not very useful for a newbie.
1. Revolutionary failed
2. i did temp root + rumrunner - failed (image attached)
I wonder if my device was not made on this earth or something. Just simply soff. Also dont know if i cant install a JB rom on this without soff safely.
Click to expand...
Click to collapse
What firmware and hboot do you have?
My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000
rajdeeprath said:
My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000
Click to expand...
Click to collapse
do you have sdk tools installed?(adb/fastboot)
also check if usb debugging mode is ticked
oh! hello again hope you are great.
yes i have adb setup properly. i do android dev so all development tools are setup properly. htc drivers are installed htc sync has been uninstalled.
i have tried on windows 8 and windows 7 pcs.
rajdeeprath said:
oh! hello again hope you are great.
yes i have adb setup properly. i do android dev so all development tools are setup properly. htc drivers are installed htc sync has been uninstalled.
i have tried on windows 8 and windows 7 pcs.
Click to expand...
Click to collapse
if revolutionary.io method doesn't work then try to update officially
see this thread
http://forum.xda-developers.com/showthread.php?t=1672425
then try with juopunutbear or rumrunner method again
rajdeeprath said:
My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000
Click to expand...
Click to collapse
One thing you could do is:
- get your phone updated to ICS (OTA over device settings) to get the latest firmware/hboot on it
- HTC Dev unlock your device (nothing complicated, you need to have fastboot running)
- Install/flash latest 4ext recovery (once more via fastboot) and enable smart flash option
Now in recovery with updated firmware/hboot make a nandroid backup and flash almost every rom you like.
In first place I'd not flash a CM12 rom.
tom0769 said:
One thing you could do is:
- get your phone updated to ICS (OTA over device settings) to get the latest firmware/hboot on it
- HTC Dev unlock your device (nothing complicated, you need to have fastboot running)
- Install/flash latest 4ext recovery (once more via fastboot) and enable smart flash option
Now in recovery with updated firmware/hboot make a nandroid backup and flash almost every rom you like.
In first place I'd not flash a CM12 rom.
Click to expand...
Click to collapse
firstly thank you very much for continuing to show hope. appreciate that. tell me thiss. i have a ota pending which i haven't gone for yet.
4.0 update sense 3.6 system upgrade 3.33.720.6
see attached image.
i never did that cause not everyone on htc blog had a good experience. Should i do that now ? will that help me move forward? will i be able to install android revolution or vipers or cyanogenmod after this? will i be able to soff?
i understand 3.33 is ics firmware ? right? what if i wish to go for jellybean ?
thanks
rajdeeprath said:
firstly thank you very much for continuing to show hope. appreciate that. tell me thiss. i have a ota pending which i haven't gone for yet.
4.0 update sense 3.6 system upgrade 3.33.720.6
see attached image.
i never did that cause not everyone on htc blog had a good experience. Should i do that now ? will that help me move forward? will i be able to install android revolution or vipers or cyanogenmod after this? will i be able to soff?
i understand 3.33 is ics firmware ? right? what if i wish to go for jellybean ?
thanks
Click to expand...
Click to collapse
since you update to ics you will be able to flash every ics/jb/kk/lp custom rom you like
so should i go ahead with the official ics update?
It's up to you.
Might be you're just satisfied with your new ICS firmware.
If you want to go further, unlock and custom recovery is an quite easy step.
For custom rom s-off is not necessarily needed.
Sent from my Sensation using XDA Free mobile app
rajdeeprath said:
so should i go ahead with the official ics update?
Click to expand...
Click to collapse
If you do the update, try again with rumrunner after it has finished.
Thanks. I updated to ICS and did a full factory reset. The device seems to be quiet smooth compared to GB though. The next update i do will be using what you suggested. Without SOFF flashing a custom rom.
When i get there i will message back on this thread. Going to test drive this ICS now for a while.time.