[Q] 2 quick Gapps questions - Barnes & Noble Nook Tablet

FYI, I use kuzma's latest CM10 builds (currently 1/16/2013) along with 12/12/2012 Signed Gapps from goo.
1 - Every time I do an update when kuzma releases a new version I have to redo Gapps afterwards. Should that be staying intact, or is it normal to have to re-install every time?
2 - My NT is mainly a gaming and reader device. I don't use it for e-mail, music, movies, etc. Is there any way to install ONLY the Google store, or does it require all this other stuff to run properly? I"ve tried several different ways with standalone apk's I found online, but they always give errors. Full Gapps is the only way the store will work.
Thanks in advance.
~Vol

Gapps and the ROM (system files/data) both reside in the same /system partition which gets reformatted by CWM/TWRP recovery every time before a new ROM gets flashed -- hence Gapps needs to be re-flashed as well.
It's not clear which of the apps included in the Gapps zip file are needed in order to have a functional NT with Google Play. Next time you flash a new ROM build you can try removing a few "unwanted" apps from the Gapps zip file before re-flashing it and see what you can get away with.

Good tip. I'll give that a try. Thx!

Related

gapps restore option

Hey yall,
I've been having a blast trying all the different JB ROMs for my i717 Note. I've noticed that in some cases when first booting a fresh ROM, google apps will ask me if I'd like to restore. It then proceeds to automatically download all the apps I had installed before. I think this is awesome. I thought it had to do with the July 26 gapps, but I just flashed the cookies & cream ROM with July 26 gapps and it didn't do it! So is this something that is ROM-specific?
Try re-downloading GApps, might have gotten a bad copy. When you flash GApps do you get an error in TWRP/CWM?
fprice02 said:
Try re-downloading GApps, might have gotten a bad copy. When you flash GApps do you get an error in TWRP/CWM?
Click to expand...
Click to collapse
Not at all, everything goes smoothly. I just figured it had to do with which version of gapps is being used.
It is a feature of setup wizard that is in all android roms(unless removed by dev of specific rom) but is turned off by default on touchwiz roms. It will only run on first bootup. You can see the setting for it in buildprop and apk is in system/app.

Re-rooting?

