Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,732,170 Members 43,579 Now Online
XDA Developers Android and Mobile Development Forum

[HOW TO]Update from stock rooted MF9/MJA/MK2 to NAE (with root) without losing data

Tip us?
 
Ingenium13
Old
(Last edited by Ingenium13; 16th February 2014 at 03:09 AM.) Reason: update for NAE
#1  
Senior Member - OP
Thanks Meter 75
Posts: 179
Join Date: Dec 2006
Location: San Francisco, CA
Default [HOW TO]Update from stock rooted MF9/MJA/MK2 to NAE (with root) without losing data

Updated for NAE. When the NAE tar.md5 comes out you can just flash it directly rather than doing all this.

This will update everything (firmware, modem, bootloader, ROM, recovery, etc) to NAE. As long as you're coming from stock or mostly stock, this should work, and you will still have all your data and apps. It will also probably work coming from another MF9, MJA, or MK2 based ROM, but you may have problems (in which case you can just wipe data. The whole process should take less than 30 minutes, not counting the time it takes to download the stock tar.md5 image. I recommend starting it now (link in Step 2) so it will be ready when you need it. This will NOT work if you've already tried to take the NAE OTA and it failed because you weren't fully stock.

You will need odin. It can be downloaded from this thread. Alternatively, if you're using OS X or Linux, I found that Heimdall works very well in place of odin. There are a few extra steps involved though, but if you install Heimdall Frontend then you don't have to mess with the terminal.

Step 1: Backup your current ROM with TWRP, CWM, or Philz.

Step 2: Download the MK2 tar.md5 from sammobile. Sammobile is pretty slow to download, but I found a mirror and a second mirror. I also made a torrent that might be faster (please seed if you use it to speed it up for everyone). Flashing this with odin does NOT wipe data. You can verify it by opening it in an a program that supports tar and looking at the files within it; those are the partitions it overwrites. This will give you stock MK2 recovery, bootloader, modem, firmware, and software.

Step 3: Use odin to flash it over your current ROM. To do this, you need to first put the phone into download mode. Power it off completely, then press and hold volume down, home, and power. Then connect it to your computer.

In odin, I just left default odin settings checked. Make sure that you add the tar.md5 in the PDA slot and apply it. Reboot and verify that your data is all there. You can still easily revert to the backup you made in Step 1 if things aren't right.

Step 4: Put the MK2 to NAE OTA on your external sd card (not internal). You don't need to rename it.

Power the phone off completely. Then press and hold home, volume up, and power to get into stock recovery. Navigate to where you put the OTA zip on your external sd card and flash it. It will reboot a couple times during the update, including one time where it seems like it's booted up and done before it powers off again. You'll know it's done when you get a popup notification saying it completed successfully. All your data and apps should still be there.

Note: From this point on, performing any of these steps will set the Knox flag. So if you just purchased the phone (within your return window) or are having issues and may need a replacement, you may want hold off on root. Sprint may or may not check for this during a warranty replacement. Insurance replacements should be fine.

Step 5: Go back into download mode and flash CF Auto Root through odin. You should now have root, and knox will not complain. You'll need to re-download the SuperSU app from the Play Store though. Open the app and let it update the su binary to the newest version.

Step 6: Flash TWRP (or CWM or Philz) through odin (it didn't work for me with goo manager). Optionally reboot into recovery to make sure it actually stuck.
The Following 24 Users Say Thank You to Ingenium13 For This Useful Post: [ Click to Expand ]
 
random45
Old
#2  
Senior Member
Thanks Meter 120
Posts: 212
Join Date: Dec 2010
Quote:
Originally Posted by Ingenium13 View Post
As long as you're coming from stock or mostly stock, this should work, and you will still have all your data and apps. It will also probably work coming from another MF9 based ROM, but you may have problems (in which case you can just wipe data. See note at the end if you're using Titanium Backup). The whole process should take less than 30 minutes. It will NOT work if you've already tried to take the MJA OTA and it failed.

Step 1: Backup your current ROM with TWRP, CWM, or another recovery.

