I don't know am I lucky or something.
Story: I manually update from 2.3.3 (with supercurio kernel) to stock 2.3.4.
OH NO!!! Low contrast comes back.
I tried some method to root the phone in order to use ROM manager (clockworkmod) but I got no success, but I did an experiment to flash the kernel using adb (I flash netarchy kernel extracted from this package http://forum.xda-developers.com/showthread.php?t=936219 ) with the following command:
cd\
cd (your adb tools location)
fastboot flash boot netarchy.img (make sure you copied the kernel to that directory to avoid hassle)
After that, I tried to run superoneclick 1.9.1 http://forum.xda-developers.com/showthread.php?t=803682 again using GingerBreak and this time it's working!!! (I was prompted to install busybox during root process).
After I restarted the phone, it's really rooted (I can use ROM manager and Root Explorer) and I run ROM manager again to flash clockworkmod and reboot to recovery. I picked this package to flash http://forum.xda-developers.com/showthread.php?t=949292 (get stock 2.3.4 version).
When you are in recovery, choose install zip package and MAKE SURE YOU TOGGLE SIGNATURE CHECK to bypass, and flash the James Bond kernel as well as other drivers.
Now my NS got "old color/contrast" and rooted. YAY!!!
Here is the log:
Code:
SuperOneClick v1.9.1.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
2.3.4
OK
2.3.4
Pushing GingerBreak...
1264 KB/s (16830 bytes in 0.013s)
OK
chmod GingerBreak...
OK
Running GingerBreak...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
OK
Waiting for device...
OK
Running GingerBreak...
ROOTED
Pushing busybox...
3305 KB/s (1062992 bytes in 0.314s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/platform/s3c-sdhci.0/by-name/system
OK
Remounting system with read-write access...
OK
Pushing su-v2...
693 KB/s (26264 bytes in 0.037s)
OK
chmod su...
OK
Pushing Superuser.apk...
2369 KB/s (196521 bytes in 0.081s)
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Checking for busybox
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Don't forget to reboot!
note: my NS is OEM unlocked
Will this work on my Nexus S running 2.3.4? About Phone Info shows the following:
Baseband Version = i9020XXKD1
Kernel version 2.6.35.7-ge382d80
[email protected] #1
Build number = GRj22
The boot loader is already unlocked.
Thanks in advance!
Anubis2k12 said:
Will this work on my Nexus S running 2.3.4? About Phone Info shows the following:
Baseband Version = i9020XXKD1
Kernel version 2.6.35.7-ge382d80
[email protected] #1
Build number = GRj22
The boot loader is already unlocked.
Thanks in advance!
Click to expand...
Click to collapse
It should work with i9020 as well. The only difference is for T-Mobile US (as long as 3G is 900/AWS/2100).
It's funny, I didn't like the fixed colors Google did to the Nexus S in 2.3.3 and higher but oh well and I got used to it... Then I was trying out some kernels (netcharty, etc.. that has "fixed" colors)...and it was back to the old way before Google fixed it.... and man holy cow, it's horrible. I can clearly see now how people were saying the original Nexus S colors were REALLY BLUE. heh.
Related
I am no noob when it comes to rooting- I've had my D1 and Incredible both rooted manually.
However, I'm having some serious problems rooting the DroidX...
I have all the drivers and ADB software installed. This is the 3rd computer i've tried this on and i've been receiving the same errors.
Droid X
Froyo 2.2
1) when i try to adb push exploid to /sqlite_stmt_journals/exploid - i received an error message that says that there is no such file or directory.
instead i adb pushed exploid to /data/local/tmp - and went on from there.
2) I'm able to run ./exploid and even get to the rootshell- but then when i try to cp /sdcard/Superuser.apk /system/app/Superuser.apk - an error occurs that says /sdcard/Superuser.apk is a directory (not copied)
3) I also tried running the 1-click root for the DX - and it fails every time.
I'm completely stuck. Any ideas?
The Answer
To problems one: Where are you getting your information on how to root the X?
To problem two: Did you remember to mount the system to read-write (rw)? And to problem three: Try using this instead, if your on the official OTA of 2.2 FroYo, GO HERE!!!
The link above is what you need and it is the first post on the page.
Good Luck
-Cameron
*edit*
Apparently I'm not allowed to post links...
rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
*end*
got it
yeah i forgot to mount the system- started getting "read-only" errors- the rooting instructions that i was reading seemed to have left that out... :-/
Okay, so I put my Atrix in USB debugging mode, and set it for Windows Media Sync.
This is the SuperOneClick log:
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
1339 KB/s (585731 bytes in 0.427s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
1249 KB/s (1062992 bytes in 0.831s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mmcblk0p12
OK
Reading OS Version properties...
Version: 2.2.1
OK
Remounting system with read-write access...
OK
Pushing su-v2...
1165 KB/s (26264 bytes in 0.022s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1511 KB/s (196521 bytes in 0.127s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Click to expand...
Click to collapse
When I run Root Checker, I have Busybox installed correctly, but no root. I also have the SuperUser app.
Well when I did it, I didn't have it set to that, rather to the "none" setting.
After rooting, reboot the phone and see if you have super user. After confirming that, go back to the program and aacheck the install nonmarket apps.
Rooted/ROM Captivate
Rooted Atrix
FLAC Vest said:
Well when I did it, I didn't have it set to that, rather to the "none" setting.
After rooting, reboot the phone and see if you have super user. After confirming that, go back to the program and aacheck the install nonmarket apps.
Rooted/ROM Captivate
Rooted Atrix
Click to expand...
Click to collapse
Haha, that was it. Setting it to 'none', and then doing it worked for me
My issue was that the root was successful but busy box wasn't installed.
couldn't you install TiBu and install busybox through it? I did that and Busy box was there.
First do a Shell Root then after temporary root has been attained, click Root.
Oh and you might want to disable Development mode.
After that, go ahead and Enable Non-Market Apps while you're in the client.
Should be golden.
I am having issues trying to get my phone rooted.
I have followed tutorial on theunlockr.com. I have created my goldcard as indicated. But when I try to update the phone with the provided sappimg.zip it gives me wrong model ID. It tells me that try creating the goldcard again, and it doesn't work.
I have even tried to do the clockworkmod tutorial with superoneclick method and that does not work. Can someone assist me in getting this to work? What I'm looking for someone to do is to spend some time helping me. Is there a different way to get this working?
I have also tried 3 different goldcard's.
OS version 2.2.1
Does have 3.5mm Jack
I realize that I need to get that sappimg to install before I get that SPL and radio changed.
Have you tried this: http://forum.xda-developers.com/showthread.php?p=10824837#post10824837
?
Sent from my Sapphire/dream using XDA App
Did you not read my post? I stated that the superoneclick option does not work.
I will root phone but will not do the su test. I get error:
Running psneuter...
ROOTED
Pushing busybox...
1186 KB/s (1062992 bytes in 0.875s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock3
OK
Reading OS Version properties...
Version: 2.2.1
OK
Remounting system with read-write access...
OK
Pushing su-v2...
failed to copy 'E:\Phone\SuperOneClickv1.7-ShortFuse\su-v2' to '/system/bin/su': No space left on device
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
cp: write error: No space left on device
OK
Pushing Superuser.apk...
failed to copy 'E:\Phone\SuperOneClickv1.7-ShortFuse\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Pushing Superuser.apk... (/data/app)
877 KB/s (196521 bytes in 0.218s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
ro.product.brand=tmobile
ro.build.date.utc=1291961525
ro.product.model=T-Mobile myTouch 3G
ro.build.date=??? 12??? 10 14:12:05 CST 2010
ro.build.version.codename=REL
ro.build.tags=release-keys
ro.com.google.clientidbase.vs=android-hms-tmobile-us
ro.com.google.clientidbase=android-tmobile-us
ro.product.name=htc_sapphire
ro.product.device=sapphire
ro.build.type=user
ro.build.host=HPA004
ro.build.version.sdk=8
ro.build.display.id=FRG83D
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.build.id=FRG83D
ro.build.version.release=2.2.1
ro.build.user=
ro.build.version.incremental=300801
btw I have the newer radio 2.22.28.25 and SPL 1.33.0013 <---- perfected SPL
Try rooting with gingerbreak. Or root manually using gingerbreak, rageagainstthecage, or killinginthenameof. Try with the gingerbreak apk first, and if that fails cone back and ill give you different instructions
I have tried gingerbreak on the phone manually installing. It reboots, but no superuser on phone.
I have tried superoneclick v.1.7 and 1.9.5 with rageagainstthecage and gingerbreak. It says it roots but I get the sending "su" command and fails. It states that device is full error too as you see in the post.
SAPPHIRE PVT 32A Ship S-ON G.
I have created a goldcard right but when I try to install the SAPPIMG.zip it tells me incorrect MODEL ID. From where I read you have to get the ENG SPL on this first. I also read that 2.2.1 update has locked to bootloader.
zelda26 said:
I have tried gingerbreak on the phone manually installing. It reboots, but no superuser on phone.
I have tried superoneclick v.1.7 and 1.9.5 with rageagainstthecage and gingerbreak. It says it roots but I get the sending "su" command and fails. It states that device is full error too as you see in the post.
SAPPHIRE PVT 32A Ship S-ON G.
I have created a goldcard right but when I try to install the SAPPIMG.zip it tells me incorrect MODEL ID. From where I read you have to get the ENG SPL on this first. I also read that 2.2.1 update has locked to bootloader.
Click to expand...
Click to collapse
Gingerbreak the app or the binary the app uses to root?
If the app doesn't work then I would try going to c-skills.blogsot.com and downloading gingerbreak or killinginthenameof and rooting manually (run exploit. Push su, install superuser)
Also it could be possible that it ran out of space for the superuser app. Try installing it from the market and see if it works
Also, the website is just from memory, could be wrong. If it is then go googleing
I tried gingerbreak the apk, and I have tried the gingerbreak from the superoneclick method. I will try this other one. Thanks for the help.
zelda26 said:
I tried gingerbreak the apk, and I have tried the gingerbreak from the superoneclick method. I will try this other one. Thanks for the help.
Click to expand...
Click to collapse
Try doing it manually (from adb shell or a terminal emulator on the phone)
Run the exploit. Remount system rw. Push su. Install superuser from market
going to need some help on that one. If you dont mind.
zelda26 said:
going to need some help on that one. If you dont mind.
Click to expand...
Click to collapse
Sure. Just tell me what part you need help with
Two ideas.
Use superoneclick to get shell root then push su via adb. Then install superuser from the market.
Or downgrade to 1.6 and root via universal androot
That sounds like an easier way. I will try yours. I'll have to look around how to downgrade to is that cupcake or donut?
Is there someone that is willing to IRC chat with me to get it done? Im running into the issue that it says that device is full.
Is there anyone willing to assist me? Or me to send the phone to to root with AMON-RA Im willing to paypal $20 to do it. This phone is a piece of junk without it being rooted. I dont have money for a new phone at this time. I will in the next couple months.
Update: I have now also made a Linux port for DooMLoRD's rooting of ICS phones.(Sony Xperia only)
Please see attached file: Xperia-2011-ICS-ROOT-emu-Linux.zip
Note: You need flashtool for linux. Procedure remains the same as for windows.
Original script thread: http://forum.xda-developers.com/showthread.php?t=1601038
Rooting procedure: http://talk.sonymobile.com/thread/41119?start=0&tstart=0
Please update Superuser app as well as SU binary to the latest version after rooting is done successfully.
Update: Updated as per DooMLoRD's v4.0 script with zergRush binary of 21 Nov 2011 and with makespace which deletes Google Maps if there is not enough space.(< 6MB).
Hello
I am completely new to Android but not at all new to Linux.
I used paxchristos script (ran commands manually though) to root my Sony Ericsson Live with Walkman. (WT19i / Android 2.3.4 / Build 4.0.2.A.0.58)
Source threads used:
http://forum.xda-developers.com/showthread.php?t=1319653
http://forum.xda-developers.com/showthread.php?p=18615502
In an attached file, I fixed/modified/added few things in paxchristos script. Here is the detail:
1) Fixed error in symlinking su. (source/destination were same)
2) Don't delete (and recreate) /data/local/tmp/ directory unnecessarily, just delete its contents.
3) Create /data/local/tmp if it does not exist.
4) Uses dd instead of cp (because DooMLoRD's script does, dont know why!). Update: as per anantshri, dd is used because cp has been known to give errors.
5) If your system already has 'adb' then it uses system 'adb' instead of one in zip-archive.
6) Updated zip archive to contain the latest files from DooMLoRD's archive (paxchristos archive seemed old)
Please try/verify and let me know if I missed something.
Thanks.
Very nice to know that fellow *nixers are on xda.
Thanks, I am still getting used to this forum.
Have already found answers to many of my questions regarding Android.
One thing that shocked me is Android uses Java and not C. I would have preferred C anyday.
ohk so few things
1) yes java is used mainly in Android, However look at NDK if you are a C fan.
2) dd command is used in scripts to avoid cp related issues. coz last i remember we encountered multiple errors based on scenarios where cp used to fail but dd used to work. so dd is defacto there.
@doomLord, Correct me if i am wrong.
Ah that clears dd confusion. Till now I was wondering why he chose dd? I thought may be because dd was faster for internal memory to internal memory transfer.
Since DooMLoRD is good programmer I knew there has to be a reason. And that is why I changed paxchristos script to use dd.
Updated to match with DooMLoRD's v4 script. See update on first post for details.
Just used this script on my Galaxy S 2 Skyrocket. Worked great!
Have used the script with Sony Ericsson Xperia Mini E10a Latin America.
Script runned, ADB found the device, device has rebooted correctly but... no root after reboot. Checked with Root Checker from Market.
Anyway, great script! Should work for some models.
On my phone (Milestone 2 with Gingerbread 2.3.6) the root process worked, but part of the space check it returns 90% of free space, the software does not correctly identify and delete my google maps. The following screen to evaluate and correct the bug. And congratulations for the initiative, I'd have to do it by hand when I found your script ready.
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
This script has been ported by paxchristos and modified by amish
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable 'USB DEBUGGING'
from (Menu\Settings\Applications\Development)
(3) enable 'UNKNOWN SOURCES'
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip 'PC Companion Software' prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
PRESS ENTER WITHIN 120 seconds TO CONTINUE OR ctrl-c to cancel
--Starting---
---Killing the adb server to make sure that there are no problems---
---Waiting for Device---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
---Cleaning out any previous zergRush attempts---
mkdir failed for /data/local/tmp, File exists
rm failed for /data/local/tmp/*, No such file or directory
---Pushing zergRush---
531 KB/s (23060 bytes in 0.042s)
---Fixing permissions for zergRush---
---Running zergRush---
If it gets stuck here for a long time then try:
1)disconnect usb cable and reconnect it
2)toggle 'Usb Debugging' (first disable it then reenable it)
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000151e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x4011ccd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd19413 0xafd3925f
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
---Waiting for Device---
---Pushing busybox---
2011 KB/s (1075144 bytes in 0.522s)
---Fixing busybox permissions---
---remounting system---
---checking free space on /system---
10 KB/s (439 bytes in 0.040s)
--- Free space on /system : 90% bytes
test: 90%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
---copying busybox to /system/xbin---
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.084 secs (12799333 bytes/sec)
---fixing ownership and permissions---
---installing busybox---
---cleaning up---
---pushing SU binary---
546 KB/s (22228 bytes in 0.039s)
---correcting ownership and permissions for SU---
---correcting symlinks---
---Pushing Superuser app---
2160 KB/s (785801 bytes in 0.355s)
--cleaning---
---rebooting---
---All done, your Xperia has been rooted by DooMLoRD---
---This script has been ported by paxchristos and modified by amish!!---
---If have any questions, feel free to email me @ [email protected]---
Umm.... Freespace checking script was not developed by me. I have copied it directly from DooMLoRD script AS IS (had not tested it either). I think we dont need it anyway. It will be very rare that person rooting wud have run out of space. Person can re-install Google Maps (so no big harm done by bug)
But when I get the time I will check the DooMLoRD's script if there exist a bug.
Please click on THANKS if u liked my script
Your script has saved me a lot of work, because I'm tired of borrowing the notebook of my wife for flashing my phone and was looking for solutions for linux, missing root can do, I do not want to use SuperOneclick (did not want to install it just for Mono ) and go on to adapt the script DoomLord for Linux, which you did very well done. Now I can do everything on my computer with linux, what about the bug, I realized that the program was part of the original script, but I made a warning to those who wish, like me, deactivate the check room not to lose Google Maps (or have to reinstall the Market).
adb drivers in linux ?
Hy ! Can I use this script to root my Galaxy Note ? And can you say me how to install adb drivers in linux, plz ?
Just try it.
ADB is already there with script.
If you have fedora then u can install adb by running:
yum install android-tools
OK
Thank you, i will try. I didn't realize that "ADP" is the same as "ADP drivers".
well in linux there is nothing like drivers u can say
very few hardware require driver.
and when android itself is born from linux, linux shud already have support for it
Everything went well, thank you very much! We should just specify the need to execute the file "runme-linux" as root (with "sudo") ;-).
I would not to abuse, but would it be possible to have the same thing for unroot, please ?
Easy unroot for linux
Hy,
I used Amish translation to do the same for the DooMLoRD's Unrooting Script. I succesfully tried it with my phone, but REMEMBER YOU ARE DOING THIS AT YOUR OWN RISK (I suppose you know this song ;-))
DooMLoRD's instructions :
so here is the unrooting script to be USED ONLY AND ONLY IF U HAVE USED MY FILES (Easy Rooting Toolkit) FOR ROOTING
[ WARNING ]
if u have used any other way/solution for rooting then PLEASE DO NOT RUN THIS... you MIGHT END UP with damaged system...
(thats cause some ppl create symlinks for busybox in /system/bin/ which wipes out stock symlinks to /system/bin/toolbox and breaks/damages system)
More informations here http://forum.xda-developers.com/showthread.php?p=18615502 and here http://forum.xda-developers.com/showthread.php?t=1329360
I havent unrooted but I think unrooting wud be nothing but removing busybox symlinks (and busybox itself) and removing su binary and superuser.apk.
btw there is no need to run "runme-linux" as super user.
it works as normal user (recommended)
amishxda said:
btw there is no need to run "runme-linux" as super user.
it works as normal user (recommended)
Click to expand...
Click to collapse
If I run the script without sudo, the script block just after "* daemon started successfully *"
You can see below the console log :
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
This script has been ported by paxchristos and modified by amish
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable 'USB DEBUGGING'
from (Menu\Settings\Applications\Development)
(3) enable 'UNKNOWN SOURCES'
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip 'PC Companion Software' prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
PRESS ENTER WITHIN 120 seconds TO CONTINUE OR ctrl-c to cancel
--Starting---
---Killing the adb server to make sure that there are no problems---
---Waiting for Device---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
^C [COLOR="Red"](because no reaction after 5 minutes)[/COLOR]
error: protocol fault (no status)
---Cleaning out any previous zergRush attempts---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: insufficient permissions for device
error: insufficient permissions for device
---Pushing zergRush---
error: insufficient permissions for device
---Fixing permissions for zergRush---
error: insufficient permissions for device
---Running zergRush---
If it gets stuck here for a long time then try:
1)disconnect usb cable and reconnect it
2)toggle 'Usb Debugging' (first disable it then reenable it)
error: insufficient permissions for device
---Waiting for Device---
^C
If I run the same script as root (with "sudo"), the script continues without problem.
ive tried cydia impactor superoneclick and spectrum window and bin4ry none of them are working to root the phone
which method currently works to root stock lg e400?
please develop a new method for rooting lg e400
bug 8219321 and 9950697 are being shown as unpatched on this firmware V10L june 7 2013
still no root exploit is working.
Moved here as this does not belong in the Development Section, please read the Forum Rules on posting....
Judge Joseph Dredd said:
Moved here as this does not belong in the Development Section, please read the Forum Rules on posting....
Click to expand...
Click to collapse
thanks this problem has been solved:good:
psychem said:
thanks this problem has been solved:good:
Click to expand...
Click to collapse
Did you root your phone? I can help you if not.
Ckovvi said:
Did you root your phone? I can help you if not.
Click to expand...
Click to collapse
ya i have rooted it
Please tell me how to root it.i have tried all methods my version is v10L.
ragunathan said:
Please tell me how to root it.i have tried all methods my version is v10L.
Click to expand...
Click to collapse
have you tried this?
http://forum.xda-developers.com/showthread.php?p=56495206
Sent from my LG-P705 using XDA Free mobile app
Tried iroot but says no roo permission.
ragunathan said:
Tried iroot but says no roo permission.
Click to expand...
Click to collapse
thats strange it should root your phone with out any problems.
Sent from my LG-P705 using XDA Free mobile app
Screenshot
Bro the only rooting method working with L3 is Superoneclick with Rageagainstthecage (version 1.7)
To run the exploit you must change the exploit engine from pseneuter to rageagainstthecage.All other methods don't work.
Inviato dal mio LG-E400 con Tapatalk 2
I tried the method described above, this one also crashes on looking for device. I got usb debugging on, latest drivers installed and full battery. The phone has the last software, which is V10j-OCT-17-2012. Android version 2.3.6.
I have seen other LGL3/E400 phones rooted, so what am I doing wrong here and how can I actually root my phone then?
Thanks in advance.
410172_Chief
It might just be the software version that is not compitable with the current rooting methods. Is there a way to downgrade my LG L3/E400 to a firmware that is rootable?
With the firmware of my device, 10J, it says E400GO. It is from Vodafone, The Netherlands. Don't know if that information will help but you never know.
So I am trying to root my LG L3 E400GO. Who knows how to do the trick?
Oh my...
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
5 KB/s (5392 bytes in 1.000s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1462 KB/s (1062992 bytes in 0.710s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mmcblk0p14
OK
Reading OS Version properties...
Version: 2.3.6
OK
Remounting system with read-write access...
OK
Pushing su-v2...
2565 KB/s (26264 bytes in 0.009s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
4797 KB/s (196521 bytes in 0.040s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Though it did not reboot at all, I might have just rooted it.
410172 said:
It might just be the software version that is not compitable with the current rooting methods. Is there a way to downgrade my LG L3/E400 to a firmware that is rootable?
With the firmware of my device, 10J, it says E400GO. It is from Vodafone, The Netherlands. Don't know if that information will help but you never know.
So I am trying to root my LG L3 E400GO. Who knows how to do the trick?
Oh my...
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
5 KB/s (5392 bytes in 1.000s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1462 KB/s (1062992 bytes in 0.710s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mmcblk0p14
OK
Reading OS Version properties...
Version: 2.3.6
OK
Remounting system with read-write access...
OK
Pushing su-v2...
2565 KB/s (26264 bytes in 0.009s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
4797 KB/s (196521 bytes in 0.040s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Though it did not reboot at all, I might have just rooted it.
Click to expand...
Click to collapse
Yea it doesn't reboot...i did three phones like that yesterday.
Yes man!You rooted it!
Check for the superuser app in your app drawer.
Inviato dal mio LG-E400 con Tapatalk 2