Database Info

Stuck in boot loop every time I flash a rom

I've flashed a few roms now (masters stock rooted voodoo versions of nexus s firmware) and every time I do the boot logo just keeps on going until I do a battery pull and reboot, and then it's ok.
It's not a problem, I just wondered why this happens??

did you wipe dalvik, factory settings, cache?
did you change the kernel?

zephiK said:
did you wipe dalvik, factory settings, cache?
did you change the kernel?
Click to expand...
Click to collapse
No. These roms don't wipe anything and I don't want to lose my stuff. I don't think you are meant to wipe with them either.

buachaille said:
No. These roms don't wipe anything and I don't want to lose my stuff. I don't think you are meant to wipe with them either.
Click to expand...
Click to collapse
I was asking if YOU did wipe them because if you're going from one ROM to the other ROM you are supposed to wipe.
You lose your settings and apps. Back them up using Titanium Backup (Or any other related app).
Or.. better yet, just perform a nandroid backup. After that, wipe those 3 and reboot. See if the problem is resolved, if it is then you already know. If not then nandroid restore.

If you're going from one ROM to a completely different ROM made by someone else, you have to wipe data/factory settings!
If you're flashing an updated version of the current rom you're using, wipe cache/dalvik-cache.
If you're flashing different roms every other day, go buy Titanium Backup to backup your apps/settings.
And uh what ROM are u flashing where "you're not meant to wipe"
-Nexus S

nxt said:
If you're going from one ROM to a completely different ROM made by someone else, you have to wipe data/factory settings!
If you're flashing an updated version of the current rom you're using, wipe cache/dalvik-cache.
If you're flashing different roms every other day, go buy Titanium Backup to backup your apps/settings.
And uh what ROM are u flashing where "you're not meant to wipe"
-Nexus S
Click to expand...
Click to collapse
I am new to this so I'm still getting my head around it.
From stock I went to the rooted voodoo version of this - http://forum.xda-developers.com/showthread.php?t=971690.
From there I went to the stock rooted version of this - http://forum.xda-developers.com/showthread.php?t=979851
In both cases it says:
Rom Information:
Does it wipe: No
Does it flash the radio: Yes
So since they don't wipe, I assumed I shouldn't wipe anything, but it looks like I was wrong. From your post it looks like I should have wiped the cache and dalvik cache. I know how to do this in CW but I've never done it and my roms are working fine.
So next time master releases an update I gather I should wipe cache and dalvik cache yeah?
Also, when I do this will it remove any of my settings or apps?
Hope you can answer these questions, and thanks for advice so far.
<<edit>>
Just did a bit of googling and it looks like you don't lose settings when you wipe dalvik cache and cache, so what does actually get removed.

There is a thread stickied in development called ref roms themes and kernels. It gives step by step directions on how to flash all three including what should be wiped. Check it out
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.

It says:
Does it wipe: No
Does it flash the radio: Yes
Click to expand...
Click to collapse
because its saying that the ROM doesn't wipe. Some ROMs are built in a way so that it automatically wipes your phone to ensure best performance. The creator is just saying that it doesn't do that BUT you need to wipe. The keyword does and need are two different things. The basic concept between going from 1 ROM to another (unless its the same ROM series) requires a wipe in all three: dalvik, cache, factory. If you're going from the same ROM to a newer version and encounter bugs, its best if you wipe.
I'm a more advanced user when it comes to Android since the first Android phone. I know what I'm talking about. When you go from stock ROM to another, its going to have bugs if you don't wipe.
If you're using Axura 1.1.1.0 and its fine, and he releases a new version. You can flash without wiping (but you can wipe cache & dalvik to be safe; none of your settings will be wiped). Wiping factory settings is the only one that will wipe your settings / apps.
If you're going to be a flasher, its best if you purchase Titanium Backup Pro (or MyBackup.. but I highly recommend Titanium Backup). Use this program and it will save all of your apps + settings to them. Just don't use it to save SYSTEM apps/files because it will cause FCs.
Dalvik Cache / Cache.. its nothing you need to know in particular. It's just removing cache that your phone set up to increase speeds. It just wipes them and gets the Android system to re-establish them. So no caches from the previous ROM will carry over onto the new one.

EDIT: n/m..............

