Related
Hi all, first of all: i am from germany, so sorry for my bad english
So i tried to root my phone the "manual" way and used a german tutorial.
i'll explain what i did step by step:
- first i go the needed files, superuser.apk, SU, rage, root, busybox, wpx.ko (for my handset, here from the forum "2.6.32.21-gbe90714")
- adb push su /sdcard/su
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push rage /data/local/tmp/rage
- adb push busybox /data/local/tmp/busybox
- adb push root /data/local/tmp/root
- adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
usb disconnected and in terminal:
- /data/local/tmp/rage
after forking all the innocent children, in the tut it says:
"reset terminal. it should shut down. start it again and click away the FC, start it again and u should see a # in the terminal command line"
all that happend like he said!
- than connect usb
- adb push wpx.ko /data/local
- usb off
- in terminal "insmod /data/local/wpx.ko"
than he says, if everything goes right, it should appear "init_module 'wpthis-OTA.ko' failed (Function not implemented)" and you have temp root.
this all worked too, but now the bad part.
in the tut he says, in terminal do "/data/local/tmp/root"
when i did that, for me it said "mkdir failed. folder already exists"
so i opened the root file and did all my self by hand.
what i did was:
Code:
#!/system/bin/sh
#clean up after rage
/data/local/tmp/busybox killall rage
#remount system as read/write
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
#set up busybox
mkdir /system/xbin [COLOR="Red"]<- this i skipped! Folder existed allready[/COLOR]
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
#set up su and Superuser.apk
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
#remount system as read-only
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
ok, so far so good. it worked!
THAN the tut says, type "sync" in terminal, wait about one or two minutes and reboot. now u should see superuser and so on in the appdrawer list.
i did but there is NOTHING! no superuser rights at all!
than i was dissapointed and tried visionary+r14. did the temp root, it took really long (bout 1-2 min) and in the middle, the screen went black for some seconds. i only saw the statusbar. it ends and i click "permroot", nothing happens. i wait and wait. after about 5 mins, i restarted visionary, klicked permroot again and this time , after about 20 seconds the phone reboots. BUT, adw.launcher was gone FC, newsrob FC, browser FC'ses, gapps FC. And it didn't stop FC'ing. after about 2 minutes the phone restarted itself and booted normally.
Now my phone works almost, but adw.launcher, browser, newsrob and so on are still FC'ing when i try to launch them. 3 or 4 games too.
In german forum they say, first i have to reflash a RUU to restore my system and than i should try visionary directly and it should work.
my questions now:
1. What did i do wrong?
2. What went wrong?
3. Which RUU do i need?
4. How should i root my phone? Which TuT may i use?
My system build is: 1.32.405.3 CL275498 release-keys
Baseband: 12.28b.60.140eU_26.03.02.15_M3
Im thankfull for every help i can get!
tranceonline said:
Hi all, first of all: i am from germany, so sorry for my bad english
So i tried to root my phone the "manual" way and used a german tutorial.
i'll explain what i did step by step:
- first i go the needed files, superuser.apk, SU, rage, root, busybox, wpx.ko (for my handset, here from the forum "2.6.32.21-gbe90714")
- adb push su /sdcard/su
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push rage /data/local/tmp/rage
- adb push busybox /data/local/tmp/busybox
- adb push root /data/local/tmp/root
- adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
usb disconnected and in terminal:
- /data/local/tmp/rage
after forking all the innocent children, in the tut it says:
"reset terminal. it should shut down. start it again and click away the FC, start it again and u should see a # in the terminal command line"
all that happend like he said!
- than connect usb
- adb push wpx.ko /data/local
- usb off
- in terminal "insmod /data/local/wpx.ko"
than he says, if everything goes right, it should appear "init_module 'wpthis-OTA.ko' failed (Function not implemented)" and you have temp root.
this all worked too, but now the bad part.
in the tut he says, in terminal do "/data/local/tmp/root"
when i did that, for me it said "mkdir failed. folder already exists"
so i opened the root file and did all my self by hand.
what i did was:
Code:
#!/system/bin/sh
#clean up after rage
/data/local/tmp/busybox killall rage
#remount system as read/write
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
#set up busybox
mkdir /system/xbin [COLOR="Red"]<- this i skipped! Folder existed allready[/COLOR]
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
#set up su and Superuser.apk
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
#remount system as read-only
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
ok, so far so good. it worked!
THAN the tut says, type "sync" in terminal, wait about one or two minutes and reboot. now u should see superuser and so on in the appdrawer list.
i did but there is NOTHING! no superuser rights at all!
than i was dissapointed and tried visionary+r14. did the temp root, it took really long (bout 1-2 min) and in the middle, the screen went black for some seconds. i only saw the statusbar. it ends and i click "permroot", nothing happens. i wait and wait. after about 5 mins, i restarted visionary, klicked permroot again and this time , after about 20 seconds the phone reboots. BUT, adw.launcher was gone FC, newsrob FC, browser FC'ses, gapps FC. And it didn't stop FC'ing. after about 2 minutes the phone restarted itself and booted normally.
Now my phone works almost, but adw.launcher, browser, newsrob and so on are still FC'ing when i try to launch them. 3 or 4 games too.
In german forum they say, first i have to reflash a RUU to restore my system and than i should try visionary directly and it should work.
my questions now:
1. What did i do wrong?
2. What went wrong?
3. Which RUU do i need?
4. How should i root my phone? Which TuT may i use?
My system build is: 1.32.405.3 CL275498 release-keys
Baseband: 12.28b.60.140eU_26.03.02.15_M3
Im thankfull for every help i can get!
Click to expand...
Click to collapse
1 & 2 ...
Who can say? You could spend some time examining logcat and dmesg outputs but why? May as well just accept it went wrong and start again.
3.
You want this RUU file.
The most reliable method to flash it would be here. Make it into a pd98img.zip.
4.
After using the visionary r14 tool to temproot I then used this excellent tool to get permanent root. The tool can be used to get eng hboot s-off if you want it as well.
You should also get radio s-off using another excellent tool. Radio s-off is the single best thing you can do to protect yourself from rogue OTA updates which kill root.
5. If your phone explodes its not my fault.
I'm not sure why I'm helping a guy like you though. Fancy forking innocent children
EDIT: Just corrected my post slightly.
i'll try what u said.
I dont know why the rage command forked all the children
I am only thankfull, i did not have had to see that!!
so i am in the bootloader, first it says "no blablaimg.nbh" and so on, than it starts checking the pd98img.zip and after that, its back in the main menu of the bootloader and nothing happens
If you get stuck I'll try my best to help if I'm still around.
it doesn't ask me if i want to flash. first it loads when its says "Checking pd98img.zip" and a blue bar at the right upper corner starts loading. after that, it says "checking pd98img.zip"
when thats finished, nothing happens.
than i reboot my phone and everything is like before
it says "System UID Inconsistent" and i can press "I'm feeling lucky"
Edit: Just saw, that the browser is fully gone! no app in the list anymore!
Edit1: In the zip is an exe file? is this correckt? or is this file only for flashing through pc?
Edit3 LOL: i did a factory reset in the bootloader.
everything is back to stock and working fine now!
OMFG THATS A FU***ING JOKE!!
I did a factory reset to stock, configurated everything and what do my eyes see?
the superuser.apk! i tried SU in erminal and got SU rights! WTF???
how did THAT happen??
i dont know, but i have root now.
Tried to reboot and root stays permanent. This is ok for now i think.
Becaus i read that a Custom ROM don't gives u sooo much advantage, ill stay at stock with root for now. it runs fine and until it starts lagging to much or something else, i'll stay at stock ROM i think
Thank you very much for your help mox !
Ok, now there is another problem.
I have root, setcpu and terminal work fine. Titanium backup les too and says busybox is working too. Solo I wanted to use root explorer and delete some Stuff out of the /system/app folder. Things like amazon mp3 and so on. But I can't get read write rights in that folder. Why that? Can anyone help plz?
Sent from my Desire HD using XDA App
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
/data/local/tmp/root
Click to expand...
Click to collapse
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
sammd301 said:
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Click to expand...
Click to collapse
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
raitchison said:
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
Click to expand...
Click to collapse
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
gbarayah said:
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
Click to expand...
Click to collapse
right now...neither method works not the "visionary r14 or ADB/RAGE/GFREE" I wouldn't mind using either method, the problem is that ADB/Rage/GFREE METHOD keep giving this error message "mkdir failed for /system/xbin, File exists" which I have done a ton of research and still can find a fixed,
sammd301 said:
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
Click to expand...
Click to collapse
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
ON YOUR PHONE:
1. Launch Terminal Emulator
2. Execute /data/local/tmp/rage
3. Wait for the message: "Forked #### childs."
4. Menu > Reset Term - Terminal Emulator will exit.
5. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
Click to expand...
Click to collapse
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Right now I going to try to use this command to fix the error and if it doesn't work, I will then try to flash a custom and see how that goes...Update will be posted as I go along....thanks for the kind help....
raitchison said:
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Click to expand...
Click to collapse
I will attempt to flash ClockWorkmod, once I try out "ianmcquinn" suggesting in trying to fix the rooting error...thanks for the help
ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Yes I used the wiki instruction to gain temporary root on the phone and proceeded to tryout the above command...I got mostly error with the command below is what I en-counted as I enter the command....
# /data/local/tmp/busybox killall rage
No error here just # prompt
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
No error again just # prompt
# rm -rf /system/xbin
Error "rm failed for -rf, Read-only file system"
# mkdir /system/xbin
Error "mkdir failed for /system/xbin, File exists"
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
Error "cp: can't stat '/system/xbin/busybox': Not a directory"
# chmod 4755 /system/xbin/busybox
Error "Unable to chmod /system/xbin/busybox: Not a directory"
# /system/xbin/busybox --install -s /system/bin
Error "/system/xbin/busybox: not found"
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
Error "cp: not found"
# cp /sdcard/su /system/bin/su
Error "cp: not found"
# chmod 4755 /system/bin/su
Error "Unable to chmod /system/bin/su: No such file or directory
I am now going to attempt the Clockwork custom rom flash..
Folks victory is mine....No, VICTORY IS OURS, I sincerely like to thank all of you all, who replied with helpful suggesting...especially the following members "raitchison" from West Hill, CA and "ianmcquinn" a true senior member of xda-developer.
This is what I did to finally get the phone rooted....
I took "Raitchison" advice by trying to use flash_image to flash ClockWorkMod recovery... but during the process I could not get pass copying file to the phone root system folder usind android terminal emulator ...so I input this command "chmod 777/system" to gain write access to the folder...after doing that I manually moved busybox file to system folder and attempted a rooting the phone using the rooting instruction from the HTC G2/DESIRE Z wiki site...at...
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
And this time around, everything went as normal after rooting the phone I open root required app and Wa La...no error message...
Guys I once again wants thank you all for the support....I also looked forward to help out others facing the same issue...so if anyone has encounter the same or similar issue please feel free to post here and I will response....
Can any one help me I am trying to close this thread...How do I go about doing it....thanks
There is no need to close the thread, if anyone has a similar problem and finds it via search they can come in here and bring the discussion back up, otherwise if there is no activity it will naturally fall to the bottom of the thread list.
It works for me I just did it yday using visionary and gfree all on my phone weird that it doesn't work for you?
Sent from my Liquid Metal using XDA Premium App
Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
I ask because a few months back I rooted my DI18 Epic with a "One Click Root" and, for some reason, all my apps became unlinked from the android market, and nothing I did worked to restore their connections. After a few hours of panic, I unrooted using the accompanying "One Click Unrooter," and the problem went away.
Then, I noticed my bluetooth was't working. I took it to the Sprint store, they ordered me a replacement phone, and then wouldn't exchange it because CWM was on my current phone. I got them to exchange it eventually, but I felt like a complete dumbass for not knowing it didn't come off in the one-click-unrooting process.
So, is there a way to just get root? And then is there a simple way to get rid of it (uninstall SU and such as well) in case I have to exchange the hardware?
I've read a lot of stuff about flashing stock with Odin, but all the dl links for Odin are 404'd, and I'd rather not have to go back to fresh stock every time I need to take my phone in. What's your advice?
SuperOneClick v1.7 worked for me.
Trickee360 said:
Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
Click to expand...
Click to collapse
I don't know about "one-click", z4root might work, but there's anecdotal reports of it not working on Android 2.2.1. The one-click w/CWM redirector is the easiest way to root and definitely recommended if you want to do anything more advanced (ROMs, etc.). You can always return to stock everything with Odin.
That said, if all you want is root and nothing more, the manual version is relatively simple. It's really just three steps:
Use an exploit (rageagainstthecage-arm5.bin) to get "temporary root" (an ADB root shell).
Install Superuser's su binary to /system/xbin with the appropriate permissions (root.shell 4755).
Sideload Superuser.apk as a regular program, or download it from the market.
In which case "unrooting" is trivial. Just delete /system/xbin/su with root-explorer or something, and after remove Superuser via "Manage applications".
A while back I wrote up semi-detailed directions for doing this. They should work on EB13 with some modification. Here's some notes for EB13:
"rageagainstthecage-arm5.bin", "su", and "Superuser.apk" are all included in the one click package, that's the easiest place to get them.
Actually running "rageagainstthecage-arm5.bin" is the trickest part. There's a few ways to do it, and due to the nature of the exploit, sometimes only one or two of them will work for anyone. You can tell it works if on the next run of "adb shell" you get a "#" prompt instead of "$". Try these three ways in order until one of them works:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell /data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell (press return, and type below at the "$" prompt):
/data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb push root.sh /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/root.sh
adb shell /data/local/tmp/root.sh
With the last method's root.sh from the one-click package.
Once you have root, and have verified such by getting a "#" prompt with "adb shell", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb push su /system/xbin
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
adb install Superuser.apk
If you do nothing more, OTA updates should apply just fine. The only caveat is that /system/xbin/su will lose the appropraite permissions, so Superuser will no longer work. To restore it, do the same steps above to regain "temporary root", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
You shouldn't have to push a new "su" binary since it's already there, and similarly, you don't need to reinstall Superuser.
Yes, I do understand that zergRush is for Gingerbread, but I've read so many threads on user SOC, and multiple versions of it at that, to gain root. From past experiences rooting phones (LG Optimus V, Samsung Intercept, HTC Vivid) I understand ADB, and how things work, but this phone really has me stumped.
So I've tried everything under the sun, multiple different SOC versions (you name it, i've tried it), TPSparkyRoot, among others. Nothing will root this phone, even used the unbricking guide after finding out that V10F(or J, can't remember) is unrootable. So now I'm not V18F, which from what everyone is saying is very rootable. Some say SOC 2.3.3 will root on first try, well not for me.
For some reason SOC was always stopping at Step #7, no matter what version I am on. Reading the log I would always see it stop and freeze up at a step that looked like it was trying to mount something, or remount something. I would try Shell Root and it would just give me the Gingerbreak error when it tried to run the zergRush exploit.
Now I even got my hands dirty and installed the SDK, ran ADB and tried to manually run the zergRush exploit, I knew it probably was going to spit out the same feedback as SOC did but it was worth a shot.
Now I'm really stuck, should I reflash the V10 firmware to try and manually zergRush the phone? Is there really a working method out there, I mean there has to be cause people have been rooting these phones.
Just to make everyone aware, when I flashed the V18F firmware it was a ROM (HO!NO!) that was suppose to already have been rooted (the download to the rom was in one of the unbricking guides I found). The only problem was once I install V18F there was no root, no Superuser app, nothing.
So I'm going to once again, ask the nice people here at the Nitro XDA Community to lend me some advice.
===========================
UPDATE:
Ok, so upon more reading, and gutting out codes and methods from devs everywhere (credit will be made later) I got temp root, although any application that I used to check for root always took forever, let me explain.
I ran these commands manually, as found in TPSparkyRoot
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
I then waited until the phone booted back up completely and ran
Code:
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
I then waited for another full reboot. Now here is the weird thing, I can run "adb shell" and am automatically greeted with # instead of $. So I'm temp rooted right? I don't know what this script exactly is doing, the code looks to complex for my feeble mind to understand.
So now that I have root, I started pushing the required files into directories I couldn't access before.
Code:
adb remount
adb push su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chown 0.0 /system/bin/busybox
adb shell chmod 0755 /system/bin/busybox
adb push Superuser.apk /system/app/Superuser.apk
adb shell chown 0.0 /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
Now I'm not sure but after step 2/3 in the TPSparkyRoot it would feed me errors on writting those files, manually entered though it worked, for some reason I think that the script was not executing a remount, because manually they worked fine.
So I seem to have temp root, restarting the phone will set the shell back to $. Google Play will offer an update for SuperUser and update correctly, but it never shows in my app drawer, and other apps seem to act funny when trying anything with root. Any ideas?
Okay folks, I am a rooting newb where it comes to this wonderous device known as the Optimus G, and I need some questions answered.
First lemme fill you all in on some details where the computer I might be using to root my Optimus G is concerned. I run Zorin OS 6.1 64bit Core edition (yes, Linux) and that obviously that begs my first question, of any of the rooting methods mentioned in the development part of this forum, are there any that will work with Linux? And if so which ones or is there some kind of special magic I'll need to cast or some kind of coding wizardry level I'll have to obtain in order to be able to root my Optimus G?
Second, to fill you in on the phone, yes I have updated to ZV9 so if that borks me if you could please let me know?
Third, and Fourth actually are my concerns over being able to fix whatever possible brick type damage might be done. 3)How stable are the root/unlock methods, meaning there would be no way to reverse them? Of course I mean outside of accepting an OTA update which I already know better than to do on a custom ROM (had a Samsung Epic 4g before this so yeah I know how that goes.)
and 4)Is there an LGNPST (sp?) version for Linux or will I have to figure out a wa to maybe run it on WINE or something along those lines?
I'd ask about ROMS but I know everybody has an opinion of their own and I don't so much mind the stock one, though I might get the debloated version and see what else I can do with that.
Thanks in advance everybody for any help you all can give.
1) You can root through linux, although I don't know about which distros. I did it on ubuntu, using one of the links in the link in my sig.
2) AFAIK, you have to be on zv7/8 to root or unlock. You will have to use LGNPST to go back to one of those, and as far as I've ever heard that is a windows program only.
3) Both the root and unlock methods are reversible through whatever program you use to do it.
4) ???
You forgot profit!!!!
Sent from my LG-LS970 using xda premium
As long as you can attain a root shell and install ADB aka Android SDK, and as long as after that you can run ADB shell and then receive a prompt from your device you should be able to push the necessary files and then run the exploit and install the superuser binary there should be no issues. I actually took the windows root method, and used the commands in my Debian box and it worked very well. The only thing that I would be concerned with is weather not you can get a root shell in your specific version once that is attained, run ADB start-server as root then finish.
Basically I took this root method, and modded the script to fit linux.
(as noted from my post on the last page of that thread)
Preparation
ADB can be found either from the android sdk(tools only) or from the 'stuff' folder, in the archive below (i ran the one from the sdk)
Download this zip file, and extract the 'stuff' folder to a newly created 'root' folder on your Desktop
Open a terminal and cd to ~/Desktop/root
My adb location is coded into my $PATH variable so when I issue adb, it runs ~/android-sdk-linux/platform-tools/adb but you can either set up an alias (to the one included which would be alias adb=~/Desktop/root/stuff/adb if you follow the below extraction procedures or the one from the sdk which could be anywhere)
Before running the root I ran:
Code:
su -
adb start-server
exit
Then to test whether or not I had the correct version of adb, I ran:
Code:
adb shell
You should see your prompt change to that of the phone. if it displays any type of error message, please check your version of adb. to exit this prompt and continue with the root, simply type exit and press enter.
ROOT:
Paste the following into your terminal (which should now be in the ~/Desktop/root directory)
Code:
adb "wait-for-device"
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
adb restore stuff/fakebackup.ab
echo 'Select "Restore my data" on your phone!'
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
echo "Your phone will now reboot twice, DO NOT DISCONNECT USB!"
adb reboot
adb "wait-for-device"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system && /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su && /data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk && /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
echo "Rooting Complete!"
echo "SuperSU should now be available in your applications drawer!"
Assimilated using the interface that interacts with the advanced internet.