Hello all.
I recently started modifying my 2 Kindle fire HD 7". I tried to install Hashcode's latest rom. Everything seems to go fine, but in the end the rom is stuck at the cyanogen loading logo.
I followed the following steps :
1 / brick my kindle
2 / Buy a factory cable, go to fastboot, use Kindle First aide to restore my kindle to rooted 7.2.3
3 / Follow Hashcode's steps to install TWRP
4 / My kindle can now boot normally, or in recovery. Copy the 2 latest roms from hashcode and gapps on the memory.
5 / in recovery, wipe -> cache , davlik cache, then system
6 / install the latest rom
7 / Re-wipe cache and davlik cache
8 / reboot system.
right after reboot, I see the cyanogen spinning logo for a while.
Then "optimizing aplications xx/58"
Then reboot.
Cyanogen logo again, for a while
Then, sometime, the lock screen very briefly shows up. For a short second. And before I can do anything, it reboots again.
I tried both 514 and latest build from hashcode. They both behave the same way.
Sadly, I did not save an amazon rom on the SDCARD (silly me) so I can't try to go back to amazon stock. Unless I restore the whole thing from kffirstaide, but it's taking so long I'd really like an alternative.
Funny thing is, on my first kindle (I have 2) I had the same problem 2 or 3 time. I fiddled with it a bit, I think I re-installed the rom without wiping anything, and it worked. And I am very happy with the rom.
But I have been trying to do the same with the 2nd one for 2 days, and nothing seems to work.
So, did this happen to anyone before ?
What are the exact steps I should take to flash a rom : what should and shouldn't be wiped, in what order ?
Is it possible that TWRP was incorrectly installed ?
Also, I can't seem to either mount usb storage when in recovery, or make sideload works. Did anybody manage that with a KFHD7 ? How ? It could allow me to try amazon stock rom without restrating the whole process ...
Thanks in advance for any help.
kaceps said:
Hello all.
I recently started modifying my 2 Kindle fire HD 7". I tried to install Hashcode's latest rom. Everything seems to go fine, but in the end the rom is stuck at the cyanogen loading logo.
I followed the following steps :
1 / brick my kindle
2 / Buy a factory cable, go to fastboot, use Kindle First aide to restore my kindle to rooted 7.2.3
3 / Follow Hashcode's steps to install TWRP
4 / My kindle can now boot normally, or in recovery. Copy the 2 latest roms from hashcode and gapps on the memory.
5 / in recovery, wipe -> cache , davlik cache, then system
6 / install the latest rom
7 / Re-wipe cache and davlik cache
8 / reboot system.
right after reboot, I see the cyanogen spinning logo for a while.
Then "optimizing aplications xx/58"
Then reboot.
Cyanogen logo again, for a while
Then, sometime, the lock screen very briefly shows up. For a short second. And before I can do anything, it reboots again.
I tried both 514 and latest build from hashcode. They both behave the same way.
Sadly, I did not save an amazon rom on the SDCARD (silly me) so I can't try to go back to amazon stock. Unless I restore the whole thing from kffirstaide, but it's taking so long I'd really like an alternative.
Funny thing is, on my first kindle (I have 2) I had the same problem 2 or 3 time. I fiddled with it a bit, I think I re-installed the rom without wiping anything, and it worked. And I am very happy with the rom.
But I have been trying to do the same with the 2nd one for 2 days, and nothing seems to work.
So, did this happen to anyone before ?
What are the exact steps I should take to flash a rom : what should and shouldn't be wiped, in what order ?
Is it possible that TWRP was incorrectly installed ?
Also, I can't seem to either mount usb storage when in recovery, or make sideload works. Did anybody manage that with a KFHD7 ? How ? It could allow me to try amazon stock rom without restrating the whole process ...
Thanks in advance for any help.
Click to expand...
Click to collapse
I personally never had this happen to me but it seems you forgot to flash gapps and the rom seperately. If you need a backup of the amazon os I have one because, I switch every 15min to check performance. I can give you a twrp backup it will work though. Also what guide did you use because I think you should have used this one http://forum.xda-developers.com/showthread.php?t=2271909 I used to root and install CM10. I encounter the same problem when trying to mount to the computer in twrp, its an issue, but not the main problem. Is it a problem currently or is it working? But use that guide and tell me how it works for you.
I flashed ONLY the rom ... the gapps where on the memory for later flashing.
But guesss what, I just randomly succeded.
Here is what I did
- Wipe cache / davlik cache / system / factory reset (in that order)
- Flash EVERYTHING at the same time. Meaning a rom (the 514 from hashcode) gapps, and the 2 zip for acid audio. I put them all in install before flashing.
- Do NOT re-wipe anything after flash. Just reboot
And it worked ...
Related
Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help
If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?
Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)
when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse
Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.
Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App
Hello everyone,
I just tried to install the stable version of CM 7.2 (cyanogenmod) and I kind of have a little problem: after rooting the device as described by iProHackr in one of his videos on youtube (Unlock Root 2.4.2 did not work for me), I used the Clockworkmod Rom Manager, downloaded from there the stable version of CM 7.2 and started the installation. The Rom Manager asked me before, if I wish to do wipe the cache and dalvik cache, as well as backup the current os. I selected all options and then the installation started normally.
After some time, the phone rebooted (as part of the installation), but it's stuck at the LG boot logo. I can see the LEDs blinking, but nothing has happened for aprox. 2 hours. The phone does not boot.
What should I do next? Should I reboot in recovery mode and try to repeat the procedure? If yes, how do I boot into recovery mode?
Thanks in advance.
Problem solved. I don't know what the problem was, but I made the same steps one more time, wiped the data and cleared the cache, installed the cm 7.2 again and after a couple of minutes, the phone started successfully.
So this morning I decided to get myself a new ROM on my optimus 2x. After 2years with CyanogenMod7, I was starting to get more and more problems, so I went for it... my 2nd lifetime rom installation.
I thought I understood it all good.. decided to go with ParanoidAndroid CM10 (http://forum.xda-developers.com/showthread.php?t=2097807). I followed pengus's instructions thoughtfully.
1. Copied the ROM .zip, the gapps .zip, and the kernel .zip.,
2. Factory reset, clear cache, dalvik, etc..
3. Booted the phone in recovery, and installed the 3 .zip package in the order I just mentioned (at step1)
After rebooting my phone would keep booting with a new and fresh version of Cyanogenmod 7.. for some reason. I remade the operation a couple times and it would always get my in cyanogenmod (wtf?). Now, after a couple hours of messing around, I installed back nvflash and tried other loaders : cwm 5.0, cwm 6.0, twrp 2.5.0..
Eventually after the usual clear cache / factory reset, unpacking zip files, my phone stoped rebooting in cyanogenmod7, but then it would just get stuck with the "LG" logo forever....
Now, I've taken my ENTIRE day off trying to figure this one now. I've been at it since 8hours more or less, and now I'm expecting calls and I'm out of phone. The whole experience has been very frustrating.... and I'm out of solutions here..
Hopefully this is just a newbie mistake (cuz I'm still kinda newbie in the whole rooting experience). Plz help...
something I don't understand :
when using twrp 2.5.0 as recovery, after I did a full wipe, and fresh installation, just after I click reboot now. it says that it appears my phone is not rooted, and that I can click yes to install SuperSU.. sometimes I click YES, sometimes I don't ... both action don't change the fact that my phone gets stuck at the LG logo.
So turns out I had a gingerbread partition and was trying to install an IceCreamSandwitch version of android.
With All-In-One-Toolkit, I was able to fix the partition and all.... wow all my day because of this ;(
Hallo together,
I seem to have done something wrong while trying to flash the rom "RazRi_JB_X-2014-Jul-16".
Here is what i did:
- Unlocked to bootloader using official Motorola homepage
- Flashed CWM (non-touch) recovery using "Recovery Flasher by LeBobo v1.7", USB-Debugging was on
- Rebooted into bootloader and flashed "RAZRiRoot2" to prevent Stock-ROM from overwriting the recovery
- Tried to install the Custom ROM using CWM, but it fails to wipe cache (stuck on line "Formatting /cache")
Because it didn't work, i tried to reset everything as it was before to be able to try again - flashed stock-recovery using the Recovery Flasher by LeBobo, booted into bootloader and selected "Factory". The cell is now just showing the "Warning bootloader unlocked" warning and nothing else happens.
When i try to select the recovery in the bootloader menu, an image of a Android laying on its back with an opened hatch and a red warning symbol showing a "!" appears and nothing else happens.
I seem to have bricked my device, because i cant't really do anything now - is there any solution?
I read through different topics but could not find a real solution to this particular problem...
Thank you so much in advance for your help!
It's not bricked
At the moment u enter stock recovery with that android and red warning sy,bol, u need to press bot volume up + downp. Than it will enter stock recovery mode.
Those are the following things u can do to get custom rom,
1. Flash another recovery, cwm touch, cwm non-touch, twrp. They all work a little different.
2. Flash the custom rom and wipe everything, The wip can take some time. sometimes it will be seconds, sometimes it will take a couple of minutes. Every recovery behaves different, and every flash/wipe too.
3. enjoy
If u really want to go back to stock, flash your stock JB firmware by RSD-Lite.
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
StarGeneral said:
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
Click to expand...
Click to collapse
5 minutes is a bit too much. But that's the problem with this device. Every device behaves different and we haven't found out a solution too it.
At the moment i can't do much for you. I can only say try to wipe the partitions mannualy. Wipe system, data and cache. and mount system. And then try to install it. Maybe if that doesnt do the trick try again another recovery.
This from KTR-ROM
Code:
- Enter in TWRP or CWM
- Wipes required: data, system, cache y dalvik
*In CWM mount system must format before (Mount and storage -> Mount system)
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
StarGeneral said:
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
Click to expand...
Click to collapse
nice, glad that it worked
Hey guys,
Lately my phone was beginning to slow down a bit and my storage was nearly full so earlier today I decided to factory reset my phone and reflash Android Revolution HD 71.1 (prior to the factory reset I was running the same ROM, along with the latest (I think) ElementalX kernel). ARHD installed fine but when I went to reflash the same kernel I found that each time I tried, the phone would turn off as it started installing (after I selected all my overclocking preferences etc). The majority of the preferences were set to default so no overclocking or overvolting, and as far as I can remember, the rest of the preferences were the same as I had set prior to today. Before trying to flash the kernel each time, I wiped the cache/dalvik cache and tried installing the kernel .zip from within TWRP with no luck. Is there anything obvious that I'm missing?
Cheers
FallThroughInfinity said:
Hey guys,
Lately my phone was beginning to slow down a bit and my storage was nearly full so earlier today I decided to factory reset my phone and reflash Android Revolution HD 71.1 (prior to the factory reset I was running the same ROM, along with the latest (I think) ElementalX kernel). ARHD installed fine but when I went to reflash the same kernel I found that each time I tried, the phone would turn off as it started installing (after I selected all my overclocking preferences etc). The majority of the preferences were set to default so no overclocking or overvolting, and as far as I can remember, the rest of the preferences were the same as I had set prior to today. Before trying to flash the kernel each time, I wiped the cache/dalvik cache and tried installing the kernel .zip from within TWRP with no luck. Is there anything obvious that I'm missing?
Cheers
Click to expand...
Click to collapse
Have you followed these instructions from the OP?
1. Install zip from recovery
2. Follow the instructions, if you don't know what to do, use the preselected options
3. Reboot
For installation, it seems a lot of people have finicky phones when it comes to flashing stuff with aroma.
If the installer gets stuck at 0% then you need to reboot to bootloader and do fastboot erase cache
If the installer reboots at 10%, you need to do a nandroid backup of /system partition and restore it. I think a dirty flash would also work.
After you install it, if you get a black screen or stuck at the HTC logo, no need to worry. Just hold down the power button untill the capacitive buttons start flashing and the phone restarts. The kernel installed correctly.