Develop Bugs

KFHD8.9 starirom twrp confusion

Hi guys! I recently swore off tinkering with my Kindle Fire HD 8.9, but just couldn't help myself. I'm not too incompetent...I've rooted the 7 inch Kindle with success and recently unlocked and rooted a Samsung Infuse phone. All that being said, I am bit confused. Here is what I've done:
I rooted the KFHD8.9 using the binary tool. The only problem I ran into was in the window shell portion (when I was supposed to type in /data/local/tmp/onload.sh). I ended up skipping this part. Probably not wise. Anyway, the root was successful and Root Analyzer says it is rooted.
I then successfully installed 8.9Starirom. I have it set up the way I want it now. My goal is to install xbmc apps so I can stream icefilms.
Here is the catch ...
I don't have TWRP installed. I never installed it after rooting. I saw that installing 8.9Starirom would give me an option to install it. It says I would get a red screen if I didn't have it and then I'd have an option to install, thus correcting the red screen. I never got the red screen. I also never get the "blue" Kindle logo when booting. The device loads and I get the option to load with Go Launcher EX, Go Locker, or Kindle.
All is working well. My apps that I had installed all work. New apps I install work. Wifi works.
I'm just not convinced I have everything set up properly. Can someone point me in the right direction as to what I should do at THIS point. Maybe the answer is "nothing", but I want someone more experienced than me to tell me that.
Thanks for any guidance!

this teekb
For what it's worth ... I just successfully installed XBMC and Icefilms on this Kindle. Both are working.
Any ideas on my twrp / fastboot issue?

[Q] Kindle hd 8.9 stuck in slow mode after failed re root

My kindle hd 8.9 was re rooted using bin4ry v31 after the last ota update 8.4.8. It worked fine. Now there was another ota update to 8.4.9 on 6/14/14. I tried using the same method as before. ADB is enabled in my kindle, I am seeing Android Composite ADB interface. when I plug the kindle in. I got through part of the re root, where it rebooted, and now it is extremely slow, has a black screen with white cracked lines to slide in open, and although some things work they are very very slow. Please can someone either help me re root or unroot it so that the kindle runs normally. I don't know what mode that slow one is, but you can't do much of anything. I tried to roo a few times, and tried to put in the stock kindle update and re run it, but nothing is working to get it out of the slow mode. Right now my computer can see and put things onto the kindle, and when trying to root, it seems like it is trying to work, but since the kindle is slow, I don't know if it is getting stuck and not finishing.
Can you help me figure out what is wrong?

benee16 said:
My kindle hd 8.9 was re rooted using bin4ry v31 after the last ota update 8.4.8. It worked fine. Now there was another ota update to 8.4.9 on 6/14/14. I tried using the same method as before. ADB is enabled in my kindle, I am seeing Android Composite ADB interface. when I plug the kindle in. I got through part of the re root, where it rebooted, and now it is extremely slow, has a black screen with white cracked lines to slide in open, and although some things work they are very very slow. Please can someone either help me re root or unroot it so that the kindle runs normally. I don't know what mode that slow one is, but you can't do much of anything. I tried to roo a few times, and tried to put in the stock kindle update and re run it, but nothing is working to get it out of the slow mode. Right now my computer can see and put things onto the kindle, and when trying to root, it seems like it is trying to work, but since the kindle is slow, I don't know if it is getting stuck and not finishing.
Can you help me figure out what is wrong?
Click to expand...
Click to collapse
Yep sucks for us for now it seems
Mine is in the same state. To unslow mo it all i found that works is using recovery mode to erase every single thing on it. This will speed it back up to normal. Beyond that i don't have a clue what to do.
You can enter recovery mode if you dont know how by pressing volume down and power. Or dl droid explorer run it click the multi colored shield icon and reboot to recovery.
I would hold off for now though. As one of these guys may have a way to save you all the head aches i have now. I had psp emulator playstation emu nintendo ds dolphin aka game cube and wii all running properly now all gone. go figure. Pain in the rear to get em all running properly. Oh worst bit loosing my crisis core newgame + save lvl 35+ with all items etc etc. Was gona put the hurt on every thing LOL
Oh and if theres any amazon employees lurking and reading great job on becoming a apple clone wanabe In other words amazon you all need to get a grip. People want to customize their tablets and have something that runs like mad with out regards to warranty. We want our tablets the way we want them not the way you want them. No one likes apple with their forced updaties etc

