[Q] Can't flash system. Is Motherboard toast? - 7" Kindle Fire HD Q&A, Help & Troubleshooting

I have a Kindle Fire HD 7in 2012 model that is stuck on the orange/white boot logo. I have a lot of experience flashing Kindles but this is the first time I have encountered this problem. The boot and recovery partitions seem to flash ok, based on time but take a look at the time it takes when flashing system and also the time it takes to clear cache and userdata. Is this motherboard toast? Any way to save it?
fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.016s
fastboot -i 0x1949 flash recovery images/recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 2.860s]
writing 'recovery'...
OKAY [ 2.829s]
finished. total time: 5.689s
fastboot -i 0x1949 flash boot images/boot.img
sending 'boot' (8192 KB)...
OKAY [ 2.875s]
writing 'boot'...
OKAY [ 1.235s]
finished. total time: 4.110s
fastboot -i 0x1949 flash system images/system.img
sending 'system' (907264 KB)...
OKAY [316.630s]
writing 'system'...
OKAY [ 1.235s] *** This should normally take 60 to 70 seconds **
finished. total time: 317.864s
fastboot -i 0x1949 erase cache
erasing 'cache'...
OKAY [ 1.235s] ** Normally takes approx. 50 seconds **
finished. total time: 1.235s
fastboot -i 0x1949 erase userdata
erasing 'userdata'... ** Normally takes 80 to 90 seconds **
OKAY [ 1.240s]
finished. total time: 1.243s
I also tried to format the system partition and this is what I get...
fastboot format system
< waiting for device >
After waiting 15 minutes I gave up on this...
Then I tried it this way:
fastboot -i 0x1949 format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.016s
Any ideas???

