Database Info

[Q] Bricked Xoom, flashing not working. HELP!

I believe I'm bricked, and when I installed the moto stock .img and tried to flash them, I get an <unknown error> in command prompt. Please help me! can anyone give me some step by step instructions for a fix? thanks!

This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk

This is how I unbricked my xoom it will take you back to stock 3.0, then you will have to wait for the over the air updates before you can root again. Any questions, please ask. I have bricked my xoom a few times. Lol.
tabletroms.com/forums/xoom-general-discussion/1268-how-unbrick-your-moto-xoom.html
Sent from my Xoom using Tapatalk

johnny0911 said:
This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes I'm using adb, and yes, I'm in fastboot.

you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.

rohit3192 said:
you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.
Click to expand...
Click to collapse
I am in Fastboot protocol support. I try flashing the 4 stock .img in platform-tools, and I get errors.
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.253s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
See, it isn't working. any advice! I really hope I didn't pay $700 for a paper weight!!

I also get the OK, then it fails and says this...
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.727s]
writing 'boot'...
FAILED (status read failed (Too many links))
finished. total time: 1.319s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
C:\AndroidSDK\platform-tools>fastboot flash userdata userdata.img

I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.

rohit3192 said:
I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.
Click to expand...
Click to collapse
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...

V0nice said:
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...
Click to expand...
Click to collapse
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.

