Develop Bugs

[Q] Eeek, help!! In TWRP, can't get rom onto kindle to flash!!

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.

Help with fastboot!

Disregard, issue resolved.
I followed the procedure listed below from the 'Help how root new update 8.5.1' thread page 10 from andraw40 (which worked fine btw) but when I got to step 7, Fastboot doesn't seem to be doing what it is supposed to do which is reboot my device into Fastboot. I shut my tablet down, issue the command and then plugin my device but all it does is just boot up into the OS. What am I doing wrong? The SDK is installed and ADB appears to be working. With the device plugged into my PC, I can issue the command 'adb devices' and it shows a device plugged in. Any help would be greatly appreciated!
andraw40 said:
Guys, first of all THANK YOU for posting and helping other people.
For the last several days I have tried as hell to make my Kindle Fire HD to work like an usual android tablet. It was hell! with blocking the tablet, bricking it, reinstall it, coming back to Amazon version, and all of that for many times. Why? Because of too many version of procedures, because of missing important info from different procedures, because of me doing things wrong, and of course, because of me not reading carefully the procedures. Whatever... Finally I get it. And because it is normal to give back, here I am trying to make easy the path for a next "me".
(This procedure is for Windows Vista or above. On Windows XP there will be a lot of problems with ADB.)
So, what I had: Kindle fire HD, 8.9", version 8.5.1
What I have now: Kindle Fire HD, 8.9" (same ), runing CyanogenMod 11 and all the Google Services
How did I get there:
1. install from Amazon the ES File Explorer
2. make sure you enable ADB in Security, on Kindle
3. connect Kindle on computer and make sure you have installed ADB drivers. Check this in Device Manager. If you have the yellow warning, with the tablet connected, install "Kindle_Fire_HD_ADB_Drivers"
4. download, copy on Kindle (in Downloads) and then install "www apks.org-com zhiqupk root apk" to root the tablet. You need to root it in order to give permission to write in System folder. The aplication is the one mentioned by esema1o in the begining (keymasteroot) - Thank you esema1o! It is in Malaysian and you can use Google translate on computer if you are curious about the labels. It will not help you further but it will satisfy your need to know. So: press Mulai Root - it will do something, then will get a message. Press Root, not Batal. Another "doing something" then a new message. Choose Batal. (search on youtoube for "How to Root an Android Device with Key Root Master"). Done! You have rooted the Kindle. Reboot.
5. Open ES File Explorer and in Tools put all the switches on. Actually you will need only the Root Explorer. If you have problems keeping on the Root explorer reboot, open again ES File Explorer, try again. On the same tablet I had experienced different result after restoring the tablet to original Amazon version. Some time, I let the tablet open, come back after 15-30 minutes and try again to activate Root explorer. Surprise! it worked! Other times worked from first try or at seccond try. It is about your luck! Now, after is staying on, press on Root Explorer. A window will pop-up. Choose there to allow w/r on System folder.
6. Download "KindleFireHD89Root.zip" (you can fiind it by search on this forum by name. I'm not yet allawed to post links so remove the space before here: downloadandroidrom com/file/KindleFire/8.9root/KindleFireHD89Root.zip). Extract. Navigate into "stuff" folder. Shift +right click in window, then choose "Open command window here". (Or you just run cmd and navigate to "stuff" folder.)
7. Check fastboot avability:
Type the following command into the cmd window you had opened before at 6.
fastboot -i 0x1949 getvar product
it should return:
< waiting for device>
Then connect Kindle to computer with a regular usb cable. Power down Kindle. Press power buton to start Kindle. . It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04
Type this to reboot out of fastboot mode:
fastboot -i 0x1949 reboot
8. follow this procedure: wiki cyanogenmod org/w/Install_CM_for_jem (again, remove spaces and add points to have working link)
Note: when you get to the point "Installing CyanogenMod from recovery" you may be confuse about the fact that adb commands are not working. If so, you check not to be in the recovery boot mode. Just shut down Kindle by long pressing power button, or reboot from meniu and if not passing the booting yellow logo, shut it down again by long pressing power button, then go in the fastboot mode again (see the first part of point 7; do not execute reboot! if you did reboot try again to enter in fastboot mode). Now, in fastboot mode, you can follow the instructions to copy zip files on tablet (I used the cyanogenmode 11 and Google apps zip files). After copy them on tablet, go back to the procedure at the point 4 where you start the kindle in recovery mode again by pressing volume up etc. If you do not succeed by pressing volume up during boot, simple enter again in fastboot (you should know how to do it by now ) and from terminal window on computer (cmd window where you are in "stuff" folder) type:
fastboot -i 0x1949 oem recovery
At this point you are back in the procedure at point 6. Do or not the backup and go next. I did not encountered any problems from this point on.
That is all. Sorry for my English, and I hope that my "procedure" will help someone. Again, thank to all the good people that bother to help us!
Click to expand...
Click to collapse

[SOLVED] Sideload from recovery: Watch does not appear in adb devices

Hi all,
I have seen mentions in several places (including here http://9to5google.com/2014/12/18/how-to-update-android-wear-manually-ota-downloads/ and there http://forum.xda-developers.com/showpost.php?p=61430452&postcount=6 ) that it is possible to sideload an OTA to the SmartWatch 3 without using fastboot or rooting, just rebooting in recovery and running adb sideload.
However, in my case, although the watch properly appears in "adb devices" when it's powered on, when I go into recovery, it does not appear anymore... And thus I can't run "adb sideload" as adb, obviously, says "no devices found"
Any idea? Am I missing some trick? I have tried this both on Windows 8 and on Ubuntu, both behave in the exact same way.
I have also tried going into recovery using two different means: "adb reboot recovery" and using the menu that has fastboot/recovery options, nothing solves the issue.
Thanks!
PS: The reason why I am trying to sideload the OTA is to go 4.4 -> 5.0.1 and not 4.4 -> 5.1.1 because of all the 5.1.1 issues + I hate 5.1.1 UI

Did you click the adb sideload button in recovery? This enables adb.
If that does not work, try using fastboot to temporarily boot twrp from fastboot, but you will need to install fastboot drivers on your p.c. and find a 4.4 version of twrp.
The command is
Code:
fastboot boot twrp.img
From there you should be able to use adb.

Hi!
Do you mean selecting the "sideload" option in recovery? Yes I have selected this (by swiping down and then right to validate the choice) and my device still does not show up in adb. Have you been able to do this on the SmartWatch3? I feel like most people have experience with the LG G Watch...
In order to flash TWRP. I need to unlock the bootloader, don't I? If I can avoid voiding my warranty, that'd be great...
Thanks!

My first thought was the sideload option. I did not do it, but am on an SW3. I went right to option 2.
This does not unlock your boot loader, or void your warranty. What it does is hotboot another Rom (in this case recovery) without writing it to disk. I did do this, and it worked well.
This is the thread I followed. Skip the fast foot unlock step. That. An void your warranty.
http://forum.xda-developers.com/showthread.php?t=3107501

Oh! This is pretty awesome. Trying it, thanks a lot!

YESS! lekofraggle, I owe you a good one
So, for future readers, here is the procedure I went through. I have tried many different ways, this is the only which yielded results, so I'll only explain this one:
1) First, make sure that when your watch is connected to your phone, it displays the notification prompting you to upgrade your andoird wear version (I am not sure it will work if you don't have this notificaiton) (note that this notification only appears when the watch is connected to the phone in bluetooth, for me)
2) Follow http://forum.xda-developers.com/showthread.php?t=3107501 instructions to hot boot TWRP 5.0.2 (yes, even though you're in 4.4, does not matter (too much)). (command: fastboot boot twrp.img)
3) Root your watch by downloading the rooting zip from http://forum.xda-developers.com/attachment.php?attachmentid=3342605&d=1433157678 and "adb push yourzip /sdcard/root.zip"
4) In TWRP, your watch, go to "Install" and select "root.zip". You watch is now rooted.
5) Reboot your watch in normal android boot. Now push the OTA zip to it: "adb push yourota.zip /sdcard/update.zip"
6) Now is the trick: Replace the official OTA by yours: do "adb shell" and then "rm /cache/update.zip" and "cp /sdcard/update.zip /cache/update.zip".
7) Now check you still have the notification prompting for upgrade (your watch needs a bluetooth connection to phone, else it does not display it). Check the zip in /cache is still your by looking at the size, for instance: "ls -l /cache/update.zip" and compare with the size of your file.
8) If you're confident it is still your file, use the notifcation prompt on the watch and say you are ready to apply the upgrade.
9) Watch restarts and upgrade.... using your OTA file !
I tried using the custom "recovery command" that tutorials like http://www.carbontesla.com/2014/12/tutorial-update-smartwatch-3-lwx48p-android-5-0-1/ tell you to use but it would not work for me, only the notification would really trigger the upgrade...
Hope it helps!
PS: The reason for not using "adb sideload" directly from TWRP is that my OTA package (4.4 -> 5.0.1) would not be applied, it would complain that I am trying to apply it from a 5.0.2 system while it should be applied from a 4.4 system (oh, really?).

