Database Users

[Q] Factory Reset After Root? Will mods prevent OTAs?

So I originally rooted using SuperOneClick, then I got an OTA that broke root. I then found gingerbreak and rooted using that method. I have done a few cool things, like change the boot animation and lock/unlock sounds, enabled sideloading, etc.
Anyway...
With rumors and speculation about Gingerbread coming out in the coming months (hopefully), I am wondering if the boot animations, lock sounds, and/or SuperUser access will deny the OTA from installing. Is it a good idea to return the ROM to stock to avoid any bugs?
Second,
Specifically on the Atrix, if I performed a factory reset, I assume I won't lose root access, but would I lose the boot animations, and lock/unlock sounds? Let's say I wanted to return it to a 100% stock ROM (un-root, stock boot animation, EVERYTHING) before the 2.3 update comes, how would I do it? I feel as though if I perform an OTA with the mods I've done to it, some unknown bugs/issues would appear (I've seen PLENTY of bugs as is). Can anyone shed some light on this? Call me paranoid, but I've seen too many software issues with this phone, and I'm hoping 2.3 will address them, and I hope I don't introduce any new bugs by updating a modded phone.

You should definitely go back to stock. I doubt that you'll even be prompted if you're rooted, so you won't get the update to Gingerbread. Instructions to return to stock can be found on Motorola's website, by Googling, or from Android Central.

If I do a hard reset using Android Recovery, will that effectively unroot and restore EVERYTHING to the factory image? I know if I do a soft reset through the OS, I will still have root access. I realize I can just unroot using SOC, but there have been issues where busybox is still installed along with the superuser icon, even though the phone doesn't have root access. I just want a clean slate.

rytymu said:
If I do a hard reset using Android Recovery, will that effectively unroot and restore EVERYTHING to the factory image? I know if I do a soft reset through the OS, I will still have root access. I realize I can just unroot using SOC, but there have been issues where busybox is still installed along with the superuser icon, even though the phone doesn't have root access. I just want a clean slate.
Click to expand...
Click to collapse
Try this.
Motorola

brewstermax said:
Try this.
Motorola
Click to expand...
Click to collapse
I have 4.1.83, and this will not work for it.

I would be interested in learning more about this too
Sent from my MB860 using XDA Premium App

This is a thread I commented on over at the Motorola forums. I actually got the forum manager to comment on the issue:
"rytymu
What do I do if I'm on 4.1.83 and want to return to stock (rooted)? The software given just says my device is up to date...
Mark (Forums Manager)
With next update/upgrade you will go up to next stock version. You have to
wait til then.
rytymu
So if I understand right:
I most likely will not get an OTA notification because of the root access, so when I run the Motorola Software Update program after the next update comes out, it will then flash a 100% stock image as if I just pulled it out of the box? This includes removing/wiping busybox, root access, boot animations, and EVERYTHING else?
Mark (Forums Manager)
If you are on 4.1.83 but modded you will get ota notification but will
likely fail on install. If MSU is made available you can update /upgrade to
that version. Root and other sideloaded things will be removed. Stock ATRIX
Att software. Not AOSP Android."
I guess this is what I'm looking for, unless someone interprets otherwise...

brewstermax said:
You should definitely go back to stock. I doubt that you'll even be prompted if you're rooted, so you won't get the update to Gingerbread. Instructions to return to stock can be found on Motorola's website, by Googling, or from Android Central.
Click to expand...
Click to collapse
OTA update should be fine if you have not deleted any of the original Moto files/bloatware, or leave any of the original Moto bloatware frozen. The updates only throw up at you when there are missing or frozen Moto apps and/or files.
If you are on 4.1.83, (or any firmware), and rooted only, you will get the update fine, but will lose root.
If you have flashed for example GladiAtrix, you will more than likely have to flash back to stock first.
If you have rooted on any version and then frozen any apps, thaw those apps and you will update fine, but again lose root.
Every time you update you lose root.

So I have frozen all bloat, but I did uninstall swype and reinstall a newer version. Is this going to be a problem for the next ota? Am I going to have to do a fresh sbf flash or is there a way to reinstall the stock version of swype? I'm not sure I still even have that file...
Sent from my MB860

