Related
I have sitting here a Samsun Nexus S from Fido in Canada. From what I can tell that makes it the 9020a.
It belongs to a friend and he really wanted CM7 on it after seeing CM7 on my Nexus One.
I helped him root and unlock the phone along with installing ClockWork Recovery.
I left before getting around to installing the ROM. He downloaded it through the ROM manager. After the phone restarted though he was just presented with the white Google logo and it never moved on.
I am trying to help fix this, but he wiped the sdcard and the backup that was done when ROM Manager did a backup.
Here is the problem though, I have installed about 5 or 6 different recovery ROM's trying to get this to work, even more ROM's themselves.
I have tried combinations of ROM's and recovery ROM's.
All of them end with me staring at a white Google logo.
I have access to fastboot and the recovery ROM still. So I decided to just go back to stock by flashing the partitions from fastboot. Some of them will flash, but others won't. I can flash the cache, but I can't flash the recovery, data, or system partitions. When I try I get
sending 'recovery' (8192 KB).
OKAY [ 1.029s]
writing 'recovery'...
FAILED (remote: Write Fail)
or this for Data
FAILED (remote: Unkown Partition)
or this for System
FAILED (remote: Write Fail)
Any and all help would be greatly appreciated. Right now the phone is basically bricked. I am going to sleep but will check back in the morning. If I left some information out please let me know.
Did you unlock the bootloader?
fastboot oem unlock
Then follow the on screen instructions. I had to do that to flash certain *.imgs. I think it has to do with the security checks....
Sent from my Nexus S using XDA Premium App
Does the white Google logo have a padlock symbol at the bottom of the screen? If not then the bootloader is locked. What root method did you use?
Sent from my Nexus S 4G using xda premium
And also what were the commands you used to flash the images.
Sorry for the late reply. Some stuff at work blew up and kept me out late.
atrixboy:
Yes, the bootloader is unlocked.
Rem3Dy:
Yes, there is a pad lock at the bottom of the screen.
suksit:
The commands run originally was just to unlock the phone (fastboot.exe oem unlock). The phone was then rooted and the OS was launched. Once in the OS RomManager was downloaded and installed. Through RomManager clockwork recovery was installed. After that CM7 was selected as the Rom to install. The phone rebooted, did its thing in recovery, then booted to this black screen with white Google logo which I have yet to get passed.
Since then though I have flashed several different recovery images trying to get this to work, right now the recovery is: CWM-based Recovery v4.0.1.4
If I install a Rom from zip through the recovery it says it was OK, but I still get the white logo and nothing else on boot.
I have been trying to just flash boot and system images at this point and am having no luck.
When I try the following:
C:\1>fastboot.exe flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.032s]
writing 'boot'...
FAILED (remote: Write Fail)
finished. total time: 1.039s
C:\1>fastboot.exe flash system system.img
sending 'system' (151459 KB)...
OKAY [ 19.073s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.078s
C:\1>fastboot.exe flash data data.img
sending 'data' (4 KB)...
OKAY [ 0.002s]
writing 'data'...
FAILED (remote: Unknown Partition)
finished. total time: 0.032s
If I boot the recovery and go into adb and try and mount the same 3 partitions I get the following:
mount /system - works fine
mount /boot - mount: can't find /boot in /etc/fstab
mount /data - this one runs for like 5 minutes and then fails with the following error: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
I just realized that there is some more information on the screen of the device while in fastboot and I try this. When I try "fasboot.exe flash boot boot.img" I get the following on screen:
Exceed blocks 0x00000020 > 0x0000001e (The exact number of zeros may be wrong, hard counting them at that size)
FASTBOOT STATUS - FAILWrite Fail
Fastboot also indicates at the top of the screen: FASTBOOT MODE - NO BOOT OR RECOVERY IMG
I am able to get into the recovery though...
Not sure what other information to include.
I have run out of ideas. Does anyone know where else could I go and get help with this?
are you flashing *.img files in cwm or bootloader mode?
In fastboot I am flashing .img files, from CWM I am trying to flash .zip. I downloaded a nandroid backup and tried restoring that from within CWM with no luck.
try formatting all memory locations except sd card in "mounts & storage" and fix permissions and then flash img files.
What exactly do you mean by "fix permissions" ?
Edit: Stupid question, found it under advanced.
So I formatted each of the partitions, did the fix permissions option, and then booted back into the bootloader and tried to flash the system.img file with fastboot. It failed.
C:\1>fastboot.exe flash system system.img
< waiting for device >
sending 'system' (151459 KB)...
OKAY [ 19.001s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.006s
Thank you in advance for trying to help, I really appreciate it.
Edit: I just realized at the bottom of the bootloader after trying to flash the system.img file it now says in bold orange text:
Invalid Magic Code! 0x00000003
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
litanyoffail said:
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
Click to expand...
Click to collapse
I can mount:
/sdcard
/system
/cache
When I try and mount /data it takes 15 minutes and then fails. Says: Error mounting /data!
The model is most definitively i9020a, I just checked under the battery. Thanks for telling me where that is.
milesman said:
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
Click to expand...
Click to collapse
I did, but I am trying it again now.
So, I tried that Nandroid backup again, and it says MD5 mismatch. I checked the MD5's myself and they match. The ones listed in the MD5 file, and the files match.
I tried flashing the *.img files from fastboot, and get that failed to write message I posted earlier.
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
milesman said:
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
Click to expand...
Click to collapse
Did this, still having the same problems.
Possible the bootloader unlock corrupted guys? Sounds to me like either a bootloader error else the nand may have died. Unlikely but possible. I read somewhere about loading a custom bootloader to the Nexus S. Maybe try looking for that, I know it was here on XDA, only place to get good help IMHO. The orange error codes are generally related to a corrupt bootloader/bad nand chip to the best of knowledge, feel free to correct me if I'm wrong.
Sent from my Nexus S using xda premium
If the nand was shot, data, SD and system wouldn't mount either. I had a busted nand on my nexus last month, had to send it in.
Seems like the bootloader is unlocked, but acting as if it is locked. Do fastboot devices, make sure the numbers match on your screen and your command prompt.
Something I noticed: If the fastboot flash recovery is failing, how did you get the multiple recoveries on prior to posting here?
Sent from my Nexus S
Hi all.
Im having some problems with this, and was hoping that some one here could help me.
I have unlocked my device, no problems.
Then i have installed CWM, no problems.
Now here my problems begin... I have copied a custom ROM zip file, onto my tablet. When i boot my tablet into CWM i get some errors in the bottom of the screen looking like this:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Now when i choose to "- Install zip from sdcard" and after that i choose "- Choose zip file from sdcard" i get this error: E:Can't mount /sdcard/
Then i try to select the "- Choose zip from internal storage" but then i get this error: E:Can't mount /emmc/
Basicly i cant do anything at all in CWM without getting errors, cant even whipe the cache or anything.
Can someone help me to find out what to do now. And hopefully how to solve this?
I can boot into my androind system without any problems.
Hope some one know's what to do. Thank you in advance.
Info:
TF300T
Android 4.2.1
Kernel 3.1.10-g6f31760
CWM-based Revovery v6.0.2.3
If there is anything else you need to know to be able to help me, please ask.
Have a good day.
CWM doesnt work with the 4.2 bootloader from ASUS. Only TWRP for bootloader 4.2 seems to work. You will have to flash TWRP 2.5.0.0-tf300t-4.2. Take note you need the TWRP version with the "-4.2" at the end. Flashing the incorrect TWRP version can brick your tablet.
Download http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
Reboot tablet and hold volume down button while it's powering up to enter fastboot mode. Do not select any of the 3 icons (RCK, Android logo, Wipe Data) on tablet. Connect tablet to PC via USB cable.
On Windows PC, cmd window type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
On tablet, wait until blue progress bar completely fills up.
On Windows PC, cmd window type:
fastboot reboot
That should replace your CWM with TWRP.
Hello ImmovableObject.
Thank you very much for you reply, that was excatly what was wrong.. Stupid me, not checking up on that. I actually flashed another version of TWRP, so i guess i was extreemly lucky that it did not brick my tablet.
But after i flashed the right TWRP its all good, everything is working as intented, and i can make backups and flash custom roms now. Thank you very much for your help
Have a good day all.
Jrod236 said:
Hello ImmovableObject.
Thank you very much for you reply, that was excatly what was wrong.. Stupid me, not checking up on that. I actually flashed another version of TWRP, so i guess i was extreemly lucky that it did not brick my tablet.
But after i flashed the right TWRP its all good, everything is working as intented, and i can make backups and flash custom roms now. Thank you very much for your help
Have a good day all.
Click to expand...
Click to collapse
You are very much welcomed! I'm glad it worked for you.
I found this useful when I was struggling with CWM as well, very glad I was careful to pick the 4.2 blob
Thanks for the help!
Holy Crap!
I can't believe how stupid I was! I ahve always despised CWM yet I was using it on my TF300T. After searching and searching for a fix I came onto this. Great job man!
THANK YOU FOR THIS!! I too stumbled around with CM Recovery for about 30 minutes, dumbfounded by the fact that it couldn't mount either the internal or external storage. I did some research and that's when I came across this post. I can't believe they don't make any mention in any of the tutorials that CM Recovery won't work with the newest 4.2 bootloader from Asus.
Your method did not work with my TF300T, Please assist
@ImmovableObject , I've tried your method but for some reason my Tablet did not reboot with the command "Fastboot reboot" and i still get CWM-based Recovery v6.0.2.3 for recovery instead of TWRP. it did say the flash was OKAY.
Please Please help
ImmovableObject said:
CWM doesnt work with the 4.2 bootloader from ASUS. Only TWRP for bootloader 4.2 seems to work. You will have to flash TWRP 2.5.0.0-tf300t-4.2. Take note you need the TWRP version with the "-4.2" at the end. Flashing the incorrect TWRP version can brick your tablet.
Download http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
Reboot tablet and hold volume down button while it's powering up to enter fastboot mode. Do not select any of the 3 icons (RCK, Android logo, Wipe Data) on tablet. Connect tablet to PC via USB cable.
On Windows PC, cmd window type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
On tablet, wait until blue progress bar completely fills up.
On Windows PC, cmd window type:
fastboot reboot
That should replace your CWM with TWRP.
Click to expand...
Click to collapse
mseck said:
@ImmovableObject , I've tried your method but for some reason my Tablet did not reboot with the command "Fastboot reboot" and i still get CWM-based Recovery v6.0.2.3 for recovery instead of TWRP. it did say the flash was OKAY.
Please Please help
Click to expand...
Click to collapse
That's strange.
Was your tablet running Android 4.2?
Try waiting a little longer (5 or more seconds) before issuing the "fastboot reboot" after the message that the flash was OKAY.
Things you could also try:
* Update your fastboot.exe to the latest version. You can do this via the Android SDK Manager on your computer. Fastboot is included under "Tools" > "Android SDK Platform-tools."
* Use a different USB cable.
* Connect cable to a different USB port on your computer.
ImmovableObject said:
CWM doesnt work with the 4.2 bootloader from ASUS. Only TWRP for bootloader 4.2 seems to work. You will have to flash TWRP 2.5.0.0-tf300t-4.2. Take note you need the TWRP version with the "-4.2" at the end. Flashing the incorrect TWRP version can brick your tablet.
Download http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
Reboot tablet and hold volume down button while it's powering up to enter fastboot mode. Do not select any of the 3 icons (RCK, Android logo, Wipe Data) on tablet. Connect tablet to PC via USB cable.
On Windows PC, cmd window type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
On tablet, wait until blue progress bar completely fills up.
On Windows PC, cmd window type:
fastboot reboot
That should replace your CWM with TWRP.
Click to expand...
Click to collapse
Thank you! Looking for days now. I installed TWRP 2.6 and CWM 5, 6 and touch. All the same problem. Flashed the TWRP from your link and everything works fine. Thank you
Raice.f4h said:
Thank you! Looking for days now. I installed TWRP 2.6 and CWM 5, 6 and touch. All the same problem. Flashed the TWRP from your link and everything works fine. Thank you
Click to expand...
Click to collapse
Hello.
I have TG300TG that only goes to CWM-based recovery v.6.0.1.3 and can not mount sd card. I've tried the mothod described here, but I can't get to fastboot mode. When I hold vol down it only goes to CWM again and again.
ImmovableObject said:
CWM doesnt work with the 4.2 bootloader from ASUS. Only TWRP for bootloader 4.2 seems to work. You will have to flash TWRP 2.5.0.0-tf300t-4.2. Take note you need the TWRP version with the "-4.2" at the end. Flashing the incorrect TWRP version can brick your tablet.
Reboot tablet and hold volume down button while it's powering up to enter fastboot mode. Do not select any of the 3 icons (RCK, Android logo, Wipe Data) on tablet. Connect tablet to PC via USB cable.
On Windows PC, cmd window type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
On tablet, wait until blue progress bar completely fills up.
On Windows PC, cmd window type:
fastboot reboot
That should replace your CWM with TWRP.
Click to expand...
Click to collapse
Hello everyone.
I have same issue even with TWRP recovery 2.5.0.0
First of all when recovery starts i have a password request, don't know why but i press cancel and recovery starts normaly,
But when i select "install" i see internal storage (0 MB), nothing it's recognized into internal SD card.
I really need help for this issue, i'm in your hands guys :crying:
Device: TF300T
ROM: Asus Stock
ultimate_technologies said:
Hello.
I have TG300TG that only goes to CWM-based recovery v.6.0.1.3 and can not mount sd card. I've tried the mothod described here, but I can't get to fastboot mode. When I hold vol down it only goes to CWM again and again.
Click to expand...
Click to collapse
I have the same problem, to actually get back to the bootloader and select RCK or Android do this:
Once CMW is loaded open command and do
adb reboot-bootloader
that also enabled fastboot again but I'm still not able to load TWRP
---------- Post added at 01:50 AM ---------- Previous post was at 01:13 AM ----------
So just like the previous few posts I too installed CWM and I can't reflash TWRP.
Here's the output from the console:
D:\Android SDK\sdk\platform-tools>fastboot -i 0x0B05 flash recovery openrecovery
-twrp-2.5.0.0-tf300t-4.2.blob
sending 'recovery' (6448 KB)...
OKAY [ 2.699s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 4.955s
D:\Android SDK\sdk\platform-tools>fastboot devices
???????????? fastboot
D:\Android SDK\sdk\platform-tools>
Device is unresponsive to any commands and must be rebooted manually. Once I reboot the device loads to the CWM Recovery unless I run "adb reboot-bootloader" and then I can choose to boot the ROM. So at least it's not bricked.
Fix
Found this posted by buster.
So if you're TF300T is booting directly to recovery and you can't get to fastboot do what I post above:
1. Let recovery load
2. With recovery loaded you can now use adb. enter: adb reboot-bootloader
3. You should now be at the bootloader screen (RCK, Android, Wipe screen). Do this:
Originally Posted by Buster99 View Post
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 -i 0x0B05 erase system
fastboot -i 0x0B05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase misc
fastboot -i 0x0B05 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
As Buster said
this was the first time i saw the loading bar while flashing
Click to expand...
Click to collapse
Before flashing I was not able to fastboot reboot-bootloader but this time I was.
Hope this helps
Many Thanks
Raice.f4h said:
Thank you! Looking for days now. I installed TWRP 2.6 and CWM 5, 6 and touch. All the same problem. Flashed the TWRP from your link and everything works fine. Thank you
Click to expand...
Click to collapse
All thanks for this thread, it solved my problem and now am rooted.
Again many thanks,
Gary
twpr is working
flashed twpr v2.5.0.0
works great so far, but it takes a little more time to load than cwm.
help!
right guys, I'm completely green when it comes to stuff like this so apologies if my questions are too daft.
I tried to root my tablet and forgot to back it up, tired few things I found online and got myself in a position where I can't use fastboot as my tablet is taking me to CWM recovery straight away and holding volume key and power makes no difference... any ideas? apart from throwing my table in a bin?
My Nexus 5 is under 2 months old.
I have TWRP flashed.
I also have Cyanogenmod flashed. (11-20130103-SNAPSHOT-M2-hammerhead)
Here's what happened.
Dropped the phone a few weeks back. Ordered a new screen.
Opened up the phone and switched the screen myself without any trouble.
Turned the phone on and everything was great for 2 days.
Then out of the blue the phone turned itself off in my pocket.
Had a hard time getting it to turn back on. Managed to do this a few times when I plugged the charger in.
It booted up normally but after a few hours it would turn off again.
This happened 3 times.
On the 4th time it started turning on normally without any problem but each time it would run the CM setup again.
All this time I was also unable to access the phone's internal storage via the USB. (debugging was turned on).
When the phone finishes the setup it shows that the internal storage is only 128MB.
When I plug the phone in this is what I see.
(see attachment)
When I boot into recovery and try to wipe the phone. This is what it says.
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Does anyone have ANY ideas on what to try?
If there is more info needed about the phone just let me know. I'll get right back to you. I'm here all day.
pahh said:
My Nexus 5 is under 2 months old.
I have TWRP flashed.
I also have Cyanogenmod flashed. (11-20130103-SNAPSHOT-M2-hammerhead)
Here's what happened.
Dropped the phone a few weeks back. Ordered a new screen.
Opened up the phone and switched the screen myself without any trouble.
Turned the phone on and everything was great for 2 days.
Then out of the blue the phone turned itself off in my pocket.
Had a hard time getting it to turn back on. Managed to do this a few times when I plugged the charger in.
It booted up normally but after a few hours it would turn off again.
This happened 3 times.
On the 4th time it started turning on normally without any problem but each time it would run the CM setup again.
All this time I was also unable to access the phone's internal storage via the USB. (debugging was turned on).
When the phone finishes the setup it shows that the internal storage is only 128MB.
When I plug the phone in this is what I see.
(see attachment)
When I boot into recovery and try to wipe the phone. This is what it says.
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Does anyone have ANY ideas on what to try?
If there is more info needed about the phone just let me know. I'll get right back to you. I'm here all day.
Click to expand...
Click to collapse
You might try flashing CWM recovery in fastboot to see if this will solve your issue. Downloadlink http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-hammerhead.img.
gee2012 said:
You might try flashing CWM recovery in fastboot to see if this will solve your issue.
Click to expand...
Click to collapse
How do I go about doing this?
I am unable to download any apps. The Play Store* app crashes as soon as I open it.
And can't store the img file on the internal memory, since I can't access it.
I am able to use adb however.
EDIT: Play Store not AppStore.
What does the appstore have to do with his recommendation?
Sent from Omni Nexus 5
AndroidSlave said:
What does the appstore have to do with his recommendation?
Sent from Omni Nexus 5
Click to expand...
Click to collapse
Did a quick google search on how to flash CWM and one of the guides told me...
"Download and install ROM Manager FREE [Market Link] on your Android device."
The other option was to store it on the internal memory.
Sadly both of these options aren't working for me.
EDIT: Sorry! I meant the Play Store.
You would flash it just like twrp via fastboot
Sent from Omni Nexus 5
AndroidSlave said:
You would flash it just like twrp via fastboot
Sent from Omni Nexus 5
Click to expand...
Click to collapse
This ^^ !!!
I tried flashing the recovery-clockwork-touch-6.0.4.5-hammerhead.img
Here's what I did.
Ran these commands.
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-hammerhead.img
This happened.
sending 'recovery' 11312KB
OKAY
writing 'recovery'...
OKAY
finished.
But the recovery mode still opens up TWRP...
pahh said:
I tried flashing the recovery-clockwork-touch-6.0.4.5-hammerhead.img
Here's what I did.
Ran these commands.
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-hammerhead.img
This happened.
sending 'recovery' 11312KB
OKAY
writing 'recovery'...
OKAY
finished.
But the recovery mode still opens up TWRP...
Click to expand...
Click to collapse
Did you restart bootloader after flash? Just double check now? If still twrp, maybe consider taking it back to stock.
rootSU said:
Did you restart bootloader after flash? Just double check now? If still twrp, maybe consider taking it back to stock.
Click to expand...
Click to collapse
Yes I did. I tried it 3 times. Going to try going back to stock now.
This happened when trying to flash stock...
C:\StockNexus5>fastboot flash bootloader bootloader.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.477s
pahh said:
This happened when trying to flash stock...
C:\StockNexus5>fastboot flash bootloader bootloader.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.477s
Click to expand...
Click to collapse
Looks like it, look here http://www.google.nl/url?sa=t&rct=j...pQhJJwQEs5bFuyY6nYlSRTA&bvm=bv.60983673,d.bGQ and here https://www.google.nl/search?q=FAIL...channel=rcs&gws_rd=cr&ei=xdH4Ut7yHqP_ywO_loAI for more info. You`ll probably have to send it in for repair.
Same problem with my Nexus 5.. Help!!
hey.. i m facing the same problem and got reseted with recovery mode.. nothing happens.. still showing memory 128 MB.. not choosing any network in the cell...
try 'fastboot boot' rather than 'fastboot flash'
Flashboot boot recovery.img. If your phone cannot flash memory it can still boot another recovery image.
Hi I wonder if anyone can help me. My tf700 is running Zombi-Pop 5.1.1-OMNI-DEODEX RC2 . I may have wrecked my recovery and boot-loader. My Infinity is unlocked and rooted and had TWRP 2..7.00 or roughly that. In preparation for installing KatKiss 6.0.1 . I updated TWRP to [RECOVERY] KANG TWRP TF700T [email protected] JAN 4 from within TWRP and it completed ok. When I went to reboot into recovery I got a unable to boot error boot-image is unreadable X000000 or something like that, But I am able to boot the system which seems to be working OK. Does anyone know if the is anyway for me to re-flash a working recovery or am I stuck without a recovery? If anyone can help me with this I would much appreciate it.
Cheers Al-Man
ps. I have read loads of posts but I am still unsure as to what is the best course of action. I don't want to make it totally useless.
Your bootloader is fine or you would not be able to boot Android.
Kang TWRP 2.8.x is fine for any current rom so that is not the problem either.
Did you let the tablet reboot after the recovery flash? Sounds to me as if that was when things went south.
So fastboot flash the recovery, then reboot to system once before you try to boot into recovery.
If you don't know how to fastboot flash it's high time you learned it.
http://forum.xda-developers.com/showthread.php?t=2688891
You could also use flashify or dd commands if you have root.
Sent from my KYOCERA-C6745 using Tapatalk
Tried Fastbbot still no joy
berndblb said:
Your bootloader is fine or you would not be able to boot Android.
Kang TWRP 2.8.x is fine for any current rom so that is not the problem either.
Did you let the tablet reboot after the recovery flash? Sounds to me as if that was when things went south.
So fastboot flash the recovery, then reboot to system once before you try to boot into recovery.
If you don't know how to fastboot flash it's high time you learned it.
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Thanks for your quick reply bernbib. I have tried to fastboot and load a new recovery image. I am able to see the device using the fastboot devices command. When I flash a new TWRP image it shows the following
twrp.img
sending 'recovery' (7038 KB)...
OKAY [ 2.801s]
writing 'recovery'...
OKAY [ 2.541s]
finished. total time: 5.343s
I then try fastboot reboot and all I get is
rebooting......
on the boot loader screen it reads just under the boot version
Starting Fastboot USB download protocol this is constantly showing every time I boot to the boot loader.
and then I reboot from the tablet and its back to square one .
Any Help with this problem would be most appreciated I can still boot to system but I am not able to access recovery.
Many Thanks. Alex
Can you reboot recovery from adb or shell?
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Can you reboot recovery from adb or shell?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Hi RealWelder Thanks for your quick reply No I'm afraid not.
Cheers. Alex
screenshot of boot screen
I just thought I would post a screen shot to see if anyone has any suggestions
View attachment 3863929
Any help with this would be much appreciated. :crying:
cheers Alex
Al-Man said:
I just thought I would post a screen shot to see if anyone has any suggestions
View attachment 3863929
Any help with this would be much appreciated. :crying:
cheers Alex
Click to expand...
Click to collapse
I have seen many cases of "unrecoverable bootloader error" but never that you could still boot into system with that error. So I have no idea what is going on for you, but the only method I know of to successfully recover from a unrecoverable bootloader error is to flash the Asus system blob in fastboot after fastboot erasing each major partition. We call it a buster99 and you'll find it here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Before you do that why don't you try to 'fastboot boot recovery twrp.img' instead of flashing it. You should still be able to use TWRP as usual, flash a rom with it etc. It just does not get installed on the tablet....
See if you can use the recovery that way...
berndblb said:
I have seen many cases of "unrecoverable bootloader error" but never that you could still boot into system with that error. So I have no idea what is going on for you, but the only method I know of to successfully recover from a unrecoverable bootloader error is to flash the Asus system blob in fastboot after fastboot erasing each major partition. We call it a buster99 and you'll find it here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Before you do that why don't you try to 'fastboot boot recovery twrp.img' instead of flashing it. You should still be able to use TWRP as usual, flash a rom with it etc. It just does not get installed on the tablet....
See if you can use the recovery that way...
Click to expand...
Click to collapse
Thanks. berndblb I tried to fastboot twrp from my PC (Ubuntu 14.04) but no joy got the following :crying:
[email protected]:~/Android$ fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Android$ fastboot boot twrp.img
creating boot image...
creating boot image - 7211008 bytes
downloading 'boot.img'...
OKAY [ 2.727s]
booting...
FAILED (remote: ()
finished. total time: 2.751s
[email protected]:~/Android$ sudo fastboot boot twrp.img
[sudo] password for alex:
creating boot image...
creating boot image - 7211008 bytes
downloading 'boot.img'...
OKAY [ 2.729s]
booting...
FAILED (remote: ()
finished. total time: 2.747s
Any other suggestions, I don't like the sound of Buster 99 also tablet is the wife's.
Cheers. Alex
Buster99 has been a tablet saver for many users.
But if you don't want to do the whole thing try to fastboot erase recovery, cache and misc, then flash TWRP again and see if you can boot it.
Sent from my Nexus 5X using Tapatalk
berndblb said:
Buster99 has been a tablet saver for many users.
But if you don't want to do the whole thing try to fastboot erase recovery, cache and misc, then flash TWRP again and see if you can boot it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks berndblb After erasing everthing 3 times I was finally able to flash a new TWRP image. Many Thanks again for all your help. Alex
Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.
What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.
I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk
Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s
Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?
Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.
Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk