Original post can be found [HERE] [HERE] and [HERE]
Standard disclaimer applies. I am not forcing you to follow this guide or any part thereof you are responsible for anything that you do.
If you find this useful hit the thanks button so I have a reason to keep on keeping on
Thanks to kedriastral, P3Droid, RealBBB, CellZealot, swc2001, Daybreak, and darkstarsinner
From what I hear the 901 radio provides the Bionic with much better reception and will help to alleviate the data drops that are so frequent to many of us. I take no credit for this guide it is more of an extension of the original post.
1) you will need are the drivers.
Bionic 32bit Windows v5.4.0
Bionic 64bit Windows v5.4.0
2) DO A NANDROID3) Proceed with RISK. Proceed with fully charged battery. [this can't be stressed enough, I now have a spare battery and wall charger]
4) Download this Bionic Path Saver 1 Click and unzip it.
5) Navigate into the unziped folder and double click on runmebbb.bat at this point you can follow the script output to see what and when to do it.
[*] Motorola universal root script (Windows version)
[*] by P3Droid * ROOT FIX BY BBB
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to continue after you have changed your USB Mode to Charge Only.
..
Press any key to continue . . .
[*]
[*] Pushing the update zip file to your sdcard...
[*] Do not wipe data or cache...
[*] Pushing 5.5.893...
4412 KB/s (57116385 bytes in 12.641s)
[*] Pushing 5.9.901...
4372 KB/s (59018834 bytes in 13.180s)
[*] Rebooting phone to bootloader...
[*] Press enter to continue if both files pushed to sdcard without an error...
[*] If either file failed to push to device disconnect phone and exit this windo
w...
Press any key to continue . . .
[*] Fastboot flashing needed partitions...
< waiting for device >
sending 'system' (262144 KB)... OKAY [ 18.417s]
writing 'system'... OKAY [ 25.072s]
sending 'system' (229120 KB)... OKAY [ 16.082s]
writing 'system'... OKAY [ 21.371s]
sending 'preinstall' (262144 KB)... OKAY [ 18.110s]
writing 'preinstall'... OKAY [ 23.763s]
sending 'preinstall' (49152 KB)... OKAY [ 3.351s]
writing 'preinstall'... OKAY [ 4.253s]
sending 'webtop' (262144 KB)... OKAY [ 18.132s]
writing 'webtop'... OKAY [ 23.355s]
sending 'webtop' (262144 KB)... OKAY [ 18.196s]
writing 'webtop'... OKAY [ 23.174s]
sending 'webtop' (262144 KB)... OKAY [ 18.215s]
writing 'webtop'... OKAY [ 23.532s]
sending 'webtop' (262144 KB)... OKAY [ 18.394s]
writing 'webtop'... OKAY [ 23.161s]
sending 'webtop' (262144 KB)... OKAY [ 18.860s]
writing 'webtop'... OKAY [ 23.193s]
sending 'webtop' (54016 KB)... OKAY [ 3.736s]
writing 'webtop'... OKAY [ 4.966s]
[*] Rebooting phone...
rebooting...
[*] Rebooting the Phone <------------------| At this point you have to manually boot the phone up by pressing power to turn it off then press and hold vol U+D and power, select normal boot to continue
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
804 KB/s (23056 bytes in 0.028s)
[**] 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 ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000161e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40122cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd19807 0xafd397f7
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
error: device not found
[*] Waiting for phone to reboot.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Attemping persistence...
remount succeeded
1455 KB/s (22364 bytes in 0.015s)
3567 KB/s (1994516 bytes in 0.546s)
3644 KB/s (843503 bytes in 0.226s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Installing 43v3r Root...
2 KB/s (1501 bytes in 0.528s)
[*] Rebooting...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Installing 5.5.886 BOOT...
3730 KB/s (8388608 bytes in 2.196s)
16384+0 records in
16384+0 records out
8388608 bytes transferred in 9.336 secs (898522 bytes/sec)
[*] Your phone will now restart in recovery, you will need to manually select th
e update893.zip from the menu and install. <------------------| like it says here you have to manually select the update, the recovery screen just looks like a box with a droid until you press the volume keys
[*] If you want to test 5.9.901 install the update901.zip right after you instal
l the update893.zip.
[*] All Done!
Press any key to continue . . .Once all this has been done you can go ahead and check out the 901 patched ROMS.
Just for good measure you should wipe data, cache, dalvik, and format system for all ROMS.
Eclipse V2.0 (.901 Patched)
KINETIX_V1.0_Final SIGNED (.901 OTA Compatible)
Liberty (.901 OTA Compatible)
If you run into problems you should be able to find everything that you need [HERE] if you do use this method the batch file that is included is incomplete, use the one from this post or you will still be BRICK [HERE]
superuser is installed but no root permissions. ROM manager and root checker from the market verified... It appears this method will install superuser but not root privileges.
Decay78 said:
superuser is installed but no root permissions. ROM manager and root checker from the market verified... It appears this method will install superuser but not root privileges.
Click to expand...
Click to collapse
It does root the phone in the .886 stage however once you have updated to .893 you need to rerun the FOR3V3R root hack again in the R3l3AS3D package. At this time use Bionic Bootstrap and put on your CWM Recovery.
After this you will need to Re-boot back into Stock Recovery and flash the .901 update. Once this has been achieved you will have .901 and root will stay.
swc2001 said:
It does root the phone in the .886 stage however once you have updated to .893 you need to rerun the FOR3V3R root hack again in the R3l3AS3D package. At this time use Bionic Bootstrap and put on your CWM Recovery.
After this you will need to Re-boot back into Stock Recovery and flash the .901 update. Once this has been achieved you will have .901 and root will stay.
Click to expand...
Click to collapse
I am stuck on the flash-boot screen nothing is working can someone please help me with better steps to follow
can install the .901OTAzip but then..
the phone reboots and the radio never comes up. I've done it three seperate times (formatted phone, cache, etc.. just to be safe) and it gets to the 'touch android' screen. However the circle with the slash (no radio) remains. It just sits there and says this may take a few minutes blah blah. ANyway I got safely back to .894. wondering if anyone else is having this issue trying to apply the 901ota.zip file
is there an alternate download link for that radio? the megaupload link isnt bionic friendlyy(yes, trying to download directly from phone).
ok so i downloaded this and am already rooted, do i just double-click the " moto-fastboot.exe " file ?
all i really want to do at this point is just update to the new radio
---------- Post added at 12:13 PM ---------- Previous post was at 11:52 AM ----------
alright well, since there weren't instructions here i read on another forum that you have to double-click that 'runmebbb.bat' file. everything seems to be progressing along now although my battery was at 70% when i started so hopefully everything still finishes ok.
ok so i am not rooted running .893 what file do i need to download in order to get on the .901 ??
and is the difference as good as everyone claims that it is
I already did this & got 901. Currently have 'safestrap' installed & running Eclipse. the original OS i accidentally wiped & did not make a backup. Now, if i disable 'safe strap' & try to boot up it just stays at the boot animation and won't do anything else.(but with safe boot enabled, it will boot into eclipse just fine)
If I re-run this all over again will it restore the original OS?
All you need to do is moto-fastboot the system.img and it should work again, but yes rerunning this or using the RSD Lite method with the full FXZ for 5.5.893 will return you to stock again.
That is what these files and methods are intended to do...revert to a completely stock configuration from any modified build. There are some things that cannot be reverted still, like the cdt.bin., so if you go to 5.9.901 then you will need to use that cdt.bin file after reverting with the path saver of the FXZ.
It.s very important to understand how all this works prior to Modding and flashing anything so you know what your options are and you are prepared for unforseen problems.
Otherwise you might end up in a situation where you believe you have to return a device that you destroyed under warranty.
HELP, update did not work phone stuck in boot loop
I just tried to apply this update and it fails at the Webtop flash part of the script. The command is "moto-fastboot flash webtop grfs.img" and it fails with "load_file: could not allocate 1397489664 bytes error: cannot load 'grfs.img'". I have seen other users with this error, but have not found a fix. I know it has nothing to do with the phone itself because I can produce this error with the phone disconnected, but when I run "moto-fastboot flash preinstall preinstall.img" it WAITS for the phone to connect. I then thought maybe the grfs.img file was corrupted and downloaded the ZIP from mydroidworld, but I still have the same issue. The phone is now stuck in a boot loop. How can I fix this?
Terror_1 said:
Original post can be found [HERE] [HERE] and [HERE]
Standard disclaimer applies. I am not forcing you to follow this guide or any part thereof you are responsible for anything that you do.
If you find this useful hit the thanks button so I have a reason to keep on keeping on
Thanks to kedriastral, P3Droid, RealBBB, CellZealot, swc2001, Daybreak, and darkstarsinner
From what I hear the 901 radio provides the Bionic with much better reception and will help to alleviate the data drops that are so frequent to many of us. I take no credit for this guide it is more of an extension of the original post.
1) you will need are the drivers.
Bionic 32bit Windows v5.4.0
Bionic 64bit Windows v5.4.0
2) DO A NANDROID3) Proceed with RISK. Proceed with fully charged battery. [this can't be stressed enough, I now have a spare battery and wall charger]
4) Download this Bionic Path Saver 1 Click and unzip it.
5) Navigate into the unziped folder and double click on runmebbb.bat at this point you can follow the script output to see what and when to do it.
[*] Motorola universal root script (Windows version)
[*] by P3Droid * ROOT FIX BY BBB
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to continue after you have changed your USB Mode to Charge Only.
..
Press any key to continue . . .
[*]
[*] Pushing the update zip file to your sdcard...
[*] Do not wipe data or cache...
[*] Pushing 5.5.893...
4412 KB/s (57116385 bytes in 12.641s)
[*] Pushing 5.9.901...
4372 KB/s (59018834 bytes in 13.180s)
[*] Rebooting phone to bootloader...
[*] Press enter to continue if both files pushed to sdcard without an error...
[*] If either file failed to push to device disconnect phone and exit this windo
w...
Press any key to continue . . .
[*] Fastboot flashing needed partitions...
< waiting for device >
sending 'system' (262144 KB)... OKAY [ 18.417s]
writing 'system'... OKAY [ 25.072s]
sending 'system' (229120 KB)... OKAY [ 16.082s]
writing 'system'... OKAY [ 21.371s]
sending 'preinstall' (262144 KB)... OKAY [ 18.110s]
writing 'preinstall'... OKAY [ 23.763s]
sending 'preinstall' (49152 KB)... OKAY [ 3.351s]
writing 'preinstall'... OKAY [ 4.253s]
sending 'webtop' (262144 KB)... OKAY [ 18.132s]
writing 'webtop'... OKAY [ 23.355s]
sending 'webtop' (262144 KB)... OKAY [ 18.196s]
writing 'webtop'... OKAY [ 23.174s]
sending 'webtop' (262144 KB)... OKAY [ 18.215s]
writing 'webtop'... OKAY [ 23.532s]
sending 'webtop' (262144 KB)... OKAY [ 18.394s]
writing 'webtop'... OKAY [ 23.161s]
sending 'webtop' (262144 KB)... OKAY [ 18.860s]
writing 'webtop'... OKAY [ 23.193s]
sending 'webtop' (54016 KB)... OKAY [ 3.736s]
writing 'webtop'... OKAY [ 4.966s]
[*] Rebooting phone...
rebooting...
[*] Rebooting the Phone <------------------| At this point you have to manually boot the phone up by pressing power to turn it off then press and hold vol U+D and power, select normal boot to continue
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
804 KB/s (23056 bytes in 0.028s)
[**] 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 ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000161e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40122cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd19807 0xafd397f7
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
error: device not found
[*] Waiting for phone to reboot.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Attemping persistence...
remount succeeded
1455 KB/s (22364 bytes in 0.015s)
3567 KB/s (1994516 bytes in 0.546s)
3644 KB/s (843503 bytes in 0.226s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Installing 43v3r Root...
2 KB/s (1501 bytes in 0.528s)
[*] Rebooting...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Installing 5.5.886 BOOT...
3730 KB/s (8388608 bytes in 2.196s)
16384+0 records in
16384+0 records out
8388608 bytes transferred in 9.336 secs (898522 bytes/sec)
[*] Your phone will now restart in recovery, you will need to manually select th
e update893.zip from the menu and install. <------------------| like it says here you have to manually select the update, the recovery screen just looks like a box with a droid until you press the volume keys
[*] If you want to test 5.9.901 install the update901.zip right after you instal
l the update893.zip.
[*] All Done!
Press any key to continue . . .Once all this has been done you can go ahead and check out the 901 patched ROMS.
Just for good measure you should wipe data, cache, dalvik, and format system for all ROMS.
Eclipse V2.0 (.901 Patched)
KINETIX_V1.0_Final SIGNED (.901 OTA Compatible)
Liberty (.901 OTA Compatible)
If you run into problems you should be able to find everything that you need [HERE] if you do use this method the batch file that is included is incomplete, use the one from this post or you will still be BRICK [HERE]
Click to expand...
Click to collapse
Here is the link to the latest Eclipse Rom. This Rom is actually built on .901
It is version (Eclipse 2.1 RC1) Donate to Nitro He is AWESOME!!
I had multiple problems with this update so I put together the method I used to get my phone up and running... enjoy.
http://forum.xda-developers.com/showthread.php?p=21514430
trackie said:
I upgraded to 901 but lost root. I have stock recovery. How do i go back to 893?
Click to expand...
Click to collapse
This site is a gold mine. Fixed my problem. Thanks for the wealth of information and everyone's hard work posting these guides
.901 + safestrap + enabled = no boot
Liberty3 + .901 = boot loop
Fyi thanks rooted on .901 atleast
Sent from my DROID BIONIC using XDA App
Slie said:
.901 + safestrap + enabled = no boot
Liberty3 + .901 = boot loop
Fyi thanks rooted on .901 atleast
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
If you're rooted on .901 all you need is Clockwordmod and Liberty3 2.0 (.901 patched). If you use the normal Liberty3 2.0 ZIP you WILL have issues because it isn't setup to support the .901 radio.
Thanks I double checked that i was using the correct build.
I just don't know why I cant boot with the safe system enabled on stock, or with the custom rom.
I grabbed the patched.901.liberty file again but i have a feeling it will have the same results. I'm stoked i upgraded for this rom. I couldn't go back the the older radio's the newer ones are so much better. So much..
Any suggestions on either issues would be great.
Im on stock rooted(43v3r) .901 and is confirmed.
Sent from my DROID BIONIC using XDA App
Slie said:
Thanks I double checked that i was using the correct build.
I just don't know why I cant boot with the safe system enabled on stock, or with the custom rom.
I grabbed the patched.901.liberty file again but i have a feeling it will have the same results. I'm stoked i upgraded for this rom. I couldn't go back the the older radio's the newer ones are so much better. So much..
Any suggestions on either issues would be great.
Im on stock rooted(43v3r) .901 and is confirmed.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Let me know if you can flash. You definately should be able to...
Okay, so this morning tried it multiple times no go.
Only thing I did different this time was leave the file on my internal sdcard and flash.
All good finally back on liberty,
Thank you a bunch.
.901 + safemode + enabled = Liberty
EDIT: is it supposed to say I'm back on 5.5.886,
Sent from my DROID BIONIC using XDA App
Slie said:
Okay, so this morning tried it multiple times no go.
Only thing I did different this time was leave the file on my internal sdcard and flash.
All good finally back on liberty,
Thank you a bunch.
.901 + safemode + enabled = Liberty
EDIT: is it supposed to say I'm back on 5.5.886,
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Good to hear. I have the same version information, but my radio issues have pretty much gone away. Also, Liberty cannot flash the radio so there is no way it could downgrade it.
all,
after updating my rooted kl7 to la1 I had to reflash using odin (PC) because it did not flash the csc correctly (nullnullnull issue).
trying to root it based on the official thread i end up with
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
1442 KB/s (23052 bytes in 0.015s)
--- correcting permissions
--- executing zergRush
[**] 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 ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
Click to expand...
Click to collapse
Any suggestion what to do to regain root? downgrading will most probably not work due to the CSC issue i had in the first try..
thanks
will try to re-flash.
perhaps that works.
Update:
still no progress with rooting after flashing.
Code:
Press any key to continue . . .
--- pushing zImage
4730 KB/s (8387840 bytes in 1.731s)
--- flashing zImage
/dev/block/mmcblk0p5: cannot open for write: Permission denied
--- cleaning up
--- rebooting
Downgrade, then flash with Mobile Odin. Make sure EverRoot is selected.
Solution
Nah, that did not work.
What worked was this:
* downgrade (kk9 in my case)
* root + cwm
* upgrade to LA1
* again NULL error
* just flash the CSC file via odin
THAT actually did work and kept me root.
help!
hey donblick i have the same situiation as your's as mine is i'm not rooted and i want to get root my version is the same as yours N7000DXLA1 .My problem is also the same when i run the runme.exe after pushing 189 zerlings it says blue flames with hellions. So you said you have solve the problem by downgrading? can you help me how to downgrade? thanks
I ran the runme.bat and everything seemed to run just fine, no errors. after reboot, I'm still at unroot. no SU permissions. BTW, I just want to root, not flash a custom ROM. Sorry I'm posting here. XDA wouldnt' let me add to the current thread about zergrush.
CODE:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 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 any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
720 KB/s (23060 bytes in 0.031s)
--- correcting permissions
--- executing zergRush
[**] 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 ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd193a3 0xafd3908f
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
1222 KB/s (1075144 bytes in 0.859s)
--- correcting permissions
--- remounting /system
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 12380 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.503 secs (2137463 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
694 KB/s (22228 bytes in 0.031s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
1169 KB/s (785801 bytes in 0.656s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
i had the same problem i downloaded super one click and rooted my phone using that method it worked like a charm on the first try
Or you could just unlock it..
superoneclick is easy and quick
http://forum.xda-developers.com/showthread.php?t=803682
Sent from my Nexus One using Tapatalk
Thanks for the advice. I forgot to mention that I tried SuperOneClick as well. It told me that I was already rooted and did I want to run it anyway. I said yes. I tried Root Check Baisc and it said I'm rooted as well. the problem is when I open Terminal Emulation I get a $. If I type SU, I get permission denied. SU binary is up to date.
BTW, I'm primarily doing all this so I can clear dalvik-cache and perhaps move some of my apps to SD. Still can't do that.
If I open ADB shell on my computer, I can change $ to #, but after I reboot phone, it's back to no permissions.
what abt your firmware version? its impossible to root .62. you must downgrade it first to .58. Same was the case with and after downgrading it worked like a charm.
this helped me get there:
http://forum.xda-developers.com/showthread.php?t=1695514
Hello
I was on ROM XXKKA with Root.
I flash the new rom XXLC1 with Mobile ODIN Lite. Now, device isn't anymore root.
Y tried to get root with CF Root en I get
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
865 KB/s (23052 bytes in 0.026s)
--- correcting permissions
--- executing zergRush
[**] 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 ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
---------------------------------------------------------------
We should have (temporary) root now
We will try to flash CF-Root kernel now
Please watch for any errors beyond this point!
---------------------------------------------------------------
Appuyez sur une touche pour continuer...
--- pushing zImage
3341 KB/s (8387840 bytes in 2.451s)
--- flashing zImage
/dev/block/mmcblk0p5: cannot open for write: Permission denied
--- cleaning up
--- rebooting
---------------------------------------------------------------
If all is well, CF-Root should be flashed
Your device should be rebooting now
Please check if you have root and CWM after boot completes!
---------------------------------------------------------------
But after that my devic still Unroot...
Anybody can Help??
Thread closed, double plus wrong section.
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
davidliu21 said:
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Click to expand...
Click to collapse
try this one
that's the one i used....
Try super one click I don't remember how I rooted I can try later maybe I would have to flash it tho
sent from my acidhazard thrill
I rooted m lg thrill with megatron in windows 7. I didnt have any problem. You can try this.
Ok finally ive tried 3 comouters , non of them works all windows 7 and i use a old computer running windows xp. And it works like a charm lol
Sent from my LG-P925 using XDA
I'm glad ya got it working, but it should of worked fine on win7. Ive been on 7 sense it came out and use nothing else.
davidliu21 said:
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Click to expand...
Click to collapse
Spent hours and hours spread across many days trying to find out what happened. All you need to do is hard reset your phone and take out Micro SD card. Restart your computer to eliminate any usb driver conflicts (don't really need to do this step but you never know). Then run megatron_windows.