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
Related
I accidentally bricked my 7" Kindle Fire HD while trying to follow "[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [12/09 FREEDOM 7.4.6]". I made a fastboot cable and have tried the System.img restore tool, first aide scripts, and straight up fastboot commands to no avail. There is a very rare chance that it will boot into the amazon os but it will shortly crash and go into a boot loop. I know it is not a driver issue because I have tested it with Linux and Windows 8. I have even tried flashing the backup files I made and it still doesn't work. Any suggestions on what I should do?
Which images did you flash? Just the system, or did you also reflash the boot partition too?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Which images did you flash? Just the system, or did you also reflash the boot partition too?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I flashed boot, recovery, and system.
jscombs91 said:
I flashed boot, recovery, and system.
Click to expand...
Click to collapse
Did it show the process as completed? What does the command window show if you type "fastboot -i 0x1949 getvar product" while in fastboot?
LinearEquation said:
Did it show the process as completed? What does the command window show if you type "fastboot -i 0x1949 getvar product" while in fastboot?
Click to expand...
Click to collapse
Yep, no errors or anything. and
Code:
[email protected]:~$ fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.000s
jscombs91 said:
Yep, no errors or anything. and
Code:
[email protected]:~$ fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.000s
Click to expand...
Click to collapse
Are you CDing from inside the folder with the three images from the system restore tool? Confirm they are for the 7". Try downloading the SDK package and sticking the images in the tool folder containing fastboot.exe and CD from there.
Edit: just to make sure these commands are being used.
fastboot -i 0x1949 flash boot "boot image name here" include .img at end
fastboot -i 0x1949 flash recovery "recovery image name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
LinearEquation said:
Are you CDing from inside the folder with the three images from the system restore tool? Confirm they are for the 7". Try downloading the SDK package and sticking the images in the tool folder containing fastboot.exe and CD from there.
Edit: just to make sure these commands are being used.
fastboot -i 0x1949 flash boot "boot image name here" include .img at end
fastboot -i 0x1949 flash recovery "recovery image name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
Click to expand...
Click to collapse
Okay I took the 3 images from http://forum.xda-developers.com/showthread.php?t=1951254 and moved them into /opt/android-sdk-linux/platform-tools/ where my fastboot executable is.
and the output from the 4 commands:
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.818s]
writing 'boot'...
OKAY [ 0.681s]
finished. total time: 3.499s
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.815s]
writing 'recovery'...
OKAY [ 0.672s]
finished. total time: 3.487s
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [311.701s]
writing 'system'...
OKAY [ 72.359s]
finished. total time: 384.060s
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.000s
once it starts it does this:
logo once
black screen
logo again
black screen
logo again
black screen
logo again
black screen
logo again
black screen
logo with shimmer animation
black screen
random green pixels on screen
black screen
logo again
black screen
logo with shimmer animation
"Kindle is upgrading..."
frozen with green pixels on screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've waited about 5 minutes and it hasn't changed.
I held down the power button for 10 seconds to turn it off and when i turn it on it goes:
logo once
black screen logo twice
logo with shimmer
"Kindle is upgrading" screen
back screen
black screen with diagonal green pixels
logo again
black screen that flashes repeatedly
jscombs91 said:
Okay I took the 3 images from http://forum.xda-developers.com/showthread.php?t=1951254 and moved them into /opt/android-sdk-linux/platform-tools/ where my fastboot executable is.
and the output from the 4 commands:
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.818s]
writing 'boot'...
OKAY [ 0.681s]
finished. total time: 3.499s
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.815s]
writing 'recovery'...
OKAY [ 0.672s]
finished. total time: 3.487s
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [311.701s]
writing 'system'...
OKAY [ 72.359s]
finished. total time: 384.060s
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.000s
once it starts it does this:
logo once
black screen
logo again
black screen
logo again
black screen
logo again
black screen
logo again
black screen
logo with shimmer animation
black screen
random green pixels on screen
black screen
logo again
black screen
logo with shimmer animation
"Kindle is upgrading..."
frozen with green pixels on screen
I've waited about 5 minutes and it hasn't changed.
I held down the power button for 10 seconds to turn it off and when i turn it on it goes:
logo once
black screen logo twice
logo with shimmer
"Kindle is upgrading" screen
back screen
black screen with diagonal green pixels
logo again
black screen that flashes repeatedly
Click to expand...
Click to collapse
I'm concerned about the shimmering and green. You're definitely bootlooping. In the system store tool there are two of one of the images if I remember right? Try using the other image with the other two. Seems I remember someone mentioning one time that one of them did not work although I don't see why not
There is always the chance the download was corrupted.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
I'm concerned about the shimmering and green. You're definitely bootlooping. In the system store tool there are two of one of the images if I remember right? Try using the other image with the other two. Seems I remember someone mentioning one time that one of them did not work although I don't see why not
There is always the chance the download was corrupted.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, there's 2 system images ("Factory Rooted with SuperSU.apk" and "Factory Rooted with SuperSU.apk, Apex Launcher, and PlayStore")
I flashed the second system image:
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 flash system system2.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [311.373s]
writing 'system'...
OKAY [ 72.372s]
finished. total time: 383.745s
sadly still doesn't work.
logo once
logo again
and a red triangle with this "Kindle Fire System Recovery" screen and green diagonal pixels:
Whenever I choose to reset to factory defaults it shows the kindle fire logo with a progress bar and then starts doing the bootloop again.
jscombs91 said:
Yep, there's 2 system images ("Factory Rooted with SuperSU.apk" and "Factory Rooted with SuperSU.apk, Apex Launcher, and PlayStore")
I flashed the second system image:
Code:
[email protected]:/opt/android-sdk-linux/platform-tools$ ./fastboot -i 0x1949 flash system system2.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [311.373s]
writing 'system'...
OKAY [ 72.372s]
finished. total time: 383.745s
sadly still doesn't work.
logo once
logo again
and a red triangle with this "Kindle Fire System Recovery" screen and green diagonal pixels:
Whenever I choose to reset to factory defaults it shows the kindle fire logo with a progress bar and then starts doing the bootloop again.
Click to expand...
Click to collapse
Red triangle means no recovery. Try using KFFA http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Red triangle means no recovery. Try using KFFA http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried that using the option "Completely Restore the KFHD 7 7.2.3" no difference
jscombs91 said:
I've tried that using the option "Completely Restore the KFHD 7 7.2.3" no difference
Click to expand...
Click to collapse
Hmmm, I'm running out of options here. We have covered everything. Maybe run the bat tool and try again.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Not to insult you or anything, Maybe the cable you made is causing a problem like not properly communicating/transmitting files between your computer and Kindle?
Maybe give this a shot?
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
LinearEquation said:
Hmmm, I'm running out of options here. We have covered everything. Maybe run the bat tool and try again.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried running KFFA with the 7.2.1 option this time and got the error messages:
Code:
Would You Like To Wipe Data And Cache (y/n) ?y
erasing 'userdata'...
OKAY [ 71.768s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.020s]
erasing 'cache'...
OKAY [ 55.814s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.015s]
finished. total time: 127.628s
And when the the red triangle appears there's addition Linux errors now:
Maybe there's something wrong with those partitions?
Jserrano56 said:
Not to insult you or anything, Maybe the cable you made is causing a problem like not properly communicating/transmitting files between your computer and Kindle?
Maybe give this a shot?
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No worries and well I checked continuity on the cable and it's perfectly fine. The only difference between a factory cable and a regular cable is the factory cable has a pull-up resistor on pin 4. And I've already tried that batch script. and still doesn't work
jscombs91 said:
I tried running KFFA with the 7.2.1 option this time and got the error messages:
Code:
Would You Like To Wipe Data And Cache (y/n) ?y
erasing 'userdata'...
OKAY [ 71.768s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.020s]
erasing 'cache'...
OKAY [ 55.814s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.015s]
finished. total time: 127.628s
And when the the red triangle appears there's addition Linux errors now:
Maybe there's something wrong with those partitions?
No worries and well I checked continuity on the cable and it's perfectly fine. The only difference between a factory cable and a regular cable is the factory cable has a pull-up resistor on pin 4. And I've already tried that batch script. and still doesn't work
Click to expand...
Click to collapse
@jscombs91
Wait... I'm new here so I don't really know the difference between the kindles fire HDs but I know there are two separate ones, one came with OS 7.x.x the others were like 11.x.x, are you 100% positive yours was a 7.x.x OS Kindle straight out of the box?
Umm honestly I'm just a new guy on this thread... Umm have you tired running the tool from the link I gave you on a higher version, I mean like flashing 7.3.0+? If we could get it to flash and boot properly we could save your Kindle, when you tried flashing the 2nd bootloader and recovery what Stock OS version was your Kindle running?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Jserrano56 said:
@jscombs91
Wait... I'm new here so I don't really know the difference between the kindles fire HDs but I know there are two separate ones, one came with OS 7.x.x the others were like 11.x.x, are you 100% positive yours was a 7.x.x OS Kindle straight out of the box?
Umm honestly I'm just a new guy on this thread... Umm have you tired running the tool from the link I gave you on a higher version, I mean like flashing 7.3.0+? If we could get it to flash and boot properly we could save your Kindle, when you tried flashing the 2nd bootloader and recovery what Stock OS version was your Kindle running?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep 100% sure. I believe it came with 7.4.6 out of the box. and I tried the 2 latest versions of that the 1.3.0 and 1.3.5 ones. an I believe it was running 7.4.6.
jscombs91 said:
Yep 100% sure. It came with 7.4.6 out of the box. and I'll try that. I've tried flashing the recovery for TWRP and it will boot into it maybe once rarely but after about 15-30 seconds it will freeze then reboot into a bootloop.
Click to expand...
Click to collapse
I'd try flashing 7.3.0 or anything higher, try using tool from the previous link I posted first, or anything else available and if it boots use KFFA to downgrade to 7.2.3 and I'd use FireFlash to flash the 2nd bootloader and recovery
When it boots is it useable for 30 secs or is it just frozen during those 30 secs and then crashes back into a boot loop?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Jserrano56 said:
@jscombs91
Wait... I'm new here so I don't really know the difference between the kindles fire HDs but I know there are two separate ones, one came with OS 7.x.x the others were like 11.x.x, are you 100% positive yours was a 7.x.x OS Kindle straight out of the box?
Umm honestly I'm just a new guy on this thread... Umm have you tired running the tool from the link I gave you on a higher version, I mean like flashing 7.3.0+? If we could get it to flash and boot properly we could save your Kindle, when you tried flashing the 2nd bootloader and recovery what Stock OS version was your Kindle running?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Jserrano56 said:
I'd try flashing 7.3.0 or anything higher, try using tool from the previous link I posted first, or anything else available and if it boots use KFFA to downgrade to 7.2.3 and I'd use FireFlash to flash the 2nd bootloader and recovery
When it boots is it useable for 30 secs or is it just frozen during those 30 secs and then crashes back into a boot loop?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the latest version which is 7.3.0 (That's the newest one I can find) and it just goes into a boot loop. and it's usable during that time then freezes and crashes.
jscombs91 said:
I tried the latest version which is 7.3.0 (That's the newest one I can find) and it just goes into a boot loop. and it's usable during that time then freezes and crashes.
Click to expand...
Click to collapse
Okay well to be honest I never used recovery until I need to use twrp so I'm not sure how stock recovery is set up but try booting into stock recovery and see if you have to option to either
1. Wipe cache and data
Or
2. Factory Reset
Let me know how it went
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Jserrano56 said:
Okay well to be honest I never used recovery until I need to use twrp so I'm not sure how stock recovery is set up but try booting into stock recovery and see if you have to option to either
1. Wipe cache and data
Or
2. Factory Reset
Let me know how it went
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe the screen with the red triangle is the stock recovery (I am unable to get to it through normal means just have to wait for it to randomly boot to that) and if it is then the reset to factory defaults button doesn't do anything to fix it.
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
Hello fellow users of the Razr i.
A friend of mine got this phone a long time ago and complained his phone wasn't starting... Since it seemed he phone got stuck on the bootscreen, i thought it would be quite easy to fix it through re-flashing another firmware, but i encountered some problems...quite a lot of them actually...
First of all, after getting on the bootloader screen, i saw the yellow message;
Fastboot Reason:
fastboot max download size: 100MB
Oddly, it doesn't show any information why it's fastboot download is limited.
I've managed to unlock the bootloader successfuly, even though it didn't really change much...
After downloading a rom and giving an attempt to flash through fastboot, it locks the whole process, failing when sending the system image, which is about 780mbs.
Searching a little bit more, i installed RSD Lite 6.1.4, and on the Device Properties side, it shows nothing at all. Everything is (N / A).
I'm not entirely sure if there's something wrong, but as far as i've noticed, the drivers and everything else seems to be working fine, since unlocking the bootloader didn't fail.
Any help on this is really appreciated!
michaelnishi said:
Hello fellow users of the Razr i.
A friend of mine got this phone a long time ago and complained his phone wasn't starting... Since it seemed he phone got stuck on the bootscreen, i thought it would be quite easy to fix it through re-flashing another firmware, but i encountered some problems...quite a lot of them actually...
First of all, after getting on the bootloader screen, i saw the yellow message;
Fastboot Reason:
fastboot max download size: 100MB
Oddly, it doesn't show any information why it's fastboot download is limited.
I've managed to unlock the bootloader successfuly, even though it didn't really change much...
After downloading a rom and giving an attempt to flash through fastboot, it locks the whole process, failing when sending the system image, which is about 780mbs.
Searching a little bit more, i installed RSD Lite 6.1.4, and on the Device Properties side, it shows nothing at all. Everything is (N / A).
I'm not entirely sure if there's something wrong, but as far as i've noticed, the drivers and everything else seems to be working fine, since unlocking the bootloader didn't fail.
Any help on this is really appreciated!
Click to expand...
Click to collapse
So u unlocked successfully. Then everything should be repairable.
The normal fastboot won't flash past 100mb for this device. So no problem there. U need to use mFastboot to get past that.
I don't know about RSD Lite. Maybe start it in administrator mode. Another thing u can do is get mFastboot and flash the system, recovery and boot manually. If that won't work we can try to use a custom rom with a custom recovery. By unlocking your warranty is already voided.
Do u know what firmware its holding? I know the device doesn't boot, but maybe u know.
Hazou said:
So u unlocked successfully. Then everything should be repairable.
The normal fastboot won't flash past 100mb for this device. So no problem there. U need to use mFastboot to get past that.
I don't know about RSD Lite. Maybe start it in administrator mode. Another thing u can do is get mFastboot and flash the system, recovery and boot manually. If that won't work we can try to use a custom rom with a custom recovery. By unlocking your warranty is already voided.
Do u know what firmware its holding? I know the device doesn't boot, but maybe u know.
Click to expand...
Click to collapse
I see...I'd need a tutorial on how to work properly with mfastboot though, never heard of it before.
And i don't know the firmware version either. I guess this is going to make it a little harder... Or we could, maybe try to use the latest possible firmware version and not worry about downgrade problems...
michaelnishi said:
I see...Id need a tutorial on how to work properly with mfastboot though, never heard of it before.
And i dont know the firmware version either. I guess this is going to make it a little harder... Or we could, maybe try to use the latest possible firmware version and not worry about downgrade problems...
Click to expand...
Click to collapse
Have a look at my signature. The Index guide in the general section. But i think to be really savwe could flash a custom rom and see what happends then. We can always go back after that.
Have a look around. I will help u if still needed, after 23.00 gmt+ for the mefastboot by making a guide for mfastboot and latest firmware. What region did the phone come?
Hazou said:
Have a look at my signature. The Index guide in the general section. But i think to be really savwe could flash a custom rom and see what happends then. We can always go back after that.
Have a look around. I will help u if still needed, after 23.00 gmt+ for the mefastboot by making a guide for mfastboot and latest firmware. What region did the phone come?
Click to expand...
Click to collapse
South America/Brazil. And thanks a lot for replying to me. I'm going to work soon, sadly, and i'm not sure when ill get back home. But as soon as i arrive i will be searching for a custom rom and trying to flash it.
Hazou said:
So u unlocked successfully. Then everything should be repairable.
The normal fastboot won't flash past 100mb for this device. So no problem there. U need to use mFastboot to get past that.
I don't know about RSD Lite. Maybe start it in administrator mode. Another thing u can do is get mFastboot and flash the system, recovery and boot manually. If that won't work we can try to use a custom rom with a custom recovery. By unlocking your warranty is already voided.
Do u know what firmware its holding? I know the device doesn't boot, but maybe u know.
Click to expand...
Click to collapse
Thanks a bunch for the help, Hazou. I've managed to get the mfastboot to work perfectly and it flashed the device as it should have. The thing is already up and running!
michaelnishi said:
Thanks a bunch for the help, Hazou. I've managed to get the mfastboot to work perfectly and it flashed the device as it should have. The thing is already up and running!
Click to expand...
Click to collapse
Glad to hear that it worked
Same issue - I trust this isn't a hijack
Good evening all,
My Razr I fails to boot, hanging on the initial Motorola M logo after the power on vibrate and green LED flash. It is unmolested in any way (no root, no custom anything). It's a UK retail ROM (from memory) and is not locked to a provider
The issue started on Sunday by randomly rebooting, the launcher crashing (home etc soft buttons not displaying). I tried to uninstall a few of the recently installed apps then upgraded what was left, only to have it reboot and not boot.
I have been browsing the forums and read a few bits and pieces, but it doesn't make much sense. I am IT literate, but new to Android in this sense of trying to fix things
So far I have installed
RSDLite v6.16
Clicking on "show device" gives me
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
In the table below Model is Fastboo SMI s
ABD:
C:\Users\User1\adb>adb devices
List of devices attached
Motorola Device Driver:
Device software update - come back later - The server is temporarily unavailable due to maintenance
I can boot into the AP Fastboot Flashmode by all 3 methods I found on here.
I get the menu in blue, where I went into recovery and formatted the cache - to no avail.
In Yellow it says:
Fastboot Reason:
Fastboot: max download size :100MB
USB Connected
I obviously have data which has no back up and I would hate to lose. Can I do a back up of everything in some way then reinstall the OS in whatever way is required?
black_cab said:
Good evening all,
My Razr I fails to boot, hanging on the initial Motorola M logo after the power on vibrate and green LED flash. It is unmolested in any way (no root, no custom anything). Its a UK retail ROM (from memory) and is not locked to a provider
The issue started on Sunday by randomly rebooting, the launcher crashing (home etc soft buttons not displaying). I tried to uninstall a few of the recently installed apps then upgraded what was left, only to have it reboot and not boot.
I have been browsing the forums and read a few bits and pieces, but it doesnt make much sense. I am IT literate, but new to Android in this sense of trying to fix things
So far I have installed
RSDLite v6.16
Clicking on "show device" gives me
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
In the table below Model is Fastboo SMI s
ABD:
C:\Users\User1\adb>adb devices
List of devices attached
Motorola Device Driver:
Device software update - come back later - The server is temporarily unavailable due to maintenance
I can boot into the AP Fastboot Flashmode by all 3 methods I found on here.
I get the menu in blue, where I went into recovery and formatted the cache - to no avail.
In Yellow it says:
Fastboot Reason:
Fastboot: max download size :100MB
USB Connected
I obviously have data which has no back up and I would hate to lose. Can I do a back up of everything in some way then reinstall the OS in whatever way is required?
Click to expand...
Click to collapse
Search for mFastboot in the index thread. Make sure u have your firmware ready and unpacked. Reboot in fastboot mode and do the command "mfastboot devices" when device is connected to usb. It will list your device.
Now try to flash the system partition by sending the command "mfastboot flash system <path to system image>"
Do the same with the boot.img with the command "mfastboot flash boot <path to boot image>
If this wont work, there is no possible way to get your data back as far as i know.
Hi, thanks for the quick reply
Hazou said:
Search for mFastboot in the index thread. Make sure u have your firmware ready and unpacked. Reboot in fastboot mode and do the command "mfastboot devices" when device is connected to usb. It will list your device.
Click to expand...
Click to collapse
I guess I am looking for the closest firmware to what I have? I did see a link to a page of images somewhere in this section, so will find it again
Hazou said:
Now try to flash the system partition by sending the command "mfastboot flash system <path to system image>"
Do the same with the boot.img with the command "mfastboot flash boot <path to boot image>
If this wont work, there is no possible way to get your data back as far as i know.
Click to expand...
Click to collapse
Cool will give it a go
filenames?
I downloaded and unzipped CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml.zip to C:\Users\User1\android\firmware\CFC which contains the following files
Directory of C:\Users\User1\android\firmware\CFC
05/11/2014 19:38 11,534,336 boot_signed
05/11/2014 19:38 8,160,652 bos_signed
05/11/2014 19:39 54,536,192 cdrom_signed
05/11/2014 19:39 1,462 CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml
05/11/2014 19:39 66,528 dnx
05/11/2014 19:39 32,768 gpt_signed
05/11/2014 19:39 1,937,660 ifwi
05/11/2014 19:39 875,336 logo_signed
05/11/2014 19:39 23,832,048 motoboot
05/11/2014 19:39 17,501,930 motobp
05/11/2014 19:39 11,534,336 recovery_signed
05/11/2014 19:40 850,539,260 system_signed
05/11/2014 19:40 875,336 ulogo_signed
mfastboot devices results in TA32404O14 fastboot
So far so good
Hazou said:
Now try to flash the system partition by sending the command "mfastboot flash system <path to system image>"
Do the same with the boot.img with the command "mfastboot flash boot <path to boot image>
Click to expand...
Click to collapse
so my commands will be
mfastboot flash system C:\Users\User1\android\firmware\CFC\system_signed
mfastboot flash boot c:\...\motoboot ?
black_cab said:
I downloaded and unzipped CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml.zip to C:\Users\User1\android\firmware\CFC which contains the following files
Directory of C:\Users\User1\android\firmware\CFC
05/11/2014 19:38 11,534,336 boot_signed
05/11/2014 19:38 8,160,652 bos_signed
05/11/2014 19:39 54,536,192 cdrom_signed
05/11/2014 19:39 1,462 CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml
05/11/2014 19:39 66,528 dnx
05/11/2014 19:39 32,768 gpt_signed
05/11/2014 19:39 1,937,660 ifwi
05/11/2014 19:39 875,336 logo_signed
05/11/2014 19:39 23,832,048 motoboot
05/11/2014 19:39 17,501,930 motobp
05/11/2014 19:39 11,534,336 recovery_signed
05/11/2014 19:40 850,539,260 system_signed
05/11/2014 19:40 875,336 ulogo_signed
mfastboot devices results in TA32404O14 fastboot
So far so good
so my commands will be
mfastboot flash system C:\Users\User1\android\firmware\CFC\system_signed
mfastboot flash boot c:\...\motoboot ?
Click to expand...
Click to collapse
The system is good. For boot take boot_signed
Hazou said:
The system is good. For boot take boot_signed
Click to expand...
Click to collapse
mfastboot flash system C:\Users\User1\android\firmware\CFC\system_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 10.125s]
writing 'system'...
OKAY [ 2.769s]
sending 'system' (102400 KB)...
OKAY [ 16.931s]
writing 'system'...
OKAY [ 2.668s]
sending 'system' (102400 KB)...
OKAY [ 14.804s]
writing 'system'...
OKAY [ 2.687s]
sending 'system' (102400 KB)...
OKAY [ 14.098s]
writing 'system'...
OKAY [ 2.497s]
sending 'system' (102400 KB)...
OKAY [ 14.420s]
writing 'system'...
OKAY [ 2.508s]
sending 'system' (102400 KB)...
OKAY [ 12.225s]
writing 'system'...
OKAY [ 2.499s]
sending 'system' (102400 KB)...
OKAY [ 14.111s]
writing 'system'...
OKAY [ 2.474s]
sending 'system' (102400 KB)...
OKAY [ 14.652s]
writing 'system'...
OKAY [ 2.509s]
sending 'system' (11404 KB)...
OKAY [ 8.356s]
writing 'system'...
OKAY [ 2.071s]
finished. total time: 142.472s
mfastboot flash boot C:\Users\User1\android\firmware\CFC\boot_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.448s]
writing 'boot'...
OKAY [ 3.181s]
finished. total time: 4.635s
So it looks like the images were sent.
On the phone I got a few Downloading ... MultiFlashing system ... etc
then
MultiFlashing system ...
Getvar max-sparse-size
Fastboot command failed
Now it says Flashing boot, but seems to be hung, been like that for 5 mins or so. How long should it take?
Actually ignore that, it has booted!
Thanks very much for all your assistance
Glad it worked
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?
I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s
I've managed to resolve it for anyone else that might read this....
Follow the guide here https://forum.xda-developers.com/tr...f701t-nvflash-unbrick-solutiontested-t3742848 and use the NvFlash TF701T Unbrick tool, you need to do a bit of prep but it worked for me
Big thanks to Mr.Bin for this fix.
Cheers and good luck
Martin
martinnut said:
I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s
Click to expand...
Click to collapse