Database Develop

[SCRIPT] GladRoot v4.3 (Bell 0.37.4, AT&T 1.26/1.52/1.57/1.83 Supported)

Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.​Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!​GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.​
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
​Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**​Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
​DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)​Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.​Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
​

I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?

Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results

So do this version allow sideloading?

awww yeahhh

PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.

plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload

After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?

drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?

drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?

Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?

shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?

s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.

drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.

Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).

Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?

PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.

tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?

Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...

when i run beforeupdate i get backup failed to execute properly
am i missing something?

[FIX] Updated by accident? Lost your Root? Downgrading Instructions

I've updated my phone. Lost my root.
Here are the instructions that got me successfully back to STOCK ROM that is still rootable.
EDIT #2: USE AT YOUR OWN RISK!
Instructions:
1. Get the LGNPST Package with the GenericModels and Components Plug-In.
http://www.megaupload.com/?d=GQ0P3XM7
2. Get the driver for the phone and install it.
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
3. Get the Stock Rom TOT file and extract it.
http://forum.xda-developers.com/showthread.php?t=1120062
4. Get the DLL file specifically for the Revolution
http://forum.xda-developers.com/showpost.php?p=14850289&postcount=19
5. Extract the "LGNPST Store & Lab"
6. Install the following order:
a. LGNPSTv1.2_Store_Version.msi
b. LGNPST_v1.2_Lab_Version.msi
c. Components >> LGNPST_Components_Ver_5_0_12_0.msi
d. GenericModels >> LGNPST_GenericModels_Ver_5_0_10_0.msi
7. Run "Right_Click_Register_DLL.reg"
8. Make a new folder called "Models" in the program's directory
Default: "C:\LG Electronics\LGNPST\"
9. Grab the "VS910.dll" and put it in the "Models" folder.
10. Right Click "VS910.dll" and click on Install.
Note: DLL WILL NOT INSTALL UNLESS COMPONENTS AND GENERICMODELS PLUG-INS ARE INSTALLED!!!
a. Make sure you install it properly
b. REBOOT!!
11. Run "LGNPST"
12. Plug in your phone, use Internet Connection Mode,and enable USB Debugging.
13. Phone should pop up in the list
14. Select the phone and click on the Open folder button inside the .BIN query underneath the COM## details.
15. Since it wants a .bin file, you can open the .TOT file by typing "*.*" inside the File Name query and hitting Enter
16. Select "VS910ZV4_04.S4_04.P58008.R5.user.tot" and Click OK
17. Then click on Upgrade
18. Wait a few minutes
19. Voila
EDIT: To all users running 64bit versions of Windows, you guys may run into problems since I only tested this method under a 32bit environment of Windows 7. I will attempt to get my hands on a 64bit version of Windows 7 to test some more and make a instructional Youtube video to help out everyone soon.
EDIT #2: Been busy, Haven't got a chance to make a youtube video yet.

Nice post!
Sent from my Cubed VS910 4G.

I didn't need this as I didn't lose my root but just wanted to say thank you for taking the time and posting this. Lot of upset people
Sent from my VS910 4G using XDA App

Nice Post.. now if i get bored one late night I will have to try it!

hilong08 said:
I've updated my phone. Lost my root.
Here are the instructions that got me successfully back to STOCK ROM that is still rootable.
Instructions:
1. Get the LGNPST Package with the GenericModels and Components Plug-In.
http://www.megaupload.com/?d=GQ0P3XM7
2. Get the driver for the phone and install it.
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
3. Get the Stock Rom TOT file and extract it.
http://forum.xda-developers.com/showthread.php?t=1120062
4. Get the DLL file specifically for the Revolution
http://forum.xda-developers.com/showpost.php?p=14850289&postcount=19
5. Extract the "LGNPST Store & Lab"
6. Install the following order:
a. LGNPSTv1.2_Store_Version.msi
b. LGNPST_v1.2_Lab_Version.msi
c. Components >> LGNPST_Components_Ver_5_0_12_0.msi
d. GenericModels >> LGNPST_GenericModels_Ver_5_0_10_0.msi
7. Run "Right_Click_Register_DLL.reg"
8. Make a new folder called "Models" in the program's directory
Default: "C:\LG Electronics\LGNPST\"
9. Grab the "VS910.dll" and put it in the "Models" folder.
10. Right Click "VS910.dll" and click on Install.
Note: DLL WILL NOT INSTALL UNLESS COMPONENTS AND GENERICMODELS PLUG-INS ARE INSTALLED!!!
a. Make sure you install it properly
11. Run "LGNPST"
12. Plug in your phone, use Internet Connection Mode,and enable USB Debugging.
13. Phone should pop up in the list
14. Select the phone and click on the Open folder button inside the .BIN query underneath the COM## details.
15. Since it wants a .bin file, you can open the .TOT file by typing "*.*" inside the File Name query and hitting Enter
16. Select "VS910ZV4_04.S4_04.P58008.R5.user.tot" and Click OK
17. Then click on Upgrade
18. Wait a few minutes
19. Voila
Click to expand...
Click to collapse
I thought this process caused problems with 4G not working and other various problems mentioned in the firmware thread?????

