busybox update zip - Hero CDMA General

Can one of you rom gurus make a busybox update zip which includes (super user, busybox and wireless tether) that is compatible with any rom. I like to flash different roms and not all roms allow for metamorph use or wireless tether...

this is for ubuntu 32bit with build-essentials installed and arm enabled in the kernel.
go here
http://busybox.net
then download the tarball and patches
apply the patches
then
make menuconifg
select you options
then make CROSS_COMPILE=arm-linux-uclibcgnueabi-
remount phone in rw mode
then copy the binary to the location of busy box on the phone usually /system/bin or data/local/bin
should be good

I am a complete noob when it comes to this, that why i am asking the community to make it. your instructions appear to be complete, but i am completely lost.

orrrrr........
you could search the Hero CDMA sub-forum and find someone already did this!
http://forum.xda-developers.com/showthread.php?t=593952&highlight=busybox
pretty sure your looking for something exactly like that right?
EDIT: adb remount- superuser application- and busybox plus app2sd if your card is partitioned properly.
EDIT2: wireless tether apk can be found in this thread http://forum.xda-developers.com/showthread.php?t=612221&highlight=wireless+tether

you take all the fun out of it.

Related

Post-Root Setup Instructions?

I know many of us are new to the whole rooting thing. I'm coming from the Windows Mobile world of custom ROMs, kitchens, etc., but I do have some linux experience. However, I can't for the life of me figure out how to do a lot of what comes "standard" in MoDaCo's ROM. Obviously it would be easier to simply install Paul's ROM and be done with it, but I'd really like to learn how to do it on my own too.
So, that being said, maybe we can pull together some tutorials, guides, and/or links to existing guides which explain how to go about setting up our Rooted phones manually. Here are some of the built-in mods the MoDaCo ROM comes with which would be nice to be able to do manually or on a one-off basis:
Included in MoDaCo 1.1 'core':
Rooted with 'adb remount' permission and superuser APK
A2SD included (fully automatic thanks cyanogen!) create a EXT2 partition as your second partition to use. dalvik-cache remains on device.
Added Jbed Java
Added Dropbear SSH running by default, check 'About' screen for password (port 2222). You can now remove this by running /system/bin/removedropbear.sh
Added Notes app from Dragon
Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
Added android-wifi-tether 1.60 pre3 (props to the developer, this is a great app!)
Added WiFi Status indicator, with kind permission of Andrew Schwimmer
Added busybox 1.15.2 tweaked such that 'get information' in Swapper now works as desired
Added nano 2.09 text editor for use in shell mode
Added parted and sqlite tools
Added terminfo and settings to boot.img to allow nano etc. use
Added files required for Debian linux including loxley's updated bootdeb script
Moved Quickoffice to data partition to allow easy uninstall
Moved Google Maps and Google Voice Search to data partition to allow easy update
Silenced boot sound (it's still there and can be reactivated with a file edit)
Click to expand...
Click to collapse
*********
*********
!Working!
Wireless Tethering:
http://android-wifi-tether.googlecode.com/
Go to the "Downloads" tab and download version 1.61-pre
!Not Working!
Superuser Whitelist App
I found two threads here that describe how to install Superuser.apk.
http://forum.xda-developers.com/showthread.php?t=582140
http://forum.xda-developers.com/showpost.php?p=4897587&postcount=5
Using the first one, I was able to get the files onto the phone and I used the chmod commands found in the second file in the hopes this would work; however, whenever I try to use it, nothing happens. The ES File Explorer, in particular, used to work with MoDaCo. When I'd try to browse as root, Superuser would pop-up and ask if I wanted to grant the app permissions. Now it just hangs there (black screen) and ES File Explorer says I don't have root access. Other Root apps work fine though, it's just they don't seem to be dependant on Superuser Whitelist.
'adb remount' permission
This requires that the default.prop file be edited from ro.secure=1 to ro.secure=0. Unfortunately, I can't seem to get this file to stick. If I use the mv command using adb shell, I get some kind of permissions error. If I use the cp command when booting into the recovery menu and using adb shell, the file reverts to the original on boot. Or maybe it's simply not being overwritten, but not throwing any errors either
I think I may have found a thread that will help with the default.prop changes. Looks like this has to be done in the recovery.img which apparently overwrites any modifications in the root of the device on each reboot. I'll post an update if/when I figure it out.
HOWTO: Unpack, Edit, and Repack Boot Images
http://forum.xda-developers.com/showthread.php?t=443994
The adb remount permission issue is driving me crazy. Please keep us updated if you figure out a way of resetting that without installing a new ROM.
I ended up modifying one of the MoDaCo update scripts to set up ADB Remount, Superuser.apk, and Busybox. It's been working fine for me, but be sure to do a backup before you apply the update. Check it out here:
http://forum.xda-developers.com/showthread.php?t=593952

Busybox update.zip for incredible?

Does an update.zip exist for the incredible to add busybox to a stock rooted Rom? Or is there anyone willing to make one? I found one for the hero where they stripped down a rom and just left busybox, apps2sd, and Su. It would be greatly appreciated by many noobs like myself.
Sent from my ADR6300 using XDA App
I believe Stericson has an app out that installs busy box for you with a single click. Just search "Busy box" in the market and it should come up. Not sure as to whether or not it works on the Incredible, as I've an Evo, but it should.
I tried that but it failed saying either I it couldn't remount or I wasn't rooted.
Sent from my ADR6300 using XDA App
bradatz said:
Does an update.zip exist for the incredible to add busybox to a stock rooted Rom? Or is there anyone willing to make one? I found one for the hero where they stripped down a rom and just left busybox, apps2sd, and Su. It would be greatly appreciated by many noobs like myself.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I think the unrevoked tool installs it for you.
I'll try that again, but I used 3.0 to root it. Maybe 3.1 will install it, I thought that was only windows fixes from 3.0
maybe
kind of a rookie here, but couldn't you just install titanium backup and then click the problems button. I think it downloads and install busybox??
Nice call!!! Worked like a charm. Thx.
NO
ejkeebler said:
kind of a rookie here, but couldn't you just install titanium backup and then click the problems button. I think it downloads and install busybox??
Click to expand...
Click to collapse
Wouldn't be permenant since NAND is still locked. Would lose it after reboot and have to do same thing over and over after every reboot.
http://www.unrevoked.com/incredible/payload-update.zip
Apply this payload-update.zip and it will install busybox. Just go to recovery and choose install zip from SD card and then choose this one
Then to test
go to cmd prompt
type adb shell
then when in shell type
busybox and you will see its now installed.
If you want the latest busybox, I've attached 1.16.2 freshly compiled.
One issue I ran into was that all the info on the forums has busybox being installed in /system/xbin. The PATH variable has /system/bin before /system/xbin, so that means the original symlinks to "toolbox" are getting picked up first - I don't know if I'm the only one who was annoyed by ls -al returning "-al: No such file or directory"
I guess "toolbox" didn't support this, so you can either install busybox to /system/bin, or leave it in /system/xbin and create a symlink called toolbox in /system/bin that points to busybox in /system/xbin.
As usual, backup your "toolbox" binary first before removing it from /system/bin.
Now ls -al returns a correct listing and I see no app breakage by the symlink method - Ti Backup runs just fine without needing to install its own busybox.
*edit - I guess this doesn't really answer the OP, but I figured I would share this anyway.
ok so I found a side effect - WiFi doesnt work after this. There seems to be a problem with dhcpcd and the new busybox, even though external dhcp support was compiled in...guess I've got some digging to do...
http://codehydra.com/Dinc/RootStock/roto-rooter.zip
that is a busybox install I ripped out of a N1 froyo root update.zip Cyanogen did, modded for the D-Inc.
Seems to work well for me.
the easy way is just to install titanium backup from the market and then click problems and it will install busybox for you in like 5 seconds
Not Really
... but it does NOT install the newest busybox; just one which is compatible with Titanium Backup.
Busybox.net shows v1.17 is the latest (unstable) release, and v1.16.2 is the latest stable. Titanium Backup pushes something in the v1.15 area.
http://www.busybox.net/
Also when I did it through titanium and went to busybox to install latest it said my system had none.
I have a busybox 1.16.2 version that I ripped from one of the posted ROMs that I can attach. It works on the Inc, and I think the whole DHCP / resolv.conf thing works too. At least it's the only version I tried where I can get wget working properly. You may need to create /system/etc/resolv.conf with some valid nameservers first though. Let me know if you want me to post it.
Hmm, nevermind. I tried with the busybox version I have, and WiFi does not get an IP address. Seems to be the same problem.
If you track it down, when you compile your version check if wget works properly also. There were some issues with that and DNS lookups. Don't forget you may need a valid resolv.conf.
Joe92T said:
the easy way is just to install titanium backup from the market and then click problems and it will install busybox for you in like 5 seconds
Click to expand...
Click to collapse
I second this , I used ones off the rooting forums and it never quite worked right until I let titanium backup install it for me. Also its much easier than pushing files to your device if you are unfamiliar with doing it, because you can download tb from market and it does the work for you
Sent from my ADR6300 using Tapatalk
Easiest way to stay current is to install the Stericson app. It can't install it for you due to the NAND lock, but
1) It's trivial to extract it and install manually from the .apk file.
2) It will give you an easy notification via the marketplace that a new version is available.

