Hi all, back when the unlock was released for this phone I installed a custom GB rom on my brother's phone. I am very experienced.with flashing and rooting etc so this wasn't a problem. Now with S-Off things have gotten a bit more complicated, not to mention the mainver nonsense I've been reading about. To make matters worse I haven't found a good thread outlining all these details on what needs to be done for the transition from GB to ICS; everyone basically assumes you're already on ICS and either S-On or S-Off.
So I have a few questions I'm hoping someone can answer.
1. I want to keep my brother's phone S-On. I have reviewed the S-Off method and deem it too risky for hardware that is not my own. That said, what's the best path to getting to a custom ICS OTA based rom from GB firmware?
a. Should I flash stock GB, relock phone, install OTA, unlock phone, install custom ICS rom?
b. Should I directly install a certain firmware from the boot loader along with a custom ICS OTA based rom from recovery? If so, which firmware should I flash? Is there any mainver stuff I need to tweak?
c. Or something else?
2. I always perform backups before flashing a new rom to ensure if something goes wrong I can restore to the previous rom image. However, if I backup a GB rom that runs on an older firmware and install ICS based on a newer firmware, would restoring to GB be as simple as going into recovery and restoring his old GB rom? Or would I have to flash the old firmware first?
3. I've noticed some roms like Viper use aroma installer which can handle multiple situations of installation. Would the situation I am describing (GB firmware, S-On) be handled? I am unsure how many different firmware versions there are out there. I don't know if referring to the "old firmware" means an older ICS firmware or GB firmware.
Thank you all for your help. It is frustrating for me to be this confused about how to upgrade a phone considering the amount of times I've done it in the past. I appreciate any responses or links that could help me better understand what I must do.
so your s-on and unlocked? or locked either way
re-lock if you are unlocked and then run
the ics offical .exe RUU from
here
http://forum.xda-developers.com/showpost.php?p=29979907&postcount=133
after you do that then unlock and flash a custom recovery then flash a ics rom of your choice
Div033 said:
Hi all, back when the unlock was released for this phone I installed a custom GB rom on my brother's phone. I am very experienced.with flashing and rooting etc so this wasn't a problem. Now with S-Off things have gotten a bit more complicated, not to mention the mainver nonsense I've been reading about. To make matters worse I haven't found a good thread outlining all these details on what needs to be done for the transition from GB to ICS; everyone basically assumes you're already on ICS and either S-On or S-Off.
So I have a few questions I'm hoping someone can answer.
1. I want to keep my brother's phone S-On. I have reviewed the S-Off method and deem it too risky for hardware that is not my own. That said, what's the best path to getting to a custom ICS OTA based rom from GB firmware?
a. Should I flash stock GB, relock phone, install OTA, unlock phone, install custom ICS rom?
b. Should I directly install a certain firmware from the boot loader along with a custom ICS OTA based rom from recovery? If so, which firmware should I flash? Is there any mainver stuff I need to tweak?
c. Or something else?
2. I always perform backups before flashing a new rom to ensure if something goes wrong I can restore to the previous rom image. However, if I backup a GB rom that runs on an older firmware and install ICS based on a newer firmware, would restoring to GB be as simple as going into recovery and restoring his old GB rom? Or would I have to flash the old firmware first?
3. I've noticed some roms like Viper use aroma installer which can handle multiple situations of installation. Would the situation I am describing (GB firmware, S-On) be handled? I am unsure how many different firmware versions there are out there. I don't know if referring to the "old firmware" means an older ICS firmware or GB firmware.
Thank you all for your help. It is frustrating for me to be this confused about how to upgrade a phone considering the amount of times I've done it in the past. I appreciate any responses or links that could help me better understand what I must do.
Click to expand...
Click to collapse
Try CleanROM, I've been using it since I got it. Very easy to install with S-On.
nstallation for S-ON Devices on Gingerbread firmware
Copy ROM to SD Card AND PH98IMG.zip AND GB Firmware Patch to ROOT of SD Card
Reboot to recovery
wipe data / Factory Reset
Flash ROM
Flash GB Fimrware Patch
Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
Reboot
Profit!
Click to expand...
Click to collapse
The phone might say something about the SD card not working, so make sure you download the Gingerbread Firmware patch. Just Flash it like a rom and you're all god
Related
Hi,
I have a TF201 running ICS WW version.
I've been searching for days now trying to understand how you update to JB from ICS without bricking your device as there seems to be various warnings that your bootloader must be the correct version in order to flash the correct rom.
So my version is 2.10. I would have assumed from the numbering that that implies I have a HC bootloader? But I'm currently running ICS.
So, im sorry if this is a rookie question, but how do I update to JB from ICS when my bootloader is this version. Or perhaps more directly, how do I update my bootloader version to the JB version so I can then flash the correct ROM.
On a side note, I seem to have both CWM recovery mode 5.5.0.4 and TWRP v2.3.0.0 installed. Currently however I can only access TWRP by holding down volume down and power which brings me straight to the multiple choice of fastboot, TWRP. cold boot and wipe.
I have installed nvFLASH and backed up my blobs prior to all this - in case something like this happened
Thanks for your time
The easiest way to upgrade to the JB Boot loader is to just flash a rom that has it included such as Androwook 1.3 from the dev forum. Since you have nvflash victory you're safe from about any brick as long as you have your file back ups backed up 3x over :laugh:
McJesus15 said:
The easiest way to upgrade to the JB Boot loader is to just flash a rom that has it included such as Androwook 1.3 from the dev forum. Since you have nvflash victory you're safe from about any brick as long as you have your file back ups backed up 3x over :laugh:
Click to expand...
Click to collapse
wonderful thank-you! im now happily using HB 1.51 .
That's good, but I'm stuck in the same way and that rom is not available anymore...
Any suggestion or link to that rom?
Help please.
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
bloodbath said:
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
Click to expand...
Click to collapse
you need to flash the original recovery to install ota updates,, you will lose root access doing so
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
All you need to do is put the stock Tmo recovery on your one. Then go update with ota and you will still be unlocked but you do lose root.
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
bloodbath said:
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
Click to expand...
Click to collapse
I'm sorry I was wrong you will lose root after you update ota. But you can do ota while being unlocked so no need to relock bootloader just flash the stock Tmo recovery and update.
chong67 said:
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
Click to expand...
Click to collapse
U mean something like this!? https://copy.com/aSLnP
Team-Noctural.com/androidtechy.com/droidnow.com
Hello,
I wanted to have newer android and have rooted and flashed HTC Amaze with Hasoons toolkit using TWRP recovery system. After flashing Cyanogenmod 10 ROM through ADB Sideload and flashing Cyanogenmod 10 ROM kernel (boot.img file which was included in the zipped folder) manually with Hasoons toolkit, the phone started to boot normally, load welcome screen, but after several seconds it freezes and then restarts. Can you please help what can be the cause of this problem and how can I repair? The phone is rooted and bootloader unlocked, but its still S-ON.
Before installing the Cyanogenmod I have tried to flash other ROMs, but on all of them after flashing kernel, the phone was freezing on booting mode and then just restarting continuously.
I hope there should be some way out and the phone is not bricked. If something I have backed up the data and will try to restore, but would prefer to repair Cyanogenmod ROM.
Thank you guys in advance for your help.
ratijs100 said:
Hello,
I wanted to have newer android and have rooted and flashed HTC Amaze with Hasoons toolkit using TWRP recovery system. After flashing Cyanogenmod 10 ROM through ADB Sideload and flashing Cyanogenmod 10 ROM kernel (boot.img file which was included in the zipped folder) manually with Hasoons toolkit, the phone started to boot normally, load welcome screen, but after several seconds it freezes and then restarts. Can you please help what can be the cause of this problem and how can I repair? The phone is rooted and bootloader unlocked, but its still S-ON.
Before installing the Cyanogenmod I have tried to flash other ROMs, but on all of them after flashing kernel, the phone was freezing on booting mode and then just restarting continuously.
I hope there should be some way out and the phone is not bricked. If something I have backed up the data and will try to restore, but would prefer to repair Cyanogenmod ROM.
Thank you guys in advance for your help.
Click to expand...
Click to collapse
Did you follow the directions posted in the pinned threads at the top of the forums and update to ICS before unlocking and flashing these other ROMs?
I ask because if you say you're unlocked, but s-on, and you need to be on an ICS radio baseband prior to flashing any newer ROM. If you were already on ICS prior to these flash attempts then I suggest you try again with the latest version of 4ext instead of TWRP, and make sure to enable smart-flash. TWRP doesn't flash kernels properly on HTC handsets with s-on, while 4ext does when smart-flash is enabled. Of course all of this comes with the stipulation that you're doing this on a T-Mobile US version handset.
If you're on an Asian or non-branded international version it gets a bit more complicated because you must attain s-off before attempting to flash. This is because these handsets never got an ICS update. So there is no carrier image to flash to, and the only way to install the updated firmware with the ICS baseband is to attain s-off first then flash the T-Mobile US image.
Again, if you haven't I strongly suggest reading the pinned threads at the top of the different forums here as they contain all of the info you need to successfully flash your device to an updated ROM. Good luck.
Ciao
Odysseus1962 said:
Did you follow the directions posted in the pinned threads at the top of the forums and update to ICS before unlocking and flashing these other ROMs?
I ask because if you say you're unlocked, but s-on, and you need to be on an ICS radio baseband prior to flashing any newer ROM. If you were already on ICS prior to these flash attempts then I suggest you try again with the latest version of 4ext instead of TWRP, and make sure to enable smart-flash. TWRP doesn't flash kernels properly on HTC handsets with s-on, while 4ext does when smart-flash is enabled. Of course all of this comes with the stipulation that you're doing this on a T-Mobile US version handset.
If you're on an Asian or non-branded international version it gets a bit more complicated because you must attain s-off before attempting to flash. This is because these handsets never got an ICS update. So there is no carrier image to flash to, and the only way to install the updated firmware with the ICS baseband is to attain s-off first then flash the T-Mobile US image.
Again, if you haven't I strongly suggest reading the pinned threads at the top of the different forums here as they contain all of the info you need to successfully flash your device to an updated ROM. Good luck.
Ciao
Click to expand...
Click to collapse
Thank you for information. It is non-branded international version. It means I will have to try S-off and then flash the ROM with 4ext.
ratijs100 said:
Thank you for information. It is non-branded international version. It means I will have to try S-off and then flash the ROM with 4ext.
Click to expand...
Click to collapse
Please read the pinned threads first. You're going to have to relock your bootloader before proceeding, so save the binary unlock blob you got from HTC as you'll need it to unlock again. Place the stock image in the root of your external SD card and flash from hboot. Then after getting s-off and superCID then you can flash the T-Mobile ICS image. Again read the pinned threads thoroughly or you'll be posting about how to unbrick your handset. Good luck.
Ciao
I had the same issues and had to turn off security with the joupunut bear program. Just to be safe with future flashing I've understood it works best. You should first s-off your phone and then go about flashing whichever firmware you want. Make sure you upgrade to the stock ics rom first as a pre requisite towards flashing any other rom and you'll be fine. Do a search on the stuff needed to gain s-off here in the forums. Report back if you need more assistance
Sent from my T-Mobile myTouch using xda app-developers app
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
Ok so im not new to the rooting scene but am new to the flashing scene. I know a good jist of it but cant seam to figure out the whole firmware process.
I want to install this ROM: http://forum.xda-developers.com/showthread.php?t=2699616
I am currently running 4.4.2 with 1.58.xx firmware unlocked S-OFF and rooted. and this ROM requires 2.22.1540.4
Now I have found the 2.22.1540.4 firmware and know that i have to relock my bootloader and such but my phone says my ID is CWS__001 and i cant find any with that.
Also if i flash the newest 2.23.xx firmware will i still be able to flash any rom using older firmware versions?
And last question say i am flashing a new firmware and it screws up, since my custom recovery gets removed how do i flash my nandroid backup.
also if successfully flash the new firmware am i able to flash my old backup to restore to a old firmware or do i need to reflash the old firmware first.
sorry for so many questions i just dont want to blow up my phone due to stupid mistakes.
EDIT: so I think i managed to update my firmware. In bootloader it shows 2.22.1540.3 under os but in the phone settings it still says 4.4.2 and 1.58.xxx. I am assuming all i need is a updated firmware to run the mods and not a updated software? correct me if im wrong.
What exactly did you flash (link it if you can)? I think you are confusing software (OS or ROM) with firmware. Firmware as its mostly commonly discussed here (updating to run 2.xx based ROMs) refers to the hboot, radio, recovery, and other modules (media, WiFi, Bluetooth and more) deployed with an RUU or OTA. You have only flashed firmware if you installed an RUU/OTA or manually flashed it with fastboot.
devonjerothe said:
Also if i flash the newest 2.23.xx firmware will i still be able to flash any rom using older firmware versions?
Click to expand...
Click to collapse
Yes, 2.23 firmware will work as well. But again, make sure you are talking about the right thing (firmware versus software/OS).