hocplyr98 said:
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.
Click to expand...
Click to collapse
Got it to work. I Google'd my issue, and I came up with a few possible issues. 1 being the usb cable, and the other being the usb port. Mine was a stock cable, so that wasn't the issue. But when I plugged the usb cable into the back of my pc (directly to the motherboards usb's) it worked, and I did not encounter the "command write failed"! successfully flashed the boot and system... ect img. and now my xoom is working!

./fastboot flash revovery fails with "partition table doesn't exist"

Can any admin move this to Q&A pleas? Sorry; I was in the wrong window in my browser.
Hi @all,
I just tried to follow the unlock procedure for my new Nexus5.
The first step (oem unlock) ran fine. The device was rebooted - it took a while. After reboot was complete the system was shut down and rebooted into bootloader (USB debugging switched on!)
Situation now: (all done as root)
d780:~/adb_fastboot # ./fastboot devices
xxxxxxxxxxxxxxx fastboot
d780:~/adb_fastboot # ./fastboot flash revovery openrecovery-twrp-2.7.1.1-hammerhead.img
sending 'revovery' (13586 KB)...
OKAY [ 0.955s]
writing 'revovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.135s
And whatever I try it refuses to flash this recovery. md5sum on recovery image is checked and fine.
I'm searching since more than 2 hours in the network but I could not find any tip to do the trick.
What is going wrong here??
Thanks in advance

wudelbrumpf said:
Can any admin move this to Q&A pleas? Sorry; I was in the wrong window in my browser.
Hi @all,
I just tried to follow the unlock procedure for my new Nexus5.
The first step (oem unlock) ran fine. The device was rebooted - it took a while. After reboot was complete the system was shut down and rebooted into bootloader (USB debugging switched on!)
Situation now: (all done as root)
d780:~/adb_fastboot # ./fastboot devices
xxxxxxxxxxxxxxx fastboot
d780:~/adb_fastboot # ./fastboot flash revovery openrecovery-twrp-2.7.1.1-hammerhead.img
sending 'revovery' (13586 KB)...
OKAY [ 0.955s]
writing 'revovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.135s
And whatever I try it refuses to flash this recovery. md5sum on recovery image is checked and fine.
I'm searching since more than 2 hours in the network but I could not find any tip to do the trick.
What is going wrong here??
Thanks in advance
Click to expand...
Click to collapse
You have written the spelling of recovery wrong
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-hammerhead.img

Hehe. revovery
Sent from my Nexus 5 using Tapatalk

Problem is sitting in front of the screen (as usual)
Don't laugh
I read this at least 10 times and I did NOT see this! Shame on me.
FIXED

Haha. I was wracking my brain trying to see what could have been wrong.

This made me laugh hard lmao. Atleast you got it fixed up though

[5.1 stock] n5 hangs on boot, black screen recovery mode

Hello everyone,
today I had very unpleasant surprise with my nexus 5. Let me tell the whole story from the beginning.
At first, I've never played with my nexus in any way (custom roms, root, etc.), it's all default from the beginning.
Few days ago I upgraded to 5.1 using android default upgrader. Next day I did a factory reset (from the settings menu) and then I encrypted the device. Since the flow of turning on the encrypted Android sucks, I did the factory reset again. Then I installed all the apps etc. and I was happily using the phone for 2 days until today's evening. I plugged my nexus into charging, it had 5% battery and was turned on. An hour or two later, I've noticed that the phone restarted and stucked on "Google" screen.
I tried booting several times. Then I googled how to boot into recovery mode. I hold volume and power buttons for a while, from the screen I chose "Recovery mode" and hit the power button again. Unfortunately I am getting the black screen...
Please, help me to make it working again, I found a lot of Google screen loop problems on the web as well as black screen recovery mode but happening not together and not with stock android.
I would like to have stock 5.1 back, possibly to backup some data before erasing.
Thanks,
alatar

alatar- said:
Hello everyone,
today I had very unpleasant surprise with my nexus 5. Let me tell the whole story from the beginning.
At first, I've never played with my nexus in any way (custom roms, root, etc.), it's all default from the beginning.
Few days ago I upgraded to 5.1 using android default upgrader. Next day I did a factory reset (from the settings menu) and then I encrypted the device. Since the flow of turning on the encrypted Android sucks, I did the factory reset again. Then I installed all the apps etc. and I was happily using the phone for 2 days until today's evening. I plugged my nexus into charging, it had 5% battery and was turned on. An hour or two later, I've noticed that the phone restarted and stucked on "Google" screen.
I tried booting several times. Then I googled how to boot into recovery mode. I hold volume and power buttons for a while, from the screen I chose "Recovery mode" and hit the power button again. Unfortunately I am getting the black screen...
Please, help me to make it working again, I found a lot of Google screen loop problems on the web as well as black screen recovery mode but happening not together and not with stock android.
I would like to have stock 5.1 back, possibly to backup some data before erasing.
Thanks,
alatar
Click to expand...
Click to collapse
Well you have two options:
Reflash stock rom with fastboot http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Or
Reflash stock rom with LG flashtool http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Both method will wipe your phone.

Use fastboot to reflash stock rom, but you may need to wipe data too. I've had this randomly happen before, luckily for me tho I had twrp and a backup, but even after re-installing the rom it'd still not load, i assume data had just got corrupted somehow unluckily, wiped data and all was fine and has been ever since
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5

Thank you @bitdomo and @Ben36.
So I tried reflashing with fastboot. I connected n5 to my notebook (running Ubuntu 14.04) and I turned on the device into fastboot mode. I ended up with "FAILED (remote: flash write failure)".
Here is what I did:
Code:
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot devices
[I]XXXXXXXXXXXX[/I] fastboot
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 48.373s]
finished. total time: 48.374s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.292s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.476s
I wanted to try with another cable and usb port but I didn't manage n5 to be recognized in fastboot lately (fastboot devices list is empty, lsusb is blind as well). I did a lot of attempts both on linux and windows 8 but it worked only twice on linux.
I will try again later. Perhaps you have some advise for this problem?
PS What is strange, after few minutes I plug n5 intro charging , it starts booting by itself... What the hell?
PS2 The phone keeps restarting whole the time... The battery seemed empty so I was charging it. It starts charging, after a minute it starts booting and then after 3 minutes it goes off. All over again and again.

