Related
I use a backup from TWRP because I flash different ROMs.
But when I restore my backup the Hands Free Activation screen always bothers me on first boot.
How to delete it from TWRP terminal, what is the specific app causing it to remove it?
anees02 said:
I use a backup from TWRP because I flash different ROMs.
But when I restore my backup the Hands Free Activation screen always bothers me on first boot.
How to delete it from TWRP terminal, what is the specific app causing it to remove it?
Click to expand...
Click to collapse
Flash this zip file in twrp recovery and get rid of that annoying activation.
https://www.androidfilehost.com/?fid=24665509702140432
If you don't want that activation thing pop up at notification follow this
Open root explorer
Go to system/private app
Look for folder ( sprint dm )
Open folder you will see sprint dm.apk
Rename it to ( sprint dm.bak )
Save&exit
Reboot device
You will nevet get that activation thing again unless you flash another rom.
anees02 said:
I use a backup from TWRP because I flash different ROMs.
But when I restore my backup the Hands Free Activation screen always bothers me on first boot.
How to delete it from TWRP terminal, what is the specific app causing it to remove it?
Click to expand...
Click to collapse
Rename /system/priv-app/SprintSyncMLSvc.apk
to /system/priv-app/SprintSyncMLSvc.bk
I restored my backup after wipe factory default and saw this HFA then I restarted to twrp recovery and removed the 2 ,SprintDM & SprintSyncMLSvc but when I restarted I saw HFA again.
I don't know what happened maybe the rm - rf command from recovery didn't execute.
EFIDroid
A UEFI based Android bootloader.
EFIDroid provides an easy Installer, good looking Material Design user interfaces and uses very dynamic code.
Homepage: efidroid.org
Take over control before loading the Operating system.
EFIDroid attempts to make it easy for both users and developers to control their boot experience.
Multiboot
Install and boot any number of operating systems and recovery tools.
Boot plugins
Change the boot behavior without modifying ROM's. Swapping internal/external memory, overclocking or modifying the ramdisk. Live and without any permanent modifications.
UEFI Apps
EFIDroid uses UEFI in the background which means that you can boot other bootloaders like GRUB or rEFInd and even small games
Download
see Installation section
Requirements
The main OS (that one you currently use) must be rooted to use the efidroid app.
You may be able to install magisk later in a secondary ROM (never tried it though)
Hint:
lineageos root add-on works (tested on LOS 15.1) and magisk will NOT work. Use supersu.
TWRP / FlashFire installable ZIP:
Stable: supersu-stable
Beta: supersu-beta
Latest: supersu
At the moment the only TWRP which is working for efidroid is: twrp-3.1.1 - any newer TWRP release will fail with a ramdisk size error which is not due to a missing kernel patch. It's a known issue for efidroid and one of the reasons for the efidroid rewrite
I maybe find a workaround to get newer TWRP versions installed.. we will see..
So if you have a newer version of TWRP installed currently: upgrade/downgrade to that version first.
Installation
A full howto with screenshots can be found here
Unlock your device! This will NOT work with a locked bootloader (you know about UsU?)
Download the EFIDroid Manager from Google Play Store - Has been removed..
Efidroid manager download: main efidroid thread
Download the latest version by opening the "Downloads" tab of this thread (requires to open this thread in a browser)
Activate my efidroid OTA server:
Option 1 (permanent): modify /system/build.prop
Boot to TWRP
Make a backup (including system partition)!
Mount System partition in TWRP
enable the efidroid OTA server:
Code:
adb shell
echo "efidroid.server_url=https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master" >> /system/build.prop
reboot
verify that the efidroid server URL has been set properly:
Code:
adb shell getprop efidroid.server_url
Option 2 (will be lost on reboot): using setprop
Set the efidroid OTA server:
Code:
adb shell
setprop efidroid.server_url https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master
verify that the efidroid server URL has been set properly:
Code:
adb shell getprop efidroid.server_url
Open EFIDroid Manager
HINT: If you see an error like "cannot load device info, please check your connection : no value for lge/H815" then the above OTA url has not been set or is set wrong.
Go to Install/Update
Click Install --> HINT: THIS WILL MOVE YOUR BOOT AND RECOVERY PARTITION CONTENT
This means
1. from now on EFIDroid will boot each time u power on the device.
2. the recovery partition gets backed up and you will see it in EFIDroid again as (if TWRP): TWRP (internal).
3. you can still boot your main ROM by just choosing it from the list --> your ROM name - (internal)
If you don't like this you can install EFIDroid to either: recovery or boot partition only. But this is a manual process and when you upgrade with EFIDroid Manager it may overwrite your changes.
Install a custom ROM
A full howto with screenshots can be found here
Open EFIDroid Manager
Open the menu "Operating Systems" and click the FAB (Floating Action Button) at the bottom
Choose in the screen /data/media/0/multiboot as location.
Enter a name for the ROM
Optional: Choose another icon for the ROM
You can leave the partitions as they are (Schema LoopSystem + BindOther) Press the tab "PARTITIONS" and choose "LoopAll". You will see that the data partition is quite big (the g4 internal storage is just 23 GB so you choose a smaller size for each ROM to fit all your ROM slots).
Tip "data" and select GB in the drop down. Choose a proper size (i.e. 2 GB) depending on what you wanna do with that ROM and how many you wanna install (each ROM will take 4 GB for system + the data size you choose here)
In the tab "REPLACEMENTS" click the floating plus button and add a new cmdline override:
Code:
Name = androidboot.selinux
Value = permissive
press the tick in the top right corner to finish the setup
Now you can see your newly created ROM slot in the list
Reboot
Once you are in the efidroid, you can navigate around with volume down to go down, volume up to go up and the power button to confirm your selection.
To flash a ROM to the new empty slot, select TWRP (Internal) , press power and select the slot name with power again
At the moment the system partition is just empty and needs to be formatted before you can use it!
In TWRP:
select WIPE -> Advanced Wipe -> select "system" and "cache", then swipe to wipe.
select WIPE -> "Format Data" button
Reboot -> System. When you see efidroid again choose TWRP and select the new ROM slot again to boot TWRP again.
Install your ROM of your choice.
Hint: If you get an error regarding device detection you have to remove the assert line(s) within the ROM zip first
Supported devices
Any LG G4 model which can be unlocked (yea even UsU ones but that still requires some more work to detect them properly)
Known Issues
The Operating System list in the EFIDroid Manager is empty just upgrade to the latest EFIDroid manager app..
after installing a ROM it may bootloop under some circumstances
AROMA installer flickers extremely. Workaround: press power to turn off screen then turn it on again. It still flickers but u can see and use the installer at least.
As we need to use TWRP 3.1.1 (see requirements) UsU devices get not detected correctly!
The state of this project is ALPHA so expect issues and even data loss is possible (so do a TWRP backup often)
Booting a secondary ROM and working in a secondary ROM may feel slower (that's by design)
if a ROM has set selinux to enforcing it will not boot! --> If you setup the ROM slot properly (see above REPLACEMENTS tab) you do not need to care about.
Without that adjustment in the efidroid manager you have to modify the boot.img of every ROM:
change the cmdline from
androidboot.selinux=enforcing
to
androidboot.selinux=permissive
I started a while ago to make selinux policies for efidroid but it's not that easy and so atm no ROM which has selinux set to enforcing will boot.
Credits
@m11kkaa for EFIDroid
@J0SH1X for bringing a first port for the G4
@steadfasterX for being steadfast and optimizing efidroid
XDA:DevDB Information
EFIDroid for the LG G4, Tool/Utility for the LG G4
Contributors
steadfasterX, @m11kkaa, @J0SH1X
Source Code: https://github.com/steadfasterX/efidroid_device_lge_g4
Version Information
Status: Alpha
Created 2017-04-14
Last Updated 2018-12-17
Workarounds for known issues
1) random app crashes, settings do not persist on reboot
The reason is that file permissions get not set correctly on the bind mounted data partition.
So nothing can be stored there (or what get stored will be stored with the wrong perms).
When creating a new ROM slot it is important (atm) that you choose LoopAll .
This would create a data partition image with 23 GB which is way too much so you need to touch the data partition in the partitions tab and set the size to GB and choose e.g. 2 GB.
2) no WiFi
First boot TWRP internal / primary slot
Code:
adb shell cp /data/misc/wifi/config /external_sd/data_misc_wifi_config
Then for each slot you created you must reboot TWRP in its slot and:
Code:
adb shell cp /external_sd/data_misc_wifi_config /data/misc/wifi/config
adb shell chown system.wifi /data/misc/wifi/config
adb shell chattr +i /data/misc/wifi/config
Reserved
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
jokuu said:
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
Click to expand...
Click to collapse
Oh damn. I forgot to update the OTA for the other devices..
There is nothing you can do on your site atm.. Sorry I will fix it asap and let you know..
.
Sent from my LG-H815 using XDA Labs
still hard at it heck yea
jokuu said:
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
Click to expand...
Click to collapse
ok done. please try again
.
steadfasterX said:
ok done. please try again
.
Click to expand...
Click to collapse
Now it works. Thank you! :good:
ok .. im able to boot a LL based ROM now (Imperium ROM).. but only ONCE. lol..
Well I can boot into it again after booting in the TWRP version of that ROM and doing a factory reset from within TWRP...
Cleaning /data, /cache and dalvik cache manually does NOT work.. interesting. <-- I tested with a special (FIsH) TWRP version which does not WIPE but RM only.. Once I switched to a regular TWRP it is still strange but at least behaves the same now: When I wipe /data and /cache I can boot (but only when wiping both).
Update:
Keeping strange:
When I wipe /data only -> no boot
When I wipe /cache only -> no boot
When I wipe both -> boot ok .. wtf.?!
I will look into /misc - maybe the reason can be found here!
.
I just booted a second rom successfully using efi on my h811
My primary rom: lineage nougat
My secondary rom: resurrection remix (mm)
First boot was slow, second a little less slow, third and so on boot at normal speed.
Anyone else with an h811 care to try it coz @steadfasterX thinks mine booted coz i have an h811.
So if anyone else with an h811 can test it, that would help.
Btw, you all jelly? :victory:
Update: i have a complex sort of bootloop.
I decided to flash gapps.
Now when i try to boot the rom, i get the optimizing apps screen, then starting apps, then the boot logo, then again starting apps, and again boot logo and it goes on like that.
If i clear cache and dalvik i get the optimizing apps again, then the circle continues.
Maybe its gapps?
Or maybe its coz you all were too much jelly
tanveer7652 said:
Update: i have a complex sort of bootloop.
I decided to flash gapps.
Now when i try to boot the rom, i get the optimizing apps screen, then starting apps, then the boot logo, then again starting apps, and again boot logo and it goes on like that.
If i clear cache and dalvik i get the optimizing apps again, then the circle continues.
Maybe its gapps?
Or maybe its coz you all were too much jelly
Click to expand...
Click to collapse
heat
kevp75 said:
heat
Click to expand...
Click to collapse
Heat? What do you mean
tanveer7652 said:
Heat? What do you mean
Click to expand...
Click to collapse
I believe he thinks you have the ilapo because he don't know what efidroid is.
have you tried to wipe /data as mentioned (on IRC) ?
.
tanveer7652 said:
Heat? What do you mean
Click to expand...
Click to collapse
steadfasterX said:
I believe he thinks you have the ilapo because he don't know what efidroid is.
have you tried to wipe /data as mentioned (on IRC) ?
.
Click to expand...
Click to collapse
LOL I have a good idea with efidroid is
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
J0SH1X said:
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
Click to expand...
Click to collapse
Congrats. Please remember some of us poor guys when u buy another g4 ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
kevp75 said:
LOL I have a good idea with efidroid is
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
Click to expand...
Click to collapse
But it doesn't get hot.
kevp75 said:
LOL I have a good idea with efidroid is
Click to expand...
Click to collapse
oh that's good
kevp75 said:
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
Click to expand...
Click to collapse
tbh I don't think that this is the case here. We have bootloops when something changes in /data. This is not heat related. It is something efidroid related..
J0SH1X said:
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
Click to expand...
Click to collapse
u like pain do u ?
steadfasterX said:
oh that's good
tbh I don't think that this is the case here. We have bootloops when something changes in /data. This is not heat related. It is something efidroid related..
Click to expand...
Click to collapse
theres software bootloop and hardware bootloop. i only get software when i install something or say remove gapps. or mess with system . flashing rom fix it..
So, grabbed the latest OTA, and went through the usual re-root cycle, but was unable to edit the build.prop. While /root is mountable, /root/system is not, which means no tethering for me.
Anyone else running into the same issue?
I have the same issue, I've been fighting with it all day.
I patched the boot.img with Magisk Manager and flashed it, Magisk Manager show's I'm installed and Root Checker says I'm rooted, I was even able to install Adaway. But i cannot use any root app that needs to mount /System
I tried using Root Uninstaller and it says it has root access but cannot mount /system as R/W
It seems Magisk is only able to partially root on Android 10
I tried this with the Canary version and the standard version of Magisk and the same issue both times
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
bbarnes1 said:
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
Click to expand...
Click to collapse
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
This has been a problem since the Q beta came out, with each update I tried to figure something out. With no luck! I tried the Magisk Mod but it didn't seem to work.
suggestions would be most appreciated!!
Thinkin about a clean install....maybe.....
Edit: It was also a problem with the P beta until it was out of beta (That was my hope for this)
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....
Click to expand...
Click to collapse
I'm trying to add a prop, which seems like a different need, but will look into it.
tufyuma said:
Thinkin about a clean install....maybe.....
Click to expand...
Click to collapse
Was thinking about this, but realized a clean install for every update isn't worth a hotspot to me.
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
I gave this a whirl, its doesn't appear to actually be change build.prop
bbarnes1 said:
I gave this a whirl, its doesn't appear to actually be change build.prop
Click to expand...
Click to collapse
It doesn't physically change anything in system. The intent is to offer the same functionality as physically editing the build.prop without modifying that file. It creates the prop and value setting and loads into into memory at boot time.....(similar to the way the build.prop file is read at boot time for those settings.) At least that is my understanding. It works for me on Android 9 for setting the prop for tethering...for example. You can confirm it works by using the getprop command to verify the prop you set is set as you intended.
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
somethingsomethingroot said:
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
Click to expand...
Click to collapse
Can you tell me what the process is that got you tethering capability?
Having the same issue on my P2XL which was upgraded via flash of full image minus -w. Using latest canary build of Magisk. I couldn't mount system or anything under it.
I then downgraded Magisk to v19.3 and had no issues mounting system using FX File Explorer, etc. and still had root. But I couldn't mount anything under system so I still can't edit build.prop.
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
Thanks for posting this, it worked great on my Pixel XL on Sprint. I had about given up on being able to edit the build.prop.
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Your prop
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Are you sure that your screenshot of the props output is correct? Because it looks like you have the value set to "net.tethering.noprovisioning" and the prop name has =true in it. I'm just trying to figure this out because I've tried this and everything else trying to get my hotspot to work. My hotspot will turn on and devices can connect to it, but they don't have internet access. Any ideas at all?
Edit: Nevermind, I had the custom prop set to post fs data when it was supposed to be set at boot stage (default). My hotspot is working now. Thank you all.
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Confirming that this works on rooted pixel 4. Thank you for this btw
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
This seems to have worked for me, though I don't really understand why or what did it.
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
wolvmarine said:
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
Click to expand...
Click to collapse
Why need to turn on Hotspot for build.Prop editing? What's wamo?
truelies1 said:
Why need to turn on Hotspot for build.Prop editing? What's wamo?
Click to expand...
Click to collapse
Does anyone know a way to enable gestures on 3rd party launchers on stock rom
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2239421
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3xl.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3xlRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Looking forward to this, Tulsa. Will be a real lifesaver and game changer.
sliding_billy said:
Looking forward to this, Tulsa. Will be a real lifesaver and game changer.
Click to expand...
Click to collapse
It's official. It works.
Tulsadiver said:
It's official. It works.
Click to expand...
Click to collapse
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.
sliding_billy said:
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.
Click to expand...
Click to collapse
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time
Tulsadiver said:
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time
Click to expand...
Click to collapse
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.
sliding_billy said:
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.
Click to expand...
Click to collapse
I pasted it again. Hopefully it works now.
Tulsadiver said:
I pasted it again. Hopefully it works now.
Click to expand...
Click to collapse
It works!
Thank you!!!!
Latest magisk canary added an adb command to remove modules if bootlopps happens ?
DvLAx3l said:
Latest magisk canary added an adb command to remove modules if bootlopps happens
Click to expand...
Click to collapse
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?
Tulsadiver said:
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?
Click to expand...
Click to collapse
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know ?
DvLAx3l said:
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know
Click to expand...
Click to collapse
Well, if it's an ADB fix, a person is going to have to, at the very least, flash boot.img (though probably system images depending on what you flashed), reboot without root. Enable the ADB mode, flash ADB commands, and reboot. Remove bad modules. Then, go back and root again.
Seems simpler to just flash the modded image-new.img, reboot with root, remove modules (with ADB if you like) and reboot.
Edit: what would be cool is an option to patch a boot.img in core-only mode, right from Magisk manager, where the other option is to patch the boot.img. All that would be needed on John's part is an edited init file in that option. That's the only difference.
Thanks for this! I could've really used this image a few times in the past...
Face_Plant said:
Thanks for this! I could've really used this image a few times in the past...
Click to expand...
Click to collapse
You and me both, buddy!
Got in to a bootloop situation with Bromite systemless webview module. I restored stock boot image and patched it with the latest canary build (the one with 'recovery mode' checked under advanced settings) and bootlooped again. I flashed this file, got in with magisk working, disabled the offending module, patched the boot image without recovery mode, then flashed the patched boot image and everything is up and running! Thanks for the help!
Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?
Jiggs82 said:
Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?
Click to expand...
Click to collapse
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.
Tulsadiver said:
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.
Click to expand...
Click to collapse
Yes I was able to open magisk but even if I uninstalled it I still had this weird bootlloop so before I saw this message I ended up just flashing factory 10 image clean this time just to be sure everything would flash/install successfully and luckily they did lol but thanks anyways and I will hold onto to these files for future references:good:
would the modded boot img that disables modules work for the pixel 3 as well?
I am not responsible for anything that may occur.
Most of the GSI's need SELinux Permissive status. This cannot happen with boot.img because of Vendor. So we have to use Magisk to make Permissive. This is for old GSI's. If you are gonna use new GSI's from Erfan and Phhusson check the end of the thread.
1- You need a working GSI installed(HavocOS works). https://sourceforge.net/projects/havoc-os/files/arm64-aonly/
2- You need to install Magisk. I installed v19.3.
3- You need TWRP recovery. I use 3.3.0. And make sure you disabled your data encyrption.
4- You need a Permissiver. With Magisk SELinux Manager module we are patching SELinux systemlessly.
*After installing Magisk reboot. Then add this module in Magisk Manager and reboot(Follow steps on guide. Volume up to confirm, after volume down to select permissive). https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042 You don't need latest. Just download 1.0 from Attached Files. I used that.
* Go to about on your settings. You should see in bottom permissive status. If you see enforcing go back and fix what you have done wrong. After making permissive go to TWRP recovery. In recovery make sure data is mounted in Mount. Then go to Advanced > File Manager. In there open data folder and delete everything other than adb, app, media. Then go to app folder and delete everything other than com.topjohnwu.magiskxxx.
* Now you should only have adb, app/com.topjohnwu.magisk(xxx), media. Exit from File Manager and go to Backup. Choose only Data. Then swipe to backup. Backup stored in /sdcard/TWRP, /data/media/0/twrp. That's why we didn't delete media folder. And don't ever wipe Internal storage(Your backup in there.).
5- But you can wipe data and that excludes backup. So wipe Dalv, system, data and cache. And then in Restore your backup and you should get your Magisk and Modules back(You can see adb and app folder by remounting).
6- Flash any GSI you want. If you want to install GApps stock version go to mount and uncheck Mount system partition read-only and tick system on the top. Go to Wipe> Advanced Wipe> Check system> Repair or Change File system> Resize File System> Swipe to resize. This will make your space 3600mb again. Your system files will not be touch. Now you can install gApps zip.
Working OxygenOS: https://drive.google.com/open?id=1GPGWJu3lUeheUO2iGSNHQWEPiYgeF3DY
LINKS to GSI's: https://docs.google.com/document/d/123s7H37wHKqlxn8rIBQmG_DvffgTVZv3hO-uiy7N-sk/edit?usp=sharing
Some Files if needed = https://drive.google.com/drive/folders/1yFJl-teTlbSWilgJIgN317Ba2FFVRSaO?usp=sharing
Tested on Version V16.0615.1908.109.
As of today, Android Q/10 is working. https://github.com/phhusson/treble_experimentations/releases
Wipe dalv, system, data, cache. Flash img, then flash Magisk-phh.zip.
For Erfan:
Since 25.09.2019, all new ErfanGSI's will work on our devices. Check the date. It should be newer than 20190925. No need to flash Permissiver or Zygote fix.
You need to flash stock boot.img. Mount vendor and delete /vendor/overlay in Advanced > File Manager to fix Pixel Launcher crash. If you want to backup vendor.img follow this guide.
Telegram Channel:https://t.me/Zenfone5GSI
In Turkish Language: https://docs.google.com/file/d/1GKlOl68vOngXAMfvj9rV6YZ9Wq8AC4JG7m7AdIf6i74/view
Thank you very nice work in the telegram group, I would appreciate it if you help us
LifefesTR said:
Thank you very nice work in the telegram group, I would appreciate it if you help us
Click to expand...
Click to collapse
What help do u need? Contact me from telegram and I will try to help.
emincangencer said:
What help do u need? Contact me from telegram and I will try to help.
Click to expand...
Click to collapse
I've done the way step by step ... but when I install Evolution Erfan GSI still not boot..When I see the file manager in Twrp..Is open the data ..like ADB, Media, app is the lost.. I restore again ... still not boot... I again see in twrp...file manager,,data/app,media,adb is lost again..Why?? Is there anything wrong ?
albarudin said:
I've done the way step by step ... but when I install Evolution Erfan GSI still not boot..When I see the file manager in Twrp..Is open the data ..like ADB, Media, app is the lost.. I restore again ... still not boot... I again see in twrp...file manager,,data/app,media,adb is lost again..Why?? Is there anything wrong ?
Click to expand...
Click to collapse
In twrp "adb push C:\Users\Emincan\.android\adbkey.pub /data/misc/adb/adb_keys". Reboot. In bootanimation "adb shell getenforce". If answer is permissive, it should work. If it's enforce, you have done something wrong.
I have done this on Vendor Version V16.0615.1908.109. Maybe that's affecting.
And make sure you are doing it with https://sourceforge.net/projects/evolution-x/files/GSI/Evolution-9.0-GSI-ARM64-AONLY-20190811.zip/download
emincangencer said:
In twrp "adb push C:\Users\Emincan\.android\adbkey.pub /data/misc/adb/adb_keys". Reboot. In bootanimation "adb shell getenforce". If answer is permissive, it should work. If it's enforce, you have done something wrong.
I have done this on Vendor Version V16.0615.1908.109. Maybe that's affecting.
And make sure you are doing it with https://sourceforge.net/projects/evolution-x/files/GSI/Evolution-9.0-GSI-ARM64-AONLY-20190811.zip/download
Click to expand...
Click to collapse
ok sir...thanx you
sir...please help me,how the fix dt2w in the rom gsi
link for image oxygen os please on google drive link error
phentem said:
link for image oxygen os please on google drive link error
Click to expand...
Click to collapse
I deleted them because it's outdated. U can find it on https://t.me/VegaGSIs