Database Info

Hard bricked my XOOM help

NOTE: Says when on rsd mode failed to boot 0x00001
on fastboot same + is says failed to format pds and does't connect to the pc after that
i have over 50 hours in 5 days looking for way to fix no luck .
i try my luck with Fastboot. I first tried flashing the recovery with no luck. I then tried flashing over the official moto files (boot/sytstem/....)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
....
If i follow that order boot/system and recovery fail then userdata says it works and it lets me flash the other options (but clearly just says they work it looks like it's lying)
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
.......
C:\SDK_tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 11.598s]
writing 'userdata'... OKAY [ 0.164s]
finished. total time: 11.764s
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.688s]
writing 'boot'... OKAY [ 3.462s]
finished. total time: 4.151s
.....
If I try fastboot oem unlock I'm prompted with the unlock message and after hitting accept. I see the following error on the screen
ERROR: Failed to format UDA.
Error while unlocking device.
My next try was with RSD light. I tried flashing all of the images for my xoom off this site . all of them give me the following error:
Failed flashing process. Failed Flashing process. Interface AP-OS: Error flashing subscriber unit. Device API error: 0xE0020085 Address: 0x1F870 Command: ADDR (0xE0222085); phone connected
I ran out of ideas on what to do next. One post i saw said try using a nand backup but I can't find one that will work.
Any help would be great. I really love my XOOM and I'm sad i can't fix it.

Fastboot Not Working (Blu Pure XL)

Hello!
Mi Blu Pure XL is dead, No OS installed.
I tried to install the system image with fastboot, but I have the following errors.
The recovery and Boot was installed OK.
[[email protected] BLU]# fastboot flash recovery BLU_RECOVERY_0.img
target reported max download size of 134217728 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.933s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.573s
Errors:
[[email protected] BLU]# fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.002s
[[email protected] BLU]# fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.002s
[[email protected] BLU]# fastboot flash system BLU_SYSTEM_0.img
target reported max download size of 134217728 bytes
Invalid sparse file format at header magi
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
Please Help me!!! :crying:

Any Help!????
Any Help!????

This phone has a semi unlocked bootloader. You can only flash BOOT and RECOVERY. For the rest the need to use SP Flash Tool.

Error
Error with SP Flash Tool:
BROM Exception! ( BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)
I see that I need flash preloader firts. But i dont have preloader.bin
Someone could share ?

Thanks to all!!
I found everything needed in the following message
http://forum.xda-developers.com/pure-xl/general/blu-development-t3213354/post65349290#post65349290
Thanks to all! Today I am the happiest man in the world .

Nexus 5 bootloop & recovery doesn't work

First of all, I'm german, so sorry if something's wrong with my English
Hey I've got a Nexus 5 laying around (I don't use it) and it is bootlooping. I would like to fix it but nothing works.
1. Power button isn't stuck (checked it)
2. I can boot into the bootloader
3. fastboot works fine
4. Can't get into Recovery ( when I boot into Recovery the Google Logo comes up and it keeps restarting)
5. Flashing a fresh Android doesn't work
6. Flashing a custom Recovery doesn't work
7. I don't know anything about the phone (I just got it because i wanted the display for my other Nexus 5)
8. bootloader is unlocked
I have fastboot and adb on a Windows and a Linux machine. Thanks for your help

Your English is perfect (apart from the lower case on "German" ) - if you hadn't started with that sentence I would never have known.
At the risk of boring people who may have already seen this post in other threads, see if this advice helps at all. If you have a working bootloader screen it may work. You can ignore the first sentence about backup, since in your situation it's redundant.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/images#hammerhead) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

