Develop Bugs

Bricked Kindle Fire?

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

[Q] Kindle Fire Boot loop

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.

Flashed cm10.1, stuck on boot screen

I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium

stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
When you plug in the usb to the computer do you get any change in windows device manager? like an unrecognized kindle fire (yellow triangle) under usb or similar?

stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Looks like you might need to reflash. Don't forget to do a wipe/factory reset...

seecay said:
Looks like you might need to reflash. Don't forget to do a wipe/factory reset...
Click to expand...
Click to collapse
I can't get to recovery and my pc doesn't recognize the kindle, so I can't reflash
Sent from my Galaxy Nexus using xda premium

stewtang said:
I can't get to recovery and my pc doesn't recognize the kindle, so I can't reflash
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's a strange problem. Have you tried to reinstall the drivers or use a different PC? If it can get into the boot animation, you should theoretically be able to get into recovery/TWRP... Sounds like a bad flash may have happened so try a newer/older build. I hope it goes ok...

Use this to replace the the one in kfu driver folder http://db.tt/vXXeuL10 and rerun the driver bat, that will get adb going again. Try reboot recovery to enter recovery or use kfu to set your bootmode to recovery. Bootloader? fff will take you to recovery as well.

Thepooch said:
Use this to replace the the one in kfu driver folder http://db.tt/vXXeuL10 and rerun the driver bat, that will get adb going again. Try reboot recovery to enter recovery or use kfu to set your bootmode to recovery. Bootloader? fff will take you to recovery as well.
Click to expand...
Click to collapse
I replaced the file and still shows ADB status as offline and boot status as unknown. The computer makes the noise that a device is connected once the kindle reaches the CM screen but the that is it, ADB is still offline. Also, the kindle fire logo at start up is no longer blue, it has reverted to the stock orange color.

stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Click to expand...
Click to collapse
I have the same problem with CM 10.1 with the splash screen. It loads through FFF 1.4 and gets to the spinning splash screen which appears to be half off the screen and just sticks there. I used the 0102 version of the JB 4.2.1 CM10.1 SGT7 rom by twapriv. When I flashed it using TWRP 2.2.2.1 it said "successful". I try to install the 121212 Gapps zip and it wouldn't work, saying unable to unzip. However, after a reboot the splash screen does what I just mentioned.
It appears we aren't the only ones though (http://forum.xda-developers.com/showthread.php?t=2051331&page=24) according to stewtang's post. I guess I'll retry to flash an older version and see if that works. Anyone have this problem and found a fix for it?
Hah! OMG I so totally didn't realize that stewtang was the OP, LAWLEROFLCOPTEROMGWTFML...

guruizzy said:
I have the same problem with CM 10.1 with the splash screen. It loads through FFF 1.4 and gets to the spinning splash screen which appears to be half off the screen and just sticks there. I used the 0102 version of the JB 4.2.1 CM10.1 SGT7 rom by twapriv. When I flashed it using TWRP 2.2.2.1 it said "successful". I try to install the 121212 Gapps zip and it wouldn't work, saying unable to unzip. However, after a reboot the splash screen does what I just mentioned.
It appears we aren't the only ones though (http://forum.xda-developers.com/showthread.php?t=2051331&page=24) according to stewtang's post. I guess I'll retry to flash an older version and see if that works. Anyone have this problem and found a fix for it?
Hah! OMG I so totally didn't realize that stewtang was the OP, LAWLEROFLCOPTEROMGWTFML...
Click to expand...
Click to collapse
Any luck getting into recovery? If so, how did you do it?

stewtang said:
Any luck getting into recovery? If so, how did you do it?
Click to expand...
Click to collapse
I have always been able to get into recovery. However, I did find that my /system/bin/sh file and all other system files are completely missing. I have yet to fix this, as this could be some of my problems. I don't know I'm still a noob at this. I have reflashed TWRP 2.2.2.1 while in fastboot mode using a factory cable. I just bought one for $6 on ebay from a US seller. Using this cable I find that the KFU works more like it should. It actually tells what boot mode status is currently instead of just saying unknown.
I know I did something wrong or out of order when I tried to root my KF because it is very difficult to do an ADB PUSH command successfully. It takes a few reboots and then a trial and error until it works right. As for the latest 0102 update for CM10.1 and SGT7, I haven't been able to get passed the cyanogen splash screen.
I would like to know if that update includes all the files necessary to run JB 4.2.1 or is it a completely different OS altogether? Again, uber noob here.

guruizzy said:
I know I did something wrong or out of order when I tried to root my KF because it is very difficult to do an ADB PUSH command successfully. It takes a few reboots and then a trial and error until it works right. As for the latest 0102 update for CM10.1 and SGT7, I haven't been able to get passed the cyanogen splash screen.
I would like to know if that update includes all the files necessary to run JB 4.2.1 or is it a completely different OS altogether?
Click to expand...
Click to collapse
So a question for both of you. Did you do a clean install (wipe everything but SD card)? Also does it hang on the CM screen or does it endlessly reboot? Did either of you have previous ROMs installed?
When I installed CM10.1 on my friend's kf, at first that happened. I don't know what happened, but it took me a couple tries before it worked. Try redownloading the ROM and Gapps, and remember to wipe everything beforehand, and wiping cache before flashing Gapps.

jma9454 said:
So a question for both of you. Did you do a clean install (wipe everything but SD card)? Also does it hang on the CM screen or does it endlessly reboot? Did either of you have previous ROMs installed?
When I installed CM10.1 on my friend's kf, at first that happened. I don't know what happened, but it took me a couple tries before it worked. Try redownloading the ROM and Gapps, and remember to wipe everything beforehand, and wiping cache before flashing Gapps.
Click to expand...
Click to collapse
Yes. I performed a clean install and unfortunately I am unable to re-flash anything. When the kindle boots it endlessly stays on the cm splash screen and I can't enter recovery or use the kfu.
Sent from my Galaxy Nexus using xda premium

stewtang said:
Any luck getting into recovery? If so, how did you do it?
Click to expand...
Click to collapse
Looks like you may not have FFF so you probably can't get into TWRP... Have a look at this thread.
http://forum.xda-developers.com/showthread.php?t=1428428

stewtang said:
Yes. I performed a clean install and unfortunately I am unable to re-flash anything. When the kindle boots it endlessly stays on the cm splash screen and I can't enter recovery or use the kfu.
Click to expand...
Click to collapse
So for you, when you turn on from off, possibly from a hard force-restart, what do you see? The original orange kf logo? And it goes straight to the swirling cm logo?

jma9454 said:
So for you, when you turn on from off, possibly from a hard force-restart, what do you see? The original orange kf logo? And it goes straight to the swirling cm logo?
Click to expand...
Click to collapse
Yes that is what I see, but before I flashed it the kindle fire logo was blue.
Sent from my Galaxy Nexus using xda premium

I had the same thing happen to me when I flashed my kindle fire demo unit with CM10.1, it turned out to be some sort of an issue with the twrp recovery when I reflashed it with the cotr recovery that the kindle fire utility program also has as a alternate this worked just fine. I did notice that when I tried to use twrp to wipe my unit it didn't seem to fully wipe the unit. doing the same thing under cotr took longer.
The reason I think it was twrp is that no matter what version of CM10.1 I used be it a nightly or the M3 experimental build, it would still just show the distorted logo and never finish booting. this happened even after I wiped the /system and cleared cache and dalvik cache.
After I flashed cotr recovery I did the same thing again using the exact same zip files for CM10.1 and gapps and it worked this time.

I have a similar problem with you guys. My Kindle is showing the orange logo and then continues to the CyanogenMod animation where it loops infinitely. The logo is also off center, half of it is off the screen. I cannot enter the recovery mode in any way. KFU shows it as online but unknown boot status. ADB shows it as offline.
Any suggestions on how to fix it? Will I need a factory cable?

I'm in the same boat, tried soupkit in linux and no dice, windows recognize a device while the CM logo is looping but the kindle drivers or adb drivers do nothing.

andreasS2 said:
I have a similar problem with you guys. My Kindle is showing the orange logo and then continues to the CyanogenMod animation where it loops infinitely. The logo is also off center, half of it is off the screen. I cannot enter the recovery mode in any way. KFU shows it as online but unknown boot status. ADB shows it as offline.
Any suggestions on how to fix it? Will I need a factory cable?
Click to expand...
Click to collapse
yadspi said:
I'm in the same boat, tried soupkit in linux and no dice, windows recognize a device while the CM logo is looping but the kindle drivers or adb drivers do nothing.
Click to expand...
Click to collapse
In both of your cases, if you don't have FireFireFire installed which will allow you to access recovery with the power button, you need a factory cable. And remember to factory reset next time.

soupmagnet said:
In both of your cases, if you don't have FireFireFire installed which will allow you to access recovery with the power button, you need a factory cable. And remember to factory reset next time.
Click to expand...
Click to collapse
I did, I was going to sell it with CM10, I rebooted, did a factory reset, reinstalled cm.zip and gapps.zip and rebooted....lost firefirefire and stuck on CM logo. If I buy or make the factory cable, will it be easy to "revive"?
Edit: Saw it on eBay for $4.45 free shipping

[Q] Flashed Kindle Fire boots to a strange screen with rotating triangles

Hi, I have an original KF that was running v6.3.2, I am trying to get it to run JB 4.2.
I successfully (I think) rooted it using SuperOneClick
I installed FFF and TWRP using KF Utilities
It can boot into TWRP
I try to flash Hashcode's 4.2.2_r1 and TWRP seems to complete although it does stick on "Updating partition details"
When I restart it it just goes to a screen covered in weird rotating triangles.Only thing I can do is hard shut down.
I did do backup and can restore it to original Amazon 6.3.2 KF firmware. Interestingly when I do this TWRP asks me to install SuperSU, which I do.I then boots as if its a new KF, except with SU app installed.
Can anyone give me any pointers as to where I might be going wrong?
Thanks
Gordon

Bad download/corrupted file?
Wait my reading caught up with me. You say it is still booting into stock? That doesn't sound like bad firmware download after all. Sorry... I don't know then! Someone else should have a thought.
I read it once again and realize you restored stock. Lol I go with my original suggestion. Redownload and reflash.
Sent from my GT-p511x

gordonj56 said:
Hi, I have an original KF that was running v6.3.2, I am trying to get it to run JB 4.2.
I successfully (I think) rooted it using SuperOneClick
I installed FFF and TWRP using KF Utilities
It can boot into TWRP
I try to flash Hashcode's 4.2.2_r1 and TWRP seems to complete although it does stick on "Updating partition details"
When I restart it it just goes to a screen covered in weird rotating triangles.Only thing I can do is hard shut down.
I did do backup and can restore it to original Amazon 6.3.2 KF firmware. Interestingly when I do this TWRP asks me to install SuperSU, which I do.I then boots as if its a new KF, except with SU app installed.
Can anyone give me any pointers as to where I might be going wrong?
Thanks
Gordon
Click to expand...
Click to collapse
The "weird rotating triangles" is the stock AOSP boot animation. 9 times out of 10, when your device gets stuck on the boot animation, it is from not wiping data in recovery before flashing the ROM. Boot into recovery, factory reset, then reboot to see if it fixes the problem.

Pixel 2 xl stuck on white screen with G on it and status bar underneath

Phone is stuck on this white screen with the G on it and the status bar scrolling over and over. Phone is unlocked and rooted and i was having trouble installing a recovery onto it. I just spent 3 hours setting everything up. Do i have to wipe and start again?

equlizer said:
Phone is stuck on this white screen with the G on it and the status bar scrolling over and over. Phone is unlocked and rooted and i was having trouble installing a recovery onto it. I just spent 3 hours setting everything up. Do i have to wipe and start again?
Click to expand...
Click to collapse
What did you flash to cause this?? Did you try a hard restart by holding the power button down until it starts rebooting?

Tried a hard restart and same thing happens. I was trying to install TWRP using skipsoft toolkit #6 option.

equlizer said:
Tried a hard restart and same thing happens. I was trying to install TWRP using skipsoft toolkit #6 option.
Click to expand...
Click to collapse
Since I'm not familiar with toolkits, or their interface, I'll let someone else take over. Have you considered using adb and fastboot commands to accomplish your task?

I would if i knew what i was doing I just tried the wipe everything option and now it says "cant load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device"
Well i did that and i get that same message over and over again. How do i start fresh? I have the image on my computer

equlizer said:
I would if i knew what i was doing I just tried the wipe everything option and now it says "cant load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device"
Well i did that and i get that same message over and over again. How do i start fresh? I have the image on my computer
Click to expand...
Click to collapse
If you want to continue using the toolkit, I would post your problems in that thread. The folks that made it will be more qualified to help you than I could.

i went into bootloader mode and did the flash all. The phone reboots and comes back with the same message "cant load android"
I dont care what i use to get things working again. pls help.

equlizer said:
i went into bootloader mode and did the flash all. The phone reboots and comes back with the same message "cant load android"
I dont care what i use to get things working again. pls help.
Click to expand...
Click to collapse
I will try my best.
1. You have definitely unlocked_critical correct. If you haven't, you need to.
2. Have you downloaded SDK on your pc? You need this as well. You can find a link to it on Google's factory image page.
3. You have downloaded the latest factory image and unzipped it with the 7zip program.
4. Inside the SDK program, look for a file called platform tools.
5. You need to take the contents you extracted from the factory image, and place them in the platform tools folder. That includes: Radio, bootloader, the flash-all.bat file, and another large zip file that contains the boot, system, vendor and about 16 other things.
6. Put your phone into bootloader mode and plug it into the pc. Open a command prompt from the platform tools folder and type "fastboot devices" if your phone ID comes up, your good.
7. Double click the flash-all.bat file, and that should start the installation process. It will take a little while to install the OS, so be patient. If all goes well, your phone should automatically boot up.
8. I will try and find a link for all this installation stuff.
9. Good luck!
---------- Post added at 01:23 PM ---------- Previous post was at 01:16 PM ----------
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Here is a link to instructions written by one of the best kernel developers out there. Read it carefully if what I gave you doesn't make sense.

Tried it this morning and when i go to root with magisk (followed every step) i get the white screen with the G and the bar scrolling

equlizer said:
Tried it this morning and when i go to root with magisk (followed every step) i get the white screen with the G and the bar scrolling
Click to expand...
Click to collapse
Did you ever get your phone to boot up on stock system?

Badger50 said:
Did you ever get your phone to boot up on stock system?
Click to expand...
Click to collapse
Not sure how i did it but it seems to have reverted back to complete stock. Everything setup after but when it rebooted it said "this device cannot be trusted, hit the power button to continue" so i do and it seems to boot back into the phone. How do i get rid of that message?
Ive never had so many issues with a phone before.

How do i get rid of that message?
once you had the Bootloader unlocked in this phone it will display that message in every boot, there is no way to get rid of it at this moment.

equlizer said:
Not sure how i did it but it seems to have reverted back to complete stock. Everything setup after but when it rebooted it said "this device cannot be trusted, hit the power button to continue" so i do and it seems to boot back into the phone. How do i get rid of that message?
Ive never had so many issues with a phone before.
Click to expand...
Click to collapse
A lot of trouble people have with these phones has to do with the A/B partitions, glitches in cables, sdk, PC's, ghosts in the machine, and users not taking the time to read and learn what to do. Anyway, glad you got it going. Your welcome.

Everything else worked except for the rooting with magisk. when it patches the image using manager 5.4.3 it says its downloading version 14.0 not 14.5. I go to flash the patched boot img then it just reboots to the white screen with the G and it hangs there till i shut it off.

equlizer said:
Everything else worked except for the rooting with magisk. when it patches the image using manager 5.4.3 it says its downloading version 14.0 not 14.5. I go to flash the patched boot img then it just reboots to the white screen with the G and it hangs there till i shut it off.
Click to expand...
Click to collapse
Manually download 14.5 and flash it in twrp. Or, take the stock boot.img, place it on your phones internal storage, open magisk, hit install, and select patch boot (I think) Then take the patched_boot.img and flash that with fastboot. Either way should give you root.

I already said I patched it using the magisk I installed but when I flash it I get the G on the white screen. I can't even get twrp to stick. This was all using 8.1 but now I'm on 8.0. I guess I'll try again?

equlizer said:
I already said I patched it using the magisk I installed but when I flash it I get the G on the white screen. I can't even get twrp to stick. This was all using 8.1 but now I'm on 8.0. I guess I'll try again?
Click to expand...
Click to collapse
What twrp version are you using? So, you can fastboot the twrp-3.1.1-beta2-taimen-img but then are unable to flash the twrp.zip once you enter temporary twrp?

I just downloaded twrp 3.1.1 beta 2 taimen.img and the zip
how do i fastboot the img?
then from there do i flash magisk 14.5.zip then reboot and install magisk manager 5.4.3 then check for root?

equlizer said:
I just downloaded twrp 3.1.1 beta 2 taimen.img and the zip
how do i fastboot the img?
then from there do i flash magisk 14.5.zip then reboot and install magisk manager 5.4.3 then check for root?
Click to expand...
Click to collapse
Go to fastboot and type: fastboot boot twrp-3.1.1-beta2-taimen.img
That should immediately take you temporary twrp where you then flash the twrp.zip, and then flash your magisk zip. That should also install the magisk app as well.

it takes me to the screen where it says "this devices cannot be trusted" so i hit the power button then it just reboots into android 8.0. I appreciate all the help