Database Users

Returned my phone to the Stock and it wont go back

I Had to take my phone back to sprint today for warrant repair so i ran the stock 1.56.651.2 RUU all was good. Got home and executed these commands
adb push asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
And it spit out
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/752/fd/3
SUCCESS: Enjoy the shell.
#
Then I TYPED
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin9:
cat sh > su10:
chmod 4755 su
exit
exit
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb shell reboot
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
It Returned to root # and then typed
reboot recovery
It did not boot into recovery any way i tried
So i went to execute the RUU 1.29.651.1 and now it gives me a error
Error[140] Bootloader version Error.
I checked my bootloader version in Hboot and it shows 1.41.00
Now im stumpped I cant get my root back and i cant flash a recovery ne ideas...........Please dont rip my ass for not searching i tried but nothing i saw pertained exactly to the cdma Hero.

once you run the 1.56 ruu you can't run the 1.29 ruu, as it overwrites the bootloader with a new updated one. bootloaders don't like to be downgraded. you are stuck with the 1.56 software. just run the 1.56 ruu again? why not?

Possibly a bad recovery flash. Try reflashing the image, maybe with the 1.6.2 RA Image.

thedudejdog said:
just run the 1.56 ruu again? why not?
Click to expand...
Click to collapse
I cant its says its already installed or something along those lines
Im trying to flash 1.6.2 as we speak ill let you know what happens

Ok now why did that just work???????

flipzmode said:
What else do I need to know?
The phone is still rootable. I tested it successfully using the auto-rooter in the pre-kitchen.
Fresh ROM still works just fine (as should any 1.56 based rom)
You will not be able to use the 1.29 RUU after this one, but I don't know of any reason that you would want to
Although some img's in the RUU have different dates than the original it appears that they are identical other than system.img
You don't need to run this unless you are trying to return your phone to stock. You won't get anything special from running it.
Download here: http://geekfor.me/news/sprint_ruu_156/
Click to expand...
Click to collapse
read the thread where you got that ruu here and let me know what you should do next

should i try to reflash 1.5.2 so i can regain a2sd capability

lostinroot:) said:
should i try to reflash 1.5.2 so i can regain a2sd capability
Click to expand...
Click to collapse
what? no. apps2sd is rom based it has nothing to do with recovery...

Sorry im still a bit on the newb side. J dog I didnt read far enough. That very well could of been a mistake that could of briked my phone. I i was doing something else.
You just taught me a major lesson. READ>READ>READ

But when you read the 1.6.2 forum it says in gigantic red letters This recovery is NOT yet fully compatible with the new apps2sd method!
Any i just realized jdog your not but 40 miles from me!!!!!

yep, well actually I'm a little north-east of kansas city, it's about 83 miles to topeka from here. (give or take)
read then read some more. then read more. anything you could possibly run into someone has done before.
you don't want to be in a hurry when you're flashing. also don't drink and flash. if you do make sure you have a designated nandroid-er.

when talking about not compatible with the new a2sd method, they mean the new version in cyanogen mods, of mounting the ext partition to /sd-ext as opposed to /system/sd, the only rom it could have any effect on here at the moment would be darchdroid, but I believe darch may have modded it in the port to keep it working on the hero's. The amon-ra recovery 1.7.0 supports cyan's new method, although I am not honestly sure if it supports the current method at the same time..
edit: basically, stick with 1.6.2 or godspeed recovery. try flashing again, I recommend the godspeed recovery as it runs faster (for me anyways), plus the thread will have instructions of how to flash.

thedudejdog said:
also don't drink and flash. if you do make sure you have a designated nandroid-er.
Click to expand...
Click to collapse
AINT THAT THE TRUTH. Aw....SH*T....I just blew pas a nand-check-point.
danaff37 said:
basically, stick with 1.6.2 or godspeed recovery. try flashing again, I recommend the godspeed recovery as it runs faster (for me anyways), plus the thread will have instructions of how to flash.
Click to expand...
Click to collapse
And that gos to show that i havent read enough!! I started flashing the RA1.2.3 and upgraded to the 1.5.2............Then it wasnt till last night i even knew about the 1.6.2.........................And now im about ready to hit the search button and type in "godspeed Rocovery"

