[SCRIPT] Root for 4.1.57 (Depreciated, use newer version) - Atrix 4G Android Development

HTML:
The new update blocks the current ways of attaining root for the device. However, if you have root before you update, it is possible to retain this during the upgrade.
Script is online!
A newer version is available here:
http://forum.xda-developers.com/showthread.php?p=12540398#post12540398

Yeah... I'll just wait for you
Thanks for this! been holding out on the update ever since I found out you lose root during the beta testings

if this works i guess it's time to get my desktop back up and running so i can flash back and use this. damn power supplies dying on me.

ill wait for ur auto script
will this b possible btw neone?
Flash the 1.5.7 sbf -> run gblur custom rom -> run the root scrip

No Gingerblur needs root to push its files, also if you need a host I can host

Scripts are online!
Run beforeupdate.bat, update, then run afterupdate.bat.

Haven't tried it yet but wanted to say thanks and great work!

--EDIT -- BELIEVE THIS IS FIXED--
you didn't package the bin folder with psneuter.. :X

In reference to "adb.exe push movesu.sh /data/local/tmp > NUL 2>&1"
movesu.sh is now backup.sh, yes?
Also busybox "mv /system/xbin/su /system/bin/frozenfish" clobbers the copy from system/bin, if there is a difference, i thought it was generally a symlink to /system/bin.
Other than that, good idea in renaming the binary file, I probably won't use frozenfish in case Motorola targets that now..

Sounds sweet! If I already updated can I flash back to old then re root? Then run script then update?
Sent from my MB860 using XDA App
Update: Yes You Can ! just finished..

Whoops - I based it from adeo without making the proper changes. Corrected one should be live in a few minutes.

all good take your time..
so far the only corrections were the movesu.sh in beforeupdate.bat
and the missing /bin folder :X .. well technically you just need psneuter in there.. and just change the /bin/psneuter.. to /psneuter saves you time lol

The new version is up. It depends on su being installed on the system. You'll also need to OK a request by Superuser for root before it will run on beforeupdate.bat.

curious as the previous workaround used webtop to retain root through LXterminal... with root on here, will we be able to re-apply the Webtop mod?
by the way, good work

"movesu.sh" is called but doesn't exist.

shawnbuck said:
The new version is up. It depends on su being installed on the system. You'll also need to OK a request by Superuser for root before it will run on beforeupdate.bat.
Click to expand...
Click to collapse
Do you have the su that does not require Superuser.apk installed?

Let me boot into my windows partition and I'll give it a try. Let me make sure I have the steps right:
Run beforeupdate.bat
Get OTA from system update
Run afterupdate.bat
Anything I'm missing? I'm rooted using aRoot fyi.

I think
adb.exe push movesu.sh /data/local/tmp > NUL 2>&1
is a typo and it should say backupsu

dLo GSR said:
curious as the previous workaround used webtop to retain root through LXterminal... with root on here, will we be able to re-apply the Webtop mod?
by the way, good work
Click to expand...
Click to collapse
Root here is a normal root, anything you could do before you'll be able to continue doing.
eval- said:
I think
adb.exe push movesu.sh /data/local/tmp > NUL 2>&1
is a typo and it should say backupsu
Click to expand...
Click to collapse
Thats right - I corrected that and added a new version.
OrangesOfCourse said:
Let me boot into my windows partition and I'll give it a try. Let me make sure I have the steps right:
Run beforeupdate.bat
Get OTA from system update
Run afterupdate.bat
Anything I'm missing? I'm rooted using aRoot fyi.
Click to expand...
Click to collapse
Exactly right. I'll clarify the directions in the OP.
lpsi2000 said:
Do you have the su that does not require Superuser.apk installed?
Click to expand...
Click to collapse
This doesn't come bundled with a copy of su, it uses the one already installed in the system.

will this work on flash sbf?

Related

[HACK] Busybox for HTC Tattoo - CoburnBrew Flavor! :D

