I've rooted my GT 10.1 but I have two questions that I can't find the answer.
1. Has anyone discovered how to unroot back to stock?
2. If rooted, will I be able to get the OTA of touchwiz by checking for updates under settings?
PS I flashed the TouchWiz UX found in this forum. Got to say it is really nice and I can't wait to get the version from Sammy. I then restored a backup using Rom Manager and restored fine except when checking for software updates. It used to say no update available, but today it says failed to connect to servers. Anyone else getting this error?
I guess that is actually 3 questions.
Thanks
1. Unrooting is pretty simple. Just flash the 3.1 OTA in the dev forum, after doing a full wipe. If you feel the need to go back to full stock, you'll also want to nvflash back to the original retail recovery, which you undoubtedly saved when you first rooted.
2. No one knows yet, but rest assured, within a day (less probably) of the update being released, it'll be available here as a rooted flashable ROM. If you learn one thing from your time on XDA, it should be "never accept an OTA update." Let the devs pull it apart and repackage it in a nice root-safe download.
Undoubtedly! (I wish) I wasn't planning to root but while playing with Odin, I thought I was locked at the downloading screen while testing odin. (Didn't hold down the power button long enough to shut off tab) I thought my only solution was to continue and root. No problems rooting, it was easy. I just wanted to make sure I get the TouchWiz update. Now I learned my lesson I will never do an OTA update.
Glad you told me that, otherwise I probably would have screwed up my GT. I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
pmsrefugee said:
Glad you told me that, otherwise I probably would have screwed up my GT.
Click to expand...
Click to collapse
It's not so much that you'll screw up your device by accepting an OTA, but rather that you might lose root and/or your custom recovery (perhaps permanently). Nevertheless, there are some cases of OTAs screwing up devices when accepted over non-stock installs, so IMHO its always best to wait for a flashable ROM.
pmsrefugee said:
I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
Click to expand...
Click to collapse
Yes, I believe the stock retail recovery is posted in the CWM recovery download package here: http://forum.xda-developers.com/showthread.php?t=1130574. You'll note that Step 3 is where you were advised to backup your original stock recovery, although the step is (correctly) noted as optional. No big deal, in any event. Glad I could help.
Hi, I just got a hand me down samsung fascinate to replace my barely functioning OG Droid. I rooted it and installed rom manager and it kept failing the custom rom installation or any installation of anything from recovery manager. It kept saying the signature verification failed if I remember the error code correctly. That was with the 3e recovery software. I read a few posts that said the older 2e version would work better with rom manager.
So I used odin and reverted to an older software revision, 2.1-update1. That successfully shows 2e as the recovery manager version. But now the market doesn't show rom manager(free) as an install option, premium shows up though. If I use the web browser to look at the market and look for it it shows up but it shows four devices, my old droid, a nook I rooted and converted for a friend, and then two devices that just show a question mark and doesn't allow them to be selected for installation. I thought thats ok I'll just download it from clockwork mods website and install it manually. I downloaded it but astro opens it and shows no info, details tab says it cannot open RomManager.apk as APK file. If I open it with file manager it says it cannot parse package. I tried downloading it on my computer and transferring it to my phone and it still says the same thing.
So I'm really confused as to what is going on. I do have install non market stuff checked.
I was hoping someone could give me some advice. I want to install miui as that was what I ran on my droid and liked it. Want to see how it runs on a faster phone.
Thanks in advance hopefully I provided enough information and didn't miss something simple.
When you were on Froyo, did you install the modified 3e Recovery needed for CWM to stick? I'm sure this is your problem if you didnt take this step.
Here is a link to the thread with everything you will need. If you have additional problems, dont hesitate to ask!
Hope this helps!
BTW: 1. Dont worry about this being for the infuse. It will work fine & 2. These types of threads should go in the Q&A section, for future reference
Rom manager is pointless unless you run cm7 nightlies. Get the recovery fixed for cm7 (first post of jt's cm7 thread in development) put miui rom on sd. Pull batt, flash fixed cm7 recovery in odin, insert battery (don't boot), 3 finger to recovery and flash miui. Profit.
good day.
First thank you for the replies very appreciated.
Tone_Capone I was going to try your method first. You are correct when I was on the updated firmware I did not flash the "fixed" 3e recovery did not realize there was one. My question now is I'm currently at 2e recovery, on the older firmware. Can I still follow those directions and put the modified 3e recovery onto the phone how it is. Or does the modified file count on other files being in place that I don't have since I'm downgraded? Do I need to update it again? I hate to ask but I just want to make sure.
chopper the dog Sorry about wrong section, thought q and a would be for commonly asked questions and the answers for them. I was gonna try this method then but I'm not sure if I choose bootloader in odin or pda like I did when downgrading the firmware.
joebells said:
First thank you for the replies very appreciated.
Tone_Capone I was going to try your method first. You are correct when I was on the updated firmware I did not flash the "fixed" 3e recovery did not realize there was one. My question now is I'm currently at 2e recovery, on the older firmware. Can I still follow those directions and put the modified 3e recovery onto the phone how it is. Or does the modified file count on other files being in place that I don't have since I'm downgraded? Do I need to update it again? I hate to ask but I just want to make sure.
chopper the dog Sorry about wrong section, thought q and a would be for commonly asked questions and the answers for them. I was gonna try this method then but I'm not sure if I choose bootloader in odin or pda like I did when downgrading the firmware.
Click to expand...
Click to collapse
refer to section 3...just replace ics rom with miui... although honestly I would go with ics 4.0
http://forum.xda-developers.com/showthread.php?t=1238070
thanks everyone, droidstyle I followed your links directions and miui is up and running. Very appreciated. I considered ics but I'll wait a while.
joebells said:
First thank you for the replies very appreciated.
Tone_Capone I was going to try your method first. You are correct when I was on the updated firmware I did not flash the "fixed" 3e recovery did not realize there was one. My question now is I'm currently at 2e recovery, on the older firmware. Can I still follow those directions and put the modified 3e recovery onto the phone how it is. Or does the modified file count on other files being in place that I don't have since I'm downgraded? Do I need to update it again? I hate to ask but I just want to make sure.
chopper the dog Sorry about wrong section, thought q and a would be for commonly asked questions and the answers for them. I was gonna try this method then but I'm not sure if I choose bootloader in odin or pda like I did when downgrading the firmware.
Click to expand...
Click to collapse
Glad we got it figured out.
Just for future reference, It is customary of this forum that if someone were to find a post helpful, go ahead and hit the thanks button on their post. Some guys take this very seriously.
Hello,
I am getting a bit confused with all the threads and I really don't want to mess up my phone. I have rooted it and my background is the Xperia X10, on Rogers too. I would like to test out some different ROMs or maybe even the ICS Rom that just came out from the EternityProject team. However, if I understood, there is no way to revert back to stock since we have a locked bootloader. Can anyone could just guide me to threads step by step? I read the tutorial to flash the Arctic Rom, but I am not sure what to do. Is the bootstrap recovery this? If so I guess I can go from there... I was a bit scared since it was saying unofficial. Would it work for Rogers Canada? Most of the things I see are for US or Europe.. Please help me out, would be much appreciated!
I just reread the bootstrap thread.. Having a question regarding this. There is a note stating that you can only access it through Android.. I am guessing I need to reinstall the bootstrap everytime I flash a ROM.. right? Sorry, pretty lost. Thanks for any help! I just feel like it was wayyy easier with my X10..
I came from the X10 on rogers too!, I seems the X10 was way easier to understand and mod. I am so lost with all this motorola stuff too!
Advise
Hey there guys, well I would advise not to flash anything unless you have at least a ClockWork backup of your phone after you rooted and installed the bootstrap recovery. The bootstrap recovery is an .apk file which you install and run from the phone itself not in recovery mode like most other unlocked bootloaders.
I'm holding off myself because there is no full flash file from Rogers as of yet, the closest one is the Brazil Xt910 flash using RDSlite. Still if you flash that if something goes wrong with your tweaking you won't get the CSC files from the Rogers Rom unless I guess you back them up. I'm not quite sure if you can actually pull the csc files from the rogers and port it over but it's worth a try if your daring.
At the moment I'm content with root and backing up the system folders and other partitions just in case something goes wrong, remember to backup your efs as well.
Thx for ur input gdmuscle, makes more sense now. I might risk it once there is a stable Ice Cream Sandwich ROM. I admit for now it is kind of useless to risk that much with the lack of ROM choices. Much appreciated!
And Chriskwan, yea, was much easier with the X10 lol. Good to see some canadians feeling the same way! Btw I am in contact with Moto to see when the update should arrive at Rogers.. Will make a thread if i get an update
After playing around with a Rogers Droid Razr the past 3-4 days trying to figure out ROMs and such, I can safely say I will never actually BUY this device.
There is WAY more community support for the Galaxy S2, and it is a lot easier to manage. Flashing via odin, is MUCH simpler. The stupid fastboot crap is annoying.
well for the razr its much easier than using odin i can assure u that...
1. get the root package and root your phone ... its a simple script u run and it does the rest...
2. get bootstrap.apk and cwm-on-boot.zip ... put the cwm zip in the root of your sd card (external sd)... install the bootstrap ... reboot into your recovery using the app... and then install the cwm on boot zip...
3. make nandroid backup (mad slow)
4. get the deodexed rom needed for arctic... wipe, install that
5. install Arctic...
thats the condensed guide ofcourse... just a few setup steps u need to follow...
As opposed to what? Running SuperOneClick? Because that is all I did and it worked perfectly for my Galaxy S Captivate.
I should mention that just gives me root, but from there installing CWM was relatively easy, and there is nothing more complicated.
The Razr is a great device, but it is to me a PITA compared to the Galaxy S series in terms of Android Development.
gdmuscle said:
Hey there guys, well I would advise not to flash anything unless you have at least a ClockWork backup of your phone after you rooted and installed the bootstrap recovery. The bootstrap recovery is an .apk file which you install and run from the phone itself not in recovery mode like most other unlocked bootloaders.
I'm holding off myself because there is no full flash file from Rogers as of yet, the closest one is the Brazil Xt910 flash using RDSlite. Still if you flash that if something goes wrong with your tweaking you won't get the CSC files from the Rogers Rom unless I guess you back them up. I'm not quite sure if you can actually pull the csc files from the rogers and port it over but it's worth a try if your daring.
At the moment I'm content with root and backing up the system folders and other partitions just in case something goes wrong, remember to backup your efs as well.
Click to expand...
Click to collapse
I wish i read that before i started to mess with my phone. I used a tutorial to try to add a custom rom to my phone and read people with rogers with success but i guess i was one of those who messed up. Now my phone just turns on and stays at the motorola screen
can either of you post the backup file of your rogers ROM
Yes that would be very useful to try
where is the efs folder?
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
upndwn4par said:
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
Click to expand...
Click to collapse
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
I just sold mine but will look in PC history. My matrix was stock 4.5.145 and I rooted it. I remember failing a few methods till I found one that worked. If I figure out what I did I will post it for you. If not fruitcake is best way
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
upndwn4par said:
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
Understood, thanks for the explanation.
UnlockRoot couldnt gain root access
I will attempt your suggestions Thanks very much for the guidance, its invaluable
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
KetoSoi said:
Unless some one figures out what motorola/att did with 145 to completely screw root ...
Click to expand...
Click to collapse
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
upndwn4par said:
Let me know how things go with the above before you even consider this.
Click to expand...
Click to collapse
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
ravilov said:
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
Click to expand...
Click to collapse
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
KetoSoi said:
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
Click to expand...
Click to collapse
Wow, that's just bizarre. Not sure what to think here.
I meant something like
Code:
moto-fastboot erase preinstall
KetoSoi said:
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
Click to expand...
Click to collapse
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
upndwn4par said:
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
Click to expand...
Click to collapse
Very odd some cannot root. I was on permalocked bootloader and still rooted after soak
Its sad, because the 145 update seemed like it made the phone a little snappier, and the screen was a pinch smoother.
What do you guys think about applying the CWM Zip for update 4.5.145 in my situation? Would that be safer?
Uh oh.... you guys ran away! LOL
I was able to flash the 145 update via CWM from NYG-SBXLII's handy zip file
No real problems, 145 running fine WITH root intact. Awesome
Had to blow away the recovery-from-boot.p file afterwards, and re-flash CWM Recovery, but it was all good.
Updated SU and bin's, good to go.
affiatic said:
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
Click to expand...
Click to collapse
This worked for me too with 4.5.145, followed it exactly and had no problems. Thanks!
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
How did you unlock the bootloader for firmware 4.5.145? I've been looking everywhere on how to do it safely!
upndwn4par said:
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
hello, ive been using 4.5.145 and was unable to root it, the problem with mine is that when I try to use the preinstall method it chokes when i type the "cp /preinstall/su /system/bin/... there was a message cp write error: no space left on device.. I have tried everything (almost) to root it but was unlucky.. then i saw this thread http://forum.xda-developers.com/showthread.php?t=2153422 ... i wanna try your suggestion but cant find the zip file in suggestion 1 and the 141 fruitcake you made on suggestion 2 and cant find file on option 3.. please do help me.. I have unlocked bootloader and have rom racers cwm.. thank you and more power..
Hello everyone!
I've been very happy with my rooted M9 for the last few months but now a system update message on my screen and I'm trying to figure out what to do about. I seem to recall when I rooted my phone that there could be complications if I install a system update on a rooted phone (like making a Nandroid Backup) but I'm finding scarce information on the topic. Does anyone here have some advice about this?
Rom...
http://forum.xda-developers.com/showthread.php?t=3083799
Firmware...
http://forum.xda-developers.com/showthread.php?t=3073355
Follow the second link above.
You will need to restore the factory system.img using TWRP (exFAT or NTFS for external USB as file is > 4GB).
This puts the modified system (root) back to stock so the update will run successfully.
Flash the original recovery for you system version too.
Then you can accept the OTA and then root the phone again.
Thanks for the responses! I'm still uncertain about a few things so tell me if I have this right.
First I need to restore the factory image. Is that a guy named OJM is talking about on this thread? (http://forum.xda-developers.com/sprint-one-m9/general/rooting-guide-t3073004)
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
Click to expand...
Click to collapse
In that case, what is a system.emmc.win?
Then I flash the original recovery...what are you refering to when you say "original recovery"?
After that my phone should be locked again and I can go to that second link, download the latest firmware and flash it. And then I can unlock and root my phone again.
Edit: So it looks like someone has made a guide on how to get the OTA updates (if you use the right words in your search). It looks no one done anything with it since May so maybe it still works? http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Sim-X said:
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Click to expand...
Click to collapse
That was what I ended up doing. Had few bumps on the way but I managed to get everything working. Thanks for the help everyone!
RUU
Sim-X said:
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Click to expand...
Click to collapse
hi sim I have a question the only thing I got to make sure is that the phone is S-OFF and nothing will happen because I read that also the bootlooder had to be lock again so I'm not sure