Database Users

Don’t try OTA 4.5.141 with a rooted phone

I was getting "Failed to boot 2 starting RSD mode" error and when my Atrix tried to reboot to install the OTA update. The only way I could get to boot again was to remove the battery and put it back, and after that, it boots normally to the home screen, and after the SD card gets mounted it shuts down to try to install the OTA update and you get the same error again.
I got it working again by following the suggestions from Atrixforums.com. What I did was to flash my phone with RDS lite v5.6 using the file 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011 and that fixed my phone and it’s been working normally.
If you can get your phone to the home screen without rebooting or you get a different type of error, you could try the Automated Update (PC Users Only) from Motorola website (I need confirmation if this would work with a unlocked bootloader)
Details:
My phone was using the stock rom version 2.3.4
Rooted (I did not remove the root access before applying OTA 4.5.141 and this is reason why I got in this problem)
Locked bootloader (I am not sure if this would work with unlocked bootloader)
Unlocked sim card
I hope it helps,

Already posted in Dev section:
Warning 1
Warning 2
Search before posting :>

Alaq said:
Already posted in Dev section:
Warning 1
Warning 2
Search before posting :>
Click to expand...
Click to collapse
Those threads reference problems with unlocked phones. The OP has a rooted phone that is not unlocked. So, not a dupe per se.
That said, I upgraded my rooted-only phone with no issues. I rather suspect the OP may have unlocked his bootloader and forgotten about it.

You can OTA 141 with a locked and rooted phone. Just be sure to unroot (you need to do this manually if you ever used the fastboot preinstall method) and make sure everything is back to stock. If you used oneclick or any other root method that has an unroot, manually verify it really removed everything (su, superuser.apk, etc).

gnahc79 said:
You can OTA 141 with a locked and rooted phone. Just be sure to unroot (you need to do this manually if you ever used the fastboot preinstall method) and make sure everything is back to stock. If you used oneclick or any other root method that has an unroot, manually verify it really removed everything (su, superuser.apk, etc).
Click to expand...
Click to collapse
I have used the one click easy method only and nothing else. And I agree with you, it seems that not unrooting your phone before the OTA update creates this problem. I’ll be more careful the next time when the ICS it’s available.
I just want people like me that it’s not been in the android scene for long, do not get in to this kind of problems.
It would probably be a good idea to post a check list every time a new update comes up, reminding us of the precautions that we must have. Because even if you know what you are doing If you forget just one little change you made it could lead to some problems.
Greetings,

btw, here is what I did to unroot prior to the 141 update. I rooted 2.3.4 with the fastboot preinstall method...no idea if this unroot method cleans up the one click method.
link
1. Open Android Terminal Emulator
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
Click to expand...
Click to collapse

I am was also facing the same issue with OTA. I finally managed to update my rooted, locked phone via USB method using Motorola Software Updater.
Root is lost after the update.

I did the OTA on my atrix which was locked and rooted. Updated fine without any problems, but I did lose root. Can't figure out which method is safe to use to re-root.

http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
k00ey said:
I did the OTA on my atrix which was locked and rooted. Updated fine without any problems, but I did lose root. Can't figure out which method is safe to use to re-root.
Click to expand...
Click to collapse

live4nyy said:
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Click to expand...
Click to collapse
I used this method and it worked fine. It did give an error message that superuser was already installed but it rooted the phone anyway.
Sent from my MB860 using Tapatalk

live4nyy said:
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Click to expand...
Click to collapse
Thank you! Worked great.

charlyee said:
I used this method and it worked fine. It did give an error message that superuser was already installed but it rooted the phone
Click to expand...
Click to collapse
Charlyee, did you unroot your 4G with the preinstall method prior to following these instructions? Please confirm. Thanks!