beazie0885 said:
So I have frozen all bloat, but I did uninstall swype and reinstall a newer version. Is this going to be a problem for the next ota? Am I going to have to do a fresh sbf flash or is there a way to reinstall the stock version of swype? I'm not sure I still even have that file...
Sent from my MB860
Click to expand...
Click to collapse
If you installed a newer version of the same Swype, this should I imagine be the same as updating Swype. I'm thinking this would allow you to just unfreeze all the bloatware and update OTA. Only thing I can think of is that you try the OTA when it's available, and if it balks at you, flash back to stock.

I just followed another thread on XDA, and flashed to 1.26. After about 40 minutes, I had a fresh install. I then did a factory reset, as I was told that some user data and caches aren't touched by flashing (?). I did it just for good measure. I then went into the menu and updated to 4.1.57. I was tipped off (in an above post, actually) about some Motorola Softare Update program that will flash you from 4.1.57 to 4.1.83. The forum manager at Motorola instructed to do this to basiclly restore your phone if you had modified it (to clear the OTA check). Again, just for good measure, I used this to flash from 4.1.57 to 4.1.83 to be 100% sure I had a bone-stock phone.
Sent from my MB860 using XDA App

rytymu said:
I just followed another thread on XDA, and flashed to 1.26. After about 40 minutes, I had a fresh install. I then did a factory reset, as I was told that some user data and caches aren't touched by flashing (?). I did it just for good measure. I then went into the menu and updated to 4.1.57. Now, I'm actually in the "soak" beta feedback over at the motorola forums, and I was tipped off (in an above post, actually) about some Motorola Softare Update program that will flash you from 4.1.57 to 4.1.83. The forum manager instructed to do this to basiclly restore your phone if you had modified it (to clear the OTA check). Again, just for good measure, I used this to flash from 4.1.57 to 4.1.83 to be 100% sure I had a bone-stock phone.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
The Moto Software Update is not needed, and Mark, or whoever over on the Moto forums did not "tip" you off to this. This is no secret, and is well known. (BTW, you are breaking the NDA just by saying you are in beta, (soak feedback forums are down in any event as they are always taken down between betas), but that's another story, and being in beta doesn't make you more knowledgeable either).
You have made this sound more complex than it is.
To go back to stock (and the instructions are all over the forums BTW) --->
Flash 4.1.26, OTA to 4.1.57, OTA to 4.1.83!..............Done!
Or ------------>
Flash 4.1.57 sbf, OTA to 4.1.83!..................Done!
People who were having the OTA notification issues, (continually popping up), were those who flashed the 4.1.83 sbf which is floating around, and that's why they were told to flash 4.1.83 through the Moto Update portal.

(Edited above statement)
Sent from my MB860 using XDA App

Froyo updaters

These are questions for thoses that have used the official update from motorola.
1) Did you have to unroot before updating?
2) Did you have to wipe your phone before the update?
3) Was the update successful?
4) If it was successful, were you able to successfully root again? If so how?
5) If successfully rooted, were you then able to get rid of crapware from ATT?
6) Did you have any problems with the update detecting a non-oem battery? I bought my phone used off ebay so not sure if the battery is oem or not.
Thanks for your help. Im not ready to brick my phone, or not be able to charge my battery if the update doesnt work.

I was able to successfully update my wife's phone this weekend. Her's was not rooted before the update. I wanted to successfully root her's before I update mine. I was able to root her phone with SuperOneClick. After rooting I removed some of the preinstall AT&T stuff.
I'm planning on flashing mine back to stock before updating.

pre4speed said:
These are questions for thoses that have used the official update from motorola.
1) Did you have to unroot before updating?
2) Did you have to wipe your phone before the update?
3) Was the update successful?
4) If it was successful, were you able to successfully root again? If so how?
5) If successfully rooted, were you then able to get rid of crapware from ATT?
6) Did you have any problems with the update detecting a non-oem battery? I bought my phone used off ebay so not sure if the battery is oem or not.
Thanks for your help. Im not ready to brick my phone, or not be able to charge my battery if the update doesnt work.
Click to expand...
Click to collapse
1) No
2) No
3) Yes
4) Yes, superoneclick newest version
5) Yes
6) I use the original battery
Sent from my MB508 using Tapatalk