benee16 said:
My kindle hd 8.9 was re rooted using bin4ry v31 after the last ota update 8.4.8. It worked fine. Now there was another ota update to 8.4.9 on 6/14/14. I tried using the same method as before. ADB is enabled in my kindle, I am seeing Android Composite ADB interface. when I plug the kindle in. I got through part of the re root, where it rebooted, and now it is extremely slow, has a black screen with white cracked lines to slide in open, and although some things work they are very very slow. Please can someone either help me re root or unroot it so that the kindle runs normally. I don't know what mode that slow one is, but you can't do much of anything. I tried to roo a few times, and tried to put in the stock kindle update and re run it, but nothing is working to get it out of the slow mode. Right now my computer can see and put things onto the kindle, and when trying to root, it seems like it is trying to work, but since the kindle is slow, I don't know if it is getting stuck and not finishing.
Can you help me figure out what is wrong?
Click to expand...
Click to collapse
Factory reset is always better than flashing and other serious tinkering. kindle hd 8.9 is still rootable with 8.4.9 update, I did it and another member KatanAlive have done it.

What method did you use to root? There are a few different methods. used bin4ry v31 I used the old special option, then also tried the old option.

akb1ajay said:
Factory reset is always better than flashing and other serious tinkering. kindle hd 8.9 is still rootable with 8.4.9 update, I did it and another member KatanAlive have done it.
Click to expand...
Click to collapse
Ive tried various tools etc. While it seems i am able to get root i can not for example view the root directory in adb shell. I can kill any process under ps list even ones ran by root. Again the root directory shows as empty under ls. Running the superuser app that does show under apps seems t do nothing (im assuming this is because root is already active by this point) It does load but nothing in log window. Also it remains stuck running extremely slow. I can not install google frame work etc.
What i want to do is just go with a custom rom and be done with this mess. After all if amazon managed to force updates on kindles with ota disabled and blocked once they will likely be able to do so again. So theres zero point in staying on a stock rom even downgraded and or rooted.
Now the only problem there is it seems rom update requires fastboot? If this is not the case what are the steps to go about it by a different means? Or what methods other than fastboot cables are there to force it in to fastboot with out ripping in to the kindlefire hd 8.9 in my case?

benee16 said:
What method did you use to root? There are a few different methods. used bin4ry v31 I used the old special option, then also tried the old option.
Click to expand...
Click to collapse
I used manual method described in this thread and yesterday another member also used this same method to root the Kindle with update 8.4.9 http://forum.xda-developers.com/showthread.php?t=2069117
I have been extensively reading this forum for rooting Kindle Fire HD 8.9 and I have seen people failed just because of a simple mistake or not starting afresh. Many people were able to overcome their anomalous problem just by a factory reset and then starting again the process of rooting.
No one knows at which step problem started to appear until you clarify completely that what method you were following, or did you install some other drivers mentioned in another method, or did you interrupted the progress, or any other tinkering you had had done earlier with Kindle.
Every method pre assumes that your device is in default condition and your PC has favourable environment for the completion of the rooting process. Like a meber was following the process of rooting and when a stage came to enter his Amazon password, he entered the password but the process could not be continued, because his Kindle was not registered , so even after entering the correct password the process was aborted. Later he registered his Kindle and started agin and it was rooted.

So true what you've said about it not being a fresh root. I am going to try a few more times to root, then do a factory reset. My kindle could use a fresh start, but I thought I'd try just for future knowledge. If anyone else comes back from the slow kindle stage, please contribute what you've done to fix it because it may help someone else resolve their issues.

I decided to do a full restore. Then I was able to use a bin4ry script for kindles to root. Now I am having difficulty getting google play to work again. I keep getting an error not enough space on the partition \system. Free up 6MB in system and try again. I put a version of google market on to see if there would be a difference. I was able to open it, but nothing will download. Anyone else have any experience with this problem?

benee16 said:
I decided to do a full restore. Then I was able to use a bin4ry script for kindles to root. Now I am having difficulty getting google play to work again. I keep getting an error not enough space on the partition \system. Free up 6MB in system and try again. I put a version of google market on to see if there would be a difference. I was able to open it, but nothing will download. Anyone else have any experience with this problem?
Click to expand...
Click to collapse
If you have rooted Kindle "not enough space" problem can be easily resolved. Is your Kindle rooted?

Yes my kindle fire hd 8.9 is rooted. I currently have version 8.4.9 software from amazon.

benee16 said:
Yes my kindle fire hd 8.9 is rooted. I currently have version 8.4.9 software from amazon.
Click to expand...
Click to collapse
I too have had this low space problem after updating to 8.4.9. I was despaired but after searching the internet for 2/3 hours I found the solution. First thing you need to do is to get Titanium Backup from somewhere. It has the capacity to convert system app to user app and this will free up some ROM space so you can install Google Play afterward. Convert one by one some system apps that are not critical to Kindle's functioning, to user app. For example, you can convert Silk browser, Amazon Video, Amazon music, Kindle tutorial, Office Suite to user app. The moment you have above 20 MB free space in ROM you can install there Google Play. I am not sure if a free version of Titanium Backup have this functionality or not, I have installed a pro version of it. If free version is of no use then get a pro version from somewhere. I think you know where to get it from. Good Luck.

