I updated to 6.0.4.3. so I could install gapps 4.4 since i read it was required. First I tried gapps 4.4 with cm11 and it wouldnt boot, just had a black screen. tried rebooting into recovery to retry the installation after wiping system but the recovery wouldnt properly load, couldnt get past cache wipe. Afterwards I downgraded back to 5.0.2.6 to install CM10.2 so i could try installing 6.0.4.3 through ROM Manager. I think gapps is freezing up cwm because it still happened again with the touch cwm 6.0.4.3 while trying to install cm 11 with gapps. i downloaded the package from galaxys2root.com and first i thought it was just a faulty upload because many people were posting comments on it with no resolution. Then I came here and downloaded the new Hellkat and BeanStalk ROMS and Hellkat did the same thing where cwm froze at cache wipe and i downgraded back to 5.0.2.6. although after I downgraded to that cwm, the Hellkat boot animation is continuous. I'll try BeanStalk next. I've been using darkside sper wipe and cache wipe with the installation of these.
Related
I've tried to install rom 3 different times but it keeps getting stuck on the boot logo for 15 min +. Can anyone help?
What recovery are you using? if using CWM remember to use tdj cache wipe after flashing the rom
Same issue different rom
i followed the 4.04 instructoins to root
did odin
superuser
and got the stock rom rooted
made a backup
then flashed cyanogenmod 9.1.0 stable
wiped data/factory reset
wiped cache partition then rebooted
i basically followed these instructions
http://forum.xda-developers.com/showthread.php?t=1514434
cyanogen mod bootloop ive wiped everything and still no luck
using CWM recovery 5.0.2.7
kinda stinks i could root but cant load any version of cyanogen even tried 9.0.0 and nothing im still looping
lostangelino said:
i followed the 4.04 instructoins to root
did odin
superuser
and got the stock rom rooted
made a backup
then flashed cyanogenmod 9.1.0 stable
wiped data/factory reset
wiped cache partition then rebooted
i basically followed these instructions
http://forum.xda-developers.com/showthread.php?t=1514434
cyanogen mod bootloop ive wiped everything and still no luck
using CWM recovery 5.0.2.7
kinda stinks i could root but cant load any version of cyanogen even tried 9.0.0 and nothing im still looping
Click to expand...
Click to collapse
Thats because you are using the stock recovery and on CM roms you need to use tdj super wipe cache after you flash the rom...
this is the instructions I use everytime I flash a rom
wipe factory reset 3 times
wipe cache 3 times
wipe dalvic
flash tdj super wipe
flash rom
flash gapps (if im flashing any aosp roms)
flash tdj cache wipe
reboot
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
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.
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Edit: I have now also tried
1. Restoring to original stock touchwiz 4.1.1
2. Wiping cache from original recovery
3.Rerooting
4.Restoring a backup of 4.3
5.Attempted to update to C-Rom, Carbonrom, Resurrection Remix -- No Luck Fails
Corvetrims77 said:
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Click to expand...
Click to collapse
I'd like to know myself. I'm stuck too. I can flash a 4.3 rom and everything works, but when I reboot, it gets stuck. All was fine until I flashed Wicked rom and flashed " MJ2 bootloader MJB" Now every time I reboot it gets stuck. Also If I try a reflash, the only way to get it to bootup is to format before flashing.
Try using Philz Touch as your recovery program.
audit13 said:
Try using Philz Touch as your recovery program.
Click to expand...
Click to collapse
I had cwm when I originally started out, switched to twrp to see if the recovery was the issue.
I assume you were running the latest version of cwm before you switched to twrp so it can't be the recovery.
Are you doing a full wipe of the system, cache, data, and Dalvik before installing the ROM?
Yea every time I wiped data, cache, dalvik , I even reformatted once. I have managed to boot up into tasl650AOKP which is a d2lte build but no other ROMs. I mean at this point it looks like I should just wait a bit to see if it is something with the ROMs interacting with my phone(as per all phones are made different)
Sent from my d2lte using Tapatalk
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
audit13 said:
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
Click to expand...
Click to collapse
Yeah I gave it a shot still no dice. I keep seeing other people having similar issues, so I am still leaning it has to do with the differences in d2lte builds vs dtatt builds
Sent from my d2lte using Tapatalk
d2att ROMs are okay? Just not any d2lte?
audit13 said:
d2att ROMs are okay? Just not any d2lte?
Click to expand...
Click to collapse
As I stated before I am able to boot int Task650AOKP(Which is a d2lte build), any of the others that I have tried have not worked. There are some updates out today, I am going to attempt again and post back results.
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
audit13 said:
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
Click to expand...
Click to collapse
Thanks for the help, I actually was just able to boot into C-Rom by following the same steps except I am using TWRP. No idea really what caused the Roms to get stuck on boot. Quite annoying.
I had TWRP on my phone but I was having problems installing ROMs when I first got the phone in January.As soon as I switched to CWM or Philz, no problems at all except for ROMs based on a stock 4.3 ROM.
I have tried the roms below:
Pac-rom
LiquidSmooth
CyanogenMod 12.1
CyanogenMod 11
And the result is it always gets stuck at boot where the boot animation continues infinitely. I have gave it about 30 minutes to boot.
With LiquidSmooth I was able to run logcat, but CM12.1 I am not able to.
I have tried resetting system, data, caches in twrp and using the reset for new rom in philz.
I have tried flashing with both TWRP and Philz.
I am using the latest Philz and TWRP.
The only thing that has worked for me is samsung stock ROM, but I do not like the stock ROM.
Are there SPH-L900 phones you have to do something different?
Is there a way to get boot logs from CM12?
Am I doing something wrong?
See attachment from LiquidSmooth.
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
GRMrGecko said:
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
Click to expand...
Click to collapse
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Raziel10000 said:
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Click to expand...
Click to collapse
Followed this guide from some post I found after reading for 8 hours, LOL. Don't remember who it is from... It's for the Cyanide ROM but worked perfect for CM12.1 latest nightly with the latest GAPPs
1.) revert everything to stock
Using Odin3 v3.09 I first flashed this: L900VPUCNE2_L900SPTCNE2_SPR.zip
2.) Reboot and verify it's not bricked, then use ODIN to flash Philz philz_touch_6.15.4-l900.tar.md5
3.) Reboot into Philz recovery and follow these steps exactly
1. Mounts and Storage
Format / system
Format / cache
Format / data
Format / data and /data /media (/sdcard)
(note this isn't the EXTERNAL sdcard, on to which I had loaded the ROM, Shift and gapps)
2. Power Options > reboot recovery
3. Wipe cache partition
4. Advanced > Wipe dalvik cache
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
At one point Philz asked me if I wanted to root and I said yes.
3.) Flash (from the external sdcard) the ROM (Tablet style ROM found in OP "5.0.2-RC-7.1-tablet"), Then flash Shift (Shift-LP-4.3 other versions DID NOT WORK), then flash gapps (GApps-5.0.2-20150315-signed NO OTHER VERSION WOULD FLASH, got Error 20 every time) Here's the
After everything was flashed I rebooted and got stuck at boot animation AGAIN, so I rebooted into recovery and wiped cache. Just cache, not dalvik or user data, rebooted, and it worked.
Installed Netflix from appstore, when I logged in to netflix it asked me to update google play services (I've seen it do this on other devices as well). Updated google play services and went back to Netflix, chose a random show and tapped on it, stuck at "loading" screen. Rebooted phone, tried netflix again and it works.
This was a tough one! But it's working now and I've saved all these files in one place incase it bricks again. Now to install the Note 3/4 style faux-stitched-leather back cover I got off Amazon.
Thanks all!