Upgraded, but...
I successfully updated to the motorola froyo official release. Im loving how much faster everything runs. Able to root successfully with superoneclick and used titanium backup to remove att crapware. However here is my issue. I used link2sd previously on eclair. Had about 50+ apps on phone with about 40% give or take free. So I was so excited about the apps to sd in froyo. Well, I tried putting back all my apps, using an app I got from market for apps2sd and link2sd for those unable to move per the app. With link2sd, I lost no phone space but as the apps that could be moved got moved to the sd via the market app, my phone space went BYE BYE. Down to 0% free. WTH is going on? I just did a factory reset and am going to try just link2sd and see what happens. Anyone else running into this problem or am I alone in this?

Ok, so
I used just link2sd and had no problems with memory. For some reason, using any app2sd app or the built in move to sd eats up my memory. Makes no sense to me at all, but I now have all my apps back, linked and at 40% free space. Strange.

This is why you should read....
Link2d... moves apk, davlik cache, and lib file...
App2d just moves the apk... so the cache and the library are still installed on /data/
Sent from my MB508 using Tapatalk
Edit: you can use titanium backup to take stuff off installed by apps2sd

New Problem
Im having a problem with the phone freezing up now. Only way to remedy is to remove battery. Anyone else?

Yup... though for me its not freezing... the screen shuts off... its still running though...
I could charge it... and somehow once either voice command or vlingo started up... and the white notification led that I didn't know the phone had was flashing
Sent from my MB508 using Tapatalk

pre4speed said:
Im having a problem with the phone freezing up now. Only way to remedy is to remove battery. Anyone else?
Click to expand...
Click to collapse
Yea i'm having the same issue. I used to have this same issue when I had the motorola backflip. It would always freeze up th first couple times after I flashed a new ROM. After a coulpe times of restarting and pulling the battery, eventually it just fixed itself...hopefully this is the case with this and its not a permanent problem

I have not seen any freezing issues with either of the 2 Flipsides that I have updated.

I hope so too, cuz having to pull the battery at least 5-8 times a day is really frigging annoying! At least it starts much faster than eclair did.

Hello!
I would like to ask for some help about updaters since I was reading some posts of the forum and the mixed results/reports may seems somewhat confuse, so , I would like to ask about help with info about these details in order to try to make an succesfull update froma Beta installed flipside phone without brick it.
1) Anyone of the succesfull updaters were made from a phone with BETA 2.2 installed?
2) In case that update was made from a BETA 2.2 phone, which was the way used to do the succesfull update
a-With Official 2.2 file and Moto windows software?
b-With Official 2.2 file and Linux flash-sbf software?
c-With Official 2.2 file and the in-phone menu option for update.
d-With Official 2.2 file in SD card RENAMED to the name: update.zip and using option in boot recovery menu?
3) Any Update to Official Froyo 2.2 from a BETA 2.2 installed phone was succesfull AFTER a downgrade to eclair 2.1 rom official rom file and WITHOUT BRICKING the phone in the process?
Thank You very much for kind help and best regards!

pre4speed said:
These are questions for thoses that have used the official update from motorola.
1) Did you have to unroot before updating?
2) Did you have to wipe your phone before the update?
3) Was the update successful?
4) If it was successful, were you able to successfully root again? If so how?
5) If successfully rooted, were you then able to get rid of crapware from ATT?
6) Did you have any problems with the update detecting a non-oem battery? I bought my phone used off ebay so not sure if the battery is oem or not.
Thanks for your help. Im not ready to brick my phone, or not be able to charge my battery if the update doesnt work.
Click to expand...
Click to collapse
1) I did not unroot my phone before doing the update. I had rooted using Sideloadwonder and z4Root.
2) I did not wipe data from my phone before doing the update. I did have everything backed up in Titanium backup.
3) Yes my update was successful.
4) I was able to root the update with Superoneclickv2.1.1
5) I have uninstalled most of the bloatware from ATT using Titanium backup.
6) I am running an OEM battery so I cannot answer this question.

Notified to update OTA to 4.2... from 4.2???

As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics

jjimenezjj said:
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
Click to expand...
Click to collapse
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.

phonic said:
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
Click to expand...
Click to collapse
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J

jjimenezjj said:
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
Click to expand...
Click to collapse
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!

phonic said:
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
Click to expand...
Click to collapse
It's not that bad. Everything works fine except for updating the thing. As for the restoring the original browser.apk, if you mean Chrome, I never touched it so it is there.
My guess is that I didn't install the CWM Recovery correctly because I can't boot into Recovery Mode. It just hangs and stays in a loop. I will re-install CWM and see if that helps.
John J

