I have the old TWRP installed via KFU and now want to update it.
Can I just install it straight over the old one and if so how do I do it ?
I understand that it's not as simple as using KFU to do it.
Any advice appreciated.
Use fastboot if you can. Assuming you have FFF installed and know how to use fastboot:
fastboot flash recovery /path/to/twrp.img
...or you could use one of smirkis' scripts.
http://forum.xda-developers.com/showthread.php?p=22608974
Is there an advantage to the new TWRP? I'm currently at 2.0 and trying to flash AOKP and hung at the opening animation and wondering if it has to do with an old TWRP .
I have FFF but as fire as I know that just takes me into twrp.
How do I get into fastboot. I've previously done this through KFU I think.
All I need is a step by step of how to do the install.
I get that I put the twrp 2.1.1 file on my pc and point the fire at it by running the fastboot command but I'm really not sure how to get into fastboot.
wigsey, I couldn't figure this out either. I had switched from TWRP 2 to CWM. Messed around with ADB and Kindle Fire Utility and I was only able to get back to TWRP 2; then I followed soupmagnet's advice. Installed Root Browser, downloaded and installed the scriptfiles. BEFORE running the scripts, however, I moved the latest version of TWRP into the Files folder of the scripts; renamed the twrp2-blaze.img version that was in there to "old" out of habit; copied over the new version of TWRP and renamed that to "twrp2-blaze.img" and then ran the script. Rebooted and had the 2.1.1 come up.
I am sure that there is an easier way, but for whatever reason using ADB just didn't work for me and this did.
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
wigsey said:
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
Click to expand...
Click to collapse
If you can, you want to get into fastboot and flash it from there. You don't have to copy it over to your KF first, fastboot knows where your recovery partition is located, it will do some basic checks to see that it will fit on the partition, etc.
Code:
fastboot flash recovery twrp.img
If at all possible, do it this way.
Alternatively, you can put the image on your /sdcard partition (this is what pops up when you mount the Kindle Fire's USB mass storage device on your computer) and write it directly to the recovery partition.
From the terminal emulator app...
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p5
This is essentially identical to the way smirkis' script will do the job.
It's a pain to type this on a virtual keyboard, so you can also use adb like this...
Code:
adb shell dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p5
In both cases above, you must have the mass storage device unmounted from your computer so your KF can access the file.
If you need fastboot or adb help, you can find it in the 3rd post of this thread...
http://forum.xda-developers.com/showthread.php?t=1552547
It should be noted that the "dd" command is nothing to be trifled with. It's been nicknamed "data destroyer" for a reason.
Pay CLOSE attention and verify what you have typed is correct before entering.
kinfauns, I tried the fastboot method, having renamed the 2.1.1 IMG file and it did not work for me. Seemed to go along, but when I rebooted into recovery, I still had 2.0.
The scripting method is a kludge, granted, but in my case it was idiot-proof.
---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------
wigsey said:
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
Click to expand...
Click to collapse
Actually I renamed the old one ".old" in case I needed it later. After success I deleted it. And yes, the TWRP website seems to be the best place to get the latest version.
koop1955 said:
kinfauns, I tried the fastboot method, having renamed the 2.1.1 IMG file and it did not work for me. Seemed to go along, but when I rebooted into recovery, I still had 2.0.
The scripting method is a kludge, granted, but in my case it was idiot-proof.
Click to expand...
Click to collapse
This sounds like you used the wrong fastboot command. The old install directions for 2.0 had you "fastboot boot" the image and now you need to "fastboot flash recovery" for version 2.1.0 and beyond. Any chance you just mixed up the commands? If you were not successful with the "fastboot flash recovery" command, it would have told you so... otherwise, it almost certainly would have wrote it out to the recovery partition.
"Any chance you just mixed up the commands? "
Always a chance of that, but I am all sorted anyway. FFF 1.3 and TWRP 2.1.1
koop1955 said:
"Any chance you just mixed up the commands? "
Always a chance of that, but I am all sorted anyway. FFF 1.3 and TWRP 2.1.1
Click to expand...
Click to collapse
You're on a roll, may as well get the latest FFF while you're hot.
Hashcode's new FFF 1.4
Very nice...damn near brick-proof now.
Related
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
James_Caliber said:
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
Click to expand...
Click to collapse
For flash_image, you need to make sure you have the binary. There is a thread all about it. (http://forum.xda-developers.com/showthread.php?t=902493)
For fastboot, is the recovery.img file located in whatever directory you are running the fastboot command from? What command are you running?
ianmcquinn said:
For flash_image, you need to make sure you have the binary. There is a thread all about it. (http://forum.xda-developers.com/showthread.php?t=902493)
For fastboot, is the recovery.img file located in whatever directory you are running the fastboot command from? What command are you running?
Click to expand...
Click to collapse
Yes I have flash_image in my tools folder :/
Does that answer the question?
James_Caliber said:
Yes I have flash_image in my tools folder :/
Does that answer the question?
Click to expand...
Click to collapse
Do you have an ENG. Hboot? If not, you can not use fastboot, youll have to flash recovery from terminal using flash_image.
Edit: See in your first post says you have HBoot installed, you mean ENG. Hboot right?
If you do have ENG. Hboot type
Code:
fastboot devices
Do you get a "serial # fastboot" ?
See if you have the right drivers installed. I had ADB up and running but when I tried fastboot it would not recognize my G2 so I had to install new drivers.
James_Caliber said:
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
Click to expand...
Click to collapse
Take the .img file that you have for CM 3 and rename it to: recovery.img then place it on your sdcard. Open terminal emulator on your phone and type in the following 3 commands, hitting enter after each one:
su
flash_image recovery /sdcard/recovery.img
reboot recovery
If you need a copy of the latest CM 3 (3.0.0.5) you can download it from here:
http://phones.crackflashers.com/vision/recoveries/vision-cwm3src3.0.0.5-1-16-11.img
EdKeys said:
Take the .img file that you have for CM 3 and rename it to: recovery.img then place it on your sdcard. Open terminal emulator on your phone and type in the following 3 commands, hitting enter after each one:
su
flash_image recovery /sdcard/recovery.img
reboot recovery
If you need a copy of the latest CM 3 (3.0.0.5) you can download it from here:
http://phones.crackflashers.com/vision/recoveries/vision-cwm3src3.0.0.5-1-16-11.img
Click to expand...
Click to collapse
If you want to use flash_image, you need to place the binary on your phone and make it executable. The guide I linked to explains exactly what you are supposed to do.
For fastboot, do you have recovery.img in your tools directory?
I've got the same problem as the OP. How do i know if i have hboot? I have s off using the original visionary method. I try to push the image through termimal but it says the image isn't found. I need to do the entire binary method to get the path to work? this is why i want to wait for the update through rom manager, so i can flash back and forth anytime.
sent from my V I S I O N.
PatrickHuey said:
I've got the same problem as the OP. How do i know if i have hboot? I have s off using the original visionary method. I try to push the image through termimal but it says the image isn't found. I need to do the entire binary method to get the path to work? this is why i want to wait for the update through rom manager, so i can flash back and forth anytime.
sent from my V I S I O N.
Click to expand...
Click to collapse
Not exactly sure what you are saying about pushing things through terminal and the binary method, but if you want to use flash_image, you should follow the guide I linked to.
If you want to use flashboot, you need to make sure you have the engineering hboot (if you boot you phone while holding volume down, the first line should say something like ENG S-OFF instead of SHIP S-OFF).
If you want yet another method to flash the recovery, there is also the sticky at the top of this forum.
i found this to be the best and easiest way to flash CWM recovery 3.0.0.5
I found a really easy way to flash the new recovery. My fastboot didnt seem to have an option for a terminal so I thought of this genius yet n00b way. Here are the steps.
Steps:
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
Click to expand...
Click to collapse
If you rooted using rage, the flash_image kernel should be on your phone.
blackknightavalon said:
If you rooted using rage, the flash_image kernel should be on your phone.
Click to expand...
Click to collapse
I don't think that's true. Temp rooting with rage doesn't install any apps for you by itself (and the temp root to perm root guides only install Busybox, SuperUser, and the su binary). It's just that most people flash a custom rom after rooting, and many of those roms include flash_image. If you rooted and then stayed on stock for example though, you would have to get the flash_image program yourself (and it's something independent of the kernel).
I have rooted and installed custom Roms on my wifes KF and mine and it worked flawlessly. So i assumed i could root my co-workers also. (FAIL)
So i loaded up KFU installed TWRP first. stuck on splash screen, conducted a hard reset and then tried to root.Then it stuck on "attempting to remove root checker" Waiting for Device. and reset again.
Now it reboots though FFF boot loader and then again straight to TWRP. After much reading and trial and error i have (i think ) flashed an up date using adb push C:\kfu\software\update.zip\ /sdcard/ line command but the file is not in the sd card parition of twrp
i have identified the boot mode as obviously 5002 recovery should i be in 4002 fastboot for that to work?
this is a two part thread. adb works fine and the kindle is recognized as a device but i am unable to access the files on it.....
just use mount and put this rom on instead http://forum.xda-developers.com/showthread.php?t=1439916 select mount make sure there are no checks in the boxes of system and data then hit the big button transfer this rom (not the alt version) to the sd card but dont put it inside any folder then umount flash it and enjoy.I have seen more people screw up by trying to flash update.zip not always a good idea unless you know what your doing..
Thepooch said:
just use mount and put this rom on instead http://forum.xda-developers.com/showthread.php?t=1439916 select mount make sure there are no checks in the boxes of system and data then hit the big button transfer this rom (not the alt version) to the sd card but dont put it inside any folder then umount flash it and enjoy.I have seen more people screw up by trying to flash update.zip not always a good idea unless you know what your doing..
Click to expand...
Click to collapse
DL zip now could i use the same process to see the file i pushed earlier?
Forgive me i did not read the whole post
it must be in zip form to flash it no need to wipe this is the only rom you do not have to wipe to flash...
this is the command line is used
adb push C:\kfu\softwear\Gr9.2.zip\ /sdcard/
is that correct? i am in fastboot mode now (kindle fire white/blue)
b.king said:
this is the command line is used
adb push C:\kfu\softwear\Gr9.2.zip\ /sdcard/
is that correct? i am in fastboot mode now (kindle fire white/blue)
Click to expand...
Click to collapse
fastboot isnt for flashing roms and if thats the file path where you placed the rom.zip then its right but you dont need to be in fastboot you need to be in twrp to flash the rom you mis spelled software
Thepooch said:
fastboot isnt for flashing roms and if thats the file path where you placed the rom.zip then its right but you dont need to be in fastboot you need to be in twrp to flash the rom you mis spelled software
Click to expand...
Click to collapse
im back in recovery and recieving no such file or directory message i possibly have the wrong path quoted
yes forget the adb stuff just select mount... transfer the rom by simple copy paste to your sd card
Thepooch said:
yes forget the adb stuff just select mount... transfer the rom by simple copy paste to your sd card
Click to expand...
Click to collapse
i am unable to view my folders in the kindle for some reason it is visable under devices but i cannot access the files or i would done that already
try reinstalling the drivers that came with kfu
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
also the easiest way to set the correct file path is to type
Code:
adb push
then drag drop the file to the terminal this will place the file path then add /sdcard
---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------
sent you a message
b.king said:
i am unable to view my folders in the kindle for some reason it is visable under devices but i cannot access the files or i would done that already
Click to expand...
Click to collapse
BIG THANKS ThePooch
mounted the sd card to pc loaded files and i am rooted with a custom rom!!!
very good your set next time you go to recovery perform a backup as well as remember this is the only rom you can flash without wiping... next one you will need to wipe factory reset,cache,dalvik and system.... of course all after a backup...
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.
So i combed through the threads and either i missed it or it was removed but i'll ask anyways. So, BND-L24 with unlocked bootloader, no root, no twrp installed. How do I go about backing up my stock files. I tried booting into the twrp image through fastboot and it kept saying "remote connection not allowed" or something along that line. I'd like to back up everything including the stock recoveries and have something to fall back on in the event that something goes not to my liking. So what options do i have as far as this goes? Backup through a booted (not flashed) TWRP, backup through ADB commands? Any knowledge would be appreciated.
Here's a backup .bat file.
May want to try flashing TWRP instead of booting
You need to ADB while in TWRP, make sure you have a microSD card installed.
Its just a $ shell
https://drive.google.com/open?id=1AkZ0s7FIa8vvgQwGOiDaAEuaixNGDWEl
tlxxxsracer said:
Here's a backup .bat file.
May want to try flashing TWRP instead of booting
You need to ADB while in TWRP, make sure you have a microSD card installed.
Its just a $ shell
https://drive.google.com/open?id=1AkZ0s7FIa8vvgQwGOiDaAEuaixNGDWEl
Click to expand...
Click to collapse
But if I flash twrp, I won't be able to backup the stock recovery correct? So if something goes wrong down the line I won't be able to revert back to compete stock or install ota updates
boot into twrp dont flash, that way stock recovery isnt touched
tlxxxsracer said:
boot into twrp dont flash, that way stock recovery isnt touched
Click to expand...
Click to collapse
That's what I was attempting do but it wouldn't boot into it. It kept saying failed. I think I tried two different versions of twrp that are posted. Is there a different command line besides "fastboot boot twrp.img" that I need to be using? Or am I missing something else? I unlocked the bootloader and it is showing up in "fastboot devices" I moved the recovery image into the adb folder and renamed it twrp.img. Should've been pretty straight forward, never had problems with adb before
str8stryk3r said:
That's what I was attempting do but it wouldn't boot into it. It kept saying failed. I think I tried two different versions of twrp that are posted. Is there a different command line besides "fastboot boot twrp.img" that I need to be using? Or am I missing something else? I unlocked the bootloader and it is showing up in "fastboot devices" I moved the recovery image into the adb folder and renamed it twrp.img. Should've been pretty straight forward, never had problems with adb before
Click to expand...
Click to collapse
Hey OP were you able to figure this out?
mjtschmid said:
Hey OP were you able to figure this out?
Click to expand...
Click to collapse
Nah man. I thought about doing the no twrp install root method posted but decided against it because the twrp available isn't 100% made for our phone. And I keep reading they disabled "fastboot boot" command. I'm gonna hold off until they release the stock firmware did the L24 before I did into root and twrp
Well I can tell you I followed the steps for backup and took it for granted that it worked. Turns out my system.img and userdata.img we're 0 bytes. If someone has done it successfully I would appreciate if they posted their system.img for BND-L24
i'm not 100% sure but i think in order to boot twrp using "fastboot boot" command you have to specify, according to "fastboot help" , it's something like "fastboot [kernel] [ramdisk] boot [xxx.img]" and in other posts i see it being written as "fastboot -c "lge.kcal=0|0|0|x" boot <path to recover.img>" but i'm not sure which device that's for. i don't mess with adb and fastboot enough to know what's going on in there. maybe one of you guys can figure it out.
How do I find a post #??I was told to look at ..... .....post # but how do I find this???