Upgraded my bootloader to 10.6.1.14.10 with WW_epaduser10_6_1_14_10_UpdateLauncher thru TWRP recovery. I was running CROMi-X_ODEX_5.4_Signed and now I cant flash the TWRP recovery again or any recovery, Fastboot keeps saying cannot open TWRP.blob and my device is still unlocked. I tried to unlock again using the Asus unlock tool but it just gives me an error. So now I cant flash any recovery and I also tried to just install Su with Mototchopper but it wont install the binary for Su. I attached a copy of my log cat if thats any help
glennd said:
Upgraded my bootloader to 10.6.1.14.10 with WW_epaduser10_6_1_14_10_UpdateLauncher thru TWRP recovery. I was running CROMi-X_ODEX_5.4_Signed and now I cant flash the TWRP recovery again or any recovery, Fastboot keeps saying cannot open TWRP.blob and my device is still unlocked. I tried to unlock again using the Asus unlock tool but it just gives me an error. So now I cant flash any recovery and I also tried to just install Su with Mototchopper but it wont install the binary for Su. I attached a copy of my log cat if thats any help
Click to expand...
Click to collapse
What command are you using to flash recovery and what is the error you are getting?
sbdags said:
What command are you using to flash recovery and what is the error you are getting?
Click to expand...
Click to collapse
fastboot -i 0x0b05 flash staging twrp.img
and fastbboot says Error: cannot open twrp.blob
The error from the unlock app v7 says there maybe a connection error please try again later
glennd said:
fastboot -i 0x0b05 flash staging twrp.img
and fastbboot says Error: cannot open twrp.blob
The error from the unlock app v7 says there maybe a connection error please try again later
Click to expand...
Click to collapse
If you are/were running cromi-x then you are unlocked. You cannot relock so no use in trying to keep unlocking it
Use this command - make sure that the twrp.img is in the same folder as fastboot.
Code:
fastboot -i 0x0B05 flash recovery twrp.img
fastboot -i 0x0B05 reboot-bootloader
Related
Basically, my xoom has been rooted and currently I have CynogenMod9 RC0 Wingray currently installed.
I wanted to install a new rom but I couldn't do this using CWM Recovery as the SD Card doesn't Mount. Upon doing some reading I found I need to install the Rogue (or EOS) Recovery image. This is where my problems begin as I can connect to the device when the xoom is fully booted in the CM9 and connected via debugging mode(running adb devices returns a sequence of numbers ).
But then when I reboot into the bootloader it gets stuck on "Starting Fastboot protocol support." and i can't connect via adb!!!
I believe this started happening after I unlocked the bootloader but i can't be 100% sure (fastboot oemunlock)
Please help!!!
When it is on fastboot mode you can only use fastboot commands (fastboot flash recovery recovery.img) that is how you would install the recovery image from rogue or EOS or TWRP, whichever you choose.
Or to make it easier, you can boot your tablet, install GOO Manager. When you open the GOO manager, tap the setting in the top right corner and choose Install Open Recovery script and let it install TWRP. Then boot to recovery.
Sent from my SGH-I747 using xda premium
d3athsd00r said:
When it is on fastboot mode you can only use fastboot commands (fastboot flash recovery recovery.img) that is how you would install the recovery image from rogue or EOS or TWRP, whichever you choose.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
But it never gets into fastboot mode now.
miahmad said:
But it never gets into fastboot mode now.
Click to expand...
Click to collapse
You specifically said it says starting fastboot protocol. That's as far as it goes. You then issue fastboot commands, not adb commands
Sent from my SGH-I747 using xda premium
Moved to Q & A.
Sent from my Galaxy Nexus using Tapatalk 2
d3athsd00r said:
You specifically said it says starting fastboot protocol. That's as far as it goes. You then issue fastboot commands, not adb commands
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Ohh ok, makes sense. I will give it a try later when i'm home. Is there a Fastboot command i can use to check the device is connected??
miahmad said:
Ohh ok, makes sense. I will give it a try later when i'm home. Is there a Fastboot command i can use to check the device is connected??
Click to expand...
Click to collapse
fastboot devices
miahmad said:
Basically, my xoom has been rooted and currently I have CynogenMod9 RC0 Wingray currently installed.
I wanted to install a new rom but I couldn't do this using CWM Recovery as the SD Card doesn't Mount. Upon doing some reading I found I need to install the Rogue (or EOS) Recovery image. This is where my problems begin as I can connect to the device when the xoom is fully booted in the CM9 and connected via debugging mode(running adb devices returns a sequence of numbers ).
But then when I reboot into the bootloader it gets stuck on "Starting Fastboot protocol support." and i can't connect via adb!!!
I believe this started happening after I unlocked the bootloader but i can't be 100% sure (fastboot oemunlock)
Please help!!!
Click to expand...
Click to collapse
These are what i use from day 1
INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
---------------------------------------------------------------------------------------------------------------------
Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6-softkeys.img
fastboot flash recoverytwrp-2.2.1-stingray_cdma.img
fastboot reboot
adb reboot recovery
-------------------------------------------------------------------------------------------------------------------------
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
this is solved ... by wiping through adb..
adb reboot bootloader
fastboot flash bootloader bootloader-crespo-********.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-********.img
fastboot reboot-bootloader
fastboot -w update image-********.zip
i did this steps but messed up big time at the end.. instead of "fastboot -w update " i did not put -w , before realizing it i already hit the enter button.. need help here.. i tried reflashing back to ics404...but i get the unknown partition error.. what do i do? HELP!!!
similiar errors
Im trying to root, flash boot loader, flash recovery, flash roms, these are the error messages I get when using nvflash tools. Any ideas??
Mario Christian Oquias said:
this is solved ... by wiping through adb..
adb reboot bootloader
fastboot flash bootloader bootloader-crespo-********.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-********.img
fastboot reboot-bootloader
fastboot -w update image-********.zip
i did this steps but messed up big time at the end.. instead of "fastboot -w update " i did not put -w , before realizing it i already hit the enter button.. need help here.. i tried reflashing back to ics404...but i get the unknown partition error.. what do i do? HELP!!!
Click to expand...
Click to collapse
obserrano86 said:
Im trying to root, flash boot loader, flash recovery, flash roms, these are the error messages I get when using nvflash tools. Any ideas??
Click to expand...
Click to collapse
Not familiar with nv tools.. its better to use adb Instead
My TF300T will only boot into TWRP. I also can't access any storage (failed to mount error) and adb sideloading fails everytime so I can't flash the stock rom. I tried using these commands:
adb shell mount -t tmpfs none /sdcard
adb push ROM.zip /sdcard
Which let me reach the .zip file it still failed to flash.
The tablet had Jellybean 4.2.2 installed. The TWRP version is 2.6.3.0.
How do I fix this?
Reboot it into bootloader menu. If holding volume down and power buttons doesn't work try 'adb reboot bootloader' command while tablet in twrp. Then flash rom through fastboot.
Graiden05 said:
Reboot it into bootloader menu. If holding volume down and power buttons doesn't work try 'adb reboot bootloader' command while tablet in twrp. Then flash rom through fastboot.
Click to expand...
Click to collapse
Now I can get to fastboot, but if I try to flash anything the cmd window says it worked but all it really does is freeze the tablet.
dewdrop623 said:
Now I can get to fastboot, but if I try to flash anything the cmd window says it worked but all it really does is freeze the tablet.
Click to expand...
Click to collapse
Did You flash rom or recovery? And does blue progressbar appears?
Graiden05 said:
Did You flash rom or recovery? And does blue progressbar appears?
Click to expand...
Click to collapse
I was able to flash cwm recovery. So now instead of booting into twrm everytime I get stuck on the splash screen. That didn't really change anything
I tried fastboot -i 0x0b05 flash system boot.blob (the .blob file from the stock rom), and I got the blue progress bar then rebooted but I'm still stuck on the first splash screen.
You do it wrong. So if Your last working firmware was 4.2 You need download this rom from asus webpage. Then unzip it twice and You get blob file. Then flash it with 'fastboot -i 0x0b05 flash staging blob' command.
Graiden05 said:
You do it wrong. So if Your last working firmware was 4.2 You need download this rom from asus webpage. Then unzip it twice and You get blob file. Then flash it with 'fastboot -i 0x0b05 flash staging blob' command.
Click to expand...
Click to collapse
Thanks. That worked. However now I'm only back where I started. CWM give can't mount error and can't reach a zip file. ADB sideload doesn't work either(failed to write data 'protocol fault (no status)'). I tried TWRP once and that's the reason I had to post hear in the first place.
dewdrop623 said:
Thanks. That worked. However now I'm only back where I started. CWM give can't mount error and can't reach a zip file. ADB sideload doesn't work either(failed to write data 'protocol fault (no status)'). I tried TWRP once and that's the reason I had to post hear in the first place.
Click to expand...
Click to collapse
Did You try only TWRP v2.6.3.0? I use v2.5.0.0 and its work fine. About CWM: flatline cwm for 4.2 bootloader was created with purpose do nvflash backup, so may be here is the cause of not working others functions.
Graiden05 said:
Did You try only TWRP v2.6.3.0? I use v2.5.0.0 and its work fine. About CWM: flatline cwm for 4.2 bootloader was created with purpose do nvflash backup, so may be here is the cause of not working others functions.
Click to expand...
Click to collapse
Success. Thanks for the help.
I unlocked the bootloader and flashed latest twrp using xt1032 img
when I try to go to recovery I get a " ! no command "
I have flashed it and reflashed it and cmd prompt says okay like it was successful???
help Confused
The no command screen is stock recovery. Try and run fastboot OEM unlock again
Also after you flash you must go straight into recovery or else when you do a normal power up the ROM will overwrite twrp.
hi all, i have tried to return to stock rom from cm 13 following the instruction from the nvida site. I rebooted the shield in fastboot, my device is already unlocked, but when i write the command flash-all.bat in the minimal adb and fastboot for flashing recovery.img system.img .... the program says "error: cannot load recovery.img" and it asks me to exit.
Solutions?
ravazz said:
hi all, i have tried to return to stock rom from cm 13 following the instruction from the nvida site. I rebooted the shield in fastboot, my device is already unlocked, but when i write the command flash-all.bat in the minimal adb and fastboot for flashing recovery.img system.img .... the program says "error: cannot load recovery.img" and it asks me to exit.
Solutions?
Click to expand...
Click to collapse
You have to explicitly state the location. Ie:
Fastboot flash recovery c:\locationoffile\twrp.img
Sent from my SHIELD Tablet K1 using Tapatalk
It is working! thanksss!!