Related
I accidentally deleted kindle fire system files and now i can do anything.
Is any way to reload operating system from scratch?
I am stuck on kindle fire logo try everything help help help
nikolasargyrou said:
I accidentally deleted kindle fire system files and now i can do anything.
Is any way to reload operating system from scratch?
I am stuck on kindle fire logo try everything help help help
Click to expand...
Click to collapse
Deleting files from the system folder only affects the current rom(or as you call it, operating system) and doesn't affect ADB or the TWRP recovery program. You can use TWRP to install a new rom, even the stock Kindle rom.
I can't post links, so search google for "kindle fire software update" and you should find amazon's page to download the latest stock rom for the kindle fire. Rename the file to update.zip and transfer it to the storage on your kindle. You can then use TWRP to select the zip file and re-install the stock kindle rom. This WILL break your root, so use the Kindle Fire utility that's linked in the development forum if you want to re-root your kindle.
If you don't have TWRP installed, try using the Kindle Fire Utility (in the development forum) to install TWRP or recover your kindle fire. I hope this helps!
karmadragon said:
Deleting files from the system folder only affects the current rom(or as you call it, operating system) and doesn't affect ADB or the TWRP recovery program. You can use TWRP to install a new rom, even the stock Kindle rom.
I can't post links, so search google for "kindle fire software update" and you should find amazon's page to download the latest stock rom for the kindle fire. Rename the file to update.zip and transfer it to the storage on your kindle. You can then use TWRP to select the zip file and re-install the stock kindle rom. This WILL break your root, so use the Kindle Fire utility that's linked in the development forum if you want to re-root your kindle. I hope this helps!
Click to expand...
Click to collapse
Thanks for the reply
The kindle its not mine it belongs to my boss.He tried to root it deleted some files i think its not rom problem but something else.Is any way to load rom and install it from the pc.can't access kindle the only thing i find on my pc is a winre drive with 2 files sources and boot.sdi.i try everything all utilties on internet all suggentions but nothing.TWRP is a utility that runs from device or pc?
nikolasargyrou said:
TWRP is a utility that runs from device or pc?
Click to expand...
Click to collapse
TWRP is the recovery program that you can boot into before the rom loads. You can use the Kindle Fire Utility to install TWRP. If the kindle fire utility isn't working, you can try installing TWRP manually, but you will also need to install FireFireFire, which is the boot loader that replaces the stock kindle loader and allows you to boot into TWRP.
The most important thing is to have ADB access. If you can plug the kindle fire into your PC and get ADB working, you can fix pretty much anything.
How i can be sure that adb is working?
The most important thing is to have ADB access. If you can plug the kindle fire into your PC and get ADB working????How i can be sure that adb is working?
download the latest kfu from here:
http://forum.xda-developers.com/showthread.php?t=1399889
extract to c:\ and rename "kindle fire utility" to "kfu"
cd to c:\kfu and run "install_drivers.bat"
cd to c:\kfu\tools and type:
"adb devices" - get a response ?
"fastboot devices" - get a respose ?
you should get a response from one of the commands
I have to mention when in b63 post where your in the tools folder it easier to right click inside that folder in an empty space within it, and then press the keyboard's shift key for an option from the right clicked dropdown to open a command prompt window right there. Then type adb devices followed by enter key. Optimum would be a device ##000000000 sorta output in that tiny window , whereas then you could close it and click run in the kindle fire utility from the download. You can see more options to root your device to here with "status info".
Same problem
b63 said:
download the latest kfu from here:
http://forum.xda-developers.com/showthread.php?t=1399889
extract to c:\ and rename "kindle fire utility" to "kfu"
cd to c:\kfu and run "install_drivers.bat"
cd to c:\kfu\tools and type:
"adb devices" - get a response ?
"fastboot devices" - get a respose ?
you should get a response from one of the commands
Click to expand...
Click to collapse
>>> Hi, I have the same problem here. I accidentally deleted my rooted KF system with no rom saved on my KF (I'm a noob). Now, I did the steps you mentioned above.
This is what I have:
-When I typed ad devices it says "list of devices attached :15FE000600000001"
-Got nothing when typed "fastboot devices.
-On KFU it says" adb statusnline', "boot status:unknown".
-I can't install the Fastboot mode on the KF because it stays on waiting for device.
-My pc recognizes the Kindle as a device on the Device Manager, but I can't explore it because it doesn't show up on My Computer.
-I have already unistalled, deleted, re-install the drivers many times. The one that comes with KFU only makes the adb status go offline. The only driver that makes it show on the computer is the one I get when I connect the KF to the computer and let it download a driver by itself.
Please tell me, what can I do to make it show up so I can paste the rom on the device.
erikac71 said:
>>> Hi, I have the same problem here. I accidentally deleted my rooted KF system with no rom saved on my KF (I'm a noob). Now, I did the steps you mentioned above.
This is what I have:
-When I typed ad devices it says "list of devices attached :15FE000600000001"
-Got nothing when typed "fastboot devices.
-On KFU it says" adb statusnline', "boot status:unknown".
-I can't install the Fastboot mode on the KF because it stays on waiting for device.
-My pc recognizes the Kindle as a device on the Device Manager, but I can't explore it because it doesn't show up on My Computer.
-I have already unistalled, deleted, re-install the drivers many times. The one that comes with KFU only makes the adb status go offline. The only driver that makes it show on the computer is the one I get when I connect the KF to the computer and let it download a driver by itself.
Please tell me, what can I do to make it show up so I can paste the rom on the device.
Click to expand...
Click to collapse
You're getting confused with how adb and fastboot work. I suggest reading this to get a better understanding.
soupmagnet said:
You're getting confused with how adb and fastboot work. I suggest reading this to get a better understanding.
Click to expand...
Click to collapse
Thanks, I have read it like 3 times, it's just a little confusing for someone dealing with rooting for the first time. What I get is that I need to get the KF come up on Windows so I can paste the rom into the KF and that the KF needs to be in fastboot to install the rom.
Anyway, now the Kindle shows up on KFU as "online" and the bootmode is "4000", but still nothing comes up on the explorer. Twrp is installed and I'm able to load it, but I did not make a Backup. How can I install the system again?
If twrp is installed when you boot into it click on mount, then click mount usb, this is the only way it's going to show up as a mass storage device on your pc so that you can transfer a rom over to it.
Sent from my Amazon Kindle Fire using xda app-developers app
erikac71 said:
Thanks, I have read it like 3 times, it's just a little confusing for someone dealing with rooting for the first time. What I get is that I need to get the KF come up on Windows so I can paste the rom into the KF and that the KF needs to be in fastboot to install the rom.
Anyway, now the Kindle shows up on KFU as "online" and the bootmode is "4000", but still nothing comes up on the explorer. Twrp is installed and I'm able to load it, but I did not make a Backup. How can I install the system again?
Click to expand...
Click to collapse
Put both zips on your sdcard in zip form, wipe factory/data reset, wipe cache, wipe dalvik, wipe system, flash rom zip, flash gapps zip, reboot then system if prompted.
Thank you so much!!! :laugh:
I have done what you told me and my Kindle is now working. It's already downloading my files from the cloud.
(Sorry for the long reply, I had to go to work.)
Very good you`re welcome.
I rooted my Kindle Fire two weeks ago and updated it to jellybean 4.2 using the ROM developed by hashcode. Now after the update, I feel like I bricked my device. Because first of all TWRP (blue Kindle fire logo with boot options below) is not loading in startup but regular Kindle fire logo is seen. And I can't install TWRP using Kindle Fire Utility because my device is now a different ROM and KFU can't detect my Kindle. And I'm not at all satisfied with the battery life of Kindle Fire on JB 4.2 and it gets hot like red-hot-iron even just when I watch a video. Somebody please help me to at least to get TWRP on my kindle so I could just set it to default ROM or any other. Or please tell me a way to get out of this condition.
Sent from my Amazon Kindle Fire using xda app-developers app
srvrpc said:
I rooted my Kindle Fire two weeks ago and updated it to jellybean 4.2 using the ROM developed by hashcode. Now after the update, I feel like I bricked my device. Because first of all TWRP (blue Kindle fire logo with boot options below) is not loading in startup but regular Kindle fire logo is seen. And I can't install TWRP using Kindle Fire Utility because my device is now a different ROM and KFU can't detect my Kindle. And I'm not at all satisfied with the battery life of Kindle Fire on JB 4.2 and it gets hot like red-hot-iron even just when I watch a video. Somebody please help me to at least to get TWRP on my kindle so I could just set it to default ROM or any other. Or please tell me a way to get out of this condition.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
The blue & white Kindle Fire logo with boot options is FireFireFire, not TWRP. You may or may not have TWRP installed but without access to it you'll probably never know.
If you have root permissions, the easiest and most straight forward way of getting FFF installed is to do so through terminal emulator on your device (install it if you have to).
1) Download FFF1.4.zip onto your device and extract it. That should put the resulting folder in /sdcard/extracted. There, find the uboot.bin file and move it directly to the root of your sdcard (i think it's named something like "firefirefire1.4u-boot.bin"...rename it to "u-boot.bin").
2) Then open terminal emulator and enter the following commands:
Code:
su
dd if=/sdcard/uboot.bin of=/dev/block/mmcblk0p[B]2[/B][COLOR=Red]<---This is a [U]TWO[/U][/COLOR]
That will overwrite your bootloader partition with the new u-boot.bin. Just reboot and it should work. The problem with that is, if you get a corrupt download, it may hard-brick your device. Be sure to do an md5 check.
A safer way to do this is through TWRP. You can install and access TWRP relatively in the same manner with terminal emulator.
1) Download the TWRP.img and the FFF1.4.zip (don't extract it) onto your device and place them on the root of your sdcard. (rename TWRP to "twrp.img" to make things easier)
2) In terminal emulator, enter the following commands:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p[B]5[/B][COLOR=Red]<---This is a [U]FIVE[/U], not a TWO...pay attention[/COLOR]
idme bootmode 5001
reboot
3) In TWRP, flash the FFF1.4.zip, but don't wipe anything. This method will automatically check the md5 of FFF before installing it and reduce the possibility of accidentally bricking the device.
Reboot and all will be well.
soupmagnet said:
The blue & white Kindle Fire logo with boot options is FireFireFire, not TWRP. You may or may not have TWRP installed but without access to it you'll probably never know.
If you have root permissions, the easiest and most straight forward way of getting FFF installed is to do so through terminal emulator on your device (install it if you have to).
1) Download FFF1.4.zip onto your device and extract it. That should put the resulting folder in /sdcard/extracted. There, find the uboot.bin file and move it directly to the root of your sdcard (i think it's named something like "firefirefire1.4u-boot.bin"...rename it to "u-boot.bin").
2) Then open terminal emulator and enter the following commands:
Code:
su
dd if=/sdcard/uboot.bin of=/dev/block/mmcblk0p[B]2[/B][COLOR=Red]<---This is a [U]TWO[/U][/COLOR]
That will overwrite your bootloader partition with the new u-boot.bin. Just reboot and it should work. The problem with that is, if you get a corrupt download, it may hard-brick your device. Be sure to do an md5 check.
A safer way to do this is through TWRP. You can install and access TWRP relatively in the same manner with terminal emulator.
1) Download the TWRP.img and the FFF1.4.zip (don't extract it) onto your device and place them on the root of your sdcard. (rename TWRP to "twrp.img" to make things easier)
2) In terminal emulator, enter the following commands:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p[B]5[/B][COLOR=Red]<---This is a [U]FIVE[/U], not a TWO...pay attention[/COLOR]
idme bootmode 5001
reboot
3) In TWRP, flash the FFF1.4.zip, but don't wipe anything. This method will automatically check the md5 of FFF before installing it and reduce the possibility of accidentally bricking the device.
Reboot and all will be well.
Click to expand...
Click to collapse
Thanks for the help! But I have a doubt, because my Kindle is on Jelly Bean, it is on MTP mode when connected to computer. Will it be a problem? And where do i get a non-corrupted FFF1.4.zip ?
srvrpc said:
Thanks for the help! But I have a doubt, because my Kindle is on Jelly Bean, it is on MTP mode when connected to computer. Will it be a problem? And where do i get a non-corrupted FFF1.4.zip ?
Click to expand...
Click to collapse
Terminal emulator is an app that is run on the device, not the computer, so it doesn't matter what settings you have enabled or whether your drivers are working properly. And there is one main source for FFF1.4. Corruption, if it happens, usually happens when downloading so an md5 check needs to be done before flashing the file you downloaded to your bootloader partition.
closed
Read this whole thread. THE WHOLE THING. Preferably thoroughly.
edited
AJThePwnapple said:
Even though I have a factory cable, do you want me to go into fastboot using your method?
I tried flashing the images but my computer doesn't recognize the device (can't install otter2-prod-04) and stays at <waiting for device>. Will it be different using your method?
Sorry if I come off a bit noobish, I'm brand new to this.
Click to expand...
Click to collapse
you need the drivers (should have been mentioned on that thread.)
If you have a fbcable, use it. on windows, device manager, uninstall the current driver if there is any, and use KFU to install the fastboot driver. (only use kfu for the driver, don't do anything else.)
Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.
AJThePwnapple said:
Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.
Click to expand...
Click to collapse
No problem, i'm happy to help
I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC
Same here...
obsolete1 said:
I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC
Click to expand...
Click to collapse
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...
yudanjah said:
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...
Click to expand...
Click to collapse
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.
melvsmis ster said:
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.
Click to expand...
Click to collapse
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck
gnandez said:
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck
Click to expand...
Click to collapse
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr then plug device to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?
melvsmeister said:
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr tn plug devicle to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?
Click to expand...
Click to collapse
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help
gnandez said:
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help
Click to expand...
Click to collapse
I guess I'm missing some steps here or maybe I need to do something to make it work since my adb is not detected in TWRP but I can have it if I let it boot to blue kindle logo. I'm still having a hard time in pushing ROM due to "No space left on device" error and even though I can push gapps I can't find it in TWRP. I'll just wait for someone who might had the same issue and have other solution to resolve this problem. Thanks for your help!:good:
I was trying to help a friend install Kit Kat on his device, we followed the guide to root his Kindle Fire here at this link: http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955 as well as sd_shadow's video (https://www.youtube.com/watch?v=WqY5AUcf0Vk&index=2&list=PLx4mdsajQ2fW9gjN5BQti-8YM5F8xNV2W) and this is the link the the instructions that I used to try and flash KitKat onto the device: http://forum.xda-developers.com/showthread.php?t=2671619. I was able to get through the instructions for rooting the tablet, but something went wrong when I was following the instructions to get his tablet running KitKat. I used v2.04 for the bootloader (it was the version that was being used in sd_shadows' video on youtube (https://www.youtube.com/watch?v=8_poieP0ruI&feature=youtu.be) ) and I also used otter x twrp version 2.7.0.0 (for the same reason that I used v2.04 for the bootloader). The bootloader flashed fine, but it just kept rebooting whenever we would try to put it into recovery mode to flash the new version of twrp. I tried converting from Amazon partitions to Otterx and back as well as EMMC corruption fix (yeah, I know it was very stupid, I will own up to that). Now all that the device will do is boot into fasboot mode whenever you try to boot into recovery or into the ROM (I figure that it is trying to tell you to use fastboot to flash a new recovery image onto the device, sort of like the "forced download mode" that Samsung Galaxies can go into when nothing else is working correctly, so at least it boots on and is trying to help me fix it right? THe only problem is adb and fastboot do not recognize the device, my computer still recognizes it as a the way that it should when it is in fastboot mode (Android ADB Interface), but the device still cannot be interacted with and I do not know why (I have the kindle fire adb drivers installed). My friend is not upset that he cannot use his kindle (he never used it much anyways) but I would really like to know what happened and what I will need to do in order to fix my mistakes.
you tried ?
Code:
fastboot devices
sd_shadow said:
you tried ?
Code:
fastboot devices
Click to expand...
Click to collapse
I turned it on. In the bootloader menu I seleted "RECOVERY MODE", it booted into fastboot mode. I plugged it into my computer and opened the command prompt. In the command promt I entered "cd\adb" then I entered fastboot devices (like you said to), then the it said D01EC0A014820PK1 fastboot. What exactly does that mean? Is this device fixable?
If you get a code back like that it means drivers are good, and kindle is receiving commands, that is good
Sent from my XT894 using Tapatalk
---------- Post added at 05:36 PM ---------- Previous post was at 05:35 PM ----------
What twrp file are you trying to flash? Full file name with commands
Sent from my XT894 using Tapatalk
I have an update, I was able to successfully flash otterx-twrp-2.7.0.0-recovery onto his tablet. I converted to otterx partitions beforehand (does that make a big difference? I am able to boot the tablet into the boot menu and then boot into recovery w/o problems. . I am wondering, what now?
CidtheCyanKid95 said:
I have an update, I was able to successfully flash otterx-twrp-2.7.0.0-recovery onto his tablet. I converted to otterx partitions beforehand (does that make a big difference? I am able to boot the tablet into the boot menu and then boot into recovery w/o problems. . I am wondering, what now?
Click to expand...
Click to collapse
I would download
zip-otterx-twrp-2.7.1.0-recovery.zip, and otterx-u-boot_v2.05.zip, push them to sd card , and install them in TWRP
redo the wipes, pick a otter x rom, download it, push it, and install.
sd_shadow said:
I would download
zip-otterx-twrp-2.7.1.0-recovery.zip, and otterx-u-boot_v2.05.zip, push them to sd card , and install them in TWRP
redo the wipes, pick a otter x rom, download it, push it, and install.
Click to expand...
Click to collapse
Can you explain this to me step by step? (I apologize, but I want to make sure that I am doing this right)
CidtheCyanKid95 said:
Can you explain this to me step by step? (I apologize, but I want to make sure that I am doing this right)
Click to expand...
Click to collapse
download zip-otterx-twrp-2.7.1.0-recovery.zip, and otterx-u-boot_v2.05.zip, rom and Gapps (gapps depend on which rom you choose)
then
push them to sd card ,
Code:
adb push zip-otterx-twrp-2.7.1.0-recovery.zip /sdcard
adb push otterx-u-boot_v2.05.zip /sdcard
To install them in TWRP: select Install, choose zip-otterx-twrp-2.7.1.0-recovery.zip, and then select add another, choose otterx-u-boot_v2.05.zip, install
reboot
at bootloader select recovery
wipe cache, reboot, format sytem..." like in video Step 4 in OtterX thread
push rom and gapps with adb
sd_shadow said:
download zip-otterx-twrp-2.7.1.0-recovery.zip, and otterx-u-boot_v2.05.zip, rom and Gapps (gapps depend on which rom you choose)
then
push them to sd card ,
Code:
adb push zip-otterx-twrp-2.7.1.0-recovery.zip /sdcard
adb push otterx-u-boot_v2.05.zip /sdcard
To install them in TWRP: select Install, choose zip-otterx-twrp-2.7.1.0-recovery.zip, and then select add another, choose otterx-u-boot_v2.05.zip, install
reboot
at bootloader select recovery
wipe cache, reboot, format sytem..." like in video Step 4 in OtterX thread
push rom and gapps with adb
Click to expand...
Click to collapse
Dude. The THANK YOU!!! His tablet is working fine now!!! :victory: Enjoying PAC-ROM!
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.
enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.