Database Develop

[Q] REvolution oneclick root help

I was unsuccessful in my search so I am posting my question in this QA forum.
The original thread was in the Revolution Android Development subforum but I am unable to post on that thread as I am a useless noob.
I have a LG Revolution Android version 2.3.4
I followed the directions as posted:
How Do I Root and Install CWM?:
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!!
I unzipped and was able to update drivers
I was sure to have the USB debugging on (before connecting).
I also set the the USB connection to Internet connection
I clicked root.bat and the following line is repeated almost every other line
'adb' is not recoginized as an internal or external command
At the very end it says:
[*] root complete, enjoy!
[*] Press any key to continue..
When I try to open Titanium backup or Barnacle it says I do not have root
A few other things I'm noticing is that I keep getting usb device not recognized when connecting the phone via usb.
I also noticed a LG software upgrade assistant in my PC tray that I cannot remove.
Any help would be greatly appreciated.

With adb not recognized it sounds like you just ran the root.bat without extracting the zip extract the zip to a folder the click on root.bat
Sent from my VS910 4G using xda premium

Yes, I believe I just unzipped the file and clicked the root.bat. Where do I extract the file to?
Thanks for your response.

Doesn't really matter you just need to extract it you can make a new folder and extract to that
Sent from my VS910 4G using xda premium

Beamer, that certainly did the trick.
Confirmed rooted with access to Barnacle and Titanium.
Now I need to figure out the Gingervolt process. Only about 75 more pages to read through.

Lol if you have clockwork mod recovery just download gingervolt put it on your sd card boot into recovery hold power button down and volume down at the same time until you get to the black screen asking to wipe data or something like that hit the power button to confirm this will not wipe your data but will boot into recovery once in recovery use the volume keys to navigate and power button to select then follow all of the directions in the 1st post every step is important.
Sent from my VS910 4G using xda premium

atlsud said:
Beamer, that certainly did the trick.
Confirmed rooted with access to Barnacle and Titanium.
Now I need to figure out the Gingervolt process. Only about 75 more pages to read through.
Click to expand...
Click to collapse
I appreciate you actually reading instead of instantly asking to be spoon fed!

atlsud said:
I was unsuccessful in my search so I am posting my question in this QA forum.
The original thread was in the Revolution Android Development subforum but I am unable to post on that thread as I am a useless noob.
I have a LG Revolution Android version 2.3.4
I followed the directions as posted:
How Do I Root and Install CWM?:
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!!
I unzipped and was able to update drivers
I was sure to have the USB debugging on (before connecting).
I also set the the USB connection to Internet connection
I clicked root.bat and the following line is repeated almost every other line
'adb' is not recoginized as an internal or external command
At the very end it says:
[*] root complete, enjoy!
[*] Press any key to continue..
When I try to open Titanium backup or Barnacle it says I do not have root
A few other things I'm noticing is that I keep getting usb device not recognized when connecting the phone via usb.
I also noticed a LG software upgrade assistant in my PC tray that I cannot remove.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]

AssumedDarkness said:
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?t=1348557

Follow this post, it's as simple as that.
http://forum.xda-developers.com/showthread.php?t=1326542&page=54
It's the easiest to understand for me & worked flawlessly.
Ed

please help
AssumedDarkness said:
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
Click to expand...
Click to collapse
no im coming up with this and im stuck
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory

AssumedDarkness said:
no im coming up with this and im stuck
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
Click to expand...
Click to collapse
Copy and paste the whole thing to pastebin and drop a link in here and I will look at it. That small portion could be normal, I would just have to look at the rest to know for sure.
Sent from my VS910 4G using xda premium

I am trying to root my Revolution 2.3.4 ( I am a complete newb)
How will I know it is rooted?
This is what showed up when it was finished:
Rooting the LG Revolution
Tool Built by mtmichaelson
Exploit Built by the Revolutionary Team
Rooting
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Pushing Zergrush
1279 KB/s (22281 bytes in 0.017s)
Running Zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd255f1 0xafd39067
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
3639 KB/s (22364 bytes in 0.006s)
3778 KB/s (828156 bytes in 0.214s)
2550 KB/s (843503 bytes in 0.323s)
Removing Trash
Finished Rooting!!!
Press any key to continue . . .
Is that normal?
Is there anything else I need to download on the phone to get rid of bloatware? I am not sure really how to do this.
Thanks!

