Sorry for the newb question here. But I have a kindle fire and the version is 6.3.1 i would like to root the device. My os is osx 10.7.x I was wondering if i could use a version of super one click or if any one had any suggestions. I also have my computer boot camped so if super one click isnt an option can you please direct me in the right way thank you.
Read this first:
http://forum.xda-developers.com/showpost.php?p=23747567
Error while rooting kindle fire with 6.3.1 leads to error while flashing JB 4.2.1
Hello,
I need help to understand the process to install the root and Jelly Bean in my KF
I attached the message I get
What I did was:
restore the KF to factory settings
install the ADB drivers on my PC
connect the KF and verify the 4000 status
install permanent root and super user (please check the log)
While rebooting, it enters into the recovery boot screen and that's it. I don't see that the process is complete
I reboot the KF and the KFU, after that I can install the extras from the KFU but not superuser app
In the recovery boot screen I can do backups, which I did and flash the JB ROM
after rebooting with the JB installed I got stuck in the waving triangles animation and from time to time it tells me that Android is updating apps
I reboot the KF and go back to the waving lines animation and sometimes I see errors of starting the apps and got stuck in the animation
I've downloaded the ROM over 5 times in 2 different PCs with the same results.
I can restore the KF into the last backup I made any time.
Please advise.
I really appreciate the attention and support.
Thanks
Mike E.
In recovery, did you wipe system and factory reset before installing the ROM?
"That's a special kind of stupid. The kind that makes me laugh"
Okay for one don't use that kfu again something is wrong with it. To flash a rom wipe factory reset, wipe cache, wipe dalvik, wipe system in that order then flash rom.zip then gapps.zip select reboot and then system. You have a bootloader and a recovery you're done with kfu for now leave extras alone that is for stock purposes not jelly bean.
Thepooch said:
Okay for one don't use that kfu again something is wrong with it. To flash a rom wipe factory reset, wipe cache, wipe dalvik, wipe system in that order then flash rom.zip then gapps.zip select reboot and then system. You have a bootloader and a recovery you're done with kfu for now leave extras alone that is for stock purposes not jelly bean.
Click to expand...
Click to collapse
Thank you very much, the order of the wipes did the trick, I'm happy with JB 4.2.1!
Related
I tried to install cm7 on my kindle fire
used thix http://forum.xda-developers.com/showthread.php?t=1399889
for rooting and installing the recovery
downloaded cm7 from here http://forum.xda-developers.com/showthread.php?t=1390773
made a backup, wiped cache and dalvik and installed, now everything stays black!
the tool and adb still "sees" the kindle
oh now i somehow managed to get back to recovery and now I'm restoring the system
what did I do wrong?
Tried again: when installing it says "E:Cannot load colume /misc!" before and after it tries to install the update
fire utility says adb status: online, adb rooted: yes, boot status: 4000
So where are you on this now? Did you get it all done?
Sent from my Kindle Fire using xda premium
It sounds like u downloaded the non wipe cm7 and only wiped caches before you flashed. Make sure you wipe data as well its the factory reset button. Sounds like ulyou got it back. If you're not completely comfortable flashing at least do some research
Sent from my ADR6300 using xda premium
orso7 said:
I tried to install cm7 on my kindle fire
used thix http://forum.xda-developers.com/showthread.php?t=1399889
for rooting and installing the recovery
downloaded cm7 from here http://forum.xda-developers.com/showthread.php?t=1390773
made a backup, wiped cache and dalvik and installed, now everything stays black!
the tool and adb still "sees" the kindle
oh now i somehow managed to get back to recovery and now I'm restoring the system
what did I do wrong?
Tried again: when installing it says "E:Cannot load colume /misc!" before and after it tries to install the update
fire utility says adb status: online, adb rooted: yes, boot status: 4000
Click to expand...
Click to collapse
That message is normal, ignore it.
It sounds like you should be good to go....What happens when you shut the kindle off and then turn it back on?
Thanks for your answers.
After another failed try I did a total wipe (factory, data, system, dalvik, cache)
and it worked
BUT after i installed everyting i put the kindle in standby, and when i tried to wake it up after a few hours, it stayed black. "reanimated" it with holding down the power button for about 20 sec. for total power off, afterwards it startet without any problem.
is ther a problem with the cm7 version for the fire or is it just bad luck?
this is a known problem on the kf espacially after some days - don't worry
btw. please post such a problem next time in the general section
oh sorry, used the wrong tab for a new thread (had dev and general open in 2 seperate tabs)
but thx for your help
Okay, I have a kindle fire and ive tried all the utilitys to fix this but none of them work.
The kindle boots up, and says the following processes stopped unexpectedly
com.android.providers.calender
and android.process.acore and then the device shuts off and loops over again
Its on the stock rom and i have no idea how to fix it
thanks in advanced
Do you have root, bootloader, and recovery? It seems your calendar or contacts are corrupted and require deleting some files, but unless you stop the reboot you won't be able to do that. I would recommend using recovery to wipe the cache and factory reset.
BTW, does the stock ROM include Google Calendar?
Its completely stock, I can't get the Kindle fire utility to flash the boot loader because it reboots itself and it keeps saying "waiting for the device". I've installed the drivers and nothing is working. No root.
Unfortunately to fix this problem you'll need access to fastboot to install custom recovery. You'll be able to revert back to stock afterwards but you'll lose some data in the process.
The easiest way to do this is with the Kindle Fire Utility but you run the risk of running into some trouble (but not much). It's unnecessary and potentially dangerous to install a bootloader if you plan to revert back to stock so don't even try it.
You absolutely have to make sure your drivers are in order to get past the "waiting for device" problem. Make sure you've read and understand the following tutorial on device drivers:
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Once you have recovery installed you'll be able to reinstall the stock 6.3.1 update which will fix your original problem and revert your device to a pure stock state (no root, no recovery, etc.)
Okay, I've double checked the drivers for the device, can you post a thread with exactly how I use fast boot and install a custom recovery? And I plan to revert to stock and then use install a custom recovery image and then cyanogenmod 7 over that. Does the device have to be powered off or on to access fast boot and install a custom recovery image? The issue I have is the device powers on and stays on for only about 15 seconds, and then it dies on my again. Also, thanks for the quick response
If your drivers are in order you can use KFU to install custom recovery as it does everything for you.
If you want to do it manually you need to read the following posts:
http://forum.xda-developers.com/showpost.php?p=23747567&postcount=1
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?p=24124828
Just remember to skip the bootloader.
[Edit:] The manual method also requires working drivers.
hunterhk said:
Do you have root, bootloader, and recovery? It seems your calendar or contacts are corrupted and require deleting some files, but unless you stop the reboot you won't be able to do that. I would recommend using recovery to wipe the cache and factory reset.
BTW, does the stock ROM include Google Calendar?
Click to expand...
Click to collapse
Thanks for this suggestion. :good::good: My kindle went into a boot loop after I hid the SU account with Voodoo OTA Rootkeeper. It took several tries to get it to go into recovery, but managed to get in. Wiping the main cache fixed the boot loop for me.
So I tried to load HellFire rom on my kindle with Clockwork Recovery. I flashed the rom and did all the resetting and clearing of cache.
What happens when I now load my kindle is this.
1.) It loads the kindle fire logo
2.) loads the hellfire animation for a split second
3.) goes back to the kindle fire logo
4.) loads this blank screen
my computer cannot find the device when it is loaded in this blank screen. It can only find it when it is on the kindle fire logo and then it's named as "Amazon" (in my device manager) and I cannot do anything after that because it only stays on the kindle fire logo for maybe 5 seconds. Once the logo is gone from my kindle, my computer cant find the kindle connected.
If there is some way that I can just get into the Clockwork Recovery I can then just put a diffrent rom on. This HellFire rom of there's is defective and shouldn't be allowed to be out there in the public.
Any help will be amazing.
Thanks.
Which clockwork mod recovery? Also I have found when flashing hellfire in twrp that system and data had checks in them under mount simply by unchecking them I could get it to boot I really dont know how this applies to cwmr my suggestion though is to do a full wipe and flash a rom other than hellfire . Another thing I have noticed is this tends to happen when gapps are prebaked into the rom IMO the kindle needs this mount and unmount of system while flashing gapps to truly have a good clean flash...
Thepooch said:
Which clockwork mod recovery? Also I have found when flashing hellfire in twrp that system and data had checks in them under mount simply by unchecking them I could get it to boot I really dont know how this applies to cwmr my suggestion though is to do a full wipe and flash a rom other than hellfire . Another thing I have noticed is this tends to happen when gapps are prebaked into the rom IMO the kindle needs this mount and unmount of system while flashing gapps to truly have a good clean flash...
Click to expand...
Click to collapse
well right now I cant even get my computer to recognize my kindle. It's stuck in this loop..
No access to recovery?
Thepooch said:
No access to recovery?
Click to expand...
Click to collapse
I dont know how I could access recovery without it being recognized by the computer.
You have no yellow triangle or white kindle with blue fire then your kinda missing out on something its a bootloader that gives you access to recovery without that its very difficult indeed somewhere along the way we need to get you a bootloader but because at this point drivers are an issue I suggest using Linux I will help you with a setup that will rule drivers out of the equation and hopefully we will be able to flash a bootloader to your device in order that you can obtain access to recovery and clean up your broken system issue by flashing a rom that your kindle will like more pm me and we can get that sorted for you
Thepooch said:
You have no yellow triangle or white kindle with blue fire then your kinda missing out on something its a bootloader that gives you access to recovery without that its very difficult indeed somewhere along the way we need to get you a bootloader but because at this point drivers are an issue I suggest using Linux I will help you with a setup that will rule drivers out of the equation and hopefully we will be able to flash a bootloader to your device in order that you can obtain access to recovery and clean up your broken system issue by flashing a rom that your kindle will like more pm me and we can get that sorted for you
Click to expand...
Click to collapse
Alright. Thanks!
I have the same problem, any solution?
Two Kindle Fires in hand: one successfully rooted and updated to Jelly Bean (yay!) using the wonderful instructions on this site, the other one installs the OS ROM seemingly fine, but will not boot. Starts up to the white/blue "kindlefire" logo, begins boot process, then goes blank and stays that way until manual power off.
Used the same procedure on both devices:
1. Started with the device running Kindle Fire software version 6.3.1.
2. Used the multi-step process provided with BreakDroid_0.6.5 to get root access and install TWRP 2.2.2.1.
3. Copied ROM to device and installed using TWRP menus.
4. Rebooted.
I can reboot many times, and get the same result: the OS boot hangs at a blank screen. I've tried multiple ROMs, using the cache & Dalvik-cache wipe procedure in between each attempt:
* jb-kfire-hashcode-07-13.zip
* jb-kfire-hashcode-10-10.zip
* jandycane_otter-v1.7.3_0xD34D.zip
* jandycane_otter-v1.8.0_0xD34D.zip
* AlienDroidV3.0.zip
I've even restored to the stock configuration (by installing update-kindle-6.3.1_D01E_4107720.bin) and started the whole process over again. Still no luck.
Similar threads don't point to any clear solution.
Ideas?
Before installing the ROM, did you wipe system and factory reset?
soupmagnet said:
Before installing the ROM, did you wipe system and factory reset?
Click to expand...
Click to collapse
Yes.
anotherbeer said:
Yes.
Click to expand...
Click to collapse
Since you stated you have the Blue KindleFire Logo I believe you are using the FFF bootloader? If so, cycle through the boot options and try the "repair boot mode" or something like that. Sorry, I don't have my KF in front of me to know the exact wording.
Try reinstalling a ROM again. Be sure to perform a full wipe and afterwards while still in recovery, pull your recovery log.
Code:
cat /tmp/recovery.log
Put it in pastebin and post the link.
danscxda said:
Since you stated you have the Blue KindleFire Logo I believe you are using the FFF bootloader? If so, cycle through the boot options and try the "repair boot mode" or something like that. Sorry, I don't have my KF in front of me to know the exact wording.
Click to expand...
Click to collapse
Yes -- FireFireFire, looks like v1.4a. The option at startup is called "Repair Boot Mode". Tried that, didn't change the OS not-booting situation.
soupmagnet said:
Try reinstalling a ROM again. Be sure to perform a full wipe and afterwards while still in recovery, pull your recovery log.
Code:
cat /tmp/recovery.log
Put it in pastebin and post the link.
Click to expand...
Click to collapse
(note: couple of links below, but as a new XDA forum user I'm prevented from including real hyperlinks)
Got it. Log file linked below, but grabbing the log was an interesting process by itself. I started the whole process from scratch, which a fresh install of the Kindle Fire 6.3.1 software, unrooted. After gaining root with SuperUser installed (again, using BreakDroid_0.6.5), I restarted into TWRP and grabbed the recovery log, here: pastebin.com/uxQjpdJV
Then I:
1. cleared the caches (and did a factory reset) from within TWRP.
2. installed jb-kfire-hashcode-07-13.zip.
3. while still in TWRP, grabbed the recovery log.
Unfortunately, the post-ROM-install recovery.log file is no longer a text file. May be a binary file, or an encoding my text editor cannot comprehend. I've posted that file here:
dl.dropbox.com/u/20056539/recovery%20-%202%20after%20install%20jb-kfire-hashcode-07-13.log
I'm not sure what to make of that, or even know if that is normal.
And, as you might have guessed, the device still won't boot into the OS.
Well, that's weird. I don't think I've ever seen that before.
Have you tried reinstalling TWRP?
anotherbeer said:
I started the whole process from scratch, which a fresh install of the Kindle Fire 6.3.1 software, unrooted.
Click to expand...
Click to collapse
When you are at this point do you have a working/booting KF? If Yes, try flashing to this ROM and see if you are able to get it to boot.
Also, how long are you waiting at the blank screen when it will not boot? When you clear the cache it can take a few minutes to rebuild. My OG Droid would take up to 5 minutes to show any sign of life the first time after clearing cache.
danscxda said:
When you are at this point do you have a working/booting KF? If Yes, try flashing to this ROM and see if you are able to get it to boot.
Also, how long are you waiting at the blank screen when it will not boot? When you clear the cache it can take a few minutes to rebuild. My OG Droid would take up to 5 minutes to show any sign of life the first time after clearing cache.
Click to expand...
Click to collapse
I have this exact same problem. hoping to get an answer.
Guys I have a big problem!
For about a month I have on the galaxy nexus rom slimkat + kernel dfk and until tonight I had not any problems, until this evening the phone has rebooted and the disaster happened, the boot animation was jerky and the phone has put more than 5 minutes to power, however going slow, and even after I have booted the phone is super slow, it's all jerky and unusable.
From recovery I tried to wipe system, but even if the message confirming correct operation, it really does not matter because if I reboot the phone loads the system, even if ever so slow and jerky.
I also tried to use the Nexus root toolkit but nothing, when I try to reflash stock hangs the command "writing system" and does not go forward ... I do not know what else to try.
I also tried using fastboot commands, but nothing changes ... not the operations are successful and the changes are not applied.
Please help me! Thank you very much!
Wipe system, cache, data, dalvik cache and internal.. Then flash stock factory image and then install roms
Wipe from recovery do not work.
I tried to flash from toolkit the stock factory image, but hangs on the command "writing system".
There is another way to flash it??
Yes..you can to flash another recovery with nexus root toolkit. Boot into android and enable usb debugging in dev. options, connect gnex with PC and flash recovery (cwm or twrp or philz, not STOCK) and then wipe..
h4xx0rr said:
Yes..you can to flash another recovery with nexus root toolkit. Boot into android and enable usb debugging in dev. options, connect gnex with PC and flash recovery (cwm or twrp or philz, not STOCK) and then wipe..
Click to expand...
Click to collapse
I've tried, the procedure seems to be successful but the recovery does not really change.
I also tried to flash the stock rom with odin, well after the half-hour procedure is successful, the phone has rebooted but nothing, everything remained as before, with the old rom.
I do not know what to think anymore, I try recovery, toolkit, fastboot and odin but nothing.
I came to doubt that it may be a hardware problem with the internal memory of the phone, do not you?
Thank you!
Try to boot into recovery temporary with nexus root toolkit if you can't to flash..this can help to wipe all and brick gnex
h4xx0rr said:
Try to boot into recovery temporary with nexus root toolkit if you can't to flash..this can help to wipe all and brick gnex
Click to expand...
Click to collapse
I boot into temporary recovery and i do successfuly all wipe, but when I restarted the system, nothing has changed, loaded the old rom
I do not know what to do!
If you wiped, system can't be rebooted. I really don't have more ideas
Maybe you have problem with hardware.
h4xx0rr said:
If you wiped, system can't be rebooted. I really don't have more ideas
Maybe you have problem with hardware.
Click to expand...
Click to collapse
Thanks ... I think like you!