Develop Bugs

[Q] Boot Fail after Custom ROM

I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.

flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot

Thanks for the suggestion but that didn't work.
Any other suggestions?

When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.

zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).

Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something

osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895

[Q] How do you install CM 10.1 via TWRP?

Hello, I am trying to do a clean install on Cyanogenmod 10.1 because of recent issues. When I attempted to install it I got a error on TWRP. Here is what I did:
1. Went to get.cm and then d2att
2. Downloaded latest nightly
3. Plugged my phone in and transferred the .zip onto phone
4. Went into TWRP
5. Did a factory reset by going to wipe then sliding
6. Clicked install
7. Selected cyanogenmod zip thingy
8. "Failed"

TimeAndroid said:
Hello, I am trying to do a clean install on Cyanogenmod 10.1 because of recent issues. When I attempted to install it I got a error on TWRP. Here is what I did:
1. Went to get.cm and then d2att
2. Downloaded latest nightly
3. Plugged my phone in and transferred the .zip onto phone
4. Went into TWRP
5. Did a factory reset by going to wipe then sliding
6. Clicked install
7. Selected cyanogenmod zip thingy
8. "Failed"
Click to expand...
Click to collapse
I did some research and heard you need to open the zip file and move the boot.img into my phone then flash it via TWRP. Is that right? Can someone tell me step by step please? I do not want to screw something up.

this "failed" message could be one of a couple of different issues. exactly what was the fail message? and what release of cm are/were you currently running?

xBeerdroiDx said:
this "failed" message could be one of a couple of different issues. exactly what was the fail message? and what release of cm are/were you currently running?
Click to expand...
Click to collapse
It just said Failed in red.
I am running 10.1-20130511-NIGHTLY-d2att
I can update OK but just not flash cyanogenmod.

Is it possible to flash boot.img by just moving it on to my device then clicking install and selecting it on TWRP?

TimeAndroid said:
It just said Failed in red.
I am running 10.1-20130511-NIGHTLY-d2att
I can update OK but just not flash cyanogenmod.
Click to expand...
Click to collapse
have you used an app like Rootchecker to see if you still have root?

xBeerdroiDx said:
have you used an app like Rootchecker to see if you still have root?
Click to expand...
Click to collapse
No I have not. I'll check now. Also, will I lose root when doing a wipe?

Yup, I do. Just had to grant it on SuperSU. Wait, am I supposed to wipe then install CM or install CM then wipe to get a clean install?

TimeAndroid said:
Yup, I do. Just had to grant it on SuperSU. Wait, am I supposed to wipe then install CM or install CM then wipe to get a clean install?
Click to expand...
Click to collapse
Full wipe, install, and than I always wipe cache/dalvik after than reboot.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KorGuy123 said:
Full wipe, install, and than I always wipe cache/dalvik after than reboot.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
So just go into TWRP click wipe and don't change anything just slide right? If yes, I have already tried that and that's when it failed to install CM after.

http://forum.xda-developers.com/showthread.php?t=2179330

TimeAndroid said:
So just go into TWRP click wipe and don't change anything just slide right? If yes, I have already tried that and that's when it failed to install CM after.
Click to expand...
Click to collapse
This is how I flash a rom in TWRP (I always transfer my pictures to my external before these steps, you might lose them if you don't)
1) Transfer ROM and GAPPS to external SD (Micro SDcard in TWRP)
2) Nandroid Backup
3) Choose "wipe"
3b) Swipe to factory reset.
4) Choose "back"
5) Choose "advanced wipe"
5b) Check Dalvik Cache, System, Data, Cache.
5c) Swipe to wipe.
6) Choose Back
7 - optional -) I always format data (not required, will wipe EVERYTHING)
8) Install Rom
9) Install Gapps
10) Wipe cache/dalvik
11) Reboot.
Your bootloader might be not up to date. The newer ROM releases are giving that problem to some people. We'll cross that bridge when we have to.

