Hi everyone-
So I was having a ton of issues with SuperOneClick, and I think it was because it failed partway through so many times that I had files in weird states.
If you're in the same boat as me, you're in luck, as I finally think I figured out all the possible things that can go wrong and documented a more manual approach to rooting.
The benefit to this is you can see where it fails, and as such, better diagnose the problem and get moving.
Attached is a folder with the files you will need, this assumes you have ADB installed and the LG drivers as well.
Here are the commands you'll need to execute in order, a couple of them are for pre-cleanup (like rm /data/local/tmp/boomsh).
Code:
adb push busybox /data/local
adb push zergRush /data/local
adb push su /data/local
adb push Superuser.apk /data/local
adb shell chmod 777 /data/local/busybox
adb shell chmod 777 /data/local/zergRush
adb shell chmod 644 /data/local/Superuser.apk
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
adb shell ./data/local/zergRush
If you see this: [-] Bad luck, our rush did not succeed
Try this command again: adb shell ./data/local/zergRush
If you see this:
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
Continue on!
Code:
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p27 /system
./data/local/busybox cp /data/local/su /system/xbin/su
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
ln -s /system/xbin/su /system/bin/su
./data/local/busybox cp /data/local/busybox /system/xbin/busybox
chown 0:0 /system/xbin/busybox
chmod 6755 /system/xbin/busybox
ln -s /system/xbin/busybox /system/bin/busybox
./data/local/busybox mv /data/local/Superuser.apk /system/xbin/Superuser.apk
Ummmm..... not trying to be negative here but DoomLord did this via a batch file... might want to give him credits here.. you just extracted/modified/added to his .BAT file commands. just give him props, it's the right thing to do.
QUOTE:
@echo ---------------------------------------------------------------
@echo Easy rooting toolkit (v3.0)
@echo created by DooMLoRD
@echo using exploit zergRush (Revolutionary Team)
@echo Credits go to all those involved in making this possible!
@echo ---------------------------------------------------------------
@echo [*] This script will:
@echo (1) root ur device using latest zergRush exploit (16 Nov)
@echo (2) install Busybox (1.18.4)
@echo (3) install SU files (binary: 3.0.3 and apk: 3.0.6)
@echo [*] Before u begin:
@echo (1) make sure u have installed adb drivers for ur device
@echo (2) enable "USB DEBUGGING"
@echo from (Menu\Settings\Applications\Development)
@echo (3) enable "UNKNOWN SOURCES"
@echo from (Menu\Settings\Applications)
@echo (4) [OPTIONAL] increase screen timeout to 10 minutes
@echo (5) connect USB cable to PHONE and then connect to PC
@echo (6) skip "PC Companion Software" prompt on device
@echo ---------------------------------------------------------------
@echo CONFIRM ALL THE ABOVE THEN
@pause
@echo --- STARTING ----
@echo --- WAITING FOR DEVICE
@files\adb wait-for-device
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/; rm *"
@echo --- pushing zergRush"
@files\adb push files\zergRush /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 777 /data/local/tmp/zergRush"
@echo --- executing zergRush
@files\adb shell "./data/local/tmp/zergRush"
@echo --- WAITING FOR DEVICE TO RECONNECT
@echo if it gets stuck over here for a long time then try:
@echo disconnect usb cable and reconnect it
@echo toggle "USB DEBUGGING" (first disable it then enable it)
@echo --- DEVICE FOUND
@files\adb wait-for-device
@echo --- pushing busybox
@files\adb push files\busybox /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 755 /data/local/tmp/busybox"
@echo --- remounting /system
@files\adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
@echo --- copying busybox to /system/xbin/
@files\adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- installing busybox
@files\adb shell "/system/xbin/busybox --install -s /system/xbin"
@files\adb shell "rm -r /data/local/tmp/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@files\adb shell "chmod 06755 /system/bin/su"
@echo --- correcting symlinks
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@echo --- pushing Superuser app
@files\adb push files\Superuser.apk /system/app/.
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/; rm *"
@echo --- rebooting
@files\adb reboot
@echo ALL DONE!!!
@pause
My bad, I didn't see DoomLords post and didn't extract from his batch.
However, this was meant to be manual so you could see point of failure.
Also, I'm sure the approach is older than DoomLord's batch as it has been a manual way of rooting for years now using rage, pneuter, zerg, etc. (I personally just tweaked an old approach to rooting my HTC Incredible).
Mods, feel free to do what you want to the thread.
Sent from my Galaxy Nexus using XDA App
ummm thanks please?
Find me something that shows DarkLord is the genesis of this general approach to rooting and I'll be more than happy to thank him/her. Heck, maybe toss in a donation.
Otherwise, feel free to have the mods lock or delete this thread if they think I'm in violation of something.
On an unrelated note, I'm dropping dev for this phone and jumping ship to the Skyrocket. See most of you around, I'm sure!
Sent from my Galaxy Nexus using XDA App
Nice job repherb, one less developer.
Aww, don't blame repherb
Phone just wasn't working out for me like I wanted. Plus my eyes are biased towards over saturated AMOLED screens.
Sent from my Galaxy Nexus using XDA App
I doubt the decision was made based on one person's post. And there is no reason to continue throwing jabs around - best to just drop it and move on...
Dev's just seem to think that LG was too late to the playing field with Android, and thus don't want to support their products. Oh well, I'm waiting for ICS anyways.
LiViD said:
Dev's just seem to think that LG was too late to the playing field with Android, and thus don't want to support their products. Oh well, I'm waiting for ICS anyways.
Click to expand...
Click to collapse
But does LG support their own products?
Where is the recovery rom??
If you tried to tweak this phone and phone won't unable to boot,
there' no ways to restore this phone to factory!
On my old Sony x10, I can reflash the rom even I'm on the latest os version.
When I talked to LG support they said the lack of a recovery image was at carrier request.
schwin97 said:
When I talked to LG support they said the lack of a recovery image was at carrier request.
Click to expand...
Click to collapse
I don't believe this BS !
I think it's just LG excuses to point finger.
How about a "leaked" rom?
htc and samsung phones so popular cus there's always a "leaked" rom for it.
To be quite honest, I personally feel for burningember as i prefer AMOLED screens too. I use the Optimus for the PPI. I didn't jab or flame or bad-talk him at all, and he knows for sure i never accused him of violating anything and I was quite positive. All i did was point something out, nothing more. his post after that was informative even to me, and he got thanks from me for it. He even admitted it had nothing to do with me at all! I have seen what he is up to, and to be quite honest i feel a sense of loss regarding his decision to drop from the LG Nitro/Optimus LTE dev scene as i am quite sure he would have been a serious asset. I wish him the best on his current and future projects. and hey, you never know... he may come back to us in some capacity!! Good luck buddy, keep tabs on us over here okay??
burningembers said:
Aww, don't blame repherb
Phone just wasn't working out for me like I wanted. Plus my eyes are biased towards over saturated AMOLED screens.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Hi Burningembers,
I understand that you are switching over to the Skyrocket. However, while you are still in possession of the Nitro, would you mind helping us as much as possible, any way you can, with whatever you can find on that phone? We are very limited with the help from Devs so any help is greatly appreciated.
Also, if it's possible for you, could you stop by once in a while with anything you can find about the phone? I'm sure you will be busy with the skyrocket but if you ever have some spare time, please help us.
Thank you for your contribution, present n future
aquariuz23 said:
Hi Burningembers,
I understand that you are switching over to the Skyrocket. However, while you are still in possession of the Nitro, would you mind helping us as much as possible, any way you can, with whatever you can find on that phone? We are very limited with the help from Devs so any help is greatly appreciated.
Also, if it's possible for you, could you stop by once in a while with anything you can find about the phone? I'm sure you will be busy with the skyrocket but if you ever have some spare time, please help us.
Thank you for your contribution, present n future
Click to expand...
Click to collapse
Ohh, I think maybe there's been a miscommunication or misrepresentation of some sort. I'm hardly a seasoned developer. I'm a software dev by day, but by night I'm a complete noob android developer.
I'm more than happy to contribute what I can, when I can, but I'll be honest - it might not be much. On the plus side, the Skyrocket is also on Gingerbread, so at least for a lot of core things there may be some applicable crossover.
I'm just learning. But its definitely fun, and if and when there is crossover with anything I do (which again, might not be much) I'll gladly contribute what I can. I do hope CWM or something makes its way to the Nitro though, that's huge in getting things going.
Also, my two cents, the Nitro's a great phone. The screen is pretty darn gorgeous, the text is crisp and clear, and it seems really prepped to receive ICS (heck, the soft keys on it seem like they were designed with ICS in mind). So I really do hope it gets some lovin'
Well, i'm in the same boat: a hardware tech with a streak of helping those with laptop issues for free by night, and a full time dad of 3 (i'm Mr. Mom here, wife has...other...responsibilities). I've been helping out here for a bit, but since i acquired the P930, i've been pouring more time into it than my past phones.
I _may_ have found a way to recover from the "lost" launcher black screen issue. I'll post in the proper category if i can successfully fix it.
Hi guys, I'm with the Thrill 4G team and it seems that if you could get z4Root or Gingerbreak it works fine.
Just remember.
You brick, I'm not to blame, bit its worth a good go!
Hopefully we will have out Thrill Nitro ROM finishes soon.
Late Merry Xmas mates!
Sent from my LG-P925 using Tapatalk
uhhhhhhhh??????? thrill ROM on a Nitro??? Did i miss something folks??? Someone please enlighten me...
rydeN- said:
Hi guys, I'm with the Thrill 4G team and it seems that if you could get z4Root or Gingerbreak it works fine.
Just remember.
You brick, I'm not to blame, bit its worth a good go!
Hopefully we will have out Thrill Nitro ROM finishes soon.
Late Merry Xmas mates!
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
We already have root, the problem is accessing recovery or the bootloader. We also need to get cwm ported over to our phone... some of us are working towards porting cwm .
I can give you a Script to port CWM via Thrill, it would work the same way.
Sent from my LG-P925 using Tapatalk
Related
I'm a stock kind of guy. If I want to change things like launchers or whatever I can do it myself once I get root. Plus I like quickoffice and a lot of ROMs like to remove it. Here's what I did.
You can download the stock firmware from samfirmware.com. Flash using Odin. Do this if you want to return to stock 2.3.5. If you are an AT&T customer, you can get the 2.3.6 OTA at this point. I'm still working on pulling the OTA for non AT&T customers.
If you can't get the OTA because you have a custom recovery flashed, see the bottom of this post for the stock recovery. Unrar it and flash using the PDA mode in Odin.
Once you're on 2.3.6, flash CWM from this thread http://forum.xda-developers.com/showthread.php?t=1458153
At this point, there is no need whatsoever to find an exploit in the system in order to try to "root" this phone. CWM provides root access using adb.
Boot into CWM by holding the down volume and the power button. At this point your phone already has root. The only things missing are to push the su and busybox binaries and the superuser.apk. Go into mounts and storage and mount /system
Since I'm lazy, I downloaded DooMLoRD's rooting script here http://forum.xda-developers.com/showthread.php?t=1321582. Note the script does not work on our phone and we don't need the zerg exploit. All we need are the binaries and a way to push them to our phone. DooMLoRD also handily includes an adb shell
In the same folder as runme.bat, make runme2.bat in notepad and paste in the following:
Code:
@echo --- creating temporary directory
@files\adb shell "cd /data/local && mkdir tmp"
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/ && rm *"
@echo --- pushing busybox
@files\adb push files\busybox /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 755 /data/local/tmp/busybox"
@echo --- copying busybox to /system/xbin/
@files\adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- installing busybox
@files\adb shell "/system/xbin/busybox --install -s /system/xbin"
@files\adb shell "rm -r /data/local/tmp/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@files\adb shell "chmod 06755 /system/bin/su"
@echo --- correcting symlinks
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@echo --- pushing Superuser app
@files\adb push files\Superuser.apk /system/app/.
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/; rm *"
@echo ALL DONE!!!
@pause
One more final note, after you reboot, update the superuser apk from Google Play. Reboot again before trying to update su or it will fail. Update busybox with the stericson app if you want but it's not necessary.
This method will work on stock 2.3.5 as well. To unroot, just open an adb shell and delete busybox, su, and superuser.apk
Hi Nardholio,
One quick clarifying question: if I flash back to stock 2.3.5 using Kies, will all my apps and personal data get wiped?
Thanks!
I've only had this phone for 2 days, but it looks like Kies will only flash a version you already have (that's not an upgrade) if you force it to initialize the phone. So yes. Hopefully someone will pull the stock recovery in a flashable package for us eventually. If you really want to do this and save your data in the meantime, flash a rooted 2.3.5 ROM (or if you installed CWM on top of non-rooted stock 2.3.5 you could use this same script to root it), then back up your data with Titanium to a safe place (external SD) before wiping the phone and getting the OTA.
Note, installing CWM doesn't appear to increase your flash counter so if you're currently on stock 2.3.5 and for some reason can't OTA to 2.3.6 AND you want to save your data and you care about your flash counter, rooting your 2.3.5 to save your apps seems to be the way to go.
Nardholio said:
I think you have to be an AT&T customer to get this.
Click to expand...
Click to collapse
So it's not enough to have the AT&T version of the phone, you actually have to have a valid AT&T SIM as well? About phone shows 2.3.5 and my phone is just telling me I'm up to date.
worked like a charm! thanks! this was the one thing that annoyed me, having to downgrade to be able to have root. i prefer to have 2.3.6 mainly because of the ability to have video chat on google talk.
Ahhhh, I wish I'd seen this thread before I flashed a custom kernal. Now I'm running ardatdat on the stock rom.
roothorick said:
So it's not enough to have the AT&T version of the phone, you actually have to have a valid AT&T SIM as well? About phone shows 2.3.5 and my phone is just telling me I'm up to date.
Click to expand...
Click to collapse
I have the same problem. Hoping someone will post a stock or rooted 2.3.6 ROM, or ICS will come out soon.
oldnoob said:
I have the same problem. Hoping someone will post a stock or rooted 2.3.6 ROM, or ICS will come out soon.
Click to expand...
Click to collapse
is there a way to create a flashable rom from a nandroid backup? or can someone flash another persons nandroid backup? i can go back to untouched stock and do a backup and post it if it could be used...
I'm sure there's a way to do it, I just don't know how. At this point it might be better to just wait for ICS to drop.
Wat does it matter having a certain build number? As long as everything works fine who cares
Sent from my SAMSUNG-SGH-I927 using XDA
http://db.tt/LbIu6LTv
Try this one, it's called megatron root. It's the only root that worked on lg thrill on gingerbread maybe it will work here.
Sent from my HTC One X using xda premium
deleted post
Will flashing CWMR prohibit the OTA ICS Update?
Nardholio said:
I'm a stock kind of guy. If I want to change things like launchers or whatever I can do it myself once I get root. Plus I like quickoffice and a lot of ROMs like to remove it. Here's what I did.
You can download the stock firmware from samfirmware.com. Flash using Odin. Do this if you want to return to stock 2.3.5. If you are an AT&T customer, you can get the 2.3.6 OTA at this point. I'm still working on pulling the OTA for non AT&T customers.
If you can't get the OTA because you have a custom recovery flashed, see the bottom of this post for the stock recovery. Unrar it and flash using the PDA mode in Odin.
Once you're on 2.3.6, flash CWM from this thread http://forum.xda-developers.com/showthread.php?t=1458153
At this point, there is no need whatsoever to find an exploit in the system in order to try to "root" this phone. CWM provides root access using adb.
Boot into CWM by holding the down volume and the power button. At this point your phone already has root. The only things missing are to push the su and busybox binaries and the superuser.apk. Go into mounts and storage and mount /system
Since I'm lazy, I downloaded DooMLoRD's rooting script here http://forum.xda-developers.com/showthread.php?t=1321582. Note the script does not work on our phone and we don't need the zerg exploit. All we need are the binaries and a way to push them to our phone. DooMLoRD also handily includes an adb shell
In the same folder as runme.bat, make runme2.bat in notepad and paste in the following:
Code:
@echo --- creating temporary directory
@files\adb shell "cd /data/local && mkdir tmp"
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/ && rm *"
@echo --- pushing busybox
@files\adb push files\busybox /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 755 /data/local/tmp/busybox"
@echo --- copying busybox to /system/xbin/
@files\adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- installing busybox
@files\adb shell "/system/xbin/busybox --install -s /system/xbin"
@files\adb shell "rm -r /data/local/tmp/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@files\adb shell "chmod 06755 /system/bin/su"
@echo --- correcting symlinks
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@echo --- pushing Superuser app
@files\adb push files\Superuser.apk /system/app/.
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/; rm *"
@echo ALL DONE!!!
@pause
One more final note, after you reboot, update the superuser apk from Google Play. Reboot again before trying to update su or it will fail. Update busybox with the stericson app if you want but it's not necessary.
This method will work on stock 2.3.5 as well. To unroot, just open an adb shell and delete busybox, su, and superuser.apk
Click to expand...
Click to collapse
Thanks for all of your info.
I have gotten myself back to bone stock ATT 2.3.5 using samfirmware and then Kies updater to wipe and reload and then used the OTA updater to get me to 2.3.6. As far as the OTA system says, I am up to date. The problem is I can't use Titanium Backup to get all my apps back if I am not rooted or use this flashable CWMR you linked to. (or any other apps that depend on root.
I have no technical issues with doing this but I am scared that I will have to start over, and go back square one when the ICS drops if i have CWMR on my system. What do you think about this? Should I wait here with stock 2.3.6 and just check the OTA updater every 24 hours or go ahead and flash CWMR?
Thanks,
Mac
macwhite1 said:
Thanks for all of your info.
I have gotten myself back to bone stock ATT 2.3.5 using samfirmware and then Kies updater to wipe and reload and then used the OTA updater to get me to 2.3.6. As far as the OTA system says, I am up to date. The problem is I can't use Titanium Backup to get all my apps back if I am not rooted or use this flashable CWMR you linked to. (or any other apps that depend on root.
I have no technical issues with doing this but I am scared that I will have to start over, and go back square one when the ICS drops if i have CWMR on my system. What do you think about this? Should I wait here with stock 2.3.6 and just check the OTA updater every 24 hours or go ahead and flash CWMR?
Thanks,
Mac
Click to expand...
Click to collapse
You might as well just wait should be any day now. That way you could get the update when it is available.
Sent from my SAMSUNG-SGH-I927R using xda app-developers app
You should be able to flash the stock recovery on top of CWM and you'll be good to go for OTAs, although there isn't much point in *just* flashing CWM if you aren't going to deviate from stock otherwise.
One more thing, I found an even easier root method. If you download the CWM flashable version of superuser from http://androidsu.com/superuser/ and flash CWM, and then flash Superuser, bam, instant root!
Hi I have used odin and CWMR_recovery.tar.md5 flashed ok, but how do I flash superuser apk etc. I have the file runme2.bat ?? but how do I use it ?
This bit for me is unclear, can anyone assist and make this bit a little clearer for "simple is as simple does."
Thanks
pgunning1 said:
Hi I have used odin and CWMR_recovery.tar.md5 flashed ok, but how do I flash superuser apk etc. I have the file runme2.bat ?? but how do I use it ?
This bit for me is unclear, can anyone assist and make this bit a little clearer for "simple is as simple does."
Thanks
Click to expand...
Click to collapse
You dont flash an apk file you only flash zip files. if you go into the ROM zip/system/app just drop the superuser apk into there and then flash that rom. When you boot up the apk file you put in the ROM will turn into an app on your phones app drawer. Or you could just install superuser in market.:fingers-crossed:
Thanks for the quick reply, Ive just installed superuser and busybox and supersu ? superuser installed as did the other two, superuser opens but busybox says it cannot install as root is not complete/accessible. the flash of cmw by odin went ok and have rebooted no probs, I have not change operating system just trying to root 2.3.6 gingerbread ! any help appreciated so close yet so far LOL
ATB
pgunning1 said:
Thanks for the quick reply, Ive just installed superuser and busybox and supersu ? superuser installed as did the other two, superuser opens but busybox says it cannot install as root is not complete/accessible. the flash of cmw by odin went ok and have rebooted no probs, I have not change operating system just trying to root 2.3.6 gingerbread ! any help appreciated so close yet so far LOL
ATB
Click to expand...
Click to collapse
just by installing superuser doesnt root your phone, you have to flash the zip file to root your phone.
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?
Rooting The Ampe A10 Dual core 3g ICS
1.
Download and install the drivers required to connect the tablet to a windows pc (I used Win7) not any old ADB drivers will do the first ones I came across didn’t work so I recommend downloading from here - http://www.topnotchtablets.com/installADBdriver (PDA Net for Android)
2.
Download the rooting program from this thread here
http://forum.xda-developers.com/showthread.php?t=1886460
Bin4ry…zip direct link - http://ul.to/h44f6vni
3.
Extract the contents of the zip folder into a directory on the pc
Rooting is done at your own risk!
4.
Plug the tablet into the pc and run the RunMe.bat file
Screen will pop up select option 1 Normal
follow the instructions on the screen, it will refer to the tablet and you need to select restore. Once updated a reboot will happen and root should be done, if you wish to check root download root checker from the android market
enjoy
you mite like Webkey for example to remotely use the Android
Thanks, I've already rooted the same device as Sanei N10 3G (MSM8625 CPU).
But do you know something about a recovery mod that works with this tablet?
recovery
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
Be careful, we're talking about the 3G version with Qualcomm Snapdragon CPU.
If you have anything but root, pls post it.
I have no Ampe A10/Sanei N10 Dual core 3G. recovery or firmware met?!
snapon said:
Rooting The Ampe A10 Dual core 3g ICS
2.
Download the rooting program from this thread here
http://forum.xda-developers.com/showthread.php?t=1886460
Bin4ry…zip direct link - http://ul.to/h44f6vni
Click to expand...
Click to collapse
First of all, thank you for your help!
Could you please upload this file on a site where one can really download it and isnʼt directed elsewhere to register for a paid package?
There are many good file sharing sites, even Googleʼs Drive.
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
The Ampe 10 seems to have its own recovery built in and can be started by turning the device off turn it back on hold both volume up and power. From this menu you can recover / update from the SD card. I found the original firmware here 86pp.com/download_view.asp and have installed this one you need to extract msm7627a_fw8937-ota-eng_mmc.zip from the downloaded zip copy it to the SD
I think the firmware can also be found here: szampe.com/support_down.asp? but as its all in Chinese its difficult to tell
Mazarin07 said:
First of all, thank you for your help!
Could you please upload this file on a site where one can really download it and isnʼt directed elsewhere to register for a paid package?
There are many good file sharing sites, even Googleʼs Drive.
Click to expand...
Click to collapse
Its not mine to re-distribute and you can download from that fileshare site without registering or paying you just use the 'Free' option and wait a little longer
thanks
thanks worked for me
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
Try this site slatedroid.com/blog/85/entry-96-aokp-cm9-cm10-installation-guide-for-ampe-a10-sanei-n10/
Thanks in advance!
W3sti said:
Thanks, I've already rooted the same device as Sanei N10 3G (MSM8625 CPU).
But do you know something about a recovery mod that works with this tablet?
Click to expand...
Click to collapse
Did you mean you rooted Sanei N 10 with dual core Qualcomm MSM8625? Could you please tell which method you followed, or how you managed to do it.
And also, will I ever be able to install Jelly bean on this particular tablet?
Thanks in advance!
Mt Everest said:
Did you mean you rooted Sanei N 10 with dual core Qualcomm MSM8625? Could you please tell which method you followed, or how you managed to do it.
And also, will I ever be able to install Jelly bean on this particular tablet?
Thanks in advance!
Click to expand...
Click to collapse
Try Tasselhofs rootscript at mediafire.com/?2jt4ft8xpfzyw2g
But in section :root I used this code:
Code:
adb root
adb shell "chmod 777 /system/local/tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb shell "echo \"ro.kernel.qemu=1\"> /data/local.prop"
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb remount
adb shell "chmod 777 /system/bin"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb reboot
It's not necessary to use any other options than 1. and 2.
After that install Titanium Backup and check for errors and let TB fix it (Some permissions seems to be "broken".).
snapon said:
Try this site slatedroid.com/blog/85/entry-96-aokp-cm9-cm10-installation-guide-for-ampe-a10-sanei-n10/
Click to expand...
Click to collapse
You cannot use this CM9/10, i'ts only for Allwinner A10 CPU!
For now, I didn't found a working recovery.img for MSM8625.
It worked fine, thank you very much! :good:
One problem still exist: the build.prop file still cannot be edited, is write-protected.
---------- Post added at 10:24 PM ---------- Previous post was at 10:18 PM ----------
snapon said:
...I found the original firmware here 86pp.com/download_view.asp....
I think the firmware can also be found here: szampe.com/support_down.asp? but as its all in Chinese its difficult to tell
Click to expand...
Click to collapse
It was deleted from the first site.
On the second site, more specifically from here, you can download the firmware (version 3 Nov, 2012), but I am afraid that everyting is in Chinese.
....
W3sti said:
Try Tasselhofs rootscript at mediafire.com/?2jt4ft8xpfzyw2g
But in section :root I used this code:
Code:
adb root
adb shell "chmod 777 /system/local/tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb shell "echo \"ro.kernel.qemu=1\"> /data/local.prop"
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb remount
adb shell "chmod 777 /system/bin"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb reboot
It's not necessary to use any other options than 1. and 2.
Hey in root you used the following commands means???how??
i have ordered this tablet and will reach me soon i think,i have the tasselhoof rootscript but it is as follows rite?
option 1 is to check the connection
option 2 is to root.
Then after choosing option 1 did you choosed option 2 or did something else???
can you explain briefly please??
Any help will be great...
Click to expand...
Click to collapse
I did root on my Sanei N10 3G Dualcore, but now I cannot find any recovery.img for CWM, can i use the one from single or quad core sanei N10 device?
I want to make a backup (nandroid) so waht can I do?
Thanks in advance
scotty2000 said:
I did root on my Sanei N10 3G Dualcore, but now I cannot find any recovery.img for CWM, can i use the one from single or quad core sanei N10 device?
I want to make a backup (nandroid) so waht can I do?
Thanks in advance
Click to expand...
Click to collapse
You cannot use an other image. For now it's not possible to use nandroid. Try "Titanium Backup Root" for a most complete backup.
---------- Post added at 08:47 PM ---------- Previous post was at 08:40 PM ----------
h.d.modi said:
...
Hey in root you used the following commands means???how??
i have ordered this tablet and will reach me soon i think,i have the tasselhoof rootscript but it is as follows rite?
option 1 is to check the connection
option 2 is to root.
Then after choosing option 1 did you choosed option 2 or did something else???
can you explain briefly please??
Any help will be great...
Click to expand...
Click to collapse
1. Edit the script, replace the code in section ":root", save the file and execute the script
2. Check the connection with option 1 and choose option 2 to root
3. If you don't know what i explained, ask somebody who knows a bit about batch-programming
its worked for sanei n10 dual core 3g tablet pc Thank you !
W3sti said:
You cannot use an other image. For now it's not possible to use nandroid. Try "Titanium Backup Root" for a most complete backup.
Click to expand...
Click to collapse
Thanks!
Is it possible to create an image out of an other one in an easy way and what do i need to do this?
Or is it to much complicated to work out an recovery image?
I am not really firm with those android things but willing to learn if possible with a "how to guide" for building recovery images
Worked great on Ampe A10, 5min job!
Any news about Android 4.1.x update/rom? Cyanogenmod? Any way to get Jellybean?
Tried to find a way to get jelly bean but i think there isn't any...
BTW, does anyone know SNES emulator that works with this tablet?
Note to moderation team: I wanted to post my contribution directly into the author's thread but I'm not allowed to do so.
If my post is right, maybe you could merge my post with the original discussion.
Hi everyone,
I'd like to to provide my feedback regarding the following tool written by Bin4ry.
Tool is available here:
http://forum.xda-developers.com/showthread.php?t=1886460
First of all, I'd like to thank Bin4ry for his job, because with the help of his tool, I have successfully rooted my noname (*) tablet, running ICS 4.0.4.
However, it did not work out at the very first try: the tool said everything went fine but after reboot, my tablet was still not rooted.
Actually, I entered the guts of Bin4ry's script, and find out this trick.
The original script contains this section:
Code:
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe 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"
GOTO FINISH
Actually, I think that the command "/data/local/tmp/busybox" is missing at some locations.
So I rewrote the script as follows and got my tablet rooted !!
Code:
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/data/local/tmp/busybox mount -o remount,rw /system"
stuff\adb.exe shell "/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk"
stuff\adb.exe shell "/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox"
stuff\adb.exe shell "/data/local/tmp/busybox chown 0.0 /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 06755 /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 655 /system/app/Superuser.apk"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 755 /system/xbin/busybox"
stuff\adb.exe shell "/data/local/tmp/busybox rm /data/local.prop"
stuff\adb.exe shell "/data/local/tmp/busybox reboot"
GOTO FINISH
Note: I'm typing from memory because sadly, I erased my own modified file hope I'm not typing too much stupid things because my memory might play me some tricks. But the general idea is here.
Said differently, I simply added the command "busybox" before "chmod" and "chown" commands.
Don't ask me why but it did work. Actually, I discovered this trick by typing the aformentionned commands one a time and find out that simply chmoding a file did not actually change its properties.
I did not rewritte the entire script, but it might be necessary to add the "busybox" command prior to any other "chmod" or "chown" commands (in the ":RICSTUFF" for instance. My tablet did not require to enter this section so I did not bother modify it).
Hope this trick will help someone. If someone finds out it solves its issue, it might be useful to modify Bin4ry's script in a next version of the tool.
(*) more precisely, my tablet is a Finetech by Akor, model TG166.
Want to try to use this method to root Docomo P-02E but something concern.
If rooting is not success, it must be kept unrooted. But will it brick the phone?
Thank you and regards,
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.