Related
Hi
I have been using Clockwork recovery for months and tonight was flashing ROM/zips as usual, and all of a sudden when I try to get into recovery my Nexus just sits on the colored X. When I pull the battery it reboots fine with the ROM I currently have installed. Then I go back into ROM manager, re-flash clockwork recovery: it says flash was successful, so then I choose to boot into recovery, and again it just sits at the blue, red, green and yellow X.
So then I tried a round-about way by going into ROM manager and choosing to restore a backup. Again, when I choose to restore backup it just boots to the colored X again and freezes there.
I've also tried the regular method of holding power button and trackball and get the same results.
Does anyone know why this might be happening? Right now I'm stuck with a ROM I was just playing with and didn't necessarily want to use permanently....I'm afraid I might be stuck with it forever now
Thanks for any help!!!
I've been searching and I should add that my bootloader is not unlocked
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Jack_R1 said:
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Click to expand...
Click to collapse
Well I ended up wiping all user data in fastboot and now I get nothing but an X nomatter what I do, won't boot at all.
All I can do is hold down the power button and trackball and get the page that says
bootloader
reboot
reboot bootloader
power down
the only way I'm going to get this fixed is to use my computer and I've never done it that way...I've always used ROM manager
I'll read the links but I think I'm screwed because a lot of this is over my head
Thanks for the links !
1) Try to follow "Unroot/restore" guide first, see if you can restore functionality using PASSIMG method. Once you have functional FRG33 with recovery, you can root it, replace the recovery and install custom ROM of your choice / update to FRG83G.
2) If nothing helps - consider a) replacing your phone, b) unlocking the bootloader and flashing recovery through fastboot.
Getting in over your head is sometimes a good way to expand your horizons
Hi Jack
Thanks for the help
I'll do some reading and see what I can do....got two feet of snow here so I guess I have the time
worst comes to worst I'm still under warranty.
Well I tried the instructions but nothing happens..it just sits on the screen with the androids skateboarding. I renamed the zip and moved it to my SD card but it doesn't seem to even search for it, let alone find it. Really wish I had not deleted storage. At least I had a working ROM at that point.
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Jack_R1 said:
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Click to expand...
Click to collapse
Hey Jack...
Sorry for taking so long to respond...I finally had to crash for awhile, my brain was frying.
Yes I did what you describe: downloaded FRG33, renamed it PASSIMG.ZIP(not ZIP.ZIP) moved it to SD card just like any ROM and held down volume and power button and came to the screen with the three androids. Then it just stayed there, nothing happened.
The only thing is I had to use my backup Nexus One(EDGE only on ATT model) to move it to the SD card as I don't know how to access the SD card with the device acting like this. If I connect the device to my computer while the three androids are on the screen, I hear it connect to the computer, but nothing pops up allowing me to access the SD card....
Like I said I'm a noob at this I appreciate you trying to help me here
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Rusty! said:
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Click to expand...
Click to collapse
Hi Rusty
Sorry I somehow missed your post here. Yes I see some text flash up...takes a little longer than 3 seconds...maybe 8 seconds...
At first it says I'm in Fastboot, but then I press the power button and then it says HBOOT at the top.....that's when the text flashes on the screen. It flashes too fast for me to read it though....but nothing happens after the text flashes on the screen.
I'll be damned guys....I got it working! After responding to Rusty's post above, I decided to give the whole thing another try. Well I went thru the whole process of putting the file on the SD card and realized I had in fact renamed it zip.zip....it LOOKED like it was only ZIP, but when I clicked on the file while it was still on my PC, it said it was zip.zip...that's when I knew what the problem was.
My problem now is getting it re-rooted. Originally I used the Universal Androot application..the true one-click method...I just tried it again and it didn't work.
Is there a way to downgrade to a version where this app will work again?
Thanks guys you really helped me out here!!
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Jack_R1 said:
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Click to expand...
Click to collapse
Yup I'm already rooted!!! Thanks man!!!! Took 12 minutes!!
Okay I'm having another issue: SuperOneClick said I was rooted,I have the superuser icon in my app drawer, but ROM manager will not flash Clockwork mod recovery and Titanium Backup says I do not have root rights??
well I rebooted and now have root rights but am still getting an error when I try and flash clockwork mod: it says: "an error occurred while flashing your recovery"
Do you have Busybox installed?
Jack_R1 said:
Do you have Busybox installed?
Click to expand...
Click to collapse
You're going to think I'm a dip**** but I don't even know what busybox is?
Let's just say it's an app that the system needs Go to Market, download and install it, try again. If it doesn't work - you can try to install custom recovery manually, using another guide from Wiki. Look in "Installing Recovery" for "For locked bootloader - flash_image using Terminal" guide. If you don't know what Terminal is - download "Android Terminal" by Jack Palevich from the Market.
Use the fix problems button in Titanium Backup to install it, long story short is it lets you use a bunch of native Linux commands that as missing from Android.
[SOLVED -- Read my last post]
Posting on forum was my last resource, but I've tried literately almost everything I can possible find.
I already bricked my phone and had to unbrick, do everything (update firmware etc) all over again.
I am at a point where I am afraid to do something new to my phone now without knowing what they are...
Please bare with me, I am not familiar with exactly what flashing is or whatnot, I just followed the instructions and got where I am....
K, recently I decided to wipe my phone CLEAN and update to new CyanogenMod 9 from factory mode.
So, I have Captivate, I897. It was ECLARE with 2.1 firmware.
I have updated to 2.3.5 (Gingerbread [I897UCKJ2]), Rooted.
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
I installed Clockwork mod (Free version).
My goal is to install CyanogenMod 9, and part of the process requires me to enter the CMW Recovery Mod.
I dont even know what this looks like, but all I know is whenever I boot my phone, after the AT&T logo animation it seems to go into this "messed up" screen, where as if my phone is broken. Stays there for 3 seconds and then continues to boot back to its OS.
In ROM manager, it says Flash ClockworkMod Recovery (You must have the clockworkmod recovery installed to flash and restore ROMs!)
Another option within ROM manager is, Reboot into Recovery (Boot into Recovery mode for manual management.), which if I do access it, it takes me back to that AT&T logo animation and that "messed up" screen again, but this time it stays there. Where all kinds of colored pixels are on my screen as if my screen is broken. It will only continue to boot back to my OS if I press power button or some sort.
Im guessing that's my Recovery Mod, which my phone for some reason cannot see?
So I tried "Download ROM (Upgrade to ROM Manager (premium) to access the full list of ROMs!", hoping this may cure that messed up screen effect, which I think is the Recovery Mod for all I know... When I click to install, it gives me Confirm Phone Models. None are my phone model for me to install.. (It only gives me Google Nexus S / Google Nexus S 4G / Samsung Epic4G / Samsung GalaxyS i9000).
Earlier, I was looking at this, http://forum.xda-developers.com/showthread.php?t=1127578
which is a way to fix recovery mod(?) But I have NO idea how to even install those files... Maybe not the .tar file but the other one.
Please help? Am I the only one experiencing this kind of problem? Couldnt find anywhere else on youtube / google / forum..
Thank you VERY much in advance, really appreciate it..
-Dan.
danroh said:
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
-Dan.
Click to expand...
Click to collapse
This is your likely problem right here. The Kernel that is installed during the rooting process and typically when you install custom roms is what is responsible for installing and therefor you being able to access the CWM recovery. Flashing back to the stock kernel likely messed things up for you.
http://forum.xda-developers.com/showthread.php?t=1300843
Now if you follow that link it will take you to several one click options for flashing your phone to stock gingerbread but with a kernel containing CWM. Also keep in mind that it is possible you could have wifi issues if you've had them in the past, but if your goal is to get to CM9 just ignore the wifi for the time it shouldn't be an isuse in the end.
Hey OP,
See this.... TRusselo's Flashing Guide
Sent from my SAMSUNG-SGH-I897 using xda premium
You need Gingerbread bootloaders.
Thanks guys! I figured out the problem and solved it!
Like you guys said, I didnt have the bootloader. The gingerbread I installed was the no bootloader version. After reinstalling to the one with bootloader, I was able to access the recovery mod and that "rainbow screen" glitch was no more.
Thank you!
I can't seem to figure out how to enter into recovery mode on my T-Mobile G4. It's running everything completely stock. I have tried holding power button and volume up until the logo comes on and releasing both buttons and then immediately holding them both down again waiting.. and nothing happens. I've even tried waiting for one second after I initially release to hold them down again. Same outcome. It always just boots back up into Android. I have tried volume down instead.. Nothing. Can someone please show me how to boot into recovery mode? Again, running stock rom.
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Demati said:
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Click to expand...
Click to collapse
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
From the T-mobile website: https://support.t-mobile.com/docs/DOC-21911
stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
That's not what I'm talking about. That's talking about factory resetting your phone with the hardware keys. I'm talking about entering recovery mode (kinda like the bios of the phone) using the hardware keys.. It's different.
Demati said:
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
Click to expand...
Click to collapse
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
stringz90 said:
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
Click to expand...
Click to collapse
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Demati said:
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Click to expand...
Click to collapse
Alright.. I guess, I'll have to try that, but first is there any way to do a backup of some sort in case I have to go back to stock rom rooted? I got my G4 about a month ago and haven't done much research on rooting this specific device. I haven't had a high end phone with rooting and rom options in a long time. The last phone I had a chance to root and install cool custom roms on was a Samsung Galaxy S2. If you can guide me in the right direction I'd appreciate it. I guess I have to start from square one again. In the past I remember that in order to go back to completely stock you had to have a usb jib to reset the flash counter. Is it the same for this case? I welcome anyone's helpful input. Thanks, everyone.
DISCLAIMER: I'm as always, not responsible for any bricks, damages to your device, or any other "bad" effect this guide may or may not have on your device. Also doing this voids your warranty. ALSO... please read the "common mistakes" section at the bottom of the post. Good luck!
Checked/Updated: November 18th, 2017, all the links check out, I've logged into my old MEGA account to keep them alive. Cheers everyone
NOTE* VERY IMPORTANT! Don't bother installing this without installing android! Why? Every time you reboot with the stock OS, it erases the recovery. At least on 8.5.1. After installing the recovery, IMMEDIATELY power off your device, boot into recovery manually, and install android. Never, I repeat NEVER use fire flash to reboot into recovery, it will soft brick your device, which you need a computer to fix.
NOTE2* I did not create any of these files, I simply put them all in one place and kept them in my mega drive (I never use it so the links should be good for a while
It's rooting time guys!
iroot.apk : https://mega.nz/#!0Z0AFB7b!LgIwouIzy6IYPFEVpKdL7fkWTWdEKJX-gV00mwXXYrE
So, now that you have iroot downloaded, go ahead and install it. Now open it and you should see your device (KFJWI) at the top, and a big button in the center. Tap it, and it will begin rooting your device. (Don't interrupt it!). When it's finished, reboot your kindle, and you should now be rooted! You'll find an app called "King User" in your device apps, it just manages root (like Super SU) and is needed to use root. Now for TWRP!
So here's the VERY STRAIGHT-FORWARD tutorial for people who's kindle fire 8.9s are on Fire OS 8.5.1 and want TWRP and Maybe even Cyanogenmod/Android running on their kindle. Anyway, let's start with fire flash, you've probably heard of this before, but all I'm really doing here is summarizing other guides and my personal experience for others to utilize (no matter what skill level)
1) Anyway, download FireFlash11 apk (it's trustworthy, worked no problem for me)
DOWNLOAD HERE: https://mega.nz/#!MIM1hbQJ!4hCcH3o3w7ZdrQylcMG0Gt-F0Kju_w_IHs8q0Pe44ng
2) Now download ALL these files. (I know one says "freedom-boot-8.4.6" It will work on 8.5.1!)
ES File Explorer (Download from app store, if unable to, download through MEGA and install from silk): https://mega.nz/#!hR1EzbiR!RSEy0wiVBadAaWDF3SGnd5CQAMcaUo8aDQlIvqEGF6U
freedom-boot-8.4.6: https://mega.nz/#!tRlDxYwK!tje6Mfa08YBTYubLvHPtn_kpakc6woBJfUpM70RTsV4
u-boot-prod-8.1.4: https://mega.nz/#!BV0V2TiS!39szFTM57OV9Pby_R88t-xeAL9nu5ouwgXv96NmfsSk
TWRP 2.6.0.0: https://mega.nz/#!ABUiAbrI!IManKhn6prbjBCyThY_33uw7wftvqxpqXXqzDx3qSGA
(TWRP because of stability and ease of use, CWM and newer builds of TWRP are available around the community but 2.6.x.x should work fine for most pre-6.0 roms)
stack: https://mega.nz/#!oBtSDIZL!WnsanHgEieY7JzeOJPRC2XnQOkrN3O7ZyDZU01-Z_eA
3) I know those links looked the same, there different, now bear with me here, here comes the TWRP install.
so, First, make sure you've downloaded and installed ES File Explorer (if through silk, open the downloads tab and install it through there) and open it. now, if you haven't already, make sure you move all the files you downloaded to your kindle. now if you moved them straight to your kindle, then they should be on the sd card, if you downloaded these through silk, they'll be in the downloads folder in your sd card. tap and install fireflash11.apk . now open it, and give it root access. you should be greeted with a somewhat complicated looking wall of text and checkboxes.
!IMPORTANT!
| | |
\/ \/ \/
*So, let me now guide you through this app, first of all, there should be red print informing you that you're not on the 8.1.4 bootloader or something like that, so click on the checkbox. above it (the one that says "install kfhd8uboot-prod-8.1.4.img or something like that)
*Now go down, and you'll see some text that says "Boot Partition Image (boot.img) and a box under it that says "NOT FLASHED" tap it. it should bring up a file manager-like list. scroll down until you see your already downloaded "kfhd8freedom-boot-8.4.6.img" , and tap/select it. (I know it says 8.4.6, IT WORKS ON 8.5.1!).
now go slightly under it and check "apply stack override".
*Next, Go under that to find a line that says "Recover Partition Image (Recovery.img), and slightly under it a box that says "NOT FLASHED" tap that, and again, you'll be greeted with a list-like file manager. scroll down until you see "kfhd8-twrp-2.6.0.0.img" and tap/select it. last part! go slightly under that and tap the check box next to "disable auto recovery update".
*Now that you have all you options in order, verify that you have them in order, and correctly selected (refer back if needed) and scroll down until you see at the bottom, a box that will install/flash all these things, it will say something like "Execute Flash Script" tap it, and your all set. if you want to boot into recovery, go right under that box to find another box that says "reboot into recovery" click it, and wait a sec, your screen will black out, and you will first see the normal kindle fire logo, then a blue one, then some glitchy looking stuff, then it should show a TeamWin logo, and go into recovery.
NOTE: If you don't flash your device with android, the stock Amazon os will erase the recovery, so NEVER REBOOT INTO RECOVERY USING FIREFLASH! Only right after you install/re-install recovery.
Now you have to download a custom firmware file for your kindle. They com in .zip format, and are all over the 8.9 HD android development forum (which is where this thread is!). Download two, one that you want, and one as a backup just in case things go bad! (make sure the backup one is a lower android version and is stable, such as CM11).
4) Now, to install these:
first off, open ES file explorer, go to the tool section (located to the left of the screen) and open it
enable root explorer (a window should pop up choose to allow it to use root)
Next, create a folder on your sd card named "0" just the zero! no quotations, no space, or a period, just ZERO!
Then, move the ROM and gapps from the download folder in your sd card to the new folder named "0" (that should be on your sd card!)
!IMPORTANT!
MAKE SURE TO CHARGE YOUR DEVICE TO AT LEAST 70% BEFORE MOVING FORWARD
(This is just in case you end up needing to fix or unbrick your kindle fire, the more battery life you have, the more time you have to fix things)
!IMPORTANT!
(Question: why are we doing this? TWRP and nonstock (nonamazon os roms) create a subfolder in your sd card labeled "0", which will be used from here on out (or until you go back to amazon os)
Now, boot into TWRP, power down your device RIGHT AFTER installing/re-installing TWRP through fire flash. Now, with your kindle powered off, push the power button for 3 seconds, release it, and hold volume up until it boots into recovery.
*Make a backup of your ROM, should be in the "Backup" section of TWRP.
*Now go back to the main screen select "Wipe"
*Go to "Wipe Data and Factory Reset"
*Now select "wipe" (its a tab you pull, kind of like the gingerbread or iOS6 lockscreen)
*Now go back (don't reboot your device just yet!)
*Now select "Install" on the main menu (It might say "Zip Install" based on your version of TWRP)
*Now select your ROM (if it's not in the scroll menu, check the right side of the screen! )
*Now click "Install" or "Flash" (again, depends on version of TWRP)
*It may show errors, (like: failed to mount dev/boot0/blah blah blah)ignore them, it only matters if it finishes and says FAILED in all red.
*When it's done tap "Reboot Device"
(You forgot to move your rom/gapps and/or you're stuck with a device with no firmware? help with this question and more at the bottom of the page!)
*DONE!!!! remember, all roms/gapps/zips get flashed like this, including the google ones, but only wipe your device when installing A NEW ROM! not gapps, just go straight to installing them.
Okay, common mistakes:
1. Trying to boot into recovery and getting a badi: bad boot image magic error, then trying to use fire flash or an app like it to boot into recovery. THIS WILL BRICK YOUR KINDLE. It'll red screen, then dump you into fast boot.
2. Using kindle fire 7 in images. Please don't make this mistake. needless to say, THIS WILL BRICK YOU DEVICE.
3.Using non-kindle fire 8.9 roms. You'd be surprised, I had a friend try to flash a ROM for the original kindle fire onto his HD 7 (Tate) kindle fire, so don't flash it unless it specifically says: "for kindle fire 8.9". THIS MISTAKE WILL SERIOUSLY BRICK YOU! Obviously.
*disclaimer: I did not make any of these files, the majority of the credit goes the Hashcode and the wonderful devs on the kindle fire community!
Common questions, with helpful answers!
Q: I forgot to make a backup and I can't find the ROM files I downloaded! what do I do!!!
A: Okay, no big deal! lets do this! in recovery open the install menu (big button that says install) now to the left is all the folders in the sd card (the "0" folder in it anyways) select "Up A Level" now, scroll around until you find a folder named "data" (should be third from the top) next, scroll down until you find a folder named "media" open it. congrats! This is where the actual sd card is! (And if you look you'll find the folder named "0")! now just navigate to the downloads folder (or an incorrectly named "0" folder/wherever you put it) select it, and install!
Q: Where did my recovery go?
A: you either deleted it or rebooted into Stock Amazon OS 8.5.1+ after installing this. Just reinstall it using fire flash, and reflash CM or Omni or whatever you use.
Q: What does Badi: Bad boot image (or similar) mean? And why does it happen every time I try to boot into recovery?
A: It means Amazon erased your rec
4. My kindle fire won't stop booting over and over again! Why? Soft brick. No big deal, flash a different custom ROM (preferably of a lower android version like 4.4.x or lower) and see if that helps. If it is still doing this update TWRPovery at boot, this error is SPECIFFICALY because of Amazon OS doing this. reflash recovery, and remember, ONLY boot into recovery manually, never use fire flash to do it.
Q: Dangit! I forgot to download a ROM for my kindle! Now I'm stuck with a firmware-less kindle fire! What do I do?
A: You will need to boot into TWRP, and tap Mount, now mount internal SD and connect it to a computer, and move a rom to it.
Can Not get Root access, Fireflash will close.?
wopspeed said:
Can Not get Root access, Fireflash will close.?
Click to expand...
Click to collapse
Don't worry Watson, I'm working on getting iroot apk set up. In the mean time, please, when you are rooted, only boot into recovery using volume key up, NOT fire flash. The system will erase twerp after reboot... Even with disable auto recovery update. Just a quirk of Amazon os. Looking into it. Should have a useable iroot by tomorrow though.
Sent from my iPhone using Tapatalk
wopspeed said:
Can Not get Root access, Fireflash will close.?
Click to expand...
Click to collapse
Okay, here is your solution (should be in the guide now, but here's iroot.apk!
https://drive.google.com/open?id=0B-JbG8_ys1PGc3ZKTDQtSmtKOHM
Sent from my iPhone using Tapatalk
When I open iroot, I do not see my device at the top. There is a circle in the middle that says "No Root Permission" and a button at the bottom that says "Get Root Access." When I press the Get Root Access button, the circle in the middle changes to "Rooting Now." When it's finished, I get a message that says "Root Succeeded" and the circle changes to "Got Root Access," but when I reboot, there is no King User app. When I open iroot again, the circle says "No Root Permission." I've repeated this process several times and cannot gain root access. Any ideas? I have the Kindle Fire HD 8.9 16G with version 8.5.1.
Ok I will DEFINITELY check this out... Worked on my kindle, and I had the 16gb wifi on 8.5.1, so I'll look into this later, but other then that, the only other app said to occasionally work is kingroot, or root with restore by bin4ry for kindle fire hd 8.9 (Google it, its on xda)
Sent from my iPhone using Tapatalk
When I go into fire flash the boot partition there is no kind...ect
Cadebonds12 said:
When I go into fire flash the boot partition there is no kind...ect
Click to expand...
Click to collapse
Thats how its supposed to be, itll always say "not flashed" just flash the images like normal. Remember NEVER USE FIREFLASH TI BOOT INTO RECOVERY DO IT MANUALLY.
Sent from my KFJWI using Tapatalk
Delete
Delete
I've tried this method several times, always ending with me having to restore a stock image via fastboot. Everything works fine until I reboot into TWRP for the first time. I can even reboot after installing TWRP (but without booting into it) and it works. Once I enter TWRP the first time, even if I don't do anything except reboot, it never boots past the blue Kindle logo. Flashing the latest nightly CM12.1 says it completes successfully, but it still never boots past the blue Kindle logo. Looks like I'm stuck with the stock Kindle Fire ROM. Any ideas?
chrisaln said:
I've tried this method several times, always ending with me having to restore a stock image via fastboot. Everything works fine until I reboot into TWRP for the first time. I can even reboot after installing TWRP (but without booting into it) and it works. Once I enter TWRP the first time, even if I don't do anything except reboot, it never boots past the blue Kindle logo. Flashing the latest nightly CM12.1 says it completes successfully, but it still never boots past the blue Kindle logo. Looks like I'm stuck with the stock Kindle Fire ROM. Any ideas?
Click to expand...
Click to collapse
I've never heard of that problem nor have I run into it, can you please tell me the following info please:
What version of Amazon OS:
What model of Kindle fire hd 8.9: (wifi or lte)?
Perhaps details on EXACTLY what you did(?):
What specific img(s) you flashed (yes it's necessary):
A log saved through twrp(not needed to be honest):
All these details and more would really help me solve your problem! Thanks!
EDIT: If possible you don't have to use the app, have you tried manually flashing through fast boot?
Sent from my iPhone using Tapatalk
after step 3, on boot, I see the gold fire, then red screen. What now?
Dnorris55 said:
after step 3, on boot, I see the gold fire, then red screen. What now?
Click to expand...
Click to collapse
Do you have a PC with admin access (Windows preferably)? If so pm me EXAXTLY WHAT YOU DID and these:
Amazon OS version you're on:
Lte or wifi kindle:
Other info:
Sent from my iPhone using Tapatalk
MeowDude said:
Do you have a PC with admin access (Windows preferably)? If so pm me EXAXTLY WHAT YOU DID and these:
Amazon OS version you're on:
Lte or wifi kindle:
Other info:
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I finally got it fixed.
I went from the red screen to a stuck Fire logo screen.
Could not get to fastboot screen using Win 10 PC. Was able to use Linux Mint to boot the Kindle into fastboot. From there, was able to flash recovery, etc.
Now running Resurrection Remix 6.01 on my KF HD 8.9 (jem).
Not sure what happened with fireflash.apk. The iroot.apk worked OK, AFAIK.
Thanks.
Sent from my SM-T800 using Tapatalk
Dnorris55 said:
I finally got it fixed.
I went from the red screen to a stuck Fire logo screen.
Could not get to fastboot screen using Win 10 PC. Was able to use Linux Mint to boot the Kindle into fastboot. From there, was able to flash recovery, etc.
Now running Resurrection Remix 6.01 on my KF HD 8.9 (jem).
Not sure what happened with fireflash.apk. The iroot.apk worked OK, AFAIK.
Thanks.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Glad to hear that!
Sent from my iPhone using Tapatalk
23-March-2016:
Read through the instructions and decided to use CM 12.1 after getting frustrated with Amazon and repeated "Google Play Services has Stopped" error messages. So far so good.
24-March-2016:
additional information: Installed TWRP 2.8.7.0 instead of 2.7.7.0 before installing CM 12.1 and GApps 5.1
No issues with TWRP 2.8.7.0.
One comment about this procedure. I was confused by the instruction lines that read:
*Now select "Install" on the main menu (It might say "Zip Install" based on your version of TWRP)
*Now select your rom (if its not in the scroll menu, check the right side of the screen!
Didn't know which rom since all previous instructions were clear on this point.
(this 61 y/o former embedded systems engineer wasn't stumped for long though)
Please add an instruction to ensure CM12.1 and Gapps 5.1 are on the Kindle before booting into TWRP.
I realized my error after starting the backup. Had to boot into Amazon one last time and move the roms.
Then I booted into TWRP, backed up the Kindle, wiped and installed CM12.1 and Gapps 5.1.
Other that that one point the upgrade went very smooth. Am impressed with the new OS.
Thank You!
wptyree said:
23-March-2016:
Read through the instructions and decided to use CM 12.1 after getting frustrated with Amazon and repeated "Google Play Services has Stopped" error messages. So far so good.
24-March-2016:
additional information: Installed TWRP 2.8.7.0 instead of 2.7.7.0 before installing CM 12.1 and GApps 5.1
No issues with TWRP 2.8.7.0.
One comment about this procedure. I was confused by the instruction lines that read:
*Now select "Install" on the main menu (It might say "Zip Install" based on your version of TWRP)
*Now select your rom (if its not in the scroll menu, check the right side of the screen!
Didn't know which rom since all previous instructions were clear on this point.
(this 61 y/o former embedded systems engineer wasn't stumped for long though)
Please add an instruction to ensure CM12.1 and Gapps 5.1 are on the Kindle before booting into TWRP.
I realized my error after starting the backup. Had to boot into Amazon one last time and move the roms.
Then I booted into TWRP, backed up the Kindle, wiped and installed CM12.1 and Gapps 5.1.
Other that that one point the upgrade went very smooth. Am impressed with the new OS.
Thank You!
Click to expand...
Click to collapse
no problem, and thanks for the info, will be sure to add these to the post! :highfive:
Great POST!!!
Successfully updated my Kindle 8.9 with CM12.1.
Thanks.
fireflash11.apx problem
I was able to complete the install previously, but in playing around had to reload my kindle back to the orig. In trying to do the install again when I get to the part where I click the "Not Flashed" it goes into the explorer, but will not show any files at all, only directories. Am I missing something here?
Hello Friends!
Can you flash the Gapps package only without flashing a custon ROM as they usually goo togather.? I have successfuly installed TWRP 7.0.0 and have a rooted KFHD8.9 (v 8.5.1) which is based on android 4.0.3 i understand. Thnaks in advance to anybody who helps me out.
i have absolutely no clue what i am doing here, i tried to reboot my tablet into TWPR menu
but i could not figure it out it has TWRP, and RR rom and root
i held the power button down and did reboot recovery and i did not get TWRP menu
so rebooted it and then i chose bootloader, and now all i get is a black screen that says fastboot..
holding power and it won't reboot it wont turn off or do anything
how do i fix this ****?
how do i get to the twrp menu screen?
how do i create a backup of my system to the SD card?
i want to try an experimental APK but i want to make sure i can recover if it messes up my tablet
but 1st how do i fix this?
gdroid666 said:
i have absolutely no clue what i am doing here, i tried to reboot my tablet into TWPR menu
but i could not figure it out it has TWRP, and RR rom and root
i held the power button down and did reboot recovery and i did not get TWRP menu
so rebooted it and then i chose bootloader, and now all i get is a black screen that says fastboot..
holding power and it won't reboot it wont turn off or do anything
how do i fix this ****?
how do i get to the twrp menu screen?
how do i create a backup of my system to the SD card?
i want to try an experimental APK but i want to make sure i can recover if it messes up my tablet
but 1st how do i fix this?
Click to expand...
Click to collapse
Clean up the language.
- no TWRP (custom recoveries) on this device
- to exit from fastboot untether and long press power until it turns off
- start with the forum index and read what you can/can't do with this device and how to accomplish it
Davey126 said:
Clean up the language.
- no TWRP (custom recoveries) on this device
- to exit from fastboot untether and long press power until it turns off
- start with the forum index and read what you can/can't do with this device and how to accomplish it
Click to expand...
Click to collapse
yes got it to reboot by holding volume and power finally ,it did not work the 1st few tries for some reason
i know i was in the TWRP screen before when i flashed the rom and xposed but now i forget how to get back to it now
so what happens if i mess up my system with an experimental APK, i am trying to add miracast
if it messes up something then will i be able to recover? or would i have to make a backup with TWRP 1st?
gdroid666 said:
yes got it to reboot by holding volume and power finally ,it did not work the 1st few tries for some reason
i know i was in the TWRP screen before when i flashed the rom and xposed but now i forget how to get back to it now
so what happens if i mess up my system with an experimental APK, i am trying to add miracast
if it messes up something then will i be able to recover? or would i have to make a backup with TWRP 1st?
Click to expand...
Click to collapse
Clean up thread title...go from there. Miracast won't work on this device.
Davey126 said:
Clean up thread title...go from there. Miracast won't work on this device.
Click to expand...
Click to collapse
sorry i can't edit it, it won't let me
also i have looked around and i found this .apk
http://cord-cutters.wonderhowto.com...rooted-android-device-running-kitkat-0156212/
(it says kitkat but there was a thread on here on it and it said kitkat or above)
https://www.androidfilehost.com/?fid=95784891001616583
and i searched and searched but i have not found any reports of it ever being tried on the 2015 5th gen fire 7
i can only seem to get to the thread in google cache ,and there are only reports of it being tried on the HD fire 7 and all posts end around 2014 so i am not sure if it will work, but what is the worst thing that could happen if i try this? with no backup and TWRP installed? could i still revert everything back?
have you ever heard of anyone trying this specific .apk on this device before?
gdroid666 said:
sorry i can't edit it, it won't let me
also i have looked around and i found this .apk
http://cord-cutters.wonderhowto.com...rooted-android-device-running-kitkat-0156212/
(it says kitkat but there was a thread on here on it and it said kitkat or above)
https://www.androidfilehost.com/?fid=95784891001616583
and i searched and searched but i have not found any reports of it ever being tried on the 2015 5th gen fire 7
i can only seem to get to the thread in google cache ,and there are only reports of it being tried on the HD fire 7 and all posts end around 2014 so i am not sure if it will work, but what is the worst thing that could happen if i try this? with no backup and TWRP installed? could i still revert everything back?
have you ever heard of anyone trying this specific .apk on this device before?
Click to expand...
Click to collapse
- have not heard of anyone trying linked apk on this device
- in general custom roms on Amazon devices do not support miracast (multiple devices/multiple roms)
- if you can access the stock recovery menu via <power>+<vol-up> recovery is possible (reload FireOS)
- unlikely a straight apk install will bork the rom; more likely it simply won't work
Davey126 said:
- have not heard of anyone trying linked apk on this device
- in general custom roms on Amazon devices do not support miracast (multiple devices/multiple roms)
- if you can access the stock recovery menu via <power>+<vol-up> recovery is possible (reload FireOS)
- unlikely a straight apk install will bork the rom; more likely it simply won't work
Click to expand...
Click to collapse
yup you are right it dod not work the app gave a message right away about not having some file for audio something t other i forget ,just uninstalled th eapk and no damage done