Not sure but maybe after doing this and obtaining root you can flash over to decrap rom or revolt rom and maybe that would fix the issues? Just a thought
dexter35803 said:
I thought this process caused problems with 4G not working and other various problems mentioned in the firmware thread?????
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App

i dont know much so probably anyone can answer this but will this wipe my phones memory or just act as an update?

squidder said:
Not sure but maybe after doing this and obtaining root you can flash over to decrap rom or revolt rom and maybe that would fix the issues? Just a thought
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Somehow i dont think so usually a tot is a full bin file that writes everything including the radio if this tot messes that up or doesnt complete properly u can have problems potentually even a brick

bonnaru said:
i dont know much so probably anyone can answer this but will this wipe my phones memory or just act as an update?
Click to expand...
Click to collapse
When I downgraded, the data stayed intact. However, do a backup anyways.

dexter35803 said:
I thought this process caused problems with 4G not working and other various problems mentioned in the firmware thread?????
Click to expand...
Click to collapse
I believe the users that have a failed downgrade had a problem with the .TOT file being downloaded properly and they probably had the phone in CDMA mode only when the phone should be in LTE/CDMA mode.
But if anything, they may have unplugged the phone before the program finished because the phone looks like it's done being flashed but the flash program says it's 80-90% complete.
Make sure you DO NOT unplug the phone until the flash program say it's safe to do so.

A note to all. If you have the drivers installed form earlier. UNINSTALL THEM!
Then restart. Install Verizon's drivers when you first plug your phone in while in 'Mass Storage' and THEN install those drivers. I had some problems getting it to work but that fixed it a bunch. Also, if you are getting a 0x800 error while trying to install the DLL, open CMD with Admin privileges and then 'regsvr32.exe "C:\LG Electronics\LGNPST\Models\VS290.dll" and it should install correctly.' I would suggest rebooting after this then running the tool.

hilong08 said:
When I downgraded, the data stayed intact. However, do a backup anyways.
Click to expand...
Click to collapse
wiped my sms log and thats it. Thanks much!

my phone isnt showing up in LGNPST...
how can i fix this?

This worked great for me! Thanks for the post!
Sent from my VS910 4G using XDA Premium App

jackpot08 said:
my phone isnt showing up in LGNPST...
how can i fix this?
Click to expand...
Click to collapse
You can try to update the drivers.
Reboot.
Turn on LGNPST.
Plug the phone to a DIFFERENT USB port.
Make sure USB Debugging is switched on on the phone.
Wait for the phone to install.
Voila.
I think LGNPST may have a refresh problem but that is what repaired the issue for me.

This Method works and is the same way I recovered my last Revo. Not sure what may have caused the issues for that phone. Using this method on the new replacement has been successful and still no problems with the phone. Did a S1C and rooted successfully and installed CWM using ADB without a hitch. Then came decrap 1.1 Life is great.

Having problems installing "VS910.dll" file. I keep getting an error. Tried Crax0r's suggestion and no dice.

You have to unzip the directory. Once that is done then the option will appear. If you still need help tonight then you might find me on irc. Im sure i can help you there. Message me if you dont figure it out.

Yeah I had download Bitzipper Trial to unzip....but when I right click the vs910.dll file I get this error "The module"C:\LG Electronics\LGNPST\Models\VS910.dll" was loaded but the call to DllRegisterServer failed with error code 0x80020009"
Edit: Sorry, I get the error when I right click and get an option to register....not Install...as the instructions says.