zephiK said:
It says:
because its saying that the ROM doesn't wipe. Some ROMs are built in a way so that it automatically wipes your phone to ensure best performance. The creator is just saying that it doesn't do that BUT you need to wipe. The keyword does and need are two different things. The basic concept between going from 1 ROM to another (unless its the same ROM series) requires a wipe in all three: dalvik, cache, factory. If you're going from the same ROM to a newer version and encounter bugs, its best if you wipe.
I'm a more advanced user when it comes to Android since the first Android phone. I know what I'm talking about. When you go from stock ROM to another, its going to have bugs if you don't wipe.
If you're using Axura 1.1.1.0 and its fine, and he releases a new version. You can flash without wiping (but you can wipe cache & dalvik to be safe; none of your settings will be wiped). Wiping factory settings is the only one that will wipe your settings / apps.
If you're going to be a flasher, its best if you purchase Titanium Backup Pro (or MyBackup.. but I highly recommend Titanium Backup). Use this program and it will save all of your apps + settings to them. Just don't use it to save SYSTEM apps/files because it will cause FCs.
Dalvik Cache / Cache.. its nothing you need to know in particular. It's just removing cache that your phone set up to increase speeds. It just wipes them and gets the Android system to re-establish them. So no caches from the previous ROM will carry over onto the new one.
Click to expand...
Click to collapse
That is a very helpful post and clears a lot up. Many thanks. Looks like I had better do it again and do it right this time.
I've got titanium backup. Bought it after I rooted, but never restored with it yet. Also, thanks for the info about no saving system files with it, as I currently do have it setup to backup all user apps and system data, so I will have to change that. I gather I should just change it to all user apps??

buachaille said:
That is a very helpful post and clears a lot up. Many thanks. Looks like I had better do it again and do it right this time.
I've got titanium backup. Bought it after I rooted, but never restored with it yet. Also, thanks for the info about no saving system files with it, as I currently do have it setup to backup all user apps and system data, so I will have to change that. I gather I should just change it to all user apps??
Click to expand...
Click to collapse
Backup all user apps is the one you want to do. You can backup bookmarks using Google sync or a app known as BookmarkSB
If you have system apps backed up, delete all backups using batch and reapply user app backup

zephiK said:
Backup all user apps is the one you want to do. You can backup bookmarks using Google sync or a app known as BookmarkSB
If you have system apps backed up, delete all backups using batch and reapply user app backup
Click to expand...
Click to collapse
Thanks for your help. I reflashed the rom and I did it properly this time. Had a bit of a problem with TB restore as I'm a noob but Joel from TB answered an email I sent him very quickly and I got it sorted (thanks joel).
How long does it take to flash a rom once you get good at it? Took me a while tonight because of mistakes.
Sent from my Nexus S using XDA App

buachaille said:
Thanks for your help. I reflashed the rom and I did it properly this time. Had a bit of a problem with TB restore as I'm a noob but Joel from TB answered an email I sent him very quickly and I got it sorted (thanks joel).
How long does it take to flash a rom once you get good at it? Took me a while tonight because of mistakes.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I can usually get from booting into recovery to having a usable device with most everything set up in about...10 minutes? Assuming I already downloaded the ROM lol sometimes those mirrors are slooooooow.

[Q] Restoring user settings after installing a new ROM

Hey guys,
I just installed CM7, which is awesome, but I'm wondering how everyone keeps up with the new nightly builds without spending an hour restoring their phone every day. Is there a way to backup everything about your phone - even your settings, shortcuts, widgets, etc. - and then restore those settings after you install a new ROM?
Any help would be very much appreciated. Thanks!

U don't need to wipe data between every nightlie, I only do that when going from cm7 to faux Rom or vice versa. Just wipe cache, dalvik cache, install zip, fix permissions , reboot.
Sent from my LG-P999 using XDA App

You probably wanna flash gapps after the nightly, as well...or you won't have much fun.

kdunn1994 said:
U don't need to wipe data between every nightlie, I only do that when going from cm7 to faux Rom or vice versa. Just wipe cache, dalvik cache, install zip, fix permissions , reboot.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
+1 to this. You wont lose any of your installed apps or settings this way. If you've edited your build.prop file for Netflix then you'll have to do that after flashing a new nightly. And if you are using a custom kernel then you'll have to re-flash that after each new nightly.