AprilRevo said:
I am trying to root my Revolution 2.3.4 ( I am a complete newb)
How will I know it is rooted?
This is what showed up when it was finished:
Rooting the LG Revolution
Tool Built by mtmichaelson
Exploit Built by the Revolutionary Team
Rooting
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Pushing Zergrush
1279 KB/s (22281 bytes in 0.017s)
Running Zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd255f1 0xafd39067
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
3639 KB/s (22364 bytes in 0.006s)
3778 KB/s (828156 bytes in 0.214s)
2550 KB/s (843503 bytes in 0.323s)
Removing Trash
Finished Rooting!!!
Press any key to continue . . .
Is that normal?
Is there anything else I need to download on the phone to get rid of bloatware? I am not sure really how to do this.
Thanks!
Click to expand...
Click to collapse
You are now rooted, I would install CWM and do a back up before doing anything else though.
Sent from my VS910 4G using xda premium

Do I get CWM from the same file as the root?
If so, I did run the "CWM Recovery" from that file. Is that what you mean?
I also see that I am rooted, I downloaded the titinium backup and was able to uninstall a lot of Verizons app that I never use.
Anything else good to do with a rooted Revo?

Gingervolt it !!!! 2.0 is real good & removes all of the bloat. If you find yourself missing anything from the stock that youo want, get the "Stock app installer" & reload what you want...
\Ed

[FIX] Bionic (Boot FAILURE) & (CDT FAILURE)

Okay so I have noticed that there are still some people out there having issues with either going back from Update .901 or have dropped into a (Boot Failure) mode and cannot find a solution. I have decided to post up what works for me. Mind you I have personally and purposely bricked my Bionic multiple times to ensure that this works. However:
I am in no way responsible for any permanent damage you do to your phone. If you have an issue I will do the best I can to assist as I’m sure the rest of the members will. But you take full responsibility for anything you decide to attempt.
While some of you have been able to use the one click method provided by , some of you can’t follow through with the fix due to the (Boot Failure) or (CDT Failure). I have changed some of the files in the One Click method provided by. These files worked for me multiple times but I cannot gauruntee they will do the same for you. But if you are brave enough giver er hell.
Step One: Download these files. You will need all three if you want to go through to .901. Each update is labeled as such to limit the confusion. Once downloaded move all folders to your desktop and unzip the CDT file ONLY!!!
http://www.megaupload.com/?d=GZ4AC6ML
http://www.megaupload.com/?d=3XE1OFOM
http://www.megaupload.com/?d=TSYCAFP4
Step Two: Plug your Bionic in via USB. Once plugged in you can either boot into Fastboot mode by holding the POWER + VOLUME DOWN. If you are in (CDT Failure) you won’t be able to reach fast boot but that’s okay. In fact “Fastboot” mode isn’t necessary as long as you are in one of these error screens.
Step Three: Open the folder labeled “CDT_BOOT_FIX” and double click “EVERYTHING”. The system will begin running the install of the files contained. ALL FILES SHOULD SUCCEED. Not one of these files should fail and in the event one does please post so we may figure it out together.
Edit: You will need to also download this and place it into the unzipped CDT folder:
Sorry I must have forgotten to add it originally when composing the file.
Step Four: Once the files have finished running, reboot your Bionic. You should now have a running system. YOU ARE NOT FINISHED YET, so please pay attention. Failure to do so will only cause you to go through this again.
Step Five: Move the Update files (893 if you only want to go that far or 893 and 901 to go all the way) to your SD card. Make sure both files are on the root of the SD card. Now shut down your phone.
Step Five: Boot into recovery and choose “Update Zip on SD Card”. Choose the 893 file and click okay. Your phone will now install the 893 update. Reboot. STILL NOT DONE. As noted below if you plan to go to the .901 update then you can skip step six and just flash both the 893 and 901 one right after the other. If only going to 893 then proceed to step six.
Step Six: Your phone will now boot into “CDT Failure”. Make sure your Bionic is plugged into the USB port. Hover your mouse over the “CDT_BOOT_FIX” folder, hold SHIFT and RIGHT CLICK your mouse. A pop-up box comes up. Click “Open Command Prompt Here”. Once the Command Prompt comes up type:
moto-fastboot flash cdt.bin cdt.bin
/\ You can copy and paste this if you would like.
Your phone will now flash the CDT file. It should succeed. Once this is complete you are full OTA 893. You now have the choice of booting into recovery and loading the 901 file should you choose to do so.
That should be it. Thank you to all who have contributed. The scripting for the Everything command came from P3DROID. If you object to me using it please let me know. I appreciate it but the files can be run manually so no biggy. Thanks
If you have any problems feel free to ask

If you are still having problems I will do my best to assist. If it comes down to it download Team Viewer (www.teamviewer.com) and all files posted here. I will then run the repair process for you. Just for some peace of mind Team Viewer is a remote PC control program. It generates a password each time it is opened so it can never be replicated unless you choose to set a password. If at anytime you feel uncomfortable with what's going on you can immediately close Team Viewer and break the connection. If you need help this badly send me a PM and we will set up a time. As it stands now I am on duty from 6 P.M. to 6 A.M. And yes if it helps you any I am a Police Officer in the State of Ohio.