EDIT: forgive me for I am stupid.......

regaw_leinad said:
EDIT: forgive me for I am stupid.......
Click to expand...
Click to collapse
Your Forgived> How are you stupid

[HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011

Stop, listen. Follow my directions, if you fail to follow directions I will no longer help you. Don't PM me and ask. If you screw up ask in the thread.
Rooted Users (Non - Root Users scroll down below):
MR1 RUU
http://www.multiupload.com/KU7GSF2EY0
PG05IMG_MR1_no_hboot.zip - c64b4367086fff4f51ec3d5d766a0456
Bootloader (FLASH THIS LAST) FLASHING THIS WITHOUT SUCESSFULLY FLASHING THE ABOVE FILE WILL CAUSE A SECURITY WARNING
http://www.multiupload.com/26WG1UZCXR
abda920f3e159fb05c00d8c54a5b8768 - PG05IMG_hboot_1.4.0000.zip
Flash the above PG05IMG_MR1_no_hboot.zip to restore everything to stock + OTA BUT still will have the s-off bootloader.
Rename PG05IMG_MR1_no_hboot.zip as PG05IMG.zip, and flash through hboot (like in the root guide).
To restore the bootloader, rename PG05IMG_hboot_1.4.0000.zip as PG05IMG.zip and flash through the bootloader. DO NOT FLASH THIS unless you are absolutely sure PG05IMG_MR1_no_hboot.zip flashed to your device, without issue.
Now you are done, enjoy. If you screwed up, and got a security warning contact me, don't stress. Then again, don't screw up.
Non root users wanting to return to 1.12.605.6 (Stock, pre OTA) can continue below:
NOT FOR ROOT USERS
Taken from AndroidPolice: [Tutorial] How To "Un-Root" The HTC ThunderBolt And Return It To Stock. Please check the site out.
One of the most popular questions about rooting the ThunderBolt is how to undo the process and return to stock, which renews your eligibility for customer support. Well, here you go:
Instructions:
Please read the whole tutorial first, and pay attention to every detail. Note that your battery needs to be charged to at least 40% at the beginning of the process, and remember to check the MD5 sums of all downloaded files before diving in. As always, neither Android Police nor Team AndIRC are responsible for any damage this may cause to your phone, and, needless to say, returning to stock means you will no longer be able to use root apps like ShootMe and Titanium Backup.
First, download the following files:
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img.
Code:
adb push misc.img /data/local/
adb push busybox /data/local/
adb shell chmod 777 /data/local/busybox
To gain root and flash misc.img:
Code:
adb shell
su
/data/local/busybox md5sum /data/local/misc.img
If the output is anything other than "c88dd947eb3b36eec90503a3525ae0de," stop and start over again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
Rename "PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_
release_174685_signed.zip" to "PG05IMG.zip" before placing it on your SD card.
Finally, reboot into bootloader mode by entering the following command. Allow the stock firmware to flash.
Code:
adb reboot bootloader
You’re done – your phone should now be stock, S-ON.

Bookmarking this, just in case. Thanks, Jcase!

Looks like I'll be going back to Froyo for now. I believe the Sense in GB leak is older than the stock on the device.. plus.. camera doesn't work, weather in clock widget doesn't work.. quadrant score is pretty low.. As for now.. I don't see any solid reason to upgrade to GB.. (though I wish I did).. sigh!

http://forum.xda-developers.com/showthread.php?t=1082114
Follow that to return to stock from gingerbread

I am getting No Image or Wrong Image Error In Final Step. I downloaded Stock Firmware Twice but same issue!

Can anyone help me out? I am not able to return to stock. I have BAMF remix 1.6.3 installed and trying to get back to stock as i have to send this device back to Verizon for replacement. I tried everything..file name is correct....md5 sum is correct however in final step when i tried to load the stock FW the boot-loader says wrong image!!
i downloaded stock FW from every possible source but no different!
Please Help!

If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?

spjoneser said:
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
Click to expand...
Click to collapse
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.

jcase said:
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
Click to expand...
Click to collapse
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?

spjoneser said:
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
Click to expand...
Click to collapse
Yes, because some radios seem to cause the files to flash in different orders, doing it like this keeps me from having to make multiple versions.
Sent from my LG Revolution

Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.

Androidfreakz said:
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Click to expand...
Click to collapse
You need to consult the author of the program, because I don't know what it did, I can't support their application.
Sent from my LG Revolution

This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?

AnalyzeFaith said:
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
Click to expand...
Click to collapse
Reverts everything back to stock + OTA

Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?

i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?

Droid_ALM2ND said:
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
Click to expand...
Click to collapse
yes
1234567890

droidrev71 said:
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Click to expand...
Click to collapse
Of course you lost root, this is for restoring to stock. It removes root.

jcase said:
Of course you lost root, this is for restoring to stock. It removes root.
Click to expand...
Click to collapse
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?

droidrev71 said:
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
Click to expand...
Click to collapse
if you are S-off, you can just flash the MR1 upgrade from the root guide, otherwise you have to do a complete re-root.

Root Obtained **EASY!**: T-Mobile G2 2.3.4 official OTA manual update

For those of you wondering why the S-OFF feature was worth your extra time to update, this is a prime example of why S-OFF kicks royal behind.
So here is the situation I was having. Friday morning, T-Mo showed me some love and sent me the Gingerbread update. I didn't have my morning coffee so I wasn't thinking strait and authorized the update. I forgot that it would probably interfere with good ol' ClockworkMod Recovery. Sure enough, it did. So, after the OTA failed due to the recovery, I haven't been able to get T-Mo to show me some OTA love again.
However, I had previously invoked the S-OFF feature when it was discovered how to.
After following the guide at http://forum.xda-developers.com/showthread.php?t=1202060 I found myself with a G2 using stock recovery and bone stock Gingerbread (S-OFF still invoked).
After some thought, I decided to do the following:
Flash ClockworkMod via the bootloader screen, and flash SU via the ClockworkMod screen.
Note: You can only do this if you have S-OFF! And since my guide writing skills are not so pristine, I'm assuming you have some sort of working adb/bootloader/recovery knowledge.
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.

Thanks!
It sounds like you started where I am: Clockwork Mod, S-OFF and stock Froyo 2.2.
Q. How did you follow the steps in the thread to get onto Gingerbread? Did you remove ClockworkMod? If yes, how did you revert to stock recovery? This is the step that I'm caught on, and can't find a thread regarding. Thanks!
Edit to add:
Did you unroot the phone using these steps?
If so, were you at all scared about the warning regarding PC10IMG.zip?

I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk

rdmerck said:
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Okay, so just to verify, you flashed CWM recovery while running the GB update? When you adb shell you open a # prompt? I've been gfree s-off'd since I got my phone so even with the leak or otherwise I've been able to just reflash the stock 1.19/1.22OTA and reroot it but I didn't think to try flashing cwm while it's stock gb'd....so tempted.

I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
So I sit down to write up a quick guide this morning and what do I find? Nicely done. Couple of points I wanted to add to why this works -
This method fixes the things that the OTA breaks for root: New stock hboot and stock recovery are flashed and on the rom side it wipes /system/xbin which breaks the su symlink.
Flashing the PC10IMG above fixes the recovery.
Flashing the superuser package reinstalls Superuser.apk, the su binary and fixes the symlink to xbin.
But, still not hboot-eng so your fastboot options are limited.
When I did this I had replaced the DZ engineering hboot.img in rmk's package with the G2 engineering hboot.img and edited android.txt for the new G2 build. This allows you to take care of both in once flash.
Hope this is useful to someone and thank you for saving me from writing a guide!
8/27/2011 Edit:
Realized ro.secure=0 so I repacked the stock boot.img from the 2.3.4 PC10IMG.zip with the below changes to default.prop. This allows use of the "adb remount" so files can be pushed to system folders without needing to go into terminal and mounting rw.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Modified installation instructions for full root:
Flash the PC10IMG.zip with the G2 engineering bootloader in this post
Flash the superuser update.zip in the OP
Extract the attached boot.img to the platform-tools directory
Remove the PC10IMG from your sdcard and reboot into bootloader
Select fastboot
Enter the following command in terminal or cmd:
Code:
fastboot flash boot boot.img
fastboot reboot
Kind Regards,
Kevin

zkid2010 said:
Okay, so just to verify, you flashed CWM recovery while running the GB update?
Click to expand...
Click to collapse
Yes. Just flash the PC10IMG and you have clockwork recovery again. However, you absolutely need SuperCID set while in froyo or this does not work.
Kind Regards,
Kevin

Confirm Here that it works...
Root and S-OFF
Gingerbread OTA 2.3.4
Thanks Guys for your help!

Flawless!
This worked flawlessly!!
I admire you so much for figuring this out!!
Thank you so much!

HELP!
sort of noobie here..
so i just updated my g2 to 2.3.4 following http://forum.xda-developers.com/showthread.php?t=1202060
and now i want to perm root my phone and overclock it but im having troubles.
1. how do i get clockworkmod installed? i know you can install this from rom manager but it requires root. right?
cause you said.. "Just flash the PC10IMG and you have clockwork recovery again"..
i tried flashing the PC10IMG.zip but got an error and says aborted.
any help please?
thanks in advance

If you are already on 2.3.4 and had not previously rooted then this thread will be of no use to you since your G2 does not have SuperCID (again, read the wiki.)
You will need to downgrade back to froyo (other threads on this and links in the wiki.) Once rooted, then install one of the rooted stock roms in this forum or follow this guide to reinstall the recovery and superuser (hboot optional.)
Hope that gets you going in the right direction.
Kind Regards,
Kevin
Sent from my T-Mobile G2 using Tapatalk

G2 Problems??
Hi, how can i get S-OFF on my g2 since it seems i can not generate a beta key from the revolutionary website cause g2 it's not in the drop down list, don't know what to pick and i want to be able to have my g2 rooted with android 2.3.. can somebody help me please?
Thanks.

Revolutionary is not available for the Desire Z/G2. Have you flashed the leaked 2.3.3 and trying to root? PM please.

Hey I notice most of the people in this thread are Americans - would this method work for the DZ or is it just for the G2?
Sorry if this is a noobish question.

Not a noob question, this one is new for me too. Fundementals are the same, process would be the same. I don't know if there is any issue using a PC10IMG with the info for a G2 (contained in the file called android-info) so may need rebuild one modified with DZ information.
Proceed with caution and do not do anything you are not 100% sure about.
Sent from my T-Mobile G2 using Tapatalk

I'll hold off on confirming the update in that case! I'm still on stock firmware, didn't apply the update from March either. When I've read enough to be confident on how to perma-root the current firmware I might risk following the method in this thread. Then I'll post back to let you know if it works on the DZ.

My DZ came with 1.34 firmware, I rooted it on this firmware. I accidentally upgraded it and am now on the OTA gingerbread ROM. Is this method suitable in this situation or do I require to flash a rooted stock ROM for this method to work.

Accidentally manually applied the OTA? Should work, you have a G2 now!
Sent from my HTC ThunderBolt using Tapatalk

Is there any newbie guide for how to do this? From getting Clockwork on there to getting this rooted 2.3.4 on. I have a rooted 2.2 with S-OFF right now, stock. Just don't really know what to do from this point on.

How to is in the OTA thread (which needs a helping of Iron Fist.) Come back here when ready to re-root.
Sent from my T-Mobile G2 using Tapatalk

rdmerck said:
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
**** Im at the step above finally lol this is my first root and I had to downgrade, man Ive been doing this for hours and hours. My brain is fried LMAO **** I currently have my G2 with S-OFF and a stock Gingerbread 2.3.4. I have the PC10IMG.zip and su.zip in the root or directly in my sdcard. In no folders im trying to say... I reboot into the bootloader. The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
Well when I do it it doesnt ask me to "flash the recovery" it says "Parsing....(SD ZIP)
(1) RECOVERY
Do you want to start the update?
<VOL UP> YES
<VOL DOWN> NO
I accept the update by pressing vol. up. It comes back and says Update comeplete... - OK
Press Power to Reboot
I reboot and get into clockworkmod it says click "install zip from sdcard" I click it and a little hat appears but it doesnt do anything from there. I let it set a couple of min but still nothing... I have to pull battery out to get it to reboot. help pls....
Sean...

How to unroot my atrix?

Rooted my Atrix 4G successfully with this method: http://forum.xda-developers.com/showthread.php?t=1240130.
Trying to unroot, but it gives me this error:
ERROR: /restore/ backup doesn't exist or is incomplete!
These files must be downloaded and saved to your computer in a /restore/ subfolder
Download links can be found in the Help menu in this program
There are no downloads available for my phone.... I made no modifications when I rooted, just rooted to see if it would work. Trying to unroot for the new SOAK test. Any help?

bump?.......

You might have to flash the correct sbf for your phone and carrier using RSDLite.
Sent from Rob's Atrix

Sounds exactly like that. Definitely start from scratch and flash the initial 1.8.3 SBF with RSDlite.
http://forum.xda-developers.com/showthread.php?t=1136261
The process, depending on how far up the chain of in updates you go, can take a bit of time, but make sure you follow it EXACTLY.
Why were you using a Droid 3 tutorial to root your Atrix anyway?

Unroot
If you can restore to the Stock Moto, then you can use the Moto upgrade software as if you were upgrading to the 4.5.91.
motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
It will tell you that you are on the highest version but will allow you to reinstall the software. When it does this, it will unroot and relock the bootloader.

e07015 said:
If you can restore to the Stock Moto, then you can use the Moto upgrade software as if you were upgrading to the 4.5.91.
motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
It will tell you that you are on the highest version but will allow you to reinstall the software. When it does this, it will unroot and relock the bootloader.
Click to expand...
Click to collapse
Tried this, but wouldn't work. Said no update available at this time. My phone is 100% stock except the root. I'm on 4.xx, whatever is Gingerbread.

It should ask you if you want to reinstall the software anyway. It basically overwrites the system files. I was on the latest but it still let me refresh it thus removing root.
Are you using the motor update software you download from the motorola website? You install it on your computer then hook up your phone via usb cable.
Sent from my MB860 using XDA App

UNROOT?
OK. I am in the same boat. My Atrix has the latest update and I am rooted. No other mods done. I want to UNROOT, get the next OTA update, then ROOT again. I believe I rooted using ADB, ROOT, ADB FASTBOOT.
I do NOT want to lose my current setup since I have WAY too much time and energy into it and I love it.
I came across this on the web:
Un-root Steps:
1. Open Android Terminal Emulator (see download link above)
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.
4. You're un-rooted and all files that /preinstall put on your phone have been removed.
I don't know if this will work, or if it will leave my setup unchange, or if there is ANY chance of bricking my phone.
ALSO, there is an app in the market called OTA ROOTKEEPER and several other apps that claim to hide your rooted device so you can get updates, then unhide the root.
Anyone know?
THANKS.

This wont be an issue if the OTA will install perfectly fine with root. Owning the phone since launch day, I recall hearing that if you update with root access it bricks your phone. Is this true or not?
Anyway, @e07015, I used the method on the Motorola website, putting the image on my SD card. I assumed it wouldn't work but tried anyway. What exactly is the method your trying to explain?

Having root access might give the user the ability to alter the phone in ways that can effect stability, but root access alone doesn't change anything like that.

e07015 said:
If you can restore to the Stock Moto, then you can use the Moto upgrade software as if you were upgrading to the 4.5.91.
motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
It will tell you that you are on the highest version but will allow you to reinstall the software. When it does this, it will unroot and relock the bootloader.
Click to expand...
Click to collapse
pretty sure the bootloader dont relock

Motorola states that the Atrix will NOT be able to install this latest update if the phone is rooted or unlocked.
Sent from my MB860 using XDA App

On the Moto website, there are two options: Manual upgrade or automated update(pc users only). Do the automated update. You download the update tool and then connect your phone to the PC. Once it has recognized your phone, it will check for updates. It will tell you that you are on the latest version but asks if you want to reload it anyway. Do that and it will clear root and relock. Good Luck.
---------- Post added at 07:50 AM ---------- Previous post was at 07:43 AM ----------
I thought so also but after restoring to stock using the Moto Automatic Update tool, I rooted and tried to restore an old backup using CWM. It was giving me an error that my bootloader was locked. It no longer had the unlocked text at startup but I though it was still unlocked. Went through the unlock process again and then it let me use CWM again. Based upon this, I now assume that you can relock the bootloader.

e07015 said:
On the Moto website, there are two options: Manual upgrade or automated update(pc users only). Do the automated update. You download the update tool and then connect your phone to the PC. Once it has recognized your phone, it will check for updates. It will tell you that you are on the latest version but asks if you want to reload it anyway. Do that and it will clear root and relock. Good Luck.
---------- Post added at 07:50 AM ---------- Previous post was at 07:43 AM ----------
I thought so also but after restoring to stock using the Moto Automatic Update tool, I rooted and tried to restore an old backup using CWM. It was giving me an error that my bootloader was locked. It no longer had the unlocked text at startup but I though it was still unlocked. Went through the unlock process again and then it let me use CWM again. Based upon this, I now assume that you can relock the bootloader.
Click to expand...
Click to collapse
I've used the auto update tool and it tells me I'm current but doesn't give me the option to reinstall. If I have the zip from moto, can I just load it using clockwork mod? I went back to stock using a fruitcake on here, but I'm still unlocked and rooted. If the upcoming soak test is ICS (very doubtful), I want to be able to update

root keeper andfactory default

HI
don't know if anyone cares or has tried it or not, but i just rooted our spare tpt and then got root keeper to do a backup, i then did a foctory restore with ota2 installed.
quick reinstall of super user and rootkeepr got me my root access back
i didn't know if a factory reset would keep root or not, but since sometimes a factory reset is the only way it's handy to know you want loose root.
cheers
Tom

factory reset didn't delete root, I do it always (but I don't have OTA2 yet)