between google backup and titanium i have pretty much everything restored in 10 minutes

what about using ROM manager?

All good ways, but I agree with the not doing a full wipe. But if you want to full wipe before each nightly another quick way to restore your apps is Android Commander, a pc program. Also, you do not have to do this:
mmapcpro said:
You probably wanna flash gapps after the nightly, as well...or you won't have much fun.
Click to expand...
Click to collapse
after every nightly, you never have.

Nice
Worked perfectly! Thanks to all of you for the tips.

adevilfish said:
between google backup and titanium i have pretty much everything restored in 10 minutes
Click to expand...
Click to collapse
How?
I have to wait for market to download every app (including titanium). I can't figure out how to get titanium running without waiting for it to get downloaded from market in some random order.
Thanks.

Woes of my Infuse

I start with a fresh wipe of my phone and then install BeanStalk with gapps (I'm currently using BS version 4.4.275 with gapps 20140105. Everything is fine for months. Then a couple of apps will start to crash a few times (the camera, dialer, browser and google apps). I've stopped using titanium backup and clockwork mod to restore my data because they were causing issues. Then the force closes become more and more frequent. I ran fix permissions and i have know clue if it helped or not. Then finally all hell breaks loose and everything begins to force close and give errors of no space left on phone. No launcher will stay open everything just bugs out. This seems to be an on going matter. It doesn't seem to resolve no matter what rom I run. I've gone through every folder sizing it and my phone is not out of space. I am getting very frustrated with my Infuse. I don't understand what some of the stuff means in my catlog file. If someone could help I'd greatly appreciate it.

i found out that Google+ and Google Drive might be the cause (such as when you upload or backup your photos to those clouds)
if you have time, go read those last 10 pages of BeanStalks, you will see what others have offered to resolve this issues
as for me, I'd do full wipe, specially format the sdcard0 (keep the Rom and Gapps to your SDcard1), and stop using the two Google services mentioned above. and use another Gapps (I am using the minimal one) Good luck!

Same problem with Unofficial CM 11.2 also
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .

Unable to get RSA prompt
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?

hemen_kap said:
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
Click to expand...
Click to collapse
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.

joel.maxuel said:
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
Click to expand...
Click to collapse
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?

hemen_kap said:
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
Click to expand...
Click to collapse
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).

joel.maxuel said:
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
Click to expand...
Click to collapse
Unfortunately the infuse is the only phone I have (so my DD)...but the lure to test the ADB on carbon is also compelling for me. Let me try moving to a non smart phone and try this out.

OK. So i installed the Carbon KK nightly, and encountered the same issue. adb devices always lists the phone as
0123456789ABCDEF unauthorized.
Also i never received the rsa prompt...
Moreover the device key seems to suggest it is some default value as compared to an actual device key.

Got it Working !!!
Ok so finally got it working.
I moved away from Scott's Unofficial CM11_2 on my daily driver and moved to Carbon ROM. Loving the new rom so far.
Once i moved to this ROM, I started adb on my desktop (adb kill-server, adb start-server) and was waiting
then on phone enabled Developer options and Android debugging over USB and connected the phone to desktop, and zingggg I get the RSA prompt.
One important thing it read is that you phone should be unlocked when you connect it to your desktop, so in case you have things like PIN or gestures that lock your screen....ensure that your screen is not locked when the phone is being connected.
Not sure if this was the issue or if it was the CM rom,,,but issue is resolved, I am loving Carbon...so not going back to CM to check the lockscreen theory....but worth a try for someone who is pulling his/her hair out like i was.
Ciao !!!
---------- Post added at 05:00 PM ---------- Previous post was at 04:41 PM ----------
missed mentioning that do not worry about the device id of 0123456789ABCDEF....i noticed it does not change for me even when adb connects properly.
It is the unauthorised state that needs to change to device.

What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.

joel.maxuel said:
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
Click to expand...
Click to collapse
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen

hemen_kap said:
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
Click to expand...
Click to collapse
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.

hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app

jloibman said:
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Click to expand...
Click to collapse
Not sure about this, but I think CM 11.2 is referred to as KitKat 4.4.4, which would be latest in the CM thread. So you are probably already running it.
Sent from my Asus MeMO Pad 8"