I have a Note 2 (obviously), and I have rooted my phone the first day I got it and have never updated the phone since I purchased it. So, I am still on 4.1.2. My phone has been super laggy and I want to take the oppurtunity the when I reset my phone that I can take advatages of the new features that mobile phones have by upgrading all the way to 5.1.x.
So, I downloaded CM 12.1 by wilson3q with 5.1 system. I first tried the 5.0 version since the 5.1 looked too new, and did not have time to deal with the bugs. When I flashed the 5.0 version, I got errors of not being able to flash gapps for 5.0 and that I lost my root. I tried downloading the new TWRP to see if I can get a newer version that would work better, but no luck. I got an error saying that I lost my root privileges and did I want TWRP to fix it. I slid yes to fix, but no luck.
The same problem occurred when I tried with 5.1.
So, I ended up restoring my nandroid backup and I am back on 4.1.2 again with root working again.
I am thinking that I am probably supposed to 'step up' the updates, but not sure. Does anyone have a solution or a link to the solution that they can help with?
PS: I did not like the camera that came with the new mod. I do like the stock one. Are there flashes of cameras that I can use as well when I do end up upgrading?
Thank you in advance!!!
geske001 said:
I have a Note 2 (obviously), and I have rooted my phone the first day I got it and have never updated the phone since I purchased it. So, I am still on 4.1.2. My phone has been super laggy and I want to take the oppurtunity the when I reset my phone that I can take advatages of the new features that mobile phones have by upgrading all the way to 5.1.x.
So, I downloaded CM 12.1 by wilson3q with 5.1 system. I first tried the 5.0 version since the 5.1 looked too new, and did not have time to deal with the bugs. When I flashed the 5.0 version, I got errors of not being able to flash gapps for 5.0 and that I lost my root. I tried downloading the new TWRP to see if I can get a newer version that would work better, but no luck. I got an error saying that I lost my root privileges and did I want TWRP to fix it. I slid yes to fix, but no luck.
The same problem occurred when I tried with 5.1.
So, I ended up restoring my nandroid backup and I am back on 4.1.2 again with root working again.
I am thinking that I am probably supposed to 'step up' the updates, but not sure. Does anyone have a solution or a link to the solution that they can help with?
PS: I did not like the camera that came with the new mod. I do like the stock one. Are there flashes of cameras that I can use as well when I do end up upgrading?
Thank you in advance!!!
Click to expand...
Click to collapse
Try Phiz recovery, I've never had trouble with "[I605][CWM Advanced Edition] PhilZ Touch". If I recall we had to start using that one when kit-kat was released (i reserve the right to recall poorly)
I have a link to download mirror here:
http://forum.xda-developers.com/showpost.php?p=60899023&postcount=146
from your new recovery, you should be able to install CM12.1 and 5.1 gaaps recommended in the Wilson3Q i605 thread. from here:
http://forum.xda-developers.com/note-2-verizon/development/rom-unofficial-build-i605-t3069506
FWIW, I am on the 20150803 build and still using the GApps Minimal Edition 2015-04-04 for Android 5.1 (91 MB) from here:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
with no issues to report.
You may also need to track down updated radios (to flash from CWM). I think you can find a link to the updated ND7 Modem/Baseband here:
http://forum.xda-developers.com/showthread.php?t=2765021
somewhere in middle of first post
Good Luck!
PS you may want to flash superSU from recovery... get the zip from chainfire's xda thread here:
http://forum.xda-developers.com/showthread.php?t=1538053
(I've been dirty flashing for so long I dont' remember if the rom came with SuperSU or superuser... as such I can't recall if I had to flash this zip or not, but I probably did if I had issues with root)
Note you may also need to enable root from the settings menu after enabling developer mode.
there should be a "root access" option (or somehting like that there)
PPS are you also remembering to wipe data & clear cache/dalvik?
I have found zoot's mega wipe useful...
http://forum.xda-developers.com/showthread.php?t=1983489
it is for the N7100/N7105, butI have used it on the i605 quite a bit. Initial test result reported here:
http://forum.xda-developers.com/showpost.php?p=44093932&postcount=117
that said zoot's script is probably overkill
jheide44 said:
Try Phiz recovery, I've never had trouble with "[I605][CWM Advanced Edition] PhilZ Touch". If I recall we had to start using that one when kit-kat was released (i reserve the right to recall poorly)
I have a link to download mirror here:
http://forum.xda-developers.com/showpost.php?p=60899023&postcount=146
from your new recovery, you should be able to install CM12.1 and 5.1 gaaps recommended in the Wilson3Q i605 thread. from here:
http://forum.xda-developers.com/note-2-verizon/development/rom-unofficial-build-i605-t3069506
FWIW, I am on the 20150803 build and still using the GApps Minimal Edition 2015-04-04 for Android 5.1 (91 MB) from here:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
with no issues to report.
You may also need to track down updated radios (to flash from CWM). I think you can find a link to the updated ND7 Modem/Baseband here:
http://forum.xda-developers.com/showthread.php?t=2765021
somewhere in middle of first post
Click to expand...
Click to collapse
I assume that you are giving steps in order, BUT I feel that I should flash the radio to 4.4.2 first, in which the link was broken. I have spent a couple hours trying to find another link, but I am afraid that I may be using an incorrect one. Do you have a good link for that, please?
Also, I have ready the newest Samsung 3.10 Odin downloaded and installed, as well as the USB driver installed and downloaded the ADB fastboot. If I remember correctly, I am supposed to move this onto C: and run it to access the device (Note 2). It has been since Android first came out since I have used the ADB though. So, I apologize for the ignorance. So, do I just make sure the adb is in the same directory and run Odin or did I not need ADB and just run Odin?
I also assume that I run the Philz touch after I have gotten to 4.4.2 rooted first. Am I correct by assuming that?
jheide44 said:
Good Luck!
PS you may want to flash superSU from recovery... get the zip from chainfire's xda thread here:
http://forum.xda-developers.com/showthread.php?t=1538053
(I've been dirty flashing for so long I dont' remember if the rom came with SuperSU or superuser... as such I can't recall if I had to flash this zip or not, but I probably did if I had issues with root)
Note you may also need to enable root from the settings menu after enabling developer mode.
there should be a "root access" option (or somehting like that there)
PPS are you also remembering to wipe data & clear cache/dalvik?
I have found zoot's mega wipe useful...
http://forum.xda-developers.com/showthread.php?t=1983489
it is for the N7100/N7105, butI have used it on the i605 quite a bit. Initial test result reported here:
http://forum.xda-developers.com/showpost.php?p=44093932&postcount=117
that said zoot's script is probably overkill
Click to expand...
Click to collapse
Yes, I have done a cache/dalvik wipe a few times (because I have tried reflashing to get it to work with no luck).
I have downloaded the .zip version of superSU as well, and gapps minimal 5.1 with wilson3q's 5.1 ROM. So, I am almost ready to go with the exception of the correct radio upgrade file.
Thank you so much for your help!!! Much appreciated!
PS Will my old WifiTether apk files still work with 5.1 or do I need to get a new one?
Thanks Again!
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
jheide44 said:
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
Click to expand...
Click to collapse
I will try this later. Thank YOU! I have to take kids to practice now.
jheide44 said:
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
Click to expand...
Click to collapse
Sorry to bother you, but I still am getting errors with Failed root access for Titanium Backup Pro. I also cannot find Developer Options in the settings menu.
I have tried flashing the radio before and after wiping and installing the ROM then gapps then superSU. I get into superSU and it asks me for root access and I grant it, but Titanium Backup Pro still says that it has no root access.
Any ideas? Thank YOU!!
geske001 said:
Sorry to bother you, but I still am getting errors with Failed root access for Titanium Backup Pro. I also cannot find Developer Options in the settings menu.
I have tried flashing the radio before and after wiping and installing the ROM then gapps then superSU. I get into superSU and it asks me for root access and I grant it, but Titanium Backup Pro still says that it has no root access.
Any ideas? Thank YOU!!
Click to expand...
Click to collapse
with SuperSU installed, you may need to just need to update binaries. open SuperSU and it should prompt you if necessary. the "normal" option should work (no need to flash from recovery)
for TiBu...
--within SuperSU settings you may need to disable (uncheck) "mount name separation".
--You may also have to enable unknown sources (under settings, security).
-- there might be something to enable for USB debugging as well (TIBU should prompt for it)
FWIW, you can restore user apps/data... but I would not attempt to restore any system data. Personally, I have found it best to get to know a fresh ROM for a while before trying to restore crap from an older ROM . there might be value in re-configuring apps manually and/or restoring them one at a time (after making sure the ROM is working properly) i.e. you won't need any of those aforementioned WiFi tether apps since it is built into the ROM now.
Instructions on enabling developer options in CM ROM, from here: http://wiki.cyanogenmod.org/w/Doc:_developer_options
1- In the Settings app, select About Phone (or About Tablet).
2- Scroll down, and tap the Build number entry seven times. On the seventh tap, you will be notified that "You are now a developer."
3- Return back to the main Settings menu. Developer options and Performance entries should now be visible.
Click to expand...
Click to collapse
(that is likely how to enable superuser that is "baked" into the rom, given you already installed SuperSU it may only complicate matters)
You may be rooted and just having TiBu issues. If all else fails you can check with an app. A long time ago, I've used "Simple Root Checker" by SimoneDev to check root/busybox. It is still in the play store.
Good Luck!
jheide44 said:
with SuperSU installed, you may need to just need to update binaries. open SuperSU and it should prompt you if necessary. the "normal" option should work (no need to flash from recovery)
for TiBu...
--within SuperSU settings you may need to disable (uncheck) "mount name separation".
--You may also have to enable unknown sources (under settings, security).
-- there might be something to enable for USB debugging as well (TIBU should prompt for it)
FWIW, you can restore user apps/data... but I would not attempt to restore any system data. Personally, I have found it best to get to know a fresh ROM for a while before trying to restore crap from an older ROM . there might be value in re-configuring apps manually and/or restoring them one at a time (after making sure the ROM is working properly) i.e. you won't need any of those aforementioned WiFi tether apps since it is built into the ROM now.
Instructions on enabling developer options in CM ROM, from here: http://wiki.cyanogenmod.org/w/Doc:_developer_options
(that is likely how to enable superuser that is "baked" into the rom, given you already installed SuperSU it may only complicate matters)
You may be rooted and just having TiBu issues. If all else fails you can check with an app. A long time ago, I've used "Simple Root Checker" by SimoneDev to check root/busybox. It is still in the play store.
Good Luck!
Click to expand...
Click to collapse
Thank you! It ended up being my version of Titanium Backup. I downloaded a new version and it is good. As far as restoring is concerned, I do not even want the apps themselves restored from there, because there may be a new version and would like a fresh install of those apps. I just want my data restored. For example, I have a surveillance software that I would just like to restore the entries (IP's usernames and passwords). I would like my email settings to be there, so that I do not have to re setup my 7 email addresses. My Text/SMS messages and my alarms. So, I am not trying to do a full restore.
On another note, I am trying to get my calendars back into my phone with no luck. I cannot install google calendar and get my google calendars to populate into my task widget, and the ROM is not letting me set up my POP email addresses. Also, I see no ringtones, so I have no ringers to ring my phone nor tones for my alarm clock. I flashed gapps for 5.1 and I see nothing extra from the ROM. I thought gapps was google apps. Am I trying to do stuff differently than you? There seems to be a few problems in that manner that I am trying to work with.
I am thinking of downgrading to 5.0. Maybe the 5.1 is too new?
Again, THANK YOU for your help!
geske001 said:
Thank you! It ended up being my version of Titanium Backup. I downloaded a new version and it is good. As far as restoring is concerned, I do not even want the apps themselves restored from there, because there may be a new version and would like a fresh install of those apps. I just want my data restored. For example, I have a surveillance software that I would just like to restore the entries (IP's usernames and passwords). I would like my email settings to be there, so that I do not have to re setup my 7 email addresses. My Text/SMS messages and my alarms. So, I am not trying to do a full restore.
On another note, I am trying to get my calendars back into my phone with no luck. I cannot install google calendar and get my google calendars to populate into my task widget, and the ROM is not letting me set up my POP email addresses. Also, I see no ringtones, so I have no ringers to ring my phone nor tones for my alarm clock. I flashed gapps for 5.1 and I see nothing extra from the ROM. I thought gapps was google apps. Am I trying to do stuff differently than you? There seems to be a few problems in that manner that I am trying to work with.
I am thinking of downgrading to 5.0. Maybe the 5.1 is too new?
Again, THANK YOU for your help!
Click to expand...
Click to collapse
I wouldn't downgrade, nobody is actively working on 5.0.2 anymore.... that thread is basically dead. Also, it is likely less "stable"/mature than what you have installed now (that is currently being maintained). i.e. you have the ROM that I would stick with.
like I said I wouldn't restore any thing into system (apps or data)... you can do whatever you please. (but it could be causing you more issues than just biting the bullet & configuring manually) i.e. restoring accounts might result in unanticipated issues, you came from a much older version of android.
all I had to do was install google calendar from play store and then the CM12 calendar stuff all worked (I might have had to restart and/or install the google calendar prior to setting up primary gmail). you might need to remove all your accounts and load them again (a factory reset might be faster though.)
also you might have to update google services and the play store before certain things "play nice".
I know you don't want to hear this but...
from here on out i'll likely point to all your issues being based on restoring system data. (based on my limited knowledge and personal experience). FWIW, I'd try to reconfigure/setup everything manually and you will likely have much better results.
jheide44 said:
I wouldn't downgrade, nobody is actively working on 5.0.2 anymore.... that thread is basically dead. Also, it is likely less "stable"/mature than what you have installed now (that is currently being maintained). i.e. you have the ROM that I would stick with.
like I said I wouldn't restore any thing into system (apps or data)... you can do whatever you please. (but it could be causing you more issues than just biting the bullet & configuring manually) i.e. restoring accounts might result in unanticipated issues, you came from a much older version of android.
all I had to do was install google calendar from play store and then the CM12 calendar stuff all worked (I might have had to restart and/or install the google calendar prior to setting up primary gmail). you might need to remove all your accounts and load them again (a factory reset might be faster though.)
also you might have to update google services and the play store before certain things "play nice".
I know you don't want to hear this but...
from here on out i'll likely point to all your issues being based on restoring system data. (based on my limited knowledge and personal experience). FWIW, I'd try to reconfigure/setup everything manually and you will likely have much better results.
Click to expand...
Click to collapse
I figured that, and feared that and the same time. So, what am I flashing onto the phone with gapps then? Also, one of the reasons I was wanting to go back was because there are a few apps that are not 'compatible' with this system. Meanwhile, I am going to wipe and reset again, and do what you suggested and just reconfigure.
Thanks again!
geske001 said:
I figured that, and feared that and the same time. So, what am I flashing onto the phone with gapps then? Also, one of the reasons I was wanting to go back was because there are a few apps that are not 'compatible' with this system. Meanwhile, I am going to wipe and reset again, and do what you suggested and just reconfigure.
Thanks again!
Click to expand...
Click to collapse
GAaps are the google apps... good read:
http://wiki.rootzwiki.com/Google_Apps
(hopefully I am not out of line for posting a link to that wiki)
many ROMS like CM don't' include gaaps due to licencing/legal issues. which is why the AOSP roms devs often have you flash the GAAPS package separately (also you can pick your package for your fact pattern... full gaaps/minimal gaaps/etc.).
Also the gaaps zip files you flash from recovery install the files into system. a lot of folks like the minimal editions of GAaps because it doesn't force all the apps into system. instead it just gets you up and running with the play store and a few essentials... that lets the user install all the other google apps as user apps, from the play store.
basically taking the "debloat" mentality as far as you can... keep stuff out of system and let the user decide what to install.

After upgrade from Android 4.2: Stuck with Android 5.1 and GApps for 4.2, unusable

I have painted myself into a corner with a Samsung Galaxy S 2. It is my
girlfriend's phone and she wanted to play Pokemon Go. The Android
version there was 4.2 (CyanogenMod) with appropriate Google Apps. It has been
working reasonably well.
Pokemon Go needs to have at least Android 4.4, so an update was due. There was
a CyanogenMod snapshot of 12.1 (Android 5.1) which was installable from within
the old CyanogenMod. I hoped that this would go through well and we did the
upgrade. After the upgrade it indeed had Android 5.1. However, the Google Apps
directly crash, especially the Trebuchet launcher. This means that one cannot
start any apps or use any Google services. Especially the Google Play Store
does not work, it shows the error message [RH-01].
I first thought that we had upgraded to Android 4.4, therefore I installed the
Open GApps nano for 4.4:
(Due to forums policy I am not allowed to hotlink or link to the images.
So this is the best I can do now.)
http ://i.imgur.com/DRHqxNx.jpg
This then (unsurprisingly) failed:
http ://i.imgur.com/qjzrDKw.jpg
At least the error message was really helpful! So then I downloaded Open
GApps nano for 5.1. This then also failed because the GApps that I
have installed together with CyanogenMod years ago were not Open GApps but some
other package:
http ://i.imgur.com/0tI6eEn.jpg
At this point I got uneasy. Her phone turned into a paperweight with a
lockscreen. Since I could not seem to move the GApps forward without flashing
the ROM again, I tried to to so without wiping the data. For this I selected
the update mechanism in Cyanogen Recovery and flashed the Android 5.1
ROM onto the device. After this I tried to install the GApps again. However,
those still fail to install. Here I would guess that the CyanogenMod 12.1
“installer” does not wipe the system partition and leaving remnants of the old
GApps package there.
Since it got late I tried to at least get back to the old state and downloaded
the CyanogenMod with Android 4.2. Trying to flash this failed as the device
type was not picked up correctly:
http ://i.imgur.com/yZ9ilM1.jpg
I do not understand this error. This (or a very similar) version of CyanogenMod
has been present on the device up til yesterday. Why doesn't that work any
more.
A friend of mine suggested to replace the Cyanogen Recovery with the
TWRP. For this I have downloaded the appropriate IMG file from Team Win.
Then using heimdall-frontend on Linux I pulled out the PIT file and put the PIT
file back with the twrp.img file onto the recovery partition. Although the
heimdall-frontend told me that I had a success, there was still the Cyanogen
Recovery.
My current guess is that this phone has hardware which does not allow for a
separate recovery partition unless there is an IsoRec kernel installed. The
CyanogenMod 12.1 should have that, but the recovery is probably the one from
the CyanogenMod 10.1 as the option to update the recovery partition was not
checked when performing the OTA upgrade.
I'm stuck and I have no idea how to get the phone into a working condition. Do
you perhaps have an idea what I could do now?
Hi,
CM12.1 Snapshot unfortunately doesn't have isorec, hence you can not install the twrp .img file.
You can flash this and it will give you isorec kernel:
https://www.androidfilehost.com/?fid=24407100847293132
You will then be able to flash TWRP here:
http://forum.xda-developers.com/devdb/project/dl/?id=17876
Once that's install, reboot back into the recovery and you should have TWRP.
Wipe /system, /cache and /dalvik cache.
Flash ROM then flash gapps, then flash isorec kernel again (because once you flash ROM, you will have overwritten the kernel).
If you can't install gapps and it says you have insufficient space, use opengapps 5.1 pico instead.
gsstudios
I managed to install the IsoRec kernel. Then flashing TWRP worked and I was able to use it. The installation of Android 5.1 has worked, but I still had issues after cleaning up /system. Installing Android 4.2 or 4.4 did not help, it kept crashing either way. 4.2 even had an infinite boot loop.
Then I ended up wiping /data and installed 5.1 and the GApps Pico package. Then everything worked, even Pokémon Go.
Thank you for your help, you saved a phone from being unusable .
I have a smiliar issue. I updated to CM 13.0 as well to newest TWRP. I wanted now to install Open Gapps Pico package but can't flash because of insufficient system space.
Do you have an idea what to do now ?
Achi92131 said:
... but can't flash because of insufficient system space.
Click to expand...
Click to collapse
Perhaps you should open up a new thread as this one does not have the correct heading for it.
As far as I have understood, one can use odin/heimdall and some modified PIT file to repartition the device and make /system larger. I suggest you further look into the partitioning of the system and make /system larger.
Python Guy said:
Perhaps you should open up a new thread as this one does not have the correct heading for it.
As far as I have understood, one can use odin/heimdall and some modified PIT file to repartition the device and make /system larger. I suggest you further look into the partitioning of the system and make /system larger.
Click to expand...
Click to collapse
Thanks Phyton Guy, I will do that.
Tired of failed installed GAPPS ? Different reasons and many many lost time ...
Here is alternative :
1. Install UC Browser
2. Inside , you will find : 9Apps ( the same app as PlayStore )
3. Install 9Apps
- same app as PlayStore
- every app related to Google : working fine.
*** BONUS - install Video Downloader for UC Browser - search Google for this as APK file .
you can download on your phone any video on youtube , inside UC Browser .
That's it ! It's so simple and ...No more Google domination on your Phone !

Open Gapps broken?

I just tried to flash open gapps 6/4/2020 stock for version 9 arm64, after I wiped cache and dalvik and rebooted all my gapps were gone but google pay was showing. I could see all the others were installed looking in system apps though. Trying to run google pay produced an error, see attached. Play services version seems to be broken? Help?
Confirmed, definitely broken. Logs attached. If anyone finds anyone in the open gapps project that actually cares feel free to let them know but from my past experiences it looks like open gapps stock is now over for 9. Might try a larger package, I'll post here if I do and it solves the problem.
Update: The Super package has the same issue.
There are other GAPPS like Nik GAPPS.
ChazzMatt said:
There are other GAPPS like Nik GAPPS.
Click to expand...
Click to collapse
True, but that's another set of issues, and wouldn't I have to get Open Gapps off first?
callihn said:
True, but that's another set of issues, and wouldn't I have to get Open Gapps off first?
Click to expand...
Click to collapse
Yes, but let's back up a step...
What LOS custom ROM do you have installed, for which you need GAPPS?
Just want to make sure we're all on the same page.
LOS-16 and LOS-17 need different GAPPS and of course stock firmware doesn't use GAPPS.
ChazzMatt said:
Yes, but let's back up a step...
What LOS custom ROM do you have installed, for which you need GAPPS?
Just want to make sure we're all on the same page.
LOS-16 and LOS-17 need different GAPPS and of course stock firmware doesn't use GAPPS.
Click to expand...
Click to collapse
Of course stock uses gapps, unless you like wasting your storage to hold the updates and then having to re-update if you land up having to restore or do a factory reset, been doing it since Gingerbread and it works great, or it did, although the majority of updates can easily be moved to the system using Link2SD I have yet to find any realible means to move play services to the system without breaking things which is a major headache, gapps solves that issue and also allows me to choose which apps I want included in a rooted stock rom. The reality is that custom/non-stock ROMs are generally broken in one way or the other and more often than not it's just not something I'm willing to deal with, in addition there's useally too much junk included that I just have no need for and if I did I'd change my stock rooted ROM to fulfill that need. I've actually never seen a stock ROM that didn't use gapps. I'm perfectly happy with rooted and reasonably de-bloated stock and change things I feel are needed, for example adding in call recording, most custom ROMs would actually leave me doing more work to take things out and put things back in, like why take out the native sms, clock, calculator, calender, keyboard etc. they work, they are free and ad free, they are useally small and thus not really bloat and they are often hard to replace with similar function anywhere near their size.
callihn said:
Of course stock uses gapps, unless you like wasting your storage to hold the updates and then having to re-update if you land up having to restore or do a factory reset, been doing it since Gingerbread and it works great, or it did, although the majority of updates can easily be moved to the system using Link2SD I have yet to find any realible means to move play services to the system without breaking things which is a major headache, gapps solves that issue and also allows me to choose which apps I want included in a rooted stock rom. The reality is that custom/non-stock ROMs are generally broken in one way or the other and more often than not it's just not something I'm willing to deal with, in addition there's useally too much junk included that I just have no need for and if I did I'd change my stock rooted ROM to fulfill that need. I've actually never seen a stock ROM that didn't use gapps. I'm perfectly happy with rooted and reasonably de-bloated stock and change things I feel are needed, for example adding in call recording, most custom ROMs would actually leave me doing more work to take things out and put things back in, like why take out the native sms, clock, calculator, calender, keyboard etc. they work, they are free and ad free, they are useally small and thus not really bloat and they are often hard to replace with similar function anywhere near their size.
Click to expand...
Click to collapse
No, you never flash custom ROM GAPPS on STOCK firmware. It already has built in GAPPS. GAPPS are usually only for LOS/AOSP custom ROM, not even stock based custom ROM. So there's your problem.
If you want to do it, go ahead, but I just know what I've been told by several devs.
When I read your question again, it seemed strange the way the wrote it, so that's why I wanted to clarify.
ChazzMatt said:
No, you never flash custom ROM GAPPS on STOCK firmware. It already has built in GAPPS. GAPPS are usually only for LOS/AOSP custom ROM, not even stock based custom ROM. So there's your problem.
If you want to do it, go ahead, but I just know what I've been told by several devs.
When I read your question again, it seemed strange the way the wrote it, so that's why I wanted to clarify.
Click to expand...
Click to collapse
No my problem is that suddenly play services in Open Gapps does not work, worked fine until this flash. Open Gapps is just Gapps, all versions should be the same as released by Google, as stated I've been doing it since Gingerbread and the only issues it's ever caused is when Open Gapps is broken as mentioned in the first post and photos has also been broken for awhile now as it no longer runs in system/app so I install that from play store and move that myself with Link2SD which puts it in system/priv-app where it works. Not sure which question you are referring to, Open Gapps is broken currently and it's my understanding that all Gapps have to be removed to switch to any other and then there's the learning curve that will come with it. If I had the time I'd just create and maintain a package for just core that wouldn't touch the rest. That will likely become a necessity in the future at the rate things are going. So yes, after all these years I'll continue doing it since it's proven to work, assuming it ever gets fixed though I doubt it will as photos has yet to be fixed and that just requires a change in the install script.
callihn said:
No my problem is that suddenly play services in Open Gapps does not work, worked fine until this flash. Open Gapps is just Gapps, all versions should be the same as released by Google, as stated I've been doing it since Gingerbread and the only issues it's ever caused is when Open Gapps is broken as mentioned in the first post and photos has also been broken for awhile now as it no longer runs in system/app so I install that from play store and move that myself with Link2SD which puts it in system/priv-app where it works. Not sure which question you are referring to, Open Gapps is broken currently and it's my understanding that all Gapps have to be removed to switch to any other and then there's the learning curve that will come with it. If I had the time I'd just create and maintain a package for just core that wouldn't touch the rest. That will likely become a necessity in the future at the rate things are going. So yes, after all these years I'll continue doing it since it's proven to work, assuming it ever gets fixed though I doubt it will as photos has yet to be fixed and that just requires a change in the install script.
Click to expand...
Click to collapse
How long have you owned the V30?
You'll need to factory reset the phone to remove the extraneous GAPPS you installed when stock firmware has GAPPS and different resolution versions of the apps.
You still haven't explained why you need gapps on stock firmware. Every V30 dev who creates a stock firmware ROM says do not install GAPPS.
From Aeron Li, the A.IS. and A.I.X. (stock firmware based ROM) dev, who says NOT to do what you are trying to do:
the bad thing is that he can flash/install mismatched gapps and that may make firmware work wrong, or even make safetynet issues and not working Gapps-related things
Click to expand...
Click to collapse
Boombox dev (another stock ROM) and JohnFawkes one of the devs who create the TWRP flashable zips has said not to flash GAPPS over stock firmware.
You're probably going to cause conflicts. But it's your phone.
ChazzMatt said:
How long have you owned the V30?
You'll need to factory reset the phone to remove the extraneous GAPPS you installed when stock firmware has GAPPS and different resolution versions of the apps.
You still haven't explained why you need gapps on stock firmware. Every V30 dev who creates a stock firmware ROM says do not install GAPPS.
From Aeron Li, the A.IS. and A.I.X. (stock firmware based ROM) dev, who says NOT to do what you are trying to do:
Boombox dev (another stock ROM) and JohnFawkes one of the devs who create the TWRP flashable zips has said not to flash GAPPS over stock firmware.
You're probably going to cause conflicts. But it's your phone.
Click to expand...
Click to collapse
I dunno never had any issues and flashed open gapps a few weeks ago, 20200513 to be exact on this phone, no issues. Actually it was explained in detail. Updates take up space, wiping data removes them and hence bandwidth and time is wasted. Moving updates into system saves space and bandwidth. Again I don't do anyone's ROMs I use stock and make the few changes I desire. The only real issue that requires it is moving play services to the system since everything else is movable using Link2SD.

TWRP-flashable Deodexed N910FXXU1DRI2 Stock Firmware (and other related files)

This is derived from the latest N910F UK BTU stock Marshmallow v6.0.1 firmware.
Some info:
PDA/AP (ROM firmware) version: N910FXXU1DRI2
CSC code: N910FBTU1DRJ1 (BTU)
Modem/CP/baseband version: N910FXXS1DQA1
There is no multi-CSC support, it is too much work to add. If you need a different CSC besides BTU, then you should consider @_alexndr's DevBase, @Andycar's ROM, etc. They are based on older firmware, but should work fine. Having this ROM's BTU CSC may mean that carrier-specific features like VOLTE/wifi calling/etc may or may not work. I think the BTU CSC should work fine for most.
Why am I doing this? Well, for one, noone has posted (to my knowledge) a deodexed version of this firmware. And 2nd, as a baseline modding resource for other users, I only ask that I'm given credit for providing the files.
Old zips:
I've taken the N910FXXU1DRI2 stock firmware from SamMobile, deodexed it with SuperR's Kitchen, and created a TWRP-flashable firmware/ROM zip. It is only deodexed, no other changes have been made, nothing has been removed. All stock bloat/Knox is present. It isnt rooted, but you may root it with Magisk/SuperSU/Phh's Superuser. The kernel is pure stock, but you may flash a custom kernel afterwards if you wish. This ROM should pass SafetyNet even without Magisk/SuperSU, as long as you dont flash something like Xposed. Private Mode will not work with this zip out of the box, you will need to flash the modded Private Mode zip to get it to work. You should only use this zip if you just want a deodexed ROM with no additional changes. Flash from TWRP. This zip only includes the stock boot.img and a deodexed system.img.
There is now a 2nd version of this, it is based on the original N910FDeodex.zip, but converted from raw img format to set_metadata format. This version will only flash the used portion of the system partition into /system, resulting in less write hits. If you want a deodexed only version of this ROM with no further changes, then use the set_metadata version. These 2 zips are otherwise identical.
https://androidfilehost.com/?fid=8889791610682928982
https://androidfilehost.com/?fid=8889791610682917301
New revised zip (deodexed, debloated, Knox removed, GApps removed, some minor changes):
This is almost the same as the above zip. Everyone should use this new zip, unless they only want a zip that is deodexed only with no further changes. Private Mode will work out of the box. You will also be able to pass SafetyNet with or without Magisk/SuperSU.
https://androidfilehost.com/?fid=8889791610682924674
See the following post for what's removed:
https://forum.xda-developers.com/showpost.php?p=83379549&postcount=38
And this one too. It includes an optional debloat script that removes even more:
https://forum.xda-developers.com/showpost.php?p=83385447&postcount=44
Link to script:
https://androidfilehost.com/?fid=8889791610682925297
Install order for revised zip:
1. Wipe system/data/cache and flash ROM zip
2. Flash my revised debloat script if you want it
3. Flash latest OpenGApps ARM 6.0 nano zip (dont use anything higher, system apps like Messages/Tags/dialer will be removed if you do!)
4. Flash Google Contacts Sync Adapter zip from Extras section (to avoid "Android is optimizing" on every boot)
5. Check /system/app/WebViewGoogle, /system/priv-app/GooglePackageInstaller, and /system/priv-app/Tags, make sure they're not deleted. If they are, flash the appropriate zips from Extras section
6. Flash any other extras you want
7. Flash custom kernel (optional)
8. Flash root (optional)
9. Reboot into ROM
For MicroG users:
1. Wipe partitions, flash ROM zip.
2. Flash my revised debloat script if you want it.
3. Flash MicroG installer zip. Signature spoofing patch is already built into ROM.
4. Flash play store, backup transport, calendar sync adapter, Google dialer, maps/media effects/widevine libraries, deodexed google contacts sync adapter, google keyboard and swype libraries. These are optional.
5.Flash any other extras you want
6. Flash custom kernel (optional)
7. Flash root (optional)
8. Reboot into ROM
Note: In my tests, ROM didnt pass SafetyNet with MicroG installed. but it did pass when I flashed OpenGApps. This means the fail is due to something in MicroG. Ask in the MicroG XDA thread for help.
Another note: I only used the official APKs from MicroG website, permissions XML file from MicroG Installer Revived, and Play Store APK from APKMirror. You can update MicroG if/when they release new APKs.
Make sure to follow these steps in the order I've listed them!
You only need to use my stock boot image and kernel library modules zip if:
1. Before you flash a custom kernel
2. Before flashing root (skip my zip if you are already using custom kernel)
You can also get rid of a custom kernel/root by flashing this zip. But it is advised that you use Magisk uninstaller zip first. Or to delete SuperSU, you can use the unSU zip by @osm0sis. Then flash my zip.
If you get an error in TWRP when flashing either of these zips, this probably means your MicroSD card is using the GPT partition table, instead of MBR. My advice is to use SD Card Formatter tool to format your SD, then copy the ROM zip onto it and try to flash the zip again. If this doesnt work, post the exact error here.
If you used the "nand erase all" option in Odin, it is advised to format data/cache in TWRP *BEFORE* flashing the ROM zip. Look at the Mount button in TWRP and see if they are checked. If they are, then all is good. If not, use the wipe/format data functions until they are checked. I advise using nand erase all because it cleans data/cache of incompatible data. Especially recommended if you are coming from different firmware/custom ROM.
Please only do clean flashes! Dirty flashes not supported! Do not report bugs if you have dirty flashed! Do not report bugs if you are using other mods like Xposed (or root), etc! Clean flash with no changes, then post here if the bug is still present.
Additional firmware-related files:
My N910FXXU1DRI2 mini firmware package. This includes all files from the stock firmware package with the exception of the boot, system, and cache partitions. This is intended to be flashed before flashing my ROM zip. Boot/system arent needed because they are included in the ROM zip. Cache also isnt needed because its' contents (the UK BTU CSC code) is already processed into the system.img. This package also includes the latest official TWRP recovery, instead of the stock recovery. I would advise that you flash this file before flashing the ROM zip, but it may only be necessary if the ROM fails to boot (which means your installed firmware is an incorrect/incompatible version).
https://androidfilehost.com/?fid=8889791610682917321
You need Odin (version 3.12.7 recommended), Samsung USB drivers, and a Windows PC. In Odin, select the "nand erase all" and select the tar file in the AP slot. Also uncheck the autoreboot box. Leave everything else as-is. Once it is flashed, wait a minute or 2 before unplugging phone from PC.
Once you've done this, pull battery from phone, put it back in, then use VolUp+Home+Power to boot into TWRP. From there you can flash the ROM zip.
Pure stock firmware N910FXXU1DRI2. This is identical to what you would get from SamMobile, I have not modded the firmware in any way. I have only recompressed the tar file so that the total overall download size is smaller. Unpack the 7z file with 7-Zip/WinRAR/some other software, then flash the tar file from Odin. Flashing instructions are the same as above. You only need this if you want a truly clean start with nothing whatsoever changed. This file can be used alone without the others, or it can be flashed before the stock ROM zip. This file does not include TWRP. If you intend on flashing the stock ROM zip, I would suggest using my mini firmware package instead.
Note: I've deleted this file, you can find it in my N910FXXU1DRI2 mega firmware collection thread.
N910FXXU1DRI2 pit file. This file is to be flashed with Odin, if you need to repartition the device. Only use it with a full, official firmware package, like the one from above. I extracted it from my device with TWRP, it is not changed in any way. Most people generally wont need this. Only use this on an N910F, it may brick other devices!!! You've been warned!
https://androidfilehost.com/?fid=8889791610682917326
Link to extra files folder:
https://androidfilehost.com/?w=files&flid=316633
You can use these files to restore removed functionality if you need it. Most of these should be flashed from TWRP. More info below:
1. AccuWeather: Restores AccuWeather widget
2. Android default hosts file: Restores the stock hosts file
3. ANT system apps: Restores ANT apps. These are mainly fitness-related
4. Autorotation library: Flash this if your autorotate isnt working
5. Car Mode/Car Mode Remote: Restores Car Mode
6. Chrome customizations: Restores a system app which sets defaults for Chrome. Generally unneeded
7. DiagMonAgent: Related to Knox, it likes to phone home
8. Dropbox stub: Restores Dropbox stub for SCloud in Settings
9. Easy mode contacts widget: self-explanatory
10. Google FaceDetect library: Part of GApps. Restores FaceDetect library. Google cancelled support for this due to security reasons. You probably dont need it
11. Google Package Installer: Needed by Android! Flash this if OpenGApps zip removes /system/priv-app/GooglePackageInstaller
12. Google WebView: Needed by Android! Flash this if OpenGApps zip removes /system/app/WebViewGoogle
13. Help widget: Restores help/manual widget
14. MicroG installer: This will install GmsCore, GsfProxy, DroidGuard, and a permissions XML file. OpenGApps users dont need this
15. Stock firmware media files: Placed in internal storage by stock recovery. probably not needed. Extract zip and copy to /sdcard/ or /storage/emulated/0
16. Official play store: Installs PS for MicroG users. OpenGApps users dont need this
17. Original Private Mode APK: Restores original Private Mode APK. PM will not work if you flash this. probably not needed
18. Patched Private Mode APK: Installs patched Private Mode APK. PM should work fine now
19. S-Voice: Restores Samsung S-Voice app (who uses this crap?)
20. Collection of updated apps from the Note 4. Extract zip and install the APKs you want.
21. Samsung Apps widget: widget for Galaxy Apps store
22. Samsung Email/Exchange: Restores Samsung email/Exchange apps
23. Samsung_Galaxy_Store_-_Samsung_Cloud_-_Samsung_Account: Restores system apps for Samsung Account, Samsung Cloud, and Galaxy Apps store
24. Samsung game optimizer: restores game optimizer
25. Samsung Gear/Watch: Restores Gear/Watch system apps
26. Samsung Health Service: Restores Health Service, which SHealth depends on
27. Samsung internet browser: Restores stock browser
28. Samsung Kies: Restores Kies stub, which is needed for interfacing with the Kies PC software
29. Samsung QuickConnect/SFinder: restores files needed to make these work. They will also reappear in the pulldown statusbar again
30. Scrapbook: restores Scrapbook app
31. SmartManager v3: restores Smart Manager
32. Stock task manager and widget: restores task manager and Active Applications widget
33. Stock boot image and kernel library modules: restores stock boot.img and the kernel library modules it depends on.
34. Calculator: restores stock calculator
35. Stock clock apps: restores all stock clock apps
36. Stock fonts: restore stock fonts system apps
37. Stock music: restores Samsung Music app
38. stock_others.xml: This is is default others.xml with no added icons in the statusbar quick pulldown menu. Rename to others.xml (all lowercase), copy file to /system/csc/, set permissions to 0644. It is preferred that you do this from TWRP. root file manager will work too, but the owner and UID values must be 0 (root). You must factory reset before the icons will go back to default settings
39. SPlanner Calendar app and widget: Restores stock calendar and widget
40. Stock Tags (NFC) system app: Flash this if the OpenGApps zip removes /system/priv-app/Tags
41. Voice recorder: Restores stock voice recorder app
42. Stock wallpapers: Restores NoiseField and PhaseBeam wallpapers
43. System daydreams apps: Restores stock daydreams apps
44. Tap and pay widget: restores widget that lets you choose payment method
45. Google backup transport: needed by MicroG users, if they want contacts/calendar sync to work. OpenGApps users dont need this
46. Google calendar sync adapter: For MicroG users. Must also flash Google Backup Transport zip. OpenGApps users dont need this
47. Google Dialer: Installs GDialer and other files it needs to work. This is for MicroG users. OpenGApps users can just install GDialer from Play Store instead
48. Google Maps/media effects/widevine libraries: For MicroG users. Some apps wont work without these. OpenGApps users dont need this.
49. Original deodexed Google Contacts Sync Adapter: For MicroG users and OpenGApps users. MicroG users must also flash Google Backup Transport zip. This APK prevents the "Android is optimizing" message on every boot.
50. Google keyboard and Swype libraries: For MicroG users. Installs GBoard, and Swype libraries that other keyboards can use. OpenGApps users dont need this, they can just install GBoard from Play Store.
51. RBoard Theme Manager: This is an app that lets you install optional themes for Gboard. Gboard has a few default themes you can pick, this app lets you install dozens more. Along with sound effects. This app needs root. You dont need to install the RBoard magisk module separately
52. Patched build.prop for RBoard Themes Manager: This zip includes an edited build.prop so that RBoard can work. And empty /system/etc/gboard_theme folder. Rboard installs themes into this folder. Flash this before installing RBoard APK
Other mods I've done:
1. Remove Smart Manager v3. Now you will see "Power Saving" instead of "Battery" in settings
2. Adblocking hosts file integrated
3. Modded Private Mode APK by @TEKHD (now it turns on). However, PM may still break with certain custom kernels, or if you install other mods/changes I havent mentioned
4. Added 27 toggles in the statusbar (pull down to see them). Restore my default others.xml if you dont want them
5. Changed ro.securestorage.support from true to false in build.prop. Apparently Private Mode and SHealth work better when this value is false
Other notes:
Custom kernels: I would recommend FlashPoint kernel, v3 or v4 is fine. I dont recommend Ram Kernel. It is stable, but it has a bug where mobile data will stop working after awhile. It just cuts out, only a reboot will fix it...really annoying. This especially tends to happen when doing big downloads. Other kernels may work too, but i havent tried them. if you install a custom kernel, i'm not responsible if things break, like Private Mode/SafetyNet!
SafetyNet: My revised ROM zip will pass SafetyNet without root. This means you can use Pokemon Go, Netflix, banking apps, etc. There are SN checker apps out there, install one and run the test, should pass. It should also pass even with Magisk installed (it does for me). I didnt test with SuperSU, but if you install it in systemless mode, it might pass SN...no gaurantees. However, if you install Xposed, SN will definitely break. Other mods may or may not break it. I'm not responsible!
2 new additions (modded FlashPoint kernels):
With @kevintm78's permission, I am posting modded zips of FlashPoint v3.1 and FlashPoint v4 beta. They are based on the following zips:
https://androidfilehost.com/?fid=745849072291697438
https://androidfilehost.com/?fid=890129502657582253
See the FlashPoint XDA thread for details on these kernels.
I did this for the following reasons:
1. The original zips have init.d related scripts in the boot.img that remount system partition to read/write on every boot. This is fine...but it prevents most Magisk modules from working (they cant bind mount into the system partition because of the remount).
The original zips also appear to flash BusyBox into the system partition. In addition to this, there is init.d stuff in the boot images. These 2 things can potentially cause SafetyNet to fail.
I have made the following changes:
1. Removed BusyBox installer zips (install it manually if needed, or use Magisk's systemless BusyBox module)
2. Removed Magisk installer zips (because they are very old)
3. Removed init.d functionality from the boot images (this involved deleting 2 scripts, and deleting a line from init.rc)
4. Removed some unnecessary ui_print and set_progress lines from the updater-script files
If you need init.d support in the kernel, then use @osm0sis's Kernel init.d Support Injector zip
http://forum.xda-developers.com/attachment.php?attachmentid=3761907&d=1464187934
Flashing order:
1. Flash either of my custom Flashpoint zips
2. Flash Kernel init.d Support Injector zip
3. Flash root
You can also use Magisk for script execution support on boot instead. SuperSU also has su.d scripts support which works like init.d. I still prefer init.d in the kernel (I'm old school), but others may not.
Kernel Adiutor app is the recommended way of configuring these kernels. Both of the modded zips have the extended battery patches built in, so if you have an extended battery (like me), then the kernels will support it fully. If you just have a stock battery, no worries. i've tried both batteries with these kernels, found no difference in battery life or % displaying correctly.
I cant gaurantee that SafetyNet will pass with my modded zips, I had Xposed installed when I tested them. But i think it should. If you're using Magisk on top of these modded kernels, try turning on Magisk Hide, then run a SN test.
Besides the changes I've listed, nothing else is changed, everything should work pretty much the same as the original FP zips. Report kernel issues in the FP XDA thread if you run into problems, but mention that you're using my zips.
At @kevintm78's request, here are links to the source code for these kernels:
https://github.com/kevintm78/Flashpoint-F_3
https://github.com/kevintm78/Flashpoint-v4
Awesome work!!! @AnonVendetta Nice to see development for the Note 4 in 2020. Much appreciated and I thank you.
this is really great news!
thanks a lot for your efforts, I do love my N4, it can't be simply replaced because of removable battery and s-pen...
I would like to make shure not to run into trouble and kindly ask for a short confirmation if I understand all the info in your first post correctly:
my phone info current status:
android 5.1.1 - N910FXXS1COK1 - TWRP 3.4 - rooted
my target is a rooted Android 6 stock ROM
action:
1. I directly flash your deodexed TWRP-flashable ROM with TWRP.
2. I check if the phone boots correctly.
The result is: I now have a unrooted StockFW still with my TWRP in place.
2. I flash Stock N910FXXU1DRI2 boot.img with Odin in order to be able to successfully flash Magisk via TWRP. (isn't it possible to flash the boot.img also with TWRP?)
3. I now flash latest Magisk.
thanks and best wishes,
Su
@suse_: it's been a long time since I ran KitKat/Lollipop on the Note 4. For your situation, I believe the following steps will work. Since you are coming from much older firmware, flashing the ROM zip alone will almost certainly not boot, because of your older bootloader:
1. Flash my mini firmware package. This will upgrade the bootloader, modem, etc to what is compatible with the ROM. My mini firmware will overwrite your TWRP with latest TWRP, no need to flash TWRP separately.
2. Flash my ROM zip from TWRP. Be sure to wipe data/cache. While it boots, wait up to 20 mins. Because the ROM is deodexed, the 1st boot will take much longer. This is the nature of deodexed ROMs. If it hasnt booted in 20 mins, or bootloops/autoreboots...
Then you should try flashing the full, official firmware package in Odin. You can flash my ROM zip after this, but you dont need to, however you will end up with an odexed ROM if you dont.
Odin will not directly flash boot.img files, but TWRP can. No need to flash this separately unless you havent yet installed root/custom kernel but plan to.
thanks a lot @AnonVendetta for your helpful reply, will try my luck tomorrow and report back:good:
best
Su
I may later release a lightly debloated and deodexed version later. And, if anyone wants it, a debloated odexed version as well. But for right now, my laptop is out of commission, so no more work can be done for about a month. There really isnt much to do anyway, besides change the system image storage format to one that is compressed. As it is, it is just a byte for byte identical copy of the deodexed system partition, no compression applied.
n910f samsung note4
yep cant replace due spen ir removable battery superb fone and very nice size
Ive loaded sooooo many custom roms, but cant find one where everything works and is fast, camera bluetooth etc, presntly on acip
if anyone knows a custom rom where everything works on sm910f appreciate a link.
Its a fone not a toy! I need it to work with the bluetooth in the car or i get fied, I need the camera to come on immediately and not freeze of i lose the pic, I need it to start reasonably quickly and not freeze!!!!!!!!
Thankyou for this marshmallow 6 rom, may I confirm
load zip file to sd card fat32 flash with twrp
end up with stock android6 still with twrp in case a good custom rom comes out.
Advantage of custom roms... note 4 commands similar to a modern fone, i forget stuff like swype up for appstore/left button app store or was it right etc runs apps like bose which no longer run on android6 possibility of volte for poor signal in home
Actually there are a couple of better features in android 6 not carried over, swype down once and see text as well as pic for data wifi etc on shade, and big bright typefaces......
gwm121 said:
yep cant replace due spen ir removable battery superb fone and very nice size
Ive loaded sooooo many custom roms, but cant find one where everything works and is fast, camera bluetooth etc, presntly on acip
if anyone knows a custom rom where everything works on sm910f appreciate a link.
Its a fone not a toy! I need it to work with the bluetooth in the car or i get fied, I need the camera to come on immediately and not freeze of i lose the pic, I need it to start reasonably quickly and not freeze!!!!!!!!
Thankyou for this marshmallow 6 rom, may I confirm
load zip file to sd card fat32 flash with twrp
end up with stock android6 still with twrp in case a good custom rom comes out.
Advantage of custom roms... note 4 commands similar to a modern fone, i forget stuff like swype up for appstore/left button app store or was it right etc runs apps like bose which no longer run on android6 possibility of volte for poor signal in home
Actually there are a couple of better features in android 6 not carried over, swype down once and see text as well as pic for data wifi etc on shade, and big bright typefaces......
Click to expand...
Click to collapse
The GRX TouchWiz Home mod V8 runs excellent with stock roms.
@gwm121: This isnt technically a custom ROM, it's just a deodexed stock ROM. As noted above, nothing has been removed, so everything should work, in terms of functionality it is identical to the odexed stock ROM. What mods you decide to install (root, Xposed, busybox, viper, custom kernel, etc), is up to you, this is just a baseline.
Yes, just flash the zip from TWRP. If it doesnt boot, then read my posts above, you will find the answer.
hi @AnonVendetta, I followed your recommendations and successfully updated my phone, looking foreward now to check battery drain over night...
unfortunately I could not (yet) install xposed, my first attempt ended in a not starting device and I had to restore backup, need to further investigate what to do.
anyway thanks a lot once more for all your efforts!
best
Su
@suse_: The battery life on this should be pretty much the same as the stock odexed ROM. I have ran many odexed/deodexed ROMs over the years, and never noticed any significant difference between them.
If you want Xposed, this is the right version to use:
https://androidfilehost.com/?fid=529152257862685344
Do not use @rovo89's regular Xposed for Marshmallow, it will bootloop/hang on Samsung stock ROMs.
You also need the Xposed Installer app by dvdandroid.
This is what I'm running now, no issues. The deodexed ROM I've provided does *NOT* have Xposed installed.
Here is a safe debloat script. It doesnt remove that much, and everything it deletes can be installed from Play Store/Galaxy Apps if you want them back. The only apps I've added are the ones that I feel are 100% safe to delete and wont affect system stability. Maybe will add more in the future as I test.
EDIT: DEBLOAT SCRIPT REMOVED
AnonVendetta said:
@suse_: The battery life on this should be pretty much the same as the stock odexed ROM. I have ran many odexed/deodexed ROMs over the years, and never noticed any significant difference between them.
If you want Xposed, this is the right version to use:
https://androidfilehost.com/?fid=529152257862685344
Do not use @rovo89's regular Xposed for Marshmallow, it will bootloop/hang on Samsung stock ROMs.
You also need the Xposed Installer app by dvdandroid.
This is what I'm running now, no issues. The deodexed ROM I've provided does *NOT* have Xposed installed.
Click to expand...
Click to collapse
running fine now, thanks a lot!
AnonVendetta said:
Here is a safe debloat script. It doesnt remove that much, and everything it deletes can be installed from Play Store/Galaxy Apps if you want them back. The only apps I've added are the ones that I feel are 100% safe to delete and wont affect system stability. Maybe will add more in the future as I test.
Click to expand...
Click to collapse
stupid question: how to apply this? I installed it via TWRP, it did nothing, I searched appdrawer without success... is it for the commandline?
thanks
@suse_: Yes, it's a script. I forgot to mention that it needs to be flashed from TWRP. I kind of just assumed that people would know how to use it.
Can i use this on but exynos
@Tx Panda: No, you definitely shouldn't flash this on Exynos N910C. Different model/CPU chipset = not compatible. You will at the very least not be able to boot the ROM, and your device may softbrick until you repair flash with Odin.
I borrowed a friend's old desktop, monitor, and keyboard for a few weeks, while my laptop is away for repairs. It's not nearly as powerful as what I have, but it enables me to do work that can only be done on a PC.
Last night I tried to convert the raw system.img to a compressed Brotli format, but the zip didn't flash. So tonight I'm going to try to convert it to compressed ext4. If it works, I'll upload it. I may debloat it as well, along with a list of what is removed.
I really don't see a point in releasing a debloated odexed ROM, since a debloated and deodexed zip accomplishes pretty much the same thing, and is much easier and less aggravating to mod system files. I actually do prefer odexed ROMS, because they seem to run slightly faster overall than deodexed. But the speed difference is minimal, and if you have a good device like the Note 4, the differences are negligable.
A few other things I'd like to note:
1. Do not use Titanium Backup to debloat. It has a tendency to delete a bit more than necessary. I have seen users complain in the past about auto-rotate not working after using TiBu. This is because it deletes, in addition to the APK, odex files as well, as well as library files (name's ending in *.so, you can find them in /system/lib/ and /system/vendor/lib/). Sometimes these library files are used by other Android processes. Use TiBu as a reference to find the location of an app that you want gone, then delete it manually with a root file manager or TWRP. This leaves library files intact. TiBu is great, I use it for backup/restore, but never for debloating.
2. If you want to confirm that the bootloader, ROM version, CSC version, and baseband/CP/modem version are the same as the values I posted, you can use the free version of Phone Info by vndnguyen (search Play Store). However, these values may not match if you didn't at least flash my mini firmware package or the full official package before the deodexed zip. This way you will know your firmware is up to date. And if you switch to a different ROM, then you probably don't need to update it. As an alternative to stock, I find Resurrection Remix Nougat to be very fast and stable. If you wanted to run this or one of the new custom ROMS, you could just flash my mini firmware, then skip this deodexed ROM.
So, I'm currently building a new ROM zip. It is deodexed, same as original zip, but also debloated/de-knoxed. I removed a fair bit more than what my safe debloat script zip deletes. Nothing has been added. This leaves the system partition with about 38% free space (2.2GB used). I've tried to limit the removals to what I feel won't affect system usability/stability. So, here's what's removed:
/system/app/Books (Google Books)
/system/app/Chrome
/system/app/Drive (Google Drive)
/system/app/Dropbox_zero (Dropbox app)
/system/app/Flipboard (news app)
/system/app/FlipboardBriefing (news app)
/system/app/Gmail2
/system/app/Hangouts
/system/app/Maps (Google Maps)
/system/app/Photos (Google Photos)
/system/app/Music2 (Google Play Music)
/system/app/Newsstand (Google Play Newsstand)
/system/app/PlayGames (Google Play Games)
/system/app/PlusOne (Google+)
task manager and associated widget (who uses a task manager these days?)
/system/app/Videos (Google Play Movies/TV)
/system/app/YouTube
lots of apps related to facebook/instagram/whatsapp/evernote
Samsung print service plugin
PEN.UP
Peel Smart Remote (constantly bombards the **** out of your phone with ads like every minute, and when you unlock screen, it had to ****ing go...never seen a more annoying app)
S Note
Galaxy Apps widget (Galaxy apps store not removed, only its' useless widget)
stock email/exhange app (there are way better email apps out there)
Hancom office
stock calculator
S Health (left S Health service intact, you can reinstall S Health if you want, it will work)
stock voice recorder (way better stuff out there)
bubbles/phase beam stock wallpapers
knox:
/system/app/BBCAgent
/system/app/Knox
/system/app/MDMApp
/system/app/RCPComponents
/system/app/SamsungDLPService
/system/app/SecurityLogAgent
/system/app/SecurityProviderSEC
/system/app/SysScope
/system/app/UniversalMDMClient
/system/container
/system/etc/secure_storage/com.sec.knox
/system/preloadedmdm
/system/priv-app/KLMSAgent
/system/priv-app/SPDClient
Knox has got to be the most annoying POS security system Samsung has ever made, it likes to block root stuff. I've always just ripped it out by the balls, never had a loss in functionality because of this.
Most of what i've removed can be reinstalled from Play Store/Galaxy Apps, except Knox. The rest is generally useless junk that I feel most people won't miss. The whole point is to decrease the installed footprint of the system partition, while saving battery/CPU/RAM.
I'll spend the rest of tomorrow testing, then upload. This will very likely be the last released zip, I don't intend on turning this into a full-on custom ROM. In fact, I mainly created this topic to help out @prkfsz with a deodexed ROM that he could easily install MicroG onto. So far he hasn't reported whether it works. But then I realized I'd be doing the community a small service, so I created this topic. With that said, I'm not inclined to do much more free work, I'm a very busy guy most of the time. But I'll still stick around to answer questions.
@AnonVendetta - thank you for all the work. Sorry for not answering before, as i said, i was away and just recently got back. Will not have time to try your ROM untill next week.
I did manage to deodex stock ROM before with that APKtool you suggested, and it was a breeze with your instructions. Even here your instructions are very clear. You should be writing manuals..
Glad to see that there still is an interest for this great device. Personally i am going to run it as long as it works. And then i have a backup or five..
Am gratefull also for this ROM you are working on. That is almost exactly what i was looking for to begin with. I just sortof don't really get why you would remove S Note from the stock rom - that is basically one of the greatest advantages of this phone. I know there are other writing apps out there, i guess Squid is ok but in my opinion no apps come close to original SNote.
Looking forward to trying out your creations!
@prkfsz: I removed S Note and PEN.UP because I very rarely use the pen. Both of these are installable from Play Store/Galaxy Apps, so you're not really losing them. I have always considered them to be bloat. Another reason is that the versions Samsung includes in the ROM are old and not up to date.
You could have deodexed the entire ROM with APKTool, but it would have taken forever compared to the Kitchen. On my powerhouse PC, deodexing takes about 15 mins.

Categories

Resources