Database Info

[TOOL] [BETA] [Windows] Android Flash Recovery

Introduction
Since I'm not a ROM developer or Java coder, I thought I could help by donating this little tool, that was origionally written for my personal use, for all to utilize in an attempt to give back to this community.
WinFastboot - Flash Recovery has been renamed to Android Flash Recovery
Requirements
- A PC running Microsoft Windows. 32 or 64 bit.
- Correct Android USB drivers installed for your device
- An Android powered device with debugging enabled
Description
Android Flash Recovery is a Windows GUI front-end for the Windows version of fastboot. This particular tool is designed to simplify flashing an Android device's recovery partition. Android Flash Recovery WILL NOT repair a bricked device. The device must be able to be put in to fastboot mode for Android Flash Recovery to be able to work. Since Android Flash Recovery is just a GUI for fastboot, the same applies for fastboot.
Beware. Android Flash Recovery unfortunately will not work with every single Android device. I am however, attempting to make strides in that direction
Installation
Installing Android Flash Recovery is simple too. Just unzip to a folder of your choice and then execute androidflashrecovery.exe, assuming your device drivers are already installed.
If you haven't installed your drivers yet, then they will need to be installed before using Android Flash Recovery as your device won't be detected.
If you are an LG user, the latest LG United Mobile USB drivers are are in a sub-folder of Android Flash Recovery, titled "USB". If you have attempted to install your USB drivers in the past with no success or with errors, go to Control Panel and uninstall any LG driver setup program you may find. Reboot your computer. Run the driver installation program. Make sure your device is NOT connected to the PC. Reboot your PC once more. Enable USB debugging on your device the power it off, trust me. After your PC has fully booted, plug your device into a USB port. Do not plug in to a USB hub. Windows may detect your device at this point and begin searching for or installing drivers. Power on your phone. Wait for all devices to be installed. For Froyo and GingerBread phones this is normally 5 or 6 devices. For ICS and JB this is 4 devices I believe. The important one is 'Android Single Sooner Interface'. This won't be installed if USB debugging isn't enabled on the device. Now your drivers should be installed and you can use Android Flash Recovery at your leisure.
Using
Using Android Flash Recovery is even easier than installing it. Browse for the recovery you wish to flash and press the 'Flash Recovery' button. NOTE: In order for Android Flash Recovery to flash, your device MUST BE in fastboot mode.
Included with Android Flash Recovery are the adb binaries with support libraries as well as fastboot. Android Flash Recovery is written to use the binaries included in it's package. Also included is the driver setup application for LGE Android Mobile devices ( United Mobile USB Drivers ).
Post questions here. I will try to answer them as I can. I have a regular full-time job so I am not a full-time developer. You may also email me at [email protected]. Set your subject line to "Android Flash Recovery". If the subject line isn't correct your email will be ignored.
Download
Latest version here -> Android Flash Recovery

Reserved...

Removed

Since I have had zero feedback about my previous post, I've decided to rename "WinFastboot - Flash Recovery" to "Android Flash Recovery". I'd also like to mention that it will be updated later this evening. I have a few more minor things to wrap up and then I'll upload and post a new link.
I've had quite a few downloads, so I know my app is being tried. I really need some feedback folks. If you have issues with, a feature request, or even a simpe UI improvement/suggestion. I'm also curious as to the types of devices that my app is being used in conjunction with. What works and what doesn't.
Thanks.

if a device is able to go into recovery mode, does it mean this app is applicable?

oldsap said:
if a device is able to go into recovery mode, does it mean this app is applicable?
Click to expand...
Click to collapse
Unfortunately no. The device must be in fastboot/bootloader mode.

bill.weckel said:
Unfortunately no. The device must be in fastboot/bootloader mode.
Click to expand...
Click to collapse
well there goes every samsung device that isnt a nexus

jamcar said:
well there goes every samsung device that isnt a nexus
Click to expand...
Click to collapse
There is a way to install a ROM with adb so I'd say it may be possible to do a recovery too. I'll do some investigating. Might be able to do something.
Sent from my LG-P506 using xda app-developers app

bill.weckel said:
There is a way to install a ROM with adb so I'd say it may be possible to do a recovery too. I'll do some investigating. Might be able to do something.
Sent from my LG-P506 using xda app-developers app
Click to expand...
Click to collapse
could you keep us posted on you research?

jamcar said:
could you keep us posted on you research?
Click to expand...
Click to collapse
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.

