Database Develop

Root Technical Details

Hi, I've been searching for technical details of how root is actually obtained on the Android system. Specifically, I'm interesting in the Nexus One, but I'm curious about any methods that are available.
After reading the adb documentation among others, I've come to the belief that at least on the N1 it's as simple as remounting system as root and changing the permissions of su followed by installing busybox. After that the superuser application is installed, and it updates su with it's own version.
(This is only for updating the application on an already rooted system)
Superuser appears to grant root privileges to itself then overwrites su with it's own variation that uses its database for permissions, and calls the app with:
Code:
sprintf(sysCmd, "am start -a android.intent.action.MAIN -n com.koushikdutta.superuser/com.koushikdutta.superuser.SuperuserRequestActivity --ei uid %d --ei pid %d > /dev/null", g_puid, ppid);
I'm curious how cyanogen handles it without having the user install busybox, etc. before flashing his mod. I would think the Android system would only allow signed updates, but I have a feeling that the custom recovery image bypasses that.
If someone could just link me to a forum link/blog/etc. (if they exist) or give me some advice on things to search for, that would be great.
I'm just now getting into Android kernel development, and would love to know everything I can about it. I've been way to busy with a research project at school, but it's pretty much over at this point. I plan on becoming much more involved here especially with some programming some ideas I have for improvements to both the kernel and Google's applications.

meinhimmel said:
I'm curious how cyanogen handles it without having the user install busybox, etc. before flashing his mod. I would think the Android system would only allow signed updates, but I have a feeling that the custom recovery image bypasses that.
If someone could just link me to a forum link/blog/etc. (if they exist) or give me some advice on things to search for, that would be great.
.
Click to expand...
Click to collapse
bingo. upon unlocking the bootloader, you are able to flash a custom recovery which does not require google keys and you are able to install custom roms. the roms usually have busybox and the other applications built in. custom recovery also has all the binaries require for flashing roms.
a good site would be platform.android.com (something like that) for developing roms/editing kernel. you can also check the "android development" on the xda main forum homepage, there are a couple of stickies there worth reading

[HACK] [Script] Semi-Automated Unlock/Root Script for Linux

Script pulled; should have it back up by Wednesday.
Hey guys. I've written a shell script to automate some of the more menial tasks involved with unlocking the Nexus S bootloader and rooting it. It also guides you through the various tasks involved in the process, and IMO is a more noob-friendly alternative to my guide on manually rooting.
Disclaimer again: I take no responsibility if something goes wrong (if it does, it should be fixable though), Unlocking your bootloader voids your warranty (but you can lock it back), Unlocking the bootloader will wipe your entire phone, including USB Storage; so make a copy of all those family photos and other files you may have put onto the USB storage if you want to keep them.
The script should run fine on most configurations; if you have issues post them below. The script isn't very elegant, but it gets the job done. Pay attention to the terminal as you go through it and you should be fine.
Some Notes:
- OTA updates will not flash because the modified boot.img flashed in this script causes an MD5 mismatch. You should flash the latest OTA update before running this script, if you aren't already running the latest update.
- The latest OTA update, GRH78 (2.3.1) can be found with instructions on flashing here: http://forum.xda-developers.com/showthread.php?t=884097
- You do not need root to flash OTA updates.
How to run
1. Download the attached file and rename it to 'nsrootscript.sh'
2. Mark it as executable either by navigating to it, right-clicking it, Properties > Permissions tab, and checking 'Allow executing file as program', or running this command:
Code:
chmod +x /path-to-file-here/nsrootscript.sh
3. Double-click it and choose 'Run In Terminal' or use the command:
Code:
./path-to-file-here/nsrootscript.sh
4. Follow the instructions given in the script, and you should be rooted in no time.
Special Thanks
Koush; Developer of ClockworkMod Recovery and ROM Manager. Buy him a beer here: https://www.paypal.com/us/cgi-bin/w...63663d3faee8d9384d85353843a619606282818e091d0
Paul; Developer of Superboot. Help him raise money for Cancer Research and possibly win yourself a nice gadget here: http://android.modaco.com/content/charitable-projects/317387/10k-for-p10k-for-childhood-leukemia/
If you have any issues, concerns, or comments, feel free to leave them below.

