Hey guys. I successfully rooted and installed twrp last night. This morning, I tried to install a custom rom but after installing and then rebooting I received an error message on the screen stating "Provisioning Fail". I tried a couple of other roms and have even tried the original stock Amazon rom but none of them will work. I followed a thread that I saw here and attempted a system recovery using fastboot and original img files,
This resulted in the loss of twrp on my kindle and now every time I boot, I get the normal kindle fire logo and then straight the the "Provisional Fail" screen. Please help. Cheers.
Any ideas???
tmosxda said:
Any ideas???
Click to expand...
Click to collapse
That usually comes up with a firmware update failure. Even people with stock units got that message before but it's been a while. You need to restore it via system restore tool again and use option 3.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
LinearEquation said:
That usually comes up with a firmware update failure. Even people with stock units got that message before but it's been a while. You need to restore it via system restore tool again and use option 3.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
Click to expand...
Click to collapse
I have tried to restore it with a couple of tools that I found on the forum but I get an error message saying device not found. When I connect the Kindle, it doesn't even show up in the device manager on my laptop.
tmosxda said:
I have tried to restore it with a couple of tools that I found on the forum but I get an error message saying device not found. When I connect the Kindle, it doesn't even show up in the device manager on my laptop.
Click to expand...
Click to collapse
You need a fastboot cable to restore it.
stunts513 said:
You need a fastboot cable to restore it.
Click to expand...
Click to collapse
I was hoping that wouldn't be the case! Is it possible to make a cable myself without needing a soldering iron?
Eh yea but Its not fun and you still will need a cable that has a contact point for the pin that's normally soldered. Not all USB cables have them(and I believe the cable that came with the kindle didn't have the contact point either) You could use a paperclip and try to hold it in place but I don't recommend this, you might accidentally slip the paperclip and short something. The black hat adapters are nice. I recommend them, they go between a normal cable and the kindle.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Eh yea but Its not fun and you still will need a cable that has a contact point for the pin that's normally soldered. Not all USB cables have them(and I believe the cable that came with the kindle didn't have the contact point either) You could use a paperclip and try to hold it in place but I don't recommend this, you might accidentally slip the paperclip and short something. The black hat adapters are nice. I recommend them, they go between a normal cable and the kindle.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I am going to order one of those adapters and hopefully it will do the trick. Thanks for your help.
Simlar situtation
Were you able to get past this?
I had successfully loaded the 2nd bootloader and put CM 10 on my Kindle. When I tried to go to CM11, something got borked. All I could get was a boot loop with the normal kindle boot screen - I no longer saw the blue graphic.
I get provisioning fail only when I use the recovery tool - any version. Honestly I have tried so many things I don't know how to get back to stock.
IrishMLK said:
Were you able to get past this?
I had successfully loaded the 2nd bootloader and put CM 10 on my Kindle. When I tried to go to CM11, something got borked. All I could get was a boot loop with the normal kindle boot screen - I no longer saw the blue graphic.
I get provisioning fail only when I use the recovery tool - any version. Honestly I have tried so many things I don't know how to get back to stock.
Click to expand...
Click to collapse
Do you have a fastboot cord? Use the most recent SRT and choose option 3. http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Do you have a fastboot cord? Use the most recent SRT and choose option 3. http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
I do have the fastboot adapter and option 3 still brings up the provisioning fail error. I have tried all permutations of the SRT and KFFA. I get nothing but provisioning fail unless I go back to the 2nd bootloader boot/recovery/system files. Then I get the orange kindle fire boot loop.
Thanks, MLK
I had this problem, I had gotten it due to trying to put different kernel on stock system. My way of getting out of this loop was using KFFA and doing the option that installs all partitions off a working kindle. It installs a total of 7 partitions,if I'm correct, and viola your fixed! That was the thing though.....I used another extra kindle I had in hand, I extracted the partition files from it and injected them to faulty kindle.
{
"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"
}
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
IrishMLK said:
Were you able to get past this?
I had successfully loaded the 2nd bootloader and put CM 10 on my Kindle. When I tried to go to CM11, something got borked. All I could get was a boot loop with the normal kindle boot screen - I no longer saw the blue graphic.
I get provisioning fail only when I use the recovery tool - any version. Honestly I have tried so many things I don't know how to get back to stock.
Click to expand...
Click to collapse
Sorry for the late reply.
I contacted amazon and they sent me a replacement kindle. I sent them back the broken kindle.
south956 said:
I had this problem, I had gotten it due to trying to put different kernel on stock system. My way of getting out of this loop was using KFFA and doing the option that installs all partitions off a working kindle. It installs a total of 7 partitions,if I'm correct, and viola your fixed! That was the thing though.....I used another extra kindle I had in hand, I extracted the partition files from it and injected them to faulty kindle.
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Click to expand...
Click to collapse
Hi! I'm having the same problem with "Provisioning Fail" I bought a fastboot cable and used KFHD System restore tool. My Kindle Fire HD (2012) is unrooted and kept freezing until one day i opened it again and saw the Provisioning Fail on the screen. So chose option 3, going back to stock but when I opened the device, the Kindle Fire logo back but after a few seconds went back to Provisioning fail.
Can you tell me you used the KFFA? And what partitions did you mention about? Sorry I'm a total noob about all these stuff. Hope you can help me.
Related
My problem:
flashed the zips below to a droid bionic. Everything went well, rebooted and it didn't unlock the gsm bands like I hoped. So I tried to restore the Bionic to factory with rsd light and 902 but I get flashed failed. So now every time the phone boots it goes directly into fastboot (flash failure screen) And now my phone shows up as ics xt912...?I looked all over the web and nobody has the same problem as me. Any way to uninstall this xt912 patch?
I tried a factory reset but now google play, bootstrap and safestrap all forceclose
I think its just a radio, but I'm not sure and wont risk hard bricking the phone..Any help on this issue would be greatly appreciated
{
"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 Flashed this : GSM PATCH > http://bit.ly/JW7Hjd
& FLashed this : "MAGIC code" lol > http://forum.xda-developers.com/atta...4&d=1336485537
original thread: http://forum.xda-developers.com/showthread.php?t=1619563&page=11
Have you turned off any Virus/Spyware scanners on the computer you're running RSD Lite from?
That happened to me before.
I'm not going to ask about how this happened.
I don't have any virus protection :/
Get a fresh download of .902
Reboot your PC.
turn off your phone, pull the battery for a few seconds.
Power up the phone into AP fastboot
connect with RSDLite
try to reflash.
I've tried that method numerous times with no success. I've tried the pathsaver method but when the program runs, it's interrupted because the phone boots up into flash failure screen.
I don't know where else to go from here. I'm no expert by any means.
Surely there is an android vet here that can help more than I.
Sent from my DROID BIONIC using XDA
What step did rsdlite fail at?
It says RAZR on it. How did you manage to even be looking in a RAZR area when you have a Bionic?
In any case, making sure that you re-download the .902 FXZ, updating your drivers, and using the newest RSDLite will maximize your chance at success.
RSDLite 5.7
https://rapidshare.com/files/386582613/RSDLite5.7.rar
5.9.902 Full FXZ
https://rapidshare.com/files/3690790507/VRZ_XT875_5.9.902.XT875.Verizon.en.US_CFC_01.xml.zip
Motorola USB Drivers
http://developer.motorola.com/tools/usb_drivers/
STEP 1
Power off your phone. Pull the battery if you have to. Take this time to install RSD Lite & Motorola drivers on your PC. Reboot your PC.
STEP 2
On your Bionic, down VolUp+VolDown and then press Power. You should get a boot menu. Choose AP Fastboot.
STEP 3
On your PC, start RSDLite as Administrator. (Right Click - Run As Administrator)
STEP 4
Plug in your Bionic. RSDLite should detect it.
STEP 5
Point RSDLite at the FXZ file. Flash and wait. This can take upwards of 10-15 minutes.
STEP 6
Whatever errors you get, post them. If all goes well, you should have a properly functioning Bionic again that's on a fresh .902 build.
eye__dea said:
What step did rsdlite fail at?
Click to expand...
Click to collapse
it fails on the first step. 1 second after the flash process start i get fail
projektorboy said:
It says RAZR on it. How did you manage to even be looking in a RAZR area when you have a Bionic?
In any case, making sure that you re-download the .902 FXZ, updating your drivers, and using the newest RSDLite will maximize your chance at success.
RSDLite 5.7
https://rapidshare.com/files/386582613/RSDLite5.7.rar
5.9.902 Full FXZ
https://rapidshare.com/files/3690790507/VRZ_XT875_5.9.902.XT875.Verizon.en.US_CFC_01.xml.zip
Motorola USB Drivers
http://developer.motorola.com/tools/usb_drivers/
STEP 1
Power off your phone. Pull the battery if you have to. Take this time to install RSD Lite & Motorola drivers on your PC. Reboot your PC.
STEP 2
On your Bionic, down VolUp+VolDown and then press Power. You should get a boot menu. Choose AP Fastboot.
STEP 3
On your PC, start RSDLite as Administrator. (Right Click - Run As Administrator)
STEP 4
Plug in your Bionic. RSDLite should detect it.
STEP 5
Point RSDLite at the FXZ file. Flash and wait. This can take upwards of 10-15 minutes.
STEP 6
Whatever errors you get, post them. If all goes well, you should have a properly functioning Bionic again that's on a fresh .902 build.
Click to expand...
Click to collapse
ok I'll give this another try with all fresh files.
I think I need to reflash the .902 radios again in recovery but will do this first
This is the error I get. I really really need to get this phone back to stock. I can press volume up and down and boot the phone up normally and get in to stock recovery but it wont let me flash a stock rom..
Every time I try and power the phone on this is the screen I get
Ok it's failing due to a USB error according to that pic.
First and foremost:
Goto add/remove programs(assuming you have winxp) and remove anything motorola.
Reinstall from scratch the USB MOTO drivers
Then try it.
If it fails again....I recommend replacing the cable with a different one.
If that doesn't work try it on a different PC.
Let us know.
Try using moto-fastboot to just flash the system partition.
If it was the patch with the wrong build.prop file that caused the problem, then flashing just the system.img from the XML.zip should fix it.
You need to have ADB installed on your PC and the moto-fastboot exe in the same directory with the fastboot images..
Unzip the FXZ to a directory and open a command prompt from that directory and run the following command: moto-fastboot flash system system.img
It will send and write the system in several chunks then return to the prompt.
Now type moto-fastboot reboot and it should boot normally with the new system image.
If you want an expert, go to droidhive or rootwiki. Xda is obsolete for the Droid bionic. Xda has became overrun by noobs and chased all the experts off.
Sent from my DROID BIONIC using XDA
nobreak1970 said:
ok it's failing due to a usb error according to that pic.
First and foremost:
Goto add/remove programs(assuming you have winxp) and remove anything motorola.
Reinstall from scratch the usb moto drivers
then try it.
If it fails again....i recommend replacing the cable with a different one.
If that doesn't work try it on a different pc.
Let us know.
Click to expand...
Click to collapse
oooooommmmmmmmggggggggg. After like 5 days of sleepless nights, on every forum trying every possible solution and giving up like 10 times. It was the freaking cable!!!! I had an extension on it. I removed it and plugged the cable directly into the computer and boooom. Rsd worked. Thanks for all your help and everyone who suggested things.
Helpercell said:
It was the freaking cable!!!!
Click to expand...
Click to collapse
Oddly enough, you're not the first person to say something like this with regards to RSDLite flashing. It seems like Moto phones & RSD Lite are extremely intolerant when it comes to irregularities in USB cables. Glad to hear that you've got a properly flashed phone again.
Helpercell said:
oooooommmmmmmmggggggggg. After like 5 days of sleepless nights, on every forum trying every possible solution and giving up like 10 times. It was the freaking cable!!!! I had an extension on it. I removed it and plugged the cable directly into the computer and boooom. Rsd worked. Thanks for all your help and everyone who suggested things.
Click to expand...
Click to collapse
Anytime.
Sent from my DROID BIONIC using XDA
Did you get ALL gsm bands unlocked on your Bionic or just the AT&T 3g band?
Hello,
I was trying to root my device, and I thought it was going well. once I rebooted it, the "Kindle fire system recovery" showed up. with two options. to reboot or to reset to factory defaults. booth options cause the device to reboot ans show the same message again.
I desperately need your help.
Thank you
Thank you for the reply,
I hope I could get it to adb but I can only boot it and when its booting the message shows up. I don't know if it has fastboot or if I could access it.
any other suggestions?
Thanks for the comprehensive response,
I tried what you suggested and the only output I get is ERROR: could not get pipe properties
I guess I need to look into factory cables hopefully it will get me to run fastboot mode.
If you have any other suggestions please share them
If your (stock) device only boots into recovery, you cannot change bootmodes without a factory cable, unless it's rooted. If your device IS rooted, changing bootmodes will be slightly different because you have to do so using the shell.
Code:
adb shell su -c idme bootmode 4000
adb reboot
If changing the bootmode doesn't work to bring your device back, you're probably looking at much bigger problems.
Thank you for the reply
the commands you listed are to be entered using a factory cable? am I correct?
because the device is rooted but I could not connect to it via adb nor fastboot.
samio2 said:
Thank you for the reply
the commands you listed are to be entered using a factory cable? am I correct?
because the device is rooted but I could not connect to it via adb nor fastboot.
Click to expand...
Click to collapse
No. If the device won't connect via adb, it's likely a problem with your computer and/or drivers.
One thing I have to ask is...are you using the Kindle Fire HD or the original Kindle Fire? With the Kindle Fire HD, you should not be trying to use fastboot unless you absolutely know what you're doing. Any alteration to the bootloader or recovery partitions WILL lock your device down, and it's highly unlikely you'll get it running again.
I am using the fire HD 7" ..
and I want to make sure because the only screen I am available to access right now is the "Kindle fire system recovery" menu. and during it being displayed and I'm not sure if the system fully booted to access it with adb
{
"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"
}
and I think my problem is caused by messed up permissions of the /system/app folder
Josepho1997 said:
I'm not sure if fastboot will work. You could try running fastboot in cmd. If its the same as the original kindle fire, you should first completely shut it down. Then, with fastboot type
Code:
fastboot getvar store
Then, turn on your kindle fire. If it says something in cmd, then it worked and your in fastboot. As of right now, fastboot wont help anything. But, when the kf hd gets a custom bootloader and a custom recovery, you could enter something like
Code:
fastboot 0x1949 flash bootloader nameofbootloader.img(or some file extension)
fastboot 0x1949 flash recovery nameofrecovery.img
Again, 0x1949 was for the original kindle fire. I don't know if it will work for the kf hd.
After you would flash the recovery and bootloader, you could flash a ROM or you could get somebody to make a backup of a kindle fire hd that just had a factory reset, and then you could restore it in recovery.
And if you want to get out of fastboot mode, you could
Code:
fastboot 0x1949 bootmode 4000
fastboot 0x1949 reboot
Android>iOS... Android FTW!
Click to expand...
Click to collapse
it's wrong.
KF HD no 4000 bootmode
KF 1 can boot on mode 4000
but KF HD can't
please confirm
bournezhang said:
it's wrong.
KF HD no 4000 bootmode
KF 1 can boot on mode 4000
but KF HD can't
please confirm
Click to expand...
Click to collapse
You're going to have to provide more detail than that. Where are you getting this information?
OP, if the KFHD is anything like the KFOG (I'm betting it is), you should be able to send adb commands while in recovery (stock or otherwise). What errors are you getting, if any, when trying to send adb commands?
At the prompt shown in the screenshot, there is no connectivity between the device and pc. I checked the device manager and also tried it on the mac "adb devices" shows nothing ... that why I thought fastboot is the only way out. if there is anything you want me to try I'll be glad to.
??
Got an answer about the problem now?
No. still waiting for some senior member revelation, or buying the factory cable
I ordered a factory cable ... I will need assistance with flashing the stock ROM back with fastboot
I have same bootloop issue.
I have entered Kindle Fire HD 7" fastboot mode
but it entered shorting some cables, not completed makes factory cable.
my KFHD is fastboot mode but my computer has not detect any devices.
It's normal micro 5pin data cable now.
anyone have idea to convert this to facory cable?
front of cable has REV.3 and RED, BLK words
back of cable has GRN, WHT words
i have no electric tester
you are one step ahead of me .. so I can't help you ... hope a more experienced member could lend a hand with this.
parintan said:
I have same bootloop issue.
I have entered Kindle Fire HD 7" fastboot mode
but it entered shorting some cables, not completed makes factory cable.
my KFHD is fastboot mode but my computer has not detect any devices.
It's normal micro 5pin data cable now.
anyone have idea to convert this to facory cable?
View attachment 1370293
View attachment 1370294
front of cable has REV.3 and RED, BLK words
View attachment 1370295
back of cable has GRN, WHT words
i have no electric tester
Click to expand...
Click to collapse
Did you read this: http://forum.xda-developers.com/showthread.php?t=1392693 ?
Found these instructions on ebay, don't know if they are useful.
Boot up your computer to Windows
Turn off the Kindle Fire
Plug cable into Kindle Fire
Plug into USB Port of the computer
The Kindle Fire unit if not on already will have turned on again.
Press and Hold the Power button for 20 seconds (past the do you want to turn off prompt). The device will go dark.
Press the power button once and let go.
The device will turn on and it will stop at the Kindle Fire Triangle ( This is in the Fastboot Mode)
If you check your devices, it should say under Android Phone
Android ADB Interface
OMG Stop.
Stop, stop, stop ,stop, stop, before you lock your device down for good.
You need to do some research before trying random things, not knowing what they are for.
The factory cable PUTS THE DEVICE IN FASTBOOT. It does not take it out of fastboot. Research fastboot commands to determine the best course of action for you. Just be sure you know what you are doing and the potential consequences of doing so.
@parintan
any luck with your kindle?
Any updates on the KFHD front?
I've been trying to install TWRP from "Kindle Fire Utility 0.9.6" but unable to proceed.
ADB Status is Online, but Boot Status is Offline. I don't know why. I have all the drivers installed. And also Kindle Fire is rooted with latest version 7.3.1, if the information helps. When pressed "3" in the menu it brings up the status:
HTML:
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
2611 KB/s (510876 bytes in 0.191s)
fail opening shift: No such file or directory
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
Any information on how I can fix this? Also if needed further information please post.
Is it going into fast boot?
Sent from CM10.1 using Tapatalk HD
Wait a second, KFUtility? isn't that for the 1st gen Kindle Fire's?
Anyways, setting idme bootmode to 4002 wont work in KFHD 7"
And if it really is a 2nd gen KF. since you said 7.3.1.
Go to 7" Kindle fire HD Android development and find
Installing second bootloader, you will need root access and a fastboot cable
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
You have a Kindle Fire HD 7" (3rd generation Kindle Fire), why are you trying to root it with a software designed for the very first generation Kindle Fire?
"ADB Status is Online, but Boot Status is Offline" Miss typo. "ADB Status is Online, but Boot Status is Unknown" I don't know what generation, but i'm guessing it's a 3rd generation. Also, the only cable that i have a the cable that was included with the Kindle Fire, don't know if that is a fastboot cable. And my Kindle Fire HD is rooted. What Utility should i be using for the 7" Kindle Fire HD then?
If your tablet has the "HD" in the name, then you're in the right place. Go to the 7" Theme and Apps forum, and click on the thread with the "flash boot image and recovery" in the name. That's the app FireFlash, go ahead and download the .apk file. Move that file to the sdcard on the tablet, and install it using any file manager. Open the app, get the files from Hashcode's 2nd-Bootloader thread in the 7" Development forum, move those to the sdcard, plug everything in (follow the picture in the FireFlash thread), and flash.
That's how you install TWRP. Then you can backup and restore, and flash custom ROMs.
seokhun said:
If your tablet has the "HD" in the name, then you're in the right place. Go to the 7" Theme and Apps forum, and click on the thread with the "flash boot image and recovery" in the name. That's the app FireFlash, go ahead and download the .apk file. Move that file to the sdcard on the tablet, and install it using any file manager. Open the app, get the files from Hashcode's 2nd-Bootloader thread in the 7" Development forum, move those to the sdcard, plug everything in (follow the picture in the FireFlash thread), and flash.
That's how you install TWRP. Then you can backup and restore, and flash custom ROMs.
Click to expand...
Click to collapse
Ahh thanks! Gotcha, so the fastboot cable isn't needed at all then?
Yes, but it is recommended to have one just in case
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
dugoy13 said:
Yes, but it is recommended to have one just in case
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
I get this Warning sign when launched app.
{
"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"
}
Might have to right click-->Copy image URL
caithao said:
I get this Warning sign when launched app.
Might have to right click-->Copy image URL
Click to expand...
Click to collapse
That just means you aren't on the 7.2.3 bootloader, go ahead and check that box to install it. Otherwise you'll end up with a red screen after you reboot from the flash.
seokhun said:
That just means you aren't on the 7.2.3 bootloader, go ahead and check that box to install it. Otherwise you'll end up with a red screen after you reboot from the flash.
Click to expand...
Click to collapse
So do i follow the steps that were given in this thread or the steps on the 2nd Bootloader. This is the ROM i wanted to install on. Does this, what I'm doing is correct? For BOOT PARTITION and RECOVERY PARTITION.
caithao said:
So do i follow the steps that were given in this thread or the steps on the 2nd Bootloader. This is the ROM i wanted to install on. Does this, what I'm doing is correct? For BOOT PARTITION and RECOVERY PARTITION.
Click to expand...
Click to collapse
Do you see the space to select the .img files? That's where Hashcode's files come in. Grab his freedom-boot.img and plug that into the "boot image" section. Then grab his TWRP 2.4.4.0 build and plug it into the recovery section. Then hit flash and wait. Once you restart into TWRP, you're good. Just hit reboot, and you'll be able to start flashing ROMs. Put any custom ROM's .zip file on the sdcard, then turn off the device. Turn it on, and immediately hold Volume-Up before the yellow logo turns to blue, and let go.
seokhun said:
Do you see the space to select the .img files? That's where Hashcode's files come in. Grab his freedom-boot.img and plug that into the "boot image" section. Then grab his TWRP 2.4.4.0 build and plug it into the recovery section. Then hit flash and wait. Once you restart into TWRP, you're good. Just hit reboot, and you'll be able to start flashing ROMs. Put any custom ROM's .zip file on the sdcard, then turn off the device. Turn it on, and immediately hold Volume-Up before the yellow logo turns to blue, and let go.
Click to expand...
Click to collapse
I followed your steps:
But then when i hit flash, errors occurred.
caithao said:
I followed your steps:
But then when i hit flash, errors occurred.
Click to expand...
Click to collapse
What errors? That window that pops up just tells you the progress. After you hit OK, you should restart into TWRP.
seokhun said:
What errors? That window that pops up just tells you the progress. After you hit OK, you should restart into TWRP.
Click to expand...
Click to collapse
Oh well, nothing happened after i pressed "Ok". O.0 Do i reboot, then when logo pops up and hold down "Up button"?
caithao said:
Oh well, nothing happened after i pressed "Ok". O.0 Do i reboot, then when logo pops up and hold down "Up button"?
Click to expand...
Click to collapse
Go ahead and turn it off, then turn it on and see if you have a blue Kindle logo. If you do, then you have the 2nd-bootloader installed. Turn it off again, and turn it on. Hold Volume-Up (the leftmost button from the power button) before it turns blue, and see if you boot into TWRP (takes a minute). If it does, you're golden, if it doesn't, try the flashing again.
seokhun said:
Go ahead and turn it off, then turn it on and see if you have a blue Kindle logo. If you do, then you have the 2nd-bootloader installed. Turn it off again, and turn it on. Hold Volume-Up (the leftmost button from the power button) before it turns blue, and see if you boot into TWRP (takes a minute). If it does, you're golden, if it doesn't, try the flashing again.
Click to expand...
Click to collapse
Okay thank, all worked out! But thing is, there isn't much ROMS out to install and isn't favor.
caithao said:
Okay thank, all worked out! But thing is, there isn't much ROMS out to install and isn't favor.
Click to expand...
Click to collapse
There's three out right now, Kinology (Amazon 7.3.1 modified with Android ICS) by psychophobia, CyanogenMod 10.1 (Android AOSP, Jelly Bean 4.2.2) by Hashcode, and ParanoidAndroid (built upon CM10.1 by Hashcode, Android AOKP, Jelly Bean 4.2.2).
seokhun said:
There's three out right now, Kinology (Amazon 7.3.1 modified with Android ICS) by psychophobia, CyanogenMod 10.1 (Android AOSP, Jelly Bean 4.2.2) by Hashcode, and ParanoidAndroid (built upon CM10.1 by Hashcode, Android AOKP, Jelly Bean 4.2.2).
Click to expand...
Click to collapse
Okay, i'm trying to reboot back into my original image that i backed up followed by this thread http://forum.xda-developers.com/showthread.php?t=2128848 is there any way i can restore it back without a fastboot cable? i booted into TWRP and do not see the file under "INSTALL" or "RESTORE" ? Help
caithao said:
Okay, i'm trying to reboot back into my original image that i backed up followed by this thread http://forum.xda-developers.com/showthread.php?t=2128848 is there any way i can restore it back without a fastboot cable? i booted into TWRP and do not see the file under "INSTALL" or "RESTORE" ? Help
Click to expand...
Click to collapse
That depends on where you made the destination. You won't find them in TWRP because TWRP only recognizes its own backups. The backups you made are not Nandroid backups. Check your ADB folder in the Android SDK folder. What are you trying to restore from? Everything went successfully, didn't it?
I screwed up installing CM10.1 forgot to put rom onto device and ended up in boot loop.
I got a fastboot cable but the kindle shows as Tate PVT and the update driver box is greyed out. Cant get fastboot or adb to recognise the device.
Is there anyway to recover from this
Thanks
dean
You have TWRP installed, right? Does your Kindle Fire logo turn blue while booting?
soupmagnet said:
You have TWRP installed, right? Does your Kindle Fire logo turn blue while booting?
Click to expand...
Click to collapse
i might be in the same boat...my kindle fire logo turns blue and gives me a msg at the bottom to press power button for boot menu
when i do i get normal boot,recover,and reset boot mode...when i click on one it just says booting and power button stays organish red for ever
Maybe you don't have your drivers properly installed
sent from my rooted kindle fire hd 7
Baconrind said:
I screwed up installing CM10.1 forgot to put rom onto device and ended up in boot loop.
I got a fastboot cable but the kindle shows as Tate PVT and the update driver box is greyed out. Cant get fastboot or adb to recognise the device.
Is there anyway to recover from this
Thanks
dean
Click to expand...
Click to collapse
If you have twrp installed and the blue kindle boot screen just hit volume down and use the side load feature. But if your fastboot is giving u a problem where u can't hit update driver I would assume it would be because windows is already searching for one still? If so tell windows to skip obtaining from windows update and it finish sooner so u can try to update it manually.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Baconrind said:
I screwed up installing CM10.1 forgot to put rom onto device and ended up in boot loop.
I got a fastboot cable but the kindle shows as Tate PVT and the update driver box is greyed out. Cant get fastboot or adb to recognise the device.
Is there anyway to recover from this
Thanks
dean
Click to expand...
Click to collapse
Hi Baconrind. Screwing one’s device is a good opportunity to learn new things. At least this is what happened to me and I’m glad I did. A couple of months ago I bought a new KFHD7. I spend "wonderful :laugh:" weeks as the happy owner of a KFHD7 until I started to discover the shortcomings of same, so I started reading xda-developers’ stuff to try to customise the device. First I rooted it to be able to install Google Play Store. The idea was to stay as close to stock as possible. Unfortunately I lost root with the first Amazon OTA update, then I decided to install a second bootloader, TWRP, etc. To do that I followed Hashcode’s method Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 7 but at some point I bricked :crying: my device. I was stuck at the Kindle Fire logo. I spent hours browsing through xda-developers and discovered that the first thing to do was to get a fastboot cable. I did not have the patience to wait for it to come from China or wherever they make them, so I found a couple of posts on the xda forum here and here. I made my own even my soldering capabilities are quite limited. I shut down the KFHD7 and plugged the “fastboot” cable to the PC and then to the Kindle, a couple of seconds later I could see the fastboot logo. Once I saw the fastboot logo I unplugged it and used the regular data transfer cable instead. Before I started the unbricking process proper I downloaded and installed this tool: KFHD_SRT_v1.3.5.-7.3. I followed the onscreen indications and could reset my KFHD7 back to its original state. Good luck.
I purchased a used 2012 Kindle Fire HD 7" from Cowboom, and I decided to look into rooting/installing CFW on the device. I looked at a few automated utilities that would basically do the installation for me, and found that none of them were working.
This was all on Amazon's latest update, I think 7.4.8? All the guides I read were for earlier versions etc, but I went and tried them all anyway. After using KFU(I think), my device was red screen bricked after attempting to install TWRP. Now, I have a device that only shows a red screen when trying to turn on.
I've read almost every guide on how to unbrick the device, using fastboot(and yes, I did purchase a factory cable that can successfully get me into fastboot), but whenever I try to use any fastboot commands, or utilities, I get a <waiting for device> error every time. It seems to be the main issue I'm running into.
I installed various Kindle drivers to see if it was the problem(I'm on Win8 64-bit), and have run into the same error no matter what I do. I've also tried restoring the device on my laptop(same OS). No luck
I've tried using KF First Aide, Kindle Fire Utility, KF SRT, basically everything, but I always run into <waiting for device> no matter what I try doing. Using a fastboot cable extension to get into fastboot, then unplugging, replugging, changing cables, everything
Prior to being bricked, the drivers were fine and the device showed up as Kindle in the device manager, but now since it has been bricked, it shows up as Tate-PVT-08.
If ANYONE could please, please help me with this, it would be greatly appreciated... I'm honestly about to give up after trying to fix it for hours on end, and its giving me a headache everytime I try again...I really don't know what to do at this point. I feel like my device is permanently bricked :crying:
breannak said:
I purchased a used 2012 Kindle Fire HD 7" from Cowboom, and I decided to look into rooting/installing CFW on the device. I looked at a few automated utilities that would basically do the installation for me, and found that none of them were working.
This was all on Amazon's latest update, I think 7.4.8? All the guides I read were for earlier versions etc, but I went and tried them all anyway. After using KFU(I think), my device was red screen bricked after attempting to install TWRP. Now, I have a device that only shows a red screen when trying to turn on.
I've read almost every guide on how to unbrick the device, using fastboot(and yes, I did purchase a factory cable that can successfully get me into fastboot), but whenever I try to use any fastboot commands, or utilities, I get a <waiting for device> error every time. It seems to be the main issue I'm running into.
I installed various Kindle drivers to see if it was the problem(I'm on Win8 64-bit), and have run into the same error no matter what I do. I've also tried restoring the device on my laptop(same OS). No luck
I've tried using KF First Aide, Kindle Fire Utility, KF SRT, basically everything, but I always run into <waiting for device> no matter what I try doing. Using a fastboot cable extension to get into fastboot, then unplugging, replugging, changing cables, everything
Prior to being bricked, the drivers were fine and the device showed up as Kindle in the device manager, but now since it has been bricked, it shows up as Tate-PVT-08.
If ANYONE could please, please help me with this, it would be greatly appreciated... I'm honestly about to give up after trying to fix it for hours on end, and its giving me a headache everytime I try again...I really don't know what to do at this point. I feel like my device is permanently bricked :crying:
Click to expand...
Click to collapse
KFU is the wrong bootloader and not made for KFHD. Use Kindle Fire SRT v30 and choose the third option. The waiting for device is because you don't have the paths set right in your environment. Have you downloaded the SDK package? If so you can Copy/paste the path you set for the platform tools/tools and I can see if everything looks OK.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
I have downloaded the android SDK, and java runtime environment.
Added the environment variable too, supposed to look like this right?
{
"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"
}
Nothing works, I've followed the instructions for KF SRT very carefully
Wow, I found out what the problem was thanks to f4hkramer. I didn't install the drivers manually so instead of it showing up as Tate-PVT-008, it shows up as Kindle Fire. Successfully restored device..... so happy :laugh:
f4hkramer said:
I think I've figured it out. The key was when entering the update driver window and click browse my computer, instead of looking for a file location clicking pick from list of drivers on my computer. It installed the kindle driver and is now listed as kindle fire - android adb device.
Click to expand...
Click to collapse