i just unpacked the 901 update and flashed the cdt file from it to get by this problem. took me a few different cdt files to get it right though.

Glad you found a solution. Some people just can't seem to get through this issue. Doing this process will put you back on 893 updatable.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk

I'm having an issue now it wont let me use your recovery img and I have to use one from 893 FXZ rather then yours. but then once I get to recovery it wont let me update to 893 (I guess it thinks I'm already there?) so I'm not sure what to do atm.
I also noticed on your batch file you put "moto-fastboot boot boot.img" it should be "moto-fastboot flash boot boot.img"

Eluvatar said:
I'm having an issue now it wont let me use your recovery img and I have to use one from 893 FXZ rather then yours. but then once I get to recovery it wont let me update to 893 (I guess it thinks I'm already there?) so I'm not sure what to do atm.
I also noticed on your batch file you put "moto-fastboot boot boot.img" it should be "moto-fastboot flash boot boot.img"
Click to expand...
Click to collapse
I apologize and will fix this. Thank you for pointing it out. I also posted a reply to your thread on Rootzwiki.

Hello, first off, I will like to thank for all the help!
Ever since I tried upgrading to 901, I been having a brick for 2 days now.
I read through your post a few times and I am using your method to fix the problem.
You specifically stated, everything should be OKAY. But in my case,
boot.img and recovery both failed.
Any help will be greatly appreciated!
Thank you again for all the help and support!
Gil
Here is a copy of my output:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.008s]
writing 'cdt.bin'... OKAY [ 0.864s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.000s]
Press any key to continue . . .
erasing 'cache'... OKAY [ 0.013s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.008s]
writing 'lbl'... OKAY [ 0.466s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.062s]
writing 'logo.bin'... OKAY [ 0.379s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.008s]
writing 'ebr'... OKAY [ 0.466s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.002s]
writing 'mbr'... OKAY [ 0.404s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.044s]
writing 'devtree'... OKAY [ 0.511s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 17.225s]
writing 'system'... OKAY [ 24.643s]
sending 'system' (229120 KB)... OKAY [ 15.139s]
writing 'system'... OKAY [ 22.028s]
Press any key to continue . . .
downloading 'boot.img'... OKAY [ 0.553s]
booting... FAILED (remote: unsupported command)
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 0.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 0.908s]
writing 'cdrom'... OKAY [ 2.269s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 16.790s]
writing 'preinstall'... OKAY [ 23.150s]
sending 'preinstall' (49152 KB)... OKAY [ 3.175s]
writing 'preinstall'... OKAY [ 4.221s]
Press any key to continue . . .
sending 'webtop' (262144 KB)... OKAY [ 17.211s]
writing 'webtop'......

Can you try manually pushing the boot and recovery images. Some users have reported that the one click want able to do this. Let me know what happens.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk

There is a missing command in the batch file I have.
This below should do what you need it to do, I still have the recovery flashing error though.
ERROR
sending 'recovery' (9216 KB)... OKAY [ 0.663s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )​
Which actually doesn't matter once you can get into a working system.
Contents of the corrected batch file
@echo off
pause
moto-fastboot flash cdt.bin cdt.bin
pause
moto-fastboot reboot-bootloader
pause
moto-fastboot erase cache
pause
moto-fastboot flash lbl lbl
pause
moto-fastboot flash logo.bin logo.bin
pause
moto-fastboot flash ebr ebr
pause
moto-fastboot flash mbr mbr
pause
moto-fastboot flash devtree device_tree.bin
pause
moto-fastboot flash system system.img
pause
moto-fastboot flash boot boot.img
pause
moto-fastboot flash recovery recovery.img
pause
moto-fastboot flash cdrom cdrom
pause
moto-fastboot flash preinstall preinstall.img
pause
moto-fastboot flash webtop grfs.img
pause
moto-fastboot flash radio radio.img
pause
moto-fastboot -w
pause​
The fixed batch file can be downloaded [HERE]

Terror_1 said:
There is a missing command in the batch file I have.
This below should do what you need it to do, I still have the recovery flashing error though.
ERROR
sending 'recovery' (9216 KB)... OKAY [ 0.663s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )​
Contents of the corrected batch file
@echo off
pause
moto-fastboot flash cdt.bin cdt.bin
pause
moto-fastboot reboot-bootloader
pause
moto-fastboot erase cache
pause
moto-fastboot flash lbl lbl
pause
moto-fastboot flash logo.bin logo.bin
pause
moto-fastboot flash ebr ebr
pause
moto-fastboot flash mbr mbr
pause
moto-fastboot flash devtree device_tree.bin
pause
moto-fastboot flash system system.img
pause
moto-fastboot flash boot boot.img
pause
moto-fastboot flash recovery recovery.img
pause
moto-fastboot flash cdrom cdrom
pause
moto-fastboot flash preinstall preinstall.img
pause
moto-fastboot flash webtop grfs.img
pause
moto-fastboot flash radio radio.img
pause
moto-fastboot -w
pause​
Click to expand...
Click to collapse
That is awesome and thank you. As for the Recovery what is your current system info?

