After trying to flash TWRM img from flashify I get an "unrecoverable bootloader error 0x00000000" I have tried to flash CWM by the same method, with no avail, PLEASE HELP. I can acess CM11 though,and root is still good. the only thing not working is recover
kansasboy001 said:
After trying to flash TWRM img from flashify I get an "unrecoverable bootloader error 0x00000000" I have tried to flash CWM by the same method, with no avail, PLEASE HELP. I can acess CM11 though,and root is still good. the only thing not working is recover
Click to expand...
Click to collapse
I'm sorry I don't have time to post links right now but try to download and install flashboot. If you get that far, you can then download almost any recovery solution and see if you can flash it. I believe the command will be:
Code:
Fastboot -i 0x0B05 flash recovery <file location>
Please read up a bit before you try this. It should flash just the recovery so it shouldn't intefer with the OS or root. Please use caution and read, read, read on the topics (fastboot, TWRP, CWM.)
-Tony
This is the ONLY solution for this problem, worked great for me.
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Hey I just got a tf300 for cheap and decided to put a rom on it. I got twrp installed and got root access. The version of twrp was too old and when I updated it and got into twrp I was prompted for a password. I figured something was wrong with the version of twrp I installed and I could go go back to the previous version of twrp by using fastboot but I am unable to get into fast boot.
I hold power and volume down but it boots right into twrp. I'm not able to get it to boot normally either it just boots into twrp. Has anybody run into this or have any ideas why I can't get power + volume down to bring up the recovery menu?
EDIT: Oh and adb doesn't see any devices either.
EDIT #2: It seems that my pc kind of recognizes that something is installed. It shows up on Device Manager as "Transformer" with the yellow exclamation point. I haven't been able to find any drivers that work with it. Anyone have a link?
EDIT #3: Ok I forced the universal naked drivers to install and adb devices now shows tf300 in recovery. When I put in adb reboot bootloader it comes up with the rck android and wipe data. I used fastboot to load my original twrp blob that was working fine. I get:
I:\tf300>fastboot -i 0x0b05 f
sending 'recovery' (6448 KB).
OKAY [ 1.895s]
writing 'recovery'...
OKAY [ 2.862s]
finished. total time: 4.757s
But when I go into recovery its still the version of twrp that was causing issues and it still asks for a password.
I figured i'd do a fastboot erase of boot, cache, recovery, system, userdata and then fastboot the original twrp blob but I get:
I:\tf300>fastboot erase boot
< waiting for device >
EDIT #4: It seems that adb recognizes by device but fastboot does not. Entering fastboot devices returns blank. Anyone know if this is an issue with the driver?
Anyone?
Ok after a couple of hours of hair pulling I figured it out.
Fastboot was definitely not working witht tf300 due to drivers. Since I couldn't find any drivers for windows. I booted up my trusty linux server, installed android-tools-fastboot and voila sudo fastboot devices shows the tf300t.
Reloading twrp did not work so I tried formatting the partitions by doing the following:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc (The first couple of times I did this, I missed this one which caused bootloader to hang when installing twrp)
fastboot erase cache
I then installed the working version of twrp I had originally by:
fastboot –i 0x0b05 flash recovery twrp.blob
I then rebooted into recovery and twrp works great without any password prompt or errors that it could not access the partitions.
I user twrp to flash 2.7.01 version of twrp and rebooted, I then used twrp to flash CM11 snapshot M7 and gapps, cleared cache and davlik and then rebooted.
The CM spinning animation took a while but then it booted into CM.
The topics I got all this info from are too numerous to mention. I hope this helps anyone that has ran into the same situation.
Hi Guys,
Yesterday I installed the new TWRP 2.7.1.0. and that is when the problems started. Everytime when i loaded TWRP my screen got messed up and i got a split screen (At that time my ROM worked). So I tried to get back to a older TWRP, after a couple of tries i finally installed 2.4.4.0. But then I couldn't acces my internal memory nor my sdcard through TWRP(The ROM still worked fine). So i tried CWM, other TWRP's, still the same issue. To keep the story short, I eventually pressed on the WIPE button in Recovery ... And now I am stuck in TWRP. I can't load any zip files.. Is there any hope?
Tab: TF300T
A small update. After some trial and error i got my rom running again and i can also get in to recovery (Power button + volume down). Now I have erased the old TWRP with "fastboot erase recovery". But now I can't install a new recovery? I tried flashing a recovery and I am getting the messages "sending recovery ok", "writin recovery ok". But i don't see the loading bar on the tab...
I feel lonely here hehe.:laugh:
I resolved the issue and got my tablet running again, with the following steps:
Download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
http://support.asus.com/download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T&os=8
Install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
If the PC doesn't recognize your tab, then try installing the universal naked drivers:
http://forum.xda-developers.com/showthread.php?t=2263822
Guide: http://forum.xda-developers.com/showthread.php?t=2139767
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
All credits to - Buster http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Hello,
I have a Motorola Moto G XT1032 on which I have successfully unlocked the bootloader. I can access to recovery (CWM 6.0.4.7) and transfer files using adb in this mod. However, CWM does not get past the splash logo (I do get the occasionnal lag when CWM rebuilds the cache, but this is another minor issue). I have tried the following ROMs, installed each after formatting /system, /data and /cache:
cm-11-20140308-SNAPSHOT-M4-falcon.zip
cm-11-20140405-SNAPSHOT-M5-falcon.zip
cm-11-20140504-SNAPSHOT-M6-falcon.zip
cm-11-20140613-NIGHTLY-falcon.zip
cm-11-20140730-NIGHTLY-falcon.zip
cm-11-20140823-NIGHTLY-falcon.zip
None worked. I did checked the md5 checksums. I have also tried installing GApps using gapps-kk-20140606-signed.zip .
I do not know how to get more information on what happens when CM11 stucks during the boot. 'Show log' from recovery only prints some configuration information as well as:
Code:
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
From what I undersood, extendedcommand is an optional executable used to launch stuff at boot.
I found some ideas from another thread and tried locking/unlocking oem:
Code:
$ fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.057s]
finished. total time: 0.057s
$ fastboot oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.037s]
finished. total time: 0.037s
$ fastboot oem unlock
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.008s
Additionnally I also reinstalled recovery:
Code:
$ fastboot erase recovery
$ fastboot flash recovery CWM-swipe-6.0.4.7-falcon.img
I did have a message "Mismatched partition size (recovery)" but CWM starts fine. I then reinstalled CM11 again, but it did not help either.
Would you have further instruction to try and get CM11 to work?
Just a short post to avoid the thread from being buried down into oblivion.
Same happened to me days ago. I was unable to install any custom ROM. I was in Enhdroix and I flashed the original version of my ROM via fast boot but every time I tried to install a custom was stocked and bootlogo. Some how I figured that the boot loader of the original version was corrupted so I flashed a different stock ROM, after that was able to install custom.
The recovery message is normal you can check videos or post.
Hope this helps my friend.
To prevent any further problems, I also recommend that you flash twrp or philz recovery because the stock cwm recovery is outdated and it will give you problems while flashing ROMs in the future...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
ThisIsMadness said:
Just a short post to avoid the thread from being buried down into oblivion.
Click to expand...
Click to collapse
Check previous answers
Thanks for your help, I finally got it to work!
If someone gets stuck with the same problem, here is what I did:
first, fastboot flash recovery to TWRP
reinstalling (wipe and so) CM11 from TWRP did not work any better
I reinstalled a stock ROM following http://forum.xda-developers.com/showthread.php?t=2542219
I did not boot at all (no logo), but I could still get to fastboot
I reinstalled TWRP, and then CM11
it worked!
From my own diagnosis, I must have accidentely corrupted a partition with fastboot flash. Or maybe I wiped something that I should not have. Anyway, by reinstalling stock, I restored all the partitions and could install CM11. I do not think CWM is to blame here.
Hi,
I followed Motorola procedure to unlock my G3, but I missed I should have first set "Allow OEM unlock" with a working phone:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
Then my phone was unbootable. I tried "Factory reset" as here:
http://forum.xda-developers.com/showpost.php?p=66521508&postcount=590
Then I ended in a endless animation of Android robot working to erase data at every boot.
The I tried to reflash stock rom (my bootloadre is still locked), using this method:
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
but this line always timed out:
fastboot flash system system.img_sparsechunk.0
I was on 6.0 via OTA.
How can I fix my phone? Only sending it to Motorola will solve?
Thanks
So you didn't have OEM Unlocking enabled and you tried to unlock? It should have just said "Nuh uh, not gonna do it" and you could reboot and go.
You probably didn't need to flash anything, just factory reset and WAIT... a factory reset on the Moto G3 can take 10-20 minutes to complete, then the first boot can be 10, 15, even 20 minutes of panic... you just have to be patient.
Problem is now you have started a flash process, but it sounds like you not in oem fb_mode because your sparcechunks are not taking... You need to slow down and start over, and make sure you have a complete firmware image and are following these instructions EXACTLY.
It is somewhat difficult to brick a Moto G, although not impossible, chances are in all this there wasn't enough patience... some things this phone does takes a scary amount of time.
Dear acejavelin, thank you for answering.
I tried a factory reset and waited, mainly because I didn't know what to do next...the reset didn't complete in 30 minutes.
Now (and when factory reset didn't complete), I follow exactly the instructions at http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750, including the lines for partition and bootloader:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 <- This always times out after 7200sec, 5000sec, ...
This last step never completed. Then I start again from beginning (from "oem fb_mode_set") with no success.
Also this step:
fastboot erase userdata
times out (once I tried to skip system.img_sparsechunk.0 and go ahead)
Flashing the bootloader works, I tried 1st with bootloader of Android 6.0 and it showed correct version at reboot, and with version 6.0.1.
Now I cannot dowgrade from this level (when flashing boot.img, recovery.img) but always stuck at system.
I think I have lost my phone.
ziko111 said:
Dear acejavelin, thank you for answering.
I tried a factory reset and waited, mainly because I didn't know what to do next...the reset didn't complete in 30 minutes.
Now (and when factory reset didn't complete), I follow exactly the instructions at http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750, including the lines for partition and bootloader:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 <- This always times out after 7200sec, 5000sec, ...
This last step never completed. Then I start again from beginning (from "oem fb_mode_set") with no success.
Also this step:
fastboot erase userdata
times out (once I tried to skip system.img_sparsechunk.0 and go ahead)
Flashing the bootloader works, I tried 1st with bootloader of Android 6.0 and it showed correct version at reboot, and with version 6.0.1.
Now I cannot dowgrade from this level (when flashing boot.img, recovery.img) but always stuck at system.
I think I have lost my phone.
Click to expand...
Click to collapse
Unfortunately, I have to agree... You could try manually erasing and formatting the main partitions before starting.
fastboot erase userdata
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot flash partition gpt.bin
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format boot
Then attempt the factory flash again, at this point it can't hurt anything... Under no circumstances do a fastboot erase all though, if you do might as well throw it in the trash.
Since this problem occurred while attempting to unlock the device, might be worth a shot to post in the official Motorola forums.
ziko111 said:
Dear acejavelin, thank you for answering.
I tried a factory reset and waited, mainly because I didn't know what to do next...the reset didn't complete in 30 minutes.
Now (and when factory reset didn't complete), I follow exactly the instructions at http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750, including the lines for partition and bootloader:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 <- This always times out after 7200sec, 5000sec, ...
This last step never completed. Then I start again from beginning (from "oem fb_mode_set") with no success.
Also this step:
fastboot erase userdata
times out (once I tried to skip system.img_sparsechunk.0 and go ahead)
Flashing the bootloader works, I tried 1st with bootloader of Android 6.0 and it showed correct version at reboot, and with version 6.0.1.
Now I cannot dowgrade from this level (when flashing boot.img, recovery.img) but always stuck at system.
I think I have lost my phone.
Click to expand...
Click to collapse
Which stock rom have you downloaded? What variant of Moto G 2015 do you have?
EvilHowl said:
Which stock rom have you downloaded? What variant of Moto G 2015 do you have?
Click to expand...
Click to collapse
Hi, thank you
I have a moto XT1541 with 1GB RAM/8GB emmc.
I only used rom from xda-developers (http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639).
I first tried with this:
v6.0 - XT1541_OSPREY_RETEU_6.0_MPI24.65-33_cid7
Then I thought v6.0.1 could have been better so,
v.6.0.1 - XT1541_OSPREY_RETEU_6.0.1_MPI24.107-55_cid7
then, since I had a Vodafone EU phone, this one:
v.6.0.1 - XT1541_OSPREY_VFEU_6.0.1_MPI24.107-55-2_cid7
From fastboot getvar all, I still have v 6.0 (flash system always failed):
(bootloader) ro.build.fingerprint[0]: motorola/osprey_vfeu/osprey_umts:6
(bootloader) ro.build.fingerprint[1]: .0/MPI24.65-33/36:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.41.33.osprey_vfeu
(bootloader) ro.build.version.full[1]: .vfeu.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
At any point in the process are you getting a "Pre-flash validation error" or any response other than OK up until the sparcechunk timeout?
acejavelin said:
At any point in the process are you getting a "Pre-flash validation error" or any response other than OK up until the sparcechunk timeout?
Click to expand...
Click to collapse
I get "Pre-flash validation error" only if I try v6.0.
With v.6.0.1 I arrive with all OKs till system.img which hangs.
When I boot, I get "failed to validate system image", also for recovery
ziko111 said:
I get "Pre-flash validation error" only if I try v6.0.
With v.6.0.1 I arrive with all OKs till system.img which hangs.
When I boot, I get "failed to validate system image", also for recovery
Click to expand...
Click to collapse
OK... Next time try
fastboot erase system
fastboot format system
Right before starting the sparcechunks. If that fails, probably bricked.
acejavelin said:
OK... Next time try
fastboot erase system
fastboot format system
Right before starting the sparcechunks. If that fails, probably bricked.
Click to expand...
Click to collapse
#fastboot oem fb_mode_set
OKAY
#fastboot flash partition gpt.bin
OKAY
#fastboot flash bootloader bootloader.img
OKAY
#fastboot flash logo logo.bin
OKAY
#fastboot flash boot boot.img
OKAY
#fastboot flash recovery recovery.img
OKAY
#fastboot erase system
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.104s
# fastboot format system
Formatting is not supported for filesystem with type 'raw'.
Thank you for trying.
Will Motorola be able to recover the phone? Or will they propose to change motherboard for a fool price?
ziko111 said:
#fastboot oem fb_mode_set
OKAY
#fastboot flash partition gpt.bin
OKAY
#fastboot flash bootloader bootloader.img
OKAY
#fastboot flash logo logo.bin
OKAY
#fastboot flash boot boot.img
OKAY
#fastboot flash recovery recovery.img
OKAY
#fastboot erase system
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.104s
# fastboot format system
Formatting is not supported for filesystem with type 'raw'.
Thank you for trying.
Will Motorola be able to recover the phone? Or will they propose to change motherboard for a fool price?
Click to expand...
Click to collapse
Hmm... /system should be ext4, not raw... Since your locked I guess you're kind of screwed. Sorry.
Can you try flashing TWRP again? There is a repair file system option in TWRP>Wipe>Advanced Wipe. You can try that and then start fastboot flashing the stock firmware again, hoping for the best.
BTW, what does it say in the bootloader menu- locked or unlocked? Is the device status official, unofficial or engineering (<- not good)?
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Can you try flashing TWRP again? There is a repair file system option in TWRP>Wipe>Advanced Wipe. You can try that and then start fastboot flashing the stock firmware again, hoping for the best.
BTW, what does it say in the bootloader menu- locked or unlocked? Is the device status official, unofficial or engineering (<- not good)?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
He messed up while unlocking his bootloader. I doubt there's anyway to install TRWP. He's better off sending it to Motorola, they'll fix it since it isn't unlocked yet
firuzmaster said:
He messed up while unlocking his bootloader. I doubt there's anyway to install TRWP. He's better off sending it to Motorola, they'll fix it since it isn't unlocked yet
Click to expand...
Click to collapse
Yes, they will fix it but not under warranty... Once the unlock code is issued the warranty is done.