Didn't work...
Here's my output:
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash bootloader bootloader.img
target didn't report max-download-size
sending 'bootloader' (2506 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
OKAY [ 0.453s]
finished. total time: 0.688s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash radio radio.img
target didn't report max-download-size
sending 'radio' (42033 KB)...
OKAY [ 1.422s]
writing 'radio'...
OKAY [ 2.891s]
finished. total time: 4.313s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 1.109s]
finished. total time: 1.109s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash system system.img
target didn't report max-download-size
erasing 'system'...
OKAY [ 0.516s]
sending 'system' (692940 KB)...
OKAY [ 21.893s]
writing 'system'...
OKAY [ 46.692s]
finished. total time: 69.132s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase boot
erasing 'boot'...
OKAY [ 0.234s]
finished. total time: 0.234s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (8620 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.734s]
finished. total time: 1.234s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.500s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash cache cache.img
target didn't report max-download-size
erasing 'cache'...
OKAY [ 0.484s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.063s]
finished. total time: 2.188s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (14626 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 1.125s]
finished. total time: 1.797s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
When i boot to recovery the google logo appears and still restarts all the time.
As i said, i've already tried flashing a custom recovery and Android before... Didn't work for me..

Sorry to hear that. I've never seen the "target didn't report" message. Maybe a hardware problem?

I thinks it's a hardware failure. I found somebody else having this problem on the google forum. They say the flash storage is demaged. Not repairable. But thanks for the quick reply.

Budden6800i said:
I thinks it's a hardware failure. I found somebody else having this problem on the google forum. They say the flash storage is demaged. Not repairable. But thanks for the quick reply.
Click to expand...
Click to collapse
Why you are using krt16m image? It's old...
Please download M4B30Z and try again...

Z3 bricked, no recovery

Hi all,
somehow my sons' D6603 messed up and didn't boot anymore. Had an old CarbonROM installed before, but that failed for no reason I can pinpoint.
OK, to recover I tried to reflash the ROM - but boot process got stuck in boot animation for hours (until battery ran out).
OK, so I fired up flashtool and tried to install an FTF - but all FTFs I tried to retrieve failed to unpack.
OK - one more try - got me a stock ROM that was supposed to be flashed through recovery.
Now I get Sony splashscreen, then display turns black and stays like that forever. Only sign of something happening is that the notification LED blinks occasionally.
I tried to enter recovery - wouldn't work at all: never saw any change in boot process.
I can put the phone into flash mode and into fastboot - so I tried to flash a new TWRP:
Code:
[email protected] ~/temp/TWRP-z3 $ fastboot flash FOTAKernel recovery.img
target didn't report max-download-size
sending 'FOTAKernel' (15904 KB)...
OKAY [ 0.502s]
writing 'FOTAKernel'...
OKAY [ 1.056s]
finished. total time: 1.558s
[email protected] ~/temp/TWRP-z3 $ fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (15904 KB)...
OKAY [ 0.501s]
writing 'recovery'...
OKAY [ 1.055s]
finished. total time: 1.556s
But still the mobile won't boot into recovery
OK, there's a different TWRP available - but I can't flash it to FOTAkernel:
Code:
[email protected] ~/Downloads $ fastboot flash FOTAkernel twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'FOTAkernel' (10808 KB)...
OKAY [ 0.342s]
writing 'FOTAkernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
[email protected] ~/Downloads $ fastboot flash recovery twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'recovery' (10808 KB)...
OKAY [ 0.342s]
writing 'recovery'...
OKAY [ 0.721s]
finished. total time: 1.063s
Can anyone help me to get stuff working again? I'm lost for options right now - TWRP won't come up, and I can't get an FTF via flashtool to my harddrive. Any other ways to unbrick the phone?
Got a recent LinuxMint 19.x here as my machine right now. Getting a Windows up and running would be an obstacle (although I might get a hand to one).

Flashing is not allowed for Critical Partitions

Hello guys!
Today I unlocked my old oneplus 6 phone,I wanted to flash google rom,so I execute
Bash:
adb reboot bootloader
and run flash script inside google android images.
Bash:
└─$ ./flash-all.sh
Sending 'bootloader' (4620 KB) OKAY [ 0.154s]
Writing 'bootloader' FAILED (remote: 'Flashing is not allowed for Critical Partitions
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.051s
I have no idea why this happpened,so I searched on google but got nothing.
And I've tried
Bash:
└─$ fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
Since I am new to these kinds of topics,any advice would be appreciated.

did you already set fastboot flashing unlock ?
makesure your adb / platform-tools is the latest too