badnokia said:
Charlyee, did you unroot your 4G with the preinstall method prior to following these instructions? Please confirm. Thanks!
Click to expand...
Click to collapse
I did the root saver method but I had all kinds of problems doing the OTA, so I ended up by downloading the software from the Moto website via USB.
At that point my Atrix was unrooted, but I don't know if it was the root saver method or download of the software.
I tried Motofail to root as well but that didn't work.
Hope that helps.
Sorry, didn't mean to write a thesis in answer to a simple question.
Sent from my MB860 using Tapatalk

Is it safe to use the aRoot unroot method if my Atrix is rooted and unlocked in order to update to 4.5.191?

Confirmed Success: Unroot, OTA Update, Root
Sorry if this info is redundant, but I'm super paranoid about the OTA updates & wanted to confirm what I did worked for my rooted, but locked Atrix 4G:
1) Unrooted with the directions on this page: http://www.atrixforums.com/forum/mo...ons-including-stock-locked-2-3-4-2-3-6-a.html
2) Ran OTA update
3) Rooted again with the following instructions: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/

I just did sucessful update on my unlocked and rooted Motorola Atrix 4G (MB860) from 2.3.4 to 2.3.6 via RSDLite 5.6, and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf SBF file.
Windows 7 64-bit Ultimate. Everything passes O.K.

I had this happen on my atrix rooted no unlocked bootloader I reflashed with the above method nd success. I unrooted my wife's atrix first and installed the ota with no problems. So unroooting first seemed to work.
Sent from my MB860 using XDA App

I did not have a problem at all updating to 4.5.141 with a rooted phone minus the fact I lost root until I saw the link live4nyy posted.

Just an FYI for others like me that have been waiting to pull the trigger on the update.
I was rooted with the /preinstall (briefmobile) method (had never unlocked the bootloader). I read conflicting reports on whether OTA would work, and for some reason I couldn't get the Motoroloa update program to see my phone. Rather than figuring out why it wasn't seeing my phone, I did the "unroot" steps listed by gnahc79 in this thread and then let the phone update OTA and then rooted again using the /preinstall method.
The whole process took about 30 minutes, most of that was the OTA download and install.

Did you guys have to re-hack mobile hotspot after the OTA update?
Sent from my Motorola 2-way pager

[Q] Will rooted device get future update from Google?

Hi all,
Just got a Nexus 7. Say if I root my device with the Toolkit, will it be able to get future updates when Google releases them? And if it's posible, will a update from Google remove the root hack?

stan2 said:
Hi all,
Just got a Nexus 7. Say if I root my device with the Toolkit, will it be able to get future updates when Google releases them? And if it's posible, will a update from Google remove the root hack?
Click to expand...
Click to collapse
You'll always be able to update. It's more a matter of whether or not you'll need to undo some of the changes you made. Changes that cause OTA updates to fail include: custom kernels, modified system apks, etc. It really depends on what the OTA update is patching.
If the only change is adding root, you'll most likely be able to install OTA updates, but will need to re-flash supersu or fix the permissions on the su binary manually.
Sent from my Nexus 4

comminus said:
You'll always be able to update. It's more a matter of whether or not you'll need to undo some of the changes you made. Changes that cause OTA updates to fail include: custom kernels, modified system apks, etc. It really depends on what the OTA update is patching.
If the only change is adding root, you'll most likely be able to install OTA updates, but will need to re-flash supersu or fix the permissions on the su binary manually.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks for your reply.
So re-rooting is needed after an update? Sry, I'm still new with all the superuser lingos atm =D

stan2 said:
Thanks for your reply.
So re-rooting is needed after an update? Sry, I'm still new with all the superuser lingos atm =D
Click to expand...
Click to collapse
It's a bit of a misnomer that the device will need to be re-rooted. I say this because the su binary does not get removed, rather the owner and permissions for /system/bin and /system/xbin are set by OTA updates. This leads to a lot of talk about "losing root" after updating.
Technically all that needs to be done is to have the owner and permissions reset on the su binary. Most people find it easier to just re-install the SuperSU apk rather than modify the file permissions.
Pro-tip:
The ownership and permissions should be as follows:
owner: root, group: root (uid:0, gid:0)
permissions: 06755

