when i try to install any rom other than cm10 and 10.1 it wont go past the boot logo i think jedi mind trick still works i have used CWM recovery and twrp recovery and i always wipe in this order; cache,dalvik,factory,system..... then i install and wipe cache and dalvik again do my gapps if there is one then another cache and dalvik and boot and i always hang on the bootlogo could the wrong gapps version make any difference ike using 4.2.1 gapps on 4.1 or 4.0 cause it not to boot it shouldnt keep it from booting
One way to find out if it is the gapps causing the problem is to install the rom, after installing the rom DO NOT install gapps and reboot the rom and see if it comes up, if it comes up fine then reboot into recovery and install gapps, then if it doesn't come up you know it is the gapps. I always install this way because I have had issues with gapps, need to make sure you have the right gapps for the rom your installing, sometimes I get a bad download and have the same problem, just redownload and try again
can't post a link yet but go to goo.im/gapps, that has helped me
JMT
Jedi mind Trick isn't too bad for our phone
To get Jedi mind trick to install without boot loop or boot hang then after you flash a ROM do a factory reset instead of wiping dalvik and cache then reboot
Sent from my SGH-T989 using xda app-developers app
Related
I successfully loaded the latest Cordroid ROM V4 on HTC One X as far as install goes. However on reboot I get the Sense ring screen which am unable to use before phone reboots.
In a constant boot loop.
Thankfully took a Rom backup prior to install that got me out of trouble.
Anyone else managed to get this to work or is there an error in the Rom or the way I am installing?
Not had issues with previous Roms from Coredroid….
Probably something wrong with your install. Did you wipe dalvik cache, etc.?
Reflash new boot.img.
Sent from XDA App using HTC One X.
PCHAPM said:
I successfully loaded the latest Cordroid ROM V4 on HTC One X as far as install goes. However on reboot I get the Sense ring screen which am unable to use before phone reboots.
In a constant boot loop.
Thankfully took a Rom backup prior to install that got me out of trouble.
Anyone else managed to get this to work or is there an error in the Rom or the way I am installing?
Not had issues with previous Roms from Coredroid….
Click to expand...
Click to collapse
perform full wipe, clear cache and dalvik cache before installing v4 as it has new kernel and reflash boot image and reinstall ROM again
vivek_bhoj said:
perform full wipe, clear cache and dalvik cache before installing v4 as it has new kernel and reflash boot image and reinstall ROM again
Click to expand...
Click to collapse
Had done the full wipe and cleared both cache but not the reflash of boot imgage this did the trick. Thanks for the great help.......
Im not a noob to rooting but i can not figure out y it wont boot. Just stays on boot animation. Ive wiped cache reinstalled rom even tried diffrent rom and nothing. Any help would be great!
Sent from my SGH-T679 using xda app-developers app
Because you're trying to get Liquid All-Star V5 and Slim Bean All-Star V5 to work, follow these instructions (use TWRP): 1. Format System 2. Wipe Data/ Factory Reset 3. Wipe cache/dalvik 4. Flash ROM 5. Flash Gapps 6. Reboot
If you follow those instruction you shouldn't have a problem.
Hi All,
Seem to have a slight problem with flashing Custom Roms onto my GNex at the moment. Not too sure what's causing it to freeze when booting up. All I get is the X logo and will stay there until the battery dies.
I'm able to revert back to a Google rom and regain use of my phone. Just can't seem to flash any custom roms at all. It's happened with CM10.1, CM10, XenonHD Stable-2.0, Minoco.
I've attempted to flash with CWM and TWRP. Both get the same results. Prior to flashing I've whiped both the Cache and Davlik.
I have previously used CM9 and older versions of Minoco on this device. So seems odd that this is happening now.
Any advise or ideas towards what I should look at would be appreciated.
Thanks,
Drav
you have wipe data before flashing different roms... dirty flashing(only wipe cahce and dalvik) is only if you are updating the same rom.. this is how i normally flash ALL roms
1. wipe data/factory reset
2. wipe system
3. wipe cache
4. wipe dalvik cache
5. flash rom
6. flash gapps
7. reboot
8. wait 10 mins then do another reboot
9. enjoy
PS- the 10 min wait and reboot is soemthing i do that IMO lets the new rom settle
Thanks k786,
It's booted up in a custom rom now after following those step by step. Much appreciated! :good:
Cheers,
Drav
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
4.3
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
stormannorman said:
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
Click to expand...
Click to collapse
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
dkrcubsfan said:
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
Click to expand...
Click to collapse
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
kj2112 said:
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
Click to expand...
Click to collapse
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
if twrp keeps giving you problems like these maybe try doing it from cmw. ive read it gives way less problems than twrp:good:
Decimus Meridius said:
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
Click to expand...
Click to collapse
This. 2.6.1.0 twrp.
Sent from my cellular telephone
hi,everyone.
i've just tried to install cm11 in my galaxy nexus and it cannot boot on now
its installation is fail because status 7 in the cwm recovery
i still cant boot on my phone
can anyone help me
What version of CWM Recovery are you on? An update of the recovery to a newer build might help.
Break me off a piece of that Kit-Kat ROM!
What version of Android are you coming from? Anytime you are switching to a different ROM, especially from a JellyBean (4.3 or other) to a KitKat 4.4 ROM, you must do a clean wipe of your phone prior to installation. It sounds like you tried to do a dirty flash. Boot into recovery, and format data, cache, and dalvik cache, then try flashing the CM11 and Gapps.
If that doesn't work...try this thread. http://forum.xda-developers.com/showthread.php?t=2302599
tonykunyin said:
hi,everyone.
i've just tried to install cm11 in my galaxy nexus and it cannot boot on now
its installation is fail because status 7 in the cwm recovery
i still cant boot on my phone
can anyone help me
Click to expand...
Click to collapse
dwoods1983 said:
What version of Android are you coming from? Anytime you are switching to a different ROM, especially from a JellyBean (4.3 or other) to a KitKat 4.4 ROM, you must do a clean wipe of your phone prior to installation. It sounds like you tried to do a dirty flash. Boot into recovery, and format data, cache, and dalvik cache, then try flashing the CM11 and Gapps.
If that doesn't work...try this thread. http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
i am coming from the stock android 4.3 rom. I've tried wipe the data,wipe cache and dalvik cache.However,it just keeps saying installation error in the cwm touch recovery because of the status 7.
That method doesnt work for me. i still even cannot boot on my phone.how can i send it in again
OK, first you need to manually boot into your recovery by holding the volume up and down buttons at the same time and then pressing the power button. You should get into your bootloader and then be able choose recovery. I assume you have a backup...so just flash back to your stock android 4.3. Then once you are able to get back into your phone see if you can update your cwm. If updating you cwm turns out not to be the issue then go watch a YouTube video on how to fix the status 7 error. It basically involves copying the zip file you are trying to flash over to your computer and editing one of the files. Goodluck...let me know if this works.
tonykunyin said:
i am coming from the stock android 4.3 rom. I've tried wipe the data,wipe cache and dalvik cache.However,it just keeps saying installation error in the cwm touch recovery because of the status 7.
That method doesnt work for me. i still even cannot boot on my phone.how can i send it in again
Click to expand...
Click to collapse
check your baseband..you should be in the latest radio..mine is XXLH1..other rom required latest baseband..
Pretty sure it sounds like he is on an outdated version of cwm, status 7 errors can be signs of old recovery version. Fastboot flash the latest cwm.