Hey guys!
I have been using Omni ROM for a while. And yes, its a pretty stable KitKat ROM! Almost everything works fine without any issue. But the thing that bugged me was root. There wasn't root permission in the the ROM. So no link2sd and no other script works for expanding storage.
So basically, the only major problem in the ROM was ROOT.
So I worked it out and present before you an easy method.
Prerequisites:
Omni ROM
Root flashable zip
Method:
Download the required packages
Install Omni ROM (Refer installation from this)
Reboot
Now go back to recovery and flash root.zip
Reboot
Enjoy
NOTE:
You need to have atleast 3mb in /system
This zip is only for ARM based devices and won't work with x86 based devices
P.S. Personally this is the best ROM to use as daily driver
rhar**** said:
Hey guys!
I have been using Omni ROM for a while. And yes, its a pretty stable KitKat ROM! Almost everything works fine without any issue. But the thing that bugged me was root. There wasn't root permission in the the ROM. So no link2sd and no other script works for expanding storage.
So basically, the only major problem in the ROM was ROOT.
So I worked it out and present before you an easy method.
P.S. Personally this is the best ROM to use as daily driver
Click to expand...
Click to collapse
Congrats! Downloading and will give a try
Looks very much like a normal superuser or superSU install.
Very good that will work on other devices as well. I mean, ours would not have all the google apps on system. No room for one of them
The su binary is much smaller than cm-11's.
Comment, should probably go on xbin, be symlinked to bin.
Normally, superuser.apk is installed as a user app and would be updated as such from play. But may try it this way!
Great work.
Dovidhalevi said:
Looks very much like a normal superuser or superSU install.
Very good that will work on other devices as well. I mean, ours would not have all the google apps on system. No room for one of them
The su binary is much smaller than cm-11's.
Comment, should probably go on xbin, be symlinked to bin.
Normally, superuser.apk is installed as a user app and would be updated as such from play. But may try it this way!
Great work.
Click to expand...
Click to collapse
We can have Google apps on our phone as well. I have managed to do so, at least the important ones.
Gonna upload that too soon
rhar**** said:
We can have Google apps on our phone as well. I have managed to do so, at least the important ones.
Gonna upload that too soon
Click to expand...
Click to collapse
They should NOT be on system/app, especially on our phones. Install from Play as user apps, let link2sd symlink them.
Anyway, flash worked like a charm! Neatly got rid of CWM's superuser, installed superSU which I will leave as a system app for now.
Note that it behaves like what I tried, spawns multiple instances of su and daemonsu (should daemonsu be symlinked to su--why have two copies?).
Link2sd played immediately. Tasker took some time. Xposed almost did not make it. Finally, after a blank screen freeze, reboot, a few attempts, got the dialog! Talking a good ten minutes or aggrivation. What is unique about how this asks for root?
Dovidhalevi said:
They should NOT be on system/app, especially on our phones. Install from Play as user apps, let link2sd symlink them.
Anyway, flash worked like a charm! Neatly got rid of CWM's superuser, installed superSU which I will leave as a system app for now.
Note that it behaves like what I tried, spawns multiple instances of su and daemonsu (should daemonsu be symlinked to su--why have two copies?).
Link2sd played immediately. Tasker took some time. Xposed almost did not make it. Finally, after a blank screen freeze, reboot, a few attempts, got the dialog! Talking a good ten minutes or aggrivation. What is unique about how this asks for root?
Click to expand...
Click to collapse
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'. It's a bit faster this way
Sent from my LG-P500 using XDA Premium 4 mobile app
rhar**** said:
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'
Click to expand...
Click to collapse
The problem is unique to Xposed. Everything else comes either immediately to quickly enough. I will post to that dev thread about this.
Dovidhalevi said:
The problem is unique to Xposed. Everything else comes either immediately to quickly enough. I will post to that dev thread about this.
Click to expand...
Click to collapse
Worked fine for me.
Try again by giving root permissions by default
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
z1022 said:
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
Click to expand...
Click to collapse
Shouldn't happen if the OTA survival mode is present. But ya, the only problem may be the space in /system
z1022 said:
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
Click to expand...
Click to collapse
MUST trim the ROM. Omni is no different here, maybe even bigger.
The superSU installation wil temporarily move some stuff to make room for the root install, then move it back. However, none of that stuff belongs on system. There is not enough room for even one of those gapps. GAPPSLight is trivial and should not fill you up. In other words, trim the ROM first.
---------- Post added at 12:36 AM ---------- Previous post was at 12:30 AM ----------
rhar**** said:
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'. It's a bit faster this way
Click to expand...
Click to collapse
First thing I tried (with my simple daemon start method). Never came up. But up and running now, all's well that ends well.
Question: SuperSU offers to make a backup script first time the UI is exercised. Promises to survive further flashes. Does this indeed work (and ... how)?
I will copy files and edit a version of the setup script from this zip and have them available on my sdcard just in case
Modded Omni Rom
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
sumansur2008 said:
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
Click to expand...
Click to collapse
Smell a rat! Trim that ROM first.
Omni has it own file manager called "Documents." The CMFileManage can be installed as a user app.
BUGs on Omni -- I still am using a daily driver, though:
1. Clock FC's. Widgets appear fine (I use Chronus) but no alarms, stopwatch, wordclocks, etc.
2. GPS apparently not functioning, though location services seem to work. Some apps dependent on GPS FC.
3. Long widget, background process startup times but much better than cm-11
4. About 10 meg worth of apps symlinked by link2sd will be un-symlinked (more probably dereferenced) on start up. Easily cleaned up every few starts. Make sure to recreate link2sd build scripts freshly, reboot after new flash or internal storage mishaps worse than this.
5. Will usually get a wait message on system on startup. Everything works anyway, just open home screen and dismiss.
Those dl builds are genuine "nightlies," scheduled, regardless of whether or not any changes made that will be noticed.
Dovidhalevi said:
Smell a rat! Trim that ROM first.
Omni has it own file manager called "Documents." The CMFileManage can be installed as a user app.
BUGs on Omni -- I still am using a daily driver, though:
1. Clock FC's. Widgets appear fine (I use Chronus) but no alarms, stopwatch, wordclocks, etc.
2. GPS apparently not functioning, though location services seem to work. Some apps dependent on GPS FC.
3. Long widget, background process startup times but much better than cm-11
4. About 10 meg worth of apps symlinked by link2sd will be un-symlinked (more probably dereferenced) on start up. Easily cleaned up every few starts. Make sure to recreate link2sd build scripts freshly, reboot after new flash or internal storage mishaps worse than this.
5. Will usually get a wait message on system on startup. Everything works anyway, just open home screen and dismiss.
Those dl builds are genuine "nightlies," scheduled, regardless of whether or not any changes made that will be noticed.
Click to expand...
Click to collapse
I saw a file manager namely"Documents", but i couldn't install any .apk from there, it said " the file can't be opened" or such that. I flash a file explorer but can't enter enter any subfolder in sdcard. But i will have a another go 2day.
sumansur2008 said:
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
Click to expand...
Click to collapse
Yea, I'll try to make a Trimmed ROM soon
sumansur2008 said:
I saw a file manager namely"Documents", but i couldn't install any .apk from there, it said " the file can't be opened" or such that. I flash a file explorer but can't enter enter any subfolder in sdcard. But i will have a another go 2day.
Click to expand...
Click to collapse
For time being, to install any apk, get a file manager. If you cant, then from Documents, navigate to the apk and hold on it. It will be highlighted. Now copy it and from documents' side panel (swipe from left) go to Downloads and paste it there. Now go to Downloads from app drawer and install from there.
The root is working pretty fine. I tried a lot of times. Sorry to say it now when maybe a week passed, but I forgot to comment. Omni seems to be a good project. And this is the first taste of omni and kit kat, so doble pleasure.
chalo99 said:
The root is working pretty fine. I tried a lot of times. Sorry to say it now when maybe a week passed, but I forgot to comment. Omni seems to be a good project. And this is the first taste of omni and kit kat, so doble pleasure.
Click to expand...
Click to collapse
Yeah. I too use it as a daily driver, and so am thinking of mading it a bit. Like Halo))) or multiwindow
But, unfortunately, not anytime soon
rhar**** said:
Yeah. I too use it as a daily driver, and so am thinking of mading it a bit. Like Halo))) or multiwindow
But, unfortunately, not anytime soon
Click to expand...
Click to collapse
Xposed Xhalo will work in cm-11 but not in omni! Omni takes the window's flag for ... its own multiwindow. So ... where is that?
Xposed multiwindow (its own UI) might work in omni or alongside halo or xhalo ... uses a different flag to avoid the conflict.
In any event, Xposed might be the best way to get these things.
Dovidhalevi said:
Xposed Xhalo will work in cm-11 but not in omni! Omni takes the window's flag for ... its own multiwindow. So ... where is that?
Xposed multiwindow (its own UI) might work in omni or alongside halo or xhalo ... uses a different flag to avoid the conflict.
In any event, Xposed might be the best way to get these things.
Click to expand...
Click to collapse
Yea, I was also wondering about multi-window
And never noticed the thing about HALO. Will try to get something done.
Hi rhar****,
I sucessfully flashed the root.zip into my device(Samsung Galaxy Tab2 10.1 GT-P5110, OMNI6.0.1 based on Android 6), but the SuperUser couldn’t work without a binary file.
The screenshot is in Chinese, it said that ‘The SU Binary file is not installed, and it can’t be downloaded and installed via SuperUser. If you just upgraded to Android 4.3, go to the forum and download the binary file, then install it manually. ’
Can you please offer me the binary file? Or give me an URL?
Related
I want to share the versions of the Market and various Gapps that work for me on Sam's HC EMMC v4.0, 2nd ed. build {Huge props to him, deeper-blue, and others who got HC working on the NC. Without their heroic efforts, I'd be working 4 jobs right now trying to save up to buy a Xoom}
This script is the first one I run after doing a fresh build of HC EMMC, but you should also be able to do it on a stale version of HC as well.
Maps is version 5.0
While I am confident that these files will work for you as well, please remember, individual results may vary---use at your own discretion.
NOTE: The 'GoogleServicesFramework.apk' file in the attached .zip will remove the blue wi-fi icon from Sam's initial build. If you prefer the blue icon over a working Market (My Apps), then DO NOT proceed with the installation!
That being said, please do the following before trudging ahead:
+ Perform a full backup using your bootable CWR SD card [see samuelhalff's thread for instructions on this: http://forum.xda-developers.com/showthread.php?t=947071]
+ Backup each of the original files on your NC that will be replaced by the script
+ See #1 & #2 above...you've been warned
Instructions for Installation:
Extract the files contained within the attached .zip into the same directory as your ADB directory (where your 'adb.exe' file lives). Mine was located here on my computer: C:\android-sdk-windows\platform-tools
Connect your NC to your computer, ensuring ADB is working properly ahead of time
Double-click on the file 'HoneyGAppInstall.cmd' and the script to install the new apps will run
The script will reboot your NC upon completion
Once your NC comes backup from the reboot, you can then login to the Market, select "My Apps" and they should show up right away.
I have also attached the 'build.prop' file I use. This modified file allows me to see tablet apps (NY Times Tablet, More Good News Tablet) and also I can see/download/install both Angry Birds games.
NOTE: The ro.sf.lcd_density is set to 140 in my file. This is not friendly to Zeam and needs to be set to at least 150 for that launcher to work without Force Closing in Portrait mode.
Good luck and let me know if any issues.
EDIT: For those running a build that is not new and already has the original Market setup, would be best to do the following steps after running the Gapps script:
1.) Settings > Manage Applications > All > Market: Clear Cache then Force Stop -- DO NOT Clear Data2.) Settings > Manage Applications > All > Google Services Framework: Clear Data3.) Reboot
~ Razir
Would it be possible to flash the market zip through recovery? Looks like it would work in theory.
I can see all the installed apps on My Apps. Thanks for these files. But I have one problem. My Nook no longer shows up on market.android.com. Anyone else have this problem?
Is Youtube working?
JaysFreaky said:
Is Youtube working?
Click to expand...
Click to collapse
HQ videos don't work. If you disable HQ it works.
Vasanth said:
I can see all the installed apps on My Apps. Thanks for these files. But I have one problem. My Nook no longer shows up on market.android.com. Anyone else have this problem?
Click to expand...
Click to collapse
I don't use that site much, but I did just check it out of curiosity.
I verified it was working by going into: My Market Account > Settings tab. I can see "LogicPDZoom2" with last access of today's date.
bdcrim said:
Would it be possible to flash the market zip through recovery? Looks like it would work in theory.
Click to expand...
Click to collapse
Not being a dev, I don't know how to compile the files I attached and make them flashable.
However, I can tell you that I do have a black-themed Market by Darkslide for my DroidX that is flashable via CWR, but sadly, it did not work for me. I tried it by booting to the CWR SD card. Would have been nice to have the black-themed version.
I also have a flashable version of Zeam, but again, did not work for me.
Now, I have not tried it by going into CWR using Sam's method with his built-in utility. This is because I have not really been able to get that to work 100% of the time and also because it is just so easy to get to CWR via the bootable SD card that I have not really messed with it too much.
I can post the black-themed Market if someone smarter than me wants to take a look at it...might prove useful. I am just not sure if a DX file can be used on the NC
Just let me know and maybe we can figure it out together.
Vasanth said:
HQ videos don't work. If you disable HQ it works.
Click to expand...
Click to collapse
And you have to be pretty fast at disabling that little "HQ" icon in the top-right corner of the screen. From my experience, has to be almost instantaneous by the time it appears on the screen or the video won't load.
360Razir said:
I don't use that site much, but I did just check it out of curiosity.
I verified it was working by going into: My Market Account > Settings tab. I can see "LogicPDZoom2" with last access of today's date.
Click to expand...
Click to collapse
Thanks for checking. I did mess around with the build.prop you provided. I think I messed something up. I will use the file you provided without any changes.
Thanks.
Not being dev minded, I don't know how much help I would be. I was able to extract the apks from the zip file and move them with root explorer, changed permissions and it appears to be holding. Have rebooted twice and still good. Your script in the zip file would not work with cwr since it is windows based, I think. I don't know if the apks would install in recovery without a script, seems like it would not. Anyway, thanks for putting this together. Market works with the apks and the build. prop seems to have helped as well. Thanks again.
360Razir said:
Not being a dev, I don't know how to compile the files I attached and make them flashable.
However, I can tell you that I do have a black-themed Market by Darkslide for my DroidX that is flashable via CWR, but sadly, it did not work for me. I tried it by booting to the CWR SD card. Would have been nice to have the black-themed version.
I also have a flashable version of Zeam, but again, did not work for me.
Now, I have not tried it by going into CWR using Sam's method with his built-in utility. This is because I have not really been able to get that to work 100% of the time and also because it is just so easy to get to CWR via the bootable SD card that I have not really messed with it too much.
I can post the black-themed Market if someone smarter than me wants to take a look at it...might prove useful. I am just not sure if a DX file can be used on the NC
Just let me know and maybe we can figure it out together.
Click to expand...
Click to collapse
bdcrim said:
Not being dev minded, I don't know how much help I would be. I was able to extract the apks from the zip file and move them with root explorer, changed permissions and it appears to be holding. Have rebooted twice and still good. Your script in the zip file would not work with cwr since it is windows based, I think. I don't know if the apks would install in recovery without a script, seems like it would not. Anyway, thanks for putting this together. Market works with the apks and the build. prop seems to have helped as well. Thanks again.
Click to expand...
Click to collapse
You are most welcome and yes, the .zip is not flashable for CWR. XDA will only allow for certain types of files to be uploaded and .zip is one of them, so easier for me to go that route.
Files in the .zip are meant to be extracted into the folder where ADB.exe exists in order for the script to work correctly. As stated in the OP, I have only tested this on a Win7 box, as that is the only platform I have access to at the moment.
Root Explorer will also work, as you already know. So, for those who want to go that route, it is certainly an option. Glad things are working well for you at this point. Thanks for your feedback!
I'm just checking. These are the Android 3.0 gapps from the XOOM, not the 2.3 gapps? (Sorry I'm a little tired and don't have the emmc version installed, I run the SD card version, so I can't test ATM)
kdb424 said:
I'm just checking. These are the Android 3.0 gapps from the XOOM, not the 2.3 gapps? (Sorry I'm a little tired and don't have the emmc version installed, I run the SD card version, so I can't test ATM)
Click to expand...
Click to collapse
2.3, not 3.0.
Just transferred all the apps and the build.prop to a stale build of eMMC 2nd (3 days of use) and other than using root explorer followed the instructions to a T. My apps seemed to work but not thinking I updated maps in the market and now it doesnt work. Tried to uninstall updates in market (didnt seem to even finish the process), replace with my original apk, replace with apk from your zip here, clearing cache and data. Nothing seems to bring it back to life. Anyone else have this problem?
P.S. I think the white wifi icon looks nice.
Sent from my LogicPD Zoom2 using Tapatalk
Just used a combination of Root Explorer and ADB (for the chmod) to use your mod and everything is working great. Thanks a ton for posting this!
Only change I had to make was the LCD Density in the build.prop since I want to use Zeam. I tried using the default launcher but it is so laggy, I just can't.
lospulpo said:
Just transferred all the apps and the build.prop to a stale build of eMMC 2nd (3 days of use) and other than using root explorer followed the instructions to a T. My apps seemed to work but not thinking I updated maps in the market and now it doesnt work. Tried to uninstall updates in market (didnt seem to even finish the process), replace with my original apk, replace with apk from your zip here, clearing cache and data. Nothing seems to bring it back to life. Anyone else have this problem?
P.S. I think the white wifi icon looks nice.
Sent from my LogicPD Zoom2 using Tapatalk
Click to expand...
Click to collapse
Did you get your Maps back and working yet? If not, PM me and we can work on it together, offline. And if we can get it to work, we can post the "method to our madness" here in case others have done the same.
911jason said:
Just used a combination of Root Explorer and ADB (for the chmod) to use your mod and everything is working great. Thanks a ton for posting this!
Only change I had to make was the LCD Density in the build.prop since I want to use Zeam. I tried using the default launcher but it is so laggy, I just can't.
Click to expand...
Click to collapse
Glad all is working for you and that is a good point...I will update the OP to let folks know the build.prop has the LCD Density set at 160, which is not Zeam portrait-mode friendly.
Thanks for the feedback!
Okay, just downloaded the new Amazon Appstore and installed Angry Birds Rio (the first Free App of the Day). Force Close... so I tried both 140 and 160 LCD Densities and still no luck. Tried both of the other Angry Birds (original & seasons) and they force close on all three densities as well.
Any thoughts on why you are able to run them but I can't using the same build.prop? The only thing I had changed from your build.prop was the LCD density, but as I said, even changing it back to match your original setting doesn't make Angry Birds work.
Angry Birds and Angry Birds Seasons work for me. I had to move them to the internal memory. I already tried moving Rio to internal memory, however it still FC's. I can get the game to almost start, but when it's time to start shooting, it FC's. I haven't tried changing the LCD density.
Same issue here with Rio. Tried internal and no dice. Doesn't run at all when on SD.
This is a Deodexed Version Of the newest JellyBean 4.2.2 Leak N5110XXCMG2
Features:
Rooted
insecure boot.img
BusyBox
Zipaligned
Deodexed
Init.d support
adb as root
Bash
Nano
Download: http://www.androidfilehost.com/?fid=23050663588004205
md5: 0386dd0afe5fd788ae2486b7820cfddd
Disclaimer: nothing has been edited this is a full stock rom that you would expect to get from samsung just rooted and deodexed for easy modability,themability
Thanks to:
SamMobile - for the basefirmware package
Dsixda - for the kitchen used to deodex
ChainFire - for superSU
FYI- i will be making me JellyBeans Rom with this base
Welcome back .
Is there much difference between this version and civato other than his has Aroma installer?
2swizzle said:
Welcome back .
Is there much difference between this version and civato other than his has Aroma installer?
Click to expand...
Click to collapse
this is pure stock deodexed nothing removed, and has adb as root. also doesnt have any mods
thank you for posting this here! :good:
Many thanks!
Thanks for this! Works great, feels more fluid... Except doesn't seem to fix the touchscreen deadzones that occur intermittently (but of course that's for Samsung to take care of)
How this update should be installed? Adb?
Edit. Sorry, never mind, this is for N5100 but I have N5100. Waiting for new version for my device.
I am interested in loading this rom on my wife's tablet. I have been flashing rom's on my Motorola Phones for years now and am very comfortable doing so, but a real Novice when it comes to Samsung.
I am on 4.1.2, insecure loader. I have tried both CWM and TWRP recoveries and can use either. I have also used Odin as well.
Question, do I need to wipe data first, and how do I load this rom onto a Samsung Device.
Sorry for the trouble, but I am a fast learner and will be on board soon (I hope)
BobC43 said:
I am interested in loading this rom on my wife's tablet. I have been flashing rom's on my Motorola Phones for years now and am very comfortable doing so, but a real Novice when it comes to Samsung.
I am on 4.1.2, insecure loader. I have tried both CWM and TWRP recoveries and can use either. I have also used Odin as well.
Question, do I need to wipe data first, and how do I load this rom onto a Samsung Device.
Sorry for the trouble, but I am a fast learner and will be on board soon (I hope)
Click to expand...
Click to collapse
Since this is an OS upgrade (4.1.2 to 4.2.2) a data wipe is highly suggested. Frankly, I would suggest wiping system, data, cache and dalvik just for good measure. If she wants to keep a lot of the apps' progress/settings she has, I would install Titanium Backup and back up all user apps first before doing anything. She may have everything synced with her Google account as I believe you can sync apps and their data through Google now, but I haven't tested it yet.
To install the ROM, you'd just need to put it somewhere locally on your tablet, I have a '000Flash' folder on the root of my internal SD storage for any ROMs/kernels/modems (on my phone), etc. Place it in there, then get yourself into recovery. Once in recovery, wipe everything I mentioned above, then go back to the install/flash option of whatever recovery you're using. Flash the .zip file you just downloaded and put locally on your tab. Wait a few minutes and boot her up!
Just make sure you have the right software for the right version tablet you have, N5110 vs N5100.
hayzooos said:
Since this is an OS upgrade (4.1.2 to 4.2.2) a data wipe is highly suggested. Frankly, I would suggest wiping system, data, cache and dalvik just for good measure. If she wants to keep a lot of the apps' progress/settings she has, I would install Titanium Backup and back up all user apps first before doing anything. She may have everything synced with her Google account as I believe you can sync apps and their data through Google now, but I haven't tested it yet.
To install the ROM, you'd just need to put it somewhere locally on your tablet, I have a '000Flash' folder on the root of my internal SD storage for any ROMs/kernels/modems (on my phone), etc. Place it in there, then get yourself into recovery. Once in recovery, wipe everything I mentioned above, then go back to the install/flash option of whatever recovery you're using. Flash the .zip file you just downloaded and put locally on your tab. Wait a few minutes and boot her up!
Just make sure you have the right software for the right version tablet you have, N5110 vs N5100.
Click to expand...
Click to collapse
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
BobC43 said:
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
Click to expand...
Click to collapse
No problem, shouldn't be too different than what you're already used to, but I can understand the need for clarification when it comes to different devices as they're all a little bit different.
OK, on 4.2.2, no problems at all after I found how to turn debugging mode on. THAT IS STRANGE
BobC43 said:
OK, on 4.2.2, no problems at all after I found how to turn debugging mode on. THAT IS STRANGE
Click to expand...
Click to collapse
Hello!
Can you please share how to turn on debugging mode? Thank you in avdavauce!
Sent from my GT-N5110 using xda premium
gqinside said:
Hello!
Can you please share how to turn on debugging mode? Thank you in avdavauce!
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
Settings / About Device /
Then tap the build number 7 times. As you are getting close to 7 taps, the screen will tell you how many more till you are in development.
BobC43 said:
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
Click to expand...
Click to collapse
Also you will need to have CWM or TWRP installed as a custom recovery for it to work. There are plenty of options for installing and the new versions that are non touch should fix any issues uyou had previously. Happy flashing!
Sent from my GT-N5110 using XDA Premium HD app
Yo Nate Dogg!!!!
I am Here!
Now we can get Jammin on this one too!!!!
I will be Flashing this on Friday, Looking around the hood now just seeing what is what on this Note 8!
Get some of that fly a$$ **** from the Note 2 over here! lol
Piece my brotha!
See you soon!
~B
@beanstown106
I'm all rooted and running the ROM...
This ROM definitely needs a little TLC...
How about putting a list of requests together so maybe we have an Idea of what we can expect?
Here is a thread for customizing this ROM!!!
Here is a link to the Google Edition 4.3 Camera
This works I have it installed. and it is pretty sweet. (even on a 5mp Camera)
I installed xposed framework today and it works well on this ROM. Has anyone else tried this?
You can go here for other mods to add to it...
After you have the Xposed frame work installed you can install the app_settings see attachments, to modify the per app DPI settings.
example, you open up app settings go to gmail, set the dpi to 160 & screen (dp): 1000x1600
I did this for System settings as well and they look nice.
Play around with it and we can build on it...
You can find other mods that you can see if they work and build a list in a new thread. REMEMBER TO BACK UP FIRST!
Ge the disabler in attachments to flash in case you get into a boot loop. These work well since this is a stock ROM.
NottachXposed works very nicely for this ROM... You just have to play with it a little bit, but you can tweak it out nicely...
Don't forget to grab the Multi-Window Manager over in the Themes and app section. It works Great Without any flaws so far...!
If you need a 3-way reboot menu, here is an excellent app here for that...
Knock it Off Please
OK, please stop with all the "bad-mouthing" and "trolling" and... the "Off-Topic" posts. You know the rules, especially in the Dev Forum.
You wanna post garbage or talk about who's gonna do what, then go to the main Android "Off Topic" forum.
Thread cleaned. (please don't make me come back in here again)
MD
Thanks for the deodexed, recovery flashable rom. I just flashed it and got everything set up. So far everything is running great.
Sent from my GT-N5110 using Xparent Green Tapatalk 2
It took nearly 24 hours to upload due to my dreadful internet connection but here it is, the latest Android version for the galaxy Mega I9200 AKA Kit Kat I9200XXUDNE4, repacked with a full Knox free bootloader.:good:
DISCLAIMER
I'm not responsible for anything, as usual procede only if you know what you do, and make a backup beforehands in case things go out of control.
This said since this ROM is Knox free you will be able to get back to 4.2.2 or to whatever ROM you want in case you don't like Kit Kat.
IMPORTANT
You can flash this ROM ONLY if you come from a non Knox Rom.
It means that if you were on a ROM that had Knox, like the latest 4.2.2 versions, you can't flash this ROM and in that case you'll have to go for the regular 4.4.2 Knox version available at sammobile.
BEFORE TO FLASH
Get a custom recovery, cuz this ROM comes without any recovery.
Why?
Because at the time I was testing it I kept my custom recovery to see if I could reuse it with Kit Kat, and since it worked, and since I don't want to loose again 24 hours to upload an other ROM with a recovery, you'll have to go like this.
There are plenty of custom recoveries on the forum, as for me I use that one:
http://forum.xda-developers.com/showthread.php?t=2415294
but you can use any one you like, it doesn't matter as long as it has been installed BEFORE to flash Kit Kat.
Edit
If for some reasons you want to stick to stock recovery head to post #5, I've attached it there with some instructions.
THE FLASH
Download the ROM, unrar it and you'll get a tar.md5 file.
Open ODIN 3.04, put the file in the PDA section.
On your phone, enter download mode (press volume down and start at the same time), then connect it to your computer.
Once it has been recognized by Odin (it gets blue on the left upper case) start the flash.
It will take approx 5 mns before it reboots, that's it.
If everything goes ok it will reboot twice and then it will enter the set up wizard.
It could be that some app forces close and that it reboots one more time, in that case you'll have to enter recovery and format /data (and since you have a custom recovery you can do so without erasing your sd card contents).
ROOT
Easy, download the latest SuperSU_1.94.zip from the master chainfire, flash it from recovery, reboot, voila.
REMOVING THE LAST KNOX TRACES:
This has to be done manually (I could have done it and repacked/uploaded a new pre rooted ROM with everything done but sorry, my connection is too slow )
There are some Knox apps in the /system/app folder and in the system/priv-app folder:
-the ones that have Knox in their name are easy to guess;
-one is called KLMSAgent and should be deleted as well, and so too ContainerAgent.apk, ContainerAgent.odex, ContainerEventsRelayManager.apk and ContainerEventsRelayManager.odex.
In the /system/lib folder delete libknoxdrawglfunction.so.
Delete completely the system/preloadedkiosk folder and the system/preloadedsso folder.
In data/data delete the com.sec.knox.seandroid folder and the com.sec.knox.store, and the other com.sec.knox whatever folders there are.
Enjoy!!!:silly:
Stay tuned, in the coming days I will put some mods here...
I already made a deodexed version but I don't think I will upload it since it takes too long (24 hours again), so if anyone with a better connection feels like doing it he or she is welcome!
THE LINK?
Here it is:cyclops::
https://mega.co.nz/#!6lhzGaab!zIFiED3APN7_lHAT5YRPbgJqb6lyrLZJwjs-gw9kLEQ
CREDITS
@SilviuMik for the tuto
@Chainfire for the root
@XDA for the opportunities it gives to all of us
Reserved, for some hopefully soon to come stuff
I'm guessing we can't jsut flash this in recovery, right?
unclefab said:
-cut-
Get a custom recovery, cuz this ROM comes without any recovery.
Why?
Because at the time I was testing it I kept my custom recovery to see if I could reuse it with Kit Kat, and since it worked, and since I don't want to loose again 24 hours to upload an other ROM with a recovery, you'll have to go like this.
-cut-
Click to expand...
Click to collapse
I expect you are ready for udate and version WITH recovery already started to upload? Please be serious of your work!
trurl3 said:
I expect you are ready for udate and version WITH recovery already started to upload? Please be serious of your work!
Click to expand...
Click to collapse
Yep, I have to be serious:cyclops: so here it is, I packed a stock recovery in case someone needs it for some reason (s).
It took (only) 15 mns to upload (not bad for a 10 mb file )...
Download the file, open Odin 3.04, put the file in PDA, flash, now you have KK's stock recovery, boooooo:laugh:
http://d-h.st/PGb
@bnb25
nope, you can't flash the ROM from recovery.
If some people are interested I can upload the deodexed version in the coming days when I have time, unless someone else does it before
I flashed somr stock rooted Rom awhile ago on the gf's phone. I been waiting on this update b4 doing anything. The phone acts up. Performance issues. She keeps ot close to full. Moving to sdcard doesn't work anymore. (That broke b4 filling the phone up. But didn't know that when we bought a 16gb sdcard.) So....thus has knox removed. You mentioned stock recovery as an option. You mean the stock kitkat recovery for the phone? Meaning that will introduce knox if you choose it? And if you do choose stock recovery with knox it can be rooted right? Just saying cause usually when first comes out it takes a lil time for someone to root it.
Sent from my SM-N900P using Tapatalk
i try this rom for 10 minutes and it keep restarting..
so i flash again with ODIN 3.04, and it keep restarting again..
i have wipe data and cache+dalvik, i use twrp recovery.
can you troubleshoot this problem?
thank you :good:
sorry for my bad english...
Works fine for me. I had latest official 4.2.2 rom; I then flash a custom recovery and a rooted rom before I flash this rom via odin. After flashing this rom, I wiped it factory reset. All is well for me. 24hrs now. Thumbs up me general.....
Sent from my GT-I9200 using XDA Premium 4 mobile app
@ninja_unmatched:
the recovery I attached is the stock KK recovery, and AFAIK it doesn't have Knox in it. About rooting a Knox cursed ROM, some people say it's easy but I don't have any personal experience on that matter.
But anyway, why don't you want to use a custom recovery?
I kept the CWM I had on 4.2.2, and after I upgraded to 4.4.2 it took me 2 minutes to root with Chainfire's SuperSu_1.94.zip...
So now I'm on Knox free KK, with custom recovery and root.
@congquer:
do a full factory reset and see if it helps.
@fpage:
nice to read that it works fine for you!:good:
@all:
if you are rooted and want to enable quad multi windows view (up to 4 apps opened at once on the same screen, fully resizable), check my thread in the themes and apps section..:
One of the best KK's new features cool:...
works like a charm, i've installed via odin, but lost root for some reason
Well the girl is like any other nooby internet user. She knows enough to get it infected over and over....lol. Knox actually helps a lil with that. I used to use my phone (Note 3) to check questionable sites out for clients. Knox would do its pop ups alerting me to there being something going on that I do not want. It has actually helped....weird thing sort of. Now of course it doesn't do that anymore but for her......it might lower my headaches if you know what I mean?
But...no I'm about to try it out now anyways after I backup her phone.
Sent from my SM-N900P using Tapatalk
It could be that some app forces close and that it reboots one more time, in that case you'll have to enter recovery and format /data
This step right here causes the same boot loop mentioned. An app forces closes just like you said. soon as you format /data after a reboot it goes into a boot loop. I am also using TWRP 2.7
You have to clear cache not data. Even with that alot of apps just force close.
Sent from my SM-N900P using Tapatalk
I am rooted and working like a charm. Quad window working and alot of modules via xposed installer.
Sent from my GT-I9200 using XDA Premium 4 mobile app
Well it didn't work for me. And the supersu only caused freezing then reboot. I just went and flashed stock. Maybe I'll root it later. The process also messed with the sdcard. Made it unreadable. So I used an app (Called Photorec) to recover some of the files from the 16gb sdcard she has.
Sent from my SM-N900P using Tapatalk
whenever I want to delete knox from system/app, it always failed to delete.
I wonder why?
@ninja_unmatched:
your girl seems to be like mine, willy to use the phone but messing it all the time, and then calling her man to fix it:cyclops:.
But you are worse tham me cuz you use her phone as a guinea pig!
The problem with SuperSu is that at first you can't install it a a system app.
In order to fix this you'll need either twrp recovery or aroma file manager ( http://forum.xda-developers.com/showthread.php?t=1646108 ) and do as follows:
-download SuperSu zip,
-extract the app from the zip but keep the zip intact,
-flash the SuperSu zip,
-do not reboot but go to your file system while still in recovery, either from the twrp menu or by flashing the aroma file manager file,
-delete SuperSu from the system/app folder,
-reboot,
-install the SuperSu apk manually as you would with any apk.
Now you are rooted, and your SuperSu being on your data/app folder it doesn't force close anymore.
Later you can convert SuperSu into a system app from the apk's settings.
But this force close is a problem on KK, cuz everytime an app FC (not only SuperSu) the phone reboots, pretty annoying and definitely a deal breaker for me.
The messing with the files is another problem, it's because somehow KK uses another format than JB. But this one is easy to overcome, just connect your phone to your computer and copy the files to it, or you can copy them from recovery/aroma file manager (that's what I did, at first I thought it was gone but nope, it's just a format stoy) to anywhere on your phone.
@fpage:
I'm happy for you if everything works:good:
@serpentlord:
salaam manis dari Jowo!:laugh:
Are you rooted? Sorry if the question sounds obvious, but if you are then deleting the Knox apks shouldn't be a problem.
Otherwise if it doesn't work, use aroma file manager (see above, and don't forget to push thanks for @amarullz our dev from Bandung!) and delete the Knox stuff from within recovery.
That said I went back to 4.2.2, this KK is plagued with bugs and I don't like the new multi windows implementation, so until they make a more stable version and until I find out whether I can implement some of JB's multi windows functions in it or not I'll stick to 4.2.2...
I'll make soon a thread about specific KK's bugs, hopefully sammy will listen but don't hold your breath
A guinea pig....lol. yeah. Only thing I ever did was flash a stock 4.2.2 rooted Rom. For wifi tethering purposes. It was fine for awhile. She starts complaining about it....I find she filled the thing up. Apps, apps, apps, mad games. I move some of the apps to the 8gb card. That helped. Later she fills it up again. I get a 16gb card and then find out it won't move anything to the card. Broke that somewhere after the 8gb card move. She goes on facebook and clicks on those questionable site posts and jave you sign up while giving them permission to post on your profile and all sorts if sites I find are questionable. That and apps from blackmart and from that site that offers hacked android games/apps.
So far now she seems fine on the stock official 4.4.2. It has a few widgets and apps in Russian. I've seen a few bugs that clear up on their own.
1. The lock screen took a bit to update. (What I mean is this. I know when playing music will say Milk it will show also on the lock screen. It wasn't doing that. Had to reboot to get that going.)
2. There is an app called Wish. It allows you to send something you think another person would be interested in that also has wish. That feature doesn't work to well. You can choose facebook or google+. FB no work at all. I think that is some other reason for that one. Google+ works but only if you choose the regular browser. Through chrome the page doesn't pop up woth the option to use the app to open the link.
And generally I've just run into these lil quarks that eventually just start working. Or partially work enough to get by.
Sent from my SM-N900P using Tapatalk
unclefab said:
salaam manis dari Jowo!:laugh:
Are you rooted? Sorry if the question sounds obvious, but if you are then deleting the Knox apks shouldn't be a problem.
Otherwise if it doesn't work, use aroma file manager (see above, and don't forget to push thanks for @amarullz our dev from Bandung!) and delete the Knox stuff from within recovery.
That said I went back to 4.2.2, this KK is plagued with bugs and I don't like the new multi windows implementation, so until they make a more stable version and until I find out whether I can implement some of JB's multi windows functions in it or not I'll stick to 4.2.2...
I'll make soon a thread about specific KK's bugs, hopefully sammy will listen but don't hold your breath
Click to expand...
Click to collapse
Salam manis dari Jakarta! :laugh:
Yes, my device is rooted. I've tried root browser, root explorer and soon. but it ends with the same result. I wonder why.
And my device also keep restarting every 10 minutes. Is it a bug?
@ninja_unmatched:
I can't tell about this wish.apk and widgets, at the time I was still on 4.4.2 I had stripped the Rom down to only about 20 system apps.
I allways do this on my ROMs cuz I don't like stock apps, I rather uninstall all that stuff and replace it by third part apps that are easier to manage and not so much on the spying/bloatware side...
@serpentlord:
what happens is probably that you have an app that forces closes, and this is what makes the phone reboot. I had the same problem and in my case it was youtube, in your case it could be any other app.
Just start your phone and keep an eye on it until it says "sorry app whatever has closed". Then if it reboots you know from wish app it comes and you can uninstall it and/or replace it with another app or another version from the same app.
A few days ago, there was an update from zhuhang for the already released Viper4Android 2.5.0.5. It addresses the issues that a lot of people are having with getting V4A working under Nougat. I tested it with my ROM, and the driver installed without error. So then I decided to make a flashable zip that would preinstall the driver and save you a few minutes plus a reboot. Other than possibly needing to grant Storage permissions in Settings, this is a quick flash and go.
The zip that should work on any LG-based ROM, and possibly on AOSP-based as well. Just download, flash in TWRP, and reboot. You may need to grant Storage permissions in Settings.
XDA Thread:
https://forum.xda-developers.com/showthread.php?t=2191223
V4A Blog Site:
http://vipersaudio.com/blog/?page_id=31
I [obviously] didn't create V4A, but if you include my zip in your ROM, please give a mention and link back to this thread.
First
Thanks for this.. I'm sure many will get use out of it..!
Not sure if I did something wrong or not - but I can't get it to work.
I'm on DevDigital's ls997 ver 6.5 magisk phh.
Flashed in twrp. Granted root permision.
go to SuperSU / un-check Mount_name spaces separately / under the settings. turn on adb debugging.
Inscribed via LG v20 (iOS 11.1.0 Aplha)
midmadn said:
Not sure if I did something wrong or not - but I can't get it to work.
I'm on DevDigital's ls997 ver 6.5 magisk phh.
Flashed in twrp. Granted root permision.
Click to expand...
Click to collapse
You shouldn't have been promoted to grant root access. V4A only needs root to install the driver, which is preinstalled.
If you're being prompted to install a driver, the ROM likely uses a different conf file to control audio.
Sent from my iPhone 7 Plus using Tapatalk
He built and ported to magisk recently. Has a module you need to install then install Swansong
I haven't played with it yet. I like the new app but dont see a diffence in drivers from 2.5.0.4 to 2.5.0.5
Magisk has a compatible module in his downloads via the app that works with my rom (2.5.0.4)
I install that via magisk manager then i pulled the latest viper4arise.apk and installed instead of the older ui viperfx apk that is linked on the downloads page inside magisk manager.
Driver installs correctly for many others as well. You may need to dirtyflash my rom and start over. Magisk manager also received a update yesterday via playstore. The process on phh or magisksu as its now called is different now as its "systemless" vs modifying the actual system files.
If you dont want to go 5through the hassel of above. Just go to developer settings inside of the viper apps settings and turn off selinux and recheck driver status. Im 99% sure it works this way but ive said it before, i wont push the rom this route as i dont perfer it to be off by defualt.
Hope this helps
Got it all worked out thanks to the rom creator above. Team DevDigitel.
Thank You
Thank you for your work on this flashable zip it's much appreciated, I just have a couple of questions though for anyone who might know..
I'm still running the original stock rom (rooted with TWRP) on my LG V20 and a while back I followed the directions from another thread to install V4A, and I was able to get it to work (even through bluetooth) but it's kind of wonky and just hit or miss so I'd really like to try this one out instead.
I'm assuming I should uninstall the version of V4A I have right now but is there anything else that I need to do (besides a nand backup) before flashing this one? Also one of the steps to install the V4A I have right now was deleting a system file (I'll have to go look to be sure but I believe it was something like mixer_paths.xml), so I just thought I'd check to see if that will somehow effect this version or if I possibly need to put the original file back where it was before flashing this one?
I apologize if these are stupid questions but I just thought play it safe and check first before giving this a shot, because even though the version I have is kind of wonky it still works through bluetooth which from what I've read is something that a lot of people haven't been able to get working, and since I use it so much I'm just afraid to even risk losing it. Anyway I'll definitely create a backup before doing anything but any help or suggestions would be appreciated. Thanks!
Sent from a ridiculously modified ColecoVision
jeep447 said:
Thank you for your work on this flashable zip it's much appreciated, I just have a couple of questions though for anyone who might know..
I'm still running the original stock rom (rooted with TWRP) on my LG V20 and a while back I followed the directions from another thread to install V4A, and I was able to get it to work (even through bluetooth) but it's kind of wonky and just hit or miss so I'd really like to try this one out instead.
I'm assuming I should uninstall the version of V4A I have right now but is there anything else that I need to do (besides a nand backup) before flashing this one? Also one of the steps to install the V4A I have right now was deleting a system file (I'll have to go look to be sure but I believe it was something like mixer_paths.xml), so I just thought I'd check to see if that will somehow effect this version or if I possibly need to put the original file back where it was before flashing this one?
I apologize if these are stupid questions but I just thought play it safe and check first before giving this a shot, because even though the version I have is kind of wonky it still works through bluetooth which from what I've read is something that a lot of people haven't been able to get working, and since I use it so much I'm just afraid to even risk losing it. Anyway I'll definitely create a backup before doing anything but any help or suggestions would be appreciated. Thanks!
Sent from a ridiculously modified ColecoVision
Click to expand...
Click to collapse
You don't need to delete any files for this zip. You're supposed to delete /system/etc/audioeffects.conf, but I've done that with the script.
As I use this more, Bluetooth still occasionally doesn't process after pausing for an extended period, like getting out of the car for more than 5 minutes, but all you need to do for it to kick back on is exit V4A from the menu, then open it up again. It'll immediately start processing again.
If you have an unmodified system backup to restore, that will help ensure it works OK, but it may not be needed.
Sent from my iPhone 7 Plus using Tapatalk
NotATreoFan said:
You don't need to delete any files for this zip. You're supposed to delete /system/etc/audioeffects.conf, but I've done that with the script.
As I use this more, Bluetooth still occasionally doesn't process after pausing for an extended period, like getting out of the car for more than 5 minutes, but all you need to do for it to kick back on is exit V4A from the menu, then open it up again. It'll immediately start processing again.
If you have an unmodified system backup to restore, that will help ensure it works OK, but it may not be needed.
Sent from my iPhone 7 Plus using Tapatalk
Click to expand...
Click to collapse
Thank you for the quick response and for the info and I have no clue why I had mixer_paths on the brain but yeah audioeffects.conf is the file I had to delete while installing the version I have, and as far as what you said about the bluetooth acting up it sounds pretty similar to the wonkyness that I was describing with the version I currently have.
One weird thing that I've noticed with mine (and I don't have the slightest idea how or why it's doing it) is when I'm listening to music through my bluetooth headset, none of the settings under the "Bluetooth" section in V4A have any effect on the sound whatsoever.. but what's weird is that all of the settings under the "Headphones" section do (so it's basically like the section names were swapped somehow)?!
I know for sure that I don't have anything plugged into the jack and the headset I'm using is definitely bluetooth (because it's pretty easy to tell lol), so I have no clue why the settings under headphones would work just fine while the ones under bluetooth don't do it anything at all?
Anyway thank you again for the info I'll give it a shot as soon as I have time and let ya know how it went, and unfortunately the only thing I didn't backup was my unmodified system (it didn't even cross my mind until after I was done rooting) but hopefully it'll still be ok. Thanks again!
Sent from a ridiculously modified ColecoVision
jeep447 said:
Thank you for the quick response and for the info and I have no clue why I had mixer_paths on the brain but yeah audioeffects.conf is the file I had to delete while installing the version I have, and as far as what you said about the bluetooth acting up it sounds pretty similar to the wonkyness that I was describing with the version I currently have.
One weird thing that I've noticed with mine (and I don't have the slightest idea how or why it's doing it) is when I'm listening to music through my bluetooth headset, none of the settings under the "Bluetooth" section in V4A have any effect on the sound whatsoever.. but what's weird is that all of the settings under the "Headphones" section do (so it's basically like the section names were swapped somehow)?!
I know for sure that I don't have anything plugged into the jack and the headset I'm using is definitely bluetooth (because it's pretty easy to tell lol), so I have no clue why the settings under headphones would work just fine while the ones under bluetooth don't do it anything at all?
Anyway thank you again for the info I'll give it a shot as soon as I have time and let ya know how it went, and unfortunately the only thing I didn't backup was my unmodified system (it didn't even cross my mind until after I was done rooting) but hopefully it'll still be ok. Thanks again!
Sent from a ridiculously modified ColecoVision
Click to expand...
Click to collapse
You can definitely control BT devices from the BT tab on this one. And I've found with more testing that before I get in my car, switch to V4A and exit it, then open it again as soon as Play Music connects. Works every time.
I would just like to say thank you!!
I installed this .zip on my T-mo variant over the previous V4A install via dirty flash. It resolved my Bluetooth processing issues on the stock V20 ROM. I've been working on this the past few days. VERY happy it now works in my car like my last phone did!
Now, once I get the nerve to flash over the new modem and bootloader via TWRP to get up to 20j, I'm highly inclined to check out the new ROM by NATF.
Cheers!
joesee said:
I would just like to say thank you!!
I installed this .zip on my T-mo variant over the previous V4A install via dirty flash. It resolved my Bluetooth processing issues on the stock V20 ROM. I've been working on this the past few days. VERY happy it now works in my car like my last phone did!
Now, once I get the nerve to flash over the new modem and bootloader via TWRP to get up to 20j, I'm highly inclined to check out the new ROM by NATF.
Cheers!
Click to expand...
Click to collapse
Thank you.
The new modem and other firmware is not a strict requirement for ROMs built on 10j. You just need to make sure TWRP is on the latest release.
NotATreoFan said:
A few days ago, there was an update from zhuhang for the already released Viper4Android 2.5.0.5. It addresses the issues that a lot of people are having with getting V4A working under Nougat. I tested it with my ROM, and the driver installed without error. So then I decided to make a flashable zip that would preinstall the driver and save you a few minutes plus a reboot. Other than possibly needing to grant Storage permissions in Settings, this is a quick flash and go.
The zip that should work on any LG-based ROM, and possibly on AOSP-based as well. Just download, flash in TWRP, and reboot. You may need to grant Storage permissions in Settings.
XDA Thread:
https://forum.xda-developers.com/showthread.php?t=2191223
V4A Blog Site:
http://vipersaudio.com/blog/?page_id=31
I [obviously] didn't create V4A, but if you include my zip in your ROM, please give a mention and link back to this thread.
Click to expand...
Click to collapse
Out of desperation I tried this on my nexus 6 running 7.1.2, works perfect so far, appreciate you work on this.
Sent from my Nexus 6 using Tapatalk
9wire said:
Out of desperation I tried this on my nexus 6 running 7.1.2, works perfect so far, appreciate you work on this.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Excellent! I'm glad it works for you. The changes made should work on multiple devices, I just couldn't test it myself.
Can we flash this if we have dolby? Or should I uninstall dolby 1st?
Still_living714 said:
Can we flash this if we have dolby? Or should I uninstall dolby 1st?
Click to expand...
Click to collapse
They can co-exist.
Sent from my iPhone 7 Plus using Tapatalk
Thanks!
Just wanted to say thanks for this. It worked great right from the get go. If anybody is wondering its running on JDCTeam AOSP 7.1.2 on a beat up old S4.
NotATreoFan said:
A few days ago, there was an update from zhuhang for the already released Viper4Android 2.5.0.5. It addresses the issues that a lot of people are having with getting V4A working under Nougat. I tested it with my ROM, and the driver installed without error. So then I decided to make a flashable zip that would preinstall the driver and save you a few minutes plus a reboot. Other than possibly needing to grant Storage permissions in Settings, this is a quick flash and go.
The zip that should work on any LG-based ROM, and possibly on AOSP-based as well. Just download, flash in TWRP, and reboot. You may need to grant Storage permissions in Settings.
XDA Thread:
https://forum.xda-developers.com/showthread.php?t=2191223
V4A Blog Site:
http://vipersaudio.com/blog/?page_id=31
I [obviously] didn't create V4A, but if you include my zip in your ROM, please give a mention and link back to this thread.
Click to expand...
Click to collapse
always a true hero. hope all is well with you and yours.
Works perfect on Desolation Rom . Just flash and reboot and approve with SuperSU and Awesomeness !
Sent from my LG-LS997 using XDA-Developers Legacy app
Going to try and keep this short, sweet, and to the point.
I modified and created a zip for personal use all the way back to my Nexus 5 days and through my N5X use. I like my ROMs extremely minimal. Removal of media files and applications that I didn't deem necessary to have. Even went as far and told the script to remove the stock launcher and replace it with Nova. This little guy worked wonders for me and saved me loads of time. My app drawer (on initial start up) only consisted of the essentials; phone, contacts, messaging, a file manager, and Google Play. Only leaving the rest to be downloaded as needed.
----------------
Since ROMs aren't abundant yet, I'm deciding to share my zip to those who actually want to remove system apps and not settle on them just being disabled. Also, to keep from going into a file manager after every OTA/update removing each app individually.
-----------------
Had to modify this little guy to work on our phones.. It took me a bit to figure out (of course, right? Nothing is 'straight forward' with these phones )
-----------------
1.) I use this for personal use but did take some consideration in other users so majority of what I don't use is still there, this list would be a lot longer (and yes, some apps are for my older phones and didn't feel like removing them from the script).
2.) I will not remove an app from the removal script - if you don't like whats being removed, don't flash the zip.
3.) If I have forgot something that comes on the phone that CAN be downloaded from the Play Store (and can not be uninstalled), let me know. I'll add it to the script.
4.) If apps you are currently using are in the removal script, don't worry. The script makes them a user app instead of a system app (in my case it did anyway).
What's removed: :highfive:
*Clock (Google)
*Maps
*YouTube
*DownloadProviderUi
*HTMLViewer
*Calendar (Google)
*Drive (Google)
*OmaDmclient
*Photos (Google)
*Gallery2
*BasicDreams
*Calendar (Google)
*GoogleJapaneseInput
*Chrome
*CMFileManager
*Email
*Exchange2
*Galaxy4
*GooglePinyinIME
*Music2 (Google Music)
*NoiseField
*OpenWnn
*PhaseBeam
*Gmail
*Videos (Google Movies)
*KoreanIME
*OpenDelta
*Launcher3
What's added: :victory:
*Google stock bootanimation (black background with no text!)
*1 additional ringtone
*2 additional notifications
*4 additional alarm ringtones
Installation: :silly:
1. backup your ROM (there is no 'undo' button, so if you want whatever you want back, do a restore)
2. flash through TWRP (do not wipe cache/dalvik unless you want to get stuck on the Google logo - a hard power reset solves that problem anyways)
3. reboot
Download: :good:
https://www.androidfilehost.com/?fid=889964283620778129
Thanks to @mauam for the awesome bootanimation!
- A picture of the animation (called Pixel 2) and reference to his thread can be found here:
https://forum.xda-developers.com/android/themes/alienware-t3721978
Again, you all are on XDA for a reason and know the risks of modifying your device in any sense. Since everyone else does this, I'll do it too:
I'm not responsible for your device.
For those that are having force closing issues on certain apps, enabling immersive mode within apps seems to fix the problem..
Things you need:
You need Android Terminal Emulator in the Play Store or cmd on Windows
i would prefer to do this from a PC so you can copy and paste the commands, but it can be done with any terminal emulator also.
Step 1: Connect your phone to your PC enable USB debugging mode
Step2: Open up cmd in Windows or the emulator on your phone and copy/paste or type:
- adb shell
itll give you a '$'
then copy and paste or type:
- settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox
should enable automatically.
so a debloat script and replacing boot ani with a black one? ill give it ago next time i redo my phone lol (i already debloated and have that boot ani)
but nice little addition, i personally love removing bloat my last debloat script i dubbed 'The Purge" lol
Sounds good to me and I hate bloat! thanks for the work!
Caution.,,
This breaks Fi app ... sort of.
the app wont run after zip. uninstall, reload from app store... still cant run app... app prompts to activate phone.. activate runs and app starts to work.
Same with "google" app (the default app that show when you swipe left from home screen.
Gmail too....
elliwigy said:
so a debloat script and replacing boot ani with a black one? ill give it ago next time i redo my phone lol (i already debloated and have that boot ani)
but nice little addition, i personally love removing bloat my last debloat script i dubbed 'The Purge" lol
Click to expand...
Click to collapse
Yep, that's pretty much what it does! The Purge hahah nice name!!
galaxys said:
Sounds good to me and I hate bloat! thanks for the work!
Click to expand...
Click to collapse
Absolutely.. Hope it works out for you.
imaverik said:
This breaks Fi app ... sort of.
the app wont run after zip. uninstall, reload from app store... still cant run app... app prompts to activate phone.. activate runs and app starts to work.
Same with "google" app (the default app that show when you swipe left from home screen.
Gmail too....
Click to expand...
Click to collapse
I don't run the Google Fi app, nor did I even touch anything related to Fi..
My Google app works as intended, and I redownloaded gmail, and that works too.. Idk what could be the issue on your end..
elliwigy said:
so a debloat script and replacing boot ani with a black one? ill give it ago next time i redo my phone lol (i already debloated and have that boot ani)
but nice little addition, i personally love removing bloat my last debloat script i dubbed 'The Purge" lol
Click to expand...
Click to collapse
I think I remember that script. Was that for the S5? ?
Badger50 said:
I think I remember that script. Was that for the S5? ?
Click to expand...
Click to collapse
i believe so haha too lazy to look it up
Those this work with the January update? For some reason when I flash it my device becomes corrupted. I'm using twrp 3.2.1 if that helps
castano22 said:
Those this work with the January update? For some reason when I flash it my device becomes corrupted. I'm using twrp 3.2.1 if that helps
Click to expand...
Click to collapse
Version/update doesn't matter..
Corrupted as in how?
I still use twrp 3.1.1. Beta 2
Corrupted as in it won't let me boot up into the OS. It's with other mods too
So far I've received an issue from a user on here (youll be able to read their issue on the last page) and i assume its user error due to me not having any issues at all..
My question is - has anyone else tried this script with complete success?? Given the 'thanks' i received, im assuming (again lol) that its working fine. In my experience on XDA, people only comment on whats wrong, and keep quiet when things are running as they should.. I'm now asking to voice your success just for reassurance for me
let me know guys, thanks! :good::fingers-crossed:
Just wanted to confirm that the debloat script works on the Feb update.. Just did it myself :highfive:
However, I did have a couple force closes on the Google app and Twitter (weird) -- after some testing, i got it working by enabling 'settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox' again
After I enabled that again, everything functions fine. :good:
Maybe this is needed for some apps that force close after flashing this debloat script (if you like immersive mode in apps)..
I'll post instructions in the 2nd post on the first page
Hey, thanks for this! Any chance of an update to April release?
elliwigy said:
so a debloat script and replacing boot ani with a black one? ill give it ago next time i redo my phone lol (i already debloated and have that boot ani)
but nice little addition, i personally love removing bloat my last debloat script i dubbed 'The Purge" lol
Click to expand...
Click to collapse
do you debloat using TitaniumBackup? Last time I tried that, I got stuck in a bootloop
dr_rick13 said:
do you debloat using TitaniumBackup? Last time I tried that, I got stuck in a bootloop
Click to expand...
Click to collapse
Yeah I find that happens too. Plus despite having busybox titanium isn't even deleting system apps anymore, they are still there after reboot. So for now I stick to freezing...