factory reset won't delete root, because it will only delete data, cache and i think sdcard partition. root is on system partition, so why should it dissapear?
OTA2 deletes /system/app/superuser.apk and /system/xbin. that's the reason why you lose root when updating. rootkeeper protects su file from /system/xbin by making a backup copy to /system named su-backup. superuser.apk can also be downloaded in the market. so you can restore root

Anyone try this on the K1? As far as using the app to regain root after updating to say the 14_14 update?

I only put this up because I know there are people out there like me that would not be sure if you could do this or not and are much happier when they find someone that has already done it.
Just hope that this will put someones mind at ease.
Tom
Sent from my ThinkPad Tablet using Tapatalk

Dueces99 said:
Anyone try this on the K1? As far as using the app to regain root after updating to say the 14_14 update?
Click to expand...
Click to collapse
It should work for all Honeycomb Tablets with update.zip-style OTA's

camou23 said:
It should work for all Honeycomb Tablets with update.zip-style OTA's
Click to expand...
Click to collapse
Any possible confirmation on this? Just having issues atm with recognizing my K1 through ADB, otherwise I would be using timmyDean's approach with a backdoor. If this app will keep root successfully, I'm surprised it isnt getting more attention.
Robert

If RootKeeper fails after OTA2, you still have root - only a little cp, chmod etc and all is done.

JA.de said:
If RootKeeper fails after OTA2, you still have root - only a little cp, chmod etc and all is done.
Click to expand...
Click to collapse
Care to elaborate? RootKeeper failed for me:
http://forum.xda-developers.com/showpost.php?p=22640567&postcount=7