YES. Mine was rooted on the first day I got it back in September and its been updated twice since then.
Sent from my Nexus 7 using xda app-developers app

You can always use OTA RootKeeper its the tool I always use when updating and has never failed
Sent from my SIII in a Galaxy Far Far Away

*GalaxyDev* said:
You can always use OTA RootKeeper its the tool I always use when updating and has never failed
Sent from my SIII in a Galaxy Far Far Away
Click to expand...
Click to collapse
Absolutely agree that OTA RootKeeper is a must have for OTA updating. Makes it totally painless to reestablish root.

Thanks everyone for replying, super useful! I got my device rooted =)

Rooted or not, if you delete any system apps you may have issues with getting updates.

[Q] How Do I Prevent OTA 4.3 Update

So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device

You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta

A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store

The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.

Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade

Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app

u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378

Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input

I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.

downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.

timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.

Error while trying to update to 4.4 (D800)

Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?

This is my problem too. Hopefully there is a way.
Sent from my LG-D800 using xda app-developers app

Maybe doing a factory reset from stock recovery?
Sent from my LG-D805 using xda app-developers app

rohan611 said:
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
Click to expand...
Click to collapse
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help

antawnm26 said:
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
Click to expand...
Click to collapse
nope. as i said in the OP< i have a stock recovery.

rohan611 said:
nope. as i said in the OP< i have a stock recovery.
Click to expand...
Click to collapse
then try root keeper it will disable root but back up root path and reinstate it once the update is done

antawnm26 said:
then try root keeper it will disable root but back up root path and reinstate it once the update is done
Click to expand...
Click to collapse
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.

rohan611 said:
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
Click to expand...
Click to collapse
lol..yeah i read each statement in your OP just wanted to get to that last part of you saying your going back to stock and going from there, because thats your next option....

Let us know if you went back to stock then did the update and it worked.

I've read that some people kept root through their OTA. Why are some people able to update and others aren't. I've been reading up on this for the VZW update whenever that happens. I hope I haven't kept all this bloatware on my phone for no reason!!
Sent from my VS980 4G using Tapatalk

hinduboy74 said:
Let us know if you went back to stock then did the update and it worked.
Click to expand...
Click to collapse
I reverted back to stock using the instructions in the Stickied post. I was then able to update to D80010o. I had to call to request a rep to push out the D80010q update again though. They're calling it a "security update" so you should use that phrase when talking to the rep so that they don't get confused and think that you're just requesting that they push out the KitKat update.
Once I got the D80010q update, the KitKat update was available and I was able to update. Unfortunately, I didn't try to root it prior to updating - though to be honest, I don't really feel the need to root anymore. Only reason I had it rooted before was to get the multitasking button, but I'm okay with using an S3 layout (Menu, Home, Back) since that's the phone I'm coming from.

I have posted this in Other thread too.. may be this helps (Or save some time)
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.

streetsmart999 said:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o

rohan611 said:
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
Click to expand...
Click to collapse
That is correct. I was on D80010o all four times I updated to Kit-kat and kept root everytime.

streetsmart999 said:
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
Same thing happened to me. I followed your advice in the other thread and did a reset using the LG flash tool, following rootjunky's guide on youtube and using the files from his website. Everything went smoothly except for at the end I got the same check flag error thing, but it completed the reset perfectly.
I then chatted with ATT and had him push the update to my phone which brought me up to d80010o. It finally went through the update and didn't get me the root error. So I think I'm in the green now. He said that he didn't have an option to push the kit kat update to my phone but it told him to have me do it through the software update in the settings. Which I tried and it said it was up to date. But he said that since they roll out in batches my phone might just not be ready for it yet. I will keep trying though and I'm one step further than I was before. At least it let me update. Shout out to ATT though, chat service is on point.

Easy 2 click root: How I got to 4.2.2 Camera Update/Rooted and WP permanently Off

Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.

It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk

Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.

So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app

No nothing roots 4.4 at this point.

vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.

akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.

mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???

-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck

mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.

-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it

mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh: