Database Info

Install vs. Update

If you want to do an update (e.g., no wipe, keeps data) of a ROM instead of a full installation, is there anything you need to do in CWM recovery other than selected update instead of install zip? Does the name of the zip need to be update?
I'm asking because I like the Phoenix ROM, but updates are coming quickly, and I don't want to have to set up everyting every few hours...
Thanks.

Unless it is indicated by the dev, you don't need to do a full wipe. It is always good to wipe cache, and dalvik cache when doing an update, patch, or add-on. There is no need to rename it, unless for some reason that makes it easier for you to remember what file it is.

Pretty sure that Rom has data wipe written into the update script so you would have to modify that.

does it do a data wipe or does it format /system

Thanks, and should I select update or install in CWM recovery? What is the difference?

Update is looking for a specific file named that, I believe. Correct me if I'm wrong, but I believe you can always run Install Zip, regardless of what it is as long as it's a flashable zip file.

Four-Fifty-X said:
If you want to do an update (e.g., no wipe, keeps data) of a ROM instead of a full installation, is there anything you need to do in CWM recovery other than selected update instead of install zip? Does the name of the zip need to be update?
I'm asking because I like the Phoenix ROM, but updates are coming quickly, and I don't want to have to set up everyting every few hours...
Thanks.
Click to expand...
Click to collapse
the rom developer should specify if a full wipe is needed. if not, you dont have to wipe or backup or anything and you wont lose your data.

i know people hate resetting up their phone, but 99.9% of the GPS and other random problems in here are from not wiping /data before the install. If you can stand it at all, do a full wipe. It seems these phones are VERY picky about what's left in /data after you wipe. Anytime I release a rom that wipes, there's usually no problems, if it doesn't wipe, there's GPS/data speed issues galore.

ROM Flashing Leftovers?

Has anyone else noticed leftover apps or info from your previous ROM that should not be in your current ROM? I am noticing this after the GB leak and the GB leaked based ROMs.
This is my process whenever I flash a ROM.
Boot into hboot and flash radio if neccessary.
Boot existing ROM and remove radio file from root of SD card.
Boot into recovery and clear data/factory reset. Wipe cache. Wipe Dalvik. Wipe battery stats. Fix permissions.
Flash ROM in recovery.
Flash kernel in recovery if neccessary.
(I don't use any type of app backup like Titanium or something like that. I just don't mind putting my apps back on because I don't have much to begin with.)
Now some examples, I flashed Teslacoil which I was running for about a week. It has a file manger app that I did not download. Then I flashed dhemke17's plain debloated GB ROM. The File Manager app remained in there which I thought was a little weird because he didn't say he was going to include it but I didn't pay much attention to it.
Then I flashed jcases GB ROM and played with it a little and noticed I couldn't lock GPS for the weather clock. Flashed back to dhemke's ROM and couldn't get a lock with the clock either but the first time it locked fine.
It seems like to me when flashing between other chef's roms it may be carrying over apps and/or info. This might be why we have been seeing extremes from both sides of some have been having great experiences and others it doesn't work for them at all.
Maybe flashing back to stock first before flashing to a new rom may he in order, I know we had to do that with some of the old skool winmo phones (remember those days?).
Anyhow, has anyone noticed these types of instances. Those of you who may be flashing to another's rom try to take notice and see if anything carries over.
Thanks gang!
And just to be sure, I do a wipe everytime I flash someone else's ROM.
Sent from my ADR6400L using Tapatalk

This also might be why some devs have been seeing their work in others Roms without being given credit.
Just guessing on this one.
Sent from my DROID PRO using Tapatalk

I also noticed, I don't like Sense so I normally change some of files to get a Sense-reduced experience from the GB Roms since we don't have a Senseless GB rom yet. I use Root Explorer to change the extension to .bak, when flashing the rom and doing this process for the new rom it would have the new file and still have the .bak file. So it would have like a Rosie.APK file and a Rosie.APK.bak file.
Sent from my DROID PRO using Tapatalk

I've also noticed something similar.. I also wipe on every install even updates to the rom i'm currently running. What I noticed is that after about five to ten minutes the wallpaper will change back to a custom one that I have saved on my sd card. Also when I turn on wifi it still remembers my password and connects to my network. to me if it isn't wiping these things it may not be wiping things that will conflict with any changes to my rom.
Now what I do is wipe data factory reset 3x, wipe cache, wipe davlick 2x, wipe battery stats ..thats clears out the issue I explained above.

To my knowledge that is just the built in restore Froyo has. You probably click to allow Google to store/backup your apps on setup, right?

Built in restore or you are not wiping.
Devs are seeing their work elsewhere because "devs" are asses.
Sent from my LG Revolution

jcase said:
Built in restore or you are not wiping.
Devs are seeing their work elsewhere because "devs" are asses.
Sent from my LG Revolution
Click to expand...
Click to collapse
OK so why am I seeing the .bak files when I change roms? It only does it from the rom right before it. Like I said I flashed from Tesla to dhemke and it had the file manager app. Then I flashed to your rom this was your first GB leak. It did not have the file manager but the weatherclock was not finding my current location. I flashed back to dhemke and this time there was no file manager app and weatherclock would not find current location. Flashed back to Tesla then back again to your rom jcase because you updated yours and file manager was there and weatherclock locked.
If the devs are being asses that's fine I was just throwing that out there, but I am sure our phones are not complete wiping when going from gb rom to gb rom. Like I said I wipe everything everytime because I don't have much crap to begin with and I am used to reinstalling my crap from the winmo days.
Try to flash and see if anything carries over.
And the wallpaper and wifi settings like others suggested is from your g account.
Sent from my ADR6400L using Tapatalk

This happens when you don't wipe and clear cache
Sent from my ADR6400L using XDA Premium App

Well I do wipe everything before each install via recovery. Read the first post for exact steps I take when flashing. When it boots it seems fresh, I have to resync my gmail account, download and install market apps, reinstall my apps that I sideload via sd card, etc. Just the apps that are in the core rom like in the system/apps folder are still there. I was just on chingys gingeritis version IV then flashed and wiped to version VI. On version IV I changed a few files to add .bak extension to get a senseless version like the Rosie.apk. After I flashed to version VI I went into system/apps and the .bak files were still there.
Again to my knowledge this is only happening with GB based roms. If I am wiping the wrong way please let me know that is why I posted my steps in the first post but that is how I wiped and flashed this whole time. The only thing I can think of is wiping, flash the rom, then wipe again. Or wipe via the settings menus.
Before someone flashes, could they try editing a core app in the system/apps folder with a .bak extension. Then wipe and install your ROM, and see if that .bak file is still there? Thank you.
Sent from my ADR6400L using Tapatalk

From looking at the updater-script file of the rom I flashed (1.13.605.7 Debloat/Deodex), it does a rm -rf /system
If your rom's updater-script file does not do that, then you should contact the head dev and ask them to add it in.
If it does have that, then there is definitely something going wrong to cause files to be left behind since that command is literally, "force recursive remove /system"
JM2c
P.S. BTW, wiping does not erase anything in /system. A rom that includes a file manager will have it in /system.
So the rom you flashed after the one with the file manager didn't erase /system before flashing its changes..

[REF] 30 Steps from GB to ICS ROM

I've gone from my long time TPC v3 to various ROMS and recently, ICS ROMs multiple times over the last few weeks. After a myriad of gotchas encountered, I wrote down this list of things to do in 30 steps and I thought I'll share the list. Where ever applicable, I've included the reason why the step is there which of course based on my (bad) experience.
Please feel free to add any additional steps you find missing and do hit me up with a Thanks if you find this useful.
1. Check space availability on internal SD
(Error handling and messages are lacking, it would be crippling if your backups or downloaded zips are incomplete)
2. Do a full Titanium backup
(take two if you have the space and just to be safe)
3. Do a nandroid backup via ROM Mgr or CWM
4. Download the target ROM
5. Download other ROMs (optional)
6. Download the radio (if needed, some are baked in)
7. Download the kernel (if needed, some are baked in)
8. Download other zips, boot animation e.g. (optional but should be done much later)
9. Download other scripts if needed like Darkside wipe (recommended)
10. Boot into CWM (either through ROM Mgr or button presses)
11. Install the radio zip (if needed)
12. Do the wipe dance, factory reset, cache, dalvik wipe, /system, /data, /cache, Darkside e.g
(see ROM instructions)
13. Install the ROM zip
14. Install the kernel zip if needed
15. Reboot
16. Let it sit for a few mins
17. Login into Market, exit and wait for Market to morph into Play Store
18. Update Titanium through Play Store (If not, TiBu may hang on some app restore or not start at all)
19. Download ROM Toolbox, change resolution and reboot (optional)
20. Setup wifi so you don't incur data usage
21. Mark sure other sources is checked
22. Run Titanium batch restore, missing apps only
23. Reboot
24. Let it sit for a few more mins
25. Run update/update all in Play Store, Amazon App Store e.g.
(This brings the apps up to ICS compatible versions if present)
26. Some apps may require re-installations
27. Some apps may be missing and require installation
28. Some apps may require re-setup (Juice Defender, Widgetlockers, widgets in general)
29. Setup security, face, pin, pattern locks, timeout value
(Re-setup required on new ROMs)
30. Re-setup and re-sync Sugarsync (optional)

Nice list, good stuff!
I'd do step 6 and 7 regardless because I like to have a backup of a working kernel and modem always incase I need to reflash them.
Oh and check out the app appextractor, it's good for restoring sms from nandroid provided the backup was the same OS version.
Sent from my SAMSUNG-SGH-I727 using Tapatalk

kr3w1337 said:
Nice list, good stuff!
I'd do step 6 and 7 regardless because I like to have a backup of a working kernel and modem always incase I need to reflash them.
Oh and check out the app appextractor, it's good for restoring sms from nandroid provided the backup was the same OS version.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Yeah, that's what I do too. I have at least one modem, kernel, boot anim, wipe script and several ROM zip files sitting there just in case I need to use it. When the phone is bricked (for various reasons) the last thing you'll need is to do the setup (download, copy e.g.) just to get the files there.

you should set some time out and do a guide like this for all the sammy rom forums on xda, I know it seems alot, but you mentioned alot in there that I didnt think about that would have save me some heartache...
just a generalized guide, nothing too fancy with definitive radios, etc...

Nice list.
Very helpful info.
I'm digging your terminology "do the wipe dance".

I typically pull the external SD card before wiping or flashing anything... it may not be necessary, but it's a huge PITA if I lose the data.

How to flash your Tab 7 Plus (P6200) with the carbon rom and have google apps work

Hi all,
Obviously you need the Carbon ROM for the P6200 first. Here is the link http://forum.xda-developers.com/showthread.php?t=2723566
Step One: Unlock Your Bootloader and Flash a Custom Recovery
How to Flash a ROM to Your Android Phone
First, let's clear up some confusion: Contrary to popular belief, you do not actually need to root your phone to flash a ROM—you just need to unlock your bootloader and flash a custom recovery. However, this process usually goes hand-in-hand with rooting—and most custom ROMs come with root access—so what you think of as "rooting your phone" is probably what you're going to have to do first.
Unfortunately, we can't go through this step in detail here, because it's different for every phone! So, I highly recommend checking out our everything root guide to learn a bit more about what's involved, what all the different terms mean, and what to watch out for. Then, search around sites like XDA Developers for instructions on how to unlock the bootloader of your specific phone, which recovery you should use (usually TWRP or ClockworkMod), and how to flash it.
I also recommend rooting your phone during step one, since it'll make the backup process in step two easier—and save you some hassle along the way. A lot of methods and one-click apps will root your phone anyways, so it might be included in the process. Again, this can vary from phone to phone. (If the instructions require you to flash SuperSU.zip, you can refer to step three of this guide for info on how to do that—ironically, it's just like flashing a ROM).
NOTE: Unlocking your bootloader will most likely wipe your phone, and without root access, you won't be able to back up very much. So, save anything you want to keep on your computer—you will have to set up your phone from scratch just this once before continuing.
When you're done, return here and continue to step two for the rest of the ROMming process.
Step Two: Make a Backup of Your System, Apps, and Data
Now that you've got a custom recovery on your phone, the first thing you should do—before you ever make a big change to your system—is back it up. First, we'll make a Nandroid backup, which is basically a image of your current system. That way, if something goes wrong, you can restore your phone to exactly the way it was before you started tweaking. This will save you a lot of hassle if something goes wonky (which, let's be honest, can happen often). To do this:
Reboot your phone and enter recovery mode. This is a bit different on every phone, but usually involves some permutation of pressing the power and volume buttons at the same time.
Head to the "Backup" or "Nandroid" section of your recovery mode. The default settings should be fine. If given the option, give your backup a name that helps you remember what it is (like "Pre-CyanogenMod Backup 01-17-14"). Confirm your backup and let it run.
Wait for the backup to finish. This may take awhile.
I also recommend making a second type of backup: your apps and settings. If you just unlocked your bootloader and wiped your phone, you can skip this step, but any time you flash a ROM in the future, you'll want to back up your apps first, since you may have to wipe your phone before you flash. With a backup, you can easily restore those apps and data after flashing, making the process a lot simpler. We recommend using Titanium Backup.
How to Set Up a Fully Automated App and Settings Backup on Android
In an ideal world, your Android's apps, their settings, and your system settings would…
Read more
How to Flash a ROM to Your Android Phone
This is different from a Nandroid backup because it just backs up the apps themselves, which you can then restore on any ROM you want. Nandroid backups take your entire system as it is, ROM included.
Note that you'll need to be rooted to use Titanium Backup (which is why I recommend you root in step one). To perform a backup in Titanium:
Open Titanium Backup and grant it root permissions if it asks for them. If it experiences any problems with root, it'll tell you right now.
Tap the "Batch" button in the upper right-hand corner (the one that looks like a little checkbox). Scroll down to the "Backup" section and find "Backup All User Apps." Tap the "Run" button. This will back up any apps you've downloaded from the Play Store, and their data. (You can try backing up your system data as well, but I find this usually doesn't work very well).
Wait for it to finish. If you like, you can also sync these to Dropbox as described here, but you don't have to for this process.
This may seem like a lot of unnecessary backups, but trust me: it's going to save you a lot of time in the long run. Now if something goes wrong, you have a nandroid backup to fall back on and don't have to start from scratch. And, when your ROM flashes successfully, you don't have to start re-downloading and setting up all your apps yourself because you can restore them with Titanium.
Step Three: Download and Flash the ROM of Your Choice
How to Flash a ROM to Your Android Phone
Now comes the fun part: flashing your ROM. First, obviously, you need to find the ROM you want. Again, this chart is a good place to start, as is our list of the five most popular. You may also want to poke around sites like the XDA Developers forums to see what's available for your particular phone.
When you've found a ROM you want to try, download it and save it to your phone. It should come in the form of a fairly large ZIP file, so you'll probably want to be on Wi-Fi to download it. You can either download it directly from your phone, or download it on your computer and transfer it over via USB.
To flash your ROM:
Reboot your phone into Recovery mode, just like we did back when we made our Nandroid backup.
Head to the "Install" or "Install ZIP from SD Card" section of your recovery.
Navigate to the ZIP file you downloaded earlier, and select it from the list to flash it.
Wait for the process to complete; it may take a few minutes.
Depending on your situation (see below), you may also need to wipe your data and/or cache. In TWRP, you'll find this under the "Wipe" section, and in ClockworkMod, you'll need to either choose the "Wipe Data/Factory Reset" option or the "Wipe Cache Partition" option. When you're done, you're free to reboot into your new ROM.
So, when should you wipe your data and cache? Here are a few general guidelines:
If you're flashing a ROM different than the one you're currently running, you should wipe data and cache. Essentially, this performs a factory reset on your phone, and you will lose all your data.
If you're flashing a new version of a ROM you're already running, we recommend wiping your data and cache—but you should be able to get away with just wiping the cache, meaning you get to keep all your apps and settings.
Remember, if you backed everything up with Titanium, then doing a factory reset isn't all that bad, since you can just restore most of it. Keep in mind that even if you're just upgrading your existing ROM, factory resets can be helpful. If you only wipe your cache, note that a few apps may run into issues, but reinstalling them or wiping that app's data usually fixes the problem.
When you reboot, you should be in your shiny new ROM, ready to play! But what? There's no Play Store? Read on for the last step of the process...
Step Four: Download and Flash Google Apps
How to Flash a ROM to Your Android Phone
Because Google's apps are not open source, custom ROMs can't bundle Google's apps—like Gmail, Hangouts, or the Play Store—with their ROMs. That means you'll need to download and flash them separately. Luckily, this is pretty easy to do: just head to this page on RootzWiki to find out which ZIP file you need, download it to your phone, and flash it just like you did the ROM in step three. Gapps Manager is also a great app that'll help you find the right package if you're stuck, and you can download the APK from XDA Developers.
Gapps Manager Gets You the Right Google Apps for Your Rooted Phone
Android (Rooted): If you root your phone and install a new ROM, the first thing you may notice is…
Read more
Once you've flashed the latest Google Apps package, you should be all set! You'll have a new ROM with tons of settings to play with, the Play Store to download new apps, and—if you made a backup with Titanium—you can now head into Titanium Backup and restore all your apps and their settings. Enjoy!

[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.