jloibman said:
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
Click to expand...
Click to collapse
apart from the issues that i mentioned - my experience with CM 11.2 has been great. There are some obvious things like MHL etc that do not work, but those are known issues.

joel.maxuel said:
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
Click to expand...
Click to collapse
You can download the Nova Launcher from the google play store if you want to have the same experience as with Scotts Beanstalk. I love the carbon ROM but I am so accustomed to the Nova launcher that I cant live without it.

hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
-Hemen

hemen_kap said:
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
Click to expand...
Click to collapse
Hmm, don't think I kept a ROM on my Infuse long enough to encounter this problem (except for my several months with CM 10.1, no issues). As for other phones, I use Jellybean on my semi-retired HTC and did not have this problem (closest I came was when I tried out Fly-On mod - lag closures often). But I don't think It's a Jellybean problem.
I think (and this may have been covered already) this has to do with the piddly datadata partition filling up. One way to check is open a terminal emulator (app on the phone of adb shell) and type:
Code:
df
Look for datadata in that listing. If it is in the 90% range, that spells trouble. If that is the case, you could try one of two solutions.
I don't know what possessed the developers to separate the data partitions in KitKat (I know, for "performance reasons") but leave 1/2 a GB for it. Lower end phones these days give you twice that.

Over the past few years or so I've installed ROMs going back to ICS. 99% of the time there was absolutely no issue. I habitually do a (1) factory wipe, (2) dalvik wipe, (3) system format, (4) sdcard0 format, (5) install ROM zip, (6) install gapps, (7) wipe cache and (8) wipe dalvik.
In the hundreds of ROMs I've installed and tested, 1 or 2 were bad compiles, and everyone soon knew it. They were immediately removed from any host site. So, if you're having issues, (1) install you ROM as above, (2) perhaps install a smaller gapps, and/or (3) check that you're not overloading your phone from the PlayStore.
The last and rarest issue could be your phone, but rule of thumb that works 99% of the time is: (1) assume it's always your fault first, and (2) read, read, read, read, read.

[ROM][Stock][Rooted] D850 20f Stock ROM Debloated

Updated: 03/24/2015
Hi all,
I did this mostly for practice but I thought it might be helpful so I went ahead and posted.
Stock LG D850 20f ROM
[*]Rooted/SuperSu
[*]Most bloat removed
[*]Oversharpening fix
[*]Flashable zip
[*]init.d support*
[*]CarrierIQ Remover*
*Init.d support is implemented in ROM only, not the kernel. CarrierIQ is removed automatically after first boot via an init script. Say thanks to @skeevydude for his help in getting this done. I shouldn't say "help", he pretty much did it!
Installation
Flash the Lollipop modem - see @autoprime 's thread here for modem zip
Flash the ROM zip
Wipe cache and dalvik (and in some cases data) if coming from a different ROM
Download
v3* - https://www.androidfilehost.com/?fid=95916177934548695
[QRCODE]https://www.androidfilehost.com/?fid=95916177934548695[/QRCODE]
*No change at all to the ROM itself since v2, I just realized that I've been forgetting to zero out the free space on the image file before uploading, which saves about 600 MB when zipped. New flashable zip is about 1.1 GB instead of 1.7 GB.
Older versions:
v1 - https://www.androidfilehost.com/?fid=95916177934543883
Apps Removed
/system/app:
Google Books
Google Chrome
Google Cloud Print
Google Drive
Facebook
Hangouts
Google Newsstand
Google Play Games
Google Play Music
Google Play Movies and TV
Google Plus
Twitter
/system/priv-app:
ATT Address Book
ATT Caller Name ID
ATT DriveMode
ATT Games
ATT Locker
ATT Lookout
ATT Mobile Locate
ATT Remote Support
ATT Smart Wifi
ATT Mobile TV
ISIS Wallet
ATT Visual Voicemail
MLT (LG tracker)
/system/vendor/app:
Amazon Kindle
ATT Family Map
ATT Home
ATT Keeper
ATT MHS Launcher
ATT Navigator
Uber
DeviceHelp
myATT
YP Mobile
ATT Apps
In case you want some of the ATT apps back, I have uploaded a zip here with those apps. This is NOT a flashable zip. You have a couple of options:
1. You may be able to install these as a normal (user) app by just pulling out the apk and installing the usual way.
2. If that doesn't work as expected, copy the app folder from the zip into the appropriate system folder as listed in the "Apps Removed" section.
Download: ATT Apps
Xposed Info
cmulk said:
Xposed has a couple of bad side effects at this point, so before doing anything you need to use Titanium or something similar to Freeze (this basically what the "helper" does):
LGSmartCover
Weather
Weather Theme
WeatherPlatform
Then you can install xposed as in the thread here: http://forum.xda-developers.com/showthread.php?t=3034811
However, there is still one more bug to keep in mind: Xposed will crash the Tethering and Networks menu. There is no fix for that yet, but as a workaround you can download some apps from the play store (like Mobile Network Settings), to shortcut around the menu that force closes.
Click to expand...
Click to collapse
Credits
@autoprime - Flashable zips, bump'd boot.img, and very clear instructions in his thread here
@timmytim - uploading the lollipop stock images (although I know a lot of others were working on that too)
@Skin1980 - Oversharpening fix
@skeevydude - init.d support and carrierIQ remover