Root problems with newer ROMs

Curse these programs that won't use newer su/busybox combinations.
After installing one of the latest blur ROMs, I wasn't able to get webtop2sd to run (a very common problem), nor Cisco's Anyconnect VPN client. webtop2sd did the usual FC, while Anyconnect would complain that it couldn't start a "critical component". Going back to the one I was running before the upgrade didn't help either.
These problems are not unique to the beta, nor this ROM, but here's what I had to do:
Follow the steps in this thread starting in step 6:
http://forum.xda-developers.com/showpost.php?p=21155110&postcount=852.
Total props to dicksteele for the original post. Thought it might be better to put out here since this seems to be a recurring issue on most ROMs now.
Specifically,
6. Install Busybox installer from Market. Ran app installed busybox into /system/bin.
7. Open Root explorer Go to /system/etc mount r/w create webtop2sd directory
8. Go to /system/bin copy busybox over to /system/etc/webtop2sd
9. Still in root explorer, go to /system/bin and /system/xbin and delete su
10. Can't use quick reboot to reboot into recovery because su has been deleted. Wherever your adb is located, run adb reboot recovery.
11. Install the superuser app from the zip I have attached. Reboot.
12. Open some other app besides webtop2sd that needs root. Verify root is working.
13. Install webtop2sd.
14. Open webtop2sd, hopefully no FC's. Do the webtop2sd partitioning and copy webtop over to new partition on sdcard.
Click to expand...
Click to collapse
Yes, webtop2sd was very picky to the point of needing busybox from the installer, not the identical one installed by the ROM. Once I got webtop2sd running, I tried Anyconnect again and it started right up.
I can understand webtop2SD not working since it hasn't been updated for a long time, but a company like Cisco should be sure their tool, available on the Market, works with the latest superuser/busybox combinations.
I would go so far as to say that if you are having trouble with any programs requiring root access, try the steps above used to get webtop2SD working. Hope this helps others stuck on similar issues with these newer ROMs.

