[ROM] X96 2/16GB with full root SuperSU and TWRP Recovery - Android Stick & Console AMLogic based Computers

This is my first attempt of creating any Android Rom myself, so don't expect too much.
Changes to the original OTA update which was the base for all:
Removed Superuser in favour for a fully integrated SuperSU by Chainfire.
Changed some root related settings in the kernel to allow a full root instead of factory default.
Keyboard bug fixed for all included keyboards and added a definition for those cheap wireless keyboards with touchpad you often get with the box.
This means pressing ENTER or OK really does just that instead of only producing unwanted characters.
Several versions for download (once I managed to test and upload all), all include a power menu for Kodi to shut down the box without the need for the IR remote.
General instructions:
Download the RAR archive of your choice and unpack the contents to a micro SD formatted in FAT32.
Insert SD into box and press the little button inside the AV port while you power the box up.
Once the logo appears release the button.
TWRP recovery will start and you should do a full backup of your box first!
I do recommend a full wipe after the backup to avoid conflicts after the firmware installation.
Install the ZIP and reboot once done.
Take your time as the initial boot will take quite some time, especially for the versions with more added programs.
Just the recovery image - for those who need it.
X96 stripped down...
In this version I removed all content from the OTA update that might be considered to be a concern in legal terms.
So no Kodi addons, no streaming apps, just a naked system with the standard Google apps and a modified Kodi.
The crappy file browser was replaced by the FX filebrowser.
For those with the need for more than the Media Box Launcher I added the ADW Launcher as well as the XMBC Launcher to have Kodi as the homescreen.
After the boot is finnished I strongly recommend to update the SuperSU binary.
I left this part manual as a confirmation that the first boot and setup really completed.
Only then can SuperSU update the binary in normal mode with success.
After that reboot to clear the memory and all leftovers.
Once you are done with all modifications and app installations you might need do a full backup trough TWRP again to safe you the time if something goes wrong.
Download RAR
After a lot of swearing, flashing, more swearing and flashing I finally managed to create a fully unbranded system that can be installed through TWRP.
If you still know how the original X96 looks with the original firmware you will be surprised
What has changed from the branded firmware:
Bootlogo original S905X.
Google bootanimation - that was the hardest part, allowing for a custom animation...
Media Box Launcher unbranded and with unbranded theme.
Unbranded Kodi completely removed so the rom will comply with all piracy laws and restrictions - more in the added apps section.
OTA updater removed.
All programs from the branded version removed, so no social media, Chrome, Netflix and so on.
Apart from the naked system with Google apps I included:
AdAway
ADW Launcher
XMBC Laucher for Kodi
File browser replaced by FX filemanager
Power Menu added - still requires to root the box! More under added apps.
Added apps and modifications:
Kodi was removed, but the install script for the addon packs is still valid.
The script no longer refers to the system folder but to /sdcard/apps
This means if you decide to install Kodi you can place the tar.gz archive for the addons in the apps folder of the internal SD.
Kodi itself is not included.
The additional apps I thought to be of use will be in the apps folder of the internal SD.
In FX file explorer it is called "Main Storage".
Here you will find:
Chrome
Facebook
Film On (from the branded firmware)
Lucky Patcher
Mobdro (from the branded firmware)
Netflix (from the branded firmware)
Showbox (from the branded firmware)
Skype
SuperSU by Chainfire
Twitter
VLC for Android
Three different Youtube apps to choose from, including a TV version.
How to install SuperSU:
All modifications to the boot image, scripts, libraries and so on are done and included.
This means the system is rooted except for the actual Superuser app.
Install from the apps folder and let the binary update, once done reboot and enjoy.
Ads...
Not all ads in programs or while surfing can be disabled by AdBlock.
For example everything coming from "trusted sources" like Google will still be allowed.
This is the only reason I included Lucky Patcher as it can be of use for some apps to enjoy without ads.
Install and use at your own risk!
Installation of the ROM:
As before wipe all through TWRP then install the ZIP file from extracted RAR archive - so unpack the RAR first to your SD card.
Installation through TWRP does take a few minutes due to the hash verification.
Since all included apps are integrated into the system the first boot is a bit faster compared to the above ROM.
And the additional apps land on the internal SD for everyone to choose or delete if not wanted.
Please allow about 5 minutes after after the launcher selection appeared before you actually start using the apps - some things are still installing in the background!
Once you finnished the network and personal setup of accounts and such bott into TWRP and make a full backup in case you need it.
A factory reset will set you back to the point of the installation of the rom - so no SuperSU and the added apps folder might be gone too.
Known bugs:
Just noticed the WiFi is not available at first activation.
As the chipset is identified during activation you might have to select the network twice until you see WiFi available.
Watch the boot on Youtube
Download from Filefactory
Beta2 with shutdown using F12 on the Wifi Keyboard and some other fixes. - This is just with the most basic apps.
I finally found a neat way to use the WiFi remote to shut down the box the same way the power button on the IR does.
Just press F12 and you will be asked if you want to power down
Will upload the Beta2 with this fix soon.
What's left to do?
Well, now that there is an unbranded and working S905x system out there it means someone could use it to make a ROM that works on all S905X systems out there...
Just needs including WiFi and where existant BT drivers, libraries and calls....
And of course a recovery capable of working on all boxes but that should not be too hard actually
Update: 12/05/2017:
Beta 3 and a Fully Naked Rom is available now.
The Fully Naked Rom has the FX File Explorer and SuperSU included, apart from that it is a naked Android without any Google apps left - great if you want to play around with different GAPPS packages.
The Beta 3 has some minor fixes and most apps moved into the system area instead of the user space.
If you need more apps or launchers then please check the Playstore.
Both have a system partition inflated to 1536mb, which is the same size as the factory OTA update.
On the Fully Naked Rom you can only install apps through the filemanager as no store of any kind is included.
Update 17/07/2017:
A new firmware was released and finally we have a navbar and notification shade "out of the box".
Other changes include the launcher and Kodi, now you find KD Launcher and KD Player...
The OTA can be found here, just unpack to the SD and use as usual, either with the supplied original recovery or your favourite TWRP.
Only downside is we have a locked bootanimation again
A cleaned rom with the usual fixes for keyboard and root can be found here as my Beta 4.
All removed and some additional apps can be found in this archive, just unpack to your SD and install with FX.
Those with just 1GB system memory or wanting to customise all themself can try the Beta 5, which is made small enough to fit on 1GB systems.
Use the above archive to add the programs you need.
Libreelec for SD or USB install.
Unpack the archive to your PC and use Rufus to get the tar.gz image to your SD/USB stick - all existing data will be wiped.
Copy the dtb.img to the SD, overwriting the existing file.
Plug in the box and boot using a toothpick.
Once Libreelec is set up it will work with the SD/USB inserted without you boot the normal Android from the internal memory.
Videoboot
With this version you can use a MP4 video file instead of a bootanimation.
Works with sound of course and should support every MP4 video the normal video player can play.
For your own video simply replace the bootvideo.mp4 in the systems media folder.
Update 04/06/2017: Finally with Open GAPPS!
The X96 showed some real resistance to overcome the chinese limitations and to allow a working installation of updated Google Apps.
As I already spent a lot of days trying to get it to work I only focussed on Open GAPPS but no manual install or the XIAOMI Gapps installer.
With the troubles in the beginning I created a way of installing it all that worked with no errors for me - I suggest to follow it before you try other ways.
This Beta is right now considered to be in an experimental stage until users provided enough feedback to confirm it indeed works fine.
All is based on a naked and slightly modified Beta 5.
The system itself is pretty much naked except for the usual fixes, everything that could make troubles was removed, this includes:
Camera, video and music, wallpapers and so on - install what you want and need through the playstore once all is working.
Main reason for this was to avoid problems with the GAPPS package and to allow the use on 1GB systems as well.
How to install:
Unpack the RAR archive to your favourite SD card or USB stick.
Plug into the box and start with a toothpick - TWRP will show up.
Go to Wipe, Advanced Wipe and wipe Dalvik/Art cache, Data, Internal Storage and Cache.
Go back and install the X96-no-gapps archive and add the opend gapps archive into the line.
Upgrading the neural network takes a few minutes, once the AI is fully operational the GAPPS package will install.
Simply ignore the fact that some of the listed apps will not be available, like Faceunlock - this is due to the removed camera and other things but also because of our harware platform.
After that reboot.
If all goes well and the intial boot goes well you can simply follow the on screen instructions from the wizard.
In case after 10 minutes the Google animation is still going you have to try again but with a different approach (50/50 chance for the first to work).
Start over with a another wipe as above, then install only the X96-no-gapps firmware.
Reboot and do your usual setup of network and screen settings - don't start any apps or mess with SuperSu yet!
Once all is good reboot into the TWRP recovery and install the Open GAPPS package.
Reboot.
Now all should go according to plan.
Troubleshooting and additional infos:
If neither the first nor the second way of installing works for I suspect that your previous ROM was not based on mine or the OTA firmware.
In this case try one of my other beta firmwares if the included firmware itself already failed to boot.
The initial connection to Google can take 4-5 minutes instead of the advertised 2 minutes, so please allow 5 minutes before you panic.
The additional Google apps are not available at this stage and the loading will stay on the screen until you click next - simply add whatever Google app you need from the playstore.
This included Google Music and Google Play TV.
Again: no additional apps of any kind are included, I suggest to use VLC for audio and video or simply whatever you prefer.
Oh, before you ask: Navbar and notification shade are active and working.
Allow some time and check the notification shade for the updates once the system is running, I did not include all updated versions at this stage.
Download the new Beta 6 - Open Gapps version.
Update 15/11/2017:
They finally released another update, got available two days ago but file date is a bit older.
You can check on the Baidu servers yourself if you like Baidu X96 Downloads
Password there is: hp7u
Download as a RAR from Filefactory.
Once I find some time I will check if and what fixes are needed that I can do.

My new x96 arrived yesterday also I found this thread and instructables yesterday. I'm really glad that you take care of this little machine.:good:
Sent from my I9195I using XDA Labs

Guess I was just in the same boat as everyone else with these noname things.
Figured almost everything out I need, ecxept how to change the bootloader/kernel to allow for a custom bootanimation.
Main thing though was to have a working recovery to avoid weird UBS cables and manual flashing.

I wish I was 2 weeks further so I could test your build but I have to look through these things atm. Its interesting that the youtube tv app hasn't changed for a while.
Too many boxes available but I do think x96 is a solid little machine.
There's also opportunity to work with libreelec.
On my s4mini I have a dolby atmos app running modded by ahrion here on xda. Maybe it would be interesting.,wheather it runs on our little devices or not.

I am working on a fully unbranded firmware for the X96 atm.
The problem of converting USB burn images into flashable ZIP was one problem to get the "unbranded" original firmware to at least install another.
They really don't like you messing with their toys in china LOL
If I can't solve the bootanimation problem I will at least upload the otherwise unbranded version with a choice of launchers and updated apps.

Chinese toys. LOL.

Who has made the custom rom from February 16th. Rar @entertainmentbox?

No clue as I did not do it and did not check either.
But the fully unbranded firmware is on the way to upload
Finally custom bootanimations are possible

The pictures I've seen on instructables are awesome. Nice launcher.
Hope you're having fun tuning these Chinese toys.
Sent from my I9195I using XDA Labs

Congrats to your unbranded system. Hope there will be soon more users for testing and enjoying your work

Fixed the shutdown through WiFi remote problem

Is it possible to have look like the normal android tablet/phone?

Hey Downunder35m http://www.tvboxforum.com/archive/index.php?thread-671.html

Just curious is the remote working? I btw changed the keyboard layout so the annoying enter key is fix as well as added the F1 = Power function

Nevermind I fixed my issues with the remote too. Now it is 100% working.

Wasn't aware that the keyboard needs fixing as it works fine here, including powering down the box

I didn't upgrade to the Beta2

Hello!
I have the X96 box mentioned here. Exactly this 2GB model: https://www.aliexpress.com/item/Hot...32779857015.html?spm=2114.13010608.0.0.dF9x4G
The problem is... No matter what i do, i get the error 7 in TWRP. I tried beta1 and beta2, but same error.
I have tried retrying, rebooting, but no effect.
Any suggestions?
What i did was;
-backup files (to internal memory)
-wipe all (byebye backup )
-try to install image from sd-card or usb-stick (both fat32)
-installed TWRP recovery (which caused SD card not to be recognized anymore)

The recovery is specifically for the X96, I had no time to make a generic recovery for all S905X boxes, but seems it should be the next step here.
The error 7 through TWRP is caused by two things (at least during all my tests):
a) The system is totally wiped and the updater script is unable to find the correct hardware info as the build.prop is no longer present.
For this problem and during my tests it just works if you flash again without a wipe.
So right after the error 7 go back and install the firmware again without any reboot or anything else and it should flash successfully.
b) Your system uses different space allocations for the boot, bootloader and recovery partitions.
For this problem the only real cure is to first use the OTA installer for the genuine firmware to get the system working again.
Then only wipe Dalvik, cache and data - the system partition will be overwritten once the update starts but then the installer can find the build prop and if compatible will continue.
If you have a download for the original firmware I will try to incule your system stuff into the next recovery I make.
Otherwise you can always try the hard way if the system is currently toast anyway:
Open the updater script in the META-INFO folder (down in the last subdirectory) and remove the device check for the X96.
That would be the first two lines of the script- everything before th OTA check.
Downside of this approach is that your entire system will be replaced by mine and if your hardware is differernt or the partition sizes won't match then it still won't boot.
Let me know how you go and I will see that by tomorrow evening I have a universal TWRP for all S905X ready.

Related

Z4 RK3368 Android LP5.1/MM6 Octa Core 64bit 2/16gb TV Box

Hey Guys,
I have a couple questions about this android box I purchased that's had me somewhat puzzled.
I have been an avid android user over the past many years. I am familiar with flashing tons of roms to all the phones I have had. Except my s6, it just sucks for roms. Anyways I have purchased the android box in this link (can't post links this new) I can't seem to fine a manufacturer website, I've Google a million things about the box and searched but I can't find anything. even in the instruction book there's no website or anything.
basically I'm looking to figure out how to at least update this box. there's no option in about device. also I don't like how the flash drive on the device is split into nand flash and regular storage. I would like to merge them all into one. I am also looking for custom roms that might enable me to achieve that, however nowhere I look has this box in their forums or anywhere. maybe it's a cloned box? there are other boxes that have the exact same components (or so they say) with custom firmware, however I don't want to chance it and rich bricking this device.
anyone that can offer any help or lead me in the right direction would be greatly appreciated. thank you in advance!
CPU-Rockchip*3368*Octa-Core(1.5GHZ)
GPU-Quad-Core*Mail-T6X*series
Memory-DDRIII*2GB
Flash-EMMC*16GB*(Support*32GB)
WiFi*- 2.4GB+5GBIRInfra*
Remote*control
Bluetooth4.0*
PowerDC*input**
5V/2AAccessoriesgift*box
Power*charger*adapterHDM*cableIR*remote*controlAV*cableUser*ManualI/O1*HDM*2.0Up*to*2160P(2K*4K)2*USB*HOSTHost**USB port1*SPDIFCoaxial*1*TF*CARDSUPPORT*1~32GB1*RJ451000*BaseT1*Power*input5V/2ASoftwareOSAndroid*5.1 LollipopVideoMKV,WMV/VC-1*SP/MP/AP,MPG,MPEG,dat,avi,mov,iso,mp4,rm,H.264,H.265,realVideo*8/9/10,etc.*up*to*2160PAudioMP3,AAC,WMA,RM,FLAC,OGGPicturejpg,JPEG,MJPEG,PNGAdobe*FlashAdobe*Flash*10.1*support*or*aboveSupport*languageChinese*,*English*,Germany*,Japanese,*Korea**etc.**24*languagesDLNASupports Video and Music Playback over networkGoogleTV*RemoteThrough*wi-fi*network*to*realize*control*the*productLANThrough*the*LAN,*can*check*other*devices*to*share*information3D*moiveSupport*3D*movieMotivator*air-mouseSupport*the*body*feeling*game,*such*as*playing*tennis,*paper*planes,*shooting,*etcApplicationsOnlineBrowse*all**video*websitesAppsDownload games and applications from the Google play storeMediumLocal*Media*playback,support for HDD, SD*cardTalk*onlineSupport**SKYPE*video**call*,MSN*,*facebook*,twitter etcOthersSupports Wifi, has router network extender functionsSupports KODI,*Email*and more
Many roms / firmwares being updated for this device:
http://freaktab.com/forum/tv-player...y-x6-acemax-ak838-z4-rk3368-ekb368-custom-rom
http://chinagadgetsreviews.blogspot.ro/2016/01/download-latest-android-lollipop-511.html?m=1
This 1 used by me and referred in other posts. Fast and stable. 16gb unified storage. Kodi and the works.
Make sure you use restore in FactoryTool_v1.39 from archive:
http://download1691.mediafire.com/p...dating+instruction&Drivers&Flashing+Tools.zip
http://4pda.ru/forum/lofiversion/index.php?t702783-100.html
roland deschan said:
Many roms / firmwares being updated for this device:
http://freaktab.com/forum/tv-player...y-x6-acemax-ak838-z4-rk3368-ekb368-custom-rom
http://chinagadgetsreviews.blogspot.ro/2016/01/download-latest-android-lollipop-511.html?m=1
This 1 used by me and referred in other posts. Fast and stable. 16gb unified storage. Kodi and the works.
Make sure you use restore in FactoryTool_v1.39 from archive:
http://download1691.mediafire.com/p...dating+instruction&Drivers&Flashing+Tools.zip
http://4pda.ru/forum/lofiversion/index.php?t702783-100.html
Click to expand...
Click to collapse
I just picked up one of these about a week ago and found instructions to install TWRP and update SuperSU. The box had 'root' out of the box but it was some specialized root based on an old version of SuperSU (1.93 I believe).
I have successfully installed TWRP 2.8.7.0 and updated to SuperSU 2.46.
Since this is just an android tablet essentially, does anyone know if you can flash these ROMs through TWRP?
Not to my knowledge, just use above tool. It will go alive once you are in bootloader with usb otg cable connected to win (of course with driver pack etc. installed). Titanium or else can do that, instead of trying to press reset button while powering on. Of course recovery will go back to default.
roland deschan said:
Not to my knowledge, just use above tool. It will go alive once you are in bootloader with usb otg cable connected to win (of course with driver pack etc. installed). Titanium or else can do that, instead of trying to press reset button while powering on. Of course recovery will go back to default.
Click to expand...
Click to collapse
Are you running liamstears custom ROM or the 12/22 factory firmware?
The split internal storage is something I would like to do without, but I was wondering if it was changed on the 12/22 factory firmware?
12/22 firmware. Fast and stable.
Havent tried liamstears yet. Feedback if you do please.
awesome thanks! thats what I suspected when I was going through the firmwares for these devices. I just wasn't sure if the z4 rk3368 device would work on this one. I've seen a few brands with z4 and as I know with phones.. wrong brand and you're bricked lol. anyways.. I ended up buying a tronsmart vega s95 telos.. but it didn't come rooted. so I rooted it and now I'm getting play services force close and all sorts of bugs and errors.. maybe I'll just keep the z4. it seems to work better.
what link did you follow to get twrp installed?? same thing I'm guessing, punch z4 twrp in google and eventually come upon the right place.
12/22 factory firmware? mines stuck at Nov 10 I think.. it won't let me update using the rk settings app.. which is why I was fed up with it in the first place lol.
12/22 firmware. Unified 16gb App storage. More available with microsd card. Fully functional Kodi with channels, etc. 4k HEVC x265 movies. Youtube 1080p.
Easiest method to update rom is to put extracted update.img from zip file
http://chinagadgetsreviews.blogspot.ro/2016/01/download-latest-android-lollipop-511.html?m=1
on a sdcard / usb and boot. After about a minute into the Android desktop, system will ask for update prompt. Only applicable to system still with default recovery.
If you have some stability issues or with different recovery, you can backup your apps / data with Titanium etc. and then use above Factory tool restore new rom.
These roms usually come with their own recovery, but some modded ones with TWRP/full root, supersu and all. But you dont really need them.
thanks a lot man! I'm downloading right now and will test it on my box tomorrow after work!
I've tried 100 times and it just keeps saying failed to mount /mnt/external_sd (no such device)
I'm using my USB flash drive.
this is becomming a huge pain in the just to update I'm starting to think why this company can make these products and not have any support or anything for it . and that flash tool is in mandarin and I can't even figure out how to work that. I put in the update.img and press go.. but whenever I try to boot to download mode like you mentioned in one of the posts it just turns off the box.. this thing is literally a piece of junk. and so is this tronsmart vega s95.. same thing. it's extremely frustrating. whoever developed this z4 box did a really chappy job on the firmware.. and I do not recommend it to anyone..
If you had gone through the instructions pdf, it clearly shows how to change into English by pressing the World icon. Remember in bootloader mode the tv screen would be black, if you are using the tool. The big red button will turn into green to show readiness.
For automatic update you dont even have to go into recovery as seen in attached image. Easiest.
Hi Roland,
love to see that there are already XDA-members looking at the Z4 TV box. I have just ordered one and hope to get it within a few weeks. Just some dumb questions, hoping you can provide me with some information:
- I see that there are several 'versions' of the Z4: for instance Acemax, but I have ordered the Andoer. Are those just different manufacturers?
- Are there any differences in model/content (installed app's) per manufacturer?
- If my Andoer turned out to have an older firmware than the 22/12, could I still use the Acemax 22/12 firmware you refered to in your link?
- Kodi will be preinstalled, I saw. I do not know what version of Kodi that will be, but can it just be updated to the most recent version in the Google Play Store?
- I do not know what other apps are installed, but is it possible to de-install apps you do not need, or are they part of the firmware and impossible to delete
I know, part of the answers I surely will discover once I got the Z4, but I just can't wait to start experimenting, even it is only in my mind
Thanks in advance!
Jos
hi Roland
I tried that batch tool first which is the one I couldn't change languages in lol. but the other tool with the red button I changed into English. however I did not know that it would remain blank when in download mode. I will have to give it one more go tonight with it. I figured that I loaded it into bootloader and the z4 box light turned red so I thought it was off and didn't load to bootloader.
I also did the USB update and it would just fail on me every time I used it. the update prompt did come up and I pressed install. perhaps I need to check if USB debugging is on. I think it is but it wouldn't hurt to check. but I think I will have to go through the factory tool to update way for sure.
thanks for your help roland, I will write back after I give it another go tonight!
i can't find the 22/12 update ! can anybody share the link direct to firmware ?
@DriftJos
l have got an Andoer too. Most of these brands come from the same hardware factory and thus have the same specs/apps.
Yes you will use the same firmware https://mega.nz/#!JBBXgDgC!VSra8Hc6KR77Pvdw67eDpjeT_ku-TXdYgYaInSAfyvU (direct link @prisim) or several user dev roms. Unified 16gb app storage etc and the works.
You can uninstall bundled Kodi (by Titanium free etc.) by official Kodi Jarvis 16.0 beta 5 & such with pass-through support test builds @ http://forum.kodi.tv/showthread.php?tid=252852
Again you will be able to uninstall useless apps directly or through Titanium.
---------- Post added at 11:47 PM ---------- Previous post was at 11:43 PM ----------
@mikekuel25
Always mention the firmware version you are having and which recovery? The automatic update should work if you still have the factory recovery.
Check the FactoryTool process in attached images.
I'm trying to flash the firmware that I downloaded from that China gadgets site that was mentioned on this thread. I think it's the stock 12/22 for the device. and I have stock recovery.
I extracted the update.exe file and saved it to my USB drive plugged it in and restarted. relieved the update prompt. chose install update and it rebooted into recovery and tried to apply the update but it fails. I'm not ready to give up yet with this device lol. it's just another platform I have to learn. it took me a bit with smartphones to figure it out back in the day.. perhaps it's the same thing now..
and I'm updated to 12/22.. awesome. those pictures really helped me man thanks.
now as for installing twrp and all that. you mentioned that it's not really needed? I'm assuming I can flash any rom given they are in .img format using factory tool. however the benefit of twrp would be an easier interface for creating nandroid backups and clearing cache/factory reset. perhaps I will install it. i might give leamstears rom a try. I will let you know how it is if I do.
thanks again!
so I updated to the new 12/22.. everything works fine except with Google play store.. I keep getting a can't retrieve source error with everything I try to download. I've refreshed and factory reset the firmware 5 times now and kept trying.
so I got fed up with the stock so I tried leamstears rom and it works great.. except sometimes it just becomes completely unresponsive. I'm starting to think there is something wrong with this box. even on stock firmware from the box I've been having issues with unresponsive freezing.
what do you think of the nvidia shield?
mikekuel25 said:
so I updated to the new 12/22.. everything works fine except with Google play store.. I keep getting a can't retrieve source error with everything I try to download. I've refreshed and factory reset the firmware 5 times now and kept trying.
so I got fed up with the stock so I tried leamstears rom and it works great.. except sometimes it just becomes completely unresponsive. I'm starting to think there is something wrong with this box. even on stock firmware from the box I've been having issues with unresponsive freezing.
what do you think of the nvidia shield?
Click to expand...
Click to collapse
The PlayStore error you were seeing is because the 12/22 firmware comes with a *very* old version (5.2.x). The PlayStore will eventually update everything to the latest version by itself but if you don't want to wait, go over to apkmirror.com and download PlayStore 6.0.5 and install it manually. Once you do, it should also update the Play Services to 8.4.x and your should be good to go. I had this issue as well but I had seen it before and knew I needed to update.
So far the 12/22 version has been great, and having the unified internal storage is a huge plus.
If you feel so inclined, knowing that some of the custom builds of Kodi take up a large amount of space... there is this trick that was introduced in Helix:
http://kodi.wiki/view/HOW-TO:Change data location for Android
This will allow you to have only the Kodi app on internal storage (~125 MB) and any data from addons/programs etc. in another location (such as an external SD).
I often
1. Install Kodi on internal storage
2. Zip up the contents of org.xbmc.com directory
3. Copy it to external storage
4. Unzip it in /external_sd/kodi_data
5. Create the xbmc_env.properties file that references my Kodi data location.
6. Delete the contents of /sdcard/Android/data/org.xbmc.com/
Voila! You have freed up internal storage.... You can also persist a Kodi setup this way or run multiple custom installs. If you re-image your media box, you can re-install Kodi and as long as the xbmc_env.properties points to your external_sd with your Kodi data, it will start right up back into your setup... :good:

[HOW-TO] CM 11 and beyond for the 8 GB Nook Tablet, BNTV250a

Updated and revised, 11-29-20
In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with microG on my 16 gb tablet), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.
I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.
I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.
Life without GApps
I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST had GApps installed once upon a time, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.
There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".
These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.
OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. No more. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.
The General Process
If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.
1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
2. First boot, enable root, USB debugging and ADB
EITHER
3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
OR
3. Flash appropriate Xposed for the OS; reboot
4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot
5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.
for CM 11 without GApps but with the PlayStore:
6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.
OR, for ROMs beyond CM 11:
6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given.
It's a lot, but if I could do it many times over you could do it once
In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.
Contacts and Location
Life without GApps doesn't mean you have to give up these services. Just keep in mind that running background services can compromise a system that is already on the edge.
I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.
1. Contacts
There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.
2. Location
To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.
If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.
Email
The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
The ROMs
Updated and revised 2-5-23
Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. You can solve this problem in CM 12 and minimize it in CM 13 by installing Simple Keyboard.
CM 11 is beginning to show expired certificates and SSL issues. You can try replacing or adding new certificates, but it's not easy and you're left with warning artifacts in the status bar. Ditto with CM 12 and CM 13, but they are not nearly as bad--for now. The stock browsers, fortunately, allow you to "ignore" security warnings which makes browsing more pleasant. You may not feel that's a great idea, but the reality is that browsing is the Achilles Heel for all these ROMS, and it's worse the higher you go. The stock browsers may give the best overall performance, whatever their shortcomings.
Because of the SSL issues, I don't recommend CM 11 any longer unless you are not going to do much in the way of internet stuff.
Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing
CM 11 (but with issues as described above)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you could even keep the PlayStore app on it and it would still behave reasonably. It's even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.
The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshot how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.
CM 12.1 (potential WiFi issue as described below)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Edit 9-30-22: I recently booted this up to find that it would no longer connect to my fairly new ATT router. Puzzled, I took the tablet to my local library and had no difficulty connecting there (open network, though). Next I started restoring backups of each of the other ROMs in this list and each one had no trouble with WiFi at home. I installed a fresh copy of the CM 12.1 ROM. It also refused to connect to the router. I scrounged around the web and found two more versions of CM 12.1. Neither would connect to my router. So...I'm not sure if there is some additional security ATT has built into their WPA2 authentication or what, but I mention this just to alert you that this might be a problem. I was even able to connect to a mobile hotspot generated by my Windows 10 machine (password needed). Why this new(?) problem for the 12.1 ROM only, I have no idea.
Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.
The stock browser seems like the best bet (I tried many), though it can be slow.
For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).
CM 13
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Never having tried this ROM on my 16 GB tablet, I was actually pleasantly surprised by its behavior on the BNTV250a. There's a funny WiFi thing where if you leave WiFi on when you shut down and then boot up again, it will not automatically connect (unless the lockscreen has come on, which is pretty fast after booting, so no biggie). Otherwise it's pretty much like CM 12 although maybe a little more stable--if you don't overdo it. The Sound Recorder app is somehow broken on the CM 13 ROM. If this is something you'd like, you can replace the broken version in /system/app/SoundRecorder with the one attached below. Make sure the permissions are rw-r-r and reboot.
Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.
This is the ROM I've settled on for my BNTV250a (screenshot of home screen below)
AOSP 6.01 "Marshmallow"
Box
notredame.app.box.com
(you want aosp_acclaim-ota-MOB30Z.160820.zip)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.
The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.
The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.
AOSP 7.0
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed
This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless. I really wanted to say the same for the BNTV250a, but I can't.
Enabling root for the ROM is achieved with Magisk.
The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0 and Magisk) and install the installer app along with the FakeGapps app as described in the previous post.
The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.
Lineage 14.1
Box
notredame.app.box.com
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Edit 2-5-23: Well...no, it does not have the classic shut-down bug (tablet reboots right after it "shuts down"). Instead, it often shuts down just fine, but occasionally locks up during shut down and has to be forced off with the power button.
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.
The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.
Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.
The stock browser is complete rubbish. It looks to be Gello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")
The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. Not a viable choice for the BNTV250a.
For a lark I tried it on the 16 GB model and it's actually not bad, but then I saw that embedded browser videos (like YouTube, for example) were funky colors, so... It may be that later versions corrected this, but those likely have the shut-down bug. In any event, a terrible choice for the 8 GB model.
Took a bit of trial and error to get the perfect version of playstore to not give an error, but I got it working. Thank you a lot for this write-up!
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
denmalley said:
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
Click to expand...
Click to collapse
While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.
So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
denmalley said:
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
Click to expand...
Click to collapse
I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.
Those are my only ideas at present. I hope one of them does the trick!
Ah yes path variable did the trick! On to the next steps, I'll keep you posted!
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
denmalley said:
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
Click to expand...
Click to collapse
Did you
1. Check microG settings to be sure everything is OK?
2. Sign in to your Google account from the microG settings (add account)?
3. Then try the PlayStore (check permissions on Phonesky folder and app)
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
denmalley said:
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
Click to expand...
Click to collapse
Yes, the PlayStore icon should appear--admittedly a very old and funky one with this old version.
The Playstore automatically updates. I wish it did not, but there is no way to stop it. But to have that happen you have to access the Playstore at least once, maybe even download an app, and leave wifi on awhile.
On my main microG settings screen I show Google device registration ON. On the self-check screen, everything is checked except the last box. I have the location stuff installed.
So if PlayStore is unchecked, something is not right. Perhaps the app got corrupted when I uploaded it. I am shut down right now but can reup tomorrow. Or you can just get another app from Apkpure or similar. I used to use something around 8.02 to get started.
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
denmalley said:
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
Click to expand...
Click to collapse
Phonesky=PlayStore, just renamed--microG expects to see Phonesky
Something is not right with the app. I have to run, but here is a link to v. 8.02 which I have used in the past:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-8-0-23-release/
Rename to Phonesky before using. It will be a little more cranky but it will work to get you going. I hope.
Edit: or, if you prefer, go to OpenGapps and download a KitKat pico GApps. Extract from that zip the Phonesky app and use it.
Edit, Edit: yeah, I tried reupping a copy of the Phonesky app but when I downloaded it the file size did not match. So I changed the first post and inserted a link to a copy on my mediafire account. That downloads with the right file size.
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
edit
The only other thing I haven't yet tried is redownloading everything and maybe even using a different PC. Ah heck who am I kidding, like I've got anything better to do. I'll keep cracking at it.
denmalley said:
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
Click to expand...
Click to collapse
I'm really baffled by this behavior. When you add a Google account via microG nothing changes on the microG settings page, but the account should show up in the CM11 settings under "accounts".
When you prepare the system for flashing, do you do an Advanced Wipe? I'm a little AR about this sort of thing, especially as my devices have been flashed with different OS's many times. I start with an Advanced Wipe, clearing out everything except, of course, the microSD card, and then I follow that by a regular wipe. Then I start flashing.
If you are still having trouble, let me know and I'll wipe my current system (I have a backup) and start again from scratch, downloading copies of the files I have posted to see if I can duplicate what is happening to you. Maybe Google has changed something in the time since I did my newest configuration and the microG folks have not caught up with it yet. This appears to be true for Contacts because I cannot get them to sync up or even see my Google contacts. This was not the case in the past. There is chatter about it on the microG site, but none of the "solutions" go anything beyond what I have already related and some of the conclusions are like "and it just started working..."
I did not do the advanced wipe, so let me try that. I'm also going to redownload everything and give it another go. No need to wipe your device just yet - you've already done WAY more than I expected to help! I will do this over the next few days and keep you posted.
Well I tried six different ways, full wipe, change the "group" set for the group permissions to "root" (it had been set to sdcard), redownloaded every last bit of software used in this process, used a different computer, etc etc etc. Nothing is working. Still no play store. Everything else seems to be fine except that.
So anyway, I finally just did a full wipe, flashed the CM11 unofficial that you provided in second post, and grabbed a kk gapps package and flashed that. Switched from trebuchet to nova and I've got a tablet I can live with! Working much better then the cm10 rom I had on there before (like swipe to unlock screen, wait 5 seconds....touch app drawer, wait 5-10 seconds....touch an app, wait 30 seconds....slooooooow).
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
denmalley said:
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
Click to expand...
Click to collapse
I'm glad you reached a point where you feel good about the outcome but sorry that you had to waste so much time.
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
nmyshkin said:
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
Click to expand...
Click to collapse
Well.....I'm not sure how the error crept in, but it looks like the creation of the Phonesky folder was the issue. This is needed for ROMs beyond CM11, but there are no folders in /system/app or /system/priv-app for CM11. Thus for CM11 only, the files like Phonesky.apk are simply dropped into /system/priv-app and the permissions set as described, Then everything works as it should.
I've corrected the instructions. My apologies.