Re-installed CWM Recovery and flashed 4.2.1 from there. Lost everything but I had anything important backup already. All is good

[Q][Root/cwm lost?]

Hi guys,
Recently I updated my i9505 to official 4.3 version XXUEMJ7...then i rooted it successfully, flashed philz cwm, it worked...i did a backup, then flashed a mod (lightning effect on lockscreen), turned on the phone. Suddenly my wifi won't work so I decided to do a restore from the backup that i made 10 minutes before that. While it was restoring i noticed that i didnt had enough storage so it skipped few things. When it was successfully restored, I turned my phone on and here are the problems:
When it has booted up i recieved so many errors and fc's like procedure system has stopped, com.google.process.gapps error and so on...
I taught ok, lets delete some HD games to gain space and restore it again. But now there was no cwm or any recovery. I can't use Google Play and every app that uses Google files (youtube, gmail, stock internet browser and even facebook)
I'm not sure if I lost root and/or cwm. My question is how to get it back? What do i need to flash over Odin? Download mode works.
Sent from my GT-I9505 using xda app-developers app

Hello.
I have same problem. Nothing works. I think it's a protected bootloader that will rewrite every custom rom/recovery. I had rom for ~20 days, and was just doing my daily routine, rebooted and lost root and CWM. After this same symptoms occured.
I downloaded XXUEMJ7 prerooted now, and it was only rom that I could flash. Have no custom recovery by now and root works... But probably not for long. What's most important - wifi works. This is partial solution for using your phone while someone smarter will explain us what's going on.

socah said:
Hello.
I have same problem. Nothing works. I think it's a protected bootloader that will rewrite every custom rom/recovery. I had rom for ~20 days, and was just doing my daily routine, rebooted and lost root and CWM. After this same symptoms occured.
I downloaded XXUEMJ7 prerooted now, and it was only rom that I could flash. Have no custom recovery by now and root works... But probably not for long. What's most important - wifi works. This is partial solution for using your phone while someone smarter will explain us what's going on.
Click to expand...
Click to collapse
Thank you. I'll try that.
EDIT: can you give me a link, and you flashed it via Odin?

http://forum.xda-developers.com/showthread.php?t=2250824
In this thread, use "ctrl+f" and write "PDA: XXUEMJ7" There will be prerooted odin flashable link.
By the way, flashing this new knox bootloader with 4.3 was worst thing that I done do my phone. And I'm really pissed off on samsung. Hope some smart devs will solve this someday and we will be able to downgrade or bypass this.

Well, I still get those errors all the time... :crying:
I taught this would remove them, but unfotunately didn't..

Samsungi9OO said:
Well, I still get those errors all the time... :crying:
I taught this would remove them, but unfotunately didn't..
Click to expand...
Click to collapse
Try factory reset

socah said:
Try factory reset
Click to expand...
Click to collapse
Thank you

Can't Flash ROMs

Wugs tool never detects my Nexus 10, I tried everything (it did when I first rooted it). I'm on 4.2.2 but for some reason I can't update to the newer versions via OTA, it always fails. I'm rooted. I tried flashing a clean 4.2.2, which I got directly from Google, TWRP fails every time, even after a full wipe. I'm lost.
Does having the AOSP browser installed have anything to do with this? I mean having it installed so that even when I factory reset, it still there.

SRCP said:
Wugs tool never detects my Nexus 10, I tried everything (it did when I first rooted it). I'm on 4.2.2 but for some reason I can't update to the newer versions via OTA, it always fails. I'm rooted. I tried flashing a clean 4.2.2, which I got directly from Google, TWRP fails every time, even after a full wipe. I'm lost.
Does having the AOSP browser installed have anything to do with this? I mean having it installed so that even when I factory reset, it still there.
Click to expand...
Click to collapse
The browser has nothing to do with it, but I will suggest to skip the toolkit as too many people run into issues with these
http://forum.xda-developers.com/showthread.php?t=2670400
Have a look at this thread, 3rd post in particular, it will help you get back to stock and then if you wish root manually and flash any ROM from that point

demkantor said:
The browser has nothing to do with it, but I will suggest to skip the toolkit as too many people run into issues with these
http://forum.xda-developers.com/showthread.php?t=2670400
Have a look at this thread, 3rd post in particular, it will help you get back to stock and then if you wish root manually and flash any ROM from that point
Click to expand...
Click to collapse
Thanks, I'll try it today.