Wow thanks so much for the info. I did not have the pro version of titanium. Instead I used /system /app mover which is a free app. I changed a few system files to user files like suggested and am now able to use google play. I made sure I could download apps from it also, and it worked just fine. Now I have to re download apps I lost when I had to restore.

benee16 said:
Wow thanks so much for the info. I did not have the pro version of titanium. Instead I used /system /app mover which is a free app. I changed a few system files to user files like suggested and am now able to use google play. I made sure I could download apps from it also, and it worked just fine. Now I have to re download apps I lost when I had to restore.
Click to expand...
Click to collapse
:good:
would not you press Thanks Button?

Not sure what I did to my fire tv.

I just got a rootable fire tv and decided i'd try the internal storage increase trick. I updated to the latest custom root firmware and installed all my apps before attempting and when I did it had some strange error and quit. Now I am left with what appears to be a fire tv that is rooted but does not know it is. I can mount external usb, all the superuser stuff still works updates are blocked etc. But when I run towel root it says this phone doesn't work... I can't open the super user program its just doing weird stuff. Has anyone ran into this? I really want to try the increasing internal storage trick.

danknasty said:
I just got a rootable fire tv and decided i'd try the internal storage increase trick. I updated to the latest custom root firmware and installed all my apps before attempting and when I did it had some strange error and quit. Now I am left with what appears to be a fire tv that is rooted but does not know it is. I can mount external usb, all the superuser stuff still works updates are blocked etc. But when I run towel root it says this phone doesn't work... I can't open the super user program its just doing weird stuff. Has anyone ran into this? I really want to try the increasing internal storage trick.
Click to expand...
Click to collapse
So you messed up your device trying to do a trick, but it makes you wanna fix your device so that you can try it again? LOL. Did you try reinstalling the rom? Reinstall the custom firmware and report back. It will probably fix everything.

porkenhimer said:
So you messed up your device trying to do a trick, but it makes you wanna fix your device so that you can try it again? LOL. Did you try reinstalling the rom? Reinstall the custom firmware and report back. It will probably fix everything.
Click to expand...
Click to collapse
Well yea it didn't explode so I wanna give it another shot.... I actually was able to get this working but it's still acting weird super user is basically cemented in the device with no way of removing it or opening it and towel root acts like it's an Unrooteable unit. At any case everything else seems to be working fine boots to xbmc shows 800 gig internal storage. Not sure what I did.

I think the su app crashes on mine also when I try to open it. Something with the latest rom from rbox. No big deal as long as it's working. I don't have much reason to open it.

i think its normal,cause u updated to 51.1.4 latest rbox rooted (think also with boot menu and cwm)
Towelroot checks firmware and when its not 51.1.0 it seems that it say, your phone is not supported.
so have fun with your 800gb ft ^-^

schybiorz said:
i think its normal,cause u updated to 51.1.4 latest rbox rooted (think also with boot menu and cwm)
Towelroot checks firmware and when its not 51.1.0 it seems that it say, your phone is not supported.
so have fun with your 800gb ft ^-^
Click to expand...
Click to collapse
Oh ok makes sense. The only reason I checked super su was because its not on grant all mode guess I'll just live with it.

yea, also didn't got su app to work. also annoying notifications on screen but i have to live with.

[Q] Fire Phone: SuperSU-me, Xposed Framework and other Issues

Hi,
I just got a fire phone and I'm facing multiple issues. It updated to 4.6.6.1 once i started it. Now I want it to act like a normal android phone so I installed google now launcher.
Next thing i wanted to do is to customize the laucher. So I did research how to root it. Did it with kingroot and afterwards followed various instructions to change to superSu. Non of them worked. Neither via adb nor SuperSU me nor the terminal version. only rooted when on kingsroot. SuperSU binaries also would never succesfuly update. Anyways.
So after I got the root, I wanted to install Xposed Framework to finally customize the launcher. Now xposed is saying, that it is not (yet) compatible wit the ANdorid SDK Version 19 or my Prozessor architecture. (armeabi-v7a)
I'm running the phone on german language. Don't know what to do anymore with both. SUpersu and Xposed. Appreciate any help.