[ROM][AL00][4/1/19] Mate 20 X GlobAL00ized 1.6 (fw 200) [Debloated][Mostly Deodexed]

Welcome to the Mate 20 X GlobAL00ized project. This ROM's goal is to transform your Chinese AL00 into a global device. We accomplish this by magic. What does this do? Well, it enables google location services, google pay, and many other global huawei device features. This was a joint venture between myself, @cflynt, and @antiochasylum. It's about as close to a rebrand as you'll get without an actual "rebrand."
Join our Telegram group:
Everest Dev
Requirements:
TWRP
Know how to boot into TWRP
Recommendations:
Be decrypted
A factory reset for first time users
Magisk installed to recovery_ramdisk
A backup of your system, preload, product, version, and vendor partitions. Not necessary as erecovery can restore your device, but I thought I'd mention it anyway.
Changelog in the second post
Update instructions in third post
Installation steps:
Step 1:
Copy ROM zip to your device.
Step 2:
Boot into TWRP
Step 3:
Factory reset from TWRP if this is your first time flashing.
Step 4:
Install ROM. This will take quite a while (3-5 minutes) to flash, as the system image is over 4GB in size.
Step 5:
Use the "reboot" and "recovery" option in TWRP.
Step 6:
Rejoice!
Credits: @cflynt and @antiochasylum for providing L29 firmware.
Donators and contributors:
@rawaf - support and testing
@VeNuMuS - support and testing
@turilo - support
@ajsmsg78 - ideas and help
@Fatouraee - support and firmware links
@OldDroid - for the amazing EMUI Flasher
Screenshots: ROM screens
Download: Mate 20 X GlobAL00ized ROM v1.6
XDA:DevDB Information
GlobAL00ized ROM, ROM for the Huawei Mate 20 X
Contributors
freeza, cflynt, antiochasylum
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Version Information
Status: Stable
Current Stable Version: 1.6
Stable Release Date: 2019-04-01
Created 2019-01-21
Last Updated 2019-04-01
Changelog and other information
Changelog
1.6 (200): This REQUIRES you to be on software version .200 first. See third post for instructions.
4/1/2019
-updated to firmware .200 with March 2019 security patch.
1.5 (198): This REQUIRES you to be on software version .198 first. See third post for instructions.
3/23/2019
-updated to firmware .198 with February 2019 security patch.
1.4 (195): This REQUIRES you to be on software version .195 first. See third post for instructions.
2/5/2019
-really removed stock incallui
-fixed google dialer incallui (spam/blocking/call identify works!)
-updated to firmware .195
Beta 3
1/30/2019
-removed stock incallui
-removed smartmmsplugin
-removed numberidentity
-removed hwrcsservice
-removed hiaction
-removed fastappengine
-removed hwvoipservice
-added forced volte (thanks @Ashish in the telegram group)
-fixed some china xmls
Beta 2: This REQUIRES you to be on software version .185 first. See third post for instructions.
1/24/2019
-Updated ROM to software .185 with January 2019 security patch.
-Updated Phone Manager to match L29 .184 firmware
-Deodexed a few more L29 apks
-Added Google Photos
-Added Huawei Music
-Added Huawei Video
Notes to be aware of
Google Pay does not, nor has ever liked ROOT. Nor do pretty much any pay type apps. So make sure you use Magisk Manager, and click on the 3 lines in the top left corner and select Magisk Hide and scroll down to Google Pay and check that to make sure it is hidden from Root. Otherwise you will run into issue. Someone said they also had to hide Google Services Framework. So you might want to hide that as well. In my tests of using Google Pay, I didn't have to do that, but it isn't gonna hurt anything.
Smart Lock might need you to re-train your voice in order to work on the phone if it recognized you had already trained it from previous devices. My guess is to make sure it is more secure from the phone. So you might go into Google Assistant and do that before setting up Smart Lock as your unlock ability if that is your chosen path.
Updating to the latest version of EMUI Software
This is a tad extensive, but mainly just lots of info to try and answer any questions anyone might have. I promise it is much easier than all the text shows. Just read through it and you will see there really isn't that much to do.
I do recommend, just as a precaution, that you do a full nandroid backup in TWRP before doing any type of update. This just covers bases. If you go into TWRP and select BACKUP and make sure all Partitions are selected and then Swipe to Backup. It will store a full backup of all partitions on your Internal Storage. You can then transfer this over to your PC for safe keeping.
Step 1: Go ahead and download and transfer ALL of the following to your Internal Storage. All files are linked at the bottom of this post except the latest ROM which is in the first post. The latest ROM, the latest Update Full Base Zip, the EMUI Flasher, the Patched TWRP Image and lastly the Current Magisk Recovery Ramdisk Image. You will need all these files here in a bit. I recommend you save the TWRP image as twrp.img for easier use shortly.
Step 2: Next, we want to run the EMUI Flasher from the phone. Make sure you are plugged into Power or the PC via USB. Run the app, it SHOULD prompt you, if this is the first time you have ran the app, to grant ROOT permissions, as well as to download some Asset files. Just select Confirm. IF, it did not. go ahead and exit the app and close it out. Run Magisk first and then hit HOME and run the app again so that it prompts. Next, tap the Select button at the top right for #1 Firmware File, and Allow the permissions to allow it access your file system. Find the update_full_base.zip file you downloaded and transferred to the phone earlier. Tap to select it. You don't need to worry about #2 right now, if they push another patch later, I might update this to observe that. But currently we only have the one push. Now tap the RED Circle at the bottom right with the Down Arrow in it. This will reboot into Recovery and flash the update. NOTE: As soon as it is done Flashing, it will reboot, you will want to be ready to hold the Volume DOWN key to boot into Bootloader Mode.
Step 3: Now that we are in the Bootloader. We want to Flash the TWRP Image over to the Recovery Ramdisk. So type the following:
Code:
fastboot flash recovery_ramdisk
twrp.img
You should get an output similar to the following:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24956 KB)...
OKAY [ 0.627s]
writing 'recovery_ramdisk'...
OKAY [ 0.175s]
finished. total time: 0.805s
Type:
Code:
fastboot reboot
To reboot the phone, then immediately unplug the USB Cable from the Phone. We want to immediately hold VOLUME UP to boot into TWRP Recovery. Until it says NOW BOOTING.
Step 4: Next we want to flash the current ROM you downloaded earlier. Tap on INSTALL at the top Left. Browse to where you placed the current ROM and tap on it. Swipe to confirm Flash.
Step 5: Now that the ROM has flashed successfully hopefully, we want to go ahead and flash the Magisk Recovery Ramdisk back on the Recovery Ramdisk. Hit BACK to get back to the main menu, tap on INSTALL at the top left, then INSTALL IMAGE at the bottom right. Locate your recovery_ramdiskMagiskAL00.img you downloaded and transferred to your Internal Storage earlier. Tap on it. Now find and tap on Recovery Ramdisk to select it. Lastly, Swipe to confirm Flash.
Step 6: Lastly, we want to put TWRP back on the eRecovery Ramdisk since most likely the Software update overwrote it. Hit BACK till you get back to the main menu, tap on INSTALL at the top left, then INSTALL IMAGE at the bottom right. Locate your twrp.img you downloaded and transferred to your Internal Storage earlier. Tap on it. Now find and tap on eRecovery Ramdisk to select it. Lastly, Swipe to confirm Flash.
That is it, hit BACK to get back to the main menu. Make sure to UNPLUG from any USB Device. Select REBOOT and then REBOOT RECOVERY to boot your system with the Magisk Recovery Ramdisk. It will probably take a little longer the first boot due to the software update and converting some files.
Enjoy the latest software!
Updating to the latest version of EMUI Software w/out using EMUI Flasher
This is for those that seem to have trouble using the EMUI Flasher for whatever reason. It has worked for us as well as many others that have tested it over and over, so not quite sure what the trouble is, but regardless, here is the older style instructions for those that do have difficulties with that flasher. Hopefully it helps ya get things updated that way.
I do recommend, just as a precaution, that you do a full nandroid backup in TWRP before doing any type of update. This just covers bases. If you go into TWRP and select BACKUP and make sure all Partitions are selected and then Swipe to Backup. It will store a full backup of all partitions on your Internal Storage. You can then transfer this over to your PC for safe keeping.
Step 1: Download the latest ROM from the 1st post, the Stock eReocvery, TWRP Image and the Magisk Recovery Ramdisk Image all from the bottom of this post if you don't already have them and transfer them to your Internal Storage. You will also need a copy of the TWRP image wherever you keep your ADB directory for fastboot later.
Step 2: We now want to boot into TWRP to flash the Stock eRecovery. Plug your phone into a USB Device, either PC or Power and Reboot holding the VOLUME UP. KEEP holding even when it prompts for the eRecovery Menu, release when it says it is NOW BOOTING at the bottom.
Once in TWRP, tap on INSTALL at the top left and then INSTALL IMAGE at the bottom right. Locate your Stock eRecovery Image you downloaded and transferred to your Internal Storage earlier and select it. Next, select the eRecovery Ramdisk Partition to restore to. Lastly Swipe to confirm Flash.
Step 3: Now we want to Reboot into the Stock eRecovery, so with your Phone plugged into a USB Device, back out and select REBOOT and SYSTEM, hold VOLUME UP. KEEP holding even when it prompts for the eRecovery Menu, release when it says it is NOW BOOTING at the bottom.
Once in eRecovery. select to Download latest version. It might prompt you to enter your Wifi Credentials. It will possibly prompt about it wiping all your data. From our experience, this has never happened. But good thing you did a backup earlier right!? Once it is done downloading and installing the latest update. It will go through a verification. You obviously will have the time, but just be prepared for when it prompts that it will be rebooting. You will want to then hold the VOLUME DOWN button so that we boot into BOOTLOADER MODE. We need to catch it before the system boots up and re-encrypts the data partition. So just be mindful of the percentage it is at. Then you will have like 10 seconds when it says it will be rebooting. Right when it starts to reboot, hold that VOLUME DOWN until you are in BOOTLOADER MODE.
Step 4: Once in BOOTLOADER MODE, change to your ADB Directory unless you have it set in your path. Now we will want to flash the Magisk Recovery Ramdisk back as well as TWRP to the eRecovery Ramdisk. First, we need to get back into TWRP so type the following:
Code:
fastboot flash recovery_ramdisk twrp.img
This will flash TWRP to the Recovery Ramdisk temporarily. We now need to boot into TWRP so that we can put everything where it belongs. We aren't able to use fastboot to write to eRecovery. So type:
Code:
fastboot reboot
IMMEDIATELY unplug your USB Device and then hold VOLUME UP until it says NOW BOOTING at the bottom. Once in TWRP, tap on INSTALL at the top left and then INSTALL IMAGE at the bottom right. Locate your Magisk Recovery Ramdisk Image you transferred to your Internal Storage and select it. Next, select the Recovery Ramdisk Partition. Lastly, Swipe to confirm Flash. Now hit back, all the way to the menu to be safe. Once again, select INSTALL at the top left and then INSTALL IMAGE at the bottom right. Locate your TWRP Image and select it. Next, select the eRecovery Ramdisk Partition this time. Lastly, Swipe to confirm Flash.
Step 5: Now that Recoveries are where they belong once again, and you are on the current release of software, we need to flash the current ROM you downloaded and transferred to the Internal Storage earlier. Back out to the main menu. Select INSTALL at the top left, locate the ROM you downloaded and select it. Swipe to confirm Flash.
Step 6: If all flashed ok and everything is good, make sure you are unplugged from any USB Device, back out to the main menu and select REBOOT and then REBOOT RECOVERY to boot your device. All should come up as it should.
Huawei Dialer
For those that aren't fans of the Google Dialer, I am not sure why, but whatever floats your boat. Google Dialer has Video, has Spam and Blocking just like the Huawei Dialer does, only thing missing is the Call Recorder option which can be added by 3rd party, and I'd much rather have video capability. Regardless, it was requested. We have included the flash at the bottom. You can flash it in TWRP. Once flashed, you will need to go into SETTINGS and then into APPS and then into DEFAULT APPS, and set your PHONE APP to reflect the proper dialer you wish. The flash actually removes the Google Dialer from the system, but it won't remove any Google updates that have been done, so most likely it will still show up in the system. So just make those changes and it will now be your default dialer for incoming/outgoing. Enjoy. Note: All ROMS will ALWAYS come with the Google Dialer. You will have to flash this ZIP anytime we do a ROM update if you wish to use the Huawei Dialer. Keep that in mind moving forward.
Google Dialer
For those that flashed the Huawei Dialer and wish to return back to the Google Dialer can download the Zip at the bottom of this post. You will flash it the same way as you did the Huawei zip in TWRP. This will remove the Huawei Dialer from your phone and put the Google Dialer back in the system. It should become your default, but just in case any updates happened that downloaded anything out of our control you can double check your default apps. Go into SETTINGS and then into APPS and then into DEFAULT APPS, and set your PHONE APP to reflect the proper dialer, in case 2 show up there. Note: You will only need to flash this if you are wanting to return to the Google Dialer from flashing the Huawei Dialer. All ROMS come with the Google Dialer and always will. So this is the only time you will have to mess with it.
Downloads
TWRP-3.2.1-0 for Mate 20X
Magisk Recovery Ramdisk
EMUI Flasher v1.0 Courtesy of @OldDroid from the Mate 20 Pro Forum. https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Stock eRecovery Ramdisk
Stock Recovery Ramdisk
Huawei Dialer
Google Dialer
Best rom to best phone from best dev freeza
Running great bro. Good work
Great job guys!!!
Now I really need to get an unlock code.
Sweeeeeeettt! Nicely done fellas. Just need to get unlock code now.
Can people who have installed this confirm that notifications are working properly or do we need to go through the multiple steps to disable smart notifications, lock the app, etc, etc...
I can confirm even with the modified ROM, googlepay does not work for me. My american express won't confirm. I'm in Canada for reference and the same card works on my L29 phone. Also, using the A&W (fast food franchise) app won't load coupons because it thinks I'm not in the area even though I granted the app permission to locations.
n1tro said:
Can people who have installed this confirm that notifications are working properly or do we need to go through the multiple steps to disable smart notifications, lock the app, etc, etc...
Click to expand...
Click to collapse
I haven't disabled anything and get notifications all day long. But it is possible you will still have to do the usual power management notifications, we can't do that for you. That is gonna be an app per app thing. But all my typical notifications like messaging, hangouts, etc have all come through without modification.
I can confirm even with the modified ROM, googlepay does not work for me. My american express won't confirm. I'm in Canada for reference and the same card works on my L29 phone. Also, using the A&W (fast food franchise) app won't load coupons because it thinks I'm not in the area even though I granted the app permission to locations.
Click to expand...
Click to collapse
I don't have an American Express, nor do I live in Canada, but it added and confirmed my Visa card without issue, and I even sent a test transaction with no issue. I don't personally use Google Pay, so I haven't taken it to a store to make a purchase, but I can only assume that if it sends transactions after the confirmation, that it works fine. Did you actually use Magisk Hide and hide the app? It is an app that won't like root.
does this need the unlocked bootloader?
Kurocham said:
does this need the unlocked bootloader?
Click to expand...
Click to collapse
Yes it does
cflynt said:
I haven't disabled anything and get notifications all day long. But it is possible you will still have to do the usual power management notifications, we can't do that for you. That is gonna be an app per app thing. But all my typical notifications like messaging, hangouts, etc have all come through without modification.
I don't have an American Express, nor do I live in Canada, but it added and confirmed my Visa card without issue, and I even sent a test transaction with no issue. I don't personally use Google Pay, so I haven't taken it to a store to make a purchase, but I can only assume that if it sends transactions after the confirmation, that it works fine. Did you actually use Magisk Hide and hide the app? It is an app that won't like root.
Click to expand...
Click to collapse
I did some more tinkering and got Google pay working. Before doing anything, I enabled magisk hide on Google services framework before trying to enable the cards. Got confirmation this time.
Still can't get A&W app to find me. It thinks I'm on the west coast for some reason.
where I can buy the unlock bootloader, where is the cheapest web to buy it
---------- Post added at 06:27 AM ---------- Previous post was at 06:15 AM ----------
https://ministryofsolutions.com/huawei-bootloader-unlock-service-all-new-models-new-firmwares
I tried to buy unlock code here but the sellers told me "New models not possible to unlock". No unlock code for my mate 20x evr-al00. I need help please
Working good here... Thank you!
where I can buy a unlock code please? I have EVR-AL00
Kurocham said:
where I can buy a unlock code please? I have EVR-AL00
Click to expand...
Click to collapse
There are many threads on the general section of this forum as to where to purchase a code. This is a ROM thread not an unlocking thread. :good:
First, thanks for getting this out!!! Everything is working so far for me. Anyway to remove the Chinese below the time/date on the lock screen?
ben63vw said:
First, thanks for getting this out!!! Everything is working so far for me. Anyway to remove the Chinese below the time/date on the lock screen?
Click to expand...
Click to collapse
The Chinese text on the lock screen is due to the preloaded themes magazine unlock comes with. In the new ROM magazine unlock isn't present so no Chinese text should appear. Did you format data in TWRP when installing or just wiped system?
VeNuMuS said:
The Chinese text on the lock screen is due to the preloaded themes magazine unlock comes with. In the new ROM magazine unlock isn't present so no Chinese text should appear. Did you format data in TWRP when installing or just wiped system?
Click to expand...
Click to collapse
I definitely did a format... I had to type "yes" to perform the format. Is there a way to remove magazine unlock without formatting and installing the rom again?
Note app
Thanks for this. It is smooth. However, I bought the M-Pen and now the note app that comes up at the home screen is now gone. Can someone help with the apk? Thanks.

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.

