Related
Hello,
I just received a Kindle Fire and decided to root and install Cyanogenmod. I found a tutorial which I thought looked pretty straightforward on Lilputing. I downloaded the Kindle Fire Utility and followed both the utility and the article told me to do. After installing TWRP 2.0, disaster. I rebooted the device and the Kindle read, "press power button for recovery," and showed a yellow triangle with a fire icon in the middle. I pressed the power button, and nothing happened. At this point, I rebooted. The device would not get passed this screen, and my PC would not recognize the Kindle. I presume I bricked my device, however (as I do not have any experience in this field) I honestly have no idea what I did, nor do I know where to go next. Any suggestions? Please help!
I'm stuck too. And i cannot install the driver because it is an unknown device.
kw1999 said:
Hello,
I just received a Kindle Fire and decided to root and install Cyanogenmod. I found a tutorial which I thought looked pretty straightforward on Lilputing. I downloaded the Kindle Fire Utility and followed both the utility and the article told me to do. After installing TWRP 2.0, disaster. I rebooted the device and the Kindle read, "press power button for recovery," and showed a yellow triangle with a fire icon in the middle. I pressed the power button, and nothing happened. At this point, I rebooted. The device would not get passed this screen, and my PC would not recognize the Kindle. I presume I bricked my device, however (as I do not have any experience in this field) I honestly have no idea what I did, nor do I know where to go next. Any suggestions? Please help!
Click to expand...
Click to collapse
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Thank you!
I did, however, find a solution using the Kindle Fire Utility.
With my device connected to my computer, I selected Change BootMode. Next, I chose Normal. That brought me out of the frozen boot screen, so I decided to wing it and flashed Cyanogenmod, and that worked. Thank you anyway for your time.
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
For me 7 resulted in a device not found, though I fixed this by rebooting the kindle (I guess fastboot mode ends at some point?)
So after I fix this - how do I get into TWRP? Trying to install it from the utility does not work!!
andTab said:
For me 7 resulted in a device not found, though I fixed this by rebooting the kindle (I guess fastboot mode ends at some point?)
So after I fix this - how do I get into TWRP? Trying to install it from the utility does not work!!
Click to expand...
Click to collapse
Unfortunately, I don't know. I've been trying to get in TWRP all night and have been unsuccessful. I knew how to get out of this issue because I've put myself here several times tonight, trying to get TWRP to start up...so far, no luck...
I had same problem. Kept booting to "press power button for recovery" but never went to recovery. I had to download and install FireFireFire manually after i installed twrp. Now works great. Just power off then hold power button in for few seconds (until it turns orange) when powering back on, release, then there's twrp.
Wired0980 said:
I had same problem. Kept booting to "press power button for recovery" but never went to recovery. I had to download and install FireFireFire manually after i installed twrp. Now works great. Just power off then hold power button in for few seconds (until it turns orange) when powering back on, release, then there's twrp.
Click to expand...
Click to collapse
THANK YOU! This fixed the problem, I just had to find the thread that was ONLY FireFireFire, and not combined with TWRP, since that hadn't worked for me. I included instruction below for anyone having similar issues:
I downloaded the u-boot.win from here then ran
Code:
fastboot flash bootloader u-boot.bin
at which point it sait "Waiting for device". So I rebooted the Kindle like had the last several times that's appeared and it flashed it and then I rebooted again and I held down the power button, and it turned amber, like it had earlier, except THIS time it actually booted into TWRP!! Hooray! Hope this helps anyone else having this issue.
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
Thank you so much!!!!!! i thought my device was a gonner... and i just got it today
how can you remove TWRP from kindle fire if it's possible, whatit to boot likeif i just got itout of the box, which i did today when i recieveit.
Thanks.
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
I tried this and it won't work, what am I doing wrong ?
Why is there a step 4? Is it only there so I check if kindle shows up or do I have to update its driver so there is no yellow triangle anymore?
EDIT:
So I managed to get it running. What I did is I added the "0x18D1" as in step 3 but after that I opened my device manager and by clicking on kindle (that has yellow triangle next to it) I updated its driver. I chose the location of adb_usb.ini that I edited. After that I ran Kindle Fire Utility and chose option 1 (Boot mode) and in the following menu I tried all of the options. In the option 3 (Recovery) it did something and now every time I boot kindle it goes to the yellow triangle but by pressing power button once it starts normal boot.
Ok, but still I would like to get it completely back to normal if possible so if anyone can help, thanks
It is supposed to show the recovery triangle EVERY time you reboot.
Just don't touch anything and it will continue to boot on its own to the OS.
The only time you should do something different is if you want to boot into recovery, then you push the power button until it turns orange and let go, it will boot into the TWRP recovery.
You really shouldn't need reboot the machine often. I do it maybe once every couple days at most.
nuttmeg said:
how can you remove TWRP from kindle fire if it's possible, whatit to boot likeif i just got itout of the box, which i did today when i recieveit.
Thanks.
Click to expand...
Click to collapse
To remove TWRP and go back to the stock Amazon ROM, all you have to do is flash the stock Amazon firmware. Use Kindle Fire Utility v.7 to download the stock update.zip, copy the file to the SD card, boot into recovery, and install it.
---------- Post added at 05:30 PM ---------- Previous post was at 05:25 PM ----------
kw1999 said:
Hello,
I just received a Kindle Fire and decided to root and install Cyanogenmod. I found a tutorial which I thought looked pretty straightforward on Lilputing. I downloaded the Kindle Fire Utility and followed both the utility and the article told me to do. After installing TWRP 2.0, disaster. I rebooted the device and the Kindle read, "press power button for recovery," and showed a yellow triangle with a fire icon in the middle. I pressed the power button, and nothing happened. At this point, I rebooted. The device would not get passed this screen, and my PC would not recognize the Kindle. I presume I bricked my device, however (as I do not have any experience in this field) I honestly have no idea what I did, nor do I know where to go next. Any suggestions? Please help!
Click to expand...
Click to collapse
I had this same problem a few days ago. I fixed it by going into Device Manager, finding the device called "kindle" (it had a yellow triangle next to it) and manually installing the ADB drivers. You can't search for drivers automatically, you have to manually specify the "ADB Composite Interface" or something to that effect.
I have also had this issue, thought it was because I was using a 64 bit windows 7 system.
I had previously installed cyanogenmod 7 using destructions from this forum, and I have also done something similar with my Galaxy S2 (I mention this, because this may be why the drivers havent worked?)
Anyway, I added the line above, then rebooted my PC (twice), and then unplugged my kindle fire and rebooted. I then plugged it in to the PC and it came up as "kindle" in device manager, but had the exclamation mark warning. I clicked update driver and found the updated usb.ini file. Windows did its stuff and then it appears as Android bridge device.
The kindle wa still stuck at the yellow triangle, but selection the fastboot menu option 1, then boot normal and it worked a charm.
Persevere and dont give up!
Thanks to the great advice on this forum, everything becomes easy, once you have found the right posts!
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
The page wont load to download that version of KFU. Also everytime I try to download fastboot I get an error saying AdbWinApi.dll is missing from my computer. Where do I find that?
http://forum.xda-developers.com/showthread.php?t=1399889
and the missing file is in kfu
krelvinaz said:
It is supposed to show the recovery triangle EVERY time you reboot.
Click to expand...
Click to collapse
That can't be right, surely?
bikeracer4487 said:
Try this:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command "fastboot oem idme bootmode 4000"
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don't hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle. Hope this helps!
Click to expand...
Click to collapse
Kindle is not recognized? Please help?
Uninstall/reinstall device drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Wired0980 said:
I had same problem. Kept booting to "press power button for recovery" but never went to recovery. I had to download and install FireFireFire manually after i installed twrp. Now works great. Just power off then hold power button in for few seconds (until it turns orange) when powering back on, release, then there's twrp.
Click to expand...
Click to collapse
I am having this problem and have gone back to install FireFireFire manually but I still get stuck at "press power button for recovery". If I leave it alone it eventually boots as normal. If I press and hold the power button for a few seconds, it turns orange but never does anything. Any ideas?
I should mention that I'm running Ubuntu Linux - no access to Windows so KFU is not an option. My Fire is at version 6.3 and I've been roughly following the guide here: http://forum.xda-developers.com/showthread.php?t=1568340
I rooted my kindle fire, using an instructional video from YouTube.
The root was successful, and then I tried to install TWRP using the Kindle Fire Utility software, but the process was unsuccessful causing my Kindle to be stucked on a screen with a Yellow Triangle Icon.
After going through several tread, a came across an interesting one saying use fast boot to restore the device. The method included:
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into ‘drivers’ and open up adb_usb.ini in a text editor and add “0x18D1″ (without the quotes) on a line underneath “0×1949″
4) Open up Device Manager and find “kindle”. It should have a yellow triangle near it.
5) Download fastboot.exe from here
6) Open up command prompt and navigate to wherever you saved fastboot to.
7) Run the command “fastboot oem idme bootmode 4000″
8) Power off your device by holding down the power button for ~10 seconds and turn it back on, and this time don’t hit the power button to go into TWRP. It should move past the yellow triangle after a few seconds and boot into Kindle.
But the method failed at the step 7 with an error message saying “The program can’t start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.”
I REALLY REALLY WANT TO BE ABLE TO USE MY KINDLE AGAIN!
PLEASE HELP ME!
ok do you have the newest version of kfu?
Just download the latest find the tools folder shift+right click on the folder itself select open command window here plug your kindle in then type fastboot oem idme bootmode 4000 your kindle should boot normal.
I bought my kindle fire HD 8.9 months ago. Its operation system vesion is 8.4.3. I wanted to change it to CM10 for a long time. Last night was the night when I made great effort but unforturnately encountered a serious problem which turned my kindle to a brick.:crying:
Here is what I have done and where my HD 8.9 BRICKED.
1. Rooting
I carried on the root process exactly as what the post http://forum.xda-developers.com/showthread.php?t=2337634 says
Quote
1. ENABLE ADB IN SETTINGS UNDER SECURITY
Step 1. Download all files provided in the post and keep kindle unplugged at all times
Step 2. To be safe uninstall any other drivers for the kindle installed on the operating system (Win.) And Reboot.
Step 3. Install the adb drivers provided in the .zip
Step 4. Unzip the bin4ry tool on ur desktop and run the .bat file for windows as admin/.sh for Linux.
Step 5. Keep kindle unplugged still... The menu u will be promoted with will ask you what is ur device type. Select normal.
Step 6. Once you selected normal and the command prompt will say plug in your device. Do it.
Step 7. It will say a bunch of stuff, once it stops spitting out lines, if your kindle isnt already. Unlock it.
Step 8. Hopefully u get a window on ur kindle asking to restore and enter ur credentials. JUST PRESS RESTORE AT THE BOTTOM
Luckily, My HD 8.9 acted correctly in the above process. In the next step, I tried to install Firefirefire1.4 +TWRP2.2. Following is the steps I took :
1. Download Firefirefire1.4+TWRP2.2(with Fastboot)
2. Open cmd prompt, enter the directory where Firefirefire1.4+TWRP2.2 was extracted
3. Connect HD 8.9 to computer with USB wire, and disconnect the device as memory mode but I really did not know how to disconnect it as memory mode,my HD8.9 device alway show "Connected as Media Device", so I just passed it and continue with the following step
4. Input the following command lines
(1)adb push u-boot.bin /sdcard/
(2)adb push twrp.img /sdcard/
(3)adb shell
(4)su
(5)dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p5
(6)dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
(7)reboot
RIGHT AFTER I HIT ENTER KEY, OhO, My HD8.9 shut down but never turn on again. No matter how long I press and hold on the power button, it just does not response any more. So what can I do to recover it, PLEASE HELP ME!!:crying::crying::crying:
http://forum.xda-developers.com/showthread.php?t=2228532
Oh dear, am a noob, please forgive me!!
I have a Kindle Fire HD 8.9, rooted it OK, then followed "Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial" to install TWRP.
Everything seemed ok, then got stuck on blue/white logo, so got into TWRP hoping somehow I could move a rom on there to flash it. Now I'm in TWRP , the Kindle won't show up on My Computer, so how do I do this? I did try pressing "mount" but nothing happened.
I've searched forums but am just getting more confused!!
Maybe the drivers are wrong, but I don't know how to fix that.
Tried looking at "[HOW-TO] ADB Push a ROM to your phone"http://forum.xda-developers.com/showthread.php?t=1667929, it tells me to find where my ADB is on my PC's hard drive, but I can't find anything that says AndroidSDK on my c:drive.
Oh God!! Am I doomed???
Please can someone kind help me??
Thanks guys
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
http://forum.xda-developers.com/showthread.php?t=2277105
mfg
German JPL
Thank you German JPL,
I did try to follow this trobleshooting bit at the end, but I'm kinda stumped by the fact I don't know where this "ADB binary is (usually inside platform-tools folder in Android SDK directory)"
I'm on Windows 7 and there's no such thing on my c:drive. Under User, there is an ".android" folder, but I don't think that's it.
Hi pixie67,
sorry for my bad english, I'm a German speaking English writer.
in what way do you have adb drivers and fastboot drivers installed?
when did you proceed to the manual, you would still have a folder with android sdk?
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
Click to expand...
Click to collapse
I have windows 7 and when I enter in the search window windows sdk, I find the folder.
mfg
GermanJPL
Hello,
I installed KindleADB.exe for the drivers. That seemed successful. I managed to root it ok,
My Kindle, in TWRP shows up in device manager as Android Phone/Android ADB interface.
I can boot into fastboot from the options in TWRP.
I've updated the android SDK package and rebooted my computer.
I can't use ADB sideload, it just sticks on "starting ADB sideload feature...."
If I reboot to system, I just end up on the white/blue logo.
I don't know what to do next
I do not understand ... have you thought you were the instructions?
you've got installed 2nd Boot Loader & TRWP after manual with ADB and fastboot .... ? why are you not looking adb.exe, then you have your folder
or you install you Andrid sdk subsequently follow the instructions, then you've got everything you need.
German JPL
I don't really understand your answer German, I've followed the instructions, but I'm still stuck on the boot screen, or in TWRP with no way to flash a ROM as there is no ROM on the device and I can't transfer a rom onto the device because mounting doesn't work and Adb sideload doesn't work.
So I'm stuck.
Help!
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
GermanJPL said:
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
Click to expand...
Click to collapse
I can't find a SDK folder anywhere, I've searched, I've enabled hidden folders. I don't know if this is why the ADB sideload option doesn't work, but it doesn't, it just hangs there.
I can start the Kindle in fastboot, there is a message saying "installing device driver software", then another, confirming the ADB driver software has been successfully installed. In device manager I now see
Kindle Fire listed with android adb interface.
I don't know what "play the 3 img a backup folder." means. I'm sorry. While I'm in fastboot mode, I'm not sure what to do. Can you tell me?
And I don't know how to start from scratch as I can't copy anything anywhere. Although I can see the Kindle in device manager, I can't get to it in windows explorer.
The problem is, I didn't copy the ROM and GAPPS onto the Kindle before installing TWRP and now I can't.
Oh dear, I'm sorry to be so frustrating!! Thank you for trying to help though xx
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Click to expand...
Click to collapse
German JPL
Thank you for helping me.
I can't transfer the 2 files as I can't access the sdcard, but I did do this initially.
Also, do I use the command prompt just from the desktop and will it work while I'm in fastboot mode as I can only get into fastboot or recovery. I can't boot normally.
I will give it a go anyway, I really am very grateful for your help
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
HELP
pixie67 said:
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
Click to expand...
Click to collapse
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
OhhRey said:
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
Click to expand...
Click to collapse
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
HELP
stunts513 said:
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
Click to expand...
Click to collapse
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
OhhRey said:
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
Click to expand...
Click to collapse
Do a factory reset from twrp and see if it fixes the problem.
Hello. Is there anyone out there that could provide me with basic instructions on how to unroot my device and put back the stock recovery image?
I haven't done too much after I rooted the device, but I will list whats been done.
1. Performed root with Minimal ADB Fastboot 1.3.1 with SuperSU and TWRP
2. Installed Xposed with a failed attempt to remap the Shield Remote for the OK button long press to kodi context menu. (then uninstalled exposed)
3. Since I couldn't get the exposed key remap to work, I performed a factory rest from within the Android TV settings. (SuperSU is still installed, and every now and then I will see the TWRP splash screen on startup.
4. I attempted to restore the Stock Nvidia Shield TV image with ADB by doing the following:
a. Downloaded the Stock Nvidia Shield TV image.
b. Extracted and copied the folder to ADB fastboot program file directory.
c. Connected Shield with USB to Windows computer.
d. Opened ADB and typed "adb devices" to verify and device showed up.
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
g. typed, "flash-all.bat" in ADB and it says, "flash-all.bat" is not recognized as an internal or external command"
NOTE: I do have Developer mode, and USB Debugging enabled on the Shield.
The reason I want to unroot is because I have experienced some pretty annoying problems since root. Intermittently upon reboot, Netlix and the Nvidia Game apps do not show. They are just empty spaces. Also the recommendations do not show. I also frequently get "Unfortunately Google Play Services has stopped working" also "Unfortunately Tegra Services has stopped working" and apps crashing/freezing on a regular basis, which force quitting does not resolve. Have to restart Shield to get working again.
I have searched online, and looks like for the most part people who root this device end up not having these problems. Seems like everyone is pretty happy with the root and not experiencing these issues. There are a few I have talked to that have these or similar problems.
If someone could provide me with instructions on how to successfully Unroot my Shield, that would help me out a great deal. I just want it to operate like it was when I first got it. Thanks much for your time.
mikie00mike said:
Hello. Is there anyone out there that could provide me with basic instructions on how to unroot my device and put back the stock recovery image?
I haven't done too much after I rooted the device, but I will list whats been done.
1. Performed root with Minimal ADB Fastboot 1.3.1 with SuperSU and TWRP
2. Installed Xposed with a failed attempt to remap the Shield Remote for the OK button long press to kodi context menu. (then uninstalled exposed)
3. Since I couldn't get the exposed key remap to work, I performed a factory rest from within the Android TV settings. (SuperSU is still installed, and every now and then I will see the TWRP splash screen on startup.
4. I attempted to restore the Stock Nvidia Shield TV image with ADB by doing the following:
a. Downloaded the Stock Nvidia Shield TV image.
b. Extracted and copied the folder to ADB fastboot program file directory.
c. Connected Shield with USB to Windows computer.
d. Opened ADB and typed "adb devices" to verify and device showed up.
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
g. typed, "flash-all.bat" in ADB and it says, "flash-all.bat" is not recognized as an internal or external command"
NOTE: I do have Developer mode, and USB Debugging enabled on the Shield.
The reason I want to unroot is because I have experienced some pretty annoying problems since root. Intermittently upon reboot, Netlix and the Nvidia Game apps do not show. They are just empty spaces. Also the recommendations do not show. I also frequently get "Unfortunately Google Play Services has stopped working" also "Unfortunately Tegra Services has stopped working" and apps crashing/freezing on a regular basis, which force quitting does not resolve. Have to restart Shield to get working again.
I have searched online, and looks like for the most part people who root this device end up not having these problems. Seems like everyone is pretty happy with the root and not experiencing these issues. There are a few I have talked to that have these or similar problems.
If someone could provide me with instructions on how to successfully Unroot my Shield, that would help me out a great deal. I just want it to operate like it was when I first got it. Thanks much for your time.
Click to expand...
Click to collapse
the firmware pack (the img files, and bat file in the zip file) need to be in the same directory as adb and fastboot
you also need to boot the shield in fastboot mode, you can't flash it otherwise.
Need Help With Unroot
xd4d3v said:
the firmware pack (the img files, and bat file in the zip file) need to be in the same directory as adb and fastboot
you also need to boot the shield in fastboot mode, you can't flash it otherwise.
Click to expand...
Click to collapse
Ok, so when I downloaded the file from: http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/#comment-505
(towards bottom of page under "Restore Shield Android TV to Stock" prerequisites)
It was 1 zip file which I unzipped, and left me a folder with all the files in it (boot.img, recovery.img, blob .bat etc.) I transferred that folder into the minimal adb fastboot folder in C:\program files x86\minimal adb fastboot
Is this the correct process? Or should I have copied the contents of the folder into minimal adb fastboot directory, like a patch?
Thanks for your time, I really appreciate it.
mikie00mike said:
Ok, so when I downloaded the file from: http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/#comment-505
(towards bottom of page under "Restore Shield Android TV to Stock" prerequisites)
It was 1 zip file which I unzipped, and left me a folder with all the files in it (boot.img, recovery.img, blob .bat etc.) I transferred that folder into the minimal adb fastboot folder in C:\program files x86\minimal adb fastboot
Is this the correct process? Or should I have copied the contents of the folder into minimal adb fastboot directory, like a patch?
Thanks for your time, I really appreciate it.
Click to expand...
Click to collapse
Direct link from nvidia http://developer.download.nvidia.co...1/nv-recovery-image-shield-atv-upgrade2_1.zip
And instructions http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
if your Shield is not showing up on devices list, you need to install nVidia's driver. It was pretty weird with my Shield. Even with generic drives installed, adb couldn't get authorization from shield. I saw it on a list, but couldn't talk to it. Only after installing official Windows drivers for Shield, I was able to get ADB authorization box to pop up and communicate with device through ADB/fastboot.
mikie00mike said:
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
Click to expand...
Click to collapse
I'm trying to flash zulu's StockRestyle 3.0 for SATV v1.0 ROM and the "adb reboot bootloader" works fine for me when the shield box is booted up to android (fastboot devices comes up blank), but when I then enter "fastboot" mode, "fastboot devices" comes up with nothing as does "adb devices". It seems once the command to reboot bootloader sends me to what should be fastboot mode, I lose control from the PC.
Any ideas?
gffmac said:
Direct link from nvidia http://developer.download.nvidia.co...1/nv-recovery-image-shield-atv-upgrade2_1.zip
And instructions http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Click to expand...
Click to collapse
I was trying to unroot 2017 Shield TV (16GB) using the instructions provided in this post and failed to notice the recovery image listed here is for 2015 ? version.
Now the shield doesn't boot, not even into fastboot. anyway I can recover?
I should have paid more attention and read more before blindly using the link provided
HELP! fastboot only sees shield for couple seconds
Trying to Restore my 2015 Shield tv.
First couple steps went ok, but in the middle of flashing the system image, I got an error. Now, the shield reboots and I get the laying down android with the "no Command". If I hold down the power button, I get a different boot-loader screen. Then it reboots after a minute. I plugged in my controller into the USB port closest to the HDMI port, hold down the A and B buttons, which gets me into the normal boot-loader.
Problem is that windows sees the shield for a couple seconds, then it disappears. When I type ADB devices, nothing shows up.
What am I missing?
Hello, So i have searched and have been unable to find any info on unroot NVidia Shield Tv (2017) without a computer. I cant seem to find my USB A to USB A cable. I think it may have been stolen last year when a bunch of my stuff was stolen.
Is it possible, if not, is it possible to use the terminal on my phone to unroot.
Any answers would help, and i would greatly appreciate it.
Mnstr3nrgy said:
Hello, So i have searched and have been unable to find any info on unroot NVidia Shield Tv (2017) without a computer. I cant seem to find my USB A to USB A cable. I think it may have been stolen last year when a bunch of my stuff was stolen.
Is it possible, if not, is it possible to use the terminal on my phone to unroot.
Any answers would help, and i would greatly appreciate it.
Click to expand...
Click to collapse
if u only want to unroot pretty sure theres amagisk uninstaller that can be used..
if u also mean relocking the bl then it might be possible if your mobile has adb and fastboot binaries.. theres a module in magisk to install adb and fastboot binaries.. then it would depend if it can connect or not
elliwigy said:
if u only want to unroot pretty sure theres amagisk uninstaller that can be used..
if u also mean relocking the bl then it might be possible if your mobile has adb and fastboot binaries.. theres a module in magisk to install adb and fastboot binaries.. then it would depend if it can connect or not
Click to expand...
Click to collapse
I know that I'm replying super late. My bad. But I just ended up buying a cable off Amazon. Then like 2 days after unrooting, I found the original cable I was looking for in the first place. LOL