omik47 said:
Yeah I had download Bitzipper Trial to unzip....but when I right click the vs910.dll file I get this error "The module"C:\LG Electronics\LGNPST\Models\VS910.dll" was loaded but the call to DllRegisterServer failed with error code 0x80020009"
Edit: Sorry, I get the error when I right click and get an option to register....not Install...as the instructions says.
Click to expand...
Click to collapse
crax0r said:
Also, if you are getting a 0x800 error while trying to install the DLL, open CMD with Admin privileges and then 'regsvr32.exe "C:\LG Electronics\LGNPST\Models\VS290.dll" and it should install correctly.' I would suggest rebooting after this then running the tool.
Click to expand...
Click to collapse
I'm using win7 x64bit and the registry key that adds the right click register option wont work for me either. The manual .dll registration worked though after a reboot.

Maintain Root from V7 into OTA V8

This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.

Flashing back to v7 now to test this out.
:::EDIT::::
So far it is failing. I get to step 5 and I am not able to remount. Permissions denied.
Also your rar file has tripped my antivirus software.
Please post a link to any original instructions.
:::EDIT::::
Yep still fails completely at step 5. The root is not carried over at all.

These are original instructions. I emailed Dan (djrbliss). Your anti-virus picked up on one of the exploits contained in the .rar. Once you download even if your anti-virus removes one of the files the rest works fine. This is how I was able to keep root. It does work.
adding the ro.kernel.qemu=1 and the adb commands were from djrbliss.. the rest is all me
Just try the super1click.
in adb type "adb shell id" what is the output?
*Should read "uid=0(root) gid=0(root)" <--- if anything but, go back to /data/local.prop and make sure it is still there.. I might be crazy but think it disappeared once or twice on me..
then the S1C or just the adb commands from OP should work..
(Your anti-virus removed psneuter from the exploit folder.. not needed anyways)

I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.

Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
Click to expand...
Click to collapse
if you have any other issues beep me on IRC freenode #lgrevolution

Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.
Click to expand...
Click to collapse
Glad to hear.. I was close to starting over from scratch to make sure I didn't miss something.. lol

Hmm, didn't work for me will try again later
Sent from my VS910 4G using Tapatalk
Edit: Got it working, typo for me too it's qemu not qenmu lol

JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..

Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol

drt054 said:
JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..
Click to expand...
Click to collapse
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
---------- Post added at 10:02 AM ---------- Previous post was at 09:55 AM ----------
dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
.
I flashed back using the tot file, rooted then proceeded from there. Once I fixed my ignorant spelling issues everything worked great. Now that I have renamed the prop file and rebooted sound seems to be working.
My issue is now battery. The phone with no use is eating battery like a thunderbolt. It has been off charger for 2 hours with no use and its down to 84%.

dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
Yes if you already have the V8 update in order to gain root you have to go back to V7 Stock firmware. If you are on GingerVolt 2.0 you have to flash the V7 Firmware to get back to LG-STock and Stock Recovery. The LG1click does NOT work on the V8 update so there is no CWM-Recovery, or GingerVolt at this time until MT figures out how once again..

Haxcid said:
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
SORRY!!!.. like I said didn't realize it until it happened, lost vibration and went to check my voicemail and no sound. But made that /data/local.prop into a .bak file, rebooted and was fixed. MT said has something to do with that entry in place the phone thinks it is a terminal emulator instead of a phone or something like that..lol So hopefully this is only temporary.
There may be a new root out soon.. not by me, like I said by someone much smarter than me may have found a way.
Click to expand...
Click to collapse

Worked like a charm DRT thanks so much!
Here is what I did:
1) Flashed MTs ZV7 Rooted Stock (RevoZV7GBStock.zip)
http://forum.xda-developers.com/showthread.php?t=1348637
2) Created the local.prop file, etc.
3) Used MTs All-in-One tool to flash Stock Recovery (Option 5)
http://forum.xda-developers.com/showthread.php?t=1348557
4) Downloaded and installed the ZV8 update OTA
5) Used ADB to push files per DRT instructions
6) Rebooted
7) Confirmed that I still have root using Root Checked Basic!
A little bit different than DRTs posted method but I wanted to avoid having to use LGNPST, so at least I can confirm that this alternate approach works as well!

drt054 said:
This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.
Click to expand...
Click to collapse
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks

Nckmsn said:
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks
Click to expand...
Click to collapse
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium

elreydotcom said:
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.