bill.weckel said:
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.
Click to expand...
Click to collapse
for samsung phones you would look into using the dd if=[recoveryimg] of=[recovery partition] to copy the recovery image to the recovery partition. this is how you manually do a samsung phone's recovery flash. so a way to implement this into the app for, let's say the GS3 would be
adb push [user selected recovery img] \sdcard\recovery.img ( or some other way of copying the user selected recovery img to the root of the sdcard )
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
and that will flash the recovery to the gs3.
of course the main issue is that the recovery partition is not always the same name of the block so /dev/block/mmcblk0p18 will not always be the name of the recovery block. The way to overcome this ( i think ) would be to program in a part of the app that reads in Build.MODEL which will give you the model device the user has plugged in and then you can determine from there what the block title is by programming in the blocks for each samsung phone model. To make it simpler befoer you do that, filter out stuff that can just be fastbooted...something like...
if(Build.Manufacturer == 'HTC' || Build.Manufacturer == 'Motorola' ||... etc)
// just do fastboot
else
{
switch(Build.MODEL) { // if switching strings is supported in Android ( it was introduced in java se 7 ) otherwise use enums
case GS3:
block = 'mmcblk0p18';
break;
}
//move the file to the SD card if the model is supported
//do the su and dd command here
}
anyways...im bored at work so just figured ide give my 2 cents, not sure how much support you wanna give this haha...hope this helps

For me it's not working i am in Fastboot mode but winfastboot tells me i am not ... it recognized that the device is connected but not in fastboot mode even tough on my phone it says "fastboot usb" :\
Phone : HTC Wildfire
s-off
radio 3.35.15.31
ROM : CM9
Yeah i just saw "ICS( 4.0.* ) and JB( 4.1.1 ) devices are not detected correctly by the driver software. Some devices may not get installed." in the readme ...
Cant you do anything about this to fix it ?

That's strange. I figured there would be some devices that this wouldn't work for. Are your USB drivers installed correctly? All other fastboot screens say "Fastboot mode started\nudc_start()". I will look into it tho.
Sent from my LG-P506 using xda app-developers app

Updated. Check first post for downloads

Yep , USB drivers installed correctly , other things worked everytime i tried to do something ...

Commandox said:
Yep , USB drivers installed correctly , other things worked everytime i tried to do something ...
Click to expand...
Click to collapse
I'm looking into a workaround for your HTC device and from what I've heard I may need one for some Samsung devices as well. I'm sorry the update I posted doesn't contain this workaround. It is something that I will look into. I do have a regular full-time job tho, so it may take a few days for me to figure out what I need to do, how to do it, then writing the code for it.
As for the fixing how device drivers are installed, that's not something that I can fix. I believe it is actually an issue with the ICS and JB ROMs themselves.

For those of you who are having issues with Android Flash Recovery, I really need the names of your recovery mount points. HTC owners and Samsung GS3 owners for sure.
I can't fix these issues without your input folks. I'd really like to be the guy that has the one universal recovery tool that no one can live without. Scratch my back and I'll scratch yours.

bill.weckel said:
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.
Click to expand...
Click to collapse
we have download mode instead of fastboot/bootloader we can use ODIN, samsungs recovery tool (tool not mode, meaning the program ODIN is on a computer)
EDIT: sprint galaxy s III is /dev/block/mmcblk0p18

I believe I've stumbled upon a universal method to check a device for mount points. I'm going to throw together a little test app and then upload here for y'all to test out if you would. If my suspicions are correct, I will then be most able to write the
universal recovery tool for windows.
@jamcar
Thanks for your response. I've actually heard of ODIN.

bill.weckel said:
For those of you who are having issues with Android Flash Recovery, I really need the names of your recovery mount points. HTC owners and Samsung GS3 owners for sure.
I can't fix these issues without your input folks. I'd really like to be the guy that has the one universal recovery tool that no one can live without. Scratch my back and I'll scratch yours.
Click to expand...
Click to collapse
For Galaxy Note International (GT-N7000) it should be - /dev/block/mmcblk0p6
i just need to confirm that

[Q] one+1 un-brickable? I think not...

OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!

jpilch said:
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
Click to expand...
Click to collapse
This honestly is very confusing. I had to read what you wrote a couple of times to try and comprehend what the problem is.
Have you tried using fastboot without any toolkit? I ask because you haven't mentioned it anywhere. Persist can be fixed by fastbooting back to pure stock, and Mike's fix on the OnePlus forums, and/or updating to 44S.
Can you tell us what errors you get when you try to reflash the same rom? What recovery are you running? Which rom were you trying to reflash?