"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)

"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)
I used Wug's all in one root. All went well. It also included the busybox app. I did the installation using the default choice of system/xbin, which appeared in a "how-to" video as well. In the video it showed that it loaded successfully. Mine did not load successfully. It specifically said that there was a conflict with the location. I tried system/bin and it basically said the same.
My main question is. 1. What does busybox do that I will need on this device, and 2. How then do I load it, as in, what options should I choose for location? Or delete altogether and reload it? and that question is asked because I want to make sure that deleting the app will not mess up my root/rom/twrp or anything else.
Thank you in advance.
busybox provides a set of linux commands needes especially when you want to run scripts e.g. in init.d
What version of Android do you have installed? Most likely there is no space left on /system and so installation of busybox failed. If you are on a custom rom, you can try to flash micro / pico gapps instead of the normal ones to leave some space left on /system for busybox, or you need to root your device "systemless" and you can install busybox on the partition provided by SuperSU ...

[Q] any PH1 rom with no GAPPS?

Hi All,
I am interested in any ROM, preferably based on LOS, that has no GAPPS pre-installed?
Is there any such? nougat, oreo, and whatever P is... doesn't matter.
A follow-up question for the more technically advanced than I: why is this such a problem for PH1? I believe the PIXEL phones also have A/B partitions, and are supported by LOS
Thanks!
lleo_ said:
Hi All,
I am interested in any ROM, preferably based on LOS, that has no GAPPS pre-installed?
Is there any such? nougat, oreo, and whatever P is... doesn't matter.
A follow-up question for the more technically advanced than I: why is this such a problem for PH1? I believe the PIXEL phones also have A/B partitions, and are supported by LOS
Thanks!
Click to expand...
Click to collapse
The number of developers fixing issues on the pixel vs this phone is astounding...
rignfool said:
The number of developers fixing issues on the pixel vs this phone is astounding...
Click to expand...
Click to collapse
I do recognize that, but given similarities between devices, would not be possible to adopt the work done by those developers. Granted that I ask this with the knowledge of a noob.
To follow up are you saying that there is no such as GAPPS-less ROM for PH1?
lleo_ said:
I do recognize that, but given similarities between devices, would not be possible to adopt the work done by those developers. Granted that I ask this with the knowledge of a noob.
To follow up are you saying that there is no such as GAPPS-less ROM for PH1?
Click to expand...
Click to collapse
There are... But they come and go as far as updates and such...
The demand is for Google... And moar features without losing Google...
Now... What you can do/try is wander over to the Project Trebble area... I would assume that you will find a plethora of development...
You're gonna be wading in some unknown territory... And it'll be a mystery as to what works... And whether it's fixable... Good luck
EDIT: or... You can magisk yourself... And try NanoMod... I think that disables a ton of Google stuff and puts FOSS stuff in it's place...
Sir! Thank You for your post. At first I thought it was a joke, but I learned something today. The concept and related work of project Treble bypassed me. I have already a GApps-less LOS on my Ph1. Again thanks!
Don't know if this applies, but lots of ppl are successfully running GSIs on the Essential.
Maybe some of them are GAPP-less?
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
DoR3M3 said:
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
Click to expand...
Click to collapse
Hey can you explain how to debloat, is there a script for it. How do you patch it and deodex it.
Thanks
arjunv said:
Hey can you explain how to debloat, is there a script for it. How do you patch it and deodex it.
Thanks
Click to expand...
Click to collapse
These steps below, you're probably going to wonder, why do I need to Deodex and Signature Spoof just to debloat? Good point, you don't, but then you can only get so far away from Google in your system by not doing this. The point to this method is to have Signature Spoofing support in Android, where you can better utilize microg support, to have it as the alternative instead of Google.
The Deodex and Nanodroid-patcher support, only need to be performed if you are running Stock Android, or a ROM that has not been Deodex and doesn't support Signature Spoofing. This also doesn't have to be done, if you still want to run the Google Services/Framework.
If you only want to Debloat, then follow the Debloat section below.
For the Deodex, YMMV (Your Mileage May Vary), but it's been working great for me, so here goes!
I did this on Stock Oreo 8.1.0 which has both odex and vdex files in /system/framework, so I followed the VDEX method mentioned below.
This is going to be easy if you're a Linux User/Geek, if you are running Windows and have never done anything like this, and if you have both odex and vdex files on your phone in /system/framework, then I can do this for you if you want, unless you want to get into learning this.
If you want me to, then in TWRP, click Mount and click on System at the top to mount it and then run this command in the command prompt, I'm assuming you have adb/fastboot installed...
adb pull /system/framework framework If that doesn't work, it typically ends up being, adb pull /system/system/framework framework
I'm assuming your device is arm64, so then look in the directory; framework/oat/arm64/ or /arm, and attach the services.vdex file and I'll patch it for you.
Deodex & Signature Spoofing
1. Check /system/framework, do you see both .odex and .vdex files?
2. If you have both .odex and .vdex files follow the guide under VDEX, if you only have .odex files, then follow the ODEX section. Don't be confused by the guide as only having either services.vdex or services.odex. You are looking to see if all the files are one or the other or both.
https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
3. If you have both files and need to follow the VDEX method in Windows, then you'll need cygwin as stated on the vdexExtractor Github, and install zlib-devel from the cygwin installer. cygwin as stated on the site is a collection of GNU and Open Source tools, this allows you to compile the vdexExtractor source in Windows into the running program.
https://www.cygwin.com/
4. If you have to do the ODEX method the baksmali.jar and smali.jar are already built, there's a download for them on the GitHub page, and you'll need to have Java JRE installed.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Whether I'm patching it, or you follow one of the methods I've described, once this is done, you'll need to download the latest NanoDroid-patcher. This is what patches the Deodex ROM to apply signature spoofing support.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 - Stable Download (Nanolx)
Be sure to also grab NanoDroid-fdroid if you don't have F-droid installed. You might want to also grab NanoDroid-microG while you're at it, if you want to go for a real system Google Debloat too, but any concerns, or issues, please post on Setialpha's NanoDroid post for any microg support.
As soon as you're done with the Deodex steps, at the bottom the tutorials clearly state; unmount /system and flash the NanoDroid-Patcher, so uncheck System that you checked before in Mount, and now install/flash NanoDroid-patcher, TWRP > Install
If the device is not rooted, then make sure to root it with Magisk. Personally I find it best with the Essential to now boot to the bootloader, then boot back into TWRP. In TWRP flash NanoDroid-fdroid if you grabbed it, then the boot.img and then Magisk, then boot into the System.
Debloating Apps Systemlessly
1. Open Magisk Manager - Downloads - search for Debloater, then you should see Debloater (Terminal Emulator).
2. Reboot
3. Now you'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with lots of things going on about it. If you didn't install F-Droid as I mentioned before, then you should of noticed on the NanoDroid download link NanoDroid-fdroid, download this and flash/install it in TWRP.
4. Now with F-Droid, open it, go to Settings and turn on Expert mode and check Privileged Extension, then close and reopen F-Droid. Next, search for and install Termux.
5. Open Termux and at the command prompt type su for superuser access. On a side note, if you don't know, or have never used Termux, press and hold Vol UP on the phone and tap q on the keyboard which will give you some short cut options. But you'll want to go online to their Wiki and learn about the power of Termux.
6. Now simply type debloat and remove what you want. Remember if you make a mistake, you have Option 4 to reinstall what you removed by mistake.
That's all there is to Deodex, Signature Spoof Patching and Debloating apps systemlessly in Android.
If the VDEX/ODEX methods don't work for some strange reason, then you'll want to explore using SuperR's Kitchen to Deodex the rom, and most people recommend you get the donate version for better features and support.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Good Luck
DoR3M3 said:
These steps below, you're probably going to wonder, why do I need to Deodex and Signature Spoof just to debloat? Good point, you don't, but then you can only get so far away from Google in your system by not doing this. The point to this method is to have Signature Spoofing support in Android, where you can better utilize microg support, to have it as the alternative instead of Google.
The Deodex and Nanodroid-patcher support, only need to be performed if you are running Stock Android, or a ROM that has not been Deodex and doesn't support Signature Spoofing. This also doesn't have to be done, if you still want to run the Google Services/Framework.
If you only want to Debloat, then follow the Debloat section below.
For the Deodex, YMMV (Your Mileage May Vary), but it's been working great for me, so here goes!
I did this on Stock Oreo 8.1.0 which has both odex and vdex files in /system/framework, so I followed the VDEX method mentioned below.
This is going to be easy if you're a Linux User/Geek, if you are running Windows and have never done anything like this, and if you have both odex and vdex files on your phone in /system/framework, then I can do this for you if you want, unless you want to get into learning this.
If you want me to, then in TWRP, click Mount and click on System at the top to mount it and then run this command in the command prompt, I'm assuming you have adb/fastboot installed...
adb pull /system/framework framework If that doesn't work, it typically ends up being, adb pull /system/system/framework framework
I'm assuming your device is arm64, so then look in the directory; framework/oat/arm64/ or /arm, and attach the services.vdex file and I'll patch it for you.
Deodex & Signature Spoofing
1. Check /system/framework, do you see both .odex and .vdex files?
2. If you have both .odex and .vdex files follow the guide under VDEX, if you only have .odex files, then follow the ODEX section. Don't be confused by the guide as only have either services.vdex or services.odex. You are looking to see if all the files are one or the other or both.
https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
3. If you have both files and need to follow the VDEX method in Windows, then you'll need cygwin as stated on the vdexExtractor Github, and install zlib-devel from the cygwin installer. cygwin as stated on the site is a collection of GNU and Open Source tools, this allows you to compile the vdexExtractor source in Windows into the running program.
https://www.cygwin.com/
4. If you have to do the ODEX method the baksmali.jar and smali.jar are already built, there's a download for them on the GitHub page, and you'll need to have Java JRE installed.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Whether I'm patching it, or you follow one of the methods I've described, once this is done, you'll need to download the latest NanoDroid-patcher. This is what patches the Deodex ROM to apply signature spoofing support.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 - Stable Download (Nanolx)
Be sure to also grab NanoDroid-fdroid if you don't have F-droid installed. You might want to also grab NanoDroid-microG while you're at it, if you want to go for a real system Google Debloat too, but any concerns, or issues, please post on Setialpha's NanoDroid post for any microg support.
As soon as you're done with the Deodex steps, at the bottom the tutorials clearly state; unmount /system and flash the NanoDroid-Patcher, so uncheck System that you checked before in Mount, and now install/flash NanoDroid-patcher, TWRP > Install
If the device is not rooted, then make sure to root it with Magisk. Personally I find it best with the Essential to now boot to the bootloader, then boot back into TWRP. In TWRP flash NanoDroid-fdroid if you grabbed it, then the boot.img and then Magisk, then boot into the System.
Debloating Apps Systemlessly
1. Open Magisk Manager - Downloads - search for Debloater, then you should see Debloater (Terminal Emulator).
2. Reboot
3. Now you'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with lots of things going on about it. If you didn't install F-Droid as I mentioned before, then you should of noticed on the NanoDroid download link NanoDroid-fdroid, download this and flash/install it in TWRP.
4. Now with F-Droid, open it, go to Settings and turn on Expert mode and check Privileged Extension, then close and reopen F-Droid. Next, search for and install Termux.
5. Open Termux and at the command prompt type su for superuser access. On a side note, if you don't know, or have never used Termux, press and hold Vol UP on the phone and tap q on the keyboard which will give you some short cut options. But you'll want to go online to their Wiki and learn about the power of Termux.
6. Now simply type debloat and remove what you want. Remember if you make a mistake, you have Option 4 to reinstall what you removed by mistake.
That's all there is to Deodex, Signature Spoof Patching and Debloating apps systemlessly in Android.
If the VDEX/ODEX methods don't work for some strange reason, then you'll want to explore using SuperR's Kitchen to Deodex the rom, and most people recommend you get the donate version for better features and support.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Good Luck
Click to expand...
Click to collapse
Thank you so much for a detailed post
DoR3M3 said:
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
Click to expand...
Click to collapse
Stoked to see two things here...1.) the answer to the question I was searching for about running my Essential with no gapps...and 2.) your choice in file explorers!

Categories

Resources