Haxcid said:
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.
Click to expand...
Click to collapse
Ive been unable to get the adb part to work. I can't get the adb command line to come up on my pc. Anyway, so I'm on v7 unrooted with no sound. I have change the name of the prop file and even removed it but my sound wont come back. Do i need to complete the whole process for the sound to come back?

If you are unrooted you can't create the file, you need to get rooted first. Use the all in one package to root.
Sent from my VS910 4G using xda premium

Once I was able to finsh the entire process, I managed to rename the prop file and all sound came back. success!
Thanks

Made a post in another thread but any word yet I how we get CWM recovery from rooted zv8?
edit: MT let me know that I needed to recreate the prop file, reboot, and then choose the root option in his new all in one package for ZV8...worked like a charm!
Sent from my VS910 4G using xda premium

[TUTORIAL] ROOT Atrix HD ICS 4.0 [Testing Method]

[TUTORIAL] ROOT Atrix HD ICS 4.0 [Testing Method]
[Credits]
ROOT for ICS. kennethpenn's
----------------------------------------------------------------
Credits Hacker812c and My friends
Credits to my friend mqguitar for tests and reports
----------------------------------------------------------------
In this post you can see a new method based on the original root of the XDA
Here you will see a method of ROOT brought to you.
Just download the ZIP file, extract it to your desktop.
Open it and click the version of Windows runme.bat
Let the program do the rest, then download the app from Google SuperUser Play]
You may also need to download busybox and install it.
[requirements]
1. Microsoft Windows Operation System [preferably Windows 7]
2. Motorola Atrix running ICS 4.0 and Atrix HD drivers installed
3. Activate USB debbuging on your android settings
4. Make sure the device is not in a way to "mass storage" incorrectly
5. Place the Atrix in MTP mode!
6. Make sure you have installed adb drivers for ur device
7. Enable "UNKNOWN SOURCES" - from (Menu\Settings\Security)
[ROOT]
1. Download the script root and Unzip to a folder
2. Connect the Atrix HD to your computer with a USB cable
3. Enable USB debugging on your android
4. Activate the MTP mode menu notifications android
5. Disable antivirus and firewall on your computer
6. Run the exploit and wait the process finished.
7. After install check your ROOT with ROOT Check Basic
[ROOT]
MOD EDIT: Links removed
[ROOT Check Basic]
MOD EDIT: Links removed
[BusyBox PRO]
MOD EDIT: Links removed

Manual method
[ROOT][ICS] Root Atrix ICS 4.0
[Credits]
ROOT for ICS. kennethpenn's
----------------------------------------------------------------
Credits Hacker812c and My friends
Credits to my friend mqguitar for tests and reports
----------------------------------------------------------------
----------------------------------------------------------------

Woah seconds after I asked
Sent from my MB886 using xda premium

mqguitar said:
Woah seconds after I asked
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Post your results.. wait ... thank you

hacker812c said:
Post your results.. wait ... thank you
Click to expand...
Click to collapse
No go my friend.
This method is for the Droid Razr ICS 4.0.4 and does not work on Atrix HD you will get permission denied when trying to move Batch from /data/local/12m or when trying to move any file like su to the directory.

The_new_user said:
This method is for the ICS 4.0.4 and does not work on Atrix HD you will get permission denied when trying to move Batch from /data/local/12m or when trying to move any file like su to the directory.
Click to expand...
Click to collapse
i updated the method...
wait on moment...
test moving data for /data/local
if this command works post reply to edit script...

hacker812c said:
i updated the method...
wait on moment...
test moving data for /data/local
if this command works post reply to edit script...
Click to expand...
Click to collapse
So you updated the auto script, so I re download it and try again?

The_new_user said:
So you updated the auto script, so I re download it and try again?
Click to expand...
Click to collapse
no, only removed razr references...
to test copy manualy debugfs and su files to /data/local
test if this command work...
if work i reedit the script...
if work test manualy your root...

hacker812c said:
no, only removed razr references...
to test copy manualy debugfs and su files to /data/local
test if this command work...
if work i reedit the script...
if work test manualy your root...
Click to expand...
Click to collapse
Permision denied I have not been able to copy or push any file to the /data or /data/local directory.

Yeah I have tried it and it does not work just says phone was rooted but when I install SuperUser nothing happens. And also my phone for some reason is not being recognized anymore