No, your motherboard isn't toast. Those times are around how long it should take to flash. If you didn't notice, flashing system went fine. Fastboot format is weird on the Kindle Fires (it doesn't ever want to work properly), but the reason you were stuck at the "waiting for device" prompt is because you didn't add "-i 0x1949" to the end of the command. Notice that once you did, it went through fine (well, sorta). Your motherboard is not toast. If it was, you would not be able to boot it up at all, even to fastboot mode. Pressing the power button and/or any combination of key presses would get you absolutely nowhere. I would double-check you have the right images. What exactly are the boot/recovery/system image you're flashing?

r3pwn said:
No, your motherboard isn't toast. Those times are around how long it should take to flash. If you didn't notice, flashing system went fine. Fastboot format is weird on the Kindle Fires (it doesn't ever want to work properly), but the reason you were stuck at the "waiting for device" prompt is because you didn't add "-i 0x1949" to the end of the command. Notice that once you did, it went through fine (well, sorta). Your motherboard is not toast. If it was, you would not be able to boot it up at all, even to fastboot mode. Pressing the power button and/or any combination of key presses would get you absolutely nowhere. I would double-check you have the right images. What exactly are the boot/recovery/system image you're flashing?
Click to expand...
Click to collapse
Thanks for the reply. It's definitely a KFHD7 2012 model and I am using KFHD_SRT_1.3.5. The images are Version 7.3.0. I have used these images several times in the past to restore that model.
So you don't think it's unusual that flashing the system partition only took 1.235 seconds (usually takes 60-70 seconds)? Or that erasing cache also took only 1.235 seconds (usually takes approx. 50 seconds) and erasing userdata took 1.240 seconds (usually takes 80 to 90 seconds)? I am wondering if those partitions got corrupted but I don't know how to reset them when all I have to work with is fastboot.
And the bottom line is after reflashing all the above partitions, the Kindle is still stuck on the static boot logo. It's got me stumped. Any help would be appreciated.

Anchorman42 said:
Thanks for the reply. It's definitely a KFHD7 2012 model and I am using KFHD_SRT_1.3.5. The images are Version 7.3.0. I have used these images several times in the past to restore that model.
So you don't think it's unusual that flashing the system partition only took 1.235 seconds (usually takes 60-70 seconds)? Or that erasing cache also took only 1.235 seconds (usually takes approx. 50 seconds) and erasing userdata took 1.240 seconds (usually takes 80 to 90 seconds)? I am wondering if those partitions got corrupted but I don't know how to reset them when all I have to work with is fastboot.
And the bottom line is after reflashing all the above partitions, the Kindle is still stuck on the static boot logo. It's got me stumped. Any help would be appreciated.
Click to expand...
Click to collapse
Oh. I must have missed that. That does sound weird, but I'm not sure if your partitions got corrupted. Try running "fastboot oem format -i 0x1949" (this kinda "resets" the partition table to what it should be, in case anything is weird) then flashing the images again.

r3pwn said:
Oh. I must have missed that. That does sound weird, but I'm not sure if your partitions got corrupted. Try running "fastboot oem format -i 0x1949" (this kinda "resets" the partition table to what it should be, in case anything is weird) then flashing the images again.
Click to expand...
Click to collapse
D:\KFHD_SRT_v1.3.5>fastboot -i 0x1949 oem format
...
FAILED (status read failed (Too many links))
finished. total time: 1114.006s
Hmmm. Not sure if it worked... Proceeded to reflash all partitions. Got the same results. Flashing system and erasing cache and userdata all took less than 2 seconds.

Anchorman42 said:
D:\KFHD_SRT_v1.3.5>fastboot -i 0x1949 oem format
...
FAILED (status read failed (Too many links))
finished. total time: 1114.006s
Hmmm. Not sure if it worked... Proceeded to reflash all partitions. Got the same results. Flashing system and erasing cache and userdata all took less than 2 seconds.
Click to expand...
Click to collapse
That oem format thing didn't appear to have worked. Try rebooting to bootloader and trying it again.

r3pwn said:
That oem format thing didn't appear to have worked. Try rebooting to bootloader and trying it again.
Click to expand...
Click to collapse
I am out of town for the weekend so I will try it on Monday. In the mean time, how to I reboot to the bootloader? Isn't that what happens when you go into fastboot? If not, how do I use the command fastboot -i 0x1940 oem format?

Related

[Q]-Bootlooping/possibly bricked 7' Kindle HD

Hi folks. SNagged an "untested" kindle fire HD 7 off ebay. Wanted to try my luck with the kindle tablet's since I haven't owned or rooted any of them. Sadly, it's not working. It turns on, comes to the kindle fire logo, does a slow lens flare, goes to the fast lens flare and cycles that a bit before briefly stopping the fast moving flare and starting it all over again.
I've tried powering it down, doing the "fastboot -i 0x1949 getvar product" with no other devices attached, attaching the fire and it won't work. It boots up exactly as if I just hit power. I never get anything saying it's going into fastboot mode. The PC doesn't give me the standard "new hardware doink" either. Is this a case for buying one of those factory cables and trying that?
That command only works on the 8.9" models, you need a fastboot cable.
Sent from my Amazon Kindle Fire HD using xda app-developers app
stunts513 said:
That command only works on the 8.9" models, you need a fastboot cable.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
So for the 7 inch version, in order for me to have any hope of trying to get this thing functional is to get that factory/fastboot cable?
Yes if you have a Samsung brand value you can make one by shorting on the micro end pins 1 and 4
Sent from my XT907 using xda app-developers app
NapalmDawn said:
So for the 7 inch version, in order for me to have any hope of trying to get this thing functional is to get that factory/fastboot cable?
Click to expand...
Click to collapse
Yes, you're in a bootloop and must have a fastboot cord now. You can make one or buy one off eBay for 10 buck or so. Then try using KFFA http://forum.xda-developers.com/showthread.php?t=2096888
LinearEquation said:
Yes, you're in a bootloop and must have a fastboot cord now. You can make one or buy one off eBay for 10 buck or so. Then try using KFFA http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
Thanks. I was poking around and saw a thread where the guy mentioned selling them. I just need to find that thread again.
I haven't been able to use the KFA to get this thing out of the boot loop.
Now that I have a factory cable, I can get the KF HD 7 into fastboot mode. When I run the utility, it seems I get errors. Here's a snippet.
Code:
OKAY [ 94.745s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.273s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.003s]
finished. total time: 150.026s
Would You Like To Wipe Data And Cache (y/n) ?
erasing 'userdata'...
OKAY [ 94.740s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.276s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
finished. total time: 150.024s
rebooting...
finished. total time: 0.001s
This happens when I restore to 7.2.3 or .1 I can unplug it from the PC, reboot it and come right back to the same bootloop as before. Goes through the fast movement of light on the logo, quick black screen, back to the logo and the lights again.
NapalmDawn said:
I haven't been able to use the KFA to get this thing out of the boot loop.
Now that I have a factory cable, I can get the KF HD 7 into fastboot mode. When I run the utility, it seems I get errors. Here's a snippet.
Code:
OKAY [ 94.745s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.273s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.003s]
finished. total time: 150.026s
Would You Like To Wipe Data And Cache (y/n) ?
erasing 'userdata'...
OKAY [ 94.740s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.276s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
finished. total time: 150.024s
rebooting...
finished. total time: 0.001s
This happens when I restore to 7.2.3 or .1 I can unplug it from the PC, reboot it and come right back to the same bootloop as before. Goes through the fast movement of light on the logo, quick black screen, back to the logo and the lights again.
Click to expand...
Click to collapse
Just so I understand, you went to KFFA and choose to restore your kindle to 7.2.3 option? Using Factory Cable? Just asking because this is what I did to restore my kindle from bootloop and it worked just fine
Wondrej said:
Just so I understand, you went to KFFA and choose to restore your kindle to 7.2.3 option? Using Factory Cable? Just asking because this is what I did to restore my kindle from bootloop and it worked just fine
Click to expand...
Click to collapse
Yes. However, did you notice the errors in my code? It seems that the tool is unable to format the KD HD 7 for some reason. Do you think it's possible that once I'm in fastboot that I can issue a command via normal fastboot (from the command prompt) that will force the format?
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.276s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
Click to expand...
Click to collapse
NapalmDawn said:
Yes. However, did you notice the errors in my code? It seems that the tool is unable to format the KD HD 7 for some reason. Do you think it's possible that once I'm in fastboot that I can issue a command via normal fastboot (from the command prompt) that will force the format?
Click to expand...
Click to collapse
one more question? how long have you let it on "boot loop" after you tried this? If I recall corectly I took me quiet a while to boot for the first time (like 2 minutes or so) I was actually worried at the time it didn't work, but I just let it be for few minutes and it booted.
Wondrej said:
one more question? how long have you let it on "boot loop" after you tried this? If I recall corectly I took me quiet a while to boot for the first time (like 2 minutes or so) I was actually worried at the time it didn't work, but I just let it be for few minutes and it booted.
Click to expand...
Click to collapse
I admit it was about only 1 min or so only because I watched it long enough to SEE the loop. It wasn't that the boot up was taking a long time, I saw it cycle at least twice from black to slow lens flare on the logo, then the fast flare, then a quick black screen and rinse/repeat. Being somebody who's flashed a lot of roms on tabs and phones for years, I definitely am patient with a "cook" time. This didn't seem like a settling in type issues since I saw the pattern repeat at least twice.
NapalmDawn said:
I admit it was about only 1 min or so only because I watched it long enough to SEE the loop. It wasn't that the boot up was taking a long time, I saw it cycle at least twice from black to slow lens flare on the logo, then the fast flare, then a quick black screen and rinse/repeat. Being somebody who's flashed a lot of roms on tabs and phones for years, I definitely am patient with a "cook" time. This didn't seem like a settling in type issues since I saw the pattern repeat at least twice.
Click to expand...
Click to collapse
I am with you, I am just trying to eliminate the easy problems first, before we start trying crazy stuff.
Wondrej said:
I am with you, I am just trying to eliminate the easy problems first, before we start trying crazy stuff.
Click to expand...
Click to collapse
Understood. When I get home, I'll boot it back up and let it sit for 5 mins and see what happens.
I can say that at least the factory cable did put it into fastboot mode properly whereas the stock USB cables did not. Is there a fastboot command that can be done to tell it to format those areas it is having problems with? The inability to format userdata and cache worries me.
NapalmDawn said:
Understood. When I get home, I'll boot it back up and let it sit for 5 mins and see what happens.
I can say that at least the factory cable did put it into fastboot mode properly whereas the stock USB cables did not. Is there a fastboot command that can be done to tell it to format those areas it is having problems with? The inability to format userdata and cache worries me.
Click to expand...
Click to collapse
Code:
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
[B] format <partition> format a flash partition[/B]
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
AFAIK KFFA only runs fastboot commands so I am not sure if you'll get different result by using fastboot directly, also I have no idea how to format the partitions properly tbh.
Wondrej said:
Code:
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
[B] format <partition> format a flash partition[/B]
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
AFAIK KFFA only runs fastboot commands so I am not sure if you'll get different result by using fastboot directly, also I have no idea how to format the partitions properly tbh.
Click to expand...
Click to collapse
I'll try a manual fastboot format tonight. I can say that I booted it up when I got home from work and let it sit for 10+ mins. Yep, definitely still in the bootloop. Does anybody have any idea what might cause the format to think the media is invalid? Could somebody have tried to flash the wrong kind of rom to this device?
NapalmDawn said:
I'll try a manual fastboot format tonight. I can say that I booted it up when I got home from work and let it sit for 10+ mins. Yep, definitely still in the bootloop. Does anybody have any idea what might cause the format to think the media is invalid? Could somebody have tried to flash the wrong kind of rom to this device?
Click to expand...
Click to collapse
Use the fastboot cord and this tool http://forum.xda-developers.com/showthread.php?t=1951254 wipe first then restore. This tool works great. Sounds like someone bootlooped their tablet and called it untested because they knew it was not working proper. Their loss will be your gain.
Sent from my Amazon Kindle Fire HD running Paranoid Android [4.3 JB] using xda app-developers
LinearEquation said:
Use the fastboot cord and this tool http://forum.xda-developers.com/showthread.php?t=1951254 wipe first then restore. This tool works great. Sounds like someone bootlooped their tablet and called it untested because they knew it was not working proper. Their loss will be your gain.
Sent from my Amazon Kindle Fire HD running Paranoid Android [4.3 JB] using xda app-developers
Click to expand...
Click to collapse
I'll give it a try tonight!
LinearEquation said:
Use the fastboot cord and this tool http://forum.xda-developers.com/showthread.php?t=1951254 wipe first then restore. This tool works great. Sounds like someone bootlooped their tablet and called it untested because they knew it was not working proper. Their loss will be your gain.
Sent from my Amazon Kindle Fire HD running Paranoid Android [4.3 JB] using xda app-developers
Click to expand...
Click to collapse
Amazingly, not even this tool fixed it. It wiped without any errors and I picked the option to factory reset with root, apex, play store and I get the same boot loops. I think this thing was held up against a magnet or something lol. I wonder what somebody did to it.
It's defintiely an HD 7 because it has the camera and the stripe on the back.
NapalmDawn said:
Amazingly, not even this tool fixed it. It wiped without any errors and I picked the option to factory reset with root, apex, play store and I get the same boot loops. I think this thing was held up against a magnet or something lol. I wonder what somebody did to it.
It's defintiely an HD 7 because it has the camera and the stripe on the back.
Click to expand...
Click to collapse
This will sound repetitive but try it again. One time it took five time. Also, when it first starts, it will blink 3 times and then stay solid on the KF logo and then look like a normal boot up. Let the ROM have some time to finish cooking. If it blinks more than 5 times, its another bootloop. A bootloop is pretty much always fixable.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
---------- Post added at 02:38 AM ---------- Previous post was at 02:33 AM ----------
NapalmDawn said:
Amazingly, not even this tool fixed it. It wiped without any errors and I picked the option to factory reset with root, apex, play store and I get the same boot loops. I think this thing was held up against a magnet or something lol. I wonder what somebody did to it.
It's defintiely an HD 7 because it has the camera and the stripe on the back.
Click to expand...
Click to collapse
Just checking that you have SDK installed http://m.youtube.com/watch?v=oaNM-lt_aHw&desktop_uri=/watch?v=oaNM-lt_aHw There is a guy on here named stunts and his modified drivers have saved many a KFHD. Maybe give them a try. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Just curious did you try the restore tool instead of kffa yet? Second question might try installing the second boot loader and see if you can get twrp installed then push a rom to it.
Sent from my XT907 using xda app-developers app

XT890 Stuck on Red Logo. Probably damaged partitions.

Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Ye, great chance that the emmc is damaged. But it still looks to me as if it is software damaged, not hardware, because of the successful flash of recovery. And it is on the same memory module.
Just as in the other post of this phone can u try this and give me the output of especially the flash of gpt.bin (partition table file). I never got an exact answer to it, for my liking, maybe i read over it.
If that doesn't flash (give me the output then i know for sure ), try flashing the boot.img and see what happens. I assume nothing will change from flashing the boot.img, but u gotta try something.
Next we can do is have a look at that intel flashing file, it looks promising. I never had to go to this part so i am out of general ideas (think outside the box maybe?). Maybe we can fiddle something from here. It looks to me like it can flash more than fastboot can, u just need the right files and some we can make, hopefully if i read the sources available to us right.
Hazou
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash gpt gpt_s
igned
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'gpt' (32 KB)...
OKAY [ 0.358s]
writing 'gpt'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 1.094s]
finished. total time: 1.460s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motoboot
motoboot
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motoboot' (23273 KB)...
OKAY [ 2.635s]
writing 'motoboot'...
(bootloader) flashing image dnx...
(bootloader) flashing image ifwi...
(bootloader) flashing image bos...
(bootloader) flashing image logo...
(bootloader) flashing image ulogo...
OKAY [ 2.338s]
finished. total time: 4.981s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash boot boot
_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.243s]
writing 'boot'...
OKAY [ 1.549s]
finished. total time: 2.799s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash recovery
recovery_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'recovery' (11264 KB)...
OKAY [ 1.338s]
writing 'recovery'...
OKAY [ 1.563s]
finished. total time: 2.907s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motobp mo
tobp
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motobp' (17091 KB)...
OKAY [ 1.714s]
writing 'motobp'...
OKAY [ 76.674s]
finished. total time: 78.396s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash system sy
stem_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.377s]
writing 'system'...
OKAY [ 2.576s]
sending 'system' (102400 KB)...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
OKAY [ 11.154s]
writing 'system'...
FAILED (remote failure)
finished. total time: 25.509s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash cdrom cdr
om_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'cdrom' (53258 KB)...
OKAY [ 4.891s]
writing 'cdrom'...
FAILED (remote: Preflash validation failed)
finished. total time: 6.273s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase cache fail
FAILED (remote failure)
finished. total time: 1.897s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
FAILED (remote failure)
finished. total time: 8.110s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>
So it looks like only few partitions are broken but how to repair it without unlocking bootloader??
Hmm, it does flash a part of the system if I read it correct. After the first one it gives errors to all partitions after it.
Can u reboot to recovery now, we finally flashed it right. Didn't work last time.
The things I wanted to do with the Intel thingy, are already done with flashing motoboot. So the things I had there are done.
Verstuurd van mijn GT-P5110
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Chamelleon said:
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Click to expand...
Click to collapse
Yep, this happens because it has nothing to start.
There is just 1 more think I can think off, because all others are closed (locked) or don't work. Or if unlocked we still don't have access.
Does the command "fastboot oem format" does something?
Verstuurd van mijn GT-P5110
Completely forgot about this command, I'll try it after work.
FAILED (remote: Restricted OEM command)
Then its over I think. We can't flash a custom recovery and fiddle around with it. Because maybe by not asking for system/data partition at start etc u can reformat the emmc with parted or other application.
Sorry, only Motorola can fix it. Or u need to replace the motherboard maybe? But that's something else.
Oh, try 1 more thing. Is it possible to load a custom boot image by the command "fastboot boot (image)"? Don't think so, but who knows. So u won't flash it.
Verstuurd van mijn XT890
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Chamelleon said:
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Click to expand...
Click to collapse
Yup, the defy could do it if i remember correctly. Hoped that this one would either. I am out of ideas now, but will have one more look. Don't expect anything, because we already tried most if not all the things we can do.
Edit:
All other things i can think of need to have adb access, and that can only be done by having an unlocked bootloader or root access. Because with root access u can flash a recovery even when u have a locked bootloader most of the time. But we don't have access to the system as well as the partitions, so we are stuck.
That Intel thingy can only flash the bootloader and the bootloader wont repartition the emmc. But we can try anyway if u want. Its a little bit different then the unbrick methode, just a little.
Verstuurd van mijn XT890
Today I flashed Samsung C3595 with partition table from S5610 and it's working well so "different" methods are not scary for me.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Hi Chameleon.. i'm having a phone with similar issues (I created a post about it). I have tried steps one and two to no success. To unlock it do you do it via the official way (I ask because I don't know much, maybe there are other ways of doing it)
Yup, only official way.
Wysłane z Motorola RAZR i
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
hjahmetoglu said:
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
Click to expand...
Click to collapse
Luckily, u don't have the same problem. U only have to search for a rsd lite flash guide. Flash your latest firmware that is available for your phone and country/brand. And all will most likely be good.
Hazou said:
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
Click to expand...
Click to collapse
Yesterday I tried it and unfortunately nothing changed, still can't erase or write to those partitions.
XT890 Stuck on Red Logo. Probably damaged partitions
I woke up this morning to find that my Motorola XT890 is not working. I followed all the procedures for hard rest got the same result as listed below.
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
Contacted Motorola customer service, followed all the procedures as prescribed by Motorola customer service still stuck at Red Logo. Motorola has requested that I send it in for repair. The phone is 11 months old and under warranty. The unfortunate thing is that this is the second time I am sending the phone to Motorola for repair.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse

stock-device bricked itself (battery drained with pinned app, ecnrypted device)

Hi there,
tl;dr:
Basically, my problem seems to be, that any write-operation on my filesytems is refused:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Click to expand...
Click to collapse
I found threads about the same problem on Moto G 2013, where "Philz Recovery" was able to fix the partitioning and filesystems, but it seems that this does not exist vor Moto G 2014. And I don't even get any other than stock-recovery working.
TWRP site states: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. " But I could not find any key combo to enter the recovery I just flashed (at least fastboot tells me so) Using "fastboot boot recovery.img" just shows a shortly flickering Motorola-logo every 10 seconds or so.
---
I am having severe issues with my Moto G (2014).
I found some reports of similar issues, but no solution described worked, and it seems I am the only one experiencing this on a stock device.
First some facts:
Device in use since 2 months
Encyption activated about a month ago, no problems
Yesterday, I used screen pinning feature to let my son play a game.
While he was playing, the battery drained until the device shut down.
I connected the device to a charger
After charging 30%, everything first seems normal, I have to enter my encryption PIN and boot process goes on, showing boot animation.
The problem:
At the point, where it would normally finish, the screen just gets black (while still being lit up). Nothing more will happen. The device will remain in this state forever or until the battery is completely drained again.
I first tried using the official methods for (factory) reset described on Motorolas website, they did not work (I am not allowed to post links here yet, google "/prod_answer_detail/a_id/99825/p/30,6720,9151" will show the URL)
Pressing 7-8 seconds restarts the phone, same situation.
Pressing 120 seconds restarts the phone several times, still not working.
I wanted to perform a factory reset, but starting recovery from bootloader only displayed "Boot Up Failed". Choosing "factory" or "bp tools" just started normal boot process. Barcodes seems to work, it shows barcodes.
So next step was unlocking the device to install TWRP. Fastboot displayed no errors, but then not TWRP, but normal recovery starts. Well, better than "Boot Up Failed".
When now performing a factory reset, this is displayed:
Code:
-- Wiping data...
Formatting /data...
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/userdata failed
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/cache failed
-- Wiping clogo...
Data wipe complete
Obviously, the partitions are untouched (or not there?), and the problem remains.
I also tried to erase cache and userdata using fastboot, there are no error messages, but after rebooting, I am still asked for encryption PIN, so it's basically the same.
I then tried to use adb sideload to flash cm12 nightly. But the device complains that the signature verification failed.
Now, I am not even able to lock the device again, while fastboot states, it would have succeeded.
I wanted to reinstall stock images as described on thetechrism.com (Google: restore-moto-g-2and-generation-2014-stock-lock-bootloader) but I have problems downloading as I only have mobile internet connection at this moment and the download from filefactory stopped two times at 200 MB and I have only about 1 GB traffic for the rest of the month.
I am stuck here, and getting desperate. Did my device brick itself?
I have CM12 and TWRP here, but just cannot get it flashed. This would be my preferred solution, but a reliable source for stock images would also be very nice.
Did anyone experience similar problems when the battery completely drained with a pinned app on an encrypted device?
Thanks in advance for any hint.
Regards
cxxxx
I was now able to download the original firmware.
But...it's the same :'(
I did every step to reinstall stock firmware. No error-messages, neither on console nor on device, everything seems to be fine.
But when I finally reboot, the device again asks for my encryption PIN and will fail to startup!
I still cannot wipe my userdata, still cannot flash a custom recovery...nothing. It's just a ******* brick.
I found one interesting error:
Code:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.066s]
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.133s
How can I manually reformat my partitions in internal storage or how can I force automatically formatting?
Code:
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.041s]
writing 'partition'...
OKAY [ 0.304s]
finished. total time: 0.347s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.134s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.954s]
finished. total time: 1.091s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.087s]
writing 'logo'...
OKAY [ 0.044s]
finished. total time: 0.134s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.458s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.060s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.607s]
finished. total time: 1.075s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 9.899s]
writing 'system'...
OKAY [ 8.160s]
finished. total time: 18.063s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 9.860s]
writing 'system'...
OKAY [ 8.230s]
finished. total time: 18.094s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 9.874s]
writing 'system'...
OKAY [ 7.975s]
finished. total time: 17.853s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 8.841s]
writing 'system'...
OKAY [ 7.559s]
finished. total time: 16.402s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.941s]
writing 'modem'...
OKAY [ 0.854s]
finished. total time: 2.798s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.013s]
finished. total time: 0.014s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.018s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot reboot
rebooting...
finished. total time: 0.002s
I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup
izaiasfilho said:
I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup
Click to expand...
Click to collapse
We are not alone, see here:
http://forum.xda-developers.com/mot...ttery-left-t3085322/post60312526#post60312526
Bad news is, that the problem has not been solved and probably will not as it seems that it's hardware-failure of the flash-storage-(controller).
@cxxxx
I read about it on the moto forums, with users having lost write operations on their phone. And all had one thing in common, they had let the battery die out .
Lesson to be learnt : Never let Li ion batteries totally get drained.
One of the moto moderator told it on their forum to never let your battery totally die. I dont know how much of it rings true as I've let my phone discharged till death many times without any issues.
Same problem here.
After the battery gone once i did't manage to enter. Services errors at android home screen and i can't do recovery - wipe data - cache (all failed). The only thing that i manage is to unlock bootloader.
My question: I 'm thinking to send device for warranty (buying one month ago). Do you think that i 'll have problem with unlock bootloader at service. Somewhere i read that motorola have 2 year warranty for software no matter what. Is that real???
HardBricked unlocked stock lollipop xt1068
Same problem here. But no enconding is on thou.
Can't flash anything - stuck on black screen after boot animation.
XT1068 Unlocked bootloader, stock lollipop, no root, no Motorola service in my country.
Once this devices gone hardbrick, after freaky TWRP could not backup or do anything else. Just could not turn in on at all.
Recovered with jtag riff drivers, but this seems to help bootup, not to flash firmwares - so its not applicable for this case.
RSD Lite 6.1.6 can't see phone, ADB sideload form stock recovery gives no device for adb or windows device manager, but fastboot is okay.
Tryed different computers, different drivers, different stock roms, different fastboot\mfastboot tools, recover scripts.
Hi, guys. I'd face the same problem, but I can boot up, using a Nokia phone charger. Don't know how to explain, but the moto g 2014 charger can't charge enough to boot, when the battery is 0%, then come back to the black screen. With the nokia charger, my moto g boot up normally.
Sorry for my bad english.
Nico
For all those users with soft-bricked "nothing changes after any actions", what if we try to use:
Fastboot erase all
If this would work - bootloader will be dead. We will get the hard brick.
But I have experience of successful recovering xt1068(exactly this one) from hard-brick state, when decice does not turn on at all in any way or mode since bootloader is missing or corrupted.
But PC still can see it over USB cable as QBULC_USB. This one would not work with Motorola drivers nor with any other, but JTAG Riff drivers for QUALCOMM.
Then special low-level tool will load up bootloader.
So? Any suggestions about this?
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app
Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Click to expand...
Click to collapse
No way of backing up this data?
I remember some of mine old RAZR - I had some backup of unique data for it.
BTW I have the box with IMEI on it, CID saved in notepad, what else...
Stock fw with no root and THIS with no reason.
Also - right before stucked - phone has drained battery from 60% to 0% in pretty short time, then this happened.
Maybe there is some hardware problem with electric circuit..
Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
With my device bricked like this I have tried, CHMOD which has unable to alter the partitions, as well as CHOWN & CHGRP(in both TWRP & ADB), Fastboot erase does nothing along with ADB wipe, TWRP does nothing and no changes can be made as nothing is overwritten, as well as with using Fastboot flash, there have been rumors that Philz can fix it but since nothing can be flashed I cannot try (Unless someone has a way to flash it to SD and let it boot from there, Let me know)
Now with my limited knowledge of android and its partitions and since none of the above methods having any effect I believe that this issue is in fact a hardware one not software related, therefore I think 'Fastboot erase all" will have no effect, that is my opinion gathered from more than two weeks testing, wiping & hoping, if there are any senior users/devs who want to correct me they may, Also if they have any other options I will be glad to try it out.
EDIT: This is purely a hardware fault and no software changes can do anything, I ran Fastboot erase all
...and a reboot later and my device is exactly the same, even boots into recovery fine and fastboot barcodes still shows my original IMEI and Serial number, ADB getvar_cid still also shows the correct CID for my device.
I would upload pictures but I haven't got enough posts to link to tinypic