This little gem of a phone is a tough little thing to custom install apps on, but that didn't stop the Coburn from being able to get busybox installed.
Therefore, introducing Busybox for your HTC Click/Tattoo!
FOLLOW THIS TUTORIAL CAREFULLY. This guide may brick or NOT brick your Tattoo (most likely the latter), however I cannot assure you that it's 100% fail proof. I have installed it successfully. IN OTHER WORDS: THIS IS NOT FOR THE FAINT HEARTED! IF YOU DO NOT KNOW WHAT 'FLASH','ADB' OR 'HACK' MEANS, PLEASE DO NOT CONTINUE.
Requirements:
1 HTC Tattoo (The Victim)
1 MS Windows Powered Computer (I used Win7 64Bit)
1 HTC Tattoo -> USB Cable (Included with phone... Well, it was in the box).
Download the package attached to this post. Extract all files to a directory like C:\BUSYCLICK . (Actually, please extract them there).
Installation
Connect your Tattoo to your phone, make sure USB Debugging is enabled (Settings -> Applications -> Development) and sit back. Windows should say "New Hardware! OMG!" and ask "What is this piece of tech?" (aka New Hardware Install Wizard). On XP, allow to search Windows Update. On Vista/7, I'm going to have to get back to you on that. The installed driver will be like "HTC Dream blah blah blah ADB Interface" or something. Odd why it says it's a HTC Dream...
Anyway, go to the folder where you extracted the files, and run the Installation.bat file. It's the one that says "Installation" With the cogs icon.
You'll get a DOS Prompt and some text, PAY ATTENTION! My installer will hold your hand and explain what's happening. Should any errors occur, you may be out of space on your Tattoo's internal memory or something. If you do get errors, please post them here! I'll try to fix them for you guys and girls.
Post-install tasks
When complete, run the TestBusybox.bat script in the same folder where you extracted the BusyBox files, and you should get some output. If not, busybox failed to install... Let me know what the error is and I'll try to fix it.
Notes:
You can use the busybox commands in /data/local/bin from "adb shell" or a terminal emulator on the phone itself... /data/local/bin/sh DOES NOT work from adb shell, I don't know why. It will work using a terminal emulator. Try "/data/local/bin/free" and such for some memory read outs, etc, etc.
Feel free to love/like/hate/kill/shoot my work, you can expect to see ROMs and the like in the near future as I love hacking devices.
Cheers,
Coburn64
Ok busybox installed normally...
Do i have root acces with busybox now? I dont see su...
C:\Busybox>adb shell /data/local/busybox ls /data
ls: can't open '/data': Permission denied
I do see /data/local and under tho... including ../bin and ../rights but dont see any use of it...
Coburn Hi, this is a step closer to being root
can be root in busybox?
chmod command does?
thx
Code:
benno.id.au/blog/2007/11/14/android-busybox
chmod command is useless without su...If only su worked
Installed and worked fine, can run busybox but:
it runs with shell privileges
setting setuid bit doesn't solve, because I can chown to root
Do I miss something?
Thanks Really appreciate your work!
Do you have to install the new RUU Click HTC WWE 1.63.405.1 WWE test signed NoDriver first?
coolbits said:
Code:
benno.id.au/blog/2007/11/14/android-busybox
chmod command is useless without su...If only su worked
Click to expand...
Click to collapse
I know friend!
I asked the chmod without adb, or if they could use the chmod as root from the busibox console
leon1984 said:
I know friend!
I asked the chmod without adb, or if they could use the chmod as root from the busibox console
Click to expand...
Click to collapse
All this does is allows you to run more commands from the shell in Android, whereas the standard shell doesn't have many commands built-in. Could be used in conjuction with a root hack.
One step more, but nothing to do with root
I'm starting to believe that Click will never have a root method working because its underused compared with other android devices
MiSSigNNo said:
One step more, but nothing to do with root
I'm starting to believe that Click will never have a root method working because its underused compared with other android devices
Click to expand...
Click to collapse
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
What's the new root vulnerability? Is it something that was just discovered?
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
Ok, where to find more info about this? :S
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
I was able to install Busybox on my phone successfully. But the problem is I don't know what it's for. Would anyone be kind enough to post a link or a tutorial for this? Thanks.
sheik_yerbouti said:
I was able to install Busybox on my phone successfully. But the problem is I don't know what it's for. Would anyone be kind enough to post a link or a tutorial for this? Thanks.
Click to expand...
Click to collapse
Busybox just allows you to use more features at the adb shell command line. So, yeah. Heh.
You lost me at 'adb shell command line'. Is that some command line provided by the Android SDK?
sheik_yerbouti said:
You lost me at 'adb shell command line'. Is that some command line provided by the Android SDK?
Click to expand...
Click to collapse
Sorry if I lost you. Let me sum it up: It's a 'feature pack' for Android Developers, which could be used in conjunction with rooting tools.
Coburn64 said:
What's the new root vulnerability? Is it something that was just discovered?
Click to expand...
Click to collapse
zenthought.org/content/file/android-root-2009-08-16-source
This is linked in the other thread...
ivendor said:
zenthought.org/content/file/android-root-2009-08-16-source
This is linked in the other thread...
Click to expand...
Click to collapse
That code is old, and apparently won't work. It won't compile either, Paul from Modaco tried it and it just spat the dummy and gave a make error.
Coburn64 said:
That code is old, and apparently won't work. It won't compile either, Paul from Modaco tried it and it just spat the dummy and gave a make error.
Click to expand...
Click to collapse
That's the code for the old asroot exploit (used in the Hero IIRC). It's been patched in August/09 so it won't affect the kernel in stock Tattoos.
Yeah, that's what I was getting at - the exploit is too old.
We need to either:
1) Get a S-OFF bootloader
2) Find another working root exploit
3) Dig around in the test ROM and extract the SU binary out of that sucker and put it in /data/local on the working ROM.
I think I can do the latter.

