[Q] Still stuck in fastboot after flashing back original system images?? - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi Folks,
I have checked through the various threads on xda about this but cannot find an answer so please be gentle.
I mistakenly flashed an incorrect kernel and so used fastboot to try and restore my orignal system backups. Now I am stuck on Fastboot screen.
I also cannot get ADB to see my device.
I have tried the other various unbrick tools on xda but had no luck. What are my options on this one?
thanks in adance.
Cheers,
Trev

You don't use adb commands to work with fastboot, so adb devices is useless. You have to use fastboot commands. As a test run "fastboot -i 0x1949 getvar product" it should return Tate if you posted this in the right device section.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Hi stunts513,
yeah its tate. I was able to use fastboot see output.
C:\ Fastboot>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.008s
C:\ Fastboot>fastboot -i 0x1949 flash boot C:\Users\ADMIN\Downloads\stock-boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.828s]
writing 'boot'...
OKAY [ 0.678s]
finished. total time: 3.508s
C:\ Fastboot>fastboot -i 0x1949 flash recovery C:\Users\ADMIN\Downloads\stock-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.828s]
writing 'recovery'...
OKAY [ 0.673s]
finished. total time: 3.504s
C:\ Fastboot>fastboot -i 0x1949 flash system C:\Users\ADMIN\Downloads\stock-system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.761s]
writing 'system'...
OKAY [ 73.290s]
finished. total time: 386.067s

So is it stuck in fastboot now or does it boot loop when you get out of fastboot?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

still stuck on Fastboot my friend. :crying:

Got it sorted. After issuing reboot I immediately pulled out the usb cable. Thanks for the help. :good:

Ah sorry, was going to advise that but I'm kinda busy trying to figure out how to compile this ROM, its so different than the stuff I'm used to compile so I'm kinda lost. Anyways glad to hear you fixed it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Ah sorry, was going to advise that but I'm kinda busy trying to figure out how to compile this ROM, its so different than the stuff I'm used to compile so I'm kinda lost. Anyways glad to hear you fixed it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
im having the same problem.. however unplugging the cable right after the reboot command still doesn't help. it goes right back to fastboot no matter what

Related

*sigh* Red screen when booting

Hello. I have a kindle fire hd 7" version 7.4.3 that I had recently just rooted. All was fine except I tried to install the second bootloader, twrp and such.
I followed the directions but on the final reboot, I got a red screen of death. I can access fastboot via a cable but I can't access adb commands.
Please help! I will continue to look around for help. Thanks.
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools>
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools> fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
target reported max download size of 1006632960 bytes
error: cannot load 'kfhd7-u-boot-prod-7.2.3.bin': No error
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools>fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.3.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.861s]
writing 'boot'...
OKAY [ 1.660s]
finished. total time: 4.531s
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools>fastboot -i 0x1949 flash recovery kfhd7-twrp-2.6.0.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8145 KB)...
OKAY [ 2.860s]
writing 'recovery'...
OKAY [ 1.250s]
finished. total time: 4.110s
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.000s
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.010s
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools>fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.3.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.860s]
writing 'boot'...
OKAY [ 1.700s]
finished. total time: 4.560s
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.000s
C:\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\pla
tform-tools>
tad bit confused said:
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
target reported max download size of 1006632960 bytes
error: cannot load 'kfhd7-u-boot-prod-7.2.3.bin':
Click to expand...
Click to collapse
You seem to have ignored the above error and continued anyway. It appears that you should be in good shape if you can get that file to flash correctly. Double check the local file name against the one in the command and make sure they match.
Please double check the md5sum on the bootloader file. This file needs to be 100% intact or you will hard brick the device. And probably have to return it to Amazon.
Sent from my XT926 using Tapatalk 2

[Q] Bootloop issues

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.

[Q] Orange logo for 2 seconds then black screen