alatar- said:
Thank you @bitdomo and @Ben36.
So I tried reflashing with fastboot. I connected n5 to my notebook (running Ubuntu 14.04) and I turned on the device into fastboot mode. I ended up with "FAILED (remote: flash write failure)".
Here is what I did:
Code:
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot devices
[I]XXXXXXXXXXXX[/I] fastboot
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 48.373s]
finished. total time: 48.374s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.292s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.476s
I wanted to try with another cable and usb port but I didn't manage n5 to be recognized in fastboot lately (fastboot devices list is empty, lsusb is blind as well). I did a lot of attempts both on linux and windows 8 but it worked only twice on linux.
I will try again later. Perhaps you have some advise for this problem?
PS What is strange, after few minutes I plug n5 intro charging , it starts booting by itself... What the hell?
Click to expand...
Click to collapse
That error message you get means that the emmc of the phone is fauilty.
Do you have warranty?

bitdomo said:
That error message you get means that the emmc of the phone is fauilty.
Do you have warranty?
Click to expand...
Click to collapse
Yes, I do. I have the phone just since few months. Are you sure about that? Cannot it be a failure of my usb port or poor cable quality?

alatar- said:
Yes, I do. I have the phone just since few months. Are you sure about that? Cannot it be a failure of my usb port or poor cable quality?
Click to expand...
Click to collapse
I am sure about that, there plenty of other people having the same problem. Only solution is to buy a new motherboard.

Bootloop! Unable to flash stock rom or lock bootloader (Help)

Hi. I can't get passed the google splash screen on a Nexus 5 D821 and could use some help.
Here are the facts:
* The owner of the device told me it bricked after an update.
* The Bootloader is unlocked. When i tried to lock i got the following message:
Code:
fastboot oem lock
...
OKAY [ 0.041s]
finished. total time: 0.041s
But it wasnt persistent. When given reboot comand the phone switched OFF instead. I turned it on to bootloader again and it was still unlocked.
* I tried flashing stock rom LRX22c manually after a failed attempt with the flash-all script. I got the following error for bootloader, radio, boot and recovery:
Code:
FAILED (remote: flash write failure)
* I tried erasing cache and flashing userdata but the after over 60 minutes waiting i came to the conclusion that i wasnt going anywhere and just rebooted the phone.
*The only thing im actually able to flash without an error message is system.img:
Code:
fastboot flash system ~/Downloads/hammerhead-lrx22c/image-hammerhead-lrx22c/system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (981472 KB)...
OKAY [ 30.934s]
writing 'system'...
OKAY [ 62.705s]
finished. total time: 93.767s
* I tried booting TWRP, but i was unable to mount the file system (perhaps because i wasnt able to flash it. i used "fastboot boot twrp.img").
Are phones technically able to get to splash screen or bootloader with a damaged NAND or EEMC chip? Im starting to consider the possibility of a hardbrick. Why would i be able to write system.img if that was the case though? Any help is welcome
===============================================
alright so im pretty sure its a hard brick. The emmc is dead. its a shame :/ guess ill just try to sell it for parts. I would delete this thread because its pretty useless, but i have created my account a few days ago, and i ddont know how to.

You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk

Ben36 said:
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of the imgs in their respective order. they all failed. i got the error
Code:
FAILED (remote: flash write failure)
. system.img was the only .img i was able to write, and i was wondering why. Also, when i try fastboot reboot the phone switches off. It doesnt reboot.

Phone hard bricked (possibly)

Help. I got an error today while trying to power on. It was something along the lines of validation failed. Cannot boot.
Then i tried installing the stock rom with the help of fastboot. It was going well. It even had success. But then I ran the command fastboot reboot and the phone doesn't turn on. Stays on black screen. Tried charging. No luck. I don't get any visual confirmation. Can I do anything to fix this phone?

Good. Via ADB the command adb devices or fastboot devices returns something? And the computer even recognizes him? It could be the same case that happened to me.
A year ago his screen turned bran and I sent in an assistance (it was updated in android stock 6.0, until it happened)... Only with the ROM it had, the system did not recognize the new screen (which was changed). Result: They downgraded the android (returned to 5.0) and now I'm breaking to solve an error, i can not even flash any twrp .... The message is
sending 'partition' (32 KB)...
OKAY [ 0.135s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.732s

Same issue here. I've been attemting to run stock firmware on mine. But I've been getting the same error. Idk if it's fixable and my recovery boot is corrupted.