I just looked through your script. Noticed it is using superboot boot.img's to root. You might want to put a note that this will probably prevent future OTA updates from flashing, since those boot.img's are modified and will get MD5 mismatches.

Luxferro said:
I just looked through your script. Noticed it is using superboot boot.img's to root. You might want to put a note that this will probably prevent future OTA updates from flashing, since those boot.img's are modified and will get MD5 mismatches.
Click to expand...
Click to collapse
Thanks for the heads up, I'll put that in the OP.

Thanks man, looking forward to getting and trying this out

works like a charm thank you very much!

I'm sorry but I just don't see the point it rooting a DEVELOPER phone? You open up lots of features that are not available to non root so therefore make developing useless as you will lose more than half your market! I understand if you are specifically making a root application but I'm sure most of you aren't!
[/Rant]

stothy862 said:
I'm sorry but I just don't see the point it rooting a DEVELOPER phone? You open up lots of features that are not available to non root so therefore make developing useless as you will lose more than half your market! I understand if you are specifically making a root application but I'm sure most of you aren't!
[/Rant]
Click to expand...
Click to collapse
Root isn't just of interest to developers. Root allows the end user to do many interesting things, a small set:
- Applying custom themes
- Blocking annoying ads
- Take screenshots
- Set CPU clock speeds / overclock for better performance, underclock for better battery life
- Replacing system apps / files (There are various reasons for this, one example is the modified MMS.apk floating around that fixes the blurry MMS issue)
- Flash custom ROMs which can offer performance increases, battery life increases and add useful features not found in stock (CyanogenMod is a good example)
-And there's a lot more, but it's 2 AM where I live, lol.
As for people that develop applications that require root, that's because what they do (blocking ads, theming, taking screenshots, etc.), well requires root. There's no way around that. And since root is obtainable on most Android devices without too much hassle, what's the harm in coding something to make people's Android experience a little better?

kexec for HP TouchPad (WORKING release!)

kexec is now fully working!
Kexec host kernel: https://github.com/willcast/ubuntu-kernel-tenderloin branch is "kexec"
Graphical bootloader: https://github.com/willcast/kexecboot
Compiled host kernel uImage UPDATED: https://docs.google.com/file/d/0B4WUjKii92l2RHJoNE93c2dVRlU/edit?usp=sharing
THE ATTACHED KERNEL PATCH (decomp_copy_atags.diff) _MUST_ BE APPLIED for ANY kernel to be bootable FROM kexec.
YouTube: http://www.youtube.com/watch?v=ko_4cOj_5iM
Kexec kernel and OS installation is best performed through SmackMe2, which is available in its own thread on this site.

I have no idea what you are saying, but keep up the great work!

Keep up the good work man , one question with you work in the future can we delete web os from the touchpad forever?

I imagine that's already possible. Use lvm to delete all the logical volumes not tied to another OS and then delete the uImage.webOS symlink. That deletes webOS, frees mostof its space and removes it from the moboot menu.
If you choose to do that, though, using the doctor to restore WEBOS will be even more difficult because you'll have to wipe out everything AND potentially need to "unbrick" your TP (using the method involving NovaCom, the small boot image ripped from the doctor and a string of LVM commands that is posted on sone or other forum.)

Lvm? Can you make a tutorial? How to remove webos from touchpad?
Thank you

Before this is complete or posted for testing, I think we will need a tutorial and links to files of how to fix the tp from a full brick such as issues with removing and restoring webos.
Great job if your boot loader works as planned we will have a full multi-boot device with a few restrictions(drivers for untested ports, etc).
Keep it up.
Sent from my cm_tenderloin using xda app-developers app

Awesome that you're resuming development castrwilliam! Can't help you with kexec though, sorry. I hang around in the Motorola Defy forums and some developers like Quarx have tried pursuing the kexec route in order to load custom kernels onto the Defy, might be worthwhile to throw him a PM. Would be great to have a more flexible bootloader!
I anyone needs a full restore, this thread helped me out. I followed the instructions when I screwed up and doctored without removing partitions. I believe WebOS Doctor handles repartitioning, so it should work:
http://forum.xda-developers.com/showthread.php?t=1426244

