Database Info

[Q] TWRP Install Fail

I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:

Seahorse said:
I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:
Click to expand...
Click to collapse
Are you installing the jb compatible twrp? what happens when you try and boot recovery?
Sent from my SGH-I727 using xda app-developers app

I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.

Seahorse said:
I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.
Click to expand...
Click to collapse
When you used twrp to flash stock it includes recovery which overwrites twrp. Go back to the instructions to fastboot twrp, do so and you should be good.
Good Luck!
Try a new download of twrp!
Reboot your pc, only plugin your asus and no other device, retry fastboot.
Forgot, if on dock remove from dock reboot pc and asus and try again.

Clearing cache maybe? Just a shot in the dark, never seen this one. I can tell you I flashed ota v13 and it blew away my recovery but I was able to get it back easily.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

After following numerous google links - too many links fastboot, I found one resolution. Another device used on pc and usb drivers installed since last use of unit giving links error. Resolution was remove offending drivers, reboot pc and profit.
Good Luck!

I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
Click to expand...
Click to collapse
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.

Blew away cache, used fastboot again on twrp.blob and got same install fail error message. However, on power on + vol down RCK now works with TWRP, which is kind of odd, but there you go. Thanks for all the suggestions...

glad you got it fixed

SITH16 said:
I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
Quote:
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.
Click to expand...
Click to collapse
Three things come to mind.
1. Try to flash as twrp directions show; without adb reboot bootloader.
2. Verify you are trying to flash the proper version for your bootloader; ics or jb.
3. If the above two items fail redownload proper version for your boot loader and try again.
Note: The twrp page also shows how to flash with adb!
Good Luck!

Terminal Emulator is an easier way to flash TWRP imo. But hey.

babymatteo said:
Terminal Emulator is an easier way to flash TWRP imo. But hey.
Click to expand...
Click to collapse
Terminal method worked. Thanks everyone for helping me out.

TWRP Install Fail
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?

BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
this is the tf300t forum. Make sure you are installing a tf700t TWRP

cmendonc2 said:
this is the tf300t forum. Make sure you are installing a tf700t TWRP
Click to expand...
Click to collapse
I noticed that after I hit reply. I was using all of the correct TF700t TWRP and whatnot. I found this in a google search because it was similar to my issue. It turned out that even though I thought I had unlocked my device, it did not unlock. I fixed that and now I am all set.

BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
The warning invalid state normally applies to the bootloader being locked make sure your bootloader is unlocked.
Sent from my Nexus 5 using Tapatalk

[Q] Need help flashing recovery image.

I just got a Moto G (Model XT1045) yesterday to replace the Nexus One that I have had since the week it was released. I am wanting to install Cyanogenmod 11, and am following "wiki.cyanogenmod<dot>org/w/Install_CM_for_falcon" to do it. (Sorry, too new to link directly.)
The bootloader is unlocked, but I am unable to get the recovery ROM working. This is what I type as well as the output:
Code:
C:\Users\User\Desktop\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot flash recovery WM-swipe-6.0.4.7-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (9954 KB)...
OKAY [ 0.395s]
writing 'recovery'...
OKAY [ 0.329s]
finished. total time: 0.734s
The Fastboot screen on the phone says the following:
Code:
USB connected
cmd: getvar:partition-type:recovery
cmd: getvar:max-download-size
cmd: download:00862000
cmd: flash:recovery
Mismatched partition size (recovery)
Other forums have said the partition thing is normal and should be ignored.
Now, when I go to "Recovery" the screen flashes for a moment the screen that says that the phone is unlocked, but then goes right back into Fastboot with the error "Boot up failed". I tried doing the recovery thing with both of the ClockworkMod 6.0.4.7 compatible images for my phone as well as TWRP 2.7.1.0. I have also tried going strait to recovery after I loaded it from the command prompt and also tried "fastboot reset-bootloader". All of those yielded the same results.
I can still get into the original OS, so I not really freaking out, but it would be nice to get CM loaded on because I don't want to spend the time tweaking my phone too much just to wipe it the next day. Any suggestions would be great. Thanks for your time.

seeigecannon said:
I just got a Moto G (Model XT1045) yesterday to replace the Nexus One that I have had since the week it was released. I am wanting to install Cyanogenmod 11, and am following "wiki.cyanogenmod<dot>org/w/Install_CM_for_falcon" to do it. (Sorry, too new to link directly.)
The bootloader is unlocked, but I am unable to get the recovery ROM working. This is what I type as well as the output:
Code:
C:\Users\User\Desktop\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot flash recovery WM-swipe-6.0.4.7-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (9954 KB)...
OKAY [ 0.395s]
writing 'recovery'...
OKAY [ 0.329s]
finished. total time: 0.734s
The Fastboot screen on the phone says the following:
Code:
USB connected
cmd: getvar:partition-type:recovery
cmd: getvar:max-download-size
cmd: download:00862000
cmd: flash:recovery
Mismatched partition size (recovery)
Other forums have said the partition thing is normal and should be ignored.
Now, when I go to "Recovery" the screen flashes for a moment the screen that says that the phone is unlocked, but then goes right back into Fastboot with the error "Boot up failed". I tried doing the recovery thing with both of the ClockworkMod 6.0.4.7 compatible images for my phone as well as TWRP 2.7.1.0. I have also tried going strait to recovery after I loaded it from the command prompt and also tried "fastboot reset-bootloader". All of those yielded the same results.
I can still get into the original OS, so I not really freaking out, but it would be nice to get CM loaded on because I don't want to spend the time tweaking my phone too much just to wipe it the next day. Any suggestions would be great. Thanks for your time.
Click to expand...
Click to collapse
You have a Moto G 4G. Look in 4G Development Forums for a semi-working TWRP.
But be careful. Moto G and Moto G 4G ROMs aren't compatible. There is no CM or any other custom ROM yet for your device

