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.
Related
I have a brand new stock verizon S3 and am wondering if I can use the MrRobinson root method to root for the very first time. I swear someone in one of the forums said they did but it sounds like most people are using those images to just update. I originally tried this 4.1.1/4.1.2 method and it bricked my phone on flashing the VRALEC bootchain step, everything looked good in odin, the phone looked like it tried to restart, then went black and never came back. I got a new phone and am wary of trying the same method again. If that is the method I have to use any thoughts on what could have went wrong?
I appreciate any input.
There should be no problem using the Mr. Robinson file in Odin. I have flashed the bootchain that soft bricked your phone and had no issue. Your following the Odin instructions exactly, right....just checking. Everything needs to be installed using the PDA slot unless it specifically says to put the file somewhere else....I have not run into that yet. You had problems with Odin before so that makes me a little apprehensive advising you to use it again.
The Mr. Robinson 4.1.2 file is not the ota. Use the 4.1.1 ota file so you can grab the 4.1.2 ota. Before installing 4.1.2 ota install ota voodoo rootkeeper....temp unroot, take ota then reroot. Pretty sure that's the only way other than flashing the bootchain that will get you on stock rooted 4.1.2
Ryno77 said:
There should be no problem using the Mr. Robinson file in Odin. I have flashed the bootchain that soft bricked your phone and had no issue. Your following the Odin instructions exactly, right....just checking. Everything needs to be installed using the PDA slot unless it specifically says to put the file somewhere else....I have not run into that yet. You had problems with Odin before so that makes me a little apprehensive advising you to use it again.
The Mr. Robinson 4.1.2 file is not the ota. Use the 4.1.1 ota file so you can grab the 4.1.2 ota. Before installing 4.1.2 ota install ota voodoo rootkeeper....temp unroot, take ota then reroot. Pretty sure that's the only way other than flashing the bootchain that will get you on stock rooted 4.1.2
Click to expand...
Click to collapse
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
I would be scared to use Odin if I had your experience too. I've used Odin several times without any issue but I have not used it since the 4.1.2 update....although I'm sure many have without any problems. Yes, you can flash any OTA via Odin even if your going backwards . I can't say you won't have any issues because I don't think you should have had an issue the first time.......maybe wait to see what others think?
Clyde Tacoma said:
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
Click to expand...
Click to collapse
idk why that happened. My best guess is if the battery was low prior to you using Odin then it may have needed charging. But that VRALEC/Odin method is proven working countless times and those files linked in the OP have been used countless times.
Just know that with mrRobinson's pre-rooted images, you'll still need to unlock your bootloader with say EZ Unlock v1.2 (available on Rootzwiki so google it) before you decide to flash custom roms/kernels.
Ryno77 said:
I would be scared to use Odin if I had your experience too. I've used Odin several times without any issue but I have not used it since the 4.1.2 update....although I'm sure many have without any problems. Yes, you can flash any OTA via Odin even if your going backwards . I can't say you won't have any issues because I don't think you should have had an issue the first time.......maybe wait to see what others think?
Click to expand...
Click to collapse
Like I said above, may have been the luck of the draw or it could have needed charging.
Clyde Tacoma said:
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
Click to expand...
Click to collapse
If you want to have a 4.1.2 rooted stock version, you need to download MrRobinson, K3 full wipe image with root (http://www.androidfilehost.com/?fid=9390214368362234355), unzip it first, then use Odin to flash this, then install Voodoo OTA root keeper from the market to preserve root, then let OTA update back to 4.1.2, finally use OTA root keeper to restore root. Done, simple and risk free.
You guys rock thank you!
As a followup for anyone that may stumble upon this thread in the future, I used the method provided by buhohitor and it worked like a champ. I flashed the mrRobinson image used ez unlocker to unlock the bootloader then used ez recovery to flash the latest version of TWRP. I'm now running this Paranoid Android 4.2.2 Rom and it is fantastic!
Please forgive me if my questions have been answered many times but I really don't know what to look for in the search menu to address my questions.
1. I have rooted my phone and installed Liquid smooth but I went back to stock (still on 4.1.2 TW) and would like to update to at least 4.3 or higher. One issue I'm having is that when the OTA comes through and I go to update it gives me an error. But even before that as I am rooted it boots into TeamWin and wants me to install from there. It has been a while since I've done anything with the boot loader and I'm afraid to install from there and/or if that is wise. (frankly I've forgotten how)
Honestly I just want a quick way to install the update to 4.3 or 4.4 or whatever the next OTA is so that I can move on. I really don't even want to mess with it much right now as my life is way to busy.
2. My search so far has shown me that others are having similar issues but they are saying that the ota update is messing up certain things with their rooted phones (haven't found the answers I'm searching for either). Should I wait on updating? If so, how do I get the ota to stop wanting me to update my phone?
Thank you for any help you can provide.
wouldn't you know, that as soon as I submit this post I find another thread dealing with the same thing... Sorry for the clutter.
Here is the thread I found http://forum.xda-developers.com/showthread.php?p=49249510
Sithlyone said:
Please forgive me if my questions have been answered many times but I really don't know what to look for in the search menu to address my questions.
1. I have rooted my phone and installed Liquid smooth but I went back to stock (still on 4.1.2 TW) and would like to update to at least 4.3 or higher. One issue I'm having is that when the OTA comes through and I go to update it gives me an error. But even before that as I am rooted it boots into TeamWin and wants me to install from there. It has been a while since I've done anything with the boot loader and I'm afraid to install from there and/or if that is wise. (frankly I've forgotten how)
Honestly I just want a quick way to install the update to 4.3 or 4.4 or whatever the next OTA is so that I can move on. I really don't even want to mess with it much right now as my life is way to busy.
2. My search so far has shown me that others are having similar issues but they are saying that the ota update is messing up certain things with their rooted phones (haven't found the answers I'm searching for either). Should I wait on updating? If so, how do I get the ota to stop wanting me to update my phone?
Thank you for any help you can provide.
Click to expand...
Click to collapse
Since your life is too busy and you don't want to mess with your phone anymore, your best bet is go back to stock 4.3 which is very good by the way, very stable, smooth and bug free. After so many complaints from my wife I rolled it back to stock 4.3 and she's so happy now.
1. Flash stock MF1 here http://www.androidfilehost.com/?fid=23134718111254196 , just unzip the flash with Odin
2. Your phone should take the 4.3 OTA update and you're home free.
buhohitr said:
Since your life is too busy and you don't want to mess with your phone anymore, your best bet is go back to stock 4.3 which is very good by the way, very stable, smooth and bug free. After so many complaints from my wife I rolled it back to stock 4.3 and she's so happy now.
1. Flash stock MF1 here http://www.androidfilehost.com/?fid=23134718111254196 , just unzip the flash with Odin
2. Your phone should take the 4.3 OTA update and you're home free.
Click to expand...
Click to collapse
Thanks so much, but now that I've put a little more research into this update I'm seeing that others are having issues with tethering and that would be a serious issue for me.
Also I used twrp to root my phone and did not use odin so I don't know how to flash with odin (or even have the files on my computer) is there a way to us twrp?
It looks like I will need to put a little more time into this than I wanted. Anyway, thanks for the help.
Sithlyone said:
Thanks so much, but now that I've put a little more research into this update I'm seeing that others are having issues with tethering and that would be a serious issue for me.
Also I used twrp to root my phone and did not use odin so I don't know how to flash with odin (or even have the files on my computer) is there a way to us twrp?
It looks like I will need to put a little more time into this than I wanted. Anyway, thanks for the help.
Click to expand...
Click to collapse
No issue with tethering for me, just root then install wifi tether router.
I swear I've read somewhere that to get the full effects of NE5, one needs to update the bootloader. Just rom/kernel/modem not enough. I've been on RODT ND2 for a while but have decided to move to something a little more recent. Is there a way to update the bootloader without utilizing a full-unmodded OTA style .tar?
AestenD said:
I swear I've read somewhere that to get the full effects of NE5, one needs to update the bootloader. Just rom/kernel/modem not enough. I've been on RODT ND2 for a while but have decided to move to something a little more recent. Is there a way to update the bootloader without utilizing a full-unmodded OTA style .tar?
Click to expand...
Click to collapse
To be honest, I don't think there's a stand alone zip for the Bootloader all on its own. But being on the previous build of Android, why not just flash the NE5 tar and start out completely fresh?
Yes, seems like alot of work, but I personally do it once a month, at least. If not more.
For me, Continuously testing things left and right, sometimes restoring backup just doesn't water my mind as a fresh start.
So I'll just flash the stock tar. Fire up CF-root, flash recovery and go from there. May be your best bet. Specially coming from. ND2
Kinda what I figured, I just didn't want to have to download yet another large file. Thanks though.
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
The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
dlc2001 said:
The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
Click to expand...
Click to collapse
to get rid of the slowness of the phone i recommend going to a lolipop rom , LP has to be the quickest my phone has ran... ever.
-step 1 use rsd lite to flash [4.4.2] 183.46.10 fxz (make sure it ends with a 10 not a 14 or 15 or you wont be able to unlock bootloader)
http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
-step 2 root and unlock use TR.apk (root)and motopocalypse.apk (bootloader unlock)
http://forum.xda-developers.com/showthread.php?t=2783912
-step 3 use ADB fastboot to Flash custom recovery, i personally use twrp there are others you can use if you decide to do the research
http://www.droidrzr.com/index.php/topic/51883-recoverytwrp-2810-11-01-14/
-step 4 flash LP custom rom, i use blisspop, it seems to have the most updates at the moment . it has really impressed me
http://www.droidrzr.com/index.php/topic/60153-rom502lollipopmsm8960-kkbl-blisspop-official/
that rom comes with supersu built in so you will have root. if your reason for having root is to have exposed, it doesnt work on lolipop so stop at sstep 3 and either flash a KK custom rom or just flash supersu which will give you root on stock kitkat
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
dlc2001 said:
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
Click to expand...
Click to collapse
yes you can install it from playstore, but once your bootloader is unlocked you can always root by flashing in custom recovery. you dont need exploits anymore
All done, worked great!