WORKING (but non-Kexec) Android multiboot for TouchPad.
DON'T TRY ANYTHING UNTIL YOU HAVE READ THE WHOLE POST!!
Beta 2 Updated with support for my Froyo Qcom kang.
I created a script that can install multiple versions of Android on the HP Touchpad, side by side, such that they can be selected at the MoBoot menu and operate independently. The script modifies them, on the Touchpad itself, to work with the new names for the partitions.
I want your feedback on this installer. It is used in the same way as ACME Installer but only shares one line of actual code with it (and it also uses the same binaries and config files on the initial ramdisk image, but they are Open Source so that should'nt matter.) I'll be posting this on XDA in a minute, my username there is also "castrwilliam".
If you do choose to use (TEST!) this:
- You need to create a folder on your media partition (the one that is shown when you select USB mode) with the following zips:
moboot [moboot_0.3.5.zip]
(the rest are optional but I recommend using them all so that you can help me test everything)
Froyo Test [Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip]
CM7 alpha3.5 [update-cm-7.1.0-tenderloin-a3.5-fullofbugs.zip]
CM9 latest nightly [cm-9-xxxxxxxx-NIGHTLY-tenderloin.zip]
CM10 latest preview [cm-10-xxxxxxxx-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM.zip]
2.3.x gapps [gapps-gb-xxxxxxxx.zip]
4.0.x gapps [gapps-ics-xxxxxxxx.zip]
4.1.x gapps [gapps-jb-xxxxxxxx.zip] MAKE SURE not to use 4.2 gapps!
(NO Android Recovery will work yet, so don't try. It will reject TWRP and CWM at least.)
- If you already have Android and/or Moboot and/or native Linux (Ubuntu, etc.) installed:
* back up any data on your media volume. webOS should back up your apps for you.
* make both a nandroid (which WON'T work to restore in a multiboot config, but if you go back to single boot, it will be fine) and a Titanium backup [which should be portable to the same OS.]
* run ACMEUninstaller and then run SmackMe-Installer.
* if you have native Linux, backup your /etc and /home (I recommend the lovely GNU tar and gzip/bzip2). That should be the majority of what to keep.
* ALSO uninstall any native Linux you may be using after you back it up.
* lastly unzip and novacom boot the SmackMe-Installer.
If you don't already have Android, MoBoot OR native Linux, just:
* back up any data on your media volume. webOS should back up your apps for you.
* then unzip and novacom boot the SmackMe-Installer.
youtube demo:
http://www.youtube.com/watch?v=8Hhy20lzhR4&feature=youtu.be
File should be attached. Report bugs by PM'ing me, or posting in this thread

Can i remove webos with this multiboot? And stay only on android and ubuntu?

This is strictly an installer. I was going to write a webOS removal script. However, android doesn't have the needed binaries. That leaves me two options: make another thing like SmackMe to do it or do it under whatever version of native Ubuntu you are running. Either way, I really don't want to have to test it myself. If I need to I'll have to doctor my touchpad EVERY TIME I do it. That's a lot of doctoring and a lot of flash write wear. So the answer is basically "find me a dev that wants to remove webos too. They'll either make you one or beta test mine." Sorry man.

Amazing keep up the good work castrwilliam !

Strange request
Hey, does anyone here still have the 2011 Froyo (2.2.1) system dump for Touchpad? It wasn't CM6, just something that HP accidentally released and someone over at Rootzwiki dumped. I'm posting this here because I have no account and they'd think I'm a noob there. All the links are down to it and I want to try messing around with its files, just for kicks. Maaaaybe I can get it to boot, and add support for it to the SmackMe installer, so at least I can have *four* versions of Android on my touchpad.
http://forum.xda-developers.com/showthread.php?t=1234381
You know, 'cause I'm just that crazy.

Wow it's been hard to find it but i think this is the good dump:
http://download.digiex.net/Consoles/Tablets/HP-Touchpad-Android2.2.1-Disk-Images.zip
sources:
http://digiex.net/downloads/downloa...hpad-android-2-2-1-system-image-download.html

it's alive! (sorta)
Somebody on XDA found a link that I thought was dead. It was the mmc dump of someone who had Froyo leaked by HP onto their fire-sale Touchpad.
FAQ:
"Obviously nobody wants this. Everybody's running Jelly Bean."
That's exectly why I did it. My point is to do the most outrageous and downright unnecessary things possible with commonplace hardware.
"What doesn't work?"
Rotation, sound, wi-fi, softkeys (i.e. Home, Back, Menu, Search.)
"What does work?"
Camera (OH HAYULL YA), touchscreen, battery reading, power button, volume button (but it dosen't matter b/c sound is borked).
"I can haz Modded Froyo?!"
Not yet.
YouTube: http://www.youtube.com/watch?v=zX29IcTIB14

Hah awesome work, I think you hold the record of most different OS'es on one device now! It looks quite functional already.
Oh and about the "Obviously nobody wants this. Everybody's running Jelly Bean." quote, I only run WebOS and your Ubuntu 12.10 port on the TP!

As soon as I get my power button sorted out I am on this!
Sent from my slim_tenderloin using xda app-developers app

Hey everyone! Froyo here!
I've just zipped up my Froyo kang such that it will work if flashed from SmackMe, and if you're crazy enough to run it alone, hopefully also Android recovery.
sound works!!
The Wi-Fi works now BUT YOU NEED A STATIC IP ADDRESS. (problems with dhcpcd)
The buttons are hacked to work (by my new shell script: /system/bin/buttond, check it out) as follows:
Volume Down is Back
Volume Up is Menu
Center is Home.
Obviously once the audio works (if ever) that will be an issue. My embarrassing secret (at least probably to the devs here) is that I don't know Java. That makes it difficult to mod on any touchscreen buttons...
The real audio library is /system/lib/libaudioflinger.real.so and the stub one (default via a symlink) is /system/lib/audioflinger.so. Using the real one causes bootloops.
Auto rotation still won't function.
Google Apps and even Facebook are included in this ROM. (It's not CM6.) So are some potentially geeky Qualcomm apps.
Don't set up your Google Account during first boot, because it will ask you to slide the keyboard open. That sounds pretty impossible onn this device. Set it up from Settings later, and you shouldn't have that issue.
UPDATED due to install issues with actual Android Recovery. Redownload.
Download Initial Version (Alpha Minus-One-Point-One): https://www.dropbox.com/s/wcs2mra8aedj1hf/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip
Download Second Version (Alpha 0.2): https://www.dropbox.com/s/t1cptjj5i02epas/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.2-incl-gapps.zip

^^^
I wanted to try froyo soo bad when I heard about those dumps last year (I think) lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?

jacobas92 said:
^^^
I wanted to try this soo bad when I heard about it last year lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
Click to expand...
Click to collapse
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.

castrwilliam said:
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
Click to expand...
Click to collapse
Ok, thanks!

Super-root vs Root

I want to start a thread cuz I think it's confusing to "only root" your device. (I personally hate Unix based system btw, the way they handle processes in intelligent multi thread way unlike windows which concentrates on one process based on its priority, Mac otherwise work on dm ready structure)
In Android and WINDOWS, SELinux there is LSM (AKA SYSTEM) (also Sudo) which is root (system user). System user > Admin user > Basic user > Quest user as well as root (kernel service) > index root > service root > service user > low level services.
Root. In order to become true root not only system user you need usually to flash custom recovery. But this way it's possible to become fake device Super-root to obtain the 0-index kernel service permissions Linux distro is needed to be installed.
Super root is a startup service such as stock recovery. In order to become true Super-root you need to perform rooting actions such as flashing TWRP or CMS. The custom recovery however won't backup kerning-based oses.
Hyperoot would be network (shell) service
And meta-root would be hardware engineering service. This is f. e. Use modified processor of the microntec car head unit with IC service in order to be able to use sound card different way.
So these are different levels of managing and servicing the devices. Then the root and Jailbreak (of Android phone too even if it's open source project) is clearly the different things
Servicing the phone (also cracking but it's rather bad thing)
1. Unlock phone (bootloader)
2. Customise system (custom recovery)
3. Root/system user
4. Obtain all partitions
5. Flash modules (not only software of internal card)
6. Assembler hacks and kerning, overclocking, adding ram etc.
Mtc 916
Hacking the phone
Will be 1, 2, 3, 4 and 5
Google Nexus, Hackintoah
Rooting (full root) the phone
Will be 1, 2, 3
Most devices
Hardness: Huawei > Manta > Nokia > sony > Acer > Asus > lg > one plus > google
Debunk phone
Will be 2, 3
Some Acer decices like s1
Simple root of a phone 3 only
Lyf flame and exotic phones from mgsm
Jailbreaking the phone
2* (apply customisation, become superuser)
Some unnown models and IPhone of course
Tweaking the phone
1 and 2*
Symbian devices, custom bloatware
What do you think, let's talk ;D
BTW As I have a lot of knowledge of computing, scripts and C in Microsoft visual I always have been soft hardware bricking my devices cuz I am dull and can't think abstractive math lab way xd
DEMANDS
Give us the hacking guide rather with rw FIXES! I don't want to spend hours typing stuff into twrp or cmc recovery (AdAway, magisk and so on)
Edit as of 19.3.19
Aroma device - is unlocked and extended device
Types of bricks:
Softbrick - "nice bootloop", simple flash from twrp or pulling system.img is enough usually
Modbrick - OTA bootloop, may require mod tool like flash tool
Hardbrick - QUSB - lack of fastboot, EMMC CMOS controller related problems, needs patents to retrieve, so its basically dead phone (when no boot at all and no signs of life, device is called "dead-boot" or "no screen device")
BAnD (Broken Android Device) is term describing hardware related problems with phone. Its not as serious as hardbrick.

Same thing :/

Potato. :good:

KlarkDevlin said:
Does root go to a new level?
Click to expand...
Click to collapse
YES
Actually smartphones are more complex than desktop pc and the trends such as Meizu Zero are begin to happen.... In the past we have had writeable system, now even the root is restricted. Until this I had always been using one click root tools, nowadays I need to spend often weeks to gain FULL administration rights to my devices (including but not limiting only to TA Backup, booting custom recovery to backup all partitions, flashing prepatched rom (along with kernel - the root of root), gapps, magisk, xposed). And it somehow hardbrick itself without reason (smartphone is working, but after one month it simply wont boot). These drms are so stupid, these companies should learn from Windows.
One of better brands: Google, Oneplus
More likely to be broken but easier to root: LG
Avoid these brands: Samsung, Verizon, Apple, Xiaomi (bad hardware I quess, but good performance)
Preferred type of rom: stock vanilla without bloatware, AOSP ones (not AOKP due to problems with ogyoutube).
!!!
The new trend by developers that occurs lately is freakin annoying, every Rom should come prerooted using universal method (magisk) and the rest should be hosted on github (clean Rom and super su Rom, Eventually tool like pfr creator). The rooting is harder than NASA microkernels oses really due to the varying versions.
!!!
BTW this is proposition by me of perfect microcomputer
(micromobile)
Other

Magisk MultiROM Support

https://forum.xda-developers.com/showpost.php?p=69226527&postcount=6
Was this ever fully achieved? Fully systemlesz MultiROM support / module support with Magisk? I have always wanted to see the day that TWRP got a bit of a work over and addition of the possibility of a flashable addon for MultiROM support for what phones that would be supported. I brought this up to my team and also the OrangeFox and a few other groups hoping it might become something. But im getting OT here.. so lets -> back to Magisk chatter.
Any info would be greatly appreciated. Usually i do my fair share of extensive research before asking such but lately I have been overworked and haven't the time to pour over pages and pages as usual.
Thanks!

I've done tons of reading, can't seem to find the answer to this question either
Maybe @topjohnwu can chime in here...

noidodroid said:
https://forum.xda-developers.com/showpost.php?p=69226527&postcount=6
Was this ever fully achieved? Fully systemlesz MultiROM support / module support with Magisk? I have always wanted to see the day that TWRP got a bit of a work over and addition of the possibility of a flashable addon for MultiROM support for what phones that would be supported. I brought this up to my team and also the OrangeFox and a few other groups hoping it might become something. But im getting OT here.. so lets -> back to Magisk chatter.
Any info would be greatly appreciated. Usually i do my fair share of extensive research before asking such but lately I have been overworked and haven't the time to pour over pages and pages as usual.
Thanks!
Click to expand...
Click to collapse
Hey Buddy, Long time no see... Since the android forums days i guess it was.
I ended up here because i was searching to see if there was perhaps a magisk module to enable this as a test feature? or if there was a bit better documentation on how this would work...
My team and I have been deving for some alcatel mtk devices, and we are searching for info to either add multi/dual boot functions to our personal recovery builds, or find or build some other sort of solution.
I actually stumbled right to here.
So say, @topjohnwu would you happen to be able to drop any of us a plug-in module or a quick how to for those of us who ARE GOING TO KILL DEVICES ANYWAY playing with this stuff?
I'd definitely beta test any of that, @topjohnwu I was taking apart your Magisk and reversing/modding parts of it to accomplish some dificult things in one of my devices and wanted to compliment your clean style in your scripts.
I was thinking to my self that day though ,
"Could I change some things to make an option to switch between several GSI system.img stored on sdcard thats partially formatted ext4... and perhaps have it ask me which slot.." When thinking about it, if I make several 4-5 GB ext4 partitions on my sdcard I should be able to write a system.img to each of those partitions, then have magisk take a user selection and boot the system from that partition....{speaking about an arm a-only device}
it would become more difficult with system-as-root though wouldn't it? I'd think it would be possible to do some sort of fstab muckery where the script looks for these partitions, u choose 1, it sets a variable, and restarts the boot process with that VAR set to boot the system on chosen partition....
IDK I bet Mr John WU probably has it already worked out but these are just a few of the things we are messing with over at my support/development group on Telegram..
https://t.me/Android_General_Chat

LgPWN'd said:
Hey Buddy, Long time no see... Since the android forums days i guess it was.
I ended up here because i was searching to see if there was perhaps a magisk module to enable this as a test feature? or if there was a bit better documentation on how this would work...
My team and I have been deving for some alcatel mtk devices, and we are searching for info to either add multi/dual boot functions to our personal recovery builds, or find or build some other sort of solution.
I actually stumbled right to here.
So say, @topjohnwu would you happen to be able to drop any of us a plug-in module or a quick how to for those of us who ARE GOING TO KILL DEVICES ANYWAY playing with this stuff?
I'd definitely beta test any of that, @topjohnwu I was taking apart your Magisk and reversing/modding parts of it to accomplish some dificult things in one of my devices and wanted to compliment your clean style in your scripts.
I was thinking to my self that day though ,
"Could I change some things to make an option to switch between several GSI system.img stored on sdcard thats partially formatted ext4... and perhaps have it ask me which slot.." When thinking about it, if I make several 4-5 GB ext4 partitions on my sdcard I should be able to write a system.img to each of those partitions, then have magisk take a user selection and boot the system from that partition....{speaking about an arm a-only device}
it would become more difficult with system-as-root though wouldn't it? I'd think it would be possible to do some sort of fstab muckery where the script looks for these partitions, u choose 1, it sets a variable, and restarts the boot process with that VAR set to boot the system on chosen partition....
IDK I bet Mr John WU probably has it already worked out but these are just a few of the things we are messing with over at my support/development group on Telegram..
https://t.me/Android_General_Chat
Click to expand...
Click to collapse
Very good write up on Tue thoughts of how one could achieve what we have in thought at this moment. I have similar thoughts but haven't taken them very deep as most know I'm back And fourth between handsets and ideas. Good work. Perhaps the top hat Mr John wu can elaborate a bit more on this subject matter.

Have you solved the problem?
Teach me please

SupraLance said:
I've done tons of reading, can't seem to find the answer to this question either
Maybe @topjohnwu can chime in here...
Click to expand...
Click to collapse
Perhaps he can. When we get around to building recoveries for the Schokk Turbo and Schokk Turbo XL along with more solid verions for the Orbic Wonder and Orbic Slim I want to get the team working on a custom verison or plugin. That and or EFI Droid which is might interesting... Here check it out - https://efidroid.org/ - https://forum.xda-developers.com/android/general/poll-recovery-t3942781 .
Btw are you a sys admin? I know a Lance that was a SYS Admin for a local ISP. I'm a stones throw away from your county.

Any solutions ever become of this idea? Curious to know.

noidodroid said:
Any solutions ever become of this idea? Curious to know.
Click to expand...
Click to collapse
Bump