Great, I am glad it worked for you.
Two points for others travelling this path.
1)I am not sure you need to be rooted to do this, because twrp has its own permissions.
2) Did you try to use the install update.zip feature of twrp? That should have worked too.
Either way, I am glad you got there.
~Leko

80% fixed but need an experienced opinion

Have read a ton on XDA and elsewhere, to the point that I have too much information, and I think it's likely someone with more experience could point me to the right area to focus on. Any help is much appreciated! Thanks!
Where I started:
Was a total noob, had never tried to flash anything or use command line
One day my stock Kindle Fire HD 8.9 just stopped working on its own. Not sure why -- I never tried to root it or hack into it. I had left it plugged in for a week and it felt a little warm.
Powering on would get to the orange/white Kindle Fire screen, and then the screen would go blank and stay that way until powering off.
I just wanted to get the Kindle running again, preferably with stock OS or something that still allowed me to use Amazon Instant Video.
What I've accomplished so far:
Successfully got fastboot running! Originally through First Aide and now through command line too.
Successfully got TWRP 2.8.7 running! Downloaded the TWRP image and used fastboot to flash recovery.
Also flashed kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin from the instructions on XDA's 2nd bootloader page.
Tried using both First Aide and the SR Tool to restore system back to stock, but neither seemed to do anything. Even flashed the system.img included with the SR Tool manually using fastboot, but Kindle still won't successfully launch. Also tried the "Restore 2 Stock" program, which says it cannot find a device in TWRP mode (likely related to my ADB issue cited below).
Where I'm at now:
Now when powering on (in normal mode), Kindle stays at orange/white Kindle Fire boot screen forever. Screen no longer goes blank afterwards.
Can get to TWRP, but only by using "fastboot oem recovery -i 0x1949"
Strangely, ADB NOT working. While in TWRP mode, I use command line "adb devices" and it returns "B0C91004245614ME Offline". I'm pretty sure I have the correct ADB drivers (while in TWRP mode, device manager shows two entries: "Kindle ADB Mode" and "Recovery ADB Mode").
Obviously I have no backups of original system/boot images because the Kindle broke on its own and I've never seemed to have ADB access.
Questions:
Is there something big I'm missing in order to restore to stock? Intuitively, it seems like I should be able to just flash a working system image from fastboot. If I can't restore to stock, I'm fine installing another OS -- would just like to get the device working again.
I doubt I would have enabled ADB access before the Kindle broke. Is that the reason that the "adb devices" command returns "Offline"?
Have not tried gaining root access. Is that a prereq for using ADB and/or restoring to stock?
-Joe