[SCRIPT] aRoot for Atrix 4G [ root - init.d - sideloading - tethering ]

Works on any Atrix, rooted, deodexed, stock, doesn't matter!!
OLYFR_U4_1.2.6 supported
OLYFR_U4_1.5.2 supported
*MOD EDIT* THIS IS OLD. USE ONLY IF YOU KNOW WHAT YOU ARE DOING.
Features:
Root
Installs tethering apn(enable the apn AFTER you enable mobile hotspot)
Unlocks all APN's for editing
Enables init.d support (on the android side, sample script mounts /system rw)
Installs Superuser.apk
Enables Non-market apps (sideloading)
Installs su and sqlite3 binaries to /system/bin
Removes oneclickroot busybox mess (if it exists)
unRoot script
How to use:
note: xp users, you will get an error about the TIMEOUT function, ignore it.
Enable USB Debugging on your phone (settings > applications > development > enable USB debugging)
Plug your phone into your computer
Extract aRoot.7z
Run aRoot.bat (run unRoot.bat to unroot)
Download:
http://ponack.net/designgears/atrix/aRoot/
Thanks DG!
Thanks DG. I knew if I waited it would pay off.
Any plans on making an "unroot" script?
designgears said:
My most recent brick was mostly caused by having busybox installed and symlinked twice. Busybox is already included on the phone stock, oneclickroot installs and symlinks it again in the /system/xbin directory. This is messy and can cause problems. I created this script to simply use what is there, only adding what is needed for a nice neat clean setup.
What this script does:
Roots
Installs Superuser.apk
Enables Non-market apps (sideloading)
Installs su and sqlite3 binaries to /system/bin
Removes onclickroot busybox install (if it exists)
Download:
http://www.ponack.net/designgears/atrix/aRoot.7z
Click to expand...
Click to collapse
Thanks for the departing gift DG. Can we install this without any issues if we have already used the superoneclick root method?
airbillion said:
Thanks for the departing gift DG. Can we install this without any issues if we have already used the superoneclick root method?
Click to expand...
Click to collapse
ya, it reverts that mess it created and does a cleaner install.
(more gifts to come)
Okay currently rooted with Adeo already assuming unroot before applying this script, but as far as Adeo I understand it doesn't need to be rooted for the install but if its already there would i have any problems swapping the root method?
Edit: Oh hehe was beat to it XD
Thank you!!! sooooo much for all your work and your continuous support, looking forward to what you will tackle next.
malfuncion said:
Thanks DG. I knew if I waited it would pay off.
Any plans on making an "unroot" script?
Click to expand...
Click to collapse
unroot script added
designgears said:
ya, it reverts that mess it created and does a cleaner install.
(more gifts to come)
Click to expand...
Click to collapse
Thanks for the reply. So no need to unroot, just apply your new script over the superoneclick?
Do you think you will go back to the atrix id it gets an unlocked bootloader?
This looks interesting: http://forum.xda-developers.com/showpost.php?p=11871384&postcount=183
Maybe this is the key we need to unlock the bootloader!
I ran the script and it gave me an error about TIMEOUT not a known function, but it still got the job done. I used the one before the unroot was added (redownloading now).
Again, many thanks. Can't wait to see what the other "gifts" are.
malfuncion said:
I ran the script and it gave me an error about TIMEOUT not a known function, but it still got the job done. I used the one before the unroot was added (redownloading now).
Again, many thanks. Can't wait to see what the other "gifts" are.
Click to expand...
Click to collapse
very odd, I wonder if older versions of windows dont support the timeout function...
what are you running?
aces, thanks DG! all the work to date on the Atrix are and have been appreciated.
Thanks DG
I used oneclickroot and have just done your aroot.bat. How do I know if it un messed the previous root and everything is now good?
tpdtopcop said:
Thanks DG
I used oneclickroot and have just done your aroot.bat. How do I know if it un messed the previous root and everything is now good?
Click to expand...
Click to collapse
pretty easy...
adb shell
cd /system/xbin
ls -l
you should only have a handful of files, no busybox, or any symlinks to it.
designgears said:
very odd, I wonder if older versions of windows dont support the timeout function...
what are you running?
Click to expand...
Click to collapse
Has to be the problem, I was on my laptop with XP loaded. Like I said, the script did the trick but just sqawked an error. I am on my 7 tablet now and the command works fine.
malfuncion said:
Has to be the problem, I was on my laptop with XP loaded. Like I said, the script did the trick but just sqawked an error. I am on my 7 tablet now and the command works fine.
Click to expand...
Click to collapse
I second that. XP here and got the TIMEOUT error, but worked just fine. Double checked my system/xbin and no busybox or symlink.
just looked it up, sure enough xp doesn't support that, oh well, doesn't matter, adb will wait for the device to some online, I might just take it out.
thanks for testing that guys.
i think xp still used it, just complained about it.
Just updated, now with init.d support and a better unrooter script
Sorry I'm new to this so if I used superoneclick then surely I will get a bricked phone...I get forced closed about once a day is that from the superoneclick?
Sent from my MB860 using XDA App
yokozuna82 said:
Sorry I'm new to this so if I used superoneclick then surely I will get a bricked phone...I get forced closed about once a day is that from the superoneclick?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It is possible that is the problem. Unless you are doing command line stuff you will be fine. It won't just brick you for no reason.
Thank you very much for your work...
Just to confirm, do I use this aRoot instead of your previous SuperOneClick?