CarrierIQ Removal
CarrierIQ has now been removed!
The removal is done via an init script that runs at boot to disable the IQ service before removing the files in order to prevent a force close. However, if you have to wipe data/factory reset without re-flashing the ROM, you will get a force close on the first boot. The good news is that I've tested this scenario and it should fix itself if you just wait about 20 seconds. In other words, the mentioned script does it's thing to stop the service to fix the force close and you are good to go after that.
Old info below:
cmulk said:
On the 20f lollipop rom (either mine or stock, there's no difference) either freezing LADDM or removing the libraries and LADDM as you mention will cause a force close unless you disable the "IQService" first, which is built into the framework-res.apk. I have repeated it multiple times and it has been discussed quite a bit in the Lounge and other threads. Disabling the service is easy for users to do with the "DisableService" app, and then you can remove LADDM and the libraries as mentioned. The difficulty is that disabling a service is a user setting, so, for example, if I reflash my ROM without the IQ files onto a phone with clean /data, I will again get the force close and an unusable ROM.
Click to expand...
Click to collapse
Manual Steps
In the meantime, here is how users can manually disable CarrierIQ. I take no credit for this method, it is posted in several places by several people, I'm just putting it here for convenience:
YOU MUST DO THIS IN ORDER (or at least the first few steps)
1. Download the "DisableService" app from the play store
2. In the DisableService app, go to System -> Android System and disable the "IQService" service
3. Use a root explorer to delete the folder /system/app/LADDM
4. Use a root explorer to delete /system/lib/libiq_client.so and /system/lib/libiq_service.so
5. (Optional) Uninstall DisableService
Remember, disabling the service is a user setting, so if you need to wipe /data for some reason, you will need to re-flash the ROM (which has the CarrierIQ files included) or else you will get a constant force close when your phone boots.

I'll give it a try, thanks

Flashing now. Will report.

I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM

JeffDC said:
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
Click to expand...
Click to collapse
Just clean flash to save yourself a hassle
2SHAYNEZ

Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Sent from my LG-D850 using Tapatalk

Flashing lollipop Issues
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.

shayneflashindaily said:
Just clean flash to save yourself a hassle
2SHAYNEZ
Click to expand...
Click to collapse
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?

JeffDC said:
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
Click to expand...
Click to collapse
I always do a clean flash.. dont need to back up and restore and still get bad results.

louvass said:
I always do a clean flash.. dont need to back up and restore and still get bad results.
Click to expand...
Click to collapse
That's not encouraging.

louvass said:
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
Click to expand...
Click to collapse
I have not seen that issue, but in case you are not clearing data you may need to try clearing dalvik cache.
Also, (and this is just a shot in the dark) you could try formatting system before doing anything else just in case something strange is left behind there.

JeffDC said:
That's not encouraging.
Click to expand...
Click to collapse
You can try dirty flashing first without losing any of your data.
1. Back up your current Boot and System
2. Back up your current modem (if you're coming from the Kitkat modem), or just download a flashable KK modem already posted on XDA
3. Flash the modem and ROM in this post
4. Wipe cache and dalvik
5. See if it works
If it's not working, then you will need to restore your boot, system, and modem to go back to your original kitkat setup without losing data.
Otherwise, you'll have to backup with Titanium and do a clean flash (wipe data) as already mentioned. Using Titanium makes clean flashing not so bad

I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.

Pdj7969 said:
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Click to expand...
Click to collapse
I agree that I use most or all of these Google apps as well. However, they update so often anyway that I prefer to just have them as user apps (otherwise you end up with 2 copies - the old static version in the system apps folder, and the updated version in the user apps folder).
As for the visual voicemail, I have posted the ATT apps in a zip in the OP. Visual voicemail is in the VVM_ATT folder.
Thanks!

cmulk,
Would you please clarify post 5 and 9 questions?

JeffDC said:
cmulk,
Would you please clarify post 5 and 9 questions?
Click to expand...
Click to collapse
Sure thing! That's actually what I meant to do in post 13. I am not sure if you can flash over 10f without wiping data, but you could give it a try without losing anything (except time) if you look at post 13.
You should clear cache and dalvik mostly any time you are flashing, unless you are just flashing over another stock 20f ROM.

louvass said:
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Click to expand...
Click to collapse
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least

cmulk said:
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
Click to expand...
Click to collapse
Thanks I do clear everything but my external mem.

Ever since flashing this I'm getting "no sd card" messages every time I try to download anything ( I don't have an external sd card) but it's never been a problem before. I've restored a backup of my stock Tim and the problem followed me after full wipes.

[Q] Bad battery life (AK Kernel) CM12s

So, I decided to flash the AK Kernel to fix the ghost swipe issue and the slow keyboard etc. It worked, but now the battery life is fairly bad, I'm getting around 10-12 hours and I'm at work for 8 of those hours so it doesn't get used. Google Play wake-up services are off etc. Just wondering if there's a remedy for this?

AaronW95 said:
So, I decided to flash the AK Kernel to fix the ghost swipe issue and the slow keyboard etc. It worked, but now the battery life is fairly bad, I'm getting around 10-12 hours and I'm at work for 8 of those hours so it doesn't get used. Google Play wake-up services are off etc. Just wondering if there's a remedy for this?
Click to expand...
Click to collapse
You have to provide more information like screen on time, graphs etc.
Edit: You are running old AK kernel, version update to the latest to fix the drain.
Sent from my A0001 using XDA Free mobile app

Can you link me to it? I'll put a graph up later after I finish work.

Google play related wakelocks are more Rom related anyways.

Yeah. I was just saying that for process of elimination incase someone suggested it. I'm in work at the moment. If someone could link me to the newer kernel version. That'd be wicked. If not, not to worry. I'll have a quick look when I'm home.

AaronW95 said:
Yeah. I was just saying that for process of elimination incase someone suggested it. I'm in work at the moment. If someone could link me to the newer kernel version. That'd be wicked. If not, not to worry. I'll have a quick look when I'm home.
Click to expand...
Click to collapse
http://ak.hiddenbytes.org/
or direct http://ak.hiddenbytes.org/downloads/AK.256.OPO.CM12.1.zip

Thanks for the effort. Managed to download their AK kernel updater app and it worked a charm. Thanks for your help. My battery now says 22hrs on 75% instead of about 5 hours. I'll leave this open for another day just incase it starts draining.

Can I flash this straight over francos kernel?

Yeah. Download it, wipe dalvik and cache before install and after install (always do it just incase)

AaronW95 said:
Yeah. Download it, wipe dalvik and cache before install and after install (always do it just incase)
Click to expand...
Click to collapse
Thanks mate. Does wiping dalvik/ cache delete any data, apps etc?

It deletes the data IN your apps. But not any apps or photos or any personal data. I.e. if you've got a game that's linked to Google Play, your data will save, if not back it up.

nokmond said:
Thanks mate. Does wiping dalvik/ cache delete any data, apps etc?
Click to expand...
Click to collapse
AaronW95 said:
It deletes the data IN your apps. But not any apps or photos or any personal data. I.e. if you've got a game that's linked to Google Play, your data will save, if not back it up.
Click to expand...
Click to collapse
That's incorrect. Wiping cache and dalvik cache doesn't wipe any app data at all. Only wiping the /data partition will erase apps (and their data) from the device.
XDA Moderator
Transmitted via Bacon