I'm on the T-Mobile variant and have followed the steps on the motorola website to unlock the bootloader. When I boot into fastboot, it says the device is unlocked with at status code 3. When I run 'fastboot flash recovery recovery.img' everything seems to run fine:
fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.930sWhen I try to reboot into recovery mode it just shows me the warning that my bootloader is unlocked, then boots as normal. I don't know what to do. I've tried both the twrp and cwm recovery images. Any help?
what recovery did you flash?
waiflih said:
what recovery did you flash?
Click to expand...
Click to collapse
I've tried both the twrp and cwm recoveries that are available in the android development section.
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
mentose457 said:
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
Click to expand...
Click to collapse
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
elijahah said:
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
Click to expand...
Click to collapse
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
jayboyyyy said:
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
I'm already on 4.2.2. I'm guessing you mean to undo the recent OTA? How would I do that without a custom recovery or root?
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
flashallthetime said:
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
Click to expand...
Click to collapse
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
mentose457 said:
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
Click to expand...
Click to collapse
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
phositadc said:
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
Click to expand...
Click to collapse
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Thanks for all your help though guys.
Click to expand...
Click to collapse
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
mentose457 said:
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
Click to expand...
Click to collapse
I get this:
fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.071s
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
Excellent. Glad you got it working.
elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
PS you had recovery the first time you hit the up volume and it sent you to a screen that said "no command" from that screen if you press the up volume and power button together it sends you to the recovery screen. It may be down volume and power together to get passed that "no command" screen but its one of the two. I saw people having that same problem in the forum about maintaining root through the OTA.
phositadc said:
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
Click to expand...
Click to collapse
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
leonardoafa said:
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
Click to expand...
Click to collapse
Will charge up a bit over 50% and see. I still get permission denied. Plus when I try to get into recovery, I can't. The Motorola log shows up for a while, then restarts and boots normally into Android.
Related
The phone is unlocked and is working fine but out of the sudden it is hung at boot up screen.
Now i cannot even access the RA-nexus recovery gui. It will hang at the screen with the 'X' logo.
I tried to re-flash the recovery but got the below error when i try to do a fastboot.
"
D:\Downloads\Nexus One\android-sdk-windows\tools>fastboot devices
123456789012 fastboot
D:\Downloads\Nexus One\android-sdk-windows\tools>fastboot flash recovery recover
y-RA-nexus-v1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
D:\Downloads\Nexus One\android-sdk-windows\tools>
"
Another weird output when i ran the 'fastboot-windows.exe devices -s'
"
C:\1>fastboot-windows.exe devices -s
123456789012 fastboot
"
Seems like i need a GoldCards for Nexus One but i don't know how to make it since my only Nexus One is not accessible now.
Any help on this??
Are to you doing this to enter recovery from bootloader mode (vol down, power)
try flashing the stock recovery image...
jerrycycle said:
Are to you doing this to enter recovery from bootloader mode (vol down, power)
Click to expand...
Click to collapse
Cannot enter the recovery from bootloader too. After selecting the 'recovery' option, it will stuck with the 'X' nexus icon.
craigacgomez said:
try flashing the stock recovery image...
Click to expand...
Click to collapse
Where can i find the stock recovery image?
If you used superboot to root try these instructions.
http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
When i try to run the command, i will hit the 'FAILED (remote: not allowed)' error.
'
>fastboot flash recovery recovery-RA-nexus-v1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
'
jerrycycle said:
If you used superboot to root try these instructions.
http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
Click to expand...
Click to collapse
Did you save the recovery image to the superboot folder?
jerrycycle said:
Did you save the recovery image to the superboot folder?
Click to expand...
Click to collapse
Yup.
D:\Downloads\Nexus One\ROM\1.0-EPE54B-nexusone-insecure>fastboot-windows.exe flash recovery recovery-RA-nexus-1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
Just try this. I know with the mt3g it worked a few time. Try to erase the recovery partition (IE: fastboot erase recovery). This will erase the recovery image. THEN immediately after reflash the recovery (IE: fastboot flash recovery <PATH TO Amon_RA1.0.7>)....Report back your findings
I AM NOT RESPONSIBLE FOR FURTHER PROBLEMS!!!! YOU UN-LOCKED AND ARE PERFORMING THIS AT YOUR OWN RISK!!!
Hi,
Still hitting the 'FAILED (remote: not allowed)' error.
"
>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
"
martin0285 said:
Just try this. I know with the mt3g it worked a few time. Try to erase the recovery partition (IE: fastboot erase recovery). This will erase the recovery image. THEN immediately after reflash the recovery (IE: fastboot flash recovery <PATH TO Amon_RA1.0.7>)....Report back your findings
I AM NOT RESPONSIBLE FOR FURTHER PROBLEMS!!!! YOU UN-LOCKED AND ARE PERFORMING THIS AT YOUR OWN RISK!!!
Click to expand...
Click to collapse
no clue then man. I mean you said your un-locked and all, ARE YOU POSITIVE? In fastboot it says "Un-locked"?? Just first time i've seen this on here.....not sure what it could be....+ I have limited android skills (sadly).....
acidash said:
Where can i find the stock recovery image?
Click to expand...
Click to collapse
When my recovery went bonkers, I used a stock recovery image to fix the issue.
http://autisticpig.com/android/roms and flashes/PASSIMG_Passion_/recovery.img
Give that a try and see if things aren't more normal.
I guess it somehow lost its root access and now my nexus one is useless until i can get hold of a goldcards.
;(
martin0285 said:
no clue then man. I mean you said your un-locked and all, ARE YOU POSITIVE? In fastboot it says "Un-locked"?? Just first time i've seen this on here.....not sure what it could be....+ I have limited android skills (sadly).....
Click to expand...
Click to collapse
Thanks. It hit the 'FAILED (remote: not allowed)' error again.
deprecate said:
When my recovery went bonkers, I used a stock recovery image to fix the issue.
http://autisticpig.com/android/roms and flashes/PASSIMG_Passion_/recovery.img
Give that a try and see if things aren't more normal.
Click to expand...
Click to collapse
acidash said:
Where can i find the stock recovery image?
Click to expand...
Click to collapse
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)
craigacgomez said:
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)
Click to expand...
Click to collapse
+1 for this
Tried the 'PASSIMG.zip' method, and it says Update Partition Fails.
Now i cannot even power it up.
craigacgomez said:
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)
Click to expand...
Click to collapse
Try getting a warranty/RMA for your device. There is something larger going on here than the fact the phone is unlocked...you should be able to flash recovery even if that partition is hosed.
actually, does anyone know a means to format just the partition recovery resides?
Oh wait..you said it won't power on...
Give HTC a ring; it may be your only recourse unless you can get your phone back on.
yup. Since i cannot even power it on, HTC is my only option.
Thanks all for all the guides.
deprecate said:
Try getting a warranty/RMA for your device. There is something larger going on here than the fact the phone is unlocked...you should be able to flash recovery even if that partition is hosed.
actually, does anyone know a means to format just the partition recovery resides?
Oh wait..you said it won't power on...
Give HTC a ring; it may be your only recourse unless you can get your phone back on.
Click to expand...
Click to collapse
Attempted my first root and ROM flash.
Followed HTC Holiday Superguide instructions (I did skip the S-OFF bit) then tried to flash CyanogenMod 10 using these instructions. Got stuck on the CyanogenMod flash screen. Don't quite remember what I did in my panicked attempts to recover. I did relock the bootloader at some point.
Now the phone continually boots to HBoot.
Can't find the RUU I need anywhere (Telstra 3.44.841.3).
Should I return to Apple in shame having found myself not man enough for rooted Androids? Or can someone help me regain some self-respect?
Did you flash the boot.img using fastboot?
Spectrejester said:
Did you flash the boot.img using fastboot?
Click to expand...
Click to collapse
Yes, I did.
SaintBen said:
Yes, I did.
Click to expand...
Click to collapse
Are you able to boot into recovery ? if so does it just flash for a sec the go back to Hboot ?
esloan said:
Are you able to boot into recovery ? if so does it just flash for a sec the go back to Hboot ?
Click to expand...
Click to collapse
When I choose RECOVERY, it displays the HTC logo while a status bar fills up, then it goes back to HBoot.
SaintBen said:
When I choose RECOVERY, it displays the HTC logo while a status bar fills up, then it goes back to HBoot.
Click to expand...
Click to collapse
Okay so you no longer have a custom recovery installed ? Is your HBOOT still locked ? If it is still locked unlock it and Flash TWRP or WCX recovery and see if you can boot into recovery.
esloan said:
Okay so you no longer have a custom recovery installed ? Is your HBOOT still locked ? If it is still locked unlock it and Flash TWRP or WCX recovery and see if you can boot into recovery.
Click to expand...
Click to collapse
It is still locked, but can I flash TWRP or WCX without having access to the phone's internal SD card through Windows? I don't know how to get them on there without that (when I connect the phone to my PC, I don't get the option anymore).
SaintBen said:
It is still locked, but can I flash TWRP or WCX without having access to the phone's internal SD card through Windows? I don't know how to get them on there without that (when I connect the phone to my PC, I don't get the option anymore).
Click to expand...
Click to collapse
No SDCARD ?
Either way you can have the recovery saved to some place on your PC and flash it to the phone. In HBOOT you should select fastboot USB and this will allow you to send fastboot commands to the phone. EX fastboot flash recovery recovery.img to flash a recovery.
esloan said:
No SDCARD ?
Click to expand...
Click to collapse
No, I haven't bought one.
esloan said:
Either way you can have the recovery saved to some place on your PC and flash it to the phone. In HBOOT you should select fastboot USB and this will allow you to send fastboot commands to the phone. EX fastboot flash recovery recovery.img to flash a recovery.
Click to expand...
Click to collapse
Okay, thanks, but it failed.
fastboot flash recovery wcxrecovery.img
sending 'recovery' (6996 KB)... OKAY [ 1.395s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.066s
Any suggestions?
SaintBen said:
Okay, thanks, but it failed.
fastboot flash recovery wcxrecovery.img
sending 'recovery' (6996 KB)... OKAY [ 1.395s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.066s
Any suggestions?
Click to expand...
Click to collapse
HBOOT still locked ?
esloan said:
HBOOT still locked ?
Click to expand...
Click to collapse
Yes, it was, so I unlocked and successfully ran fastboot flash recovery wcxrecovery.img. What do you think I should do now?
SaintBen said:
Yes, it was, so I unlocked and successfully ran fastboot flash recovery wcxrecovery.img. What do you think I should do now?
Click to expand...
Click to collapse
Can you boot into recovery ?
esloan said:
Can you boot into recovery ?
Click to expand...
Click to collapse
Sorry, I realised after I posted my last reply that you said I should try that earlier, I but had to wait five minutes before XDA would let me post again.
Yes, I can now boot into recovery. What next?
SaintBen said:
Sorry, I realised after I posted my last reply that you said I should try that earlier, I but had to wait five minutes before XDA would let me post again.
Yes, I can now boot into recovery. What next?
Click to expand...
Click to collapse
Your set.. you should be able to flash your rom of choice and fastboot flash boot boot.im (I'm assuming your not S-OFF) and then the phone will boot up like it should. The boot.img file will be located in the ROM zip but you may have to push modules around to get wifi to work depending on the ROM.
esloan said:
Your set.. you should be able to flash your rom of choice and fastboot flash boot boot.im (I'm assuming your not S-OFF) and then the phone will boot up like it should. The boot.img file will be located in the ROM zip but you may have to push modules around to get wifi to work depending on the ROM.
Click to expand...
Click to collapse
Okay, I'll have another crack at it, then. Thanks very much, esloan. I really appreciate your help.
Well, I haven't managed to get anywhere. I've tried flashing a couple of different ROMs, but I couldn't get them to boot. When I boot into recovery, I get a bunch of "Can't mount" notifications. Is that bad?
Did you start with clockworkmod?
If so...
Boot to recovery...
Mount via USB(in the mount menu)
Hook to windows...
Let windows format it...
Try again
CWM has a problem with formatting/wiping
Sent from my Vivid 4G using Tapatalk 2
rignfool said:
Did you start with clockworkmod?
If so...
Boot to recovery...
Mount via USB(in the mount menu)
Hook to windows...
Let windows format it...
Try again
CWM has a problem with formatting/wiping
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
No, I haven't used CWM.
Did you use factory reset from the hboot menu then?
Sent from my Vivid 4G using Tapatalk 2
I have non-dev Verizon Moto X 4.4.2 unlocked using the chinese method.
I'm in fastboot right now and it says "Device is UNLOCKED. Status Code: 3" if that means anything.
Every time I tried to flash TWRP and I reboot to recovery...it's still the stock android recovery.
I also tried to erase the stock recovery but i get this message:
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.094s
My motox is unlocked..so why doesn't it say permission denied and why can't i flash a custom recovery??
please help.
I'm not root btw.
Did you go into TWRP after flashing it?
You have to boot straight to recovery or it gets written over by the stock recovery
bigv5150 said:
You have to boot straight to recovery or it gets written over by the stock recovery
Click to expand...
Click to collapse
i thought i did but it boot straight into the OS instead of recovery...let me try again...
*edit*
ok wow i guess i didn't do it when i thought i did but i'm in TWRP now.
Thank you guys!
You probably hit the power button instead of volume+ the first time around.
Hey guys,
This morning I tried flashing Viper's ROM to my HTC One with ClockworkMod Recovery but it failed. I rebooted my phone but it just took me to the Bootloader screen, so I rebooted again but the the same thing happened. I tried to go into recovery but it didn't let me so I flashed TWRP Recovery to do a Nandroid backup. When I tried to do a Nandroid backup it didn't do anything. I tried a couple of times but to no avail. I've been trying to flash roms through fastboot but it doesn't let me, it tells me that "Target reported max download size of xxxxxxxxxxxx bytes error: cannot load "rom": No error. I've been stuck ever since.
Xritke said:
Hey guys,
This morning I tried flashing Viper's ROM to my HTC One with ClockworkMod Recovery but it failed. I rebooted my phone but it just took me to the Bootloader screen, so I rebooted again but the the same thing happened. I tried to go into recovery but it didn't let me so I flashed TWRP Recovery to do a Nandroid backup. When I tried to do a Nandroid backup it didn't do anything. I tried a couple of times but to no avail. I've been trying to flash roms through fastboot but it doesn't let me, it tells me that "Target reported max download size of xxxxxxxxxxxx bytes error: cannot load "rom": No error. I've been stuck ever since.
Click to expand...
Click to collapse
You need to do a sideload thru recovery. Hookup a usb cable and have the Rom you wish to install on your computer.
Sent from my HTC One Max using Tapatalk!
Do I install it through the "fastboot flash rom.zip" command?
Xritke said:
Do I install it through the "fastboot flash rom.zip" command?
Click to expand...
Click to collapse
While booted to recovery try
Code:
adb sideload ROMname.zip
or
adb push ROMname.zip /sdcard/
I always have issues with sideload so if things go south I use adb push
Tried to do adb sideload and adb push but a bunch of commands and their explanations come up
Xritke said:
Tried to do adb sideload and adb push but a bunch of commands and their explanations come up
Click to expand...
Click to collapse
Sounds like you are running the commands from the wrong folder...use the platform tools folder
Followed this: https://www.youtube.com/watch?v=f1YiI-ZZGBs
Still cmd gives me all those command things.
Xritke said:
Followed this: https://www.youtube.com/watch?v=f1YiI-ZZGBs
Still cmd gives me all those command things.
Click to expand...
Click to collapse
Try this guide everything you need is there
http://forum.xda-developers.com/showthread.php?t=2503646
I installed viper rom but now it just keeps restarting when it gets to the home screen. :/
Xritke said:
I installed viper rom but now it just keeps restarting when it gets to the home screen. :/
Click to expand...
Click to collapse
Sounds like you flashed a GSM rom at some point whiched messed up your partitions.
Follow the guide I posted above it will get you fixed up.
BD619 said:
Sounds like you flashed a GSM rom at some point whiched messed up your partitions.
Follow the guide I posted above it will get you fixed up.
Click to expand...
Click to collapse
I did the same thing, the above guide works.
Thanks for all your help guys, I finally got it to boot up and not restart. I just need to sim unlock the phone again.
C:\Users\Jimmy\Downloads\HTCOne
sending 'zip' (1173999 KB)...
OKAY [ 45.045s]
writing 'zip'...
(bootloader) signature checking
FAILED (remote: 12 signature ve
finished. total time: 196.824s
how get out with this problem my device is stuck at boot loader n I locked boot loader
---------- Post added at 12:15 PM ---------- Previous post was at 12:13 PM ----------
C:\Users\Jimmy\Downloads\HTCOne
sending 'zip' (1173999 KB)...
OKAY [ 45.045s]
writing 'zip'...
(bootloader) signature checking
FAILED (remote: 12 signature ve
finished. total time: 196.824s
I to e out of this problem my bootloader is locked and I get out from boot loader
I am trying to go through the process of flashing a custom recovery so that I can get off of stock and on to a custom rom. I have gone through the following steps:
1) downloaded the latest drivers
2) downloaded the latest version of fastboot
3) downloaded twrp 2.8.1.0 and checked the MD5 for the program
4) enabled the usb debugging, signed on as an administrator in my pc, and am using a 2.0 usb port
5) have verified the conenction between tablet and PC.
I get the following result:
C:\>fastboot devices
15C3E100910000000XXXXXXXX fastboot (I edited out a few numbers and replaced them with with x's, but got a pure result)
C:\>fastboot -i 0x0B05 flash recovery twrp.blob
target reported max download size of 643825664 bytes
sending 'recovery' (7024 KB)...
OKAY [ 0.964s]
writing 'recovery'...
OKAY [ 0.241s]
finished. total time: 1.213s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
The recovery is not actually flashing over to the device. When I attempt the flash I do a fastboot reboot and power down afterwards, then try to boot back up to the recovery and instead I get the bried vision of the android and the blue bar underneath before it's promptly replaced by the dead android. The twrp.blob file is in the same directory as fastboot. I have tried deleting and re-downloading both the blob file and the drivers. I have tried using 2.8.0.1 and 2.8.1.0. Because TWRP wasn't working I tried flashing CWM and got exactly the same result. There doesn't seem to be an issue with the cable, since I can move other forms of data between the devices with no issue. I'm beating my head against the wall here, and am hoping that you guys might be able to provide me with some direction as to what else I might try/look for. Thanks all.
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Sleeepy2 said:
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Click to expand...
Click to collapse
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
talion777 said:
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
Click to expand...
Click to collapse
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Sleeepy2 said:
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Click to expand...
Click to collapse
Thanks Sleeepy, but as I mentioned in the OP I did the flash for the CWM recovery already, using exactly the link you sent me, with the exact same commands, and with the same results. No go.
P.P.S. - also tried juggling around the MTP and PTP modes (plug/unplug while on/off) to ensure recognition and it seems fine both ways. Someone else had said they freed up their drivers that way but it made no difference on my end.
P.S. - Here, just so that you see, here are the command window results for th CWM recovery, just for clarity's sake:
C:\adb 2>fastboot devices
15C3E100910000000XXXXXXXX fastboot
C:\adb 2>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (6646 KB)...
OKAY [ 0.910s]
writing 'recovery'...
OKAY [ 0.230s]
finished. total time: 1.140s
C:\adb 2>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb 2>
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Sleeepy2 said:
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Click to expand...
Click to collapse
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
talion777 said:
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
Click to expand...
Click to collapse
The temp image will work just like normal.
Sleeepy2 said:
The temp image will work just like normal.
Click to expand...
Click to collapse
except that I will always need to be connected to my PC to use it. How do I actually make that the default recovery in my tablet? It just seems bizarre to me that I can boot the image but that I can't flash it. Also, assuming I used the image to flash a custom ROM what happens when the temp image is shut off and the recovery reverts to stock? Would the ROM work with a stock recovery?
Was able to use the CWM image to install SuperSU and root the tablet. Still can't get the recovery to flash over.
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Sleeepy2 said:
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Click to expand...
Click to collapse
I'm on 11.4.1.17, and yes I'm on the latest ASUS update.
Damn... that was my last guess. You need to get the attention of someone smarter than me like pershoot or berndblb
Sorry I can't help any better.
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
talion777 said:
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
Click to expand...
Click to collapse
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
You sir, would appear to be a genius. CWN successfully flashed to the tab. Excellent! Thanks so very much to both you and Sleeepy for your help. This was driving me absolutely bananas!
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Sleeepy2 said:
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Click to expand...
Click to collapse
A lucky guess.. LOL
Actually I worked with talion on the Transformer forums on his problem, so it was not quite as magical as it may sound. [emoji56]