I rooted my kindle fire and flashed ics energy to my kindle. After starting up my kindle it keeps on saying that setup wizard is not working. Also tried rebooting, redownloading and home button, all didnt work. Please help if you have any idea how to get passed this.
Did you wipe cache, dalvik-cache and maybe factory reset (this last one if you're coming from another ROM)?
I just checked, and the Energy ROM does not include SetupWizard.apk. Sounds to me like you are flashing the gapps zip after installing the ROM, which is wrong. Gapps are already included, so don't flash them.
Related
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
Hi there,
I have a Samsung Galaxy Nexus (GSM) with Jelly bean from here, and franco.Kernal nightly r240, with 384Mhz GPU. I auto-flashed it, and it got stuck on "Android is upgrading - starting apps". I've cleaned the cache and fixed permissions and it boots once but the next time I try to start it, it gets stuck again on "Android is upgrading - starting apps". I've tried installing it with CWM Recovery but it makes no difference. So do I have to clean the cache everytime I want to boot, or how do I resolve this problem? Reflashing the ROM would be my last resort.
Any help would be much appreciated.
I've re-installed my ROM without wipeing data - everything is fine with stock. Then when I flash franco.Kernal through ClockWorkMod Recovery it boots! ... but not the second time. I cleaned my cache and fixed permissions and now I'm back to step one. I'll stick with stock kernal or an old version.
Yharooer said:
I've re-installed my ROM without wipeing data - everything is fine with stock. Then when I flash franco.Kernal through ClockWorkMod Recovery it boots! ... but not the second time. I cleaned my cache and fixed permissions and now I'm back to step one. I'll stick with stock kernal or an old version.
Click to expand...
Click to collapse
hi, i am having issue also with this. have Kernal nightly r240, with 384Mhz GPU in Xenon HD v8 JB. upon reboot I get stuck. my fix is to remove battery and reboot again without any problems. I have not encountered this with other kernels. Will try to flash the rom again and wipe everything and see if the problem persist.
update; just downloaded newly realeased r241 franco kernel. No more stuck at "upgrading android".
mrm43 said:
update; just downloaded newly realeased r241 franco kernel. No more stuck at "upgrading android".
Click to expand...
Click to collapse
Same here. Thanks for the fix Franco.
For it worked the opposite
I installed r240 when it became available and had no problems with being stuck on "starting apps...", but today I installed r241 and discovered that audio jack for headphones is not functioning - if I plug in headphones or car aux it continue using built in speaker. Restarted the phone to recovery, cleaned cache and dalvik cache and upon restart I was stuck in "starting apps..." screen. Removed battery and phone booted ok, but audio jack still didn't work, so I returned back to r240 and now I can use headphones
Stuck at Android is updating starting apps .
Hi there ! How to solve this problem my phone stuck at android is upgrading starting apps after i select recovery from Rom Manager anyone can help me with this issue ? Thank You in advance
I've been trying to get a Rom on a S3 that the wife likes, so I've recently flashed the latest versions of Hyperdrive, Synergy and Wicked. I always follow the proper procedures of data wiping/factory reset, clear cache, clear dalvik, format system, and format data between each flash. I tried Hyperdrive first but had google sync errors, so went to Synergy. Synergy wouldn't connect to the nectwork so I went to flash Wicked v10 but the device wouldn't wipe/format data. I let it set for 20+ minutes and it never progressed. Pulled the battery and tried again but same result. I was able to install Wicked w/out the data wipe and it seemed to boot up ok but I was determined to get that wipe. So next I tried to restore to a backup from a week ago and it also stopped progress at the formatting data step. I re-flash Wicked v10 w/out the wipe. Once it did its thing and booted up I used went to the Factory Reset option under Settings but now the phone is stuck on the screen with the Android figure and a progress bar. Pulling the battery and trying to boot into recovery or even a normal boot all results back on the progress screen. I've managed to thoroughly piss off the wife by disabling her phone. Can anyone tell me how to fix this? I don't care if its reset back to factory rom or just anything to will allow the phone to work. Any help is appreciated.
Have you tried using Odin to flash a new original factory ROM?
IDK if you can get into Download Mode, but, if you can, it's worth a shot.
i agree with that statement. try flashing stock and unroot with odin. i have use hyperdrive since march, and i have not had that issue, so maybe its just a bad download or something. just try odin,
Greetings,
Starting with the first release of the combined PAC/PA/AOKP rom I have been unable to install most AOSP roms for the T-mobile Note II. Currently I was able to get AOKP 4.3.1 installed but no Paranoid, Illusion, or PAC/PA/AOKP hybrid will run. They install fine but I get all FC's once it boots. I have updated recovery, tried multiple wiping including sys, cleared cache and dalvik just before first boot and after flash, tried fixing permissions which always fails, and I tried flashing without GAPPS as well... still no dice. Any ideas? On a side note, do any of you have a good S-pen app setup while running AOSP roms. I dloaded a handful of apps but nothing feels cohesive.
Thank you
EDIT: This issue just went away on it's own. For some reason I can install whatever now and I changed nothing.... crazy.
I have been running CM13 for few months now. Yesterday the phone turned off and when I tried to turn it back on, it always kept on turning off once it gets to CM boot logo. Sometimes there might be few background flashes (the white circle that keeps on coming up behind sid, like normal boot) and then it would die.
I have since did a clean install with latest CM13 nightly with opengapps pico without xposed framework just to rule it being the cause of the issue. I am able to boot the first time after clean flash but if I reboot, the issue happens.
Installed fulmics 5.0 ROM for testing and it worked fine If I flash CM13 back again, the issue happens.
Tried to capture logcat by running adb logcat and turn on the phone. It still is stuck at waiting for device.
Does anyone else have issues with latest CM13?
Did you try older builds?
Just ask - Did you made full wipe?
halekhonza said:
Did you try older builds?
Just ask - Did you made full wipe?
Click to expand...
Click to collapse
The oldest build I could find is cm-13.0-20160422-NIGHTLY which I tried and same result.
Yes. wiped system, data, cache, Dalvik Cache & Internal storage partitions.