Manually Root w/ Zerg after 893 OTA

I claim no credit for this but after the 893 OTA you wont have root and you will have to go this way to get it back.
Original post I robbed this from [HERE]
You will need adb to do this. You can get the download here depending on your operating system. ADB
Download the follow file: it contains the exploit, su, Superuser
Download exploit -->Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb push su /data/local
---> adb push Superuser.apk /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> cat /data/local/su > /system/bin/su
---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
---> chmod 4755 /system/bin/su
---> chmod 4755 /system/app/Superuser.apk
---> reboot
This is from P3Droid.
Click to expand...
Click to collapse
Worked like a charm. Thanks!
want to do this for my brother, you just connect the phone to the computer with usb debugging mode enabled right?
Fyi if you correctly root and forever root prior to the ota you will retain root. The update does not remove root if it was forever rooted.
Sent from my DROID BIONIC using XDA App
I used this method on a used Bionic I bought that has 5.7.893. It worked perfectly.
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
charlie310 said:
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
Click to expand...
Click to collapse
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
you forgot last step....then update and youll still have forever root
I restored and forever rooted my bionic, then did OTA, and still have root. I was on rooted stock previously, but restored because I wasn't able to get or pull the OTA update due to "error try again later".
Sent from my DROID BIONIC using Tapatalk
Terror_1 said:
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
Click to expand...
Click to collapse
Let's think about this logically:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
Or, D/L and install ADB, D/L and install Java SE, and D/L & unzip the Exploit Zip and type in 15 command lines to root your phone.
It's pretty obvious what is considered easier and requires less unnecessary software.
BTW, if you are flashing a ROM, then option 1 is always the best way to go since you don't have to D/L the OTA update since most ROMs have the update built in (and you already have the updated radio).
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
charlie310 said:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
It's pretty obvious what is considered easier and requires less unnecessary software.
Click to expand...
Click to collapse
You forget that some of us already have all the prerequisites. I personally can't say if your method works or not. It failed several times for me, so I gave up and zerg worked.
luke1333 said:
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
Click to expand...
Click to collapse
I am partial to doing things manually myself but I guess 43v3r does it too.
I personally had no luck with it.
Sent from my DROID BIONIC using XDA App
what version could you not root?
Does zerg work on 5.9.901 ?
luke1333 said:
what version could you not root?
Click to expand...
Click to collapse
893 43v3r doesn't work on, if you restore the 886 then root you should be fine. Just doing the update then trying to gain root isn't going to work.
kris7778 said:
Does zerg work on 5.9.901 ?
Click to expand...
Click to collapse
I don't know for sure but I am pretty confident that it would.
THANKS!
Flawless victory!
Binarality!
Has anyone rooted a previously unrooted device running version 5.9.901? Who's process?
This method worked for me, but I notice that my 3g service was weak and my 4g was gone. Even if i restarted the phone I couldn't get my 4g to work. This was after the 4g issue with VW braking it. Has anyone else had this problem?
1 click method
is there any 1 click method out there that can be used to do this ,,i used 4ever root a couple of time to restore my phone after screwing it up .. but now even that wont work .. so yeah i have the update but no root ...no matter how i try to do it before or after ..
and i unfortunately do not know how to connect to adb to push anything to my phone .. im not that technical with it ....dont have a clue .ive tried but not easy for me that is thanking you in advance Robb
One question, if I update and then for any reason I can't get root can I go back to stock rom you know the one before ota and start over? ???
Sorry for my english lol
Sent from my DROID BIONIC using XDA App

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