mqguitar said:
Yeah I have tried it and it does not work just says phone was rooted but when I install SuperUser nothing happens. And also my phone for some reason is not being recognized anymore
Click to expand...
Click to collapse
posting new script...
remember this script is only testing...
new exploit script
http://www.mediafire.com/?4499495h4hdp3

I'm sure I'm being retarded but where do I get the Motorola drivers to allow for ADB access?
*nevermind I found them*

hacker812c said:
posting new script...
remember this script is only testing...
new exploit script
http://www.mediafire.com/?w1s2b5rv5h4hdp3
Click to expand...
Click to collapse
No mkdir failed for tmp, failed /data/local permission denied. Still no go not sure how to get permissions for the /data/local folder.

Do I just replace the files from that new folder in ICS ROOT from the first one too test?
And where can I find the drivers? I donwloaded it from motorola but I am still not able to detect my device.
I am running VMWare on my macbook pro and made sure sub connects to that.

mqguitar said:
Do I just replace the files from that new folder in ICS ROOT from the first one too test?
And where can I find the drivers? I donwloaded it from motorola but I am still not able to detect my device.
I am running VMWare on my macbook pro and made sure sub connects to that.
Click to expand...
Click to collapse
I found the drivers at Motorola dot com and queried on USB Drivers and found the Motorola Device Manager.
I can't post links just yet.

turboman93 said:
I found the drivers at Motorola dot com and queried on USB Drivers and found the Motorola Device Manager.
I can't post links just yet.
Click to expand...
Click to collapse
Problem was cable and now it is being found. Root did not work for me it all though it failed
We are getting though! I Believe in you:fingers-crossed::fingers-crossed:

Seems we need to figure out how to access /data/local directory this is where the problems lies with permission's. I have been trying for a day on and off due to work and have had no success so far. I will continue to help as much as I can.
---------- Post added at 09:13 PM ---------- Previous post was at 09:00 PM ----------
mqguitar said:
Yeah I have tried it and it does not work just says phone was rooted but when I install SuperUser nothing happens. And also my phone for some reason is not being recognized anymore
Click to expand...
Click to collapse
I am not trying the auto script, I am working on finding the exploit to allow the proper setup for rooting and permissions is our issue right now.
Try a new cable or rebooting your computer and see if it sees your phone then.

The_new_user said:
Seems we need to figure out how to access /data/local directory this is where the problems lies with permission's. I have been trying for a day on and off due to work and have had no success so far. I will continue to help as much as I can.
---------- Post added at 09:13 PM ---------- Previous post was at 09:00 PM ----------
I am not trying the auto script, I am working on finding the exploit to allow the proper setup for rooting and permissions is our issue right now.
Try a new cable or rebooting your computer and see if it sees your phone then.
Click to expand...
Click to collapse
I Finally got it to connect. I am running the auto script since I am not to tech savy. Trying the manual script through terminal on mac now. But having your same error :/

mqguitar said:
I Finally got it to connect. I am running the auto script since I am not to tech savy. Trying the manual script through terminal on mac now. But having your same error :/
Click to expand...
Click to collapse
mqguitar i testing new exploit...
i send for us in minutes...
hacker

hacker812c said:
mqguitar i testing new exploit...
i send for us in minutes...
hacker
Click to expand...
Click to collapse
Awesome I will check back soon to test, I will also continue to try new things.

[Q] Safestrap 3.05 crashed creating recovery image, now get bootloop