k-kuchen said:
You have a Moto G 4G. Look in 4G Development Forums for a semi-working TWRP.
But be careful. Moto G and Moto G 4G ROMs aren't compatible. There is no CM or any other custom ROM yet for your device
Click to expand...
Click to collapse
Well crap. Thank you. Glad nothing got bricked.

[Q] Moto G stuck in boot loop

This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.

manicresin said:
This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.
Click to expand...
Click to collapse
What did you use to flash? fastboot or mfastboot?

280
oversleeper said:
What did you use to flash? fastboot or mfastboot?
Click to expand...
Click to collapse
I used mfastboot.

http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:

oversleeper said:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:
Click to expand...
Click to collapse
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s

On a whim I decided to try the retail firmware and was able to get the phone to boot to stock, but I tried to load TWRP again and it went back to the boot looping state.
I really don't understand what is wrong with this phone because this are for the company I work for and we have flash about a thousand this exact same way and have never ran into this issue.
I am going to try philz recovery to see if it cause the normal boot process to break and if not I try loading the a custom rom from there.

manicresin said:
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s
Click to expand...
Click to collapse
Pretty normal, you got errors because you upgraded the bootloader to the last version, so you can't downgrade it. Now you can: try to flash the 4.4.2 stock boost version (without flashing gpt.bin and motoboot.img) or if doesn't work due to upgraded bootloader, just wait few days until the 4.4.4 firmware for boost will be downloadable. It's already realeased don't worry, look https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/100754/p/30,6720,9050
EDIT: It's a boost version, it's pretty different... You can't flash whatever you want so easily... search for some guide, I can't help about boost version.

The boost 4.4.2 stock firmware failed but the retail version worked, I'm try that with philz recovery to see if I can get CM 11 to work. If that fails ill wait for the 4.4.4 boost firmware.
Thanks for the help

I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
ClockWorkMod Recovery 6.0.5.0

CodyF86 said:
I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
Click to expand...
Click to collapse
I downloaded your recovery image and flashed it, wiped everything and reset.
Installed cm-11-20140903-NIGHTLY-falcon from usbdisk, it said completed only after ~20 seconds but there where no errors.
Rebooted the device and the cyanogenmod animated boot logo was displayed.
The phone booted fine was is working, now to try and see if I can get my image loaded.
Thanks for the recommendation, I didn't think to try CWM since Philz recovery is based on it, but it failed to load CM 11.

XT1039 softbricked, any help or suggestions appreciated

Hello,
Edit: Don't know how or why, but after a couple of more tries I was able to boot the recovery directly and flash the rom. So everything is working fine right now. Admin/mod, would you like to close this thread? Thank you
For some reason I wanted to flash a new rom on my XT1039. In the process I screwed up and got it softbricked. I already had a look at the thread started by alfread56 and although the situation seems quite similar, the offered solutions didn't work out for me.
Right now my phone doens't have any rom installed. Flashing twrp with fastboot suggest everything works allright (using a linux system by the way):
fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8314 KB)...
OKAY [ 0.295s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.598s
After the reboot and holding the buttons for recovery mode I still get the stock recovery screen. When I select recovery in this menu, the phone shuts down. Because I know holding the recovery buttons on reboot takes some timing, I have redone the procedure of flashing twrp and holding the buttons numerous times. But it never went to the twrp recovery.
Then I tried to boot the twrp image directly with
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.290s]
booting...
OKAY [ 0.230s]
finished. total time: 0.520s
Here I made a mistake: I have also flashed the boot partition with the twrp image with fastboot flash boot recovery.img (don't know how much of problem this is).
Booting up the TWRP image works fine. Then I've wiped dalvik, cache, data, internal storage and after several runs also deleted system by accident, and factory reset. When trying to flash the lineage zip everything works out fine for about 1 second, then the screen flashes en the phone is back in the TWRP screen. Too quick for me to see what the output is, but I do see there are not red marked lines (no errors)
I have tried it with several different ROMS (al checked), with several versions of TWRP and with fastboot and mfastboot. Does anybody know a solution on how to get twrp recovery working on my phone, or why I can't flash a rom when I boot twrp directly? Any help is appreciated!
Thank you in advance.
Regards,
weisa4564

Cannot flash TWRP with latest OTA (5.4)?

I'm trying to obtain root on a Shield K1 that has the latest ota update (5.4).
I've unlocked the bootloader, but the latest TWRP just won't flash, says OK and writes to recovery, but same stock recovery stays there.
Do I need to use an older developer image, one that was released prior to the latest TWRP?
This is what the terminal is giving me:
Code:
[[email protected] tablet ]$ sudo fastboot flash recovery twrp-3.2.1-0-shieldtablet.img
target reported max download size of 100663296 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.487s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 0.993s
Then, when I reboot to recovery, I get a dead robot with a little ? & "No command"
EDIT: OK, I fixed it, by using "fastboot boot twrp.img" and then installing lineage and then installing twrp
I didn't know that you could boot an image without installing it that's really good to know.
So that's a workaround.

I could just compile a new TWRP but that would take effort

scres said:
I could just compile a new TWRP but that would take effort
Click to expand...
Click to collapse
You definitely don't need to do that. I have a K1 on 5.4, and TWRP works fine. Although I did already have TWRP installed before flashing 5.4. So not sure if that makes a difference.
Try fastboot erase cache, and flash a different TWRP build (like a build or 2 older such as 3.1.1-0).

I fixed this already