Database Info

[Q] Droid Razr HD XT926 won't boot, different flash errors.

I was given a droid razr hd (xt926). Guy said he took an update and when the phone rebooted, it wouldn't go past the M boot screen. I don't know what build he was on and I don't know the previous status of the phone (root, rom, unlock, etc)
I can access AP Fastboot but I can't access anything else (Recovery, BP Tools, Factory).
I am using a Team Black Hat Cable, the most recent Motorola_End_User_Driver_Installation_6.4.0_32bit Driver, and a Windows 7 computer (my best computer is at ASUS getting fixed).
AP Fastboot Reads:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 03:15:48)
eMMC Info: Size 16GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
usb connected
______________________________________________________________________________
I first tried RSD Lite (using both 6.1.4 and 6.2.4 to flash VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I got:
Code:
Failed flashing process. 1/17 flash partition "gpt.bin" -> phone return FAIL
Trying VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml I had to delete the "getvar" line for it to begin BUT I also get the "gpt.bin" failed message here. If I delete steps in XML (get.bin, sbl1, sbl2, sbl3, etc) the process just gets hung up and fails on the next step
______________________________________________________________________________
Trying the most recent Matt's Utility, Mr.Parkinson's Utility, and SamuriHL's House of Moto (trying each build listed above) I get significant failed messages which I will post below.
Code:
Ready to flash...
Press any key to continue . . .
Flashing: UNIVERSAL.bat
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl2' (127 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.250s
sending 'rpm' (140 KB)...
OKAY [ 0.031s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.218s
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.218s
sending 'modem' (30720 KB)...
OKAY [ 2.371s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.434s
sending 'fsg' (165 KB)...
OKAY [ 0.031s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.094s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
sending 'logo' (854 KB)...
OKAY [ 0.078s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.140s
sending 'boot' (10240 KB)...
OKAY [ 0.796s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.451s
______________________________________________________________________________
Trying to manually mfastboot in cmd, I get similar errors. I tried boot.img first and got this error
Code:
mfastboot.exe flash boot boot.img
sending 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED <remote failure>
finished. total time: 1.451s
Flashing gpt.bin partition
Code:
mfastboot flash partition gpt.bin
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.250s
Is the phone FUBAR or does anyone have a suggestion how I could fix this?

Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.

eckdawg5 said:
Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, just by looking at your screen shots, I can tell you it's hard bricked.
Sent from my VS985 4G

[SOLVED][HARDBRICK] Unresponsive Oneplus One

SOLVED: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851/post57916281#post57916281
The story goes, I was trying to flash CM11S after trying out the Oneplus One Lollipop Alpha. Part way through the process the command line was waiting for the device to reboot into fastboot and it never did.
Command Prompt Log:
Code:
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.770s]
writing 'modem'...
OKAY [ 0.844s]
finished. total time: 2.613s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.004s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.016s
sending 'dbi' (11 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
sending 'aboot' (376 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 3.521s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.028s]
finished. total time: 0.037s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.012s]
writing 'tz'...
OKAY [ 0.015s]
finished. total time: 0.028s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.305s]
writing 'LOGO'...
OKAY [ 0.162s]
finished. total time: 0.468s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
Now the device is entirely unresponsive aside from a vibration when I hold down the volume and power keys. Screen stays black too and my computer will not detect my device. The Device is recognized by MSM8974 Downloader as well, but every time I select it to repair it it fails. The device also happens to be recognized by QPST Configuration software.
MSM8974 Downloader Log
Code:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
More Information:
Storage Capacity: 64GB
PC OS: Windows 8.1
Windows Driver Signature Verification Status: OFF
Device Drivers: PDANet Android Drivers, manually installed Oneplus One Drivers (from OPPO), ColorOS Drivers, and all the standard Google and Universal drivers.

Hello.
Same problem here. I just tried to reflash another roll since i was trying to rollback from Lollipop alpha. I did some changes in TWRP and after reboot my device did not start at all. There is only a vibration when I try to turn it on. Charging is also disabled. Screen is blank and unresponsive. Both recovery and bootloader dont work. I tried to turn my opo while connected to PC and I can hear that system found a new device. But there is no popup window, just the sound. Even after unplugging the sound can be heard.

Check this post for a solution :
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
start from "HERE IS THE SOLUTION"

TheManDroid said:
Check this post for a solution :
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
start from "HERE IS THE SOLUTION"
Click to expand...
Click to collapse
Been there done that. Nothing came of it, hence my logs posted above. Also I wouldn't be posting about it if I had found a solution

of course I'm recognizing your status as a senior member but was just giving you something to try since the image from the ColorOS.zip seem to work for some people and it has the required drivers for the MSM8974 downloader. but, to help everyone learn something about what you've tried :
- what factory image were you trying to use with the MSM8974 downloader?
- Is your OPO 64GB or 16GB?
- Which driver's version are you using?

I have the same problem. I suspect it's due to the differences in the partition tables between the ROMs. For example, the logo.bin for the CM11S image is around 9MB, whereas it is 512KB in the OnePlus ROM.
Hope we can get this fixed.

TheManDroid said:
of course I'm recognizing your status as a senior member but was just giving you something to try since the image from the ColorOS.zip seem to work for some people and it has the required drivers for the MSM8974 downloader. but, to help everyone learn something about what you've tried :
- what factory image were you trying to use with the MSM8974 downloader?
- Is your OPO 64GB or 16GB?
- Which driver's version are you using?
Click to expand...
Click to collapse
Sorry if I came off harsh in my previous post. That was not my intention. As for senior member, it means nothing other than I have been here a while (around the block so to speak), and I am very glad your willing to offer assistance (we need more people like you in fact), I just was noting that the thread had stated logs from the source you had mentioned. Now to answer your questions (I'll post this in the OP as well):
- You can see in the logs posted above what is missing in my partitions and what partitions are missing in general.
- 64GB
- I have tried using the PDANet drivers, manually installed Oneplus One Drivers (from OPPO), ColorOS Drivers, and all the standard Google and Universal drivers. I will also note that I am on Windows 8.1 (Driver Signature Verification turned off).

[Q] nexus 5 softbrick?

Hello everyone, a few days ago my phone's power button got stuck, and the devices was rebooting constantly. So I decided to disassemble it to find the problem, and after I had fixed the button, I reassembled it. But when i turned on the device, i noticed that the bootanimation changed and didn't complete the boot . " Now i have to flash the rom again" I thought, so I tried to boot into recovery. Booting the twrp took about 10 minutes, and the recovery did't recognize the internal storage (0MB), and wasn't able to mount /data and /cache partitions. Using format /data or wiping anything else didn't help.
So I tried to flash stock using fastboot, but i get a message saying "FAILED (remote: flash write failure)" (see screenshots for further information)
HTML:
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.538s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.764s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'boot' (8980 KB)...
OKAY [ 0.475s]
writing 'boot'...
OKAY [ 0.751s]
finished. total time: 1.229s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.181s]
sending 'cache' (13348 KB)...
OKAY [ 0.634s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.998s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 1073741824 bytes
sending 'recovery' (9696 KB)...
OKAY [ 0.493s]
writing 'recovery'...
OKAY [ 0.796s]
finished. total time: 1.293s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.116s]
sending 'system' (1021744 KB)...
OKAY [ 32.192s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 32.493s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 0.354s]
sending 'userdata' (137318 KB)...
OKAY [ 4.509s]
writing 'userdata'...
FAILED (remote: flash write failure)
finished. total time: 5.047s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
Post-Flash Factory Reset...
downloading 'boot.img'...
OKAY [ 0.413s]
booting...
OKAY [ 0.110s]
finished. total time: 0.526s
Searching on the internet i discovered that there's a problem on the /data partition, but eMMC is not damaged (I followed this guide). What should I do? I can access adb thanks to TWRP, and also fastboot. Please help me:crying:.

This line keep spamming, tho :
I:Actual block device: '/dev/block/mmcblk0p28', current file system: 'ext4'
Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/metadata
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
Try this, or this.
I read this issue before, and some users solved it by replacing the motherboard (just in case any of those solution above didn't work)

F4uzan said:
This line keep spamming, tho :
I:Actual block device: '/dev/block/mmcblk0p28', current file system: 'ext4'
Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/metadata
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
Try this, or this.
I read this issue before, and some users solve it by replacing the motherboard (just in case any of those solution above didn't work)
Click to expand...
Click to collapse
Thank you very much! Unfortunately it didn't work, so the only way to get my phone working again is the raplacement of the motherboard? :crying:

Take it apart again and make ABSOLUTELY SURE you did not damage or short any connections. Ideally using a jewelers loup. This should take you a minimum of 10 minutes to really check everything, not a quick glance.

fwayfarer said:
Take it apart again and make ABSOLUTELY SURE you did not damage or short any connections. Ideally using a jewelers loup. This should take you a minimum of 10 minutes to really check everything, not a quick glance.
Click to expand...
Click to collapse
Thank you very much. I checked the motherboard but i didn't see anything. However, the problem of /data happened before i fixed the button, so i think that it's not my fault.

Sorry I didn't see that in your original post. I would suggest you use your warranty and get a new device.

GGADSR said:
Hello everyone, a few days ago my phone's power button got stuck, and the devices was rebooting constantly. So I decided to disassemble it to find the problem, and after I had fixed the button, I reassembled it. But when i turned on the device, i noticed that the bootanimation changed and didn't complete the boot . " Now i have to flash the rom again" I thought, so I tried to boot into recovery. Booting the twrp took about 10 minutes, and the recovery did't recognize the internal storage (0MB), and wasn't able to mount /data and /cache partitions. Using format /data or wiping anything else didn't help.
So I tried to flash stock using fastboot, but i get a message saying "FAILED (remote: flash write failure)" (see screenshots for further information)
HTML:
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.538s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.764s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'boot' (8980 KB)...
OKAY [ 0.475s]
writing 'boot'...
OKAY [ 0.751s]
finished. total time: 1.229s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.181s]
sending 'cache' (13348 KB)...
OKAY [ 0.634s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.998s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 1073741824 bytes
sending 'recovery' (9696 KB)...
OKAY [ 0.493s]
writing 'recovery'...
OKAY [ 0.796s]
finished. total time: 1.293s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.116s]
sending 'system' (1021744 KB)...
OKAY [ 32.192s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 32.493s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 0.354s]
sending 'userdata' (137318 KB)...
OKAY [ 4.509s]
writing 'userdata'...
FAILED (remote: flash write failure)
finished. total time: 5.047s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
Post-Flash Factory Reset...
downloading 'boot.img'...
OKAY [ 0.413s]
booting...
OKAY [ 0.110s]
finished. total time: 0.526s
Searching on the internet i discovered that there's a problem on the /data partition, but eMMC is not damaged (I followed this guide). What should I do? I can access adb thanks to TWRP, and also fastboot. Please help me:crying:.
Click to expand...
Click to collapse
A couple of suggestions for you.
I do hope that you back up all your call logs sms and photos etc............
Given that I think you will have to do a "Hard Factory Reset" per these instructions
Nexus 5 Hard Factory Reset
Instructions
Performing a factory reset may take some time, so make sure that you plug your device in to a power source before you start. If your phone becomes unresponsive at any point during these steps, you can restart it by holding down the Power button for several seconds.
1. If your phone is on, turn it off.
2. Press and hold the Volume Down and Volume Up buttons, and then press and hold the Power button at the same time until the phone turns on. You'll see the word "Start" with an arrow around it.
3. Press the Volume Down button twice to highlight "Recovery."
4. Press the Power button to start Recovery mode. You'll see an image of an Android robot with a red exclamation mark and the words "No command."
5. While holding the Power button, press and release the Volume Up button once.
6. Press the Volume Down button twice to highlight "wipe data/factory reset" and press the Power button to select it.
7. Press the Volume Down button seven times to highlight "Yes - erase all user data" and press the Power button to select it.
8. After the reset is complete, press the Power button to select the option to reboot your device.
After you have that done I suggest you get yourself WUGfresh. Nexus Tool Kit.
I always do upates via WUGFresh rather than by OTA. The instructios are easy to follow.
If you have ever opened up your phone I suggest that you watch the youtube video by "LE55ONS" on the Nexus 5. It is very detailed and easy to follow.
Good luck to you and let us know how you get on.

Blacksmith5 said:
A couple of suggestions for you.
I do hope that you back up all your call logs sms and photos etc............
Given that I think you will have to do a "Hard Factory Reset" per these instructions
Nexus 5 Hard Factory Reset
Instructions
Performing a factory reset may take some time, so make sure that you plug your device in to a power source before you start. If your phone becomes unresponsive at any point during these steps, you can restart it by holding down the Power button for several seconds.
1. If your phone is on, turn it off.
2. Press and hold the Volume Down and Volume Up buttons, and then press and hold the Power button at the same time until the phone turns on. You'll see the word "Start" with an arrow around it.
3. Press the Volume Down button twice to highlight "Recovery."
4. Press the Power button to start Recovery mode. You'll see an image of an Android robot with a red exclamation mark and the words "No command."
5. While holding the Power button, press and release the Volume Up button once.
6. Press the Volume Down button twice to highlight "wipe data/factory reset" and press the Power button to select it.
7. Press the Volume Down button seven times to highlight "Yes - erase all user data" and press the Power button to select it.
8. After the reset is complete, press the Power button to select the option to reboot your device.
After you have that done I suggest you get yourself WUGfresh. Nexus Tool Kit.
I always do upates via WUGFresh rather than by OTA. The instructios are easy to follow.
If you have ever opened up your phone I suggest that you watch the youtube video by "LE55ONS" on the Nexus 5. It is very detailed and easy to follow.
Good luck to you and let us know how you get on.
Click to expand...
Click to collapse
Thank you. I tried to follow your procedure, but i had the same problem. In fact, when i try to boot recovery, i got all the problems that i explained in the first post. I'm going to buy a new motherboard at this point .

Soft brick help!!

I've had my nexus 5 for awhile now and decided that I should try to root it. So I followed a guide and youtube and it worked. I then followed a guide to install the android M developer preview, just to check out what had changed. From there I decided to install Cyanogenmod 12.1 . So I was looking at this guide when all of a sudden i noticed my root was gone for some reason. (im new to all this, not sure if that was supposed to happen). So then I followed the same rooting steps I used for the first youtube guide I watched. everything seemed to go fine until i realized that i was in a boot loop. I then decided to go ahead and install Cyanogenmod 12.1 anyway. It worked and my phone was fine. Until i woke up this morning and saw that it was in a boot loop again, but now I can't even get into my custom recovery (TWRP). I dowloaded this program to completely return my phone to stock but every time it tries to flash something to my phone, it gets this "flash write failure" message. Now I'm really lost and do not know what to do. I really rather not buy a new phone.
If anyone can help it would be really appreciated!!! If you do, I will need you to assume I do not know anything, as I'm not very familiar with everything.

Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk

ldubs said:
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I tried to flash it.. After trying to turn my phone back on, it tries to load up with the cyanogenmod logo still there.
Mathieus-MacBook-Pro:hammerhead-lmy48i mathieulaflamme$ ./flash-all.sh
sending 'bootloader' (3119 KB)...
OKAY [ 0.202s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.403s
rebooting into bootloader...
OKAY [ 0.110s]
finished. total time: 0.110s
sending 'radio' (45425 KB)...
OKAY [ 1.535s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.759s
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.104s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 06ed88372115a3f5
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8980 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.752s]
sending 'recovery' (9696 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.592s

Never seen a brick this hard to solve...

So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.

This is really bad. The solution to your first problem was to simply remove encryption by formatting data.

Jdelacrix said:
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
Click to expand...
Click to collapse
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.

sonicscrewup said:
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
Click to expand...
Click to collapse
i was in a similar situation and this method worked! connect the phone to pc in switched off condition, press power+vol down and get into fastboot and then oem unlock, install twrp and tried to installed the zips.. worked and phone booted!!