darkstarsinner said:
That is awesome and thank you. As for the Recovery what is your current system info?
Click to expand...
Click to collapse
Doesn't matter, once the phone gets to a point where it will boot you can use the 1 click path saver to get things back up and running.

Good deal. Hopefully that will work for everybody. There are so many different errors out there we should compile a list of fixes into one thread to make it a little easier for everyone to find.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk

Hi everybody,
A buddy of mine bricked his bionic by attempting the 901 update with root so I attempted this fix since it was stuck in boot failure. The phone will now boot up but doesn't pull in any service. Am able to connect it to wi-fi, but once you hit the droid to run thru set up, it sits there thinking, telling me, "please wait, this may take a few moments." I attempted going back into recovery and installing the 893 zip and 901 zip and both fail. I've also attempted using rsd lite with the 893 fxz but no dice. Here's what I'm looking at when running the script:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.011s]
writing 'cdt.bin'... OKAY [ 0.564s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.008s]
Press any key to continue . . .
< waiting for device >
erasing 'cache'... OKAY [ 0.039s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.016s]
writing 'lbl'... OKAY [ 0.486s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.162s]
writing 'logo.bin'... OKAY [ 0.309s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.013s]
writing 'ebr'... OKAY [ 0.468s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.398s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.094s]
writing 'devtree'... OKAY [ 0.518s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 81.860s]
writing 'system'... OKAY [ 22.592s]
sending 'system' (229120 KB)... OKAY [ 45.569s]
writing 'system'... OKAY [ 20.132s]
Press any key to continue . . .
sending 'boot' (8192 KB)... OKAY [ 1.674s]
writing 'boot'... OKAY [ 1.139s]
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 1.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 2.443s]
writing 'cdrom'... OKAY [ 2.109s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 46.399s]
writing 'preinstall'... OKAY [ 22.774s]
sending 'preinstall' (49152 KB)... OKAY [ 8.490s]
writing 'preinstall'... OKAY [ 4.404s]
Press any key to continue . . .
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Press any key to continue . . .
sending 'radio' (21768 KB)... OKAY [ 3.661s]
writing 'radio'... OKAY [ 2.052s]
Press any key to continue . . .
Any help would be greatly appreciated! Thanks again for all the hard work that goes into this!

s.dubs317 said:
Hi everybody,
A buddy of mine bricked his bionic by attempting the 901 update with root so I attempted this fix since it was stuck in boot failure. The phone will now boot up but doesn't pull in any service. Am able to connect it to wi-fi, but once you hit the droid to run thru set up, it sits there thinking, telling me, "please wait, this may take a few moments." I attempted going back into recovery and installing the 893 zip and 901 zip and both fail. I've also attempted using rsd lite with the 893 fxz but no dice. Here's what I'm looking at when running the script:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.011s]
writing 'cdt.bin'... OKAY [ 0.564s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.008s]
Press any key to continue . . .
< waiting for device >
erasing 'cache'... OKAY [ 0.039s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.016s]
writing 'lbl'... OKAY [ 0.486s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.162s]
writing 'logo.bin'... OKAY [ 0.309s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.013s]
writing 'ebr'... OKAY [ 0.468s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.398s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.094s]
writing 'devtree'... OKAY [ 0.518s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 81.860s]
writing 'system'... OKAY [ 22.592s]
sending 'system' (229120 KB)... OKAY [ 45.569s]
writing 'system'... OKAY [ 20.132s]
Press any key to continue . . .
sending 'boot' (8192 KB)... OKAY [ 1.674s]
writing 'boot'... OKAY [ 1.139s]
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 1.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 2.443s]
writing 'cdrom'... OKAY [ 2.109s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 46.399s]
writing 'preinstall'... OKAY [ 22.774s]
sending 'preinstall' (49152 KB)... OKAY [ 8.490s]
writing 'preinstall'... OKAY [ 4.404s]
Press any key to continue . . .
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Press any key to continue . . .
sending 'radio' (21768 KB)... OKAY [ 3.661s]
writing 'radio'... OKAY [ 2.052s]
Press any key to continue . . .
Any help would be greatly appreciated! Thanks again for all the hard work that goes into this!
Click to expand...
Click to collapse
I am getting the exact same issue. I am getting errors in the recovery and cant get to the point where i can turn usb debugging on for 1 click path to work. any ideaS?

To those getting stuck at the "push the android" screen and have the recovery error,
you can touch the four corners of the LCD starting from top left and moving clockwise to each corner. This will bypass the android guy and send you to the home screen allowing you to put your device in usb debug mode and push the files through path saver.