I have to agree with @nicholaschum, your post is very vague and confusing in its present form, and I'm a pretty seasoned troubleshooter on XDA.
What's needed? Less emotion, less comic type speech, less sarcasm, more specifics and facts.
Transmitted via Bacon

1328
If I try to sideload, it says either signature failed or whole signature failed.
Anything i push does not get pushed and I have tried multiple drivers from the galaxy ones that come in the reflash.zip from the one plus tech support to the Google ones I am using now.
If I try to fastboot through toolkit it says failed, not unlocked can't flash/erase. If I fastboot through cmd it says error: closed. I do all my checks, and it shows up in fastboot and adb but won't let me send anything.
The phone boots up for about 15 in is before restarting, the only way to get files on are to drop them in explorer within these 15secs, to internal storage, which used to be my sdcard.
I have tried flashing/side loading multiple ROMs from miui, 44s, 33r all signed to caulkins and mahdi. Nothing has worked (and the aosp OTA).
I cannot unlock bootloader, cannot reset tamper, cannot load GUI for more than 15 secs, and cannot root (although kermal already says it is, I suspect su needs to be in place).
I have also tried fastboot -c boot recovery.IMG (and recovery recovery.IMG) but no luck still. Is there a PC version of the Mac toolbox that can reset tamper? At least then I could unlock bootloader and install twrp and flash.
Thanks for the help
Josh

Still sounds like a driver issue imo.
First uninstall ALL previous drivers you have tried from device manager.
Installing one driver after another often causes conflicts.
Then download the official Android SDK and install Google USB driver. Google for instructions if needed but everything is pretty much straight forward.
This driver has the biggest chance of success.
After that you're off to start fixing your phone using fastboot and adb.

OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys

jpilch said:
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
Click to expand...
Click to collapse
For the fastboot bit, I've seen this happen a lot. Many people used this to solve their issue: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912

[Q] Nexus has been unusable since 5.0 OTA