xBeerdroiDx said:
http://forum.xda-developers.com/showthread.php?t=2179330
Click to expand...
Click to collapse
Thank you for this. No offense but could I please have help with fixing the CM 10.1 not installing issue?

KorGuy123 said:
This is how I flash a rom in TWRP (I always transfer my pictures to my external before these steps, you might lose them if you don't)
1) Transfer ROM and GAPPS to external SD (Micro SDcard in TWRP)
2) Nandroid Backup
3) Choose "wipe"
3b) Swipe to factory reset.
4) Choose "back"
5) Choose "advanced wipe"
5b) Check Dalvik Cache, System, Data, Cache.
5c) Swipe to wipe.
6) Choose Back
7 - optional -) I always format data (not required, will wipe EVERYTHING)
8) Install Rom
9) Install Gapps
10) Wipe cache/dalvik
11) Reboot.
Your bootloader might be not up to date. The newer ROM releases are giving that problem to some people. We'll cross that bridge when we have to.
Click to expand...
Click to collapse
How do I update my bootloader?

TimeAndroid said:
How do I update my bootloader?
Click to expand...
Click to collapse
https://play.google.com/store/apps/...yZy5mcmVlYW5kcm9pZHRvb2xzLnJvb3RfY2hlY2tlciJd
Install this, press "check"
After everything loads press "Build Info"
Your bootloader should be I747MVLDLK4
If it is, it's up to date if not it needs updating.
Go here ONLY if it doesn't match, this won't help you if it does.
http://forum.xda-developers.com/showthread.php?t=2292957
http://forum.xda-developers.com/showthread.php?t=2287097&highlight=bootloader

KorGuy123 said:
This is how I flash a rom in TWRP (I always transfer my pictures to my external before these steps, you might lose them if you don't)
1) Transfer ROM and GAPPS to external SD (Micro SDcard in TWRP)
2) Nandroid Backup
3) Choose "wipe"
3b) Swipe to factory reset.
4) Choose "back"
5) Choose "advanced wipe"
5b) Check Dalvik Cache, System, Data, Cache.
5c) Swipe to wipe.
6) Choose Back
7 - optional -) I always format data (not required, will wipe EVERYTHING)
8) Install Rom
9) Install Gapps
10) Wipe cache/dalvik
11) Reboot.
Your bootloader might be not up to date. The newer ROM releases are giving that problem to some people. We'll cross that bridge when we have to.
Click to expand...
Click to collapse
Will I have to re-add Bell's APN and will it mess up my IMEI/EFS/NV? Besides it removing my apps, any other things I need to know?

KorGuy123 said:
https://play.google.com/store/apps/...yZy5mcmVlYW5kcm9pZHRvb2xzLnJvb3RfY2hlY2tlciJd
Install this, press "check"
After everything loads press "Build Info"
Your bootloader should be I747MVLDLK4
If it is, it's up to date if not it needs updating.
Go here ONLY if it doesn't match, this won't help you if it does.
http://forum.xda-developers.com/showthread.php?t=2292957
http://forum.xda-developers.com/showthread.php?t=2287097&highlight=bootloader
Click to expand...
Click to collapse
It's different. It is I747MVLALH1

TimeAndroid said:
Will I have to re-add Bell's APN and will it mess up my IMEI/EFS/NV? Besides it removing my apps, any other things I need to know?
Click to expand...
Click to collapse
Bell APN is built in the ROM.
Anytime you flash a ROM you run the risk of losing you IMEI (which is why you should have it backed up already) :good:
I can't think of anything else to tell you other than make sure all your pics and personal valuables are backed up on your computer or external SD before wiping anything. If you wipe it by accident it isn't restorable.
I don't know your level of ability or flashing history so I don't know what you don't know.

To flash the bootloader, I just put it on my phone and press install, right?