MarcMaiden said:
To those getting stuck at the "push the android" screen and have the recovery error,
you can touch the four corners of the LCD starting from top left and moving clockwise to each corner. This will bypass the android guy and send you to the home screen allowing you to put your device in usb debug mode and push the files through path saver.
Click to expand...
Click to collapse
I wish it was that easy but it will not allow me to bypass the android guy. Usually i can click him and skip thru setup then go into settings but when clicking the android guy it just sits there thinking saying please wait, this may take a few minutes, but never gets past that point. Any other ideas?
Sent from my DROID BIONIC using xda premium

I believe my problem stems from flashing webtop grfs.img. Fails out any time i try and says:
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Please help! I would hate to see this phone a paper weight!
Sent from my DROID BIONIC using xda premium

Ok so i ended up flashing the radio.zip from the guide, how to receive otas again if you are on a leak, and was able to boot up afterwards, skip the setup and am about to run the pathsaver. Will let you know how i make out...
Sent from my DROID BIONIC using xda premium

Edit- looks like youre on your way

i attempted this method and it did this:
sending 'recovery' (9216 KB)... OKAY [ 1.594s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: >
Press any key to continue . . .
==============
EDIT: everything else was sent to the phone ok, so once done i powered it down/up, then rather then booting up normally, it automatically went into the stock recovery, so i pressed the VOL UP+DOWN to proceed and it then showed this:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/caller
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
==============
EDIT 2: I ignored the above, rebooted & chose to boot normally. Upon doing so, it loads up and gets to the "Welcome to DROID BIONIC" screen. When i tap on the android figure to begin, it just stays at "Please wait, this may take a few minutes." but never changes. Does not proceed any further.

[Q] I have brick my Droid 4 - Stuck in fastboot mode.

Hi !
I think have soft bricked my Droid 4:
Code:
Invalid flash mode (S) (boot failure)
OA.74
eMMC Info: Size 16G
To return to normal mode - first press key to power down
Device is LOCKED, Status Code :0
Battery OK
Ok to program
Transfer mode
USB connected
Invalid CG OTV (CG:system) Invalid SP Data
Invalid CG Version (CG:System)
Invalid CG OTV (CG:System)
I try to flash the ROM with VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml with RSD Lite 5.7 and it's stuck on flashing system.
If I try with fastboot he stuck on Writing :
Code:
C:\Documents and Settings\Administrateur>moto-fastboot flash system "C:\Documents and Settings\Administrateur\Bureau\VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml\system.img"
sending 'system' (262144 KB)... OKAY [203.703s]
writing 'system'...
What's happend ?
Regards,
Gaël

try different usb port, try different computer.
and try to do it quickly until battery has a charge

I have tried on different PC and USB Port
My batery is completly discharged.
I have make my own Factory Cable, to get it power up.
Now I trying to redownload the ZIP to view if it comrrupt ...

FukTheRegister said:
I have tried on different PC and USB Port
My batery is completly discharged.
I have make my own Factory Cable, to get it power up.
Now I trying to redownload the ZIP to view if it comrrupt ...
Click to expand...
Click to collapse
Same with new ZIP file...

I trying the Droid 4 ICS Utility ...
Exactly the same :'(
Code:
[*] Simple Droid 4 Restore
[*] Windows Version
[*] Created by mattlgroff (with help from dhacker29!)
[*] Follow us @mattlgroff @dhacker29 or on DroidRZR.com
[*]
[*] Before continuing, ensure your Droid is in the
[*] "AP Fastboot" mode and connected via USB.
[*]
[*]--- Also press the keys after the screen flashes back on when asked---
[*] IF YOUR PHONE SAYS STATUS 1 UNLOCKED EXIT NOW AND EMAIL ME
[*] YOU HAVE AN UNLOCKED BOOTLOADER! ! ! ! !
[*] [email protected] RUNNING THIS WILL LOCK YOUR BOOTLOADER!
[*]
[*] ** BE SURE YOUR BATTERY IS CHARGED **
[*]
Appuyez sur une touche pour continuer...
[*]
[*] Press enter to restore your phone to ICS 6.16.217 and ERASE DATA.
Appuyez sur une touche pour continuer...
[*]
sending 'mbm' (512 KB)... OKAY [ 0.406s]
writing 'mbm'... OKAY [ 0.484s]
rebooting into bootloader... OKAY [ 0.281s]
Press any key AFTER the screen comes back on
Appuyez sur une touche pour continuer...
< waiting for device >
sending 'mbmloader' (42 KB)... OKAY [ 0.063s]
writing 'mbmloader'... OKAY [ 0.297s]
sending 'mbm' (512 KB)... OKAY [ 0.672s]
writing 'mbm'... OKAY [ 0.469s]
rebooting into bootloader... OKAY [ 0.281s]
Press any key AFTER the screen comes back on
Appuyez sur une touche pour continuer...
< waiting for device >
erasing 'userdata'... OKAY [ 0.094s]
erasing 'cache'... OKAY [ 0.031s]
sending 'cdt.bin' (16 KB)... OKAY [ 0.031s]
writing 'cdt.bin'... OKAY [ 1.031s]
sending 'devtree' (512 KB)... OKAY [ 0.594s]
writing 'devtree'... OKAY [ 0.500s]
sending 'logo.bin' (854 KB)... OKAY [ 0.844s]
writing 'logo.bin'... OKAY [ 0.281s]
sending 'system' (262144 KB)... OKAY [207.781s]
writing 'system'...
...

Resolved
Hi !
I have take a old PC in y cave, an Dell Optiplex 755, reinstall XP SP3, and motorola drivers.
Put only one USB Factory (home made) to motorola.
I use this PC via RDP (I think, better for get more Power on USB ports), and flash it (with SAME ZIP before !).
The flash flash work directly, only 20 minutes !
The cause, is realy the HARDWARE, I cannot charge my baterie, don't change software from my before tests.
The PC have 3Go of RAM.
Regards, I hoppe if you are in same state, realy try to get a fresh PC, with MINAMAL on it.
(This PC is my 4th for the flashing !).

Modded build.prop, phone now stuck
Got bold and hastily modded my build.prop (probably forgot to change permissions on the file). Now my phone won't boot or shut off, any suggestions? Was on Hashcode's most recent JB AOKP when this happened. Phone isn't showing up in RSDlite. The phone has been plugged in to my computer as I've messing around with various apps all day so the drivers should be installed.

Stuck phone issue resolved
Sent from my SGH-T839 using Tapatalk

Working Root for ze550kl

Hello Guys,
Now it s finally here
working root for ze550kl, a very big thanks to @shakalaca,
he developed this, full credit goes to him. :fingers-crossed:
Version 1.13.40.496
original thread source
http:// www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=111151&extra=page=1
Steps to Root
1- Download the full version of firmware patch:
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
2- Descompress system.img.7z with 7zip program
3- Copy the boot.img / system.img / recovery.img to (adb/fastboot) folder.
4- Execute this commands in sequence:
-adb device
-adb reboot bootloader
-fastboot devices
-fastboot erase userdata
-fastboot erase cache
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
-fastboot flash system system.img
-fastboot reboot
system will take some time to ready, if stuck at asus splash screen, restart in recovery, wipe cache, format data partition, restart mobile.
install any super user you wish.
Enjoy,
 @shakalaca thanks again
Tried adaway working well.

HOLY!!! Thank you very much

thanks to @shakalaca
and you for information
http://zenfonlaser.blogspot.in/
How to Root ASUS Zenfone 2 Laser ZE550KL/Z00LD
How to Flash:
turn on usb debugging in mobile
connect your mobile to pc
after detecting your mobile in pc discconect it
All files link:
https://drive.google.com/folderview?id=0B_j7tYFbJZThclhsZnRPOEFUWXc
Download Flashtool and Extract it to a folder
Download system.img move it to Flashtool folder
( download all parts then put inside one folder then use 7zip software to extract system.img by opening system.img.7z.001 )
Download recovery.img and move it to Flashtool folder
Download boot.img and move it to Flashtool folder
1) now enter in to fast boot mode
methode 1: Turn Off Zenfone 2 Laser and Enter fastboot Mode (Power+Volume up)
methode 2: go to recovery and there enter boot loader mode
methode 3: by adb shell
Connect Zenfone 2 Laser with PC/Laptop
At Flashtool/fastboot folder press shift+Right Click then Open Command Here
-adb device
-adb reboot bootloader
if use methode 1 or 2 Connect Zenfone 2 Laser with PC/Laptop
At Flashtool/fastboot folder press shift+Right Click then Open Command Here
2) Enter this command:
fastboot flash boot boot.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24545 KB)...
OKAY [ 0.828s]
writing 'boot'...
OKAY [ 0.625s]
finished. total time: 1.453s
3) Enter this command:
fastboot flash recovery recovery.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (26507 KB)...
OKAY [ 0.891s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.453s
4) Enter this command:
fastboot flash system system.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 6.953s]
sending sparse 'system' (259338 KB)...
OKAY [ 13.109s]
writing 'system'...
OKAY [ 5.765s]
sending sparse 'system' (257277 KB)...
OKAY [ 13.093s]
writing 'system'...
OKAY [ 5.625s]
sending sparse 'system' (257278 KB)...
OKAY [ 12.843s]
writing 'system'...
OKAY [ 5.781s]
sending sparse 'system' (257277 KB)...
OKAY [ 12.906s]
writing 'system'...
OKAY [ 5.656s]
sending sparse 'system' (262102 KB)...
OKAY [ 13.312s]
writing 'system'...
OKAY [ 6.312s]
sending sparse 'system' (257122 KB)...
OKAY [ 13.390s]
writing 'system'...
OKAY [ 6.625s]
sending sparse 'system' (260005 KB)...
OKAY [ 13.171s]
writing 'system'...
OKAY [ 7.218s]
sending sparse 'system' (252193 KB)...
OKAY [ 12.390s]
writing 'system'...
OKAY [ 5.734s]
sending sparse 'system' (258041 KB)...
OKAY [ 12.859s]
writing 'system'...
OKAY [ 6.156s]
sending sparse 'system' (258041 KB)...
OKAY [ 12.953s]
writing 'system'...
OKAY [ 5.937s]
sending sparse 'system' (261502 KB)...
OKAY [ 13.187s]
writing 'system'...
OKAY [ 6.593s]
sending sparse 'system' (139273 KB)...
OKAY [ 7.109s]
writing 'system'...
OKAY [ 3.890s]
finished. total time: 653.488s
5) Enter this command:
fastboot oem reboot-recovery
u will see in cmd window:
G:\asus\FlashTools>fastboot oem reboot-recovery
...
OKAY [ 0.016s]
finished. total time: 0.016s
6) Wipe data/factory reset from recovery menu
use volume key for up and down
and power key for select press yes in second menu
now reboot form recovery menu
Done your Zenfone 2 Laser is Rooted.