KFHD7 teamwin logo boot loop

There's a lot of similar threads on this and I have tried every method I could find and nothing has helped.
Yesterday I took a stock KFHD7 and rooted it, flashed teamwin recovery 2.6.3.1 and freedom boot 7.4.6, and then flashed CM 12.1 and the appropriate gapps. Everything was working GREAT except I had a problem downloading the Google Play Games app through the App store (Error -505) and I read the wasiest way to handle it on a new install was to just Factory Restore through CM 12.1. It wasn't until AFTER I rebooted that someone mentioned that doing that on CM 12.1 on a KFHD7 could seriously mess things up.
Now when I turn it on it shows the orange kindle fire logo, the blue kindle fire logo, then the teamwin logo, and then it flashes off briefly and goes back to the teamwin logo for a few more seconds before repeating flashing and teamwin over and over.
I was told I need to reflash the freeboot and teamwin recovery via fastboot. I had a lot of issues in that "fastboot dvices" does not return anything. "fastboot -i 0x1949 getvar product" returns that I have the Tate. Attempting to use fastboot without the "-i 0x1949" parameter causes it to display "< waiting for device >" indefinitely. adb seems to work, but any shell commands I attempt to send return that the command is not found.
So I tried this:
Code:
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 flash boot kin
boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.173s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 2.749s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 flash recovery
kinrecovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8145 KB)...
OKAY [ 2.182s]
writing 'recovery'...
OKAY [ 0.578s]
finished. total time: 2.763s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.001s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>
It's repeating the same behavior.
I've double checked and triple checked my drivers. The device is listed as "Kindle -> ADB Composite Device". Everythign seems to be fine on that end. I am using Windows 7 x64. I tried the fk scripts on Ubuntu with no success.
Edit: I also made my own Factory cable. Doesn't seem to have any affect on the process.
Two days of trying to figure this out and I fix it minutes after I ask for help.
I retried using the KFHD SRT v1.35 to recover the system image, deleted all user data and cache, then reformatted the /data partition. It can now boot properly into the teamwin recovery and flash ROMs as usual.
Here's a good article for people who had the same issue:
http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/

