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!
Related
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2
JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.
RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.
Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars
Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps
If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.
mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.
Then just use the sideload, it works quite well for me.
mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.
No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement
stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone
hi all
I have a problem on getting TWRP to work properly.
I initially used BreakDroid to install TWRP, everything worked fine.
I tried to install the cm-11-20140512.1655-SKANKY-otter.zip OS but I first got the "error 7", fixed that, and then it was stuck at "updating package" (or similar)....
then I saw an updated version of TWRP, without realizing that it was for an asys TF101 tablet (http://forum.xda-developers.com/showthread.php?t=2434422)...I installed that and now twrp doesn't work because the screen is the wrong size and I can't get to various buttons including flash/wipe etc..
I can still mount it tho so I thought about using adb/flashboot...but I can't seem to override that version of TWRP.
...best part...i cannot restore the original amazon OS since I didn't do a backup (...i know...:angel
does anyone have any idea about how I can fix that and install a kitkat rom?
I have nandroid backup of stock in my list.
sd_shadow's collection of links for: Kindle Fire 1
Sent from my Amazon Kindle Fire using Tapatalk
sd_shadow said:
I have nandroid backup of stock in my list.
Click to expand...
Click to collapse
thanks for the reply.
I did look at it but my problem is that I don't need to backup the system, I need to be able to install a recovery tool (twrp or cwmr) that will allow me to flash a rom on my kindle.
my problem now is that I can't seem to be able to do that since the recovery I have is for a different tablet and the screen won't allow me to get to the right buttons...I can only turn the kindle on and off .
SbDROID2012 said:
thanks for the reply.
I did look at it but my problem is that I don't need to backup the system, I need to be able to install a recovery tool (twrp or cwmr) that will allow me to flash a rom on my kindle.
my problem now is that I can't seem to be able to do that since the recovery I have is for a different tablet and the screen won't allow me to get to the right buttons...I can only turn the kindle on and off .
Click to expand...
Click to collapse
you tried
with kindle fire in twrp, connected to mac
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.6.3.1-otter.img
fastboot reboot
I don't have a mac, so commands might not be quite right
may want to read [GUIDE] Set up ADB and Fastboot on a Mac easily
and you will need openrecovery-twrp-2.6.3.1-otter.img
sd_shadow said:
you tried
with kindle fire in twrp, connected to mac
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.6.3.1-otter.img
fastboot reboot
I don't have a mac, so commands might not be quite right
may want to read [GUIDE] Set up ADB and Fastboot on a Mac easily
and you will need openrecovery-twrp-2.6.3.1-otter.img
Click to expand...
Click to collapse
I did try to do that but
1)
adb shell
Click to expand...
Click to collapse
--> doesn't work and I get "error: device not found"
i did the "./android update adb" with "adb kill-server" and "adb start-server" but nothing changed..
2) I installed the img file anyway through
fastboot flash recovery
Click to expand...
Click to collapse
the img file but i still cannot get the twrp with the view for kindle...see attached image. i have NO ACCESS to some of the buttons, therefore I can't do much with it.
I would REALLY like to be able to install a CWM...i tried the one here http://forum.xda-developers.com/showthread.php?t=1454241 using
fastboot flash recovery cwm-file-here.img
Click to expand...
Click to collapse
but it gets to the boot page, I select "recovery" and then it's stuck with the kindle logo and the small "booting..." at the bottom of the screen...so I re-installed twrp even tho i still have that damn "build for Asus TF101 Series Tablets" (see attachment) warning on top!!
any help would be HUGELY appreciated!!
also, using "adb devices" I still can't see it.
Run this command from your computer with your kindle connected when you turn it on:
fastboot getvar product
The FFF bootloader temporarily enables fastboot as the device boots up. When you issue this command, it puts the device into permanent fastboot mode. Just flash the correct recovery after that:
fastboot -i 0x1949 flash recovery your-recovery.img
fastboot reboot
Duchman said:
Run this command from your computer with your kindle connected when you turn it on:
fastboot getvar product
The FFF bootloader temporarily enables fastboot as the device boots up. When you issue this command, it puts the device into permanent fastboot mode. Just flash the correct recovery after that:
fastboot -i 0x1949 flash recovery your-recovery.img
fastboot reboot
Click to expand...
Click to collapse
ok...that doesn't work...
I get the same problem, if I download the correct twrp from here http://teamw.in/project/twrp2/79 I get exactly the same screenshot I posted above..
and the cwm recovery is not available anymore so I don't really know how to fix this...without working recovery I can't install any rom!!
SbDROID2012 said:
ok...that doesn't work...
I get the same problem, if I download the correct twrp from here http://teamw.in/project/twrp2/79 I get exactly the same screenshot I posted above..
and the cwm recovery is not available anymore so I don't really know how to fix this...without working recovery I can't install any rom!!
Click to expand...
Click to collapse
When you are flashing TWRP image in bootloader/fastboot do you see sending ... writing... in command prompt?
like this?
sd_shadow said:
When you are flashing TWRP image in bootloader/fastboot do you see sending ... writing... in command prompt?
like this?
Click to expand...
Click to collapse
When I launch the fastboot flash in fastboot mode I do get nothing but the blank cursor on a new line, although I see the device with "fastboot devices". After a few min that was stuck then I turned it off and the first part came up saying " sending file" but then it gave me an error saying that the connection was lost...which makes sense cause i turned it off..
If instead I launch the command and THEN turn the kindle on it does show me the correct output in a couple of secs as your showed. But then even if I do fastboot reboot, it does reboot it but no correct recovery is loaded...still the wrong screen size... Very very frustrating...
And btw...thanks for bearing with me through this!!!
---edit---
Now that I think about it...the twrp screen, although the wring size, actually reflects the VERSION of twrp that I'm installing through fastboot...it's as if the twrp I got from here ( http://forum.xda-developers.com/showthread.php?t=2434422) controls the size of the screen while I'm able to change the version of twrp...I think that that is a recovery GUI for the Asus tablet, any idea if I can install another GUI?...hopefully this helps...
SbDROID2012 said:
When I launch the fastboot flash in fastboot mode I do get nothing but the blank cursor on a new line, although I see the device with "fastboot devices". After a few min that was stuck then I turned it off and the first part came up saying " sending file" but then it gave me an error saying that the connection was lost...which makes sense cause i turned it off..
If instead I launch the command and THEN turn the kindle on it does show me the correct output in a couple of secs as your showed. But then even if I do fastboot reboot, it does reboot it but no correct recovery is loaded...still the wrong screen size... Very very frustrating...
And btw...thanks for bearing with me through this!!!
---edit---
Now that I think about it...the twrp screen, although the wring size, actually reflects the VERSION of twrp that I'm installing through fastboot...it's as if the twrp I got from here ( http://forum.xda-developers.com/showthread.php?t=2434422) controls the size of the screen while I'm able to change the version of twrp...I think that that is a recovery GUI for the Asus tablet, any idea if I can install another GUI?...hopefully this helps...
Click to expand...
Click to collapse
Your guess is right, installing another TWRP version doesn't affect the theme you are using, unless it has a theme of its own. You could delete the ui.zip from the TWRP folder and that would solve it. The folder should be in sdcard.
Duchman said:
Your guess is right, installing another TWRP version doesn't affect the theme you are using, unless it has a theme of its own. You could delete the ui.zip from the TWRP folder and that would solve it. The folder should be in sdcard.
Click to expand...
Click to collapse
so..the problem with that is that I could not access the sdcard since adb doesn't work...however...as of now I've been able to fix the layout problem by using
fastboot -w
fastboot flash recovery twrp.2.7.0.1.img
fastboot reboot
Click to expand...
Click to collapse
once rebooting I had to re-wipe (advance wipe) sdcard/cache/data since when I tried to mount them I could not check the boxes.
now i STILL cannot mount it and adb does not recognize it.
I'm using mac and I tried
android update adb
Click to expand...
Click to collapse
but still adb can't see the kindle and I can't mount it through twrp
...however, I'm still able to reboot in bootloader and use fastboot
I don't think I can flash a .zip rom from fastboot tho...and I'm not sure how to transfer files on the kindle to flash them from twrp...any idea?
thanks a ton!!
-- edit --
i already modified the ~/.android/adb_usb.ini file adding 0×1949 and then running
adb kill-server
adb devices
but what I get is just
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
and nothing to it...the "adb shell" still gives me "device not found"!!
try flashing Cannibal Open Touch Recovery see http://forum.xda-developers.com/showthread.php?t=2025793
links are bad so uploaded my copy to http://d-h.st/XWy
sd_shadow said:
try flashing Cannibal Open Touch Recovery see http://forum.xda-developers.com/showthread.php?t=2025793
links are bad so uploaded my copy to http://d-h.st/XWy
Click to expand...
Click to collapse
SCORE !!!
dunno why twrp was the problem! the new recovery that you linked worked like magic, adb worked perfectly, I already flashed a rom and it works!!
so...why wouldn't twrp allow me to use adb or mount disks through usb?!
thanks so much for the help!!
Guessing it doesn't use the twrp theme, that was causing trouble.
Sent from my Amazon OtterX using Tapatalk
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.
Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..
Which guide did you use to do all of this? I will help us understand where you started
Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot
Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.
Hi.
So I was messing around with the twrp custom recovery and (without thinking much of it) wiped everything in the advanced wipe menu :crying: (System, data, EVERYTHING)
I knew I had removed my OS and that I could just use the twrp recovery to install a new rom onto my phone BUT little did I know, when I tried to boot into the custom recovery, it would just loop the screen with the redmi logo
I am still able to boot into fastboot mode, and I have tried to flash the same twrp recovery but with no avail (It still loops the redmi logo screen)
So now I'm here to ask if there is any advice that you could give me to try and fix this problem that I have gotten myself in (I am not worried about deleting any of my personal files. I would just like to get twrp to boot so that I can install another rom)
Thanks in advance to anyone who can help me with this problem :highfive:
Hi, which rom are you trying to install? for android 9 use this recovery https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397, for android 10 this one... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7...
If what nuvulet said doesn't work, in fastboot, flash the exact same stock ROM you had before, let it boot and then flash TWRP.
nuvulet said:
Hi, which rom are you trying to install? for android 9 use this recovery https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397, for android 10 this one... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7...
Click to expand...
Click to collapse
Hi, thanks for the fast reply.
The stock android I had before I wiped everything was android 9, MIUI 11. I tried againt to flash the recovery through fast boot but (like before) when I try to boot into the recovery (by holding the volume up button as it reboots), the redmi logo keeps appearing and disappearing and doesn't go to the twrp recovery. At the current moment I don't have any OS installed (since it got deleted when I wiped everything)
Any other leads I could try?
wang1chung said:
If what nuvulet said doesn't work, in fastboot, flash the exact same stock ROM you had before, let it boot and then flash TWRP.
Click to expand...
Click to collapse
I'm not sure how I can flash the stock ROM without the twrp recovery. I had the impression that you needed twrp recovery in order to install ROMs in the first place.
If there is a method to flash a ROM using fastboot, please explain since my unexperienced self has no idea how to do this. :laugh:
Thanks for the fast reply too
Sqorpz said:
I'm not sure how I can flash the stock ROM without the twrp recovery. I had the impression that you needed twrp recovery in order to install ROMs in the first place.
If there is a method to flash a ROM using fastboot, please explain since my unexperienced self has no idea how to do this. :laugh:
Thanks for the fast reply too
Click to expand...
Click to collapse
MiFlash works through fastboot mode. It's also safer to flash with MiFlash, just make sure you have the correct ROM.
I can't find the guide right now, I'm at work
Ok, do you know adb fastboot... if not, follow this guide...
https://forum.xda-developers.com/showthread.php?t=2317790
Install usb adb drivers for RN8P if you don't have, try this for w10...
https://forum.xda-developers.com/redmi-note-8-pro/help/usb-drivers-t4035617
Download twrp for android 9 or android 10 from here...
https://forum.xda-developers.com/showpost.php?p=82115341&postcount=2
Put the recovery (*.img format) into installed adb folder...
Open cmd and navigate to inside adb folder...
Put the phone into fastboot mode (press volume- and power) connect usb and type in console...
adb devices (this start adb server)
Type...
fastboot devices (this return a device number, if not, something is wrong)
Type...
fastboot flash recovery *.img (change * for the name of the recovery file)
Disconnect the phone and press volume+ and power at the same time and now you have twrp intalled...
When start if the data is encrypted, push cancel, go to wipe, go to format data, type "yes", and confirm slide...
Now connect the phone to usb (if not recognize the phone, go to mount, and enable MTP)
Copy the rom in to internal storage for your android twrp version... search here
https://forum.xda-developers.com/redmi-note-8-pro/how-to/redmi-note-8-pro-android-10-public-t4072795
You have several versions... for eu, search in my post...
And the rest, install, select, etc. etc....
nuvulet said:
Ok, do you know adb fastboot... if not, follow this guide...
https://forum.xda-developers.com/showthread.php?t=2317790
Install usb adb drivers for RN8P if you don't have, try this for w10...
https://forum.xda-developers.com/redmi-note-8-pro/help/usb-drivers-t4035617
Download twrp for android 9 or android 10 from here...
https://forum.xda-developers.com/showpost.php?p=82115341&postcount=2
Put the recovery (*.img format) into installed adb folder...
Open cmd and navigate to inside adb folder...
Put the phone into fastboot mode (press volume- and power) connect usb and type in console...
adb devices (this start adb server)
Type...
fastboot devices (this return a device number, if not, something is wrong)
Type...
fastboot flash recovery *.img (change * for the name of the recovery file)
Disconnect the phone and press volume+ and power at the same time and now you have twrp intalled...
When start if the data is encrypted, push cancel, go to wipe, go to format data, type "yes", and confirm slide...
Now connect the phone to usb (if not recognize the phone, go to mount, and enable MTP)
Copy the rom in to internal storage for your android twrp version... search here
https://forum.xda-developers.com/redmi-note-8-pro/how-to/redmi-note-8-pro-android-10-public-t4072795
You have several versions... for eu, search in my post...
And the rest, install, select, etc. etc....
Click to expand...
Click to collapse
Yes, this is the method I used to flash the twrp recovery.
My problem was that even after installing it (using this method), i would still not be able to boot into the recovery.
However, it is fixed now. I used the Mi Flash tool in order to install the stock rom and then installed twrp after that. :good:
wang1chung said:
MiFlash works through fastboot mode. It's also safer to flash with MiFlash, just make sure you have the correct ROM.
I can't find the guide right now, I'm at work
Click to expand...
Click to collapse
I tried this method and IT WORKED!!
After installing Mi flash I was able to download the stock rom and install it through the program without any errors.
I was then able to finally boot into the OS and install twrp recovery, then install the custom rom! :laugh:
Thanks for this method. I would probably still be stuck on the Redmi logo if it weren't for this