TimeAndroid said:
It's different. It is I747MVLALH1
Click to expand...
Click to collapse
That's why the ROM fails. Your bootloader isn't up to date. Follow those two links I sent.
I haven't had to update mine (it already is) so I can't assist you with this, it seems straight forward if you know ODIN.
No bootloaders are flashed through ODIN

[Q] Samsung Galaxy s3 i747 stuck in Cyanogenmod boot screen

Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!

dallinrigby said:
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
Click to expand...
Click to collapse
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.

ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.

shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
I have already tried to clear the cache and the dalvik and then did a reboot but it didn't change anything.

shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
I was running the stock jellybean before I installed cryogenmod...my phone is a galaxy s3 it47 (AT&T) network unlocked phone. Also, at the bottom in recovery mode it says
ClockworkMod Recovery v6. 0. 4. 5
I'm not sure whether or not this is important but it is the only thing that I can think of to tell you about my phone.
I don't care whether we keep my data, I just want it to be able to turn on! Can I just restore it using Odin somehow? I tried the wipe user memory option in recovery mode and that didn't help...

Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.

shortydoggg said:
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
Click to expand...
Click to collapse
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?

dallinrigby said:
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
Click to expand...
Click to collapse
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Go to http://download.cyanogenmod.org/?device=d2att&type=
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Go here and download 10.2: http://wiki.cyanogenmod.org/w/Google_Apps and put it on your SD card with the above .zip.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.

ChinDaChin said:
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
Click to expand...
Click to collapse
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
It says on that second link to download Torrent or via It Vends, is this the right place, and if so what do I pick?
Thanks by the way, also is there a way I could do this with Odin?

dallinrigby said:
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
Click to expand...
Click to collapse
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).

ChinDaChin said:
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
Click to expand...
Click to collapse
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Do i need to unzip it?

dallinrigby said:
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Click to expand...
Click to collapse
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)

ChinDaChin said:
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
Click to expand...
Click to collapse
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?

If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.

audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Where do i get TWRP? It doesn't say that I have Clockwork anymore, since I factory reset it

dallinrigby said:
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
Click to expand...
Click to collapse
Sorry.
I'm kind of conflicted on what's going on with your phone. It is partially a problem with going through Rom Manager to flash cyanogenmod.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I guess you can try TWRP. I haven't used TWRP so I can't comment on it. I'll try finding an explanatory video that is simple to follow. (Don't throw out Cm10.2, or the gapps. You will need those to get Cyanogenmod on your phone!)

Omni update to CM11 failed

I can't update my N7100 from previous Omnirom to latest CM11. I wiped my phone, installing latest CM11 zip and phone is stuck at N7100 logo and restart to recovery. When I install Omni zip everything is working fine. I'm tried TWRP and Philz recovery but no results. Please help

did you wipe /system, /cache, /data and dalvik? (full wipe).

atmos929 said:
did you wipe /system, /cache, /data and dalvik? (full wipe).
Click to expand...
Click to collapse
Yes of course but I think CM isn't extracting to /system because when I leave recovery it shows there's no root and asks if I want to install it.

emlo16 said:
Yes of course but I think CM isn't extracting to /system because when I leave recovery it shows there's no root and asks if I want to install it.
Click to expand...
Click to collapse
Recoveries tend to do that... they do not detect superuser from any CM based ROM and offer you to install supersu after a ROM install and rebooting system.
I you do full wipes and you have tested latest Philz and TWRP recoveries... I can only suggest you to double check that the CM11 ROM is the correct one for your N7100.
It is strange that you encounter issues with CM based ROMs... these usually install without problems... I've encountered problems booting TW based ROMs, but not these. Sorry I can't be or more help. Good luck .
EDIT:: wait a second... according to your screenshot, you did a full wipe after installing the CM ROM... you are deleting your ROM that you just installed . The steps are:
1.- full wipe
2.- install ROM
3.- Install GAPPS
4.- wipe Dalvik <-- (some devs recommend this step, others don't... doesn't hurt to do it anyway)

Flashing any rom results in infinite boot

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!