Related
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Kamakookie said:
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Click to expand...
Click to collapse
Maybe go into twrp and do a factory reset. Can you get to that menu? Click wipe and then factory reset.
I've tried the factory reset but it seems to have no effect on it. How do I do the adb push? I've tried using the command prompt to run some of the commands on other threads but I'm not doing something right. I always get an 'adb' is not recognized as an internal or external command, operable program or batch file error.
I'll apologize now for my stupidity on this one- I have never worked with android software before this.
The kindle fire utility reads:
ADB status: Offline
Boot Status: Unknown
I can get it to boot in normal and recovery mode, but each time I try to boot in Fastboot I get an error message 'Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on.' The Kindle shows up in Device Manager under Android Phone as Android ADB Interface
When using the twrp, anything that involves writing to or wiping the sd card receives this error E:failed to mount /sdcard (invalid argument)
I'd appreciate any help I can get. I'm at a standstill on this one.
im in the same position you can open it as a USB by selecting mount in TWRP and selecting mount USB Storage
do you have drivers / ADB on your computer ?
I did manage to get my kindle go into a recovery boot loop by doing the root procedure for the original 6.3 original Amazon ROM while my kindle had the 6.2 ROM . After i realized that the root procedure (intended for ver 6.3) didn't work for me, I had to try the procedure for rooting ver. 6.2.
It worked but after a couple of resets, the tablet went into a recovery boot loop.
what i did was to use ADB comands:
enter windows - > start command prompt (start - > run -> cmd)
check if kindle is connected: adb devices
if the device is found then use:
adb shell
su
idme bootmode 4000
exit
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
lukebunny said:
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
Click to expand...
Click to collapse
At startup hold thepower button untill you see the bootmenu come up and select "normal boot"
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
lukebunny said:
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
Click to expand...
Click to collapse
What version of TWRP do you have?
2.2.0
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Tried it, no go.
This is what I get in the command line
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Have you tried reboot to bootloader?
Sent from my Galaxy Nexus using Tapatalk 2
hey i got your answer I think? lol anyways...
soupmagnet said:
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Click to expand...
Click to collapse
i'm pretty sure it's bla bla bla \platform-tools in that picture anyways that my answer anyways, maybe not but goodluck anyways........... and this 5 mins between post for low posting users is for the birds
digital_cha0s said:
i'm pretty surs it's bla bla bla \platform-tools in that picture anyways that my answer anyways goodluck
Click to expand...
Click to collapse
As you can see, the "adb shell" command is successful because of the change in the prompt.
~ # <-indicates the shell is working and active, so the actual /path of adb is irrelavent.
soupmagnet said:
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Click to expand...
Click to collapse
That seems promising, but this is what I got when I tried it.
Also, thanks for your help everyone, I'm learning a lot as I go here!
Hi all, I'm hoping to get some help or advice. I have a 1st gen Kindle Fire. When I received it, it had the stock bootloader installed and appeared to be stuck in fastboot mode. I performed the following steps:
1. used a factory cable to get access to fastboot
2. used soupkit (in Unbuntu 10.10) to flash FFF 1.4a and TWRP 2.2.2.1. Both flashed successfully.
3. turned the Kindle off (holding power for 20 secs)
4. switched over to a normal USB cable
5. powered up and issued 'fastboot getvar product' to stop FFF in fastboot
6. ran 'fastboot oem idme bootmode 4000' to reset to normal bootmode
7. 'fastboot reboot'
8. in FFF chose recovery (power led turned orange and FFF says booting)
9. stuck
I've tried reflashing FFF and TWRP several times, redownloaded and check MD5 (all ok). No matter what I do it seems this KF refuses to move past the bootloader.Any help or ideas? Thanks for your time.
freyp2 said:
Hi all, I'm hoping to get some help or advice. I have a 1st gen Kindle Fire. When I received it, it had the stock bootloader installed and appeared to be stuck in fastboot mode. I performed the following steps:
1. used a factory cable to get access to fastboot
2. used soupkit (in Unbuntu 10.10) to flash FFF 1.4a and TWRP 2.2.2.1. Both flashed successfully.
3. turned the Kindle off (holding power for 20 secs)
4. switched over to a normal USB cable
5. powered up and issued 'fastboot getvar product' to stop FFF in fastboot
6. ran 'fastboot oem idme bootmode 4000' to reset to normal bootmode
7. 'fastboot reboot'
8. in FFF chose recovery (power led turned orange and FFF says booting)
9. stuck
I've tried reflashing FFF and TWRP several times, redownloaded and check MD5 (all ok). No matter what I do it seems this KF refuses to move past the bootloader.Any help or ideas? Thanks for your time.
Click to expand...
Click to collapse
Maybe try different versions of FFF and/or TWRP? You can also try the KFU tool http://forum.xda-developers.com/showthread.php?t=1399889
still perplexed
Thanks Scoobio, I did try that too. So far I have successfully installed 3 versions of bootloader (FFF 1.4a, FFF with yellow triangle, and also stock from Amazon). All three install successfully. Unfortunately all three have the same symptoms. I am able to execute fastboot commands to flash images, getvar, etc, etc, and they complete successfully. However anytime I "ask" or "let" the bootloader try to boot system or recovery it hangs. FFF 1.4a hangs, previous "yellow triangle" version of FFF hangs, stock also hangs - always at the same point. The screen never flashes like it does when the recovery or kernel first loads. So I don't think its making it that far.
I've tried with factory cable, regular usb, no usb at all. Always hangs on boot. I also tried running KFU in Windows (same problems), SoupKit (same problems), and FireKit (same problems). Last thing I tried was usb_fix_parts_and_install_fff_twrp. It also ran successfully but still same problem.
At this point I don't care so much about fixing the kindle as much as solving the riddle. I'd like to figure this out just so I know...you know I can't let the machine win. So I'm wondering if it could be bad memory blocks or something else missing...will update if i discover anything further. Any ideas greatly appreciated.
Oh and...I am able to reset bootmode back to normal or recovery or fastboot...always completes the command successfully but never makes a difference.
Hello,
Without beating myself up, here is what I did:
1. used steps from another site to root my Kindle Fire HD 8.9 and attempt to load Android 4.4.2 on it. First major mistake.
2. during that process, the steps to make a backup didn't work and I continued. I realize that was my second major mistake, one from which I cannot recover.
3. attempted to use a Factory Image found on this site. I followed the steps, and when I perform the "fastboot -i 0x1949" reboot command, I get the "kindle fire" orange logo, and it sits there. I'm guessing it's bricked.
4. without giving up, I attempted to follow the commands found on this site here (http://forum.xda-developers.com/showthread.php?t=2128175), but I've been unsuccessful.
So, I'm stuck looking at the "kindle fire" orange logo. My thoughts were to get an image on the device and boot into it to at least get all the necessary files for flashing the image. Nope. I would appreciate any assistance. I will also state that I am a very fresh NooB when it comes to these things. I thought I was prepared, but I guess not enough.
TIA!
Mike
mikeroundrock said:
Hello,
Without beating myself up, here is what I did:
1. used steps from another site to root my Kindle Fire HD 8.9 and attempt to load Android 4.4.2 on it. First major mistake.
2. during that process, the steps to make a backup didn't work and I continued. I realize that was my second major mistake, one from which I cannot recover.
3. attempted to use a Factory Image found on this site. I followed the steps, and when I perform the "fastboot -i 0x1949" reboot command, I get the "kindle fire" orange logo, and it sits there. I'm guessing it's bricked.
4. without giving up, I attempted to follow the commands found on this site here (http://forum.xda-developers.com/showthread.php?t=2128175), but I've been unsuccessful.
So, I'm stuck looking at the "kindle fire" orange logo. My thoughts were to get an image on the device and boot into it to at least get all the necessary files for flashing the image. Nope. I would appreciate any assistance. I will also state that I am a very fresh NooB when it comes to these things. I thought I was prepared, but I guess not enough.
TIA!
Mike
Click to expand...
Click to collapse
if you never installed the fastboot drivers that would explain the issue. when the kindle first turns on after you plug it in while off, it should briefly be detected as a jem device in the device manager. if it already has the drivers installed it will briefly show up as a adb device. if you don't have the drivers installed then grab the ones from mg SIG and extract them somewhere and point the update driver box to it in the few seconds it is detected. once it is installed power the kindle off! run the "fastboot -I 0x1949 getvar product" and when it says waiting for device, plug in the kindle while it is off, it should go into fastboot.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
if you never installed the fastboot drivers that would explain the issue. when the kindle first turns on after you plug it in while off, it should briefly be detected as a jem device in the device manager. if it already has the drivers installed it will briefly show up as a adb device. if you don't have the drivers installed then grab the ones from mg SIG and extract them somewhere and point the update driver box to it in the few seconds it is detected. once it is installed power the kindle off! run the "fastboot -I 0x1949 getvar product" and when it says waiting for device, plug in the kindle while it is off, it should go into fastboot.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
OK. I followed your instructions and installed the driver. I then attempted to install a base image following the instructions here:http://forum.xda-developers.com/showthread.php?t=2011126
I chose the following prompts: 1. enable fastboot, then 2. Restore-su/supersu.apk only, then 4. Erase cache and userdata, and finally Reboot normally. No luck.
I'd really appreciate any and all ideas/help. My hope is to turn this brick into something productive again.
What are you using to restore the kindle?
stunts513 said:
What are you using to restore the kindle?
Click to expand...
Click to collapse
All I have are whatever people have shared. As mentioned in my initial post, I do not have a backup of what I had before I started. Perhaps my biggest mistake. My understanding is that I need to get the Kindle software back on it in order to install the Android bits. Perhaps I am in error on that thinking. Please let me know if that is an unneeded step.
Use either kindle fire first aid or system restore tool and stay away from kindle fire utility unless you want a paperweight.
This all started when I accidentally wiped /system in TWRP. I tried to sideload a .zip but it wouldn't install, then I realized I still had my cm11 images on the internal storage. Got that flashed, then I flashed the gapps. I tried to restart the Kindle from TWRP, then all of a sudden this slide thing came up. It was something that had something to do with SuperSU and the words "Do Not Install" in caps. Also it showed up right as I was sliding to restart. Now it's sitting at the white and orange Kindle Fire startup screen. I hope I'm not bricked, because I don't have access to recovery, I don't have access/money for a fastboot cable, nor can I make one. If I have to, I might be able to make one. Thanks for your help if you can.
kernelpanic_ said:
This all started when I accidentally wiped /system in TWRP. I tried to sideload a .zip but it wouldn't install, then I realized I still had my cm11 images on the internal storage. Got that flashed, then I flashed the gapps. I tried to restart the Kindle from TWRP, then all of a sudden this slide thing came up. The only thing I got from it before it restarted was DO NOT INSTALL and SuperSU, but it showed up right as I was sliding to restart. Now it's sitting at the white and orange Kindle Fire startup screen. I hope I'm not bricked, because I don't have access to recovery, I don't have access/money for a fastboot cable, nor can I make one. If I have to, I might be able to make one. Thanks for your help if you can.
Click to expand...
Click to collapse
This is the screen atm.
kernelpanic_ said:
This is the screen atm.
Click to expand...
Click to collapse
Assuming you have the fastboot drivers installed, this should work even without a fastboot cable. First, unplug your kindle from the USB cable and make sure it's completely powered off. Next, in a command prompt (Windows) or a Terminal (Ubuntu), type "fastboot -i 0x1949 getvar product" without quotes, and press enter. You should see a message looking like "< waiting for device >", plug your kindle in if so. The kindle should now display the orange-and-white logo like in your screenshot, and then after a few seconds, it should change into a "fastboot mode" screen. If you can get this far, then you shouldn't be completely bricked.
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
piffdaddy420 said:
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
Click to expand...
Click to collapse
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
monster1612 said:
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, actually i am using windows 10. My thinkpad has windows 7, so i will try to do this using windows 7. i will post back with results. its funny, out of everywhere i looked nobody mentioned windows 8+ having to disable enforcement. actually it will probably just be easier just to disable the enforcement. ill give it a try and report back.
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
piffdaddy420 said:
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
Click to expand...
Click to collapse
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
ok so im in fastboot mode now. i checked out that thread that you sent. but i have another problem, how am i supposed to get cm and gapps onto the kindle? is there a command i can use to put the files on the internal sd card? and i cant do the adb commands to push the stack, and do the other commands adb since i couldnt get it loaded to begin with, i am not able to enable developer mode. it would be nice if i could do those commands in fastboot mode. there has to be a way to do this....
maybe if someone can send me the stock partitions that they backed up stock boot partititons when they did it. maybe if i flashed them onto my kindle it will allow me to get it to atleast boot up so i can get into adb.
right now this is completely bricked.
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
piffdaddy420 said:
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
Click to expand...
Click to collapse
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
piffdaddy420 said:
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
Click to expand...
Click to collapse
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
yes it does
piffdaddy420 said:
yes it does
Click to expand...
Click to collapse
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
monster1612 said:
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
piffdaddy420 said:
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
Click to expand...
Click to collapse
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
piffdaddy420 said:
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
Click to expand...
Click to collapse
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
monster1612 said:
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
Click to expand...
Click to collapse
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
piffdaddy420 said:
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
Click to expand...
Click to collapse
anyone have any suggestions or can help me with my situation?? i am wondering if maybe someone could just send me the original backed up bootloader, boot, and recovery. i tried the original ones that were posted with that srt file. but it included everything but the bootloader. which is what i need. i know that in original thread they recommended to back up your original files (i was unable to do so because my kindle woulnt boot so i couldnt use adb to back up these files).
so if someone on here can send me the original files so i can try to get my kindle booted back up. that so far is my only theory because i tried everything else. i know people with advance knowledge would be able to help me in a heartbeat. any devs out there wanna help me out? i would greatly appreciate it!
anyone?