I've got a broken Kindle Fire HD 7 with the following problem:
When I try to power it up, I get the Orange/White logo for two seconds, then a black screen.
While the logo is on, the rest of the entire screen is lit up grey.
After it goes to black screen there is still a tiny bit of light in the corners so it is not powered down.
When I hold the power button for 10 sec the bit of light goes away.
I have a fastboot cable and during the black screen fastboot -i 0x1949 getvar product yields
product: Tate-PVT-08
I tried using KFHD_SRT_v1.3.0 to Restore-Factory Rooted with SuperSU.apk and Restore-Factory Recovery but neither had any effect.
I also replaced the motherboard with one that I bought from a seller that said it was removed from a working Kindle Fire HD but with the new motherboard I am having the exact same problem.
I am really perplexed. Could a bad LCD panel be causing this problem?
Any help would be greatly appreciated.
Anchorman42 said:
I've got a broken Kindle Fire HD 7 with the following problem:
When I try to power it up, I get the Orange/White logo for two seconds, then a black screen.
While the logo is on, the rest of the entire screen is lit up grey.
After it goes to black screen there is still a tiny bit of light in the corners so it is not powered down.
When I hold the power button for 10 sec the bit of light goes away.
I have a fastboot cable and during the black screen fastboot -i 0x1949 getvar product yields
product: Tate-PVT-08
I tried using KFHD_SRT_v1.3.0 to Restore-Factory Rooted with SuperSU.apk and Restore-Factory Recovery but neither had any effect.
I also replaced the motherboard with one that I bought from a seller that said it was removed from a working Kindle Fire HD but with the new motherboard I am having the exact same problem.
I am really perplexed. Could a bad LCD panel be causing this problem?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you try using Kindle Fire First Aide? It's got a system restore feature built into it, and it's saved my sorry butt on more than one occasion.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
Ok, I tried using Kindle Fire First Aide and here is what I get:
9. Display the Fastboot Status
product: Tate-PVT-08
finished. total time: 0.001s
05EC000200000001 fastboot
3. Completly Restore the KFHD 7 7.2.3
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
8. Erase the Kindle Cache and User Data
erasing 'userdata'...
OKAY [ 71.909s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.006s]
erasing 'cache'...
OKAY [ 55.930s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.005s]
finished. total time: 127.853s
rebooting...
finished. total time: -0.000s
Anchorman42 said:
Ok, I tried using Kindle Fire First Aide and here is what I get:
9. Display the Fastboot Status
product: Tate-PVT-08
finished. total time: 0.001s
05EC000200000001 fastboot
3. Completly Restore the KFHD 7 7.2.3
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
8. Erase the Kindle Cache and User Data
erasing 'userdata'...
OKAY [ 71.909s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.006s]
erasing 'cache'...
OKAY [ 55.930s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.005s]
finished. total time: 127.853s
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse
Hmmm... It looks like the script is working, and fastboot is working too. Is it finding the images on your computer? They're .img files, and they would be somewhere in the KFFA folder.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
Anchorman42 said:
Ok, I tried using Kindle Fire First Aide and here is what I get:
9. Display the Fastboot Status
product: Tate-PVT-08
finished. total time: 0.001s
05EC000200000001 fastboot
3. Completly Restore the KFHD 7 7.2.3
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
8. Erase the Kindle Cache and User Data
erasing 'userdata'...
OKAY [ 71.909s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.006s]
erasing 'cache'...
OKAY [ 55.930s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.005s]
finished. total time: 127.853s
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse
The procedures are finishing almost instantaneously. This should be taking much longer. Around an hour or so just for the files to flash onto your KFHD. I would try the Kindle fire System Restore Tool again (this one is for 2012 KFHD 7 only http://forum.xda-developers.com/showthread.php?t=1951254 Same one as you tried before and use it with a fastboot factory cord.
Here is a tip you can use with the standard USB http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm If you're using a standard USB cord it will not work because you are bootlooping and the option to boot into the bootloader with a standard USB cord is gone.
LinearEquation said:
The procedures are finishing almost instantaneously. This should be taking much longer. Around an hour or so just for the files to flash onto your KFHD. I would try the Kindle fire System Restore Tool again (this one is for 2012 KFHD 7 only http://forum.xda-developers.com/showthread.php?t=1951254 Same one as you tried before and use it with a fastboot factory cord.
Here is a tip you can use with the standard USB http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm If you're using a standard USB cord it will not work because you are bootlooping and the option to boot into the bootloader with a standard USB cord is gone.
Click to expand...
Click to collapse
An hour??? Mine has never taken any longer than ten minutes to complete!
Anyway, I think KFFA attempts to download the images from @prokennexusa's Box/Dropbox accounts, which aren't active anymore. I think that may be why flashing via KFFA isn't working. There are no images to flash.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
Ph0enix_216 said:
An hour??? Mine has never taken any longer than ten minutes to complete!
Anyway, I think KFFA attempts to download the images from @prokennexusa's Box/Dropbox accounts, which aren't active anymore. I think that may be why flashing via KFFA isn't working. There are no images to flash.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
Click to expand...
Click to collapse
I wonder what the heck Chris is doing. I hope he is well what ever he is doing these days.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Ph0enix_216 said:
An hour??? Mine has never taken any longer than ten minutes to complete!
Anyway, I think KFFA attempts to download the images from @prokennexusa's Box/Dropbox accounts, which aren't active anymore. I think that may be why flashing via KFFA isn't working. There are no images to flash.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
Click to expand...
Click to collapse
You were right, the images were not getting downloaded from the Dropbox location. But the problem was that the wget command in RunMe.bat was failing because it couldn't verify the certificate. I had to add --no-check-certificate after wget and then the image files all downloaded. It did take about 10 minutes for system.img to download.
But now that the images are available in C:\KFFirstAide the command to flash them is failing.
I copied the flash commands from RunMe.bat into a CMD window and this is what I got.
C:\KFFirstAide>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
But if I check the Fastboot status:
C:\KFFirstAide>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.002s
It appears the Fastboot is working, but for some reason it can't flash the partitions.
I am using a Factory Cable but I don't see why that would matter.
And remember, in my original post I said that the original motherboard was acting this way so I bought another motherboard on eBay which the seller said that it came out of a working Kindle Fire and it's doing the same thing as the original motherboard. To me, it's really strange that both motherboards are acting the same way.
Tomorrow I plan on trying what LinearEquation suggested.
Anchorman42 said:
You were right, the images were not getting downloaded from the Dropbox location. But the problem was that the wget command in RunMe.bat was failing because it couldn't verify the certificate. I had to add --no-check-certificate after wget and then the image files all downloaded. It did take about 10 minutes for system.img to download.
But now that the images are available in C:\KFFirstAide the command to flash them is failing.
I copied the flash commands from RunMe.bat into a CMD window and this is what I got.
C:\KFFirstAide>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
But if I check the Fastboot status:
C:\KFFirstAide>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.002s
It appears the Fastboot is working, but for some reason it can't flash the partitions.
I am using a Factory Cable but I don't see why that would matter.
And remember, in my original post I said that the original motherboard was acting this way so I bought another motherboard on eBay which the seller said that it came out of a working Kindle Fire and it's doing the same thing as the original motherboard. To me, it's really strange that both motherboards are acting the same way.
Tomorrow I plan on trying what LinearEquation suggested.
Click to expand...
Click to collapse
You could also try flashing the partitions manually:
Code:
fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"
I don't think it's a motherboard issue. I've had problems where KFFA wouldn't flash partitions, but manually flashing them myself worked fine. Anyways, that's just my two cents.
Ph0enix_216 said:
You could also try flashing the partitions manually:
Code:
fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"
I don't think it's a motherboard issue. I've had problems where KFFA wouldn't flash partitions, but manually flashing them myself worked fine. Anyways, that's just my two cents.
Click to expand...
Click to collapse
I did try flashing them manually. In my reply that you quoted, where I said:
"I copied the flash commands from RunMe.bat into a CMD window and this is what I got."
C:\KFFirstAide>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
I'm not sure what "target reported max download size of 1006632960 bytes" means. I think it means that the partition is not big enough to accomodate the image file being flashed, but (for example) boot.img is only 8,192 bytes.
I am now going to try what LinearEquation suggested yesterday and see if that helps...
So I tried LinearEquation's suggestion to try the Kindle fire System Restore Tool again. This time I downloaded KFHD_SRT_v1.3.5 where yesterday I had used KFHD_SRT_v1.3.0.
This time when I tried Option 1 Restore-Factory Rooted with SuperSU.apk it actually appeared to flash the system.img file. It took about 5 minutes to "send" the file and then another 5 minutes to flash it. There were no error messages such as "target reported max download size of 1006632960 bytes" during the flash And the batch files echoed "Welcome Back" when it was done flashing.
So then, I tried Option 3. Restore-Factory Recovery and again both recovery.img and boot.img appeared to flash normally, but of course much quicker.
Then, I dis-connected the factory cable and powered down the Kindle and then powered it back up. Still not working. The only difference is that now, I don't see the Kindle Fire logo on the grey background. It just goes immediately to the black screen. But when I power it down by holding the power button for 20 seconds and then plug it in via the factory cable I do see the logo for 2 seconds and then black screen.
Edit: I was mistaken, I do get the KF logo on grey background when powering up the KF.
The only thing I can think of that could be a problem is that I am using my laptop with Windows 7 and the USB ports are USB 2.0. I remember reading quite a while back that you shouldn't use USB 2.0 ports. Is that still the case or have things evolved to where 2.0 is ok now?
Windows 7 is fine, and the problematic usb is 3.0 not 2.0. What exactly happened that made it get in this state to begin with?
Sent from my LG-P769 using xda app-developers app
stunts513 said:
Windows 7 is fine, and the problematic usb is 3.0 not 2.0. What exactly happened that made it get in this state to begin with?
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
My mistake, I should have said that all the USB ports on my laptop are 3.0. I don't know how it got this way. I bought it on eBay thinking that I would be able to fix it without too much trouble. I used to fix a few Gen1 Kindles that were stuck on the boot logo but I have since found out that Gen2 and above are different animals.
Anchorman42 said:
I did try flashing them manually. In my reply that you quoted, where I said:
"I copied the flash commands from RunMe.bat into a CMD window and this is what I got."
C:\KFFirstAide>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
I'm not sure what "target reported max download size of 1006632960 bytes" means. I think it means that the partition is not big enough to accomodate the image file being flashed, but (for example) boot.img is only 8,192 bytes.
I am now going to try what LinearEquation suggested yesterday and see if that helps...
Click to expand...
Click to collapse
The "target max size" just reports the total space available to use on the device. It reports that anytime you flash anything via fastboot.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
This problem turned out to be a defective LCD panel. I got another KFHD7 and swapped the motherboards. The unit with the questionable LCD and a known good motherboard still had the original problem in the initial post. The unit with the questionable motherboard and known good LCD worked fine.

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/

LOCKED BOOTLOADER No USB DEBUGGING STUCK IN FASTBOOT LOOP

Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.
No such options
Psychotic0666 said:
try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.
Click to expand...
Click to collapse
Dude thanks, but i dont have WIPE CACHE RESTART OPTIONS, plus i cant boot into any recovery TWRP or CHINESE stock, Thankfully i found a way to unlock bootloader i guess via FASTBOOT, , still no response and unable to get into OTG OR DATA RESET OR CACHE RESET OPTIONS
Here is the list of options i got.
REBOOT SYSTEM NOW = BOOTLOOP AGAIN
REBOOT TO RECOVERY MODE = BOOTLOOP AGAIN
REBOOT TO EMEG RECOVERY MODE = Black Screen no response.
BOOT TO EDLOAD = Success as PC detects the phone as a Qualcomm Device, NUBIA Recovery soft (Very old) also detects phone
POwer off = Bootloop AGAIN
KIndly help
thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.
Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.
JerryYin said:
Hi, maybe you should flash the twrp and use twrp to flash the stock udate package, the RM3 twrp can flash stock ota
package
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
Psychotic0666 said:
Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
JerryYin said:
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.
Click to expand...
Click to collapse
thel'vadam said:
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
Click to expand...
Click to collapse
My suggestion is that flash the global version recovery first, and see if it can boot.
JerryYin said:
My suggestion is that flash the global version recovery first, and see if it can boot.
Click to expand...
Click to collapse
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,
thel'vadam said:
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,
Click to expand...
Click to collapse
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"
JerryYin said:
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED
thel'vadam said:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED
Click to expand...
Click to collapse
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this
JerryYin said:
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this
Click to expand...
Click to collapse
Can please elaborate this a little bit, also be informed that my RM3 is indian variant, it has separate indian variant ROM available from Nubia India 1.96 GB, so In my opinion GLOBAL AND CHINESE ROM s both wont work, my luck rests with the indian ROM. Ill still try whatever you suggest.
Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work
Psychotic0666 said:
Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.166s]
finished. total time: 0.167s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modem
erasing 'modem'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.748s]
writing 'dsp'...
OKAY [ 0.343s]
finished. total time: 2.093s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash parameter parameter.img
target reported max download size of 805306368 bytes
sending 'parameter' (0 KB)...
OKAY [ 0.009s]
writing 'parameter'...
OKAY [ 0.004s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 3.432s]
writing 'boot'...
OKAY [ 0.406s]
finished. total time: 3.840s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.139s]
writing 'recovery'...
OKAY [ 0.518s]
finished. total time: 2.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.207s]
writing 'splash'...
OKAY [ 0.056s]
finished. total time: 0.265s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144180 KB)...
OKAY [ 3.778s]
writing 'modem'...
OKAY [ 1.045s]
finished. total time: 4.826s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system'...
OKAY [ 0.027s]
sending sparse 'system' 1/5 (778291 KB)...
OKAY [ 17.596s]
writing 'system' 1/5...
OKAY [ 0.004s]
sending sparse 'system' 2/5 (697207 KB)...
OKAY [ 22.095s]
writing 'system' 2/5...
OKAY [ 0.003s]
sending sparse 'system' 3/5 (752301 KB)...
OKAY [ 24.678s]
writing 'system' 3/5...
OKAY [ 0.003s]
sending sparse 'system' 4/5 (782303 KB)...
OKAY [ 30.918s]
writing 'system' 4/5...
OKAY [ 0.003s]
sending sparse 'system' 5/5 (723054 KB)...
OKAY [ 30.517s]
writing 'system' 5/5...
OKAY [ 0.002s]
finished. total time: 125.859s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>
STILL SAME
Did you flash the files from global rom?
same incident.
thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?
godric12 said:
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?
Click to expand...
Click to collapse
i was once able to get a white screen with green highlighted squicircles, it did allow me to acess the boot from OTG option, i tried installing the indian ROM, it installed successfully, then after restart, same FASTBOOT LOOP WITH ERROR, i dont know how i got to that menu, i repeated the exact steps again, im still not able to get PAST BOOT LOOP.
Psychotic0666 said:
Did you flash the files from global rom?
Click to expand...
Click to collapse
YES TRIED ALL GLOBAL CHINESE indian, all variants. All recovery files all respective System.img files.
IM USING ORIGINAL IN BOX USB C cable if thats a thing,
Though i do get this ERROR (( Invalid sparse file format at header magic )) while pushing SYSTEM.img, it still suceeds, in 5/5 parts. after brief waiting.
Switch off the device and turn back on the Try going to recovery manually with vol and power button

Categories

Resources