[Lemon Drop] A [Debloated] & [DeGooged] [Stock] [Oreo] [Rom] for the H910 & most Lgv20 phones.

STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use Audo_Debloat and or FAQ & Troubleshooting guide at your own risk there is no warranty or guarantee.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the Lemon Drop Rom, for the Lgv20...
Auto_Debloat is a twrp flashable file I created, it's very unique in that you flash in twrp after you have already flashed Stock Oreo v8.0, kernel, magisk ect. This will transform Stock Oreo 8.0 into The Lemon Drop Rom. Auto_Debloat mods the build.prop file and updates the GPU drivers and tweaks. I love music, Lemon Drop was designed with music in mind, by forcing true 24 bit audio, at 44.1 kHz and System wide Quad DAC support. You will need to install apps like the alarm clock and weather. Most all LG apps are still there and some Google apps, like Chrome and the Play Store. You can always DeGoogle, at any time or keep Google Play Services installed. The idea is to customize Lemon Drop, to fit your needs.
Please read Questions, before rooting or flashing Auto_Debloat.
What works?
-Google Play Store
-Google Assistant
-Audio (input all three mics, & output)
-Display (with image retention fix & tweaked KCAL settings for optimal color)
-Bluetooth
-FM works on (H910) mod for VS995 & US996 link
-IR Remote
-LGMusic Player (for H910)
-Second screen
-usb
-Media playback
-fast charging
-Hardware buttons
-Camera (Camera improvement tweaks)
-GPS (USA gps fix by default & other countries optional) link
-Fingerprint
-DAC (24_BIT_Deep_Buffers_Enabler v4.2 force true 24 bit audio at 44.1 kHz) & (System wide Quad DAC support. V6.2)
-Radio (VoLTE & Wifi Calling only tested on H910 with AT&T)
-Wifi (dual channel bonding on 2.4GHz + speed tweaks)
-Thermal Throttling (70c default max temp) link
-Video output via hdmi
-DRM Widevine L1
What does not work?
-Miracast (removed due to security concerns)
My other xda pages
Best Apps, Games, Emulators for android & mods/tweaks for the Lgv20
Twrp Mods not included in Auto_Debloat
This mod has to be flashed, after you have already setup your phone.
Speed up WIFI / LTE By enabling CRDA on Android aka wifi country code (root only)
Magisk Module extra add-on Mods are not included in Auto_Debloat.
Disable find my device administrator account. Only if Google is installed.
Disable lock screen service administrator account. Only if Google is installed.
Force Doze Mode Force your phone into doze mode to save battery. (root only) With Google or without, like LineageOS or a DeGoogled phone.
Thermal Engine mod for Lgv20 Stock Oreo/Nougat (root only) Lemon Drop default is 70c you can flash 80c or 60c if you want.
Change Log Notes:
New v9.82 & v8.82
Increased the Zram size to 2.5 gigabytes. Added some extra Zram tweaks that may speed up the phone.
New v9.81 & v8.81
Auto_Debloat v9.81 updated to latest working version of Magisk v24.3. Also on v8.81 updated Auto_Debloat script.
New v9.80 & v8.80
Updated Auto_Debloat script also on v8.80 I removed the DT Ignite on the H990DS roms.
New v9.79 & V8.79
Updated Auto_Debloat script also on v8.79 I removed DT Ignite (aka) Mobile Services Manager on the VS995 Roms and US996 Roms, it's a bloatware app that installs other apps on your phone. link
New v9.78 & v8.78
Updated to 24_BIT_Deep_Buffers_Enabler_v4.2_Lgv20_Oreo
new sound improvement tweaks.
New v9.77 & v8.77
Fixed the hide boot warning message on the H910. Also update the Auto_Debloat script.
New v9.76 & v8.76
Updated the Auto_Debloat script, made it a little faster when flashing.
New v9.75 & v8.75
Hide boot warning message on the H910 Auto_Debloat v9.75. Cleaned up the Auto_Debloat script a little bit.
New v9.74 & v8.74
Fixed the internet speed Mod tweak in WCNSS_qcom_cfg.ini
Added gEnablePhyAgcListenMode=7
On this version I found the fix for the slow wifi and LTE. Dual bonding is enabled on the 2.4GHz band.
New v9.73 & v8.73
Added a new internet speed fix in the WCNSS_qcom_cfg.ini
This tweak will speed up LTE and wifi.
New v9.72 & v8.72
Only fixed some typo's,
New v9.71 & v8.71
Fixed Enable power save offload on wifi. Will speed up wifi and help save power.
New v9.70 & v8.70
Enable power save offload on wifi. Save battery when using wifi.
New v9.69 & v8.69
Enabled WMM on wifi should speed up playback of video and multimedia data.
New v9.68 & v8.68
Changed the wifi scanning period and enabled wifi dual bonding on the 2.4GHz band. This should speed up the internet on 2.4GHz band, and maybe save a little battery because I slowed the wifi scanning period down.
New v9.67 and v8.67
Updated to speed mod v5.28 change GPU governor to msm-adreno-tz with default 133mhz
New v9.66 & 8.66
Fixed Auto_Debloat script to work with the GPU Drivers.
New v9.65 & 8.65
Found an issue with the GPU drivers. Fixed GPU Drivers.
New v9.64 & v8.64
Updated to Speed Mod v5.27 Removed the GPU tweaks and adjusted the idle timer that should speed up the GPU also with out the battery drain I was experiencing.
New v9.63 & v8.63
Fixed zram settings.
New v9.62 & v8.62
Adjusted the GPU tweaks so they do not use too much power but still provide a performance boost.
New v9.61 & v8.61
Updated to Speed Mod v5.25 Added some GPU Tweaks
New v9.60 & v8.60
Updated to Speed Mod v5.24 Fixed typo in last speed mod.
New v9.59 & v8.59
Updated to Speed Mod v5.23 Changed the rq_affinity to number 2. That should speed up the eMMC drive and sdcard.
New v9.58 & v8.58
Fixed delete only log files.
New v9.57 & v8.57
Removed all the Auto_Debloat.log's on /system and moved to internal storage. I was just thinking that it may be getting a little bit messy on the /system with log files.
Also on the H910, updated to the latest version of twrp. twrp-3.7.0_9-0-h910
New v9.56 & v8.56
Updated to Speed Mod v5.22 All new interactive governor settings.
New v9.55 & v8.55
Updated to Speed Mod v5.21 and tweaked the interactive governor settings.
New v9.54 & v8.54
Updated to Speed Mod v5.20. Changed governor to interactive, increased speed & increased battery life.
New v9.53 & v8.53
Updated to Speed Mod v5.19 Fixed some things with the TCP Speed Mod
New v9.52 & v8.52
Updated to Speed Mod v5.18 added a TCP Speed tweak to speed up internet.
New v9.51 & v8.51
Updated to Speed mod v5.17 Changed the TCP Algorithm to cubic. May speed up internet and make it more stable. I have an issue with Wifi Calling where the voice will cut in and out sometimes, this should fix that issue.
New v9.50 & v8.50
Changed the version number from 8.0.0_Lemon_Drop back to the default. I don't think it will hurt anything but still it was bugging me.
New v9.49 & v8.49
Updated to speed mod v5.16 changed GPU Governor to Simple_Ondemand and change the power level to save battery power.
New v9.48 & v8.48
Fixed Ram Optimization Tweaks
New v9.47 & v8.47
Updated the United States GPS fix. All other locations you can update manually link
New v9.46 & v8.46
Just some minor fixes with the script
New 9.45 & v8.45
Fixed another error in the build.prop file with Enable System wide Quad DAC support. This may improve sound quality.
New v9.44 & v8.44
Fixed an error in the build.prop file with the Enable System wide Quad DAC Support.
New v9.43 & v8.43
Added new build.prop GPU tweaks. This will improve the font on the Lgv20.
ro.hwui.use_gpu_pixel_buffers=true
ro.hwui.text_gamma_correction=lookup
ro.hwui.text_gamma=1.4
ro.hwui.text_gamma.black_threshold=64
ro.hwui.text_gamma.white_threshold=192
ro.hwui.disable_vsync=false
ro.hwui.render_dirty_regions=false
video.accelerate.hw=1
debug.sf.hw=1
debug.performance.tuning=1
debug.egl.hw=1
debug.composition.type=gpu
sys.use_fifo_ui=1
ro.HOME_APP_ADJ=1
New v9.42 & v8.42
Added some more GPU build.prop tweaks
debug.performance.tuning=1
debug.egl.hw=1
debug.composition.type=gpu
ro.HOME_APP_ADJ=1
New v9.41 & v8.41
Fixed an issue in the build.prop file with the GPU tweaks.
New v9.40 & v8.40
Added some GPU build.prop tweaks
hwui.disable_vsync=true
hwui.render_dirty_regions=false
debug.sf.hw=1
video.accelerate.hw=1
New v9.39 & v8.39
Updated to speed mod v5.15 trying to save a little bit of battery life without sacrificing speed. Also fixed some apps crashing.
New v9.38 & v8.38
Added some Zram tweaks.
New v9.37 & v8.37
I got Zram fixed. I was able to have 22 apps open at the same time and Android did not close the apps on me. I was using 1.8 gig's of Zram when doing that. Because Zram was never working before it will take like 1 second sometimes to open an app that's because it's in compressed ram and the phone needs to uncompress it on the fly. So just an fyi. The Zram size is 2304MB with a mem_limit of 768MB. But this will save loading from the eMMC drive because we are loading the apps from Zram once you have opened the app. Oh yeah and swapfile is disabled. Enjoy everyone.
New v9.36 & v8.36
Also Changed zram disk size to the optimal size of 2304MB I did the math and this is the best size of zram for this phone. Swapfile is disabled.
New v9.35 & v8.35
Removed the swapfile as it may slow the phone down. Increased the size of the Zram.
Enable 768MB Zram mem_limit and disksize of 3840MB
New v9.34 & v8.34
Fixed an issue with the swapfile priority
New v9.33 & v8.33
Changed Zram to 768MB Added swapfile 1024MB
Fixed issue with sluggish ui
I set the priority of Zram to high and the swapfile to low so the phone will use Zram first then once it's filled up the phone will start using the swapfile. This should give us a lot more ram for multitasking.
New v9.32 & v8.32
Added a 1.5Gig Zram with lz4 compression. Removed Swapfile.
Well I did a lot of research and trial and error, and have concluded that we need to give zram a try. I have came up with a custom zram that's 1.5Gig's. This phone is lacking ram. I wish we had 6 gig's or 8gig's. But we have 4gig's and most of that is used by the OS. So the only way to increase the ram on the phone is with zram. The next version will have my own custom zram config that's 1.5gig's. I got it done already. I guess I always thought that zram would slow my phone down, but I have tweaked this version to make it fast. I have to say I am impressed with the results.
New v9.31 & v8.31
Changed swapfile size to 256MB
Found the optimal swapfile size it's 256MB. That will reduce writes on the eMMC drive and still allow you to open a number of apps at the same time without having android kill them. The tweak from last version helps a lot also by freeing up extra ram.
New v9.30 & v8.30
Free up extra ram by reset zram0 and zram1
Lemon Drop is still using a swapfile
New v9.29 & v8.29
Added Speed mod v5.14 change micro sdcard disk scheduler to noop. Might speed up sdcard a little bit.
New v9.28 & v8.28
Added the Lemon Drop Boot logo. I think the phone may boot a little bit faster because there is no animation to load.
New v9.27 & v8.27
Added Speed mod v5.13 fixed image retention issue.
New v9.26 & v8.26
Added Speed mod v5.12 some tweaks a little faster and may improve battery life.
New v9.25 & v8.25
Tweaked the 1024MB Swapfile
New v9.24 & v8.24
Added Internet Speed Tweak
I tweaked "/system/vendor/etc/wifi/wpa_supplicant_overlay.conf" and the wifi is a lot faster now.
New v9.23 & v8.23
Added Camera improvement tweak. This will make the photos you take crisp, clear and sharp.
New v9.22 & v8.22
Fixed bug if system is mounted as read-only. If so then Auto_Debloat would not install. Some other small bug fixes.
New v9.21 & v8.21
Added speed mod v5.11. This should speed up the phone a little bit more. Should also save battery life. I tweaked the sched_upmigrate and sched_downmigrate. The up is set to 95% and down is set to 90%. So if a task is using more that 95% of cpu it will go the big cpu and vice versa.
New v9.20 & v8.20
Increased the swapfile to 1024MB & some fixes. No Zram only a swapfile.
New v9.19 & v8.19
Added Speed Mod v5.10 Tweaked Entropy speed tweak a little bit more.
New v9.18 & v8.18
Added Speed mod v5.9 Added an entropy speed tweak. Should speed up the phone and help with lag.
New v9.17 & v8.17
New Name for the Rom: Lemon_Drop
Added name to Android Version 8.0.0_Lemon_Drop
Just if you were wondering it's the Lemon Drop Candies not the drink. They were always my fav as a kid.
New v9.16 & v8.16
Added United States GPS Fix
To: /system/vendor/etc/gps.conf
New v9.15 & v8.15
Changed the swap file to 512MB, It's more like 488MB but it should be plenty.
New v9.14 & v8.14
Added a 341MB swap file to /cache/swapfile
This is something I wanted to do for a long time but I did not know where to put it at. The cache directory is the best place for it. Flashing the Speed Mod will remove the swap file. If that happens just flash Auto_Debloat again.
On v9.14 & v8.14
You may want to do a format data & reinstall of Oreo And Auto_Debloat. My phone is running faster, sound is great, I am getting close to the final version, this may be it.
New v9.13 & v8.13
Added AdAway default blocklist to /system/etc/hosts
New v9.12 & v8.12
Added a cool Droid startup animation no sound.
New v9.10 & v8.10
Updated speed mod to v5.8, a lot faster now. I think this is the max speed I can get out of the Lgv20.
New v9.9 & 8.9
It's even faster than v8.9 & v8.8. I found OTA file that is needed by the phone to do updates. I deleted that. And also I downgraded Magisk from v23.0 to v21.4 in v9.9. I think for now we should just stay on Magisk v21.4 it seems to work the best with Oreo. Only thing is you need to do another full reinstall again, for this new version. I am getting close to being done with Auto_Debloat.
New v9.8 & v8.8
Formatted the RCT and FOTA devices. Before I was just wiping them. Now there is no way the phone can download FOTA updates. Not in less Android knows how to read a NTFS file system. I think this new version has improved the speed of the phone a lot. Full reinstall is required for this version. Also found out how to unmount all the partitions after Auto_Debloat is done.
New v9.7 & v8.7
Updated to Speed mod v5.7 some other fixes. Enjoy.
I think this is it for awhile. I just keep finding thing to tweak. I am having fun.
New Stable versions of Auto_Debloat
v9.6 & v8.6
Updated the speed mod to v5.6
v9.5.1 & v8.5.1
I spent a lot of time changing the Auto_Debloat install script to get a perfect install of Stock Oreo Debloated. The trick is to un-mount all partitions after Auto_Debloat is done and before you reboot from TWRP into system. It's recommended to do a full reinstall with this version. Lot's of changes to the install script. Also Updated twrp to twrp-3.6.2_9-0-h910.
v9.2.2 & v8.2.2
Sable Branch version also. Has no add-on mods installed. It's recommended to do a full reinstall with this version. Lot's of changes to the install script. Un-mount all partitions after Auto_Debloat is done and before you reboot from TWRP into system.
v9.4 &v 8.4
Updated the Speed mod from v5.4 to v5.5. Moved Auto_Debloat_log to /system and moved build.prop.stock to /system.
Also there was an issue with Auto_Debloat v9.3 & v8.3 where it was not backing up the original build.prop file. Also my phone was getting hot with v9.3 & 8.3 IDK why? But this new version phone seems to be running a lot cooler.
This version there is some other changes I made to improve the install of Stock Oreo. I would recommend doing a full reinstall with this version, if anything to get your stock build.prop file backed up.
v9.3 & v8.3
I wanted to Include some of my Add-on Mods in Auto_Debloat.
What's included is in v9.3
24_BIT_Deep_Buffers_Enabler_v4.1_Lgv20_Oreo
DAC_Enabler+LGMusic_v1.3
Speed_Mod_Lgv20_msm8996_Oreo_v5.4
Thermal_Engine_Mod_v7.0_70c
System wide Quad DAC support. V6.2 in build.prop file
What's included in v8.3
24_BIT_Deep_Buffers_Enabler_v4.1_Lgv20_Oreo
Speed_Mod_Lgv20_msm8996_Oreo_v5.4
Thermal_Engine_Mod_v7.0_70c
System wide Quad DAC support. V6.2 in build.prop file
You can always just flash the version of the mod you want. Theses are just what's included.
You can update if you want, it's always best to do a full reinstall. Update instructions are down below.
v9.2 & v8.2
I was having an issue with my sdcard, my files were getting corrupted. I think I fixed the issue with v9.2 and v8.2. You can update if you want, it's always best to do a full reinstall. Update instructions are down below.
I think it had something to do with Oreo wanting to encrypt the sd card. But it's a issue I have been dealing with for a long time. Let's hope I got it this time. Always backup your sdcard just in case.
v9.1 & v8.1
This version is 95% Vanilla Stock Oreo Debloated to the max. Same for v9.2 & 8.2. This version there is a bug that may corrupt your sd card. Best use v9.2 or 8.2 if you want a Vanilla Stock Oreo Debloated.
05-06-23
Auto_Debloat v9.82 Version for H910/H915 Install Stock Oreo & debloat.
****Warning ONLY flash on the H910/H915****
What's included in v9.82?
Modded boot.img
Triton removed
LG RCT removed (root checker tool)
twrp-3.7.0_9-0-h910
Updated Oreo Modem Drivers
Magisk 24.3
ezV2020 Kernel v1.0
New GPU drivers 313.0 V11
24_BIT_Deep_Buffers_Enabler v4.2 force true 24 bit audio at 44.1 kHz
DAC_Enabler+LGMusic_v1.3_Oreo
Speed_Mod_Lgv20_msm8996_Oreo_v5.28 / includes image retention fix
Thermal_Engine_Mod_v7.0_70c
System wide Quad DAC support. V6.2
Added AdAway default blocklist to /system/etc/hosts (aka ad blocker)
Added United States GPS Fix
Added Camera improvement tweak
Added Internet Speed Tweaks
Added the Lemon Drop boot logo
Added Zram of 2.5GB + LZ4 algorithm and Zram optimization tweaks
Added Hide boot warning message
Added dual channel bonding on 2.4GHz
Upgrade Instructions:
Flash Auto_Debloat v9.x in twrp reboot. If on a lower version of Magisk v24.3 then install the latest working version of Magisk-v24.3.apk GitHub Link, Open Magisk it will say Requires Additional Setup press Ok and Allow if asked. Patch vbmeta in boot image click next. Direct install recommended let’s go then reboot.
Installation instructions:
Before installing Auto_Debloat you need to be on the latest version of twrp. The H915 needs to install the H910 twrp.
Update twrp. twrp-3.7.0_9-0-h910.img
With the phone powered off, hold the down volume button and plug in usb to computer and phone.
type on your computer:
fastboot flash recovery twrp-3.7.0_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
1. First download the two required files.
If you are having issues downloading the rom you can try this download manager for Firefox.
Turbo Download Manager
H910_20g_Oreo_full_rooted.zip
Auto_Debloat_H910_20g_only_v9.x_flashable.zip
2. Then copy both files to the micro sdcard on phone
3. Reboot into twrp
4. Click Wipe
5. Format Data Partition (this will erase your internal storage on the phone)
6. Click back and reboot into recovery again. aka twrp
7. Flash H910_20g_Oreo_full_rooted.zip
8. Flash Auto_Debloat_H910_20g_only_v9.x_flashable.zip
9. Reboot into system, run setup
Notes:
You can use an app like package manager to debloat more apps on your phone.
Magisk app v26.1, does not work with Oreo. Magisk 24.3 is the latest version that works with Oreo.
I had issues running the H910 v20H rom, my phone would crash after a day or two. With the v20G rom, my max uptime was 31 days.
Good idea to reinstall your EFS to get cell signal woking. Under "Is there a guide I can root my Lgv20 with Dirtysanta?" You only need to do this once.
You can DeGoogle at any time, if you want. Under "I want to DeGoogle after Auto_Debloat, can I do that?"
100% FOSS apps you may find useful.
Download FOSS software
F-Droid
File Manager
Amaze or Material Files
Deleted LGClock
Deskclock or New Clock
Deleted LGWeather
Forecastie or Weather
Deleted Google Calculator
OpenCalc or yetCalc
Deleted Google Keyboard
AnySoftKeyboard or OpenBoard
Deleted Google Maps
Organic Maps
Deleted YouTube
Newpipe
Twitch Client
Xtra
Deleted Google Play Music
ViMusic or InnerTune
Podcast Client
AntennaPod
Ad Blocker
AdAway
Tea Timer
Cuppa - Tea Timer
Reddit Client
Infinity
Deleted Facebook
Frost for Facebook
Latest Chromium based browser
Kiwi Browser Next download arm64
05-06-23
Auto_Debloat v8.82 Version for most Lgv20 phones, Install Stock Oreo & debloat
What's included in v8.82?
New GPU drivers 313.0 V11
Disable MLT/LDB
Removed Triton
Disabled LG RCT (root checker tool)
Disabled LG Backup
Disabled ccmd
With out having to Mod your boot.img
24_BIT_Deep_Buffers_Enabler v4.2 force true 24 bit audio at 44.1 kHz
Speed_Mod_Lgv20_msm8996_Oreo_v5.28 / includes image retention fix
Thermal_Engine_Mod_v7.0_70c
system wide Quad DAC support. V6.2
Added AdAway default blocklist to /system/etc/hosts (aka ad blocker)
Added United States GPS Fix
Added Camera improvement tweak
Added Internet Speed Tweaks
Added the Lemon Drop Boot logo
Added Zram of 2.5GB + LZ4 algorithm and Zram optimization tweaks
Added dual channel bonding on 2.4GHz
Upgrade Instructions:
Flash Auto_Debloat v8.x in twrp reboot. If on a lower version of Magisk v24.3 then install the latest working version of Magisk-v24.3.apk GitHub Link, Open Magisk it will say Requires Additional Setup press Ok and Allow if asked. Patch vbmeta in boot image click next. Direct install recommended let’s go then reboot.
Installation instructions:
Before installing Auto_Debloat you need to be on the latest version of twrp.
Update twrp link
With the phone powered off, hold the down volume button and plug in usb to computer and phone.
Note: twrp.img is your version of twrp image file name
type on your computer:
fastboot flash recovery twrp.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
1. First download the five required files.
If you are having issues downloading the rom you can try this download manager for Firefox.
Turbo Download Manager
Stock Oreo 8.0 rooted rom, for your Model of Lgv20.
H918 Rom
US996 DIrtysanta Rom
VS995 Rom
H900DS Rom link1
H990DS Rom link2
ezV2020 kernel for Oreo link
Magisk-v21.4.zip
Latest version of twrp link
Auto_Debloat_Lgv20_msm8996_Oreo_v8.x_flashable.zip
2. Then copy the five files to your micro sdcard
3. Reboot into twrp
4. Click Wipe
5. Format Data Partition (this will erase your internal storage on the phone)
6. Click back and reboot into recovery again. aka twrp
7 Flash in order
A. Your version Of Stock Oreo 8.0 rom
B. ezV2020 Kernel
C. Magisk v21.4
D. Twrp (The twrp img file you can flash with twrp you just need to select Install Image, select the file and choose recovery)
E. Auto_Debloat_Lgv20_msm8996_Oreo_v8.x_flashable.zip
8. Reboot into system, run setup
Notes:
You can use an app like package manager to debloat more apps on your phone.
Magisk app v26.1, does not work with Oreo. You can install the latest working version of Magisk-v24.3.apk GitHub Link, Open Magisk it will say Requires Additional Setup press Ok and Allow if asked. Patch vbmeta in boot image click next. Direct install recommended let’s go then reboot.
Good idea to reinstall your EFS to get cell signal woking. Under "Is there a guide I can root my Lgv20 with Dirtysanta?" You only need to do this once.
You can DeGoogle at any time, if you want. Under "I want to DeGoogle after Auto_Debloat, can I do that?"
100% FOSS apps you may find useful.
Download FOSS software
F-Droid
File Manager
Amaze or Material Files
Deleted LGClock
Deskclock or New Clock
Deleted LGWeather
Forecastie or Weather
Deleted Google Calculator
OpenCalc or yetCalc
Deleted Google Keyboard
AnySoftKeyboard or OpenBoard
Deleted Google Maps
Organic Maps
Deleted YouTube
Newpipe
Twitch Client
Xtra
Deleted Google Play Music
ViMusic or InnerTune
Podcast Client
AntennaPod
Ad Blocker
AdAway
Tea Timer
Cuppa - Tea Timer
Reddit Client
Infinity
Deleted Facebook
Frost for Facebook
Latest Chromium based browser
Kiwi Browser Next download arm64
The latest version of Auto_Debloat, can be download from MEGA or XDA.
Latest version of Auto_Debloat + Mods & Tweaks MEGA
SHA1 = e12c6b241fde84fe792c1910d0d5f1dcecb550af
Auto_Debloat_H910_20g_only_v9.82_flashable.zip
SHA1 = 2314baa5dc0054a3b94dea916bb5f329d51ce3fd
Auto_Debloat_Lgv20_msm8996_Oreo_v8.82_flashable.zip
Credits, A Special Thank You
@ezzony - for the ezV2020 kernel. XDA
@askermk2000 - for the MK2000 kernel. XDA
@me2151 for DirtySanta. XDA
@darkknight200 for the H910 Oreo modem drivers. Download Link
@gavin19 for providing the Adreno 530 GPU drivers 313.0 V11 non-treble-use Download Link
@Alex_HP for the Camera Improvement tweak for Oreo XDA
@helf for the original Camera Improvement tweak for Nougat XDA
@helf for the KCAL settings XDA
@rawe_etc for the TCP Speed mod XDA
@ZDeuce2 for the slow wifi fix XDA
@tom.etc for the dual bonding speed tweak XDA
@4shared for how to hide boot warning message on H910 XDA
@ezzony for the FM Radio mod for Oreo XDA
@clsA for the H910 Oreo v20g rom. XDA
@dudeawsome for the H918 Oreo Rom XDA
@darkknight200 for the DirtySanta-US99620F Oreo Rom Download link
@thchipmunk for hosting the VS995 Oreo Rom XDA
@NotYetADev for making the VS995 Oreo Rom XDA
@dudeawsome for the H990DS Oreo Rom Link1 XDA
@reza_xdv for the H990DS Oreo Rom Link2 XDA
at amitwh for the interactive governor settings for the msm8996 Github
at the people over at AdAway Hosts List GitHub
at the people over at Magisk, for an Opensource Root.
at the people over at TWRP for a great recovery app
at XDA, for a Great Platform.
at Everyone that gave feedback.
And everyone else that I may have missed that helped with the Lgv20.
FAQ & Troubleshooting guide
Updated on 05-17-23
Questions (please read before rooting, or flashing Auto_Debloat)
What's the number one rule I should know before I root my Lgv20?
Very crucial before you flash the KDZ to downgrade your firmware for rooting, make a DUMP with LGUP all files, you don't need to dump system or cache. Put it in a very safe place, like google drive. It will have your EFS and your EFS has the IMEI number of that particular phone. If your EFS ever becomes corrupted then you can re-flash your EFS from your backup to get cell signal working again.
Can I just edit step3.bat and install the latest twrp in there?
No. You need the old version of twrp to format data, then you can update twrp to the latest version. You only need to remove the encryption on the data partition once, when rooting your phone. The old version of twrp is the only version I know of, that can remove the encryption on the data partition.
My camera does not work after Auto_Debloat?
If you were on LIneageOS or crDroid and then flashed Stock Oreo, then your camera may not work afterwords. The only fix that I know of is to root your phone again. Flash the KDZ to downgrade your firmware and root again.
I can not download Magisk modules with v24.3?
It's because that version of Magisk is too old, that's the only version that works with Oreo. You can still install Magisk modules offline, from the zip file.
What is the EFS?
"EFS stands for Encrypting File System, which is really important part of networking and communication for Android Smartphones, It also contains your device IMEI data."
What is the MSM8996?
"MSM8996 (or Snapdragon 820) is a Qualcomm SoC released in 2016."
What does FOSS mean?
Free and open-source software
Can all Lgv20 phones be rooted?
Most but not all.
How to check to see if you can root, lgv20 Anti-Rollback Version ARB
Can my LS997 install the Lemon Drop Rom?
As far as I know there is no Oreo Stock rom for the LS997, so Auto_Debloat will not work on that model of phone. But you may be able to install Lineage OS depending on your firmware. Check your ARB.
Sprint LG V20 Model (LS997): Comprehensive Overview of Guides and Resources (and why most LS997 phones are unrootable)
Go back to the top post and follow the install guide for your phone.
End of questions.
Is there a guide I can root my Lgv20 with Dirtysanta?
Yes, this is how I rooted my H910. It should be about the same for other Lgv20 phones, you just need to find your root guide for your phone.
1. Disable real time scanning, on the windows virus scanner. Download all the files, save terminal emulator to your microsd card the other two save on your computer, unzip dirtysanta, install usb drivers if using windows. Root your H910 with this guide.
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
2. [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) Note: before you flash the KDZ to downgrade your firmware make a DUMP backup with LGUP all files. You don't need to DUMP system or cache. It will have your EFS.
3. On step3.bat wait for phone to reboot from fastboot mode, when you see the LG logo, pull the battery. Do a factory reset and that will load TWRP How to factory reset the Lgv20.
4. Then format data. Very important, you format data with the older version of twrp that is with dirtysanta.
5. Then power off phone.
Note: This next part is for the H910, you need to get your version of twrp for your model of Lgv20. Latest version of twrp link at the bottom of page
6. Download twrp for the H910 twrp-3.7.0_9-0-h910.img
7. With the phone powered off, hold the down volume button and plug in usb to computer and phone.
type on your computer:
fastboot flash recovery twrp-3.7.0_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
8. Then you want to format data once more with the new version of twrp.
9. power off phone
10. Now would be a good time to reinstall your EFS. Just scroll down tell you see Manually reinstall your EFS on the Lgv20.
Troubleshooting guide for Dirtysanta
Getting an error on step1.bat "dirtysanta no such file or directory"?
Just disable real time scanning in windows defender, and try again. You will have to unzip the files again as windows defender will eat up dirtysanta. Dirtysanta was created by the Lgv20 community at XDA, it's not a virus.
I am stuck in fastboot mode on step3.bat, I get an error?
You most likely have a driver issue in windows. Just stay in fastboot mode fix your windows drivers and run step3.bat again.
[GUIDE] V20 Fastboot access in Windows.
Getting Secure Start up when booting?
Secure start-up issue. If your getting this screen do not try and type in a password. After 30 attempts it may brick your phone. What's going on is your data partition is still encrypted. You need to do a format in twrp on the data partition. Some versions of twrp will not remove the encryption correct for the Lgv20. I know the twrp version that is with dirtysanta will remove the encryption from the data partition. Then you can just update twrp again, you only need to format once.
Stuck at boot screen after flashing Nougat rom to root?
After flashing the rom to downgrade your firmware to root, if your stuck at the boot screen. Factory reset that should fix the issue.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
With the phone powered off, hold the down volume button and plug in usb to computer and phone.
type on your computer:
Note: COM6 is what ever com port you were using at the time.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Note: If you just rooted your phone, take battery out after you type fastboot reboot. Because you do not have an os installed yet, the phone will not boot. Go back to the top post and follow the install guide for your phone.
End of dirtysanta guide.
I want to DeGoogle after Auto_Debloat, can I do that?
Yes you can, I will show you how to install microG. It's a free and open-source implementation of proprietary Google libraries, that serves as a replacement for Google Play Services.
Make sure your phone is all setup the way you like, before you DeGoogle. There is no rush, you can DeGoogle at any time. All your paid apps and games from the Play Store should run just fine with microG. You will still be able to download the free apps and games from the Play Store, just not your paid apps and games. In less you login via the Aurora Store with your Google account, but that is against Googles TOS, your account may get banned.
1. Only do this once. Copy all your contacts from your Google account to your sim card. Make sure your signed into Google Play Store, open up the phone app, choose Manage contacts, copy from your email address to your SIM card.
2. Then you want to remove your google account in settings, general, accounts. Un-Check Auto-sync Accounts. Then power off phone, do a factory reset to boot into twrp. How to factory reset the Lgv20
3. Mount system & data, make sure read only is not checked. Open file manager under Advanced and delete the following folders.
To remove any folder from your device, click on the folder.
Then hit the Delete button
Finally, perform a right swipe to confirm the deletion.
/system/priv-app/GmsCore
/system/priv-app/GoogleServicesFramework
/system/priv-app/Phonesky
/data/app/com.android.googlequicksearchbox (then some letters and numbers) May not be there.
/data/app/com.android.vending (then some letters and numbers) May not be there.
/data/app/com.google.android.gms (then some letters and numbers) May not be there.
4. Then restart phone into system, Close all the errors.
5. Then power off the phone.
6. Download the three files.
NanoDroid-microG-23.1.2.20210117.zip
NanoDroid-patcher-23.1.2.20210117.zip
NanoDroid-fdroid-23.1.2.20210117.zip
NanoDroid Main Page
7. Put them on your sdcard.
Note: Now would be a good time to let your phone cool down.
8. Boot into twrp.
9. Install NanoDroid-patcher
Note: this will take 10 minutes.
10. Install NanoDroid-microG
11. Install NanoDroid-Fdroid
12. Wipe Dalvik cache
Note: Now would be a good time to let your phone cool down.
13. Reboot into system.
14. Open F-droid, update.
15. Update to the latest version of Aurora Store from f-droid
16. Open up Aurora Services and click on Whitelist check mark Aurora Store.
17. Open Auroa store choose anonymous. Just choose the default settings for install.
18. Give microG all the permissions it wants. Open microG and enable Google Device Registration. Wait 30 seconds, then restart your phone. After your phone restarts, wait 2 minutes, open microG and check mark Cloud Messaging and the Location Modules.
All done, your phone is now DeGoogled.
Troubleshooting guide for DeGoogle
In microG under Self Check, Play Store Phonesky Has correct Signature is not checked.
First disable Chrome and then download and install Kiwi Browser Next arm64 from GitHub.
Download Termux and copy past this command:
su
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Or use adb
adb shell pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Then update Google WebView to the Latest version from the Aurora Store, restart your phone.
Phonesky should now be checked.
I am logged in as anonymous and the search does not work in Aurora Store?
Yes it's a known bug, open Auora Store sign in as anonymous, open Kiwi browser, do a google search for like "Spotify Lite Play Store". The first link will say in the top left, Google Play. Just click on the link "Spotify Lite". You should get an option to open Aurora Store and set it as the default app. If you get an error "no such app found" or it loads F-droid, then go to settings, do a search for default. Click on Default apps, App links, Aurora Store, click on open supported links, change to ask every time.
Network Location not working with microG?
You have to install Apple UnifiedNlp backend from f-droid and enable it in microG under location modules, disable Deja Vu Location Serivce.
Push Notifications not working?
Clear all data on microG. Give it all the permissions it wants. Open microG and enable Google Device Registration. Wait 30 seconds, then restart your phone. Wait about 2 minutes, enable Cloud Messaging and Location Modules.
Text to speech is not working on my DeGoogled phone.
Install "Speech Services by Google" from the Aurora Store. It was removed automatically when you DeGoogled. Once you get Google Speech Services installed you can install the FOSS app RHVoice do a search for "Speech rate" to activate it.
End of DeGoogle Guide.
How do I install EdXposed on Oreo?
Download the following. All files are from GitHub.
EdXposedManager-4.6.2-46200-org.meowcat.edxposed.manager-release.apk
EdXposed-v0.5.2.2_4683-master-release.zip
riru-v25.4.4-release.zip
Using Magisk Install the following in this order.
1. riru-v25.4.4-release.zip
2. EdXposed-v0.5.2.2_4683-master-release.zip
Reboot
3. Install EdXposedManager-4.6.2-46200-org.meowcat.edxposed.manager-release.apk
EdXposed should now be installed on Oreo.
Note: don't update Riru. You need the older version for EdXposed.
The xposed module repository is not longer working. Some modules you can try.
Gravitybox
Greenify
End of how to install EdXposed.
How can I install the latest Viper4Android FX on Oreo?
Viper4Android FX is a Adaptive Digital Signal Processor that is very powerful, and enhances your phone's audio quality tremendously.
The Viper4Android FX Magisk module was cloned directly from GitHub link
1. If you have an older version of Viper4Android installed, open Viper4Android uninstall the drivers, uninstall in Magisk, also uninstall BusyBox NDK, reboot.
2. Download the latest Viper4Android FX from the mega link, or download from XDA down below.
Viper4Android FX 2.7.2.1
3. Install Viper4Android in Magisk, reboot.
4. Open Viper4Android, allow it to access files, give it root access to install the drivers, phone will reboot.
5. Enable Legacy Mode, this will force Viper4Android to stay on.
6. Done.
Viper4Android Presets
Viper4Android-presets GitHub
direct link
Viper4Android-presets-full-presets-v1.0.zip
1. To install the presets, download, unzip, copy the three folders to your VIPER4Android home directory on your phone. /sdcard/VIPER4Android
2. Then you need to reinstall Viper4Android in Magisk, this will convert all the Presets, may take about 10 minutes.
3.Then reboot.
4. When you open Viper4Andorid it will say no driver found. Just click ok and give it root access, phone will restart.
5. done
Troubleshooting guide & questions
I have Poweramp installed and Viper4Android FX stops working at random times.
Viper4Android will say Processing No. To fix, Disable Direct Volume Control in Poweramp. You may have to restart your phone.
Does Viper4Android FX work with 24bit Hi-Res music players?
Yes, it works with both Poweramp and Neutron music player.
Is there any free and open-source music streaming apps?
ViMusic, InnerTune or Termux Music Players Rom
Does Viper4Android FX work with the Lgv20 Quad DAC with wired headphones?
Yes
How many 24bit Hi-Res music players are there that work with the Lgv20?
Not Sponsored.
There are only two that I know of. Everything else is going to be 16bit Including LGMusic Player. USB Audio Player Pro should work on 24bit but I cant seem to get the free trial version to work on 24bit only 16bit.
24bit Hi-Res music players that are confirmed to work with the Lgv20. Free trails.
Hi-Res Music Player
Poweramp
Hi-Res Music Player
Neutron Music Player
End of how to install Viper4Android FX on Oreo.
Troubleshooting
How can I disable the built in ad blocker?
It's not hard to disable just download AdAway install it and give it root access and then click the pause button to disable the ad blocker. If you ever want to enable it, just click on the button again.
I installed the H910 20H rom with Auto_Debloat, my phone locks up and crashes.
I had issues running v20H, my H910 would crash after a day or two. On v20G my max uptime was 31 days.
How can I pass SaftyNet?
Open Magisk Click on settings scroll down to MagiskHide check that. Click back go to MagiskHide under the shield icon. Check mark Google play services.
I can`t Download Netflix from the play store?
It's becasue your phone is rooted. You can download Netflix from apkmirror.com or you can Degoogle your phone and download it then.
GPS takes for ever to get a lock?
You need to find and install the correct GPS fix for your country. Default is United States.
You just need to copy the gps.conf to /system/vendor/etc/ folder permissions are "0 0 0644" reboot. GPS should connected faster.
GPS Fix
Help I updated to Magisk 26.1 now Magisk will not load?
This is a problem with the app not Magisk it's self. Just uninstall the Magisk app and install the latest working version of the Magisk app.
Magisk-v24.3.apk
My camera does not work after Auto_Debloat?
If you were on LIneageOS or crDroid and then flashed Stock Oreo, then your camera may not work afterwords. The only fix that I know of is to root your phone again. Flash the KDZ to downgrade your firmware and root again.
Security PIN not working, or I forgot my PIN to login.
This can happen if you are restoring a twrp backup. Just delete your pin & set it back up again.
How to Delete Your Android Security PIN
"Improve Location Accuracy" keeps popping up when wifi-calling is enabled?
This is how you fix the google popup message.
Note: 910 is the model number of your phone
dial
*#546368#*910#
Field Test
GPRI VoLET/VoWiFi
IMS
Common
VoWiFi
Use Geolocation Information (Uncheck)
press back, tell you get to home screen
Restart phone
End of Troubleshooting guide.
Frequently Asked Questions
How can I save battery power on the H910 & all phones?
You can turn off AT&T Auto Connect under WIFI. Then under NFC Disable Tag Reading. Also you can download Force_Doze_Mode, this is for all phones.
Force Doze Mode Force your phone into doze mode to save battery. (root only) With Google or without, like LineageOS or a DeGoogled phone.
Also one of my favorite programs for all phones
SuperFreezZ "making it possible to entirely freeze all background activities of any app."
Also if you want to save your battery from wear you can use BatteryBot Pro. You can set an alarm when charged is reached and you can see your battery level on the second screen with the screen off.
BatteryBot Pro "Battery monitoring tool"
Can I see some benchmarks for Auto_Debloat v9.67 & v8.67?
I have an H910 so I can show you benchmarks from Auto_Debloat v9.66 DeGoogled Oreo v20g. I am still using the LG OEM 2018 battery, so a new battery may show better performance.
Geekbench 5
3dmark max
All internet speed tests were done on Auto_Debloat 9.74
Home Wifi on 2.4GHz 144 connection.
AT&T LTE
What options do you recommend for a twrp backup?
Your sdcard need's to be formatted in exfat.
Boot
Recovery
System Image
data (excl. storage)
EFS
Firmware
LAF/Download Mode
What about a twrp restore?
You should factory reset, then restore only if you were already had Lemon Drop installed.
You only need to flash.
Boot
System Image
Data
How do I format my sdcard for the Lgv20 & copy over my data?
Note: Formatting will delete all you data on your microsd card. So you may want to make a backup first before formatting.
I have found that it is best to format the sdcard in twrp.
Click on Wipe
Click Advanced Wipe
Check Mark Micro SD card
Click repair or Change file System
Click Change File System
Click on exFAT
Swipe to format
It's best to just Mount the Usb Storage in TWRP to copy over your data to you micro sd card. I was having issues with my sdcard reader in my laptop. I think it was corrupting the files on the sd card. This way you don't ever have to take your card out of your phone.
What is the differences between Auto_Debloat 9.x & Auto_Debloat 8.x?
Not much they are almost identical. Auto_Debloat 9.x has the H910 boot.img, twrp and modem drivers. Auto_Debloat 8.x does not have the boot.img, twrp or modem drivers, so it can be used on most Lgv20 phones, running Stock Oreo 8.0.
Can I use my Unlocked Lgv20 on another carrier, after Auto_Debloat?
You will need to make sure your APN is setup. Access Point Names, Go to settings, Mobile Networks, Access Point Names. If you do not see your carrier there you need to manually type it in. Do a google search to find your APN carrier settings. Other than that you will need to find out if the Lgv20 model phone you have is compatible with the carrier you are using it on. You may also need to call your cell provider and have them enable LTE or give them your IMEI number.
What does Auto_Debloat change on the Lgv20?
It removes a about one gigabyte of bloatware, disables all logging on the phone. Disabled MLT/LDB that slows your phone down. Removed LG Root Checker tool. Disabled all FOTA updates, when your phone is rooted FOTA updates will break your phone. Oh and there is my very own custom build.prop tweaks I have put together. Also Auto_Debloat will update the GPU drivers. All these changes will speed up the Lgv20 and bring it back to life, so you can use it for years down the road.
Why did I make the Lemon Drop Rom and the extra-add on mods?
I love my Lgv20 phone, it's an awesome phone. I don't think there will ever be another phone like the Lgv20. I want to use my Lgv20 phone for years down the road. I cant stand it when my phone or computers don't run perfect.
Why did I make the FAQ & Troubleshooting guide?
There is no way I could remember all this information. I use the guide myself, when I need to reinstall the Lemon Drop Rom. Once I forgot that I needed to reinstall my EFS, and I could not understand why I was only connecting at 4G not LTE. That's when I decided I need to write all this information down.
I am a developer may I port Auto_Debloat to another phone?
Yes you may, I only have an Lgv20. But if you want to take the time and port Auto_Debloat over to another phone, go for it.
Is LTE going away because of 5G?
"LTE, which stands for Long Term Evolution, will be around for at least 10 years, so 5G will not make LTE obsolete any time soon. May 20, 2020"
Can I change my Lgv20 from CDMA to LTE/GSM?
Depending on your version of firmware.
LG V20 CDMA to LTE/GSM switch via Hidden Menu
Can I go to LineageOS from the Lemon Drop Rom?
Yes you can, flash the KDZ to downgrade your firmware and root your phone again.
The End.
Credits, A Special Thank You
@vlad48 for the CDMA to LTE/GSM Guide
@Vexamus for the fastboot windows drivers Guide
at Christopher Roy Bratusek for NanoDroid
at u/C---D for the guide on the LS997.
at Zackptg5 for the Viper4Android Magisk Module.
at jadilson12 for the Viper4Android-presets
at appuals.com for the guide on how to delete the security PIN.
at hardreset.info on how to factory reset the Lgv20
at viper520 for Viper4Android
at Aamir Siddiqui for the information about Viper4Android FX
EdXposedManager GitHub
EdXposed GitHub
Riru GitHub
V20 connoisseur, well done, nice to see this being kept alive. I do like my V20 even though its now a second phone. Thanks for your time & dedication on this
[email protected] said:
V20 connoisseur, well done, nice to see this being kept alive. I do like my V20 even though its now a second phone. Thanks for your time & dedication on this
Click to expand...
Click to collapse
Your welcome, not a problem. I love my Lgv20 phone.
Darnrain1 said:
First download
Auto_Debloat_Lgv20_msm8996_Oreo_v7.2_flashable.zip
Click to expand...
Click to collapse
There is no link to the flashable zip file? Or am I missing something here?
SidneyD said:
There is no link to the flashable zip file? Or am I missing something here?
Click to expand...
Click to collapse
Yeah give me 5 min I was putting the final touches on Auto_Debloat v8.3 and v7.3. Uploading now.
Auto_Debloat v9.1 and v8.1 Fixed GPU permission files. Backed up stock build.prop file just in case you ever need it.
Just wondering what do u mean by disabling the ota?
I mean what ota do u disable…
stingbandel said:
I mean what ota do u disable…
Click to expand...
Click to collapse
OTA Updates are short for Over the Air Updates. When your phone is rooted then OTA updates will break your phone. I disabled all OTA updates. Also if they push out an OTA Update that changes the ARB Anti Role Back on the Lgv20 then the Lgv20 will be bricked. So it's just a good idea to have them disabled when your phone is rooted. If your going to run a stock based rom.
"An over-the-air (OTA) update is the wireless delivery of new software, firmware, or other data to mobile devices. Wireless carriers and original equipment manufacturers (OEMs) typically use over-the-air updates to deploy firmware and configure phones for use on their networks over Wi-Fi or mobile broadband."
Hey I just wanted to say thank you for creating this! I have an h910, been running alphaomega for the last couple of years I guess pretty happy but it got a bit buggy and is no longer supported obviously.
So this afternoon I'm gonna back up and take the plunge, change to this stock debloated and see how I get along. I'm a bit nervous haha since it's been ages since I tinkered/flashed anything.....will I remember, will it go smoothly jaja....or will this be two days without a phone and lots of hours sat reading? Soon find out!
I love the v20, really appreciate peoples' efforts to keep it alive and useful - I don't know if I'll ever want/need more from a phone to be honest!
*edit* I'm having real problems getting the rom file from androidfilehost There is only one mirror available and it keeps cutting my connection, I have to pause and restart, downloads a few megs and then stops again.....
If it is easy to put up another copy of the file somewhere it'd be appreciated, thank you!
koodz said:
Hey I just wanted to say thank you for creating this! I have an h910, been running alphaomega for the last couple of years I guess pretty happy but it got a bit buggy and is no longer supported obviously.
So this afternoon I'm gonna back up and take the plunge, change to this stock debloated and see how I get along. I'm a bit nervous haha since it's been ages since I tinkered/flashed anything.....will I remember, will it go smoothly jaja....or will this be two days without a phone and lots of hours sat reading? Soon find out!
I love the v20, really appreciate peoples' efforts to keep it alive and useful - I don't know if I'll ever want/need more from a phone to be honest!
*edit* I'm having real problems getting the rom file from androidfilehost There is only one mirror available and it keeps cutting my connection, I have to pause and restart, downloads a few megs and then stops again.....
If it is easy to put up another copy of the file somewhere it'd be appreciated, thank you!
Click to expand...
Click to collapse
Thank you very much, I love my Lgv20 phone and don't want to see it die. I have used A/O in the past it is a good rom just a lot of bloatware on the H910 phone. It's not hard at all to install on the H910 just flash two files and your good to go. But as for download the rom I know what your talking about.
If you have issues downloading the rom from androidfile hosting you use this Firefox extension Multithreaded Download Manager
Edit: You also may want to take screen shots of your phone, that way you know how you had your phone setup before hand. Just press down vol and power at the same time. They are stored in /sdcard/Pictures/Screenshots Back them up to the micro sdcard because you will need to format data and it will wipe everything on your internal storage. Also you may want to backup everything you want to save from your internal storage to the micro sdcard.
Darnrain1 said:
Thank you very much, I love my Lgv20 phone and don't want to see it die. I have used A/O in the past it is a good rom just a lot of bloatware on the H910 phone. It's not hard at all to install on the H910 just flash two files and you good to go. But as for download the rom I know what you talking about.
If you have issues downloading the rom from androidfile hosting you use this Firefox extension Multithreaded Download Manager
Click to expand...
Click to collapse
Thanks for your reply! I reckon flashing it will be easy too - hope so!
I did try with a couple of different download managers in Firefox, no luck. Now slowly but surely getting it bit by bit in brave browser haha. It lets me resume after showing "network error", which firefox didn't. Fingers crossed!
koodz said:
Thanks for your reply! I reckon flashing it will be easy too - hope so!
I did try with a couple of different download managers in Firefox, no luck. Now slowly but surely getting it bit by bit in brave browser haha. It lets me resume after showing "network error", which firefox didn't. Fingers crossed!
Click to expand...
Click to collapse
Yeah Multithreaded Download Manager is the best download manager I have ever used for Firefox. If that don't work you can always use that extension. I just downloaded the rom just now took about 6 min to download. It download at full speed of your internet.
Darnrain1 said:
Yeah Multithreaded Download Manager is the best download manager I have ever used for Firefox. If that don't work you can always use that extension. I just downloaded the rom just now took about 6 min to download. It download at full speed of your internet.
Click to expand...
Click to collapse
Thanks again for your replies!
I will persist with brave for now, I'm at 1.4 gigs and it keeps resuming OK so I'll try to be patient haha. I live in the mountains with limited data connection only, when its good 700kbps, average 200ish - but 100gig a month current limit so I really want to get it this time without wasting data If this one doesn't work in brave, one more try with multithreaded and then a walk into town tomorrow if not.
Looking forward to having a clean install again, cheers!
koodz said:
Thanks again for your replies!
I will persist with brave for now, I'm at 1.4 gigs and it keeps resuming OK so I'll try to be patient haha. I live in the mountains with limited data connection only, when its good 700kbps, average 200ish - but 100gig a month current limit so I really want to get it this time without wasting data If this one doesn't work in brave, one more try with multithreaded and then a walk into town tomorrow if not.
Looking forward to having a clean install again, cheers!
Click to expand...
Click to collapse
Not a problem, just follow the Installation instructions and Auto_Debloat will do all the hard work for you.
Hey man just to update
The install went smooth as, everything seems very snappy and the battery seems to be lasting nicely, no greenify or anything else installed.
I did get an issue I had before when installing AlphaOmega - I had no modem (phone didn't recognize it had a sim card in the slot). I installed as per instructions formatting and rebooting, coming from my previous AO (also Oreo) installation. Fortunately, I solved this problem, wrote a detailed write up and still had my modified modem file from 3 years ago. Here is that detailed write up for if anyone else should have the problem of only having Modem (cell signal) or Fingerprint working after flash. Doesn't seem to happen to many people, but a few have had the same problem as me.
Now in the long process of getting the phone back as I want it
Thanks again for your time and effort on this - it is so nice to boot into a debloated, snappy phone.....just playing with all your recommendations now, the screen ghosting zip seems to have worked well, battery is great, phone is quick....I'll keep playing and reporting anything interesting etc Subscribed, too of course!
koodz said:
Hey man just to update
The install went smooth as, everything seems very snappy and the battery seems to be lasting nicely, no greenify or anything else installed.
I did get an issue I had before when installing AlphaOmega - I had no modem (phone didn't recognize it had a sim card in the slot). I installed as per instructions formatting and rebooting, coming from my previous AO (also Oreo) installation. Fortunately, I solved this problem, wrote a detailed write up and still had my modified modem file from 3 years ago. Here is that detailed write up for if anyone else should have the problem of only having Modem (cell signal) or Fingerprint working after flash. Doesn't seem to happen to many people, but a few have had the same problem as me.
Now in the long process of getting the phone back as I want it
Thanks again for your time and effort on this - it is so nice to boot into a debloated, snappy phone.....just playing with all your recommendations now, the screen ghosting zip seems to have worked well, battery is great, phone is quick....I'll keep playing and reporting anything interesting etc Subscribed, too of course!
Click to expand...
Click to collapse
That's great you got it working. Thanks for posting a guide about how to fix the modem on the H910. I know some people have had issues getting the cell signal working correct in Oreo. I have never had that issue before with both H910 phones I have. So that does help out. Enjoy.
hey everyone I have updated the Thermal mods today 5-5-22 and I have updated the speed mods 5-4-22. The thermal mods are most likely the final version, I am very happy with how they turned out this time. Sometimes I have one of those aha moments and everything just comes together. That's how it was with the thermal mods today.
Updated all the speed mods to v3.1

Categories

Resources