So you already bought Super-Sume-Pro? Good, because removing / replacing Kingroot was possible even with the (early) free version of Super-Sume (9.1.6).
Download this old version* of Kinguser.
Yes, like always, it's classified as a virus / exploit / PUP, because it uses very aggressive methods of achieving root.
"But Bingo, this is only Kinguser, I need Kingroot."
No you don't. I used this combo many times, it always worked, from the latest version down to Fire OS 4.6.1 when I first tried it.
Uninstall your current version of Kingroot / Kinguser and remove the leftover folders from the internal storage.
Install the old version (disable auto update within in the app, it can be quite annoying), let it "achieve" root, disable WiFi if you want.
Run Super-Sume. It will have no problem replacing Kinguser with 2 steps.
Download this compatible version of the Xposed Installer.
Install framework, etc. You know the drill.
For BusyBox, I'd recommend either Stericson's version or Meefik's.
I tested one of my devices with 4.6.6.1 and the above mentioned customizations (mainly to enjoy microG on Fire OS ^^), so I can say it definitely works.
* Had to use OCH, because the "good guys" like Dropbox and Google Drive won't allow hosting / linking this file, since it's a bad azz virüs.

I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot.
Click to expand...
Click to collapse
Ugh, so many letters, I'm so confused, please... no more, let's stay with "dumb it down". This saves time so I can roll around in my own feces. :victory:

Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Click to expand...
Click to collapse
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed

coolni said:
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed
Click to expand...
Click to collapse
Hmmmm...I don't know what to say. I just used it today after returning a phone to stock Fire OS for my niece. The only thing I can think of is I'm using an earlier version of Kingroot? I'm using KingRoot-4.1.0.524.apk if that matters. I can try to PM it to you, but I'm not sure it will work because, as Bingo mentioned, it is seen as a virus by most servers.

Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.

Bingo Bronson said:
Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.
Click to expand...
Click to collapse
can anybody help to root 4.6.6.1 ?
Kingroot 4.0.0.233 from zip file did not work on my phone with 4.6.6.1.

Having problems on custom recovery
Hello sir I am using amazon 4.6.6.1 almost 1 year ago I have backed up my custom recovery from flashify and deleted accidentally now I need that but can't do anything I have tried most things to get back but can't and also can't root my phone with king root I am installing it but it's saying that app not installed any solution please my email is [email protected]

Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom menu issues

Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom - 573210720
Menu selections starts at top (Filmstruck) goes down to browse, then settings. Going back up, it goes to browse, then to Criterion Channel. So can not access Watchlist or Search, and can only access Filmstruck after first opening the app. If you have already gone down a menu selection, you can't go back up to it. I don't remember which version this issue started with but I tried going back a couple rom versions with the same results.
Can anyone else confirm this on theirs or have any idea how to fix it? I have 2 FTV1 boxes and an FTV Stick 1, all rooted. I'd hate to have to go back to stock for one app but since I'm paying for the service (Filmstruck) I may have to.
Video of how it is not working https://youtu.be/uz_JEjfbv18

For what it's worth I did try older versions of the app as well as side loading the app from my kindle fire HD 8 tablet (rooted) where it works just fine. Also works fine on my phone running android nougat and PC. The side loaded app would just start to open and then close.

New versions for Amazon and Google Play - no fix
So there was an update to the Filmstruck app 3.1.1 on Amazon Appstore and 3.1.0 on the Google Play Store. Same results exactly. Both versions work fine on the tablet. Both versions have same exact menu navigation issues on the FTV 1. I'm about to throw in the towel and just give up being rooted and go back to stock. I'd really like to confirm that would be the solution before I go that route though. Can anyone else confirm they do or don't have this issue on their rooted FTV1 or if it works fine on unrooted? Right now all I can do is play it on my tablet and cast to the TV which is pretty frustrating. Thanks in advance for any thoughts on this.

Works fine on new unrooted FTV STick 2
OK, the suspense was killing me so I went and bought a Fire TV Stick 2 for testing. Opened up network so it would take updates if it needed them, set it up, installed the Filmstruck app, and everything worked perfectly. (Except I couldn't adjust the video scaling, but that's just because I have an old TV)
So I guess this confirms there is an issue with the Filmstruck app and the latest prerooted rom versions for the FTV1 and FTV1 Stick.

Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.

drewb0y said:
Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.
Click to expand...
Click to collapse
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.

Y314K said:
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.
Click to expand...
Click to collapse
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.

drewb0y said:
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.
Click to expand...
Click to collapse
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.

Y314K said:
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.
Click to expand...
Click to collapse
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!

drewb0y said:
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!
Click to expand...
Click to collapse
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...

Fixed
Y314K said:
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...
Click to expand...
Click to collapse
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!

I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.

drewb0y said:
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!
Click to expand...
Click to collapse
drewb0y said:
I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.
Click to expand...
Click to collapse
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.

Y314K said:
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.
Click to expand...
Click to collapse
Gotcha. It seemed to load just fine without the MD5.

Well it worked for a few weeks and then back to the same behavior as before. Going to try unrooting again.