As a preface, I keep my Nexus (16GB) stock/unrooted because having it down while flashing ROMs is not an option anymore. I need to the phone to work all the time, period. The irony is ridiculous.
Received the OTA from Sprint a couple of weeks ago, immediately noticed the (often-mentioned) dismal battery life and GPS hasn't been able to connect since that day. As I use GPS daily and need my phone to last for longer than 6 hours--these present full stop problems. This is in addition to the (often mentioned) stuttering/lag/freezing issues which are beyond frustrating as a heavy user. Really Google?!
Over the last week I've:
-Cleared caches multiple times
-Wiped/Factory Data Reset (3 times as it would not allow me to sign into my Google Account or sync apps)
-Spoke with Nexus Support for three hours today, which ended with 'Sorry, you'll have to call Sprint or LG'
-Tried GPS location 'fix' on XDA (didn't work)
-Been unable to send/receive SMS messages for two days
I'm beyond frustrated with this process and with Google for their lack of response in fixing widely-known 5.0 issues...on their own device. This phone is useless at the moment. What are my options? Root and roll back to KitKat? Throw this phone out of the window and go get a G3? I don't want to use a custom ROM/Recovery unless there are no other options.
Thanks for any advice-

993 said:
Over the last week I've:
-Cleared caches multiple times
-Wiped/Factory Data Reset (3 times as it would not allow me to sign into my Google Account or sync apps)
-Spoke with Nexus Support for three hours today, which ended with 'Sorry, you'll have to call Sprint or LG'
-Tried GPS location 'fix' on XDA (didn't work)
Click to expand...
Click to collapse
For the problems you're describing, you really haven't done much to solve it.
Unlock the bootloader, flash a factory image, relock the bootloader.

Why would you speak to Nexus support for 3 hours for? Waste of time

Frankly, I wanted to see if they would even acknowledge any of the issues that appear to be quite common recently with 5.0. They clearly did not, and it was relatively little effort wasted as it was through Hangouts (on a desktop though, phone forgot how to Hangout).
I have not tried to flash the bootloader, as I said I want to keep this phone as OEM as possible. Since that doesn't appear to be an option I will update when it's complete.

993 said:
I have not tried to flash the bootloader, as I said I want to keep this phone as OEM as possible. Since that doesn't appear to be an option I will update when it's complete.
Click to expand...
Click to collapse
Please read the stickies and take advantage of the knowledge base. My suggestion keeps the phone absolutely stock. It's telling that you couldn't recognize that.

I agree, just flash the stock image from fastboot.
Sent from my Nexus 5 using Tapatalk

Wakamatsu said:
Please read the stickies and take advantage of the knowledge base. My suggestion keeps the phone absolutely stock. It's telling that you couldn't recognize that.
Click to expand...
Click to collapse
That isn't what the Nexus rep said (reps have been known to be misinformed). I have read the relevant stickies and am aware of how to use this site. You didn't read my question. As I said, I would rather not flash if there are other viable options. IF this is the only workable solution thus far for people experiencing the above listed issues then OK. Thanks for your suggestion.

993 said:
That isn't what the Nexus rep said (reps have been known to be misinformed). I have read the relevant stickies and am aware of how to use this site. It is telling you didn't read my question. As I said, I would rather not flash if there are other viable options. IF this is the only workable solution thus far for people experiencing the above listed issues then OK. Thanks for your suggestion.
Click to expand...
Click to collapse
Flash the factory image. OTAs sometimes fail to implement properly. What you are describing is almost certainly that. You've already tried everything you can to fix the issues short of flashing. So flash.

You either have bad hardware, or the upgrade didn't install correctly. As others have mentioned, flashing the factory image should work.

993 said:
You didn't read my question. As I said, I would rather not flash if there are other viable options.
Click to expand...
Click to collapse
You said that you don't want to flash a custom rom. A factory image is what is installed on the Nexus by Google. Again, you're betraying a lack of knowledge on this subject.

If you wanted stablity you should of stayed on kitkat, hence why i never updated, you a os i can rely on and thats currently 4.4, as usual android builds at the start have minor issues and we wait for google to fix them.
I usually dont update till the devs can get a functioning build thats suitable for the community.
as above,
Fastboot oem unlock, flash 4.4 or 5.0 google image, relock bootloader
If he doesnt want to flash a custom rom then he should know how to flash a stock rom.
https://developers.google.com/android/nexus/images

I don't even speak to my own family for 3 hours, let alone a complete stranger lol wow

Wakamatsu said:
You said that you don't want to flash a custom rom. A factory image is what is installed on the Nexus by Google. Again, you're betraying a lack of knowledge on this subject.
Click to expand...
Click to collapse
Here's what's been done so far several times over:
Unlocked Bootloader
Installed SDK kit from Google using their walk though
Attempted ADB sideload of Google Factory images (5.0 then 4.4) from appropriate modes on CWM and TW
Attempted Fastboot (works only with CWM, no push/pull)
Multiple Full Wipes in both recoveries
Attempted ADB commands through terminal (W7 Pro - Admin)
Uninstalled, Reinstalled all recommended device driver packages, only recognizes in device manager as 'Google Nexus ADB Device' not Explorer Shell (read relevant FAQs) regardless of driver.
Used multiple USB ports/cables, rebooted PC each change in configuration
Root Toolkit 1.9.9 does not recognize through ADB
As of current, only Bootloader (unlocked) and Recovery mode work. I cannot access the SD card of the device through any means I've tried. The last that the OS booted I ensured that USB debugging was on in Settings. ADB mode in either recovery does not change device recognition on PC, nor does file system appear. System will not boot to ensure debugging setting has remained. Same issues with a laptop with no known prior driver issues.

993 said:
Attempted ADB sideload of Google Factory images (5.0 then 4.4) from appropriate modes on CWM and TW
Attempted Fastboot (works only with CWM, no push/pull)
Click to expand...
Click to collapse
You can't sideload a factory image. Fastboot commands are executed in bootloader, not recovery.

That should read that 'fastboot only responds to commands while CWM is the recovery'.
I can flash recoveries by this method from CMD but anything else (ROMS, etc) show progress but end before completion.

993 said:
That should read that 'fastboot only responds to commands while CWM is the recovery'.
I can flash recoveries by this method from CMD but anything else (ROMS, etc) show progress but end before completion.
Click to expand...
Click to collapse
Dude, you really need to read and understand the stickies before you do something bad to your phone. You are just flailing right now.
And really, all you needed to read was the install instructions on the Google factory image page.
1) Unlock bootloader
2) Unzip the factory image zip
3) Reboot in to bootloader
4) Run the flash-all script in the factory image folder.