[Q] Official update January 2014

Hi everybody!
I noticed there is another update...it should not be so strong, just minor fixes...
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/97885/p/30,6720,8302/action/auth
I haven't done it yet, but after 12 hours I have always the notice about it.
I'm using Droid 4 in Europe, so I'm not so interested.
Anyway, do you know if I will lose the root permission?
Thanks!
I currently have 98.72.18.XT894.Verizon.en.US and 4.1.2, so I'm curious as to what the new updates are for the xxxxxx.188 and xxxxx.189. I would suggest something like VooDoo OTA to attempt to save your root but there is no guarantee that it will protect it if Motorola has figured out how to patch the exploit.
From Motorola, new software is .....
98.72.188.XT894.Verizon.en.US or 98.72.189.XT894.Verizon.en.US
Voodooo worked for me on latest O.T.A
karlsdroids said:
I currently have 98.72.18.XT894.Verizon.en.US and 4.1.2, so I'm curious as to what the new updates are for the xxxxxx.188 and xxxxx.189. I would suggest something like VooDoo OTA to attempt to save your root but there is no guarantee that it will protect it if Motorola has figured out how to patch the exploit.
From Motorola, new software is .....
98.72.188.XT894.Verizon.en.US or 98.72.189.XT894.Verizon.en.US
Click to expand...
Click to collapse
I used Voodoo root keeper for the latest ota update. Worked for me. Just needed to reinstall SU
mercermtn said:
I used Voodoo root keeper for the latest ota update. Worked for me. Just needed to reinstall SU
Click to expand...
Click to collapse
ok! thank you for your answer...
except for what mentioned by Motorola, the update changes something else? I mean speed or other aspects?
Same with voodoo here, didn't uninstall the SU app though
Sent from my XT894 using Tapatalk
Using voodoo to temp unroot and install the update did not work for me. I've decided to pass on the update and instead I'll just do a different rom. I found what the update consisted of and basically it's "bug fixes and security updates"- no real benefit there for me.
woodoo didn't work for me...can I use the same procedure to root again?
Sent from my DROID4 using xda app-developers app
For those who failed with voodoo, you could try Saferoot, it harmless to try...
Just root my RAZR HD although it designed for VZW Galaxy S4...
http://forum.xda-developers.com/showthread.php?t=2565758
I used voodoo on my wife's phone. Saved the su binary, installed the ota, clicked restore root. Voodoo said root restored but the check box for root stayed empty and root apps didn't work (like titanium backup). Found a post that gave terminal commands to manually restore the su backup. Worked perfectly and I now have root back. I forgot the link but luckily I copied and pasted the steps. So If voodoo said it worked but didn't, give this a try...
(I'd give credit where credit is due but lost the link)
"My wife's Transformer Infinity exhibited basically the same behaviour after its last 2 updates (both 4.2.something, IIRC). Fortunately the backup copy of su was intact, as it likely is in your case, and I was able to restore it manually using a terminal emulater app... adb would presumably have worked as well, but my notebook wasn't available at the time. Here's what I did.
.
1. Launch the terminal emulater of your choice (I used Better Terminal Emulater Pro, but the specific app probably doesn't matter)
.
2. Go to the location of the backup copy.
===========================
cd /system/usr/we-need-root
===========================
.
3. Use the su backup to obtain a root shell. This should trigger the usual superuser popup/notification, assuming that it's configured to do so.
=================
./su-backup -
=================
.
4. Remount the /system partition in read/write mode.
============================
mount -o remount,rw /system
============================
.
5. Copy the su backup to the proper location, taking care to keep the permissions intact.
=============================
cp -p su-backup /system/xbin/su
=============================
.
6. Remount the /system partition in the normal, read-only mode.
=============================
mount -o remount,ro /system
=============================
.
7. Reboot the device (might not be strictly required), to ensure that any root-enabled background apps are able to startup cleanly.
.
The usual disclaimers apply, of course. Your device might not have the same configuration as mine, etc., so these commands may need some tweaking. Also, if it was a 4.3 upgrade which caused you to lose root then this procedure likely won't work... I believe that su needs to be running in daemon mode in order to grant privileges, which certainly won't be the case for the backup copy (even if it is a 4.3-compatible version).
squall90x said:
Hi everybody!
I'm using Droid 4 in Europe, so I'm not so interested.
Thanks!
Click to expand...
Click to collapse
I too use this in Europe, and made the mistake of accepting this OTA update, which bricked my data connectivity. More info in this post:
http://forum.xda-developers.com/showpost.php?p=49627296&postcount=23
mike-phone said:
I too use this in Europe, and made the mistake of accepting this OTA update, which bricked my data connectivity. More info in this post:
http://forum.xda-developers.com/showpost.php?p=49627296&postcount=23
Click to expand...
Click to collapse
My data connectivity works without problems...
squall90x said:
My data connectivity works without problems...
Click to expand...
Click to collapse
Your reply inspired me to dig a bit deeper. It looks like the OTA update just cleared the list of APNs. I re-added the APN, and it works fine. Thanks.
mike-phone said:
Your reply inspired me to dig a bit deeper. It looks like the OTA update just cleared the list of APNs. I re-added the APN, and it works fine. Thanks.
Click to expand...
Click to collapse
You're welcome!
Sorry I didn't tell you...it was the same also for me!!
androitri said:
For those who failed with voodoo, you could try Saferoot, it harmless to try...
Just root my RAZR HD although it designed for VZW Galaxy S4...
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Thank you so much for this link. I accepted this OTA update about a week ago and lost my root access, despite having run Voodoo OTA Rootkeeper (maybe I did something wrong?) I tried to re-root it using the Razr Blade tool (which is what I had used originally to get root access), but that didn't work. Apparently motorola/verizon plugged the smart action security hole. But this one (saferoot) got the job done. Back to wifi tethering; thanks!
Richard
edit: I have the Droid 4 XT894, and the OTA update which broke my root was 98.72.189.XT894.Verizon.en.US
squabeggz said:
I used voodoo on my wife's phone. Saved the su binary, installed the ota, clicked restore root. Voodoo said root restored but the check box for root stayed empty and root apps didn't work (like titanium backup). Found a post that gave terminal commands to manually restore the su backup. Worked perfectly and I now have root back. I forgot the link but luckily I copied and pasted the steps. So If voodoo said it worked but didn't, give this a try...
(I'd give credit where credit is due but lost the link)
"My wife's Transformer Infinity exhibited basically the same behaviour after its last 2 updates (both 4.2.something, IIRC). Fortunately the backup copy of su was intact, as it likely is in your case, and I was able to restore it manually using a terminal emulater app... adb would presumably have worked as well, but my notebook wasn't available at the time. Here's what I did.
.
1. Launch the terminal emulater of your choice (I used Better Terminal Emulater Pro, but the specific app probably doesn't matter)
.
2. Go to the location of the backup copy.
===========================
cd /system/usr/we-need-root
===========================
.
3. Use the su backup to obtain a root shell. This should trigger the usual superuser popup/notification, assuming that it's configured to do so.
=================
./su-backup -
=================
.
4. Remount the /system partition in read/write mode.
============================
mount -o remount,rw /system
============================
.
5. Copy the su backup to the proper location, taking care to keep the permissions intact.
=============================
cp -p su-backup /system/xbin/su
=============================
.
6. Remount the /system partition in the normal, read-only mode.
=============================
mount -o remount,ro /system
=============================
.
7. Reboot the device (might not be strictly required), to ensure that any root-enabled background apps are able to startup cleanly.
.
The usual disclaimers apply, of course. Your device might not have the same configuration as mine, etc., so these commands may need some tweaking. Also, if it was a 4.3 upgrade which caused you to lose root then this procedure likely won't work... I believe that su needs to be running in daemon mode in order to grant privileges, which certainly won't be the case for the backup copy (even if it is a 4.3-compatible version).
Click to expand...
Click to collapse
After some days I found time to try...
I put the same command and reboot and it worked!!
Thank you so much!!

Categories

Resources