Thank you again.. it's working and this is my feedback

How big is the patch??
---------- Post added at 01:03 PM ---------- Previous post was at 12:53 PM ----------
Btw the original image is for zenfone selfie. Will it work on 550KL

caldent said:
How big is the patch??
---------- Post added at 01:03 PM ---------- Previous post was at 12:53 PM ----------
Btw the original image is for zenfone selfie. Will it work on 550KL
Click to expand...
Click to collapse
No, this is not for selfie, this is for ze550kl.
build nos of zenfone laser and selfie are different.
This one based on latest version of zenfone laser ze550kl.

Thank you @rajiki for the news and thx to @shakalaca ....will tey this soon
Sent from my ASUS_Z00LD using Tapatalk

Superb work
I am new to Zenfone laser Ze550kl. I have two queries below
1.We need to unlock Boot-loader to execute this?
2.and this is void warranty?
Thanks for your work.

eugineprakash said:
I am new to Zenfone laser Ze550kl. I have two queries below
1.We need to unlock Boot-loader to execute this?
2.and this is void warranty?
Thanks for your work.
Click to expand...
Click to collapse
You don't need to unlock the bootloader and I'm not sure about warranty but it is usually safe to assume that you will void your warranty.
The good thing is that you can always reflash the stock rom and that should return it to factory condition but can't guarantee your warranty won['t be voided. Someone else might be able to confirm for sure.

