Hi Everyone:
I am attempting to root and install cm11 on my son's KFHD. I am a bit of a noob, but I have successfully rooted my nook color in the past and read MANY threads on how to root, but I'm kind of at a loss.
The problem is that I followed the thread on how to root and I had a bunch of trouble. I finally was able to get through the steps, but the command box closed before the KFHD rebooted successfully. In an attempt to "fix" it, I restored the device to factory settings. It seems to be working just fine with stock os, but there is a superuser app which has requested access to apps.
I downloaded an app from Mobile1 to check that there is root access and the app indicates that I do indeed have root access. Should I go ahead and try to install a rom?
I would like to root it because my son is using it for school and is having a hard time adjusting to the stock os. (Which I hate, too).
Thank you so much!!!!
-NDH
1. Super User is the app that lets apps have access to root. (easy way of understanding it)
2. You need to Install Twrp and 2nd bootlander before installing the rom.
go to this video and follow the directions carefully. http://www.youtube.com/watch?v=a1bLCuQN0-U
3.Go to this video to install cm 11 rom for 2012 version. http://www.youtube.com/watch?v=0ODVX_EYaVY
4. once intalled new rom go to settings-about tablet-cyanogenmod updates and then update to latest version. IMPORTANT
thank you
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
ndharvey said:
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
Click to expand...
Click to collapse
Did you flash anything before this happened?
nope
SafinWasi said:
Did you flash anything before this happened?
Click to expand...
Click to collapse
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
ndharvey said:
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
Click to expand...
Click to collapse
I would recommend you to install a custom ROM like CyanogenMod. Trust me,you'll love it. AOSP is much better than Amazon OS.
Related
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
neut401 said:
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
Click to expand...
Click to collapse
I'm not sure really how to help, but if you can describe the last thing you were doing prior that will help people diagnose it. Were you rooted? Or trying to root? Did you try to modify any system files?
I have the same problem. I was rooted. I was trying to copy the vendor apk into system/ app folder. I think I accidently made copy of app folder, it said app copy then froze. I clicked system restore. did nothing.
Are you able to reach the system with adb shell at all? or not? If not, I think you are stuck sending it back to Amazon for repair/replacement. If you can, you should be able to use the same method you used to root to get /system RW again, and try to fix it up.
I don't know how to use ADB. I used the one click root method. My computer isn't recognizing the device when plugged in. Is there a step by step guide on how to fix it or will it be possible in the future?
If its not recognized, then its unlikely that adb will work. If I had a bricked device though...I would start reading and trying to get that working. If you really don't feel confident in messing around and trying to fix it, call Amazon and ask them to send you a new one.
neut401 said:
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
Click to expand...
Click to collapse
what do you do so that KFTT state in bootloop?
can you take screenshot? or take a picture?
I am having the same problem.
any luck fixing it?
Hi, I am in the same situation. Here in Spain we have the KFHD since 4 days ago.
I rooted it correctly via ADB. I installed google play and installed several app's apparently without difficulties. The issue came after putting the Go luncher HD apk on system\app. After that I rebooted the device and appeared the two luncher options. So everything ok. I was moving around my new luncher and everything was ok, but suddenly the device rebooted and I had the same issue here explained. Bootloop and no factory default possible. Of course just rebooting didn't solve it. I have to say that the last thing I was doing before the sudden reboot was modifying permissions from SU. Maybe it's related, so don't touch anything from there. ADB was not working any more so very few things to try...
Amazon accepted a replacement (I just said what happened but not why) and now I'm waiting a new one.
Hope this can help.
Regards,
If you're willing to do a little work, you can try this recovery method: http://forum.xda-developers.com/showthread.php?t=1951254. Personally, I would just send in the device to be replaced, and not tell them the exact circumstances of how the problem happened. Amazon's generally pretty good about returns and replacements while you're still within warranty.
I shouldn't have restored factory defaults
I am in the same issue
The main mistake I made was selecting "Reset to Factory Defaults"
This automatically turns off the debug mode and with it stopped any communication between my PC and the Kindle Fire HD 7". Even the Factory cable I bought for £3.19 didn't help. The driver shows like it is installed correctly and my Kindle shows Fastboot on the screen when connected, but there is no communication.
I only got it for Christmas and I've goosed it. I am now hoping Amazon will be sympathetic and believe that it just started looping itself without me modding it.
When you reach the fastboot screen unplug factory cable and insert the usb that came with it. Then check your drivers to make sure they are Installed properly. Then use system Img restore tool to restore, follow directions exactly
Sent from my KFTT using XDA Premium HD app
Hello All! I was messing around with App Quarantine and ended up bricking my KFHD (not sure what I did because I was still messing around with it.) My KFHD is rooted but I didn't install TWRP or any type of recovery program. Is there any way for me to unbrick this or am I stuck with a fancy paper weight?
Ichigo said:
You guys should check the 1st gen. Kindle Fire Forums for similar problems and solutions.
Android>iOS... Android FTW!
Click to expand...
Click to collapse
Lord NO! Any Kindle with the letters HD after Fire have nothing in common. Anything run to access the system or modify it will guarantee a permanent brick with NO WAY OUT.
[email protected]@dog said:
Lord NO! Any Kindle with the letters HD after Fire have nothing in common. Anything run to access the system or modify it will guarantee a permanent brick with NO WAY OUT.
Click to expand...
Click to collapse
Technically, the factory cable will still work, even if there are ways to know that you shouldn't do some things (like number 4 in the thread in my signature).
Ichigo said:
Way to bump an old thread.
Click to expand...
Click to collapse
It was sort of a failed attempt, so what the heck.
I've bought my son and daughter a nexus 7 each for Christmas.
His upgraded over the air fine, hers downloaded the firmware, rebooted and the installation started.
After a couple of minutes the Android fell over with a red exclamation mark.
I've tried forcing the upgrade and the same happened.
Any ideas how to upgrade her nexus 7?
Thanks
Fastboot mode is working ?
Sent from my GT-I9100 using xda premium
I've not tried it.
How do I try it?
Assuming it's ok, does that help with upgrading?
Any issue truing fast boot mode?
Any ideas? Or will it need replacing?
Factory reset and try again
Sent from my Nexus 7
I have the same problem.
Hey guys,
I made an account just to post this, however it was all done my G2 so I apologize for poor formatting and/or not completely clear instructions. This issue has kept me up for hours upon hours, and I finally figured out how to fix it. The issue apparently has something to do with the way the Nexus was formatted, prohibiting the update from working. Google/Asus support have been useless regarding the issue which is a very simple fix just requiring the user to reflash the N7 with a stock image. It has been confirmed working by not just me but other people on the reddit nexus 7 board. Here is what I did (copy/pasted from my reddit thread):
---------------------------------------------------------------------------------------------------------------------
There are two methods to fix this, an in depth method, and an easy and quick method. My first time I used the in depth, but I tested this with the easy method too so I'll just post that. I'm on a cell phone so I'm not going into the in depth method - I'm posting this so hopefully the other people like me who got this on Christmas won't have to return it.
----------------
For the quick and easy method, download Wug's toolkit here:
(google this, forums wont let me post links until I reach 10 posts)
Run the driver install guide, making sure to follow the parts about uninstalling previous drivers. Follow this to a T. Next, unlock your bootloader. Its painless and takes seconds. Next, go here and download your Nexus specific update.
(Find this on google developer site, you can google it too - forums wont let me post links - also make sure its 4.2.1)
Click on the "back to stock + unroot" -- we never rooted, but just do this. Select other/browse and browse to the image you downloaded. Flash this. You WILL fail on three files - it says something like recovery.sig failed - it will do it for two other .sig files. This is fine. Let it do its thing. A few minutes later your android will boot up. Log in, and go to settings. Click about tablet. Click on build number like 10 times, until it tells you developer options unlocked. Go into developer options and enable USB debugging. Now, go back to Wugs toolkit and lock the bootloader. There you have it, an updated nexus running stock everything, and locked so your warranty is not void.
----------------------------------------------------------------------------------------------------------------------------
This was a very sloppy guide put together on my cell phone. Any questions just post and I'll do my best to get back to you. Goodluck!
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
albert_htc said:
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
Click to expand...
Click to collapse
This is definitely the easiest way for you to fix your problems. The risk of your device becoming unusable is practically none. This is the beauty of nexus devices, Google provides official factory reset ROMs for you to flash in these sorts of situations. You can either use Wugs or mskip's tookit as advised to automate the process (fastboot commands used to flash the recovery image, fastboot commands are simply used to flash it to your device) or you can use fastboot to flash it yourself manually (still very easy)
I would 100% do this to fix your device. Don't be scared! This is the official way of fixing a nexus device when it doesn't function.
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
albert_htc said:
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
Click to expand...
Click to collapse
I'm not certain about the driver issues because I don't use Wug's toolkit, sorry!
However, when you get this completed, it should solve this problem in the future.
I've had to go with option 1 for the drivers..
but it's done and working
One thing I did have to do after unlocking the boot loader was reset up on the wifi and re enable USB debugging before I could continue.
all sorted thanks
albert_htc said:
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Click to expand...
Click to collapse
Let us know how it comes out and if there's problems, exactly where you're hitting the problem. I will try to help you out and later today I could probably get on team viewer and help you figure the drivers out.
Sent from my Nexus 7 using Tapatalk HD
Hi CharliesTheMan..
It's working. Had to use option 1 for the drivers.. but its updated and working
Thanks
Glad it worked out!
Sent from my Nexus 7 using Tapatalk HD
Alright from the get go. I am running 10.3.1. I rooted using a tutorial from this site, it was rather easy. It only took me like 25 minutes and then to add the Play store, another 25. I had it running perfectly fine with GO launcher and it was the way i liked it till I saw NEXT launcher and I wanted that instead. I had GO still running and being a noob I thought if I installed NEXT launcher that it would be able to be set by default when I was asked and that would be it. From what I can tell they were fighting for the kindle's affection and it was at a constant refresh directly after the install. I then soft reset it and I'm stuck at a kindle fire screen. The animation is very fast, with no delay between ending and beginning again. I tried today using the KFU to no avail. I also tried to reinstall the drivers, nada. my computer in device manager does read it, "other devices" Kindle" Uppercase "K". I've uninstalled and reinstalled. I cannot get the SDK to work on my computer. Even with the correct environment setup, nothing. I've viewed plenty of other fixes, none help my situation, not because I don't think they do, but because I've tried. When I KFU I get a Waiting for Device, nothing further happens (40 minute waiting period). I tried to Recovery boot and I tried to push TWRP, nothing. I'm at a loss. To be clear idk what fastboot is and I don't know how to "code" anything so anything help in detail, would be awesome, you guy are a great community and I wouldn't dream going any where else for expertise. Thanks for any help. Btw AMA and I'll try and best accommodate so I can fix this
rekindle said:
Alright from the get go. I am running 10.3.1. I rooted using a tutorial from this site, it was rather easy. It only took me like 25 minutes and then to add the Play store, another 25. I had it running perfectly fine with GO launcher and it was the way i liked it till I saw NEXT launcher and I wanted that instead. I had GO still running and being a noob I thought if I installed NEXT launcher that it would be able to be set by default when I was asked and that would be it. From what I can tell they were fighting for the kindle's affection and it was at a constant refresh directly after the install. I then soft reset it and I'm stuck at a kindle fire screen. The animation is very fast, with no delay between ending and beginning again. I tried today using the KFU to no avail. I also tried to reinstall the drivers, nada. my computer in device manager does read it, "other devices" Kindle" Uppercase "K". I've uninstalled and reinstalled. I cannot get the SDK to work on my computer. Even with the correct environment setup, nothing. I've viewed plenty of other fixes, none help my situation, not because I don't think they do, but because I've tried. When I KFU I get a Waiting for Device, nothing further happens (40 minute waiting period). I tried to Recovery boot and I tried to push TWRP, nothing. I'm at a loss. To be clear idk what fastboot is and I don't know how to "code" anything so anything help in detail, would be awesome, you guy are a great community and I wouldn't dream going any where else for expertise. Thanks for any help. Btw AMA and I'll try and best accommodate so I can fix this
Click to expand...
Click to collapse
Please post in the correct forum.
seokhun said:
Please post in the correct forum.
Click to expand...
Click to collapse
Which would be...Could you link me Sir/Ma'am?
rekindle said:
Which would be...Could you link me Sir/Ma'am?
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2097. You said your device runs 10.3.1. The 7" KFHD runs 7.3.1 and the 8.9" runs 8.3.1, only the KF2 runs 10.3.1.
Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo
Guys, no one, who can help me?
arnakin said:
Guys, no one, who can help me?
Click to expand...
Click to collapse
If you have a recovery installed, I would say just grab the rooted 7.4.1 from the development section and flash that after full wiping. That should solve your issues.
arnakin said:
Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo
Click to expand...
Click to collapse
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.
A similar problem
-a- said:
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.
Click to expand...
Click to collapse
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!
CVanB said:
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!
Click to expand...
Click to collapse
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.
Solved
DroidIt! said:
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.
Click to expand...
Click to collapse
I didn't click flash script when I rebooted into recovery from fire flash. In fire flash you have a couple options, two mandatory, using a older bootloader as the 2nd. flash a boot partition image, apply stack override, flash a recovery partition image, disable auto recovery auto update, then wipe cache wipe data wipe system install zip files, flash and install script. Lastly reboot and reboot into recovery. :victory:
So did you get your issues sorted OK, or are you still having problems?
Over the past couple years and up until last week I've been able to kill and revive my tablet. This time I'm really stuck.
Setup: I have TWRP running fine, not sure if it was 3.5.2_9 or 3.6.0. I've playing around with different ROMs for the past few weeks, seeing which one I wanted to use. Friday I reinstalled LineageOS 18.1, but I click the replace/keep up to date option which now guess replaced TWRP because it was no longer there when I booted in recovery.
I've tried reinstalling TWRP, CF autoroot, etc. But the closest I've gotten is TWRP coming up, then displaying errors quickly and the system rebooting. I know just enough to be dangerous, but not enough to know exactly what I'm suppose to do in what order to get the system back up (or which versions of the files I've downloaded I should actually be using.
Any help to get back to where I can run TWRP again would be helpful, I can probably take it from there. I can get the tablet in download mode, but that's about it.
We have same device, but still i can't upgrade my tab in any roms. And unable to install TWRP higher than 3.1 version.
davidzvi said:
Over the past couple years and up until last week I've been able to kill and revive my tablet. This time I'm really stuck.
Setup: I have TWRP running fine, not sure if it was 3.5.2_9 or 3.6.0. I've playing around with different ROMs for the past few weeks, seeing which one I wanted to use. Friday I reinstalled LineageOS 18.1, but I click the replace/keep up to date option which now guess replaced TWRP because it was no longer there when I booted in recovery.
I've tried reinstalling TWRP, CF autoroot, etc. But the closest I've gotten is TWRP coming up, then displaying errors quickly and the system rebooting. I know just enough to be dangerous, but not enough to know exactly what I'm suppose to do in what order to get the system back up (or which versions of the files I've downloaded I should actually be using.
Any help to get back to where I can run TWRP again would be helpful, I can probably take it from there. I can get the tablet in download mode, but that's about it.
Click to expand...
Click to collapse
Have you just tried flashing stock firmware, using odin?
I was trying the CF_autoroot (and other kernels(?)) and TWRP in odin.
Oddly over the weekend I left it plugged in for a day and and when I opened the cover it was in TWRP.
I was able to wipe, format, and load a ROM. But I think I might have broken the battery connection now, it doesn't seem to want to plug into the main board. So it doesn't want to do anything now. I'll probably play around with the connector a bit and see if I can sort that out.
But I'm not sure what @rufio85 issue might be and I would be the last person to advise anyone on this stuff.