Hello there everyone! I was just beginning to warm up to the idea of rooting when I discovered that it is currently impossible to gain true S-Off due to a patch. Was this patch part of the ICS update? Or was it released during the GB era? I remember having a OTA show up earlier that was not ICS (A few months ago). Am I stuck now?
Software number: 1.50.531.1
Completely stock.
Thank you guys.
SensationNation said:
Hello there everyone! I was just beginning to warm up to the idea of rooting when I discovered that it is currently impossible to gain true S-Off due to a patch. Was this patch part of the ICS update? Or was it released during the GB era? I remember having a OTA show up earlier that was not ICS (A few months ago). Am I stuck now?
Software number: 1.50.531.1
Completely stock.
Thank you guys.
Click to expand...
Click to collapse
Well for soff you need to be atleast 1.18 HBOOT...and HBOOT update was being done since gb times itself(happened somewhere middle)...so people who got HBOOT greater than 1.18 you are out of luck...
For you to see what HBOOT you got...you need to go to bootloader ..power off your phone..remove battery ...then put it back ...press power+volume down ....it'll open HBOOT screen...there your HBOOT version will be there..
Also the firmware number will/can not precisely give you hboot version...I mean ppl has to remember what firmware got which hboot
sent from my blazing fast pyramid through sonic waves
It stated that I had 1.18.0000
So I'm able to root with full S-Off?
SensationNation said:
It stated that I had 1.18.0000
So I'm able to root with full S-Off?
Click to expand...
Click to collapse
you just want to root the device?
or want to update your firmware to 3.32 and want to install ICS custom roms?
I will want to root and change to an ICS ROM, such as CM9 or Hypersensation.
1. Unlock your bootloader at www.htcdev.com
2. ???
3. Profit.
SensationNation said:
I will want to root and change to an ICS ROM, such as CM9 or Hypersensation.
Click to expand...
Click to collapse
first you need to setup your mobile ready for ICS ...to install ICS custom ROMS
follow everything step by step from this guide ...until you got s-off,supercid,and custom recovery installed( recommend 4EXT rather than CWM for sutom recovery)
then for ICS ...you require latest firmware
follow this guide...until flashing firmware..
once the above steps are done you can't boot into your GB rom...so by this time..get your ROM downloaded and inside your sdcard
then you can flash the ICS ROM form recovery...(you can use above guide as reference for flashing ROMS too)
Man, thank you so much for the help! Are there any incompatibilities between GB and ICS? (Like if I were to back up my files with Titanium, will they restore onto an ICS ROM?)
Thanks!
SensationNation said:
Man, thank you so much for the help! Are there any incompatibilities between GB and ICS? (Like if I were to back up my files with Titanium, will they restore onto an ICS ROM?)
Thanks!
Click to expand...
Click to collapse
restoring data of apps (GB rom) from titanium backup...might have some glitches (because app are also modified for ICS compatibility)..try at your own risk...but people recommend to not to do this especially when moving from GB to ICS
but dont ever restore system data when moving from GB to ICS ...also when changing roms...it will completely mess up your rom
So I have to start from scratch? And what is the point of titanium backup if I can't actually restore anything?
Thanks.
SensationNation said:
So I have to start from scratch? And what is the point of titanium backup if I can't actually restore anything?
Thanks.
Click to expand...
Click to collapse
look i haven't explored TB that much (i own the premium app too)
afaik we only require a backup of sms's ,contacts (if sync is there no need for this too),call logs,and apps + its data
for sms + contacts + call logs -> i use super backup
and apps will be taken care of once you sync up with google
and apps data and missing apps i use TB.
So what would be system data?
SensationNation said:
So what would be system data?
Click to expand...
Click to collapse
No don't backup system data when version changes... I.e from gb to ics...
sent from my blazing fast pyramid through sonic waves
first_agent said:
1. Unlock your bootloader at www.htcdev.com
2. ???
3. Profit.
Click to expand...
Click to collapse
No. Don't teach people the wrong information. HTCDev does NOT unlock your phone completely. I'm not sure why people even LIKE HTCDev. Maybe they think it is the "Official" way or something...
I mean, what kind of data is system data? Screen brightness?
Related
My sensation is s-off. I want stock recovery. Can I get root without cwm? If I just download the su app from market?
Thanks.
Oops please move to q/a
Nope, but if you don't like CWM you can restore back by doing this: http://forum.xda-developers.com/showthread.php?t=1228648&highlight=OTA+stock
So I can flash cwm apply su/root then flash back stock recovery and I will get Ota updates with no problems?
Afaik, chances are good, that you'll get OTA updates, but I think you'll also lose root then.
hg3atintin said:
So I can flash cwm apply su/root then flash back stock recovery and I will get Ota updates with no problems?
Click to expand...
Click to collapse
Yes, worked for me ALSO: Read it through the guide, and insure that you got everything ready, if something should go the other way
bubuthebear said:
Afaik, chances are good, that you'll get OTA updates, but I think you'll also lose root then.
Click to expand...
Click to collapse
Nope, only if it is a brand new version, like the ICS, then you will loose it. But not if you change from gingerbread 2.3.4 to 2.3.5
TheStigx said:
Nope, only if it is a brand new version, like the ICS, then you will loose it. But not if you change from gingerbread 2.3.4 to 2.3.5
Click to expand...
Click to collapse
My experience is, that one will have to reapply root, if he installs something from stock.
But maybe I did something wrong in the past
My experience with CWM has been nothing but good. You should just install that recovery. I think, in my opinion you would like it. I've had it on my HTC sensation for several months now. No issues
100% agree guys here have latest updates in there roms before any ota updates - you can be running ics now if u want . U can always go back to stock s-on later. I'm no techie but I would never go back unless I needed to for warrenty
Sent from my HTC Sensation Z710e using XDA App
Hey Guys
So I unlocked my phone's bootloader last week, and installed The AxiomS ROM.
I was pretty excited given all the epic features. Anyway my excitement soon turned
to regret. My files are getting corrupt (Images, Videos, APK's, everything...) and
my battery life has been very lower than I had on my stock ROM. I thought I might
run into trouble with the Custom ROM so I made a Nandroid backup of my Stock
ROM. The problem is, apparently a stock ROM won't run unless the bootloader is
relocked. So I restored the backup through recovery, relocked the bootloader, but I
got stuck in a bootloop. Only way I can get a ROM on there after I relocked the boot
loader is to run a RUU from the PC (Correct me if I'm wrong :cyclops: ) I don't want
to download an external stock ROM, so my question is - Is it possible to build a RUU
from my Nandroid backup ?
Any help would be appreciated. Thanx guys ! P.S I'm still running AxiomS at the moment...
Will be trying out Team Venom's ViperOneS ROM soon.
Christian
It probably didn't restore the boot.img but you sure can run a stock rom with unlocked bootloader. Try to extract boot.img from backup, unlock bootloader again and flash boot.img through adb or just run the RUU of your stock rom.
T-MobileUS HTC One S running Stock Rooted 2.21.
Just backup and flash Venom following the directions in the thread precisely. BTW, my SD card was getting corrupted a lot too...stopped when I stopped mounting it as USB storage and using bluetooth and wifi to transfer files. Something with this phone doesn't unmount cleanly for some people.
fmedrano1977 said:
It probably didn't restore the boot.img but you sure can run a stock rom with unlocked bootloader. Try to extract boot.img from backup, unlock bootloader again and flash boot.img through adb or just run the RUU of your stock rom.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
I actually did do exactly that, as I know the boot image isn't installed with the ROM. Learned to do it when I installed Axiom...
Anyway, I still got stuck in a boot loop... But I'll Try it again. Any way to build a RUU ?
el_smurfo said:
Just backup and flash Venom following the directions in the thread precisely. BTW, my SD card was getting corrupted a lot too...stopped when I stopped mounting it as USB storage and using bluetooth and wifi to transfer files. Something with this phone doesn't unmount cleanly for some people.
Click to expand...
Click to collapse
Thanx for the help with the Data... Will give it a Try ! I'm busy downloading The Venom ROM now.
But for some reason It's EXTREMELY slow. Like 10Kb/s... It's quite bad. I've tried with different service
providers (we use like three between our family). Any thoughts ?
777Christian777 said:
Thanx for the help with the Data... Will give it a Try ! I'm busy downloading The Venom ROM now.
But for some reason It's EXTREMELY slow. Like 10Kb/s... It's quite bad. I've tried with different service
providers (we use like three between our family). Any thoughts ?
Click to expand...
Click to collapse
I know its an old thread BUT
The OP didn't get an answer to his question and i would like to hear members thought on the subject anyway
Is it possible to make a RUU from any given ROM
Im just surprised that its not been developed on here before now
On my travels i found this
http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/
Now if it possible to extract the rom from the ruu why not the reverse ?
You can turn Mustang into Pinto, but you can not turn Pinto into Mustang. Any downloaded rom have 3 files in it - Meta, System and boot.img. RUU have firmware( in addition ) and is in exe format. Just can not be done from back up rom. The easy way would be to download the RUU.
I know that it is "pain in the butt", but that way, you will get your phone back to "normal".
liesnomore said:
You can turn Mustang into Pinto, but you can not turn Pinto into Mustang. Any downloaded rom have 3 files in it - Meta, System and boot.img. RUU have firmware( in addition ) and is in exe format. Just can not be done from back up rom. The easy way would be to download the RUU.
I know that it is "pain in the butt", but that way, you will get your phone back to "normal".
Click to expand...
Click to collapse
Dead right its a pain especially when HTC release the RUUs when and if they choose to...just how many members do you searching around for RUUs that have not been released...and were talking phones that are 8 months or in some instances older
Hi,
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
Or, can I flash OTA update as update.zip in TWRP recovery?
sorry, for my bad english.
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
JohnKoeMan said:
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
Click to expand...
Click to collapse
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
Haha no problems friend!
I've found a link to a custom ROM using JB 4.1.1, you can look into that?
http://forum.xda-developers.com/showthread.php?t=1871866
Also you can instead remove TWRP (if you know how) and instead install CWM (clockworkmod).
I found CWM to work better than TWRP.
I myself am using CyanogenMod 10.1, very nice and clean, works perfectly ad has Android 4.2.1
That might also be an option if you want a clean ROM. ^^
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
orenfl said:
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
Click to expand...
Click to collapse
Since I'm facing the same problem, and there is no RUU for now, how and where to get a JB OTA nandroid... Haven't seen any around.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
tominozh said:
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
bo6o said:
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
Click to expand...
Click to collapse
Yes, you should be. Download zenrom, reboot recovery, wipe everything a few times, flash zenrom, set it up, then recovery, flash STOCK RECOVERY ( very important), prompt for update, download, install, set up, ( you may get a few errors here and there so just do factory reset in setting-->factory reset). Then flash twrp, flash superuser, backup.
Sent from my HTC One S using xda app-developers app
After two weeks of forum crawling and surviving 2 soft-bricking incidents, I've finally decided to reach out for help from the experts :crying:
Currently I have an ATT HOX, unlocked/rooted/SuperCID - running stock ICS (4.0.4).
My goal is to get JB on it and then flash to Blade ROM (I tried flashing to Blade with ICS - OOPS!)
Even though the info is on the forums - it's not all together in a streamlined format for me to follow - I feel I could get lost and screw it up (again)
From what I gathered from reading - here is what I "think" I need to do from my current phone state:
1. Facepalm S-Off
2. Install OTA Rootkeeper then backup root
3. Flash stock recovery
4. Re-Lock Bootloader
5. Flash OTA ATT JB.zip using stock recovery
6. Unlock Bootloader
7. Flash TWRP
8. Restore backup root with OTA RK
9. Flash Blade ROM
Can someone please check my thinking and make sure I'm not missing something?
Or any recommendation of an easier process? I feel I'm going to get lost somewhere in those steps and end up in Oz.
Or maybe a recommendation on an awesome ICS Rom? (so I can avoid confusing myself)
I'm terrified of another 3AM morning and a bricked-out HOX.
Thanks in advance!
Do you mean this rom: http://forum.xda-developers.com/showthread.php?t=2134328?
Because that's a rom for the quad-core Tegra One X. If you've been doing that, it's no wonder you got bricked.
You don't need OTA Rootkeeper. You can just flash a rooted rom.
2 major points:
1) As already mentioned, Blade is not for our phone, its for the quad core One X. Stay within this forum section. If you are looking at any XDA thread that just says "HTC One X" (no mention of "AT&T, Rogers" etc.) near the top of the screen, you are in the wrong section. Stick to the forum section that mentions AT&T. Flashing a ROM for the quad core version won't work, and might also hard brick your phone.
2) Aside from S-Off which is a good idea) you don't need to mess with any of the stuff you mentioned (Rootkeeper, stock recovery, OTA zip) in order to flash a JB based custom ROM if you are already bootloader unlocked and have TWRP. With S-off, just flash the ROM. If S-on, just flash the ROM, then flash the boot.img with fastboot (if hboot 1.14 or higher).
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
redpoint73 said:
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
Click to expand...
Click to collapse
<---- desperate noob
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
I can't believe I lost sleep over the simplicity of it all.
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Thanks a ton guys!
razorc03 said:
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Click to expand...
Click to collapse
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
iElvis said:
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
Click to expand...
Click to collapse
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
razorc03 said:
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
Click to expand...
Click to collapse
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
iElvis said:
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
Click to expand...
Click to collapse
Thanks for the info. But I need to bug you again.:angel:
A few questions about the ruu method. After you ruu, does that remove root, lock bootloader, and goes back to s-on?
And since I love numbered steps, here is how I am viewing it with my inexperienced understanding with question marks:
1. Check for S-off
2. Lock bootloader? (I guess not with S-off)
3. Run ruu 2.20 exe
4. Flash 3.18 ota
5. Rerun superCID (X-Factor xploit)?
6. Unlock bootloader
7. Flash TWRP
8. Flash ROM (Assuming S-off wasn't changed during the ruu)
I would love to be at your confidence level to run it it 30 minutes. One day I guess....
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
iElvis said:
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
Click to expand...
Click to collapse
Thanks for the checklist! It makes me feel safer to know an exit strategy so I don't panic if/when stuff goes bad.
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
razorc03 said:
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
Click to expand...
Click to collapse
This varies completely by device, and firmware versions. Never assume that something you learned on another Android device applies to a different device.
razorc03 said:
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
Click to expand...
Click to collapse
No, it's that once you're unlocked, you can re-root just by flashing a rooted rom.
after installing maximus hd on m htc one s I have only 2gb of available space for my pictures/music etc. what Have I done and how do i fix it to give me more available space?
Thanks
arinb12 said:
after installing maximus hd on m htc one s I have only 2gb of available space for my pictures/music etc. what Have I done and how do i fix it to give me more available space?
Thanks
Click to expand...
Click to collapse
Or any other rom I can install without this problem. Im handing the phone over to my mum who doesnt care as long as there is space and it works
Or any other rom I can install without this problem. Im handing the phone over to my mum who doesnt care as long as there is space and it works.
Only interested in battery life and useablility not fussed by sense 5 etc
Did you flash the firmware and the modfied TWRP, that are required to run MaximusHD?
Flippy498 said:
Did you flash the firmware and the modfied TWRP, that are required to run MaximusHD?
Click to expand...
Click to collapse
cant recall, this was a while back - the phone went into storage since then.
how can i find out?
arinb12 said:
cant recall, this was a while back - the phone went into storage since then.
how can i find out?
Click to expand...
Click to collapse
twrp is installed though.
If you flashed the required firmware your hboot version should be 2.16. Just boot into bootloader to find out which version you're using.
And the correct TWRP version is either the modified version 2.6.1 you can download from the MaxismusHD thread or the modified version you can find in this thread. Look at post #3 to find what you're looking for.
2.15
all i want is my storage back and for it to remain unlocked for all sims,
can i just re install stock rom and keep the simlock unlocked
dont care for options or tweaks.
arinb12 said:
2.15
all i want is my storage back and for it to remain unlocked for all sims,
can i just re install stock rom and keep the simlock unlocked
dont care for options or tweaks.
Click to expand...
Click to collapse
If you want to install MaximusHD you will have to follow the install instructions in the OP of the thread and this will upgrade your hboot version to 2.16 and install TWRP 2.6.1.0. Then your phone will show the correct amount of storage. Word of warning, some people have had problems with in call quality on 4.2.2 sense rom's, it seems to affect some phones more than others. If you don't want to do this, you can install Viper which is also 4.2.2 and keep hboot 2.15. Or you can use and RUU to go back to stock, your phone will stay sim unlocked but the latest official version is android 4.1. The RUU files are here, you can also use this unofficial RUU based on 4.2.2.
thanks for everyones help.
installed viper and rectified storage.