Been running ported ICS/JB roms and been having various software issues so I'm thinking about switching back to stock to wait for a stable ICS rom. Will I lose root if I odin flash the newest stock update? What are some precautions I should take other than the typical flashing checklist?
Yes you will lose root. Read through the thread in general for your answers
Related
I'm on T-Mobile USA, and have stock rom (2.3.6, Baseband T989UVKL1, Kernel 2.6.35.11, Build: GINGERBREAD.UVKL1). This phone is completely stock right now.
I just got the notification about the OTA, which I assume will be to ICS.
Questions before I accept the OTA update:
1. Will I be able to root after installing the official stock ICS update?
2. If so, would I use the ODIN method, or some other method?
3. Other than bloat, are there any known issues with the stock ICS rom.
4. Should I install CWM before accepting the OTA update?
Basically, I've tried looking but there doesn't seem to be much information about the official stock ICS update, probably because it is just starting to be rolled out.
Never mind. Just re-saw this http://www.tmonews.com/2012/05/t-mobile-rolling-out-galaxy-s-ii-maintenance-update-no-ice-cream-sandwich-yet/ and realized this update likely isn't ICS yet.
I rooted my Galaxy S2 then rooted Blazers Sexy Can I rom. I did a back up of my stock rom after I rooted it. Now that Sprint/Samsung MAY be releasing stock ICS, I may want to switch over to that. The battery sucks on Blazers rom. Anywho, if I restore to my stock GB backup with root and get the OTA update, am I doing any damage besides losing root? Could my phone be bricked just restoring my backup and updating? Also, if I decide to not do the stock update and keep my root, can I restore back to my stock GB backup then flash a new ICS custom rom with no issues? I keep wondering because I see how if you flash an ICS custom rom, you have to go back to a stock version before you flash another. I am just wondering if my backup is enough.
mapan83 said:
I rooted my Galaxy S2 then rooted Blazers Sexy Can I rom. I did a back up of my stock rom after I rooted it. Now that Sprint/Samsung MAY be releasing stock ICS, I may want to switch over to that. The battery sucks on Blazers rom. Anywho, if I restore to my stock GB backup with root and get the OTA update, am I doing any damage besides losing root? Could my phone be bricked just restoring my backup and updating? Also, if I decide to not do the stock update and keep my root, can I restore back to my stock GB backup then flash a new ICS custom rom with no issues? I keep wondering because I see how if you flash an ICS custom rom, you have to go back to a stock version before you flash another. I am just wondering if my backup is enough.
Click to expand...
Click to collapse
if you want to go back to stock el29 i would use sfhubs el29 1 click odin, then restore your backup....
if you want the stock system while keeping root just use the ff18 rooted 1 click as opposed to accepting the ota
if you're just upset about battery life but otherwise like the rom you're on now look into kobridge tweaks, and good practices for battery conservation- i.e. sync manually, set brightness low, etc... these could potentially greatly extend you're battery life
Having come from flashing SGS have read up as much as I can regarding flashing the HOX.
Have held back having a crack at a custom ROM until Jellybean update arrives on stock, to see how it runs.
However, if I do upgrade to stock Jellybean (which would have a new HBOOT?) would it still be possible to load AOSP Rom after.
If i've read correctly, unless I have a Nandroid backup of a custom ROM (whether it be Jellybean or ICS), the new HBOOT will prevent an ICS based ROM but custom Jellybean should be ok?
Lazieye said:
Having come from flashing SGS have read up as much as I can regarding flashing the HOX.
Have held back having a crack at a custom ROM until Jellybean update arrives on stock, to see how it runs.
However, if I do upgrade to stock Jellybean (which would have a new HBOOT?) would it still be possible to load AOSP Rom after.
If i've read correctly, unless I have a Nandroid backup of a custom ROM (whether it be Jellybean or ICS), the new HBOOT will prevent an ICS based ROM but custom Jellybean should be ok?
Click to expand...
Click to collapse
It's a confusing, ill-explained situation a lot of people are confused about.
From what i understand, when upgrading to JellyBean (including the upgraded hboot), you can STILL flash ICS custom roms & nandroid back ups. However, what you will be unable to do is flash any sort of Ice cream sandwich RUU's. This is because, the upgraded hboot will cause errors in the installation (considering the hboot version in the RUU, will be of a totally different earlier version).
Hope this clears it up a little bit.
I have a quick question. I am on a stock rooted 4.1.1 att sgs3. I was curious if i flashed this rom/kernal,[ROM/KERNEL][4.4.2] Quantum 3.54 & QuantumKernel 3/7, would i be able to go back to my stock rooted rom if I wanted to? Thanks in advance.
Looks like you are trying to flash a custom ROM. Don't know much about these particular ROMs you mentioned but you need to your research thoroughly on custom ROMs before flashing. You may know most Custom ROMs don't come with their own bootloaders but still have to rely on a manufacturer's bootloader to run. You should, therefore, avoid any ROM that may update your bootloader because this is the only way that you would not be able to return to your previous stock version. If the ROM simply updates the system without mucking with your bootloader, there is no reason why you may not be able to return to stock.
I had an AT&T SG3 on stock 4.1.1 and I was able to flash KitKat (4.4) based CM11 and return to stock 4.1.1 without any hitches. Finally, whilst you are still on stock 4.1.1 I would suggest you take advantage of all the flexibilities offered by this Android version especially free unlocking before you begin tinkering with firmware.
So as long as I dont update my bootloader, I should be fine on going back to stock rooted 4.1.1? Thanks for the info!!
So how do i know what roms dont mess with the bootloader?
Most ROMS do not include an aboot file. I have flashed CM11, Validus, Slim, and Cyanfox and none of these altered the bootloader.
I suggest that you find a ROM you like, unzip the file, and look at the updater script to determine which bootloaders are required to install the ROM on your phone.
Ok guys, thanks for the tips. I just didn't want to get stuck on a firmware where i could not have root anymore or go back to a stock rooted rom.
I'm running rooted stock 4.3 N900TUVUBMI7.
It was flashed back in December 2013 since that was the only way to accomplish root.
I had no interest in KitKat but do want the official Lollipop.
Because I'm rooted I'm unable to even download and successfully install the KitKat update.
Is there a way to update my 4.3 Jelly Bean to the latest official 5.? Lollipop?
If so, how? Can it be upgraded or will it need to be flashed fresh?
If it is a fresh flash, can I just download the official lollipop and flash with odin?
Already have my apps backed up, so it's not the end of the world if I lose them.
TIA!
Disturbed_One said:
I'm running rooted stock 4.3 N900TUVUBMI7.
It was flashed back in December 2013 since that was the only way to accomplish root.
I had no interest in KitKat but do want the official Lollipop.
Because I'm rooted I'm unable to even download and successfully install the KitKat update.
Is there a way to update my 4.3 Jelly Bean to the latest official 5.? Lollipop?
If so, how? Can it be upgraded or will it need to be flashed fresh?
If it is a fresh flash, can I just download the official lollipop and flash with odin?
Already have my apps backed up, so it's not the end of the world if I lose them.
TIA!
Click to expand...
Click to collapse
There is a great thread that was started by TEKHD: http://forum.xda-developers.com/showthread.php?t=2672393
He walks you through using ODIN to take 4.x.x firmware to 5.0 stock, then additional steps to root, add a TWRP custom recovery (needed to flash a custom ROM), and a few additional things. The link he posts for the actual stock firmware is from sammobile which is a great site but the download speeds are abysmal if you aren't a premium member. Here is a media fire link that I used: http://www.mediafire.com/download/cuoz62g1ca6id9t
Have fun! Btw it is recommended to wipe your device, but I decided not to do that to test if it would work (I had a full nandroid and EFS back up just in case) Stock lollipop upgraded flawlessly and I kept all my apps contacts etc etc... Now im waiting on a decent 5.0 non Touchwiz ROM. I've been using ECHOE ROM which is made for n9005 and is a TW but works with t-mobile as long as you flash a wifi fix. I like Filchis wifi fix. The ROM itself is buttery smooth but im hoping CM12.1 will be awesome with 5.1 lollipop
melead said:
There is a great thread that was started by TEKHD: http://forum.xda-developers.com/showthread.php?t=2672393
He walks you through using ODIN to take 4.x.x firmware to 5.0 stock, then additional steps to root, add a TWRP custom recovery (needed to flash a custom ROM), and a few additional things. The link he posts for the actual stock firmware is from sammobile which is a great site but the download speeds are abysmal if you aren't a premium member. Here is a media fire link that I used: http://www.mediafire.com/download/cuoz62g1ca6id9t
Have fun! Btw it is recommended to wipe your device, but I decided not to do that to test if it would work (I had a full nandroid and EFS back up just in case) Stock lollipop upgraded flawlessly and I kept all my apps contacts etc etc... Now im waiting on a decent 5.0 non Touchwiz ROM. I've been using ECHOE ROM which is made for n9005 and is a TW but works with t-mobile as long as you flash a wifi fix. I like Filchis wifi fix. The ROM itself is buttery smooth but im hoping CM12.1 will be awesome with 5.1 lollipop
Click to expand...
Click to collapse
Thanks for the reply, thread worked perfectly.
Did flash as just an upgrade but it broke my messages. Wiped it and started fresh, no issues so far.
Thanks again!