Hey guys, having a big problem here. Pretty much what the title says. I got my new (used) XT862 this morning, it had been reset to a fresh rom and wasn't rooted. I was so excited to finally get it that I started modding straight away.
First of all, I forgot to jot down the exact version number of the rom. I know already this was really stupid, but I can't do anything about it now... It was 2.3.4... I'm guessing it might have been the original 890? Is there any way to find this out from the recovery menu?
I'll try to describe what I did as completely as possible, I don't know if something might have gone wrong during the process or what.
First I installed Safestrap 3.05 from this link, not realizing that I had to have root (duh). It seemed to install fine, then when I ran it I got the standard "stopped responding" error with the "force close" button.
I then rooted it using Motofail, first I forgot to switch to root on my PC and it stopped at "daemon started successfully" so I hit CTRL+C until it dumped me back to the command line. Then I changed users on my desktop with su, ran it again and it worked perfectly, the superuser app on the phone showed up and it was operating normally.
(Here's what happened the first time I ran Motofail from my non-root user acct, I had to hit CTRL+C twice, once after "daemon started successfully, once after "waiting for phone to reboot" at which I rebooted the phone manually. Was still booting fine at this point.)
Code:
[*]
[*] Motofail: Universal Motorola Gingerbread Root Exploit (Linux version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
^Cerror: protocol fault (no status)
[*] Device found.
[*] Deploying payload...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: insufficient permissions for device
error: insufficient permissions for device
[*] Owning phone...
error: insufficient permissions for device
[*] Rebooting device...
error: insufficient permissions for device
[*] Waiting for phone to reboot.
^C
After rooting it was still booting fine so I think the problem was not there. Once everything was finished and I was back at the home screen I re-ran Safestrap which appeared to be running normally. I was planning to install Minimoto but I ran "create recovery image" first which I figured couldn't hurt. Well, Safestrap worked for a minute, then crashed (the "not responding - force close" error screen came up) and trying to run it again just crashed it immediately.
I did nothing else, just rebooted the phone not realizing the crash had apparently messed up my bootloader? Now I just get a boot loop, it plays the little Droid animation over and over again.
When I boot into the menu with M+power I don't get a Safestrap menu, and running "recovery" from there just gives me a screen with an /!\ icon and the Android character. I get the same screen if I try to boot with X+power.
I've tried to download the fast unbrick rom from here but neither of the links work... The old Dropbox link is long gone and the new Mediafire mirror says its allotment of 10 free downloads per week has been exceeded... infuriating!
Can anyone give me some advice or steer me in the right direction? I was so excited to get my new phone, I'll be heartbroken if I've managed to brick it for good! I don't want to do anymore damage without advice... please help?
********** // **********
EDIT: I found a mirror for fast/easy unbrick and that worked, so I'm now back to the stock 890 rom with functional bootloader and am much relieved. Two questions though:
1 - Can anyone shed some light on what went wrong during the safestrap process that bricked the phone? Was the fact that I tried to install it before I rooted it the cause?
2 - There is still a /safestrap directory on my internal storage (containing only the files "active_slot" and "translate"), should I delete this? Are there other bits of Safestrap left behind that I should get rid of too?
I will eventually try again as I'd really like to run Minimoto on this thing but I want to understand what I did wrong first.
Any info appreciated, thanks!

xjas said:
EDIT: I found a mirror for fast/easy unbrick and that worked, so I'm now back to the stock 890 rom with functional bootloader and am much relieved. Two questions though:
1 - Can anyone shed some light on what went wrong during the safestrap process that bricked the phone? Was the fact that I tried to install it before I rooted it the cause?
2 - There is still a /safestrap directory on my internal storage (containing only the files "active_slot" and "translate"), should I delete this? Are there other bits of Safestrap left behind that I should get rid of too?[/b]
I will eventually try again as I'd really like to run Minimoto on this thing but I want to understand what I did wrong first.
Any info appreciated, thanks!
Click to expand...
Click to collapse
1. I'm not sure why, but I can tell you that I have rooted using Motofail and installed Safetrap 3.05 multiple times without issue. Also, you should realize that Safestrap creates its /system, /data, and /cache directories for each ROM slot on "internal storage", so you need to make sure that you keep enough space there to fit the ROM slots. It's pretty much a given that you should use an external SD card and have the camera app, etc., store data on external SD rather than internal storage. I'd also avoid running apps on "internal storage".
2. It won't hurt to delete those files.
So, you should be able to:
- clear out enough storage on "internal storage". Make sure that you have at least 1 GB more than the data partition you want to create available, though I would want more
- enable USB debugging and root using Motofail
- *then* install Safestrap and install recovery
- do a full reboot to make sure that both the Safestrap menu pops up and the phone restarts fully without looping, etc. (In other words, make sure that stock boots and runs fine.)
- then create a ROM slot, activate it, flash Minimoto and have fun.

Well, went back through the whole process and it went great the second time. Now have Minimoto 1.7 running on a 3 GB partition (probably way overkill??) I'm really enjoying the minimalism in this release, no more sifting through pages of uninstallable crap in the menu to get the stuff I actually use. The extra speed & free memory makes a nice bump up from the HTC Dream (with 1.5 Cupcake!) this phone replaces.
Thanks for the advice, still no idea what went wrong the first time but I'm happy it's working how I want now.