Related
Has anyone had a problem with the intial setup for Good for Enterprise on custom Android ROMs? I installed it (using an issued PIN) on stock eclair on my Captivate and it worked fine. I then rooted, backed it up via TIBU and restored on Froyo and it still worked fine. The same process worked recently on Gingerbread. However, I have tried multiple custom Froyo ROMs and 1 GB recently and if I try the initial setup (with a new PIN) on anything other than stock eclair (even rooted), it will stop at "retrieving policies" and never complete. I then have to ask for a new PIN from my IT support and revert to eclair and finish the setup, backup, and restore on the later custom ROMs. Has anyone seen this and have any idea why? My IT support has no idea. I am not in a policy checking for root access and it does continue to work with root.
EDIT: I wonder if it is that the device name used in build properties is referenced during that step and it fails due to an unknown device...
Also, I have found that after I have it working after a certain PIN used, if I ever restore to an ealier point (due to a theme gone wrong, etc) then it stops syncing even if the restore point is AFTER I had it working with that PIN. It seems like the local software either is exchanging a dynamic password with the server or there is a message index, etc that has to be in sync. Any thoughts?
When in the Good setup screen, go to Menu>Device Info. Does the Phone number appear? I've been using CM7 just fine with Good but after the last few nightlies, Good no longer works. The phone number doesn't appear in the device info. Good thinks there is no phone network present.
I am a heavy Good user, unfortunately also addicted to changing ROMs on a frequent basis. I have never had an issue with Good running on any ROM, just on restoring from TiBu. I can flash new kernels, themes, etc, and Good works just fine. If I re-flash the same ROM, it resides and works just fine. It is only when flashing a new ROM I have problems. Good appears to restore OK, but won't pull new emails to the inbox. I ave to get a new PIN and re-install.
Same here.. i am addicted to flashing as well.
I tried Titanium backup to backup and restore to new ROM, but somehow Good just keep crashing after i put in my password.
I am sure I can ask for new pin, reinstall and what not.. but how often can we ask IT people (for my company at least) for new pins, until one day they may say, bugger off you ROM addict!
Finally figured it out, I think. The trick is to NOT have Good running in persistent mode when you do the backup with TiBu. IOW, reboot and backup with TiBu before you start Good and log in. I did that the last couple of new ROMs and it restored and worked just fine.
Sent from my SGH-I897 using XDA App
GOOD for Enterprise on Imito AM801 Tablet
I am also getting the Phone network is off. This is a tablet and does not have any phone piece or sim card installed. No hardware is even inside the tablet. Has anyone ran accross this issue on tablets?
This works for me.
http://forum.xda-developers.com/showthread.php?p=35263313#post35263313
Good with custom roms
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Anteus20 said:
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Click to expand...
Click to collapse
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
joshic75 said:
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
Click to expand...
Click to collapse
You quoted a 1 year old post, might be hard to get a reply. Also this is for the S1, while the app (GFE) might be the same, the ROMs definitely aren't.
That being said, chances are that the app was updated to prevent that workaround. You could flash a TW based ROM and test it though.
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
joshic75 said:
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
Click to expand...
Click to collapse
There is an xposed module for this.
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
joshic75 said:
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
Click to expand...
Click to collapse
I'm a bit confused here, Custom ROMs are pre-rooted. Therefor, if you're not on TW, you're rooted.
And yes, Xposed does require root. As for Wanam, I duno if it works on AOSP but best way to know is you try
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
joshic75 said:
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
Click to expand...
Click to collapse
I have never personally tried it without root but you can test that fairly easily. I expect it would depend on the module you're using, some require more permissions than others.
I tried it out but it didn't work.
I have to go back to stock ROM
After following the Omni 4.4 Nightlies thread, I thought it would help some people (noobs like me) to have some guidance about how to install Omni in your device and making it easier to get what's needed to make it work. Still, this is not an "official guide", just the procedure I use to flash every day's nightly and I'm open to suggestions and corrections. Also, the resourses quoted here are not my work, just links to the work of the amazing devs in Xda and out there in the Android development world.
Hope it helps. Don't forget to hit "Thanks" in case it was.
Important: be wise and don't go for anything you are not sure about. I can't be held responsible for the results, remember that you are flashing a Custom (Beta stage) ROM, and even when not likely, things can go wrong. If you are unsure about anything, just ask and/or search the forum and the net for other's experience and knowledge, that's the way to go (and learn).
Suggested procedure (updated to November the 30th 2013)
Be sure to check the official thread for lastest news and guidance here.
DOWNLOADS
1) THE RIGHT RECOVERY - Your device must be rooted and running CWM Recovery 6.0.3.2+ or latest TWRP. Latest Philz Recovery is reported to be working too if you prefer. If aren't on CWM/Philz's or not on the right version, you can find a guide to get it and install it here. The safe way to go is to follow any of the procedures listed there. There are also many threads in XDA offering the flashable zip, but if you go down that way, be sure you choose the right version.
2) GET OMNI - Download the latest Omni 4.4 for I9300 Nightly here
3) GET GAPPS - Download the 4.4 Gapps of your choice:
PA Gapps (recommended by XpLoDWilD)
Spec Gapps
Banks Gapps
Any other 4.4 Gapps of your choice (must be 4.4, earlier versions won't work or give you some mean headaches)
4) CUSTOM KERNEL (optional) - If you want to use a custom kernel, download one that you know it's compatible. If you don't know what this means or you are not 100% sure about what you are doing, it would be safer to skip this step. You can explore Xda I9300 forum for info about Custom Kernels if you like.
5) UPDATE SUPERSU - Download the latest Supersu here. Get the Zip to be flashed via CWM. At the moment, the latest can be found here.
INSTALLING
1) If you had to install CWM or Philz, make sure it's done and working.
2) WIPING - Get into recovery. Be sure you make a nandroid backup in case things go wrong. Then, it's time for some wiping. The safer way to go is a Full Wipe, and that means Wiping Data, Cache, and Dalvik. Beware this will result in loosing some user data if you don't got a backup of them (I'd recommend moving anything you want to keep into SD, since Titanium is never a neat choice when flashing a new ROM, you'd probably get your beautiful clean new install dirty if you go that way). Back to wiping, I usually format /system too, just in case.
3) FLASH OMNI - Find and flash the downloaded Omni Build.
4) FLASH GAPPS.
5) FLASH CUSTOM KERNEL (optional) - if you've chosen to do so (should be done before flashing SuperSu Update).
6) FLASH SUPERSU UPDATE.
7) (Optional) Wipe Cache and Dalvik once more. I'm not sure if this is required, just found out it solved some FCs sometimes and since then I do it allways.
8) Reboot.
Post-Installing (Absolutely Optional, but maybe useful)
1) Once you've booted and are past the Gapps Google login and stuff, you might want to install Xposed Framework, in case you use Greenify Pro or just want to access some more customization moduldes. If that's what you want, get the latest 4.4 compatible XPosed Installer APK here and run it. There you need to install the framework and if no errors arise, voilá, you got it. It's reported that you need to set RW privileges to let this happen, if that's the case, you need any root explorer (ES or any other) to do it. And if you aren't able to do so, or still got trouble, you can install BusyBox Installer from the PlayStore, and duh, install it. Or you can just take the advice found here to get that done. Then you'll be able to get /system RW privleges and install Xposed Framework. After doing it, you'll need to reboot, thought.
2) Installing GravityBox or any other Xposed module you want. Gravity is a nice collection of customization options that has been updated recently to support Kitkat. If any others become compatible too, or you want to try any available module to see if it works with 4.4 too, assume the risks and go ahead. Yet, many will become compatible soon, perhaps it would be wiser to wait for that to happen. Back to Gravity, you just need to get it here (make sure to get the last version), install it, enable the Module at Xposed Installer, and reboot.
And that's it. Course you can do plenty of other stuff to your lovely Omni 4.4 Build, but that's up to you. Hope this was of some help and I'm open to any feedback to update the guide and make it better. And in case you spot any mistakes, please let me know. I'm not a dev, just a noob trying to make other noob's life easier.
Enjoy!
Very good guide
Inviato dal mio GT-I9300 utilizzando Tapatalk
Nicely done. Enough info for those who're new to omnirom (like me).
Sent from my GT-I9300 using Tapatalk
Question on Gravitybox. I've installed the Xposed installed, Gravitybox 2.7.6 and ticked on the module, the problem is when Gravitybox opens, it says that Gravitybox System Framework is not responding. What do you think I should do?
fermasia said:
After following the Omni 4.4 Nightlies thread, I thought it would help some people (noobs like me) to have some guidance about how to install Omni in your device and making it easier to get what's needed to make it work. Still, this is not an "official guide", just the procedure I use to flash every day's nightly and I'm open to suggestions and corrections. Also, the resourses quoted here are not my work, just links to the work of the amazing devs in Xda and out there in the Android development world.
Hope it helps. Don't forget to hit "Thanks" in case it was.
Important: be wise and don't go for anything you are not sure about. I can't be held responsible for the results, remember that you are flashing a Custom (Alpha stage) ROM, and even when not likely, things can go wrong. If you are unsure about anything, just ask and/or search the forum and the net for other's experience and knowledge, that's the way to go (and learn).
Suggested procedure (updated to November the 27th 2013)
Be sure to check the official thread for lastest news and guidance here.
DOWNLOADS
1) THE RIGHT RECOVERY - Your device must be rooted and running CWM Recovery 6.0+. Latest Philz Recovery is reported to be working too if you prefer. If aren't on CWM/Philz's or not on the right version, you can find a guide to get it and install it here. The safe way to go is to follow any of the procedures listed there. There are also many threads in XDA offering the flashable zip, but if you go down that way, be sure you choose the right version.
2) GET OMNI - Download the latest Omni 4.4 for I9300 Nightly here
3) GET GAPPS - Download the 4.4 Gapps of your choice:
PA Gapps (recommended by the op)
Spec Gapps
Banks Gapps
Any other 4.4 Gapps of your choice (must be 4.4, earlier versions will likely give you some headaches)
4) CUSTOM KERNEL (optional) - If you want to use a custom kernel, download one that you know it's compatible. If you don't know what this means or you are not 100% sure about what you are doing, it would be safer to skip this step. You can explore Xda I9300 forum for info about Custom Kernels if you like.
5) UPDATE SUPERSU - Download the latest Supersu here. Get the Zip to be flashed via CWM. At the moment, the latest can be found here.
INSTALLING
1) If you had to install CWM or Philz, make sure it's done and working.
2) WIPING - Get into recovery. Now it's time for wiping. The safer way to go is a Full Wipe, and that means Wiping Data, Cache, and Dalvik. Beware this will result in loosing some user data if you don't got a backup of them (I'd recommend moving anything you want to keep into SD, since Titanium is never a neat choice when flashing a new ROM, you'd probably get your beautiful clean new install dirty if you go that way. Back to wiping, I usually format /system too, just in case. Be sure you make a nandroid backup in case things go wrong.
3) FLASH OMNI - Find and flash the downloaded Omni Build.
4) FLASH GAPPS.
5) FLASH CUSTOM KERNEL (optional) - if you've chosen to do so (should be done before flashing SuperSu Update).
6) FLASH SUPERSU UPDATE.
7) (Optional) Wipe Cache and Dalvik once more. I'm not sure if this is required, just found out it solved some FCs sometimes and since then I do it allways.
8) Reboot.
Post-Installing (Absolutely Optional, but maybe useful)
1) Once you've booted and are past the Gapps Google login and stuff, you might want to install Xposed Framework, in case you use Greenify Pro or just want to access some more customization moduldes. If that's what you want, get the latest 4.4 compatible XPosed Installer APK here and run it. There you need to install the framework and if no errors arise, voilá, you got it. It's reported that you need to set RW privileges to let this happen, if that's the case, you need any root explorer (ES or any other) to do it. And if you aren't able to do so, or still got trouble, you can install BusyBox Installer from the PlayStore, and duh, install it. Or you can just take the advice found here to get that done. Then you'll be able to get /system RW privleges and install Xposed Framework. After doing it, you'll need to reboot, thought.
2) Installing GravityBox or any other Xposed module you want. Gravity is a nice collection of customization options that has been updated recently to support Kitkat. If any others become compatible too, or you want to try any available module to see if it works with 4.4 too, assume the risks and go ahead. Yet, many will become compatible soon, perhaps it would be wiser to wait for that to happen. Back to Gravity, you just need to get it at the PlayStore, install it, enable the Module at Xposed Installer, and reboot.
And that's it. Course you can do plenty of other stuff to your lovely Omni 4.4 Build, but that's up to you. Hope this was of some help and I'm open to any feedback to update the guide and make it better. And in case you spot any mistakes, please let me know. I'm not a dev, just a noob trying to make other noob's life easier.
Enjoy!
Click to expand...
Click to collapse
carlallanvela said:
Question on Gravitybox. I've installed the Xposed installed, Gravitybox 2.7.6 and ticked on the module, the problem is when Gravitybox opens, it says that Gravitybox System Framework is not responding. What do you think I should do?
Click to expand...
Click to collapse
Should I assume you: got an i9300, installed following the procedure, did all the wipes, are on the latest (27th) nightly, got the right Xposed Framework installed successfully with no errors, rebooted, installed gravity last version (2.7.6), enabled the gravity module, rebooted again? If so, and can't live without Gravity till next nightly, I'm not sure what else to suggest but reinstall from scratch and try again.
I got it. Looks like I used Xposed Firmware not Installer. Got it working.
fermasia said:
Should I assume you: got an i9300, installed following the procedure, did all the wipes, are on the latest (27th) nightly, got the right Xposed Framework installed successfully with no errors, rebooted, installed gravity last version (2.7.6), enabled the gravity module, rebooted again? If so, and can't live without Gravity till next nightly, I'm not sure what else to suggest but reinstall from scratch and try again.
Click to expand...
Click to collapse
carlallanvela said:
I got it. Looks like I used Xposed Firmware not Installer. Got it working.
Click to expand...
Click to collapse
Cheers :good:
fermasia said:
Cheers :good:
Click to expand...
Click to collapse
This is brilliant. Maybe add the list of known bugs and as they are fixed, you can cross them out, Would definately keep the main thread cleaner. Well done :good:
cornelha said:
This is brilliant. Maybe add the list of known bugs and as they are fixed, you can cross them out, Would definately keep the main thread cleaner. Well done :good:
Click to expand...
Click to collapse
Would be very interesting, but I guess it would be a bit tricky to keep up with known issues and resolution, unless there's somewhere I can check for that information. I guess that would be in the better hands of the devs that are after bugs and solutions on a daily basis. But still, if there's any way I can help keep track and inform about that, I'd be happy to help.
fermasia said:
Would be very interesting, but I guess it would be a bit tricky to keep up with known issues and resolution, unless there's somewhere I can check for that information. I guess that would be in the better hands of the devs that are after bugs and solutions on a daily basis. But still, if there's any way I can help keep track and inform about that, I'd be happy to help.
Click to expand...
Click to collapse
It's all over the Omni Thread. The devs are way too busy building the rom and sorting out bugs. The most common ones relate to Google Services battery drain. Camera issues and root.
cornelha said:
It's all over the Omni Thread. The devs are way too busy building the rom and sorting out bugs. The most common ones relate to Google Services battery drain. Camera issues and root.
Click to expand...
Click to collapse
I'll try to build a list of those, but I believe it wouldn't be serious to post it if not very precise and up-to-date. Think it's a great idea, but again, not having access to de development roadmap, is a big drawback, and I wouldn't want to go around pushing confusing info.
Problems with Root
After I flashed the 15Dec Build, suddenly I found I'm having problems with Root.
I'm flashing SuperSU 1.75 and RootChecker won't finish.
Xposed Framework won't install, etc.
I've trued the RW trick mentioned above but never get a response to 'su'.
Root worked fine prior to this build.
Any easy fix?
harrybarracuda said:
After I flashed the 15Dec Build, suddenly I found I'm having problems with Root.
I'm flashing SuperSU 1.75 and RootChecker won't finish.
Xposed Framework won't install, etc.
I've trued the RW trick mentioned above but never get a response to 'su'.
Root worked fine prior to this build.
Any easy fix?
Click to expand...
Click to collapse
You've got the wrong SuperSU version. See that the guide redirects you to Chainfire's SuperSU Xda thread, and there you'll find the latest recovery flash version is 1.86 and that's the one you want to grab. If not, download it from the Store, then update binaries by recovery, and there you are. For sure, if you want to try to do this procedure the dirty way, see if it works, if not, you should reinstall Omni with full wipes and use the new supersu version. Let me know if you got it solved or we will try to help you out with your problem.
Hello. I just rooted my phone and I tried to uninstall HTC bloatware and virgin mobile bloatware. But every time my phone restarts the apps return. I heard of this happing with HTC phones. I'd like to remove it as this phone has very low storage as it is. I know there is a way but I'm unsure of how. Any help is appreciated.
Bloatware removal issue
Skilleg said:
Hello. I just rooted my phone and I tried to uninstall HTC bloatware and virgin mobile bloatware. But every time my phone restarts the apps return. I heard of this happing with HTC phones. I'd like to remove it as this phone has very low storage as it is. I know there is a way but I'm unsure of how. Any help is appreciated.
Click to expand...
Click to collapse
I am having the same issue. Virgin mobile bloatware returns after a reboot. I am thinking about making a backup and manually deleting the apk files. Has anyone dealt with such an issue before? If so, please offer us some advice. Thank you.
Long time VM users
Pinalp84 said:
I am having the same issue. Virgin mobile bloatware returns after a reboot. I am thinking about making a backup and manually deleting the apk files. Has anyone dealt with such an issue before? If so, please offer us some advice. Thank you.
Click to expand...
Click to collapse
Been using VM for longer than I care to admit. I've seen this once before I forget if it was my Evo 4G or my Optimus kept happening to me until a stable custom rom had them removed. I just honestly didnt reboot it ever
madtipper743 said:
Been using VM for longer than I care to admit. I've seen this once before I forget if it was my Evo 4G or my Optimus kept happening to me until a stable custom rom had them removed. I just honestly didnt reboot it ever
Click to expand...
Click to collapse
I am having the same problem with the Sprint version too. I have gone in with solid explorer and deleted the apk and the ODEX file that's with it and I get the same thing. They return....
The phones need S-OFF or a Custom Rom. I would follow one of those threads for a solution (eventually).
Wow.. Lol. Never had this problem before
Sent from my SM-P600 using XDA Free mobile app
Hi all,
If you install the kernel on this thread, it shouldn't reinstall:
http://forum.xda-developers.com/desire-510/development/sprint-virgin-mobile-stock-desire-510-t2958969
etienne97 said:
Hi all,
If you install the kernel on this thread, it shouldn't reinstall:
http://forum.xda-developers.com/desire-510/development/sprint-virgin-mobile-stock-desire-510-t2958969
Click to expand...
Click to collapse
Even after installing the kernel, the apps still come back. Plus with that kernel there is no ffc, and also SD card has problems. Trying to debloat this phone is a real pain.
luda214 said:
Even after installing the kernel, the apps still come back. Plus with that kernel there is no ffc, and also SD card has problems. Trying to debloat this phone is a real pain.
Click to expand...
Click to collapse
The Cricket version of the WP removed kernel from shinru2004 worked like a charm. All my crap apps and then some are long gone baby. Try it again, or better yet get in touch with OP of your kernel @CurbThePain and ask.
luda214 said:
Even after installing the kernel, the apps still come back. Plus with that kernel there is no ffc, and also SD card has problems. Trying to debloat this phone is a real pain.
Click to expand...
Click to collapse
Flash rbheomax's kernel (I believe both camera's work in V1), or pattyboi's kernel (both cameras work), and use Titanium Backup to remove the apps/bloatware. They shouldn't come back after that but if they do, you can always go into Play Store > Settings > Auto-update Apps and set it to Do not auto-update apps and they will quit re-installing. If you're using Flashify to flash the boot image then make sure you reboot the phone before attempting to remove the apps; if you're using TWRP to flash then you don't have to worry about that.
dip_spit said:
Flash rbheomax's kernel (I believe both camera's work in V1), or pattyboi's kernel (both cameras work), and use Titanium Backup to remove the apps/bloatware. They shouldn't come back after that but if they do, you can always go into Play Store > Settings > Auto-update Apps and set it to Do not auto-update apps and they will quit re-installing. If you're using Flashify to flash the boot image then make sure you reboot the phone before attempting to remove the apps; if you're using TWRP to flash then you don't have to worry about that.
Click to expand...
Click to collapse
That was it. pattyboi's rhinstone kernel was the way to go. Both camera's working and no sd problems with write protection removed. Time to slim this thing down a bit. Thanks dip_spit.
luda214 said:
That was it. pattyboi's rhinstone kernel was the way to go. Both camera's working and no sd problems with write protection removed. Time to slim this thing down a bit. Thanks dip_spit.
Click to expand...
Click to collapse
Has anyone else tried this kernel and can verify there are no issues? I seen HTC has a new update for my phone and wonder how that would work:
Software uptate: 1.49.652.3
This update contains important enhancements and bug fixes, including:
ALERT: Patch for critical security vulnerability ('Stagefright')
- Device Stability improvements, bug fixes
- New and or enhanced features
- Further improvements to performance
Right now, my version is 1.48.652.2
I did a backup, then installed the RUU, let their software update install to keep from getting notified about it incessantly, and then put my kernel back with the application backups.
I just got my phone back from Motorola for warranty work. When I first got it I knew that I was going to be rooting it and loading a custom ROM but I decided to just install my sim and use it just to make calls for the time being. When I went through the initial setup and asked me if I want to restore my backup from previous backups. To my surprise I had a whole list of backups from when I first got my old phone a OnePlus and I was able to choose which apps I wanted to install. Well today I loaded Benzo ROM but after the initial setup it never asked me to restore a backup. Is there still a way I can restore one of my old backups or is this not a feature with Benzo ROM?
Am I missing something?
It could be that the gapps pack you installed didn't include Google's Setup wizard, if it didn't then the restore feature introduced in lollipop won't be available. Though I've noticed with that type of situation that opening the google play store will trigger it to download all the apps you used to have out of the blue for seemingly no reason. (like it did pre-lollipop)
StykerB said:
It could be that the gapps pack you installed didn't include Google's Setup wizard, if it didn't then the restore feature introduced in lollipop won't be available. Though I've noticed with that type of situation that opening the google play store will trigger it to download all the apps you used to have out of the blue for seemingly no reason. (like it did pre-lollipop)
Click to expand...
Click to collapse
So is there a solution to this? I always use the gapps provided on the ROM's thread page, is that always necessary?
Before I sent my Nexus back for warranty, I flashed CM 12.1 and it was able to restore a old backup. So where's the difference?
Using rom specific gapps are not required unless otherwise stated, I usually use Open-Gapps since I like their full Nexus pack and also their Aroma installer pack which allows you to set exactly what you want to install. Also if benzo rom has a feature request section you could ask them to include the feature in a future release.
The difference would probably be that CM 12.1 probably includes the setup wizard apk from google where benzo probably uses the aosp setup wizard which looks almost identical but is missing some "Google specific" features. This is my guess btw I'm not familiar with either gapps pack but I've noticed that not installing a gapps pack and setting up the phone on any rom aside from stock will result with it not giving the restore option.
StykerB said:
Using rom specific gapps are not required unless otherwise stated, I usually use Open-Gapps since I like their full Nexus pack and also their Aroma installer pack which allows you to set exactly what you want to install. Also if benzo rom has a feature request section you could ask them to include the feature in a future release.
The difference would probably be that CM 12.1 probably includes the setup wizard apk from google where benzo probably uses the aosp setup wizard which looks almost identical but is missing some "Google specific" features. This is my guess btw I'm not familiar with either gapps pack but I've noticed that not installing a gapps pack and setting up the phone on any rom aside from stock will result with it not giving the restore option.
Click to expand...
Click to collapse
Thanks. I'm not sure how long I'm going to run this rom I keep on getting app crashes. I just did the OTA update and installed the latest gapps and I'm still getting random crashes.
Hi all,
I have recently tried running RR and loved ridding my Mix of Miui but had issues with root being recognized by my work email even with magisk hide. It would not allow me to run Maas360 because of that.
I then tried Pixel Experience which wasn't rooted (I think) but NFC wasn't working so that wasn't going to work.
I then tried AICP 13.1 which I think wasn't rooted and all things like NFC we're working but when I tried to install the linked Gapps (and a couple different ones) it would load and when I went into Google to set up the account it would hang at looking for details and then almost all Google apps one at a time would show as stopping.
Can anyone recommend a Rom that will give me the pixel experience that will include the Gapps and that isn't rooted.
I appreciate any help in advance.
Thanks
imapfsr said:
Hi all,
I have recently tried running RR and loved ridding my Mix of Miui but had issues with root being recognized by my work email even with magisk hide. It would not allow me to run Maas360 because of that.
I then tried Pixel Experience which wasn't rooted (I think) but NFC wasn't working so that wasn't going to work.
I then tried AICP 13.1 which I think wasn't rooted and all things like NFC we're working but when I tried to install the linked Gapps (and a couple different ones) it would load and when I went into Google to set up the account it would hang at looking for details and then almost all Google apps one at a time would show as stopping.
Can anyone recommend a Rom that will give me the pixel experience that will include the Gapps and that isn't rooted.
I appreciate any help in advance.
Thanks
Click to expand...
Click to collapse
You really need a thorough wipe when coming from miui ROMs as some files from gapps can remain and cause problems, did you try dm-verity instead of magisk, no root but stops device becoming encrypted.
james1089 said:
You really need a thorough wipe when coming from miui ROMs as some files from gapps can remain and cause problems, did you try dm-verity instead of magisk, no root but stops device becoming encrypted.
Click to expand...
Click to collapse
Thanks for the help!
james1089 said:
You really need a thorough wipe when coming from miui ROMs as some files from gapps can remain and cause problems, did you try dm-verity instead of magisk, no root but stops device becoming encrypted.
Click to expand...
Click to collapse
Thanks for your help!