when you flash stock firmware that will re-flash everything & your warranty would not be void.

Hey Buddy, I am in Big Trouble this time. While Flashing System.img file, i am getting the following error
Command - fastboot flash system system.img
error - cannot load system.img
Can you tell me what's the issue here? or can you provide me your Fastboot ADB Zip file will be great helpful
waiting for your answer

ArshArora said:
Hey Buddy, I am in Big Trouble this time. While Flashing System.img file, i am getting the following error
Command - fastboot flash system system.img
error - cannot load system.img
Can you tell me what's the issue here? or can you provide me your Fastboot ADB Zip file will be great helpful
waiting for your answer
Click to expand...
Click to collapse
Just wait & let command got completed,it will take some times as file too big to send.
it will sparse & send in parts, whole process will complete around 15 minute.

rajlko said:
Just wait & let command got completed,it will take some times as file too big to send.
it will sparse & send in parts, whole process will complete around 15 minute.
Click to expand...
Click to collapse
command is not starting at all. just showing error like screenshot i attached

what is the size of image size, did you extract file correctly ?
actual size of system image is 2.84 GB (3,05,09,60,328 bytes).
other commands executed or not ?

ArshArora said:
command is not starting at all. just showing error like screenshot i attached
View attachment 3524359
Click to expand...
Click to collapse
go in the extracted folder where system.img.7z.001-006 file is. click on anyone of these six files and decompress with 7-zip file manager.
now u will get a single file SYSTEM.img of about 2.4 gb. put this system.img in the adb and fastboot folder.
now flash the system.
happened the same with me a few hours ago.

I experienced that same error on that system.img and solved it by
1st: Not using administrative cmd C:\Users\(pcname)> on cmd
2nd: I just put those 3 files on C:\Users\(pc name)\
only recovery and boot img work when on adb folder.. dunno if it's on windows 10 but I got it working on above directory