This was the first method I tried. I have downloaded the factory image from Google several times and I get an 'unexpected end of data' message in 7zip when extracting my copies. Downloading from Google has been hit or miss with 'unknown network error' that halts the download, not sure what that could be.
I am trying to pinpoint the cause of these issues, as flashing back to factory without good images won't be possible. I understand how straightforward a factory flash should be especially with OEM tools but in my case I keep running into roadblocks.

Disable your antivirus and firewall during the download, that may help.

gee2012 said:
Disable your antivirus and firewall during the download, that may help.
Click to expand...
Click to collapse
Thanks for your suggestion. I disabled MSE + Firewall on the W7 machine and attempted to download [hammerhead-lrx21o-factory-01315e08.tgz] again from Google with the same error result, halting the download before completion.
My main machine, a Chromebook, will download the file completely however the zip cannot be moved without losing file size (downloads the entire 556.3MB, however once moved it magically becomes 417.2MB).
Further, I went to the Sprint Store today (I know) to see what the techs could do about pushing the factory image on the device. After about 30 minutes, they came back with "You should call Google". Brilliant. Now all I need is someone to suggest I call LG and the trifecta will be complete.

993 said:
Thanks for your suggestion. I disabled MSE + Firewall on the W7 machine and attempted to download [hammerhead-lrx21o-factory-01315e08.tgz] again from Google with the same error result, halting the download before completion.
My main machine, a Chromebook, will download the file completely however the zip cannot be moved without losing file size (downloads the entire 556.3MB, however once moved it magically becomes 417.2MB).
Further, I went to the Sprint Store today (I know) to see what the techs could do about pushing the factory image on the device. After about 30 minutes, they came back with "You should call Google". Brilliant. Now all I need is someone to suggest I call LG and the trifecta will be complete.
Click to expand...
Click to collapse
Try LG to see if they will help. Haha had to.
Can you not download on your phone? I'm not familiar with sending MMS but does it work forcing your phone to 1x? I'm trying to think of ideas. What all apps do you have installed?
Sent from my Nexus 5 using XDA Free mobile app

TWRP recovery will not install on ME301T

Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!

asilaydyingdl said:
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
Click to expand...
Click to collapse
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh

lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Exactly. I open a command line on the folder, renamed the file to twrp.blob, and then I I am using the following:
ADB devices
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
I think the problem is really simple though. I think for some reason, the tablet and the computer are not communicating via fastboot. I.e. the info is not actually getting through the USB cable to the tablet when in fastboot. I have android debugging enabled and all that good stuff. So my assumption is this is a driver issue or an extra step needs done on the tablet to get the communication working. All drivers did install properly according to the PC. Maybe it's even the USB port on the tablet itself and I need to exchange it. But I can transfer files like it's a media device, so I doubt that's it.
Any thoughts?
***UPDATE***I checked settings in SuperuserSU and it turns out I did not have root enabled at boot. Enabled it and it connected to the PC as "fastboot". Commands are still not getting sent to the device. Whenever I try to send the blob, it always says "0 KB" and the device just freezes. Perhaps I need a different command or fastboot on the PC isn't initializing correctly? Or maybe there is a setting on my device that needs tweaked yet?
Thoughts?

I think I know what the problem is. Someone using the TF300T tablet had the exact same problem I'm having. Turned out it was their rooting method. I used KingoROOT despite a few murmurs of it causing issues because I was looking for results quickly not a quality job like I should have been. SuperuserSU has been behaving weirdly, as well as my USB android keyboard and a few other quirks in the OS since I did the root, so it makes sense. I will have to use the KingoROOT app and undo the root, and retry with motochopper. KingoROOT must not have rooted all directories. If that doesn't work, I will probably have to do a full restore to stock settings by re-installing a stock Asus ROM and start fresh.

lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Did more work and research. I did actually have the improper drivers installed. I installed them from Asus, so that is fixed. But the problem remained. After further research, it came down to version builds and numbers. I am using a version of Asus' firmware that isn't compatible with the operations I'm trying to perform. I am using version 10.6.1.15. TWRP 2.5.0.0 and newer can NOT be installed on any Asus tablet running anything less than 10.6.1.27. There is something about the bootloader, encryption or a security setting that prevents data from being pushed via a fastboot command. So I now have a Christmas project, which is update to a newer version of Asus firmware.
I found my solution here, in a thread filled with people having the exact same issue:
http://forum.xda-developers.com/showthread.php?t=2179874&page=3
And directions for the fix here:
http://forum.xda-developers.com/showthread.php?t=2187982
Hope my work helps someone else.

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!