Related
So I have spent a bit of time testing out project treble roms, cant get any to boot unfortunately. It might be a twrp thing who at this point knows?
Hopefully some Roms & possibly kernels will pop up In the coming weeks or months
Was worth a try, if anyone has had success with GSI's and getting them to boot, please share your method......:good:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Successfully flashed ......just transitional animation bug, brightness can't be adjusted....but it's not dim....Pixel Experience Rom.
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Thanks to you both for your testing on GSI roms.
If you report the bugs with logcat to phh telegram group i suppose he will fix it for sure.
NisseGurra said:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Click to expand...
Click to collapse
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
uvitor said:
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
Click to expand...
Click to collapse
Yes, s10X uses a/b gsi's
NisseGurra said:
Yes, s10X uses a/b gsi's
Click to expand...
Click to collapse
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
uvitor said:
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
Click to expand...
Click to collapse
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Duncan1982 said:
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Click to expand...
Click to collapse
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
thebigtross said:
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
Click to expand...
Click to collapse
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
sir-harlekin said:
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
Click to expand...
Click to collapse
+1, i don't think it can be fixed by build.prop.
NisseGurra said:
+1, i don't think it can be fixed by build.prop.
Click to expand...
Click to collapse
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
thebigtross said:
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
Click to expand...
Click to collapse
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Twrp is root, so if you reboot by the method you should be aware of then you'll be booted into a rooted system :good:
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Flash magisk ou supersu from twrp as usally.
Not the patched or prepatched provided file lol.
Else some aosp roms are prerooted with supersu. They are tagged *-su* in filename
NisseGurra said:
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Click to expand...
Click to collapse
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
vonDubenshire said:
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
Click to expand...
Click to collapse
No, all us snapdragons have locked bootloaders, no root.
In the meantime, is someone running GSI as a daily driver?
sir-harlekin said:
In the meantime, is someone running GSI as a daily driver?
Click to expand...
Click to collapse
I am. BUT there are several bugs to be addressed such:
Not working:
Bluetooh/NFC
Fingerprint
Proximity sensor
Auto brightness (manual does)
MTP
Force closes on any app info in settings
Im using because the progect is very promising and phhusson is open to user's reports so, im trying exactly to do that feedback and speed up the development.
Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Can you not uninstall/flash modules through magisk?
Levi4cyber said:
Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Click to expand...
Click to collapse
Not sure if it still works, but you should be able to go in through safe mode to delete magisk. Not sure about just modules, but it would get you out of a hole anyway.
hallo dare said:
Not sure if it still works, but you should be able to go in through safe mode to delete magisk. Not sure about just modules, but it would get you out of a hole anyway.
Click to expand...
Click to collapse
Yes, that's a really good suggestion, I was in that situation couple of days ago, force reboot to safe mode, you don't have to do anything in safe mode, then just do a normal system boot and all modules should be disabled and just uninstall them before your next reboot.
Levi4cyber said:
Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Click to expand...
Click to collapse
if you are getting bootloops and in a jam, use method 2 (adb) to remove modules, this method saved me when a module caused a BL situation, only downside is it will remove all modules.
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
oscarmaldonado said:
Yes, that's a really good suggestion, I was in that situation couple of days ago, force reboot to safe mode, you don't have to do anything in safe mode, then just do a normal system boot and all modules should be disabled and just uninstall them before your next reboot.
Click to expand...
Click to collapse
For some unknown reason my modules are still installed after reboot in save mode.
Am I doing something wrong?
netgar said:
For some unknown reason my modules are still installed after reboot in save mode.
Am I doing something wrong?
Click to expand...
Click to collapse
Hey there bud, what exactly are you trying to do, a bad module creating a boot loop in you phone?
oscarmaldonado said:
Hey there bud, what exactly are you trying to do, a bad module creating a boot loop in you phone?
Click to expand...
Click to collapse
I did before so I had to basically reinstall all my apps from scratch.
I installed bootloop saver module and I hope I will be safe once any not compatible module will cause bootloop.
I'm not safe since after reboot from save mode all my modules are still active and installed.
use this command in debugging mode enabled
Code:
adb wait-for-device shell magisk --remove-modules
Hi guys,
just updated my op9p to the newer oos 11.2.5.5LE15BA and repatched with magisk, everything gone fine.
I re-deleted some google system app with sdmaid that i had debloated yet before this oos update.
Once i re-install vanced apps i detached it using magisk module from termux, rebooted and now i'm in stuck with boot loop.
Tried to clear cache from recovery but still keep in stuck.
What can i have corrupted?
Can i solve it reflashing stk boot.img?
Thanks in advance
Hunter_87 said:
Hi guys,
just updated my op9p to the newer oos 11.2.5.5LE15BA and repatched with magisk, everything gone fine.
I re-deleted some google system app with sdmaid that i had debloated yet before this oos update.
Once i re-install vanced apps i detached it using magisk module from termux, rebooted and now i'm in stuck with boot loop.
Tried to clear cache from recovery but still keep in stuck.
What can i have corrupted?
Can i solve it reflashing stk boot.img?
Thanks in advance
Click to expand...
Click to collapse
you can try booting in safe mode, this will disable all magisk modules
Same issue tring to boot into safe mode
I just posted a tutorial to use adb to remove magisk modules for a situation just like this. worth to check it out if you can't get it done via safemode
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
there might be the same tutorial on xda but i had this copied to my clipboard
Scary that a detach module could cause bootloop...
Hunter_87 said:
Same issue tring to boot into safe mode
Click to expand...
Click to collapse
Did you able to make it work?
Nope, same result tring to follow thirtythr33 tips..
Really don't undestand what i did it wrong to get this problem.
Nothing.. i had to do an hard reset!! Thanks to all anyway..
Hunter_87 said:
Nope, same result tring to follow thirtythr33 tips..
Really don't undestand what i did it wrong to get this problem.
Click to expand...
Click to collapse
Have you removed all modules via abd?
netgar said:
Have you removed all modules via abd?
Click to expand...
Click to collapse
Nope, i tried with adb command as reported on linked guide but nothing happen and i receive just an error on cmd for too waitings.
i've been trying for 2 whole days now to install viper4android on my oneplus 9 pro, i just can't get it to install. I'm basically stuck in an install loop and i've tried almost everything (permissive, AML, clean install, v4a repackaged, android 12 fix) but none of them work.
I wonder if anyone got viper working on their device running a custom android 12 rom
Take a look:
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Hammerhand.17 said:
Take a look:
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Click to expand...
Click to collapse
tried that too and just now tried it on just stock lineage os on A11 but still no luck nstalling v4a
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Hammerhand.17 said:
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Click to expand...
Click to collapse
i did follow every step with the reboots after each module but i'm still stuck in an install loop so i cant even get to the settings unfortunately... i've never had so much trouble with a device
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
Awesome, i'll try as soon as a custom rom is up and running
Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
So install magisk, reboot, AML, reboot, JamesDSP, reboot, V4A, install drivers and let it reboot? kernel can stay in enforcing?
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Hammerhand.17 said:
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Click to expand...
Click to collapse
Got it working finally!! Could you supply me with the modification i need to make in the post fs file? So i follow you exactly? Also can i remive jamesdsp now or does it need to stay installed?
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Hammerhand.17 said:
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Click to expand...
Click to collapse
But can i remive jamesdsp from magisk or does it need to be installed in order to keep viper working? Like the moment you remove it viper just stops working?
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Hammerhand.17 said:
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Click to expand...
Click to collapse
If you uninstall it viper is once again stuck in an install loop so you do need jamesdsp to stay installed
Ok. Good to know. Will left it installed, then.
Anyone use the magisk bootloopsaver module with our phones? Wanted to make sure it wouldn't mess anything up before I installed it lol
Veid71 said:
Anyone use the magisk bootloopsaver module with our phones? Wanted to make sure it wouldn't mess anything up before I installed it lol
Click to expand...
Click to collapse
Using it on OOS11. Saved me when one of the recent Magisk Canary releases had conflicts with modules and caused bootloops, it's a Godsend.
Basically if you bootloop because of modules, the boot animation stays on for like a minute, then the device restarts with all modules disabled (except for the Magisk Bootloop Saver module). You will need to re-enable them manually afterwards (and subsequently rebuild substratum themes etc).
Fishawy said:
Using it on OOS11. Saved me when one of the recent Magisk Canary releases had conflicts with modules and caused bootloops, it's a Godsend.
Basically if you bootloop because of modules, the boot animation stays on for like a minute, then the device restarts with all modules disabled (except for the Magisk Bootloop Saver module). You will need to re-enable them manually afterwards (and subsequently rebuild substratum themes etc).
Click to expand...
Click to collapse
Awesome thanks man!
Magisk has this by default for a long time now. pressing down vol key on boot will boot into safe mode with all modules disabled
Try this.
JohnFawkes said:
Magisk has this by default for a long time now. pressing down vol key on boot will boot into safe mode with all modules disabled
Click to expand...
Click to collapse
True, but this module makes it a normal boot not into safe mode.
TheKnux said:
Try this.
Click to expand...
Click to collapse
Will it work on a12l?
Tazist said:
Will it work on A12l?
Click to expand...
Click to collapse
@Tazist Try it. Sorry, the xda app is ****ing stupid.
Does anyone have a fresh copy of this? I keep getting an unzip error. Is development dead?
Droid_Nut said:
Does anyone have a fresh copy of this? I keep getting an unzip error. Is development dead?
Click to expand...
Click to collapse
Why not use magisk delta this have a bootloop protect build in
Thank you, should I patch the boot image or not?
ChrisFeiveel84 said:
Why not use magisk delta this have a bootloop protect build in
Click to expand...
Click to collapse
Tell us more, is it a module, or a version of Magisk?
Droid_Nut said:
Thank you, should I patch the boot image or not?
Click to expand...
Click to collapse
For magsik delta ?
Droid_Nut said:
Tell us more, is it a module, or a version of Magisk?
Click to expand...
Click to collapse
Is a magsik version from huskydg with build in bootloop protect and magisk hide
So its a fork of Magisk. https://magiskzip.com/magisk-delta/
ChrisFeiveel84 said:
For magsik delta ?
Is a magsik version from huskydg with build in bootloop protect and magisk hide
Click to expand...
Click to collapse
Huskydg also made the bootloop module, so patch it for either?
Actually never mind I just patched it on 3 phones with no problem.
As far as Delta, the newest Lsposed requires Zygisk, so you might find that you will need that anyways as more modules go that route. Any ways, I will give Delta try some time.
ChrisFeiveel84 said:
For magsik delta ?
Is a magsik version from huskydg with build in bootloop protect and magisk hide
Click to expand...
Click to collapse
I installed Delta, can I now turn off the bootloop module?
Droid_Nut said:
I installed Delta, can I now turn off the bootloop module?
Click to expand...
Click to collapse
No then when you enable it on magsik this isnatlled this modul
Few days ago, magisk brought update. I updated and restarted. 1st restart was ok, but 2nd restart after updating youtube revanved module caused bootloop. I had to flash firmware in, data gone. Will this module really help me if it happens next time or i should use TWRP. TWRP is not available for my device BTW. I will try to build it as it's open source.