Device Locked in fastboot even with unlocked bootloader

Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
ahsank128 said:
Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
Click to expand...
Click to collapse
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Mackay53 said:
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Click to expand...
Click to collapse
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
ahsank128 said:
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
Click to expand...
Click to collapse
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Badger50 said:
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Click to expand...
Click to collapse
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
ahsank128 said:
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
Click to expand...
Click to collapse
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Badger50 said:
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Click to expand...
Click to collapse
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
ahsank128 said:
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
Click to expand...
Click to collapse
I know who you are? At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Badger50 said:
I know who you are At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Click to expand...
Click to collapse
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
ahsank128 said:
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
Click to expand...
Click to collapse
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Will attempt this, my attempt last night was to do factory reset within the settings (when phone is booted up) and then flashed with -w. But I will try again using the stock recovery. I even changed computers, this stuff is wonky sometimes
Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
DELETED
ahsank128 said:
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Click to expand...
Click to collapse
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
ahsank128 said:
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
Click to expand...
Click to collapse
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Badger50 said:
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
Click to expand...
Click to collapse
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
Code:
Sending 'bootloader' (8761 KB) OKAY [ 0.218s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_b' (82676 KB) OKAY [ 2.180s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00041-191016-B-5945070
(bootloader) Flashing partition modem_b
OKAY [ 0.650s]
Finished. Total time: 3.090s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.051s
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: g8150-00041-191016-B-5945070
Serial Number........: 99171FFAZ006J5
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.069s]
Checking 'version-bootloader' OKAY [ 0.069s]
Checking 'version-baseband' OKAY [ 0.068s]
Setting current slot to 'b' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.387s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.139s]
Writing 'boot_b' OKAY [ 0.455s]
extracting dtbo.img (8 MB) to disk... took 0.025s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.310s]
Writing 'dtbo_b' OKAY [ 0.117s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_b' OKAY [ 0.072s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.101s]
Writing 'vbmeta_system_b' OKAY [ 0.072s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.069s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_b' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2127 MB) to disk... took 15.801s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.005s]
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
bb709394 said:
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Click to expand...
Click to collapse
No, this issue happens on stock kernel. And yes USB debugging and OEM Unlock both are checked. I believe the image is correct. US Unlocked Pixel from google store. file ends in 011
ahsank128 said:
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
Click to expand...
Click to collapse
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Badger50 said:
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Click to expand...
Click to collapse
I am up and running, I'll check to see if I can get that script running later on
ahsank128 said:
I am up and running, I'll check to see if I can get that script running later on
Click to expand...
Click to collapse
Kinda sounds like you already got the script to work

Categories

Resources