joes6789 said:
Have read a ton on XDA and elsewhere, to the point that I have too much information, and I think it's likely someone with more experience could point me to the right area to focus on. Any help is much appreciated! Thanks!
Where I started:
Was a total noob, had never tried to flash anything or use command line
One day my stock Kindle Fire HD 8.9 just stopped working on its own. Not sure why -- I never tried to root it or hack into it. I had left it plugged in for a week and it felt a little warm.
Powering on would get to the orange/white Kindle Fire screen, and then the screen would go blank and stay that way until powering off.
I just wanted to get the Kindle running again, preferably with stock OS or something that still allowed me to use Amazon Instant Video.
What I've accomplished so far:
Successfully got fastboot running! Originally through First Aide and now through command line too.
Successfully got TWRP 2.8.7 running! Downloaded the TWRP image and used fastboot to flash recovery.
Also flashed kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin from the instructions on XDA's 2nd bootloader page.
Tried using both First Aide and the SR Tool to restore system back to stock, but neither seemed to do anything. Even flashed the system.img included with the SR Tool manually using fastboot, but Kindle still won't successfully launch. Also tried the "Restore 2 Stock" program, which says it cannot find a device in TWRP mode (likely related to my ADB issue cited below).
Where I'm at now:
Now when powering on (in normal mode), Kindle stays at orange/white Kindle Fire boot screen forever. Screen no longer goes blank afterwards.
Can get to TWRP, but only by using "fastboot oem recovery -i 0x1949"
Strangely, ADB NOT working. While in TWRP mode, I use command line "adb devices" and it returns "B0C91004245614ME Offline". I'm pretty sure I have the correct ADB drivers (while in TWRP mode, device manager shows two entries: "Kindle ADB Mode" and "Recovery ADB Mode").
Obviously I have no backups of original system/boot images because the Kindle broke on its own and I've never seemed to have ADB access.
Questions:
Is there something big I'm missing in order to restore to stock? Intuitively, it seems like I should be able to just flash a working system image from fastboot. If I can't restore to stock, I'm fine installing another OS -- would just like to get the device working again.
I doubt I would have enabled ADB access before the Kindle broke. Is that the reason that the "adb devices" command returns "Offline"?
Have not tried gaining root access. Is that a prereq for using ADB and/or restoring to stock?
-Joe
Click to expand...
Click to collapse
Regarding your questions:
1) Hashcode created a TWRP-flashable ROM zip for Amazon's stock OS., which you can find in this thread. You should download the 8.4.1 version from the d-h.st link in the thread, as the goo.im links no longer work because Goo.im (a former file hosting service for Android developers) shut down. However, beware the d-h.st (Dev-Host) links, as they are notorious for causing unwanted downloads and popups. Do NOT download anything executable (the file we want is a .zip, not anything else), as it can cause unwanted software or even malware to be inadvertently installed onto your PC (and in some cases, your android device).
2) Yes, that is why the command returns "offline" when you run it with the kindle in recovery mode.
3) No, root is not a prerequisite for either of those commands. (In fact, you'd have to have adb enabled before rooting the stock OS in most cases.) However, should you need root, the stock ROM that Hashcode built as a flashable TWRP .zip is rooted, and as long as you don't update the OS, your root should remain intact.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Regarding your questions:
1) Hashcode created a TWRP-flashable ROM zip for Amazon's stock OS., which you can find in this thread. You should download the 8.4.1 version from the d-h.st link in the thread, as the goo.im links no longer work because Goo.im (a former file hosting service for Android developers) shut down. However, beware the d-h.st (Dev-Host) links, as they are notorious for causing unwanted downloads and popups. Do NOT download anything executable (the file we want is a .zip, not anything else), as it can cause unwanted software or even malware to be inadvertently installed onto your PC (and in some cases, your android device).
2) Yes, that is why the command returns "offline" when you run it with the kindle in recovery mode.
3) No, root is not a prerequisite for either of those commands. (In fact, you'd have to have adb enabled before rooting the stock OS in most cases.) However, should you need root, the stock ROM that Hashcode built as a flashable TWRP .zip is rooted, and as long as you don't update the OS, your root should remain intact.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for the answers and explanations Monster. I downloaded Hashcode's 8.4.1 ROM zip, but I cannot figure out how to copy the zip file onto my Kindle, given that I don't have ADB access.
I did some research and it seems that one workaround is to use the Mount USB Storage feature within TWRP, but I can't get that to work. When I try to Mount USB Storage, no new storage drive shows on my computer (nor in Disk Management), and the TWRP error log says "Unable to mount storage. Unable to mount '/data'. Unable to mount '/cache'. Unable to find storage partition to mount to USB." Furthermore, the mount menu in TWRP says "Storage: Internal Storage (0 MB)" -- that doesn't seem good.
Do you have any other suggestions, either on how to get the zip file on my Kindle, or another alternative method to get my Kindle functional? Perhaps flashing something else directly from fastboot? Again, appreciate the help!

joes6789 said:
Thanks for the answers and explanations Monster. I downloaded Hashcode's 8.4.1 ROM zip, but I cannot figure out how to copy the zip file onto my Kindle, given that I don't have ADB access.
I did some research and it seems that one workaround is to use the Mount USB Storage feature within TWRP, but I can't get that to work. When I try to Mount USB Storage, no new storage drive shows on my computer (nor in Disk Management), and the TWRP error log says "Unable to mount storage. Unable to mount '/data'. Unable to mount '/cache'. Unable to find storage partition to mount to USB." Furthermore, the mount menu in TWRP says "Storage: Internal Storage (0 MB)" -- that doesn't seem good.
Do you have any other suggestions, either on how to get the zip file on my Kindle, or another alternative method to get my Kindle functional? Perhaps flashing something else directly from fastboot? Again, appreciate the help!
Click to expand...
Click to collapse
Boot into TWRP, then when you're in, choose Advanced -> ADB Sideload. Check the boxes that say "Wipe cache" and "wipe dalvik cache." Swipe where indicated to sideload, and hook up your kindle to your PC if it's not already connected. Type "adb devices" into a terminal/command prompt, and you should see a device that registers itself as "sideload" in the list. If you do, then type "adb sideload path/to/file.zip", where path/to/file.zip is the location of the downloaded 8.4.1 ROM zip. The ROM should automatically copy and flash; keep the kindle plugged in until the flashing process is complete. Any luck?
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Boot into TWRP, then when you're in, choose Advanced -> ADB Sideload. Check the boxes that say "Wipe cache" and "wipe dalvik cache." Swipe where indicated to sideload, and hook up your kindle to your PC if it's not already connected. Type "adb devices" into a terminal/command prompt, and you should see a device that registers itself as in "sideload" in the list. If you do, then type "adb sideload path/to/file.zip", where path/to/file.zip is the location of the downloaded 8.4.1 ROM zip. The ROM should automatically copy and flash; keep the kindle plugged in until the flashing process is complete. Any luck?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, the adb sideload worked!!! (just had to update my adb version to 1.0.32) Kindle seems to be fully functional. Thank you so much Monster!
Last thing, do I need to worry about OTA updates or anything in the future that might create a conflict with the bootloader or ROM I'm using?

joes6789 said:
Yes, the adb sideload worked!!! (just had to update my adb version to 1.0.32) Kindle seems to be fully functional. Thank you so much Monster!
Last thing, do I need to worry about OTA updates or anything in the future that might create a conflict with the bootloader or ROM I'm using?
Click to expand...
Click to collapse
I believe that the OS is properly patched in Hashcode's stock ROM, so you shouldn't need to worry about OTAs or a conflicting bootloader. Glad to see it works again!
Sent from my Amazon Jem using XDA Labs

How were you able to get into fastboot with kf first aide? Which drivers and which options?
Gesendet von meinem Nexus 6P mit Tapatalk

[GUIDE] Root and unbrick steps for ASUS ZenPad C 7.0 (P10Z - Z170C)

Hi all! It took me a lot of time to finally being able to root this tablet. It's old, slow and practically unusable, but with some tricks it can be made much, much better. I'm going to explain what you need to do to root this tablet, and in case of brick (which happened to me many, many times) how to unbrick it. I even got to a point where I could not even boot into recovery mode, and only fastboot was working, that was scary, but I managed to get out. Every single file I will use will be bundled in a ZIP you can download, and I'll try to make sure this link stays up, because there's nothing more frustrating than wanting to make these things in the future only to find out the link is dead, along with all your hopes. Before we begin, a little disclaimer:
Code:
#You, and only you are responsible for everything that you do or happens to your tablet.
#If you screw up, I have a number of backups to help you recover, but if that's not enough don't point a finger at me.
#I will not be babysitting anybody to help restore their tablet or recover lost data.
#This process WILL wipe all of your data, do a backup before beggining.
#YOU HAVE BEEN WARNED!
1. ENABLING USB DEBUGGING
This is a very basic step, but it's needed if you want to even begin to do this. You'll need to go to "Settings -> About Phone". There, look for a line that says "Compilation Number" (or something like that) and tap it multiple times. You will see a message pop up saying "You are now a developer" (I wish it was that easy). Go back to the settings screen, you will see a new option appeared called "USB Debugging". Enable it, and make sure "Developer Options" are enabled too at the very top of the screen. Now, connect the tablet to your computer. You will see a message pop up asking for permission, tap "Always allow from this computer" and press "Allow".
That's it for this step.
2. SETTING UP ADB TOOLS AND MAKING SURE THEY WORK
Now that we have USB debugging enabled, and we have allowed our PC to access the tablet, we can begin setting up ADB. The required files are attached in the zip.
Extract the "platform-tools" folder and move it somewhere nice. Then open it, hold shift and right click in a white space and select the option "Open command window here". CMD will pop up, now type:
Code:
adb devices
It will probably say something about a server followed by a list of attached devices. If you see a serial number there, then great! ADB is working as it should. If not, make sure the tablet is connected, that USB Debugging is on, and if all else fails, try with another cable.
Now for the juicy part.
3. UNLOCKING THE BOOTLOADER
We will have to unlock the bootloader if we want to do anything here. Here's what to do. Type:
Code:
adb reboot fastboot
Wait until the tablet reboots into fastboot. Once there type:
Code:
fastboot oem unlock
fastboot oem unlock confirm
This should unlock the bootloader.
NOTE: This method of unlocking is reported to not work anymore, but I listed it anyway just in case, as it doesn't hurt to try. If this is not working for you, don't panic, it's normal, use the following code instead:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
This should work, and the bootloader should be unlocked now.
4. INSTALLING THE REQUIRED FIRMWARE
Now, your tablet may or may not have the required firmware for the procedure, but just in case we will flash one that's sure to work. If you followed along, you should be in fastboot mode right now. Type:
Code:
fastboot reboot
Your tablet should boot as normal, without any changes (unless the first bootloader unlock method worked for you, in which case it probably wiped all of your data). Now we can access ADB once again, so type:
Code:
adb reboot recovery
The tablet will reboot into recovery mode and you should see an image of wasted android with an open belly (if you don't see this it doesn't matter). You should see a list of options with blue text, you must use the volume keys to navigate this menu. If you don't see any options, press any volume key and they should appear. If instead of getting into recovery mode, the tablet just turned off, then go to the "Fixing recovery" section.
In this menu, you must select "Wipe data/factory reset". This will, obviously, wipe all of your data. Once that finishes, select the "Install update through ADB" option. Once that's done, make sure the "updated_firmware.zip" file is in the same directory as the "adb.exe" file, then type:
Code:
adb sideload updated_firmware.zip
This will install the firmware, it will take about 20 mins. Once finished, reboot the device. You may think it got bricked at this point, fear not, the first boot really takes this long (about 10 mins).
Once everything is done, the device should boot up and everything should be exactly as it was when you took it out of the box, meaning, it doesn't even remember your wifi password. Do a quick (but proper) set up and enable USB Debugging again, make sure to allow the PC again (and check the "always allow" box). Also, scroll down a bit more in the developer options section and look for one that says "Verify apps installed through USB" or something of that kind. Make sure it's unchecked. Now, we gotta install root.
5. ROOTING
The all holy root, finally here. Type this into the terminal:
Code:
adb reboot fastboot
You should be familiar with this process by now. Once in fastboot mode, type:
Code:
fastboot boot root.img
Once finished, reboot. You should boot up as a rooted user, hooray! Only one final step, we gotta give ourselves some means to control this new power, that's where the SuperSU app comes into play.
6. INSTALLING SUPERSU
Apparently, not every single SuperSU apk file works... but lucky for you, I managed to scout and bundle one that does, so use that one. Make sure the apk file is in the same folder as "adb.exe" (as with all of the previous files) and type:
Code:
adb install supersu-2-82.apk
Leave it a few mins, and you should see a "success!" message when it's finished. Open the SuperSU app and it will tell you that you need to update the binaries. Say yes to that, and when asked wether to do a "Normal" update or "TWRP" update, select normal. It should be successful and prompt you to reboot, do so.
That's about it, you now have root access in the ASUS ZenPad C 7.0.
NOTE: Every single attempt I made to make the SuperSU app a system app resulted in the app crashing and I needed to reinstall it again, do as you please.
Why would you even want to do this you might ask? Well, I personally used this to make a few tweaks with Kernel Auditor and L Speed, two apps that will let you customize the performance of the machine to its maximum... sacrificing battery of course. You can search online for the best configuration for you for these apps. With the right tweaks, it transforms from **** to usable, and you need root for all of this.
As a quick note, you might notice that the SuperSU pop up that prompts you wether to grant or deny root access to an app is delayed, that's just how life is with this machine, it's slow. As a tip, when an app is trying to acquire root access, go back to the home screen and open the SuperSU app, then go back to the app you were trying to give it access to, it should appear quicked that way. Sometimes it's so slow that the app says I don't have root, only to have the pop up appear 10 seconds later. Now... to a final chapter.
7. UNBRICKING
This would be the end of the story if nothing went wrong, you have a rooted tablet and you can now do whatever you want with it, but that's not how life is. **** happens, things can go wrong, and when they do, you better have a backup plan. I don't know how to get back your ex, but I know how you can unbrick your tablet if that should happen. Follow these steps if you want to recover this machine...
Code:
#This process will wipe all data, but you shouldn't care about that since you can't access it anyway.
So, if the tablet doesn't turn on and gets stuck at the boot up screen, what can we do? Well, let it sit at the boot up screen for a few mins, and then type in the terminal:
Code:
adb devices
If it's recognized, then type:
Code:
adb reboot recovery
If it's not recognized, press the power button and the volume down key until the tablet turns off. Once that happens, press the power button and the volume down key, when the logo appears, let go of the power button and keep the volume down key pressed, that should boot the tablet into recovery mode. If you got into recovery mode, skip to 7.2
7.1 FIXING RECOVERY MODE
Sometimes, (it happened to me), recovery mode is broken.... it just doesn't appear, no matter what you do you can't get into it. To fix this, we gotta flash it again. We gotta enter fastboot mode. One option is to boot up the device until it gets stucked and wait a few mins, then adb should be able to recognize it and you type:
Code:
adb reboot fastboot
If that's not the case, turn the tablet off and press power and volume up, that should get you to fastboot. Once there type:
Code:
fastboot devices
And the tablet should appear there, if it doesn't... well it better do. I don't really know what to do if it doesn't appear there, but there shouldn't be a reason for it not to. I guess you can try to enter fastboot once again, with the tabler connected from the beggining or something like that, let's just assume it does, and if it doesn't then I'm sorry to tell you that's homework you will have to do.
Once here, we must format the cache and the data partition, for that type the following:
Code:
fastboot format cache
fastboot format userdata
Now, we need to get the recovery files, grab them from the zip I gave you. The files in question are "recovery.bin" and "vrl.bin". We will start with vrl. Once the two formats are finished, type:
Code:
fastboot flash vrl vrl.bin
Followed by:
Code:
fastboot flash recovery recovery.bin
Once that's done, press the power button and volume down keys until the tablet turns off. Then, press them again until the logo appears, and when that happens let go of the power button, that should get you (finally) into recovery.
7.2 UNBRICKING (FOR REAL THIS TIME)
Well, now that everybody is on the same page, and we could get to recovery mode, it's time to repeat some steps really... Follow the procedure from step 4 onwards (from the part that tells you to go to recovery). So, wipe data and apply that damn zip with sideload, the tablet should work now.
That's all I have to offer guys. I'm not a developer, I'm just a guy with a bunch of free time on his hands, so I was able to gather all of this information and (most importantly) files so you can root and fix this god damn tablet. Until the next one!
FINAL NOTE: In the files I included, there's a TWRP.img file. This is the TWRP custom recovery. As far as I know, this version should work with this tablet, but I was unable to flash it and make it work. IF YOU WANT TO TRY THIS DO SO AT YOUR OWN RISK, IT'S HIGHLY PROBABLE THAT THIS WILL RESULT IN BRICKING YOUR TABLET AND BREAKING THE STOCK RECOVERY, IN WICH CASE YOU WILL NEED TO FOLLOW THE STEPS STATED IN THIS GUIDE.
I couldn't upload the files as an attachment directly... sorry.
The "updated_firmware.zip" file is added as a separate download because it's a bigger file, and I prefer to let people decide if they even want it in the first place.
updated_firmware.zip
Everything else

None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface

neghvar said:
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
Click to expand...
Click to collapse
Make sure you enable usb debugging, no driver will work without that enabled.

tralph3 said:
Make sure you enable usb debugging, no driver will work without that enabled.
Click to expand...
Click to collapse
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices

neghvar said:
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
Click to expand...
Click to collapse
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"

tralph3 said:
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
Click to expand...
Click to collapse
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?

neghvar said:
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
Click to expand...
Click to collapse
Yeah I never could get around it either. I never could install a custom recovery on this tablet, it just wasn't made for it. But hey, root is cool.

Work?
Still working?

jerryspring said:
Still working?
Click to expand...
Click to collapse
Why wouldn't it? This tablet ain't gonna change. Everything should work no problem.

Hi, any custom rom for this device to make it useful ?
It is in my drawer for more than 2 years and I just do not know what with it
Also how to play with settings in root mode so I can make it faster ?

Hey folks,
I recently followed this guide and a couple of issues.
First, I had expected all my data to be gone, which is fine. But it wasn't. I seemed to have gotten all the way through without it being reformatted, and this makes me suspect I never really achieved all the goals.
One thing I should note, in recovery boot, I had to use the volume button to select a source. No big deal, but it had not worked until I guessed I needed to do that.
Oh, and another thing is I had to install the driver package, and then after, once it was rebooted into fastboot, manually guide the device manager to select from list.
It seems after complete shutdown and then a fresh bootup, my SuperSU software was gone. So, is this only a tethered root boot? Is there a completely untethered?
After rebooting again, it seems my device will not complete booting, but I will give it some more time. I may have bricked it, though I have no idea how lol. All I did was enable USB debugging again and issued the reboot command.
I know this is an old guide, and probably long forgotten by most participants, but I recently got one of these tablets online, open box but new or like new, for around $20, and I would like to get it rooted because otherwise, it is extremely sluggish and the battery drains very fast. I read online it is google play services at fault, but I do not know for sure.
Anyway, if anyone has any updated info or alternative method to achieve full root access untethered, please advise. Unless this guide is that, in which case I just need to try again. Just out of curiosity, what is the TWRP.img for?