just xposed needed now
can we flash xposed zip file in stock recovery?via adb or any other way?
though there is some method of flashing xposed framework without recovery which we used on 551 ML..via adb only..
anyone shed some light on this?

sausuke said:
I experienced that same error on that system.img and solved it by
1st: Not using administrative cmd C:\Users\(pcname)> on cmd
2nd: I just put those 3 files on C:\Users\(pc name)\
only recovery and boot img work when on adb folder.. dunno if it's on windows 10 but I got it working on above directory
Click to expand...
Click to collapse
Awesome dude ! that worked for me finally

ArshArora said:
Awesome dude ! that worked for me finally
Click to expand...
Click to collapse
glad that worked... I hate that system.img problem

followed all guide. Finally the system error was solved and it got flashed . Now the phone is stucked on Asus logo and below bufferring type symbol is going on from past 15 mins. I removed battery and inserted it and pressed power button + vol up continuously still it directly goes to fastboot boot. No options of normal boot or recovery option please help.

Amazon Fire 7-inch tablet rooting error messages

Hi, I recently updated my Amazon Fire 7" 5th Gen tablet to the latest system update & prior to this the tablet had already been rooted when it was running Android 5.0.1, but now the newer update has un-rooted the device and I am having difficulties re-rooting the device as now I am receiving some error messages in the Amazon Fire Tablet CMD Tool and I am unsure about what I have to do to resolve the issue....Below is a copy of the error messages I am receiving:
--------------------------------------------------------------------------------
[*] NOTE this will not work unless your fastboot drivers are installed
[*] see option 1 ADB Driver install.
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.016s]
finished. total time: 0.016s
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
remount succeeded
759 KB/s (170232 bytes in 0.218s)
61 KB/s (1976 bytes in 0.031s)
1570 KB/s (75364 bytes in 0.046s)
2984 KB/s (5904943 bytes in 1.931s)
1360 KB/s (29972 bytes in 0.021s)
mkdir failed for /system/app/SuperSU, File exists
mkdir failed for /system/bin/.ext, File exists
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: Operation not permitted
cp: /system/xbin/daemonsu: Text file busy
cp: /system/xbin/supolicy: Operation not permitted
Unable to chmod /system/xbin/supolicy: Operation not permitted
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: Operation not permitted
cp: /system/bin/app_process32_original: Text file busy
--------------------------------------------------------------------------------
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.006s]
finished. total time: 0.007s
resuming boot...
OKAY [ 0.497s]
finished. total time: 0.497s
--------------------------------------------------------------------------------
[*] your device is rebooting and will finish the root process.
--------------------------------------------------------------------------------
Thanks in advance for any help and advice you can give to me.

If you have 5.1.1, the root procedure is a bit different. Start here:
http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441

shabuboy said:
If you have 5.1.1, the root procedure is a bit different. Start here:
http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441
Click to expand...
Click to collapse
Thank you shabuboy, I will read through the thread and see if any of the information can help me....:good:

I've read through the links enlisted and watched the tutorials but I've still not been able to root my device as I continue to get the same error message ...I wish now I had not updated to Android 5.1.1 and at this point I think I'm going to give up until the next update or so ....

If you followed the procedures for 5.1.1 and/or used the supertool and still did not work, I would attempt to disable OTAs at the least.

shabuboy said:
If you followed the procedures for 5.1.1 and/or used the supertool and still did not work, I would attempt to disable OTAs at the least.
Click to expand...
Click to collapse
Yes I have disabled the OTAs now, as well as this I also found another XDA user who's having the same problem with he's device: http://forum.xda-developers.com/hd8-hd10/help/looking-help-rooting-kindle-5th-gen-v5-t3285665 & I've contacted him to see if he has found a solution to his, hopefully he'll get back to me.

DeeKay10 said:
Yes I have disabled the OTAs now, as well as this I also found another XDA user who's having the same problem with he's device: http://forum.xda-developers.com/hd8-hd10/help/looking-help-rooting-kindle-5th-gen-v5-t3285665 & I've contacted him to see if he has found a solution to his, hopefully he'll get back to me.
Click to expand...
Click to collapse
Have your tried doing a restore with the 5.1.1 stock firmware before proceeding with the root process?

I may try this option next
I may be forced to try this option next, I'll give a feedback on the results once I've done this although I did factory restore obviously to no avail as once the update has been done it cannot be downgraded....

Good news!!!! I now have full root access/super user privileges
***UPDATE***
I now have full root access to my Amazon device, I think that some of the files that were giving the error messages were corrupted and therefore last night I re-installed/restored the android 5.1.1 firmware to the tablet and this resolved the problem …Thank you both "shabuboy & thekrakah", I much appreciate your contribution to my query and thankfully now my device is operating correctly....