Related
__
__
ATT seems to work
Sweet idea! Just tried this on an ATT GS3 and it seems fine. I did not test other apps. I do get an unsupported device tag at the top in the app but I don't think that impedes the function. When I use the Nexus device device, name and model (maguro, yakju and Galaxy Nexus) I don't get the warning but probably more likely to end up with incompatible apps.
Do you reset Google Wallet prior to flashing a new rom or do you just have the build.prop update before you run wallet?
__
I'm confused. I have Wallet installed on my Verizon GS3 and I have no problems now. I am rooted and running Synergy ROM. When installed Wallet, I had to use a patched APK and edit my build.prop prior to installing Wallet to trick the phone similarly to what your script does (Galaxy Nexus, yakju, and maguro instead) After installing and setting up Wallet, I restored my original SCH-I535, d2vzw, d2vzw settings in build.prop and rebooted again. I am running Wallet no problems and it doesn't even tell me that I am using an unsupported device.
When I reboot my phone, it does not affect Wallet and my build.prop is not modified. I don't understand why someone would need your script to keep modifying the build.prop to say it is the pretend device? Please don't take my reply wrong, I'm simply trying to figure out what I am missing, not be a jerk.
I am always leary about leaving my build.prop modified because you trick other things into thinking your phone is something it is not. I feel this leaves you open to potential problems. I used Goo Manager the other day to see if there were any updates for my ROM and because of a modified build.prop it thought my phone was an AT&T GS3 and if I had downloaded and tried to flash an AT&T ROM I might have bricked it. I'm not sure, but I wouldn't want to take that chance. Also, isn't there a possibility of downloading an app from the Play Store that is only for the Sprint phone you're pretending to be and causing problems?
Jim
__
Hi Jeremiah,
Thanks for the info. Just so you know, I used that Google installer few weeks ago and it worked fine. I changed to a new ROM last week and forgot to reset wallet before switching which caused bunch of problems. I was able to fix them but the installer did not work for me anymore. I was however able to get wallet working by manually editing build.prop and installing a patched apk of wallet. After wallet was up and running, I reverted back to the d2vzw and SCH-I535 version of build.prop. So you know, I have my correct build prop AND a working Google wallet. I can send you the link but its the Verizon Google wallet thread in the mods and app forum under Verizon GS3. I understand if you switch ROMs it would need to be reset and build prop edited again, but I don't think the is a need to keep your build prop edited unless you are using the play version of wallet. Perhaps the link could get you the patched version and that might help.
Take care,
Jim
__
jeremiahmegel said:
As I recall, the patched APK isn't the newest version/update of Google Wallet, right? That's why I'm using the Play Store version: to receive updates to the app. If you don't care about updates, though, I suppose your way of doing things would be best. (I don't think it works throughout ROM updates, though. Let me know if I'm wrong about this.)
Click to expand...
Click to collapse
Oh OK... I'm not sure but that makes sense... You would know more than me! Thanks... Again I was just looking for clarification. Thanks for your work. Good luck.
Jim
jeremiahmegel said:
The "Unsupported device." error only shows up if you're running Google Wallet on a rooted device (unsurprisingly); you're right that it doesn't impede the function. And you don't need to do anything as the user before or after flashing a new ROM; once you update the ROM, your phone should reboot automatically within a minute or two of starting up to put the new build.prop into effect! Simply install this once and don't worry about it again! (Unless, of course, you uninstall Tasker or wipe your phone or something.)
Click to expand...
Click to collapse
So to clarify, when you say:
"And you don't need to do anything as the user before or after flashing a new ROM"
Do you really mean "you still have to reset Google Wallet before flashing a new ROM"?
Also, I'm wondering if it's possible that modifying build.prop might cause my Nfc.apk to stop functioning. I'm wondering this because it stopped functioning (after using 'Google Wallet Installer' - which does replace nfc.apk I believe, so that could be it, but not sure).
calaski8123 said:
Hi Jeremiah,
Thanks for the info. Just so you know, I used that Google installer few weeks ago and it worked fine. I changed to a new ROM last week and forgot to reset wallet before switching which caused bunch of problems. I was able to fix them but the installer did not work for me anymore. I was however able to get wallet working by manually editing build.prop and installing a patched apk of wallet. After wallet was up and running, I reverted back to the d2vzw and SCH-I535 version of build.prop. So you know, I have my correct build prop AND a working Google wallet. I can send you the link but its the Verizon Google wallet thread in the mods and app forum under Verizon GS3. I understand if you switch ROMs it would need to be reset and build prop edited again, but I don't think the is a need to keep your build prop edited unless you are using the play version of wallet. Perhaps the link could get you the patched version and that might help.
Take care,
Jim
Click to expand...
Click to collapse
Jim will you please tell me how you fixed it? I did not reset Wallet before installing a new ROM a couple months ago and unfortunately all my nandroids are bad due to a CWM bug involving partitions (I didn't do anything to my partition structure manually...).
Thanks a lot!
Hi,
I'll tell you what I did, but I was just trying anything so I'm not sure if I got lucky or if you have to do everything I say... First I went into application manager and I cleared all data and updates from wallet. Then I rebooted into recovery and did full wipe 3x. Then I went onto Google on my laptop and logged in. Go to wallet and then to your activated devices. Not sure what they are called but you will see all your devices that have wallet. Some might day deactivated. If there are any active then disable or remove them. I don't remember what the term is Google uses to Deactivate. Once you have no active wallet applications left on Google go back to your phone. Install the working ROM or good backup. I had a good backup with wallet working...i was able to restore that nandroid and reset wallet from within the app so that i could then install the new ROM. then After setup, reboot again and wipe dalvic cache in recovery. Then try to install wallet again. Thats pretty much how I got it fixed... The key was getting it deactivated online.
---------- Post added at 09:52 PM ---------- Previous post was at 09:28 PM ----------
Oh and I uninstalled wallet after clearing the cache and updates.. Forgot that part sorry.
Jim
I followed the instructions to the T and it worked perfectly. Thank you. But my question is, what happens to the Tasker Profile? After, I went back in to check out what you did. I am a relatively new Tasker user and was curious about what all was intailed. But when I went back the profile was gone and the only sign that I had imported the xml file was two variables. Is it supposed to disapear?
__
jeremiahmegel said:
As I recall, the patched APK isn't the newest version/update of Google Wallet, right? That's why I'm using the Play Store version: to receive updates to the app. If you don't care about updates, though, I suppose your way of doing things would be best. (I don't think it works throughout ROM updates, though. Let me know if I'm wrong about this.)
Click to expand...
Click to collapse
Correct, the patches lag behind the updates somewhat. You can only use Play Store Wallet if you build.prop matches Play Store Wallet accepted devices (d2spr being one of them). For this reason, I prefer to wait for the updated patched version - if you do that, you can keep d2vzw or whatever you want in your build.prop
As far as resetting when changing ROMs, back when everything was stored on the secure element resetting was a big pain in the ass. I don't even bother anymore - there's a separate "reset wallet" option in the menu of the actual app (different than clearing app data), but you don't need to use it. I just keep a version of Wallet Installer V3 in TiBu, and restore it after installing a new rom. After restoring Wallet Installer, just run it once and then reset build.prop - the installer downloads the latest patched Wallet.apk.
jeremiahmegel said:
No, it is not supposed to disappear. Since Tasker updated its UI, Step 4 ("Tap the green check-mark at the bottom-left of the screen to save the profile.") is no longer available. Instead, press the back button or home button on your phone (or just switch to another app) to save the profile, then continue to Step 5. Let me know if this works. Nice to know that I could help you get Google Wallet up and running!
Click to expand...
Click to collapse
I tried going through the steps again but I cant get Tasker to recognize the xml file when going through the import sequence. I downloaded and extracted (when extracrted its another file folder with the xml file in it), placed it on the root of my internal sd card. I go into tasker to import. It recognizes the file folder but when I select it, there isn't anything inside. Tasker wont recognize the basic xml file. I remeber when I first did this, the xml file was recognized without being in a folder. I can plainly see the xml file on the root of the sd card from Root Explorer in ROM toolbox. Would have it something to do with the permissions of the xml file? I show the permissions as rw-rw-r--.
I think I know why I am having to go this. I didn't follow the step to the T. I clicked "Run" before saving becasue I didn't see the green checkmark.
__
jeremiahmegel said:
What is the file name of your XML file?
Click to expand...
Click to collapse
I have the actually xml file on my sd card. It is named Replace_build.prop.prf.xml
When i go to the file through Root Browser in ROM Toolbox, its visible. I click it and it presents me with options to open it. I select Tasker and is says "Failed to move import to my sd directory"
08BajaBoy said:
I have the actually xml file on my sd card. It is named Replace_build.prop.prf.xml
When i go to the file through Root Browser in ROM Toolbox, its visible. I click it and it presents me with options to open it. I select Tasker and is says "Failed to move import to my sd directory"
Click to expand...
Click to collapse
I am not what was happening but I updated to CM10.1.0 RC2. I cleared anything I had tried previously with this tut. redownloaded the file and went though everthing again. It worked and the tasker profile stuck this time. Thanks for the help.
Great write up. Very simple to install. Google wallet was installed and running in less than 5 minutes. Thank you!
Galaxy S3 :good:
MOAR :BetteR:
Can anyone confirm this method works with 4.3? I made the jump to CM10.2 Nightly 8/27 (and tried 8/14, I think) and my phone goes into bootloop. It was working fine on CM10.1.2.
__
Ok so I have a weird problem that I could not find a solution googling for a few hours. I got a nexus 5 back in February. According to "My Devices" on the google play store site it was registered on Feb 25th and shows last used on Feb 27th. I have noticed that I couldn't remotely install apps from the site but haven't tried to trouble shoot it until now. Also the android device manager does not work. I am rooted but using the stock ROM. I've been using the phone itself with no problems. I get app updates, use the google+ picture auto backup and other services on the phone. The only problem seems to be that I am not linked to the google play website with the nexus 5. Anyone seen or heard anything like this?
I tried this below but it didn't work:
Open Google Settings from your device's apps menu.
Touch Android Device Manager.
Uncheck Allow remote factory reset.
Go to your device's main Settings menu, then touch Apps > All < Google Play services.
Touch Clear Data. Note that this action doesn't remove personal data.
Go back to Google Settings and select Allow remote factory reset.
Restart your device.
you might have to unselect remote factory reset to clear data in Google play services. After clear data the go back in select it again, reboot you should be good to go.
Click to expand...
Click to collapse
Every time it unlinked for me I just installed an App from the Play Store on my Nexus 5, and it would link again and I could install remotely through the Desktop website.
Hmmm I wish that were the case. I just installed an app yesterday after the remote link didn't work and I have tried again since. I've also removed my google account and added it back. Looks like a factory reset is in my future. Some things I've done that may have affected it:
Restore apps (not system) from titanium backup
Installed Xposed
Use of OpenVPN
ant_129 said:
Hmmm I wish that were the case. I just installed an app yesterday after the remote link didn't work and I have tried again since. I've also removed my google account and added it back. Looks like a factory reset is in my future. Some things I've done that may have affected it:
Restore apps (not system) from titanium backup
Installed Xposed
Use of OpenVPN
Click to expand...
Click to collapse
Titanium Backup and Xposed should not affect it. OpenVPN, I'm not sure about, but I HIGHLY doubt it would be the cause. Try removing your Google account from Settings and setting it up again.
Titanium Backup... should not affect it.
Click to expand...
Click to collapse
Titanium Backup WILL affect it - when you first loaded it on it would have asked you if you wanted to restore the device ID.
Open Titanium, press menu, chose the Manage Android ID, and restore your original ID. Then hit Market Update Helper, that will rebuild the market links.
Edit: Actually, maybe you don't want to restore - where did the original backup come from? Was it a Nexus 5? Maybe you already did restore the original, and it was from a different device??
krs360 said:
Titanium Backup WILL affect it - when you first loaded it on it would have asked you if you wanted to restore the device ID.
Open Titanium, press menu, chose the Manage Android ID, and restore your original ID. Then hit Market Update Helper, that will rebuild the market links.
Edit: Actually, maybe you don't want to restore - where did the original backup come from? Was it a Nexus 5? Maybe you already did restore the original, and it was from a different device??
Click to expand...
Click to collapse
Yeah I moved non system apps from a CM10 GS3. I thought about the Android ID as well. I generated a new one yesterday just to see if it fixed my problem. No luck. I am going to factory reset tonight. I'll post the results soon after I get everything up and running and confirm. Thanks for the suggestions.
ant_129 said:
Yeah I moved non system apps from a CM10 GS3. I thought about the Android ID as well. I generated a new one yesterday just to see if it fixed my problem. No luck. I am going to factory reset tonight. I'll post the results soon after I get everything up and running and confirm. Thanks for the suggestions.
Click to expand...
Click to collapse
Try re-building the market links through Tibu first.. might work?
Factory reset worked. I wish I knew what happened. I did a combination restore of my apps via the nexus 5 toolkit and titanium backup. The toolkit didn't get them all. I have not tried Xposed again. I may wait a bit and see if that was the cause.
Titanium Backup
krs360 said:
Titanium Backup WILL affect it - when you first loaded it on it would have asked you if you wanted to restore the device ID.
Open Titanium, press menu, chose the Manage Android ID, and restore your original ID. Then hit Market Update Helper, that will rebuild the market links.
Edit: Actually, maybe you don't want to restore - where did the original backup come from? Was it a Nexus 5? Maybe you already did restore the original, and it was from a different device??
Click to expand...
Click to collapse
YES.I does agree Titanium Backup will affect it and have a option of restoring the device ID.:good:
ant_129 said:
Factory reset worked. I wish I knew what happened. I did a combination restore of my apps via the nexus 5 toolkit and titanium backup. The toolkit didn't get them all. I have not tried Xposed again. I may wait a bit and see if that was the cause.
Click to expand...
Click to collapse
Highly doubt Xposed would cause since I've been using it for a long time. As previously said, it was probably Titanium Backup messing with your ID.
So I have been using TB for years now, since back in the day that I had the HTC Hero and I have never had a problem with it until now. There are some certain apps that it will just not restore no matter what I try. It begins restoring the others just fine but when it gets to the same exact apps, it just stops and freezes.
I am using the Restore missing apps with data option.
I have tried deleting all backups and backing up again. I have tried verifying my backups various times. I have also tried not using batch restore for those specific apps (Going directly to that app and restoring just that one app with and without data, and it just hangs as well).
I am using SuperSU with my binary updated and busy box installed. I also changed the application processing mode to indirect. Is anyone else having this same issue? Its not on one specific rom, it happens on every rom I flash may it be stock based or aosp. I have exactly 112 apps backed up so when I have to force stop TB, and go back to uncheck the apps that are not restoring various times to restore the rest, it sucks especially since I am very picky with things working as they should.
Apps it will not restore:
Tippy Tipper
Subway Surfer
Nimble Quest
Battlefriends at sea gold
Commander (Star wars)
Instasize
If anyone has any idea what may be causing this and how to fix it, please let me know. Thank you beforehand!
What kernel do you have installed?
Stock CM that came with the official CM12 rom.
But either way, I have had this issue on every rom I have flashed.
valdesr11 said:
But either way, I have had this issue on every rom I have flashed.
Click to expand...
Click to collapse
I've had this happen to me, but I don't remember what I did to fix it.
Do you have SELinux in permissive mode?
guyd said:
I've had this happen to me, but I don't remember what I did to fix it.
Do you have SELinux in permissive mode?
Click to expand...
Click to collapse
Where do I check this?
valdesr11 said:
Where do I check this?
Click to expand...
Click to collapse
> About Phone > SELinux Status
It's in enforced mode. How can I change it?
valdesr11 said:
It's in enforced mode. How can I change it?
Click to expand...
Click to collapse
I use this https://play.google.com/store/apps/details?id=com.mrbimc.selinux
I tested this out and I am still having the same issue with the same apps.
I am having a similar issue. Diff device, but I couldn't find any other info. Oddly yesterday it restored no problem.
I was on a diff rom tho. Maybe I'll flash another rom.
valdesr11 said:
I tested this out and I am still having the same issue with the same apps.
Click to expand...
Click to collapse
If you go to the play store are you able to install them? I have had a few that i can't restore, but once I've installed them from the play store I can restore the backed up data. I haven't been able to figure out why some restore and others don't (unless they aren't compatible with the DPI and the Android version I've found a few that when you look them up in the play store they are not compatible)
scubamikejax904 said:
If you go to the play store are you able to install them? I have had a few that i can't restore, but once I've installed them from the play store I can restore the backed up data. I haven't been able to figure out why some restore and others don't (unless they aren't compatible with the DPI and the Android version I've found a few that when you look them up in the play store they are not compatible)
Click to expand...
Click to collapse
I have been able to install them from the play store without any issue, I just can't restore them using TB no matter what I try. And its weird that its the same apps every time. So it is something that those apps have that does not get along. Can someone manipulate the situation and check on their end? I am running Illusion (Latest version from the 18th) and latest version of TB. See if you can restore those specific apps backed up from any rom.
Try changing the mount namespace separation setting in super su. I got that message when I first installed titanium it was a warning I don't know what it does or if it will fix your problem
I realized today that when backing up the specific apps after deleting all backups (Fresh backup), it rushes through those specific apps like as if it doesn't want to back it up but it doesn't give me an error message.
some apps don't like restoring to a different rom than they were made on.
Have you tried using the option in TB to create an update.zip you can then flash?
Hi there in desperation I come to this thread. Ive tried everything thats suggested in this thread and more.
TT backup Pro home page shows all necessary items like Root etc checked.
Problems with Pro:
1..Nandroid restore crashes immediately on item selection eg as soon as Menu Item Nandroid is selected Titanium crashes.
2..As mentioned by others, some apps wont restore; TT sits there in restore mode with nothing happening. This is on several apps.
3..Menu/Backup data to XML Bookmarks=yes Messages=yes Call log=crash/'Unfortunately, TT bup has stopped.'
4..Several other annoyances in reliability but the above are most important.
I have politely asked Titanium for support but they dont bother answering. After a few days waiting I gave the app a feedback of 1 on Play thinking that would get some response but no!
In 20 years of computer work, I have never had a software supplier with such a terrible support policy, and the feedback page for this app supports this comment.
Im sorry to have to come to this forum asking for help, but the Titanium folks leave me no choice.
As an aside I also use 'Backup Your Mobile' which IMHO is better at restoring settings and reliably restores apps with settings at no cost if you can put up with the ads.
Kind regards,
Alistair.
Since this post and no replies I have submitted 2 more support requests with TTBup support which is done via a web page interface. I even supplied a small video showing the problem. Alogcat does not report any errors which is odd.
Still no replies from TTBup support.
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.
Hi guys, as the title says, I'm having problems restoring apps and app data both individually and through batch restore. I've tried changing the SuperSU mounting method, different versions of TB and changed the app processing mode. I've tried it all on the latest version of TB and the version before that. I have no problems backing up apps though. If I try manually installing the apk (after extracting it from the archive TB backs them up to) it installs fine. BusyBox is also installed, USB debugging is enabled and apps from unknown sources is also checked.
I would manually install all the apps, but I want app data restored too and it would be a very tedious job since I have quite a few to restore (some 173 apps) as I just updated to Marshmallow.
Any advice on what I could try next?
No advice, sorry. But I have the very same problem...
Might have been fixed in new update?
bautrupp said:
No advice, sorry. But I have the very same problem...
Click to expand...
Click to collapse
TB had an update today for Marshmallow support, so maybe that fixed it? Well, anyway I installed them with adb instead since I needed my phone today. I extracted all the apks from the archives and used a batch to list all my apks in a text file, then added "adb install X:\app dir" to the beginning of each line in the text file then changed the extension to .bat and found that TB would restore app data alone in the batch restore commands.
Code:
DIR *.apk /B>APKlist.txt
A fair bit of effort for all my apps, but I got them all back onto my phone eventually with all the data too. I'm happy now, but I'd still like a solution for future reference.
Todays TB update didn't fix it, at least for me.
Luckily I made the update to marshmallow so far only on a spare N7.
bautrupp said:
Todays TB update didn't fix it, at least for me.
Luckily I made the update to marshmallow so far only on a spare N7.
Click to expand...
Click to collapse
I wonder what the problem could be.... Do you know if there's an official thread for TB on here?
EDIT: I've emailed TB, waiting for a reply.
Same issue. It just hangs when trying to restore on Marshmallow.
I agonised over this for hours last night - turns out that the the fix for me was to switch SELinux to permissive mode.
Install this app: http://forum.xda-developers.com/devdb/project/dl/?id=12506 -- open the app, switch to permissive, and give it another go.
I fogt the same problem for hours messing with everything I could think of and this fixed it thank you very much. I know it's a temporary fix until they get the application straightened out but hey its a fix
Sent from my Nexus 6 using Tapatalk
cezuk said:
I agonised over this for hours last night - turns out that the the fix for me was to switch SELinux to permissive mode.
Install this app: http://forum.xda-developers.com/devdb/project/dl/?id=12506 -- open the app, switch to permissive, and give it another go.
Click to expand...
Click to collapse
Mine is already on permissive it seems, now what do I do?
mayurh said:
Mine is already on permissive it seems, now what do I do?
Click to expand...
Click to collapse
Not sure dude, sorry. Switching to permissive mode seemed to fix everything for me - Titanium Backup, Social Contact Sync, StickMount... pretty much everything that needed root.
cezuk said:
Not sure dude, sorry. Switching to permissive mode seemed to fix everything for me - Titanium Backup, Social Contact Sync, StickMount... pretty much everything that needed root.
Click to expand...
Click to collapse
thanks though
not sure why but if the app is already on the device(older version or with no data) then the restore works
so if i try restore an app(looks like only google apps are not restoring)..then tb just hangs at 0%...
once i manually install the app from the app store., tb stops hanging and restores the data?
maybe this can help someone figure out why restores wont work
I'm having the same issue with Titanium Backup Pro 7.6.0.1:
I backed up and validated user apps and data on my rooted Nexus 4 Cyanogenmod 13.0 Android 6.0.1;
Copied the folder to my SuperSU rooted Xiaomi Mi-5s Miui-8 Android 6.0.1;
Enabled apps from unknown sources;
Set SELinux mode to permissive;
$: su
# setenforce 0
# getenforce
# Permissive
Click to expand...
Click to collapse
Updated Titanium's backup storage by searching the device for the Storage folder then 'Reload Application';
Set a filter to list my backed-up user apps from the Nexus;
Set Preferences - App Processing Mode to Auto Direct, and Auto Indirect;
Ran a batch to restore 152 missing user apps with data
Tibu counts through the apps very rapidly, but doesn't install any.
I also made an update zip of apps and data in the new device, and updated it from TWRP without success.
What's the problem?
Thanks
Hello.
I'm having the same issue on titanium 7.6.0.1:
I've tried integrating update system apps into rom but those apps disappear:
-google play store
-android system web view
-smart suite
-talkback
-google text-to-speech output
and the most of my apps are not working now.
I've tried restoring a backup of them I have in titanium backup, but when I click to restore it just don't do anything (it stays at 0% for ever).
My phone is now not connected to my google account anymore now and I can't even add it going to Settings/Account.
Tried rebooting phone but nothing changed.
How do I get them back and the other apps back to work properly?
Thanks.
As I have the Pro version I emailed Titanium support with the problem - but no reply yet.
TiBu seems to work sometimes but not other times and support seems sadly lacking for a paid app; so I copied my issue and a link to this thread to their support.