I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
loonytoon500 said:
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
Click to expand...
Click to collapse
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
ShapesBlue said:
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
Click to expand...
Click to collapse
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
loonytoon500 said:
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
Click to expand...
Click to collapse
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
ShapesBlue said:
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
Click to expand...
Click to collapse
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
loonytoon500 said:
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
Click to expand...
Click to collapse
After all the reading I've done in order to take the OTA you have to unroot. I don't know the complete process as I am not on any OTA
From my S3 running BlissStalk
Even if you dont care about custom ROMs right now you may in the future when there are no updates released for the phone or you want to sell it and could have gotten a higher price with the lower system version. Before you update try some of the ROMs out and see if there are some you like and if you dont like any then update.
That being said I have updated using ODIN and the firmware I got from this site. look around and you will find the stuff you need.
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
loonytoon500 said:
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
Click to expand...
Click to collapse
Sure it's possible, but unlikely. To put into perspective, I don't believe there has been a bootloader unlock for Verizon Notes 2-4 and Galaxy S4-5 (which would allow one to natively run AOSP without Safestrap) so the likelihood is low.
Sent from my SCH-I535 using Tapatalk
Related
I am relatively new to the rooting experience but am a big fan of the benefits. I only do basic stuff and am too paranoid to try flashing ROMs or anything too advanced. I recently downloaded the most recent update and it didn't go as I had anticipated.
I was taken to the reboot screen as if I was using Clockwork Mod. It asked me questions that I had to answer in order to proceed but the choices were strange. It would ask me, "do you want to install this unfamiliar zip?" and the answers would be, "No, No, No, No, No, No, Yes, No, No, No, Go Back." I picked yes for the 3 different choices and it completed the install.
After the phone rebooted there was a message saying that the update had failed. I called my brother who has an unrooted phone and checked to see that I in fact do have the update. I am wondering if this is what will happen each time I get an update and if there is anything I should be worried about. The phone is still rooted and I don't notice anything different, but I am just paranoid that rooting my phone will make it so I am unable to install the jellybean update next month. Thanks for the advice in advance!
that sounds like CWM or it might be the factory download mode but either way i dont think you should have to do that for a factory update
So you are on stock, but rooted? Usually the rule of thumb is not not accept the OTA updates, but rather flash one of the stock, rooted roms when an update comes out. You might wnat to try something like the root66 rom, if not somehting like Synergy or CleanRom, which are still stock-based.
As far as this particular issue, as far as I knew, the OTA updates will usually always install. The problem is that they will sometimes revert back to un-rooted, and sometimes will even block the root exploit so you're stuck.
update will fail if you are using a custom recovery, i.e. cwm
wwjdd44 said:
update will fail if you are using a custom recovery, i.e. cwm
Click to expand...
Click to collapse
Is there any way to remove clockwork mod? I don't really need it.
Usually the information I need I can find easily here, I've never had a need to register and post until today. I've searched but can't quite find the answer to my question. So I apologize in advance if my search skills have failed me this time.
I am on a VzW SGS3 that has taken the unfortunate MD3 update. I am rooted and unlocked already. I have ClockworkMod Recovery installed. Everything is as OK as MD3 can be. I had followed the instructions in this thread in the past:
http://forum.xda-developers.com/showthread.php?t=2046439
It appears the users in that thread are awaiting the MF1 bootchain from the latest posts and other users have tried to take the OTA MF1 update and got the dreaded triangle, were forced to reflash stock, take all the OTA updates and await the bootchain to unlock again.
So with that bit of background, my question is thus: what is the easiest way to take on new OTA updates without losing all my data?
I can flash a stock ROM someone made for MF1 but I'm pretty sure I lose data since the best way to flash ROM's is clean. I don't want to deal with dirty flash issues. Do I really have to go through and set up Nova Launcher (and other apps) just the way I like it again? Do I have to go through each app and backup settings (or use Titanium?) I don't really want to go stock, take all OTA's then use Casual just to get MF1 now. I think that would require clean install too and I can certainly wait as Casual doesn't really give you a choice of your root and recovery elements from what I understand.
This thread ( http://forum.xda-developers.com/showthread.php?t=1974114 ) provides a nice stock image without losing any data. It's back to MB1, then one would take the OTA updates, then follow the rest of the guide to root and unlock. Still need to wait for the MF1 bootchain though - is THIS the best way?
Basically, what is the "best practice" when one is already rooted, unlocked and has a custom recovery to take on new OTA updates?
MRV18 said:
Usually the information I need I can find easily here, I've never had a need to register and post until today. I've searched but can't quite find the answer to my question. So I apologize in advance if my search skills have failed me this time.
I am on a VzW SGS3 that has taken the unfortunate MD3 update. I am rooted and unlocked already. I have ClockworkMod Recovery installed. Everything is as OK as MD3 can be. I had followed the instructions in this thread in the past:
http://forum.xda-developers.com/showthread.php?t=2046439
It appears the users in that thread are awaiting the MF1 bootchain from the latest posts and other users have tried to take the OTA MF1 update and got the dreaded triangle, were forced to reflash stock, take all the OTA updates and await the bootchain to unlock again.
So with that bit of background, my question is thus: what is the easiest way to take on new OTA updates without losing all my data?
I can flash a stock ROM someone made for MF1 but I'm pretty sure I lose data since the best way to flash ROM's is clean. I don't want to deal with dirty flash issues. Do I really have to go through and set up Nova Launcher (and other apps) just the way I like it again? Do I have to go through each app and backup settings (or use Titanium?) I don't really want to go stock, take all OTA's then use Casual just to get MF1 now. I think that would require clean install too and I can certainly wait as Casual doesn't really give you a choice of your root and recovery elements from what I understand.
This thread ( http://forum.xda-developers.com/showthread.php?t=1974114 ) provides a nice stock image without losing any data. It's back to MB1, then one would take the OTA updates, then follow the rest of the guide to root and unlock. Still need to wait for the MF1 bootchain though - is THIS the best way?
Basically, what is the "best practice" when one is already rooted, unlocked and has a custom recovery to take on new OTA updates?
Click to expand...
Click to collapse
Just flash Scrosler's stock rooted ROM and you'll be good to go. You won't have any problems with not wiping (except for it might be a little itchy :laugh::laugh::silly
The best "practice" is not to take an OTA when you're rooted because chances are you will already be running it before it is out! Also, it is always a good idea to keep a backup of your apps with TiBu and use Nova to backup your desktop settings.
Thanks, I did just flash that ROM. However, my Baseband Version still shows MD3 (the Build number is MF1, however) and I still get the nag screen to take the OTA update. Not sure what to do here. I think for the time being, I'll just experiment with some other ROM's and see if I truly miss anything from Samsung.
Flash the MF1 firmware package after to get the radio.
Thanks. I did such and everything now says MF1 but this still doesn't seem ideal. My root seems to be missing (Secure Settings isn't working, I see ads in apps) and my superuser app is missing. So, perhaps I have to reload that and allow the other apps su access again? Additionally, I'm still getting nagged by the OTA update.
So before I flashed Scrosler's stock rooted ROM, I performed a backup of my current build using CwM. I didn't necessarily care for the results of the flash since I was still being nagged (not sure how to deal with that part yet) I just decided to restore my backup. Well that just screwed everything up since the /system portion wouldn't restore. Wonderful.
So I used Odin to load the no-wipe-necessary MB1 file, accepted all the subsequent OTA's (it was only two - the first one being the application of the MB1 update.zip) then just used the Casual root method on a machine with Java installed. Worked great. I'll think I'll just leave well enough alone until the next update.
OTA
I took the MF1 update OTA. Then I used the root method provided by open1your1eyes0 to root and unlock. Still waiting for the final boot gain though.
Hello. I have a XT925 running 4.1.2. The phone was rooted a long time ago. I don't remember if I installed a recovery, nor which recovery (if any) was installed at the time (volume up + power yields a boot mode selection menu; it seems to be the original bootloader).
My carrier released the 4.4.2 OTA just today. When I try to update, the phone reboots and displays an "Update failed" error message. I uninstalled as many apps as AdAway and XPosed that I think could be tampering with the process, but still I can't install the update.
How can I update to KitKat? (If it isn't obvious by now, I don't follow most of the technicalities of this things with Android. I'm fairly knowledgeable about computers, just not Android. I've read a lot of threads here and still can't figure out how to do this!)
Will I be able to re-root the phone afterwards? Will I be able to unlock it?
Thanks!
unless you have some concerns about warranty, I suggest go ahead and unlock bootlocader via moto website. Then you are free to do as you please, meaning uprade to kk stock, custom rom and root without hassle.
hbenz2008 said:
unless you have some concerns about warranty, I suggest go ahead and unlock bootlocader via moto website. Then you are free to do as you please, meaning uprade to kk stock, custom rom and root without hassle.
Click to expand...
Click to collapse
Ok, I did it (and lost everything on the phone in the process). The phone said it was unlocked. The phone is now back to stock, clean 4.1.2. But I still can't update. I get the same "update failed" error message.
What should I do?
Dont panic! haha you will get it done I have no doubt.
First did you factory reset after all was done. Do that and try again
if not, there are other ways , some easier than others but all within your capabilities
http://forum.xda-developers.com/dro...tutorial-make-motorola-razr-hd-xt925-t2916465
http://forum.xda-developers.com/showthread.php?t=2760840&page=3
So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Rey0 said:
So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Click to expand...
Click to collapse
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
jagreci said:
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
Click to expand...
Click to collapse
Sounds cool then. Thanks
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
crucialcolin said:
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
Click to expand...
Click to collapse
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
beekay201 said:
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
Click to expand...
Click to collapse
I've actually been spoiled by nandroid on the HP TouchPad with CM. Really nice to have a complete backup image. Wish I would have thought about unlocking and rooting before I got a bunch of stuff on my Nexus setup the way I like it. Sort of stuck since you have to unlock the boot loader for a custom recovery. Thus is life though.
I haven't tried it yet but it looks like Adb can do it on a stock device.
ex: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
I'm actually extremely torn on the OTA thing. I find it just so damn convenient with the admission I've gotten lazy of late Otherwise I have a tendency to never update.
So as the title says, I recently sunshine unlocked my 4.2.2 (12.15.15 firmware) MAXX. At this point, I have a custom recovery from the root method I used on the phone a year ago, but other than that I'm just running the stock 4.2.2 Camera update.
What is the easiest way to get up and running on a current 4.4.4 build? Can I use RSDlite to return to stock 4.2.2, or does that not work with an unlocked bootloader? Could I RSDlite to 4.4.4 directly? What about flashing TWRP to my phone now and using that to flash a 4.4.4 rom? I dont care about losing all of my data or anything like that.
I'm a little confused on what I can and can't flash depending on the current version of andoid I'm on, so any help would be greatly appreciated. Thanks!
now that your bootloader is unlocked you can have root on any fw version you decide to update to. but you have to be on stock everything before you update to 4.4.4. if the recovery is the only thing you have changed you can just extract it from the fxz for 4.2.2 if that's what your on right now. flash it using fastboot or the easy way using rashr an app from play store. my fav for flashing recoveries. then take the update. after that you can flash T.W.R.P 2.8.4.0 for obake. then reboot to recovery. reboot to system to gain root if it is removed by updating
Thanks for the reply. I'll look into flashing that recovery and try the OTA. Would flashing the whole fxz (which i believe includes a bootlader) hurt me? Also, is there any way one of the OTA's changes the bootloader in a way that could mess up my unlock?
no. once your bootloader is unlocked then it won't relock unless you lock it by command prompt. yes you could use rsd to go back to stock. it has to be the exact version you are currently on. if you try to rsd a version your not on it will fail.
Will it fail in a "your phone is bricked" kind of way or an error message telling you it wont flash?
it will error telling it was aborted. i have done it once that's all it took for me to realise it needed the exact version. i was lucky to have the right one handy
here is a site for all the stock firmware.
http://motofirmware.center/files/category/
I'm in the same boat and going to do this tonight on my wife's phone.
She's currently on 4.2.2, bootloader is unlocked, rooted, and currently has TWRP installed.
If I'm correct, I need to
1. Flash stock recovery
2. Boot up and take the OTAs
then
3. Flash the latest TWRP
4. Use TWRP to re-root
4. Then I can flash a 4.4.4 rom, such as http://forum.xda-developers.com/showthread.php?t=2716824
Is that correct?
As long as my bootloader is unlocked, can I still regain root with the latest OTA?
Thanks guys, just making sure as the wife will be miffed if I screw up her phone!
Honestly, I doubt you have waited this long, but if you have, here is what I am gathering from your question... You want to run 4.4.4 roms instead of 4.2? While on 4.2.2 (if you still are) you can run OSE, AOSB, CM11, and pretty much any 4.4.4 custom rom. (though i can't get cm12 to work on a mini (same software/bootloader/recovery for the most part) on 19.6.3 so that may be out) The only reason you would have to update would be to be on stock 4.4.4. I haven't read up too much on the new OTA's, but I can say this, YOU CAN NEVER GO BACK TO WHAT YOU ARE ON ONCE YOU UPGRADE STOCK. this may not be a big deal for you, but personally, I liked the JB software the best (specifically 12.7.7 that my DEV MAXX came with) I haven't heard anyone say anything positive (really) about VOLTE or any new features, and honestly, not being able to go back on a DEV EDITION sucks. On a side note, I recently bought a Mini (bc my charge port on my DEV maxx crapped out and Moto doesn't have any more, so i am in phone purgatory waiting for *something* but pretty much anyone I have talked to is useless.) I just fxz'd back to 19.5.3 from 19.6.3, but I cannot go backwards any further *completely* @NWKENT has done it numerous times as best as it *can* be done. also, @NWKENT can confirm you absolutely cannot go back from 4.4.4 to an earlier edition. I hope this helps if you haven't upgraded yet. If you have, for most intents and purposes, you haven't really lost anything.