I installed the newest (5-17-2013) nightly using twrp and now my kindle 2 is stuck at the cm10.1 splash screen. Yes, I wiped factory and system; cache and davlik. Tried wiping cache and davlik, then just davlik after flashing 20+ times. I tried searching and tried many things but had no success. Anyone know how to get around this? This is the only rom on my kindle right now so I can't flash it with anything else. I saw that someone else on the CM10.1 Official rom page said 5-17-2013 got them stuck on boot logo as well. Is it me, or the rom?
Eric Vaughn said:
I installed the newest (5-17-2013) nightly using twrp and now my kindle 2 is stuck at the cm10.1 splash screen. Yes, I wiped factory and system; cache and davlik. Tried wiping cache and davlik, then just davlik after flashing 20+ times. I tried searching and tried many things but had no success. Anyone know how to get around this? This is the only rom on my kindle right now so I can't flash it with anything else. I saw that someone else on the CM10.1 Official rom page said 5-17-2013 got them stuck on boot logo as well. Is it me, or the rom?
Click to expand...
Click to collapse
5-17-2013 had issues, so flash an earlier one first to make sure everything is OK. I'm currently on 15.
You will probably have to push a rom to the KF2 using adb, oh, and always make sure you keep at least 2 versions of the nightlies on your device, one you know works and the newest one. It makes life so much easier.
adb push cm-10.1-20130515-NIGHTLY-otter2.zip /sdcard/Download
chronicfathead said:
5-17-2013 had issues, so flash an earlier one first to make sure everything is OK. I'm currently on 15.
You will probably have to push a rom to the KF2 using adb, oh, and always make sure you keep at least 2 versions of the nightlies on your device, one you know works and the newest one. It makes life so much easier.
adb push cm-10.1-20130515-NIGHTLY-otter2.zip /sdcard/Download
Click to expand...
Click to collapse
Sadly I had to learn this the hard way. I didn't have another version on my kindle. adb was a pain because it shows up as "Other devices> Kindle Fire 2" with a yellow triangle in Device manager. Luckily I was able to select "Update Drivers" and when prompted to select from a folder or select from other known drivers I simply selected "Kindle Fire" then "ADB Interface" and installed that. Then sideloading another zip was a cinch from TWRP. :victory:
Thanks for the input
Related
I rooted my kindle fire 6.3.1 using the utility and installed twrp, everything is fine , once i install a custom rom it wont boot. No matter what rom Installed . it will turn on to the black and blue kindle screen then go black and nothing happens. Or the rom will boot but hangs at the boot image.
Did you "factory reset" before flashing the rom?
I'd download the newest version of kfu, then re-flash twrp , then fire fire fire, put the from on the SD card, then factory reset, wipe both caches, then install from and wipe caches again
Sent from my Galaxy Nexus using XDA Premium HD app
chris_m128 said:
I'd download the newest version of kfu, then re-flash twrp , then fire fire fire, put the from on the SD card, then factory reset, wipe both caches, then install from and wipe caches again
Click to expand...
Click to collapse
There is no reason to re-flash twrp and there is definitely no reason to re-flash FireFireFire unless absolutely necessary. Flashing a bootloader is potentially dangerous and shouldn't be done just for the hell of it.
The OP has one post on XDA, this one; which leads me to believe he was unaware of or has overlooked the importance of performing a factory reset before flashing any new rom.
[Edit:] That wasn't intended to sound so brash, but you get the point.
I get the point that you think you know a lot more than you do.
Edit: that was intended to sound exactly like it does
chris_m128 said:
I get the point that you think you know a lot more than you do.
Edit: that was intended to sound exactly like it does
Click to expand...
Click to collapse
I tried to convey to you that my intention was not to be rude, yet you respond with unnecessary hostility. What exactly do you expect to accomplish with this? Change my mind? Hurt my feelings? Cause me to be any different than I am? I'm guessing it's probably not going to happen.
forgive me o' mighty one
This looks like exactly what I am after as I need to send my Kindle back to Amazon and I'm hoping they won't notice I've rooted etc Will this be enough? I rooted using KFU and subsequently did a factory reset but I still need to get rid of TWRP right? I have found the fastboot command for wiping the recovery partition but is there nothing stock in there?
wryel said:
This looks like exactly what I am after as I need to send my Kindle back to Amazon and I'm hoping they won't notice I've rooted etc Will this be enough? I rooted using KFU and subsequently did a factory reset but I still need to get rid of TWRP right? I have found the fastboot command for wiping the recovery partition but is there nothing stock in there?
Click to expand...
Click to collapse
It'll work. You don't need to try to wipe recovery or the bootloader yourself, and you shouldn't, either.
Just follow the steps there, and be particularly wary of step 3. If you don't wipe everything properly, you'll probably end up with a soft brick.
The moment the stock update.zip is installed and you reboot, the KF will pretty much be the same as brand new.
Thanks! Went through real smooth and didn't even get the error it mentions.
wryel said:
Thanks! Went through real smooth and didn't even get the error it mentions.
Click to expand...
Click to collapse
What did you wipe
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
I just followed the instructions on that guide, wiping the two caches and then doing a factory restore. The only other thing I did was to delete a TWRP folder that was leftover.
i have a droid x2 that i have rooted and switched roms on numerous times, as well as sbfing becoming one of my close friends. not sure what to do with the 3 different pages on rooting applications and methods. does a link to actual step by step instructions on how to root and intall roms exist? last night i rooted and installed twrp using the utility, but could not get it to boot for anything. held power down and all i get is a normal boot . when i went to install AOKP , i used the utility to get into twrp RIGHT after putting FFF on it. i flashed the rom and gapps after wiping data, and i got a blank screen for an hour. i found a tutorial on mounting sd card through twrp and saved it. my question is what is the proper way to root 6.2.2? and will installing roms through working twrp actualy work? if so how do i get twrp to work? thanks in advance guys.
clarity
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Lorenzo VonMatterhorn said:
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
Click to expand...
Click to collapse
Yes, you use adb but it instructs you what to type.
Sent from my Galaxy Nexus using xda premium
pyroscott said:
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Yes the first step should be root... which in my case also installs twrp...
If you're planning to install a custom ROM, there's no point in rooting. FFF and TWRP are more than enough.
aokp
ok well i rooted. and now twrp works flawlessly. but when i try to flash aokp, i wipe data/factory reset, install aokp and then gapps, i get nothing but a black screen after rebooting. after waiting a minute or two, i rebooted into recovery and restored a backup. am i doing something wrong? i started on 6.2.2 if that helps at all.
You should -always- wipe cache and dalvik-cache when flashing ROMs.
When you're upgrading the same ROM from a lower version to a newer one (for example, going from gede 1.65 to 1.7) you may skip factory reset, so long as there isn't a major change (going from normal to linaro, for example).
However, it is good practice to let Titanium Backup handle all of your /data backups and just factory reset every time as well.
You have the two most important steps done.
1. You have TWRP installed and you can boot into it. That is one of the hardest steps it appears.
2. You did a backup before doing anything else.
As Dasanko said you also need to wipe cache and dalvik-cache. When I do a new rom I wipe data, system, cache and dalvik-cache.
Titanium Backup (TiBu) is also awesome to restore your apps. However, you will need to install TiBu to use it to restore other apps. Some ROMS have it installed already and some don't. If you don't have access to TiBu from the Rom your are flashing you will need the GApps installed to get the Play Store. You can then download TiBu be able to restore your chosen apps.
Lorenzo VonMatterhorn said:
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Click to expand...
Click to collapse
Yes, you should get the screen with the triangle. I would try flashing the recovery again
Sent from my Galaxy Nexus using xda premium
also when you are installing a new rom I always wipe system so you dont have any errors because that is where the old rom is located. btw cm9 and aokp are both really nice on this device
I've looked around to resolve this issue on these forums, specific to my device and problems, however to no avail. I have seen similar issues but with these kinds of problems its better to make a thread/post yourself.
This is what I'm referring to directly.
http://forum.xda-developers.com/showthread.php?t=1778270
Before I started I had made my phone completely stock and the About Device Status said Normal and I also had no Flash Counts.
Alright so here we go.
The process I took is as follows:
1. Using Rom Manager from the Google Store I flashed the recovery.img file that was listed in the link I provided above. (recovery-clockwork-touch 6.0.2.3-d2att.img to be exact)
2. Placed the .zip file, from the link above. (cm-10.0.0-d2att.zip - stable version), in my internal sd.
3. Then placed my phone in recovery mode using adb shell from my computer.
4. Made sure the Recovery version was the correct one at the top of the screen. 6.0.2.3
5. Installed using .zip from the Recovery mode.
6. Install/update was successful.
7. Reboot device
8. Samsung Logo appears first, then Samsung Galaxy SIII, then CyanogenMod with the nice blue circle and animation appears last.
This is where my phone just sits there with the animation circling forever. I dont understand what went wrong. I have re-done this numerous times and with different combinations of recovery.img's and CMd2att versions.
The only thing I can do is fix the issue by going back to stock using ODIN. The phone is fine but I dont want stock obviously.
Thanks in advance and sorry if I missed a thread just like this one, but I doubt it.
Reboot into recovery and clear data (might be listed as "factory reset") and cache.
smelenchuk said:
Reboot into recovery and clear data (might be listed as "factory reset") and cache.
Click to expand...
Click to collapse
Whoops forgot to mention I did that cleared cache and that other one that starts with a 'd'
thanks for the fast response though
smelenchuk said:
Reboot into recovery and clear data (might be listed as "factory reset") and cache.
Click to expand...
Click to collapse
Wow, I did it again and I cant believe it but it worked. Thanks haha
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
mhport2 said:
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
Click to expand...
Click to collapse
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
Click to expand...
Click to collapse
No, I did not flash a new bootloader, I followed the FTL steps he posted except for wiping cache and davilk cache.
Instructions:
1) Download ROM:
Dev-Host: http://d-h.st/s7b
2) Download Gapps:
Dev-Host: http://d-h.st/UDe
Source: http://forum.xda-developers.com/show...38&postcount=1
*** Goo.im Gapps for 4.2.2 did not work. Use other Gapps at your own risk! ***
3) Download SuperSU:
Dev-Host: http://d-h.st/h3h
4) Backup Device
5) Flash the zips in order
Click to expand...
Click to collapse
jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
Click to expand...
Click to collapse
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
jsgraphicart said:
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
Click to expand...
Click to collapse
The OP is using TWRP which is what I used and I got no such options.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
mhport2 said:
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Click to expand...
Click to collapse
It could be, I can't speculate on that as I have only downloaded the files to my PC.
jaizero said:
The OP is using TWRP which is what I used and I got no such options.
Click to expand...
Click to collapse
Oh. I never use TWRP. I have never liked it. I dont know how TWRP handles stuff then.
jaizero said:
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
Click to expand...
Click to collapse
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
mhport2 said:
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
Click to expand...
Click to collapse
My next suggestion is going to be a /system wipe. Not sure If you want to go this route but if you choose to (at your own risk)..
Boot into recovery
Factory reset
wipe dalvik/cache
wipe /system
install ROM
install Gapps
install SU zip
reboot
As a warning if this doesn't work you will not have a booting system. You will be forced to reinstall an older factory image via fastboot.
Do you have a 4.2.2. ROM saved on your SD card that you can install? It might be a good idea to get a booting system first before trying anything else from this point on.
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
mhport2 said:
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
Click to expand...
Click to collapse
did it work? i am also having this problem but when i go into my bootloader it tells me my device is tuna even though its a toro if that matters. and to make things wierder when i try to adb it says i dont have fastboot even though i had it less than 3 hrs ago when i was flashing the rom.(supernova) it worked then i shut off and rebooted the next morning and i just get stuck at the google logo. if anyone can help me i would appriciate it.