Step 2: Download the MF9 tar.md5 from sammobile (here is a fast mirror: http://goo.gl/gky86G, sourced from here). This one does NOT wipe data. You can verify it by opening it in an a program that supports tar and looking at the files within it; those are the partitions it overwrites.

Step 3: Use odin to flash it over your current MF9 ROM. Reboot and verify that your data is all there. You can still easily revert to the backup you made in Step 1 if things aren't right.

Step 4: Put the OTA on your external sd card (not internal). Power the phone off completely. Then press and hold home, volume up, and power to get into stock recovery. Navigate to where you put the OTA zip on your external sd card and flash it. It will reboot a couple times during the update, including one time where it seems like it's booted up and done before it powers off again. You'll know it's done when you get a popup notification saying it completed successfully. All your data and apps should still be there.

Step 5: Go back into download mode and flash CF Auto Root through odin. You should now have root, and knox will not complain. You'll need to re-download the SuperSU app from the Play Store though. Open the app and let it update the su binary to the newest version.

Step 6: Flash TWRP (or CWM) through odin (it didn't work for me with goo manager). Optionally reboot into recovery to make sure it actually stuck.

It seems that with all the issues with the new firmware, that it's actually worth the trouble to do it the "official" way to make sure it works, especially since it's trivial to get root back. Follow these steps and you should be fine.

NOTE: For those who want to wipe data anyway (or have to because they're having problems), Titanium Backup is currently not working properly with MJA. The workaround is to manually install your apps from the Play Store and then restore just the data from Titanium Backup. Restoring the apps themselves through Titanium Backup causes problems at the moment.

You WILL Knox Warranty Void with this method.
The Following 2 Users Say Thank You to random45 For This Useful Post: [ Click to Expand ]
 
guitardoc64
Old
#3  
guitardoc64's Avatar
Senior Member
Thanks Meter 338
Posts: 1,613
Join Date: Sep 2007
Location: Lake Charles,LA

 
DONATE TO ME
Is there a workaround for tripping Knox?
Current phone: Samsung Galaxy S4
Retired: EVO 3D, Hero,Vogue,Apache
ROM:Crawrj stock rooted MF9
Recovery:TWRP
 
Ingenium13
Old
(Last edited by Ingenium13; 3rd November 2013 at 05:34 AM.)
#4  
Senior Member - OP
Thanks Meter 75
Posts: 179
Join Date: Dec 2006
Location: San Francisco, CA
Not yet. A method will probably be developed, but it will involve flashing a custom kernel that doesn't require the new bootloader. The version of MJA would have to have this kernel included. The stock kernel seems to not boot without the new bootloader. You will have to keep using a custom kernel from that point onward.
 
aberchonbie
Old
#5  
Junior Member
Thanks Meter 1
Posts: 4
Join Date: Feb 2011
Location: Los Angeles
Quote:
Originally Posted by Ingenium13 View Post
Not yet. A method will probably be developed, but it will involve flashing a custom kernel that doesn't require the new bootloader. The version of MJA would have to have this kernel included. The stock kernel seems to not boot without the new bootloader. You will have to keep using a custom kernel from that point onward.
Sorry, where do I find the OTA MJA update?
The Following User Says Thank You to aberchonbie For This Useful Post: [ Click to Expand ]
 
M3wThr33
Old
(Last edited by M3wThr33; 5th November 2013 at 07:26 AM.)
#6  
Senior Member
Thanks Meter 48
Posts: 195
Join Date: Aug 2011
Location: Los Angeles, CA
For those of us new to Odin, can we get a screenshot of what should and shouldn't be checked?

Edit: Nothing NEEDS to be checked.
Checking Auto Reboot does just that, but doesn't seem to work for me.
Checking R.Flash Time resets a counter, not a big deal, either.

The rest uncheck.

Anyways, that all worked. I tried combining the Odin'ing of CF Root and recovery, until I saw that the CF-Auto-Root restores the old recovery as one of the steps...
 
Memphisjojo
Old
#7  
Junior Member
Thanks Meter 2
Posts: 14
Join Date: Oct 2007
with this method do we get the mja modem?

if the option available to go back to aosp 4.3 if we dont like it? 4.2 tw?
 
Bonefishbf3
Old
(Last edited by Bonefishbf3; 5th November 2013 at 11:35 PM.) Reason: Solved
#8  
Junior Member
Thanks Meter 0
Posts: 5
Join Date: Aug 2012
Quote:
Originally Posted by aberchonbie View Post
Sorry, where do I find the OTA MJA update?
To be more specific, where is the OTA downloaded to?
I would like help with the file location also. Thanks.
FOUND IT in the Cache folder. You must allow root permissions in your file explorer.
 
Bielinsk
Old
#9  
Senior Member
Thanks Meter 67
Posts: 1,001
Join Date: Dec 2009
Can I follow these steps if I have TWRP instead of stock recovery?

Also, what update for to apply?
 
SpringerRider
Old
(Last edited by SpringerRider; 6th November 2013 at 09:02 PM.)
#10  
SpringerRider's Avatar
Member
Thanks Meter 11
Posts: 73
Join Date: Jul 2012
Location: Sugar Hill

 
DONATE TO ME
After reading in this forum, non stop since Oct. 28, I took the plunge and did the dirty deed late last night with the downloadable OTA, after restoring to stock.
I woke up this morning and the Keebler elves hooked me up. I was fully rooted and all I had to do was reinstall Clockwork.
Mobile ODIN and SuperUser's Keep root are what's happening.
I have been looking for any glitches this morning but this thing runs perfect. I did see a security warning once that I assume is the Knox thingy I read so much about. Other than that, I'm gravy.
Now, can someone remind me why I upgraded?
I mean, what did I gain by leaping to 4.3? Is there something under the hood I ain't seeing?

The Following User Says Thank You to SpringerRider For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes