Being a total noob, I am happy to report that my KF1 is now running CM10 (Android 4.1.2):
http://forum.xda-developers.com/showthread.php?t=1778010
[ROM] CM10/SGT7 for the Kindle Fire [20121224] [Linaro]
Some problems I ran into:
1) Installed Kindle Fire Utility (KFU) and drivers. KFU could not find Kindle Fire.
SOLUTION: Make sure Kindle Fire is disconnected from computer before installing drivers. If necessary, completely uninstall drivers, restart system, then re-install. Afterwards, you can connect your Kindle and it will should up on KFU.
2) Installed a custom rom using TWRP. Upon reboot, rom was stuck at loading screen.
SOLUTION: I didn't do a factory reset. In the Wipe menu on TWRP, make sure you do a Factory Reset, Cache Wipe, Davlik Cache Wipe, and System Wipe.
3) AOSS Keyboard kept force closing.
SOLUTION: Make sure you're running the correct version of Google Apps (GAPPS). I was installing GAPPS 4.2.x. It should have been 4.1.x for this particular rom.
I also recommend not restoring system data from titanium backup when changing roms. I did that when downgrading from a cm10.1 rom to a cm10 rom and it just got stuck at the cm splash screen until I did a factory reset.
Sent from my Amazon Kindle Fire using Tapatalk HD
Robb Flynn said:
Being a total noob, I am happy to report that my KF1 is now running CM10 (Android 4.1.2):
http://forum.xda-developers.com/showthread.php?t=1778010
[ROM] CM10/SGT7 for the Kindle Fire [20121224] [Linaro]
Some problems I ran into:
1) Installed Kindle Fire Utility (KFU) and drivers. KFU could not find Kindle Fire.
SOLUTION: Make sure Kindle Fire is disconnected from computer before installing drivers. If necessary, completely uninstall drivers, restart system, then re-install. Afterwards, you can connect your Kindle and it will should up on KFU.
2) Installed a custom rom using TWRP. Upon reboot, rom was stuck at loading screen.
SOLUTION: I didn't do a factory reset. In the Wipe menu on TWRP, make sure you do a Factory Reset, Cache Wipe, Davlik Cache Wipe, and System Wipe.
3) AOSS Keyboard kept force closing.
SOLUTION: Make sure you're running the correct version of Google Apps (GAPPS). I was installing GAPPS 4.2.x. It should have been 4.1.x for this particular rom.
Click to expand...
Click to collapse
Good job. Glad it worked out for you.
A note about solution #1:
The problem in this case isn't so much the drivers, as many (including I) had once believed. The problem is the stock bootloader itself. From what I understand, fastboot shouldn't require drivers to work properly anyway. I'm guessing, the stock bootloader (Kindle Fire logo) isn't the same bootloader the device had in it's infancy and this is causing some very confusing problems for a lot of new users.
For one, the command "fastboot devices" will never show a device connected in fastboot mode. And, when you send any other fastboot command, you'll see it hang at "<waiting for device>", indefinitely. * The solution for this, is to send the command with the device shut down completely and then turn the device back on (this is why it worked in your case). Then, as the device boots up again, fastboot will detect the device and continue with whatever process was waiting for the device. KFU uses the same fastboot commands to check if a device is connected (fastboot devices) and install FFF and TWRP (fastboot flash...), therefore the solution is still the same.
That's not to say the bootloader is always the problem. The stock boot animation can easily be confused with the stock bootloader splash screen, but that's another subject altogether.
I hope this helps to clear up some confusion as to what is actually happening when fastboot doesn't seem to be working properly.
Once you've installed your apps and got your KF running smoothly with your new ROM, reboot into TWRP and do a backup. I usually backup Data only. I keep the ROM and the GAPPS on my KF's SDcard so if I ever need to reinstall, I can do a clean wipe (the caches, factory reset, system), install the ROM and GAPPS, and restore my Data from backup.
I also recommend backing up Data regularly and testing your Data backups.
I strongly recommend twa_priv's CM10.1 rom. I use it 2 Kindle Fire's that my kids have.
Today he added hashcode's new Kernal tweaks, and the battery drain in standby (deep sleep) is unbelievable now! My daughter's Fire is getting about -15 drain when sleeping now, it was getting about -35 before todays update, and honestly I thought that was pretty good. Now ita amazing.
(I use battery monitor widget from 3c to check battery drain)
Related
So I used TWRP to install CM7
I ran backup 1st
I installed CM7
I wipe the cache and dalvik cache
I rebooted
Everything worked
Well I wanted to test the backup and load that back on, it said it was complete, but I my kindle keeps restarting to TWRP whenever I restart.
Can someone help me out here?
Thanks
Could be a corrupted backup. Try re flashing CM7 and see if it boots. If you want to go back to stock if the back is corrupt twrp has that option to download the stock update.zip.
Nevermind I found the steps
How to solve boot loop issue on Kindle Fire TWRP 2.0?
Plug in USB cable to Kindle Fire on TWRP Recovery mode.
Bring up Command Prompt.
Key in adb shell.
Key in idme bootmode 4000.
Finally, key in reboot.
That’s it.
^^ This post saved my Kindle. Thank you 4000 times!
Yeah came across that looking for help.
six3onei said:
So I used TWRP to install CM7
I ran backup 1st
I installed CM7
I wipe the cache and dalvik cache
I rebooted
Everything worked
Well I wanted to test the backup and load that back on, it said it was complete, but I my kindle keeps restarting to TWRP whenever I restart.
Can someone help me out here?
Thanks
Click to expand...
Click to collapse
This was one of the main reasons that I made this guide
http://forum.xda-developers.com/showthread.php?t=1417234
OK, I have really screwed the pooch on this.
In attempting to install the Unofficial CM9 rom, I have rendered my Xoom totally unusable.
What I did.
* Unlocked Xoom
* Rooted Xoom
* Attempted install of CM9 from here
* It failed, or I thought it did. It would start booting with the CM9 splashscreen, but that was all that would show. It would never complete booting.
* Tried to rollback another rom. Ended up mistakenly installing a rom that was not 4G/LTE, so no mobile data worked.
* Found a 4G rom and began attempts to install it.
What my problem is now.
* Device will not boot past the red M screen. (it stayed on that screen all last night until the battery finally died).
* Device will not allow me to use ADB because I can't unlock it.
* I can get to fastboot, but when attempting to unlock the xoom it does the following.
- Shows unlock warning
- will respond that it's unlocking the device
- will eventually complete and reboot
- On reboot, it will completely reboot, but it acts like a fresh install of the OS has been done (have to do the setup steps again)
- after doing the setup, ADB fails to be able to flash items over to the device as the device acts like its still locked.
What I need help with.
* How to unlock the device so I can flash using this thread, post 2
Thanks for everyone's/anyone's help on this.
Back running again
I was able to get the tablet running again.
Downloaded the HLK75D revision from the Motorola Developer's site and used Fastboot to flash the 4 components to the device.
Now to start over.
Yep, I am hardheaded.
Hope this helps others.
coolbeans8 said:
I was able to get the tablet running again.
Downloaded the HLK75D revision from the Motorola Developer's site and used Fastboot to flash the 4 components to the device.
Now to start over.
Yep, I am hardheaded.
Hope this helps others.
Click to expand...
Click to collapse
Well, what will you do differently this time? We all learn from our mistakes. Good luck.
How I did it this time.
After flashing the Moto original distro, I did the following to get the CM9 install running.
1 Using fastboot, flashed the CWM recovery onto the device.
- "recovery-clockwork-4.0.0.4-stingray.img"
2 Then rebooted to the interface and connected to laptop.
3 Copied over the "Update.zip" and used the "Cornea" tools to reboot into Recovery.
4 In recovery installed the "Update.zip" which gave me Root.
5 Rebooted to the OS.
6 Connected the tablet to windows
7 Copied over the CM9 zip "update-cm-9-20120403-SNAPSHOT-stingray-signed.zip" and the GAPPS zip "gapps-ics_tablets-rogue_v7.1-signed.zip" to SD card
8 Installed CWM (both the base app and the Premium upgrade
9 used CWM to reboot to recovery
10 In recovery cleared all the data
11 In recovery cleared all the cache
12 In recovery installed the CM9 zip
13 In recovery installed the GAPPS zip
14 Prayed. Seriously,
15 rebooted.
16 Did a happy dance.
That's it.
Hope it's helpful to others.
Congratulations! Enjoy!
I received my new Nexus 7 today (although I'll be sending it back for RMA replacement due to defective/blown speakers, but that's another discussion) and wanted to revert my Kindle Fire to stock to give to my parents. I had been previously running a vanilla build of CM9.
I downloaded Amazon's latest software update, renamed it update.zip, and copied it to my device. Using TWRP, I installed the update, wiped cache and dalvik. My Kindle rebooted (now without FireFireFire bootloader/recovery), however, once it starts I get multiple error messages as follows:
android.process.acore has stopped unexpectedly
com.android.providers.calendar has stopped unexpectedly
My only options are to force quit. Still, even if I don't touch the device and let it be, it will reboot itself withing a minute or so. There must be something amiss with how I went back to stock.
Any help with getting the device back into some working form? Or am I out of luck?
Nevermind; i managed to get FireFireFire and TWRP back on. Now to look for an edited Amazon ROM or perhaps a jellybean/CM10 rom...
when flashing the stock rom from cm9, you should do a full wipe ( system, factory reset, cache, dalvik) in TWRP
Sent from my Amazon Kindle Fire using xda premium
Josepho1997 said:
Try to root it again with KFU, and then redownload and reflash the update. Or turn your kindle completely off and then, in KFU, press install TWRP, and then turn your Kindle back on, and see if it can get into fastboot and install TWRP. Then turn it off, open off KFU, and press install FFF. Now turn it back on, and see if it installs FFF. If so, then just redownload and reflash the update.zip
Or install GR9 Modaco.
Click to expand...
Click to collapse
managed to install FireFireFire and TWRP during the brief window before the device rebooted. and thanks for the suggestion of GR9 Modaco
OK, this mat have been asked many time, but none of the thread I found applies to my case.
My device is Nexus 7 16Gb Wifi, the internal ROM is stock 4.1.2 (I cannot use 4.2.2 because of a backward compatibility issue for an app I have to use)
The recovery is the latest TWRP 20030227 version, with MultiROM bootloader 4.18. An armhf raring build of Ubuntu is also installed in the internal sdcard and all have worked fine until I tried to flash a alternative kernel.
The new kernel I flashed is the M-kernel mr1.1. I flashed it by booting into recovery and chose to install the M-kernels zip file from there. After I have got a kernel flash successful message I chose to reboot system. Then the weird thing began: at first the device seems to be booting because I saw the usual Google logo and then it turned into the boot animation with a colorful cross in the middle of the screen. But then on nothing seems to follow. The boot animation persists forever. I hve also noticed that during the initial boot it somehow skipped the step of choosing ROMs as usual (because I have Ubunto installed), so I also lost the choice of booting into Ubuntu.
I have to press the power button for more than 10 seconds to power off the device. Then I tried to boot into fastboot mode and recovery mode, both works file, so it still looks not bad. I have kept a copy of my working patched kernel which is kernel_kexec_41-2.zip. Booting into recovery and using the command
adb push kernel_kexec_41-2.zip /sdcard/
I managed to copy this zip into the device. Then, once again, I tried to flash this old kernel by installing it in the recovery. The installation exited with a success. However, when I tried to reboot the device, it is still stuck on the boot animation screen. No choose ROM screen either. So, I am totally lost. Can anybody give some hint on where I was doing wrong and how can I get my device working again without totally reflashing a stock rom and loosing all data I have installed previously? Many thanks.
Any helps please.
Let me update the situation. Tried to wipe cache/Dalvik and reflash the kernels (both the original and the newly downloaded omega3 kernel, both changed nothing -- always stuck in the boot animation. Tried MultiROM->Advanced->Inject curr.boot.sector, the screen allowing to choose rom reappeared and from there Ubuntu boots correctly. However, If the internal ROM is chosen in that screen, the device reboots and stuck in the boot animation screen again.
How about if you make a backup?
Then - no matter what follows - no matter what experiments you do - you can always restore just the /data partition. Or any of the other partitions.
Frankly, you should have done it already, but nothing is stopping you from doing it now.
Backups give you power - and freedom - to experiment with very few risks.
good luck.
Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.
instanton said:
Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.
Click to expand...
Click to collapse
Had it happened that you still had a bootloop after dirty-flashing /system and/or boot (without doing the custom recovery "factory reset" wipe of /data exclusive of /data/media), a backup can still save your bacon: it can be restored and then manually:
- all system app related /data/data/ and /data/app-lib/ folders removed
- all system app updated .apks in /data/app/ deleted
- wipe dalvik-cache
This leaves all market apps and their data intact while starting from scratch from with the base ROM's system apps. Probably doing that reduces the chances of boot loops.
UID mismatch troubles can still occur if you are coming from a "debloated" ROM and dirty-flashing something like a stock ROM (where there are more system apps than in the prior ROM which generated the /data partition); but I think that TWRP's "fix permissions" should take care of that.
But anyway - backups give you flexibility.
Hi:
I unlocked and successfully rooted my Nexus 10 (JB 4.3). Also have TWRP 2.6.1 installed. It worked fine with the stock rom rooted. Then I tried to install Custom Rom.. Paranoid Android..3.99. Everything went smooth until.I got stuck in BOOTLOOP. Reading the forums posts, I went back to recovery and wiped cache/dalvik cache.. and rebooted.. This time it proceeded with the ANDROID IS UPGRADING...but at the end of this once I got the lock screen..the dreaded UNFORTUNATELY SYSTEM UI has STOPPED window pops up and this is where I am stuck.
I have since then booted into recovery and cleaned cache and reinstalled custom roms.. PA, STOCK, CM 10.2 many times but of no use. The tablet is stuck at the SYSTEM UI HAS STOPPED.
Is there any way to fix this... ? ANY HELP WILL BE GREATLY APPRECIATED
I would be glad to get back to FACTORY SETTINGS if I can. Note that I can push files from my MAC using "ADB" and then use recovery.
THANK YOU IN ADVANCE FOR YOU ALL.
Edit: Well guess what... I did not see FACTORY RESET in TWRP all along (BEING DEFAULT ACTION) and was just wiping cache/dalvik cache before rebooting. FACTORY RESET is a life saver.... it works. Hope this helps others in similar situation. I am back on CM 10,2 and running.
Excellent. That was gonna be my suggestion, but glad you got it figured out.
Sent from my Nexus 10
vicky4112 said:
/snip
Click to expand...
Click to collapse
In the future, learn to use fastboot. ADB only helps you if you have a custom recovery that can run ADB onboard, which isn't always the case (for example, if you kill your internal storage). What could have saved you here would have been:
fastboot wipe userdata
fastboot wipe data
fastboot update -w /path/to/stock-image.zip
It's harder to kill fastboot on Nexus devices, so it's worth learning.
Rirere said:
In the future, learn to use fastboot. ADB only helps you if you have a custom recovery that can run ADB onboard, which isn't always the case (for example, if you kill your internal storage
Click to expand...
Click to collapse
Alternatively, TWRP can mount an otg-usb device. Totally saved my tush the other night.