Bricked my Phone (Mi 11T) - Magisk

I installed a bad magisk module and now my phone doesn't boot.
I flashed the original boot.img to remove magisk - didn't help.
I tried "adb wait-for-device shell magisk -remove-modules" but it doesn't do anything even though I am pretty sure I have USB debugging enabled.
The problem that There is no TWRP for my phone (only for android 11 but I am on android 12).
What can I even do now?
I REALLY don't want to format (and ofc don't want to be without a phone for longer than I absolutely have to)
I am forever grateful for anyone who can help me!
I can provide any Info y'all need
PS: I contacted the TWRP dev if he can update it to android 12.

I think magisk modules are located at: /data/adb/modules
So you could run "adb shell" command while in fastboot mode.
After that execute command "rm -rf /data/adb/modules"
If you want to delete specific module run same command just with folder name of module.

Nem1x said:
I think magisk modules are located at: /data/adb/modules
So you could run "adb shell" command while in fastboot mode.
After that execute command "rm -rf /data/adb/modules"
If you want to delete specific module run same command just with folder name of module.
Click to expand...
Click to collapse
you cant use adb in fastboot mode though

Hi,
I`m a Poco F3 user, you could try RUN_TWRP-Orange Fox FIXED.bat Temporary Recovery, you run this via FASTBOOT, Start from instruction 6.
you have a choice between TWRP & Orangefox,
just replace the .img file (twrp.img) with the correct one needed for your phone
and choose 1 TWRP.
[A13]Evolution X for POCO F3/Mi 11x[alioth][OFFICIAL]
Evolution X 7.0 for the POCO F3 [alioth] /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following *...
forum.xda-developers.com
I hope this helps.

Hallohannes123 said:
you cant use adb in fastboot mode though
Click to expand...
Click to collapse
You could try with TWRP's file manager, but since you're on Android 12 the /data folder will probably be empty. Try that command I sent you, but while booting up the phone.

I had exactely the same problem after updating a magisk module, which module made this problem?
Are you on official Magisk or on Magisk alterantive like delta?

johnr64 said:
Hi,
I`m a Poco F3 user, you could try RUN_TWRP-Orange Fox FIXED.bat Temporary Recovery, you run this via FASTBOOT, Start from instruction 6.
you have a choice between TWRP & Orangefox,
just replace the .img file (twrp.img) with the correct one needed for your phone
and choose 1 TWRP.
[A13]Evolution X for POCO F3/Mi 11x[alioth][OFFICIAL]
Evolution X 7.0 for the POCO F3 [alioth] /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following *...
forum.xda-developers.com
I hope this helps.
Click to expand...
Click to collapse
My phone doesn't have a TWRP rom that works on android 12! so This isn't possible

Harlock1978 said:
I had exactely the same problem after updating a magisk module, which module made this problem?
Are you on official Magisk or on Magisk alterantive like delta?
Click to expand...
Click to collapse
i'm on normal magisk

Hallohannes123 said:
I tried "adb wait-for-device shell magisk -remove-modules"
Click to expand...
Click to collapse
Did you try this before or after flashing stock boot.img?

Nem1x said:
Did you try this before or after flashing stock boot.img?
Click to expand...
Click to collapse
I think after, but I also flashed the patched boot.img and tried it, still didn't help

Hallohannes123 said:
i'm on normal magisk
Click to expand...
Click to collapse
Then probably is the module that create the problem, which module was you updating?

Related

[ROM][UPDATED] Asus ZenFone 4 stock WW 6.5.27 deodexed rom [20141009]

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction/About
This is just stock ww 6.5.27 deodexed rom, packed as ext4 system.img meant to be flash via fastboot, nothing fancy here.
Click to expand...
Click to collapse
Features:
Based on stock ww 6.5.27.
Deodexed.
Zipaligned.
Init.d sysinit.
Zipalign and sqlite init.d script added.
Dalvik optimization in build.prop.
Busybox 1.22.0 applet installed in /system/xbin.
Adblocking hosts file.
Xposed framework fix. Can install/update xposed without bootloop/stuck on booting.
Accessing sdcard fix for thirdparty apps. Can read/write/modify data on sdcard.
Updated asus standalone app from playstore ie camera, calendar, messaging etc.
Debloated by removing app that can be install from playstore eg gmail, youtube, google plus, google music, google book, google magazine, google game, google hangouts, omlet chat etc. If u want them u can just install from playstore.
Probably other things i forgot to list here...
Click to expand...
Click to collapse
What Works:
Everything in stock rom should work.
Click to expand...
Click to collapse
Bugs:
Fc after first boot, just turn off/reboot again and everything should be fine.
Click to expand...
Click to collapse
Installation Instructions:
U need to already have updated to 6.5.27 stock rom either full flash or update ota.
Because zenfone 4 got no custom recovery yet so this is meant to be flash from pc/laptop so u need to have pc/laptop.
Backup your data eg contact, sms, calendar, photos etc.
U need to install Intel android driver.
U need to have adb and fastboot tool, can download from my link below. Just extract the archive, ADB_FASTBOOT.7z somehere in root of drive eg in C or D.
Extract the rom, u will get system.img around 1gb in size. Put it in the same folder as adb and fastboot above.
Boot phone into droidboot mode by pressing volume up+power button together.
Connect phone via usb cable.
Open the adb and fastboot tool folder and double click on OPEN.CMD. Windows terminal will open.
Type in the terminal to erase cache
Code:
fastboot erase cache
and press enter.
Type in the terminal to erase data
Code:
fastboot erase data
and press enter.
Type in the terminal to erase system
Code:
fastboot erase system
and press enter.
Now to flash system, type in the terminal
Code:
fastboot flash system system.img
and press enter. Flashing system would take around 10minutes.
After success flash system, if u want root need to flash supersu. Download and put ASUS_ZENFONE_ROOT.zip in the adb and fastboot folder and type in terminal
Code:
fastboot flash update ASUS_ZENFONE_ROOT.zip
and press enter. Phone will reboot automatically and will flash the root zip, then it will reboot again into system. First boot would take longer to generate dalvik etc.
Click to expand...
Click to collapse
Download:
Click to expand...
Click to collapse
Thanks To/Credits:
God
Linus Torvalds and whole linux kernel team and contributors.
Google
Asus.
shakalaca
and many, many other people whose their tool/app/guide i've used to make this...
Click to expand...
Click to collapse
Thank you for this rom but i have hard bricked my phone flashing this rom would get to normal :crying:
what did u do anyway?
if u follow the instruction it should boot, and even its not booting then can always reflash to stock rom. this rom will only modify system partition.
boot, recovery, fastboot and all other partition wont be touched and can always recover back to stock rom.
great job sir... I will try
syaeful said:
great job sir... I will try
Click to expand...
Click to collapse
Edit :
Succes Deodexed.. Thank you very much sir
Is anyone know to swap the storage of this phone ???
Sent from my ASUS_T00I using XDA Premium 4 mobile app
anyone wanna root the newly released kk update can root using the root zip in first post
Hoping for a kitkat custom ROM soon! :victory:
updated to ww 6.5.27.
mdfzhi said:
updated to ww 6.5.27.
Click to expand...
Click to collapse
Can I use the root package in the 1st post with this update?
ong14 said:
Can I use the root package in the 1st post with this update?
Click to expand...
Click to collapse
yes.
mdfzhi said:
yes.
Click to expand...
Click to collapse
Thank you.
I'll get my zf4 tomorrow.
Can't wait to try your mod.
This was great..been for a while finding exploit for rooting this phone on kitkat..your deodexed one was great..nice job...hope this phone community will grow big...
Cheers.
Bro..where's link..I'm sutfing on xda app..
Nvm..opnened in browser..
Just downloaded root things..tomorrow will try this deodex..
Greet from Malaysia
actually i'm not really into roms, more into kernels. thats why the rom is just deodex and few changes only, no new added features. hated smali editing.
been waiting far too long for asus to unlock zenfone 4 bootloader so that i could compile kernel myself.
mdfzhi said:
actually i'm not really into roms, more into kernels. thats why the rom is just deodex and few changes only, no new added features. hated smali editing.
been waiting far too long for asus to unlock zenfone 4 bootloader so that i could compile kernel myself.
Click to expand...
Click to collapse
Thank you for your contributing in zf4.
I have one question;
How can I revert back to stock firmware?
Can I flash a full stock f/w directly via droid boot menu [sd download]?
Not sure about sd download option in droidboot, never use it before but what i always did to get to full stock is by downloading full rom zip from asus server, extract it to get another zip, copy it into internal memory via usb cable and when removing usb cable will get notification to update.
mdfzhi said:
Not sure about sd download option in droidboot, never use it before but what i always did to get to full stock is by downloading full rom zip from asus server, extract it to get another zip, copy it into internal memory via usb cable and when removing usb cable will get notification to update.
Click to expand...
Click to collapse
Thank you for quick reply.
I'll try your mod tomorrow. (My zf4 have 2 batteries of 1200mAh, and still charging one of them.)
Owh...yeah..nany news on asus for unlocking bootloader.
?
Thanks a lot .. U saved me from a soft brick ...
No news yet about the bootloader, no reply from Asus

[Magisk][ROOT][EdXposed]Auto install tool - Magisk Installer for OnePlus 7T Pro

Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- A / B slot support
- EdXposed customized Magisk
- Stock boot backup
- Automation
Install guide:
- First, you should unlock your device
- Then enable USB debugging in Settings
- Install Java runtime environment in your Windows computer: http://java.com
- Double-click the MagiskInstaller_hotdog_20191111.jar then follow the prompts
(If double-click not work, you should use this command
Code:
java -jar MagiskInstaller_hotdog_20191111.jar
Tips:
- Any system version (include H2OS/OxygenOS) can use this tool
- Built-in Magisk version is EdXposed customized 20.1(20101), you can replace magiskboot,magiskinit,util_function.sh to your Magisk version in jar file /assets (do NOT replace boot_patcher.sh, it will brick your device to Qualcomm CrashDump Mode)
- OnePlus 7T should also be usable (I haven't tested it, because I don't have OnePlus 7T device)
- Thanks to @mauronofrio for his unofficial twrp.
- To use EdXposed, follow the official website and install modules: http://edxp.meowcat.org/
Download:
Google Drive
at last .. hope its work in global
fahadalkhalaf said:
at last .. hope its work in global
Click to expand...
Click to collapse
should works
its work perfect.y ..
now i have superSu root ..
many thanks
@mlgmxyysd Links to social media removed from OP. Please refer to Telegram and Whatsapp Channels - Going Forward
mlgmxyysd said:
[a great post]
Click to expand...
Click to collapse
Hi, thanks for posting your guide. I have a few questions if it's okay.
1. Where is the stock boot image backed up to?
2. If I needed to undo everything this guide achieves (e.g. for warranty or selling), would I...
A. Uninstall all Magisk modules that I may have installed, then remove Magisk using Magisk Manager, then uninstall Magisk Manager
B. Restore the backed up boot image. (I'm not sure how to do that but can probably find out how to do it using adb)
C. Relock the bootloader.
3. Can I let Magisk Manager update Magisk and update Magisk Manager? The tip about how I can replace Magisk files and the risk of bricking make me think that maybe I can't.
4. Because you're thanking @mauronofrio for his unofficial twrp, does that mean this replaces the stock recovery with that twrp?
Thank you!
mlgmxyysd said:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- A / B slot support
- EdXposed customized Magisk
- Stock boot backup
- Automation
Install guide:
- First, you should unlock your device
- Then enable USB debugging in Settings
- Install Java runtime environment in your Windows computer: http://java.com
- Double-click the MagiskInstaller_hotdog_20191111.jar then follow the prompts
(If double-click not work, you should use this command
Code:
java -jar MagiskInstaller_hotdog_20191111.jar
Tips:
- Any system version (include H2OS/OxygenOS) can use this tool
- Built-in Magisk version is EdXposed customized 20.1(20101), you can replace magiskboot,magiskinit,util_function.sh to your Magisk version in jar file /assets (do NOT replace boot_patcher.sh, it will brick your device to Qualcomm CrashDump Mode)
- OnePlus 7T should also be usable (I haven't tested it, because I don't have OnePlus 7T device)
- Thanks to @mauronofrio for his unofficial twrp.
- To use EdXposed, follow the official website and install modules: http://edxp.meowcat.org/
Download:
Google Drive
Click to expand...
Click to collapse
Sir, I stuck at Flashing boot_b partition
And that time the phone have boot in to twrp
ricky886 said:
Sir, I stuck at Flashing boot_b partition
And that time the phone have boot in to twrp
Click to expand...
Click to collapse
Some devices are unable to run the ADB shell commands in recovery for unknown reasons
Anyone get EdXposed working after installing this Magisk?
cucumbersmell said:
Anyone get EdXposed working after installing this Magisk?
Click to expand...
Click to collapse
+1
Also does the safetynet passes along with EdXposed?
Ok thank God the Lord has given me a changed frame of mind cause I was about to slam my laptop and computer. I must be missing something. I have Java installed and downloaded the magisk jar and for the life of me I can't get it to work not by double clicking not by running as administrator nothing I can't get Java to pop up so I can put in the command. And I tried using the other method with adb and fastboot. I keep getting error that directory doesn't exist. I think I'm stuck with boring stock at least I got unlocked LOL oh well. Any help would be appreciated. Thanks
mlgmxyysd said:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- A / B slot support
- EdXposed customized Magisk
- Stock boot backup
- Automation
Install guide:
- First, you should unlock your device
- Then enable USB debugging in Settings
- Install Java runtime environment in your Windows computer: http://java.com
- Double-click the MagiskInstaller_hotdog_20191111.jar then follow the prompts
(If double-click not work, you should use this command
Code:
java -jar MagiskInstaller_hotdog_20191111.jar
Tips:
- Any system version (include H2OS/OxygenOS) can use this tool
- Built-in Magisk version is EdXposed customized 20.1(20101), you can replace magiskboot,magiskinit,util_function.sh to your Magisk version in jar file /assets (do NOT replace boot_patcher.sh, it will brick your device to Qualcomm CrashDump Mode)
- OnePlus 7T should also be usable (I haven't tested it, because I don't have OnePlus 7T device)
- Thanks to @mauronofrio for his unofficial twrp.
- To use EdXposed, follow the official website and install modules: http://edxp.meowcat.org/
Download:
Google Drive
Click to expand...
Click to collapse
Is it working for McLaren edition too?
Root?
Will this root my 7tpro?
And is the process reversible?
stuck
So I run it and I get stuck at Patching boot for slot a...
so has anyone done a one plus 7t pro with this method ?
garny68 said:
so has anyone done a one plus 7t pro with this method ?
Click to expand...
Click to collapse
This method is for 7T pro.
Read carefully please
i cant even get it to open , double click the jar and nothing so i type command and get
C:\Users\garny>operable program or batch file.java -jar MagiskInstaller_hotdog_20191111.jar
'operable' is not recognized as an internal or external command,
operable program or batch file.
garny68 said:
i cant even get it to open , double click the jar and nothing so i type command and get
C:\Users\garny>operable program or batch file.java -jar MagiskInstaller_hotdog_20191111.jar
'operable' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Some users above also reporting errors with this method
So
https://forum.xda-developers.com/showpost.php?p=80894389&postcount=133
If you're on 10.0.4 try this patched boot IMG
thanks but im on 10.0.3
garny68 said:
thanks but im on 10.0.3
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t...-3-patched-boot-image-oneplus-7t-pro-t3986351
Here

[GUIDE] How to root the Moto E6 Plus (pokerp) in the variant 32/2 and 64/4

Hi guys, this guide is for how to root Moto E6 Plus in the variant 32/2 and 64/4
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device,
* I will laugh at you.
*
*/
Prerequisites:
-Your bootloader must be unlocked.
-Have installed a custom recovery.
-Recovey.img for patch (32/2 variant only).
-Magisk.
Spoiler: PROCESS IN THE VARIANT 32/2
WARNING: In this variant when the root is active, the phone does not read the IMEI (I mean the mobile data won't work), this is fixed by simply rebooting normally, but yes reboot normally you won't have root.
Download and install the Magisk application.
In the section "Magisk" click on "Install" and select "Recovery Mode", then next and select "Select and Patch a File" and search recovery.img file (it can be the recovery twrp or the recovery stock), select "Let's Go" and wait for the process to finish. Once finish the process, the file patched will be in the folder Downloads.
Then reboot on TWRP, once there go to "Install", select "Install Image" and then select the file patched what is in /sdcard/Downloads and install it like "Recovery", then reboot into recovery mode and you will have root .
Spoiler: PROCESS IN THE VARIANT 64/4
Download the zip file of the GitHub of Magisk.
Reboot in TWRP, select "Install" and then search the zip file of Magisk and flash it.
Then reboot normally and you will have root .
If any part was misunderstood, sorry, I'm not very good at English ;-;
Credits: Me, @topjohnwu
Hello, did you happen to find a fix for mobile data without loosing root?
Hello do you happen to have a fix for mobile data without loosing root on moto e6plus?
jglm4u said:
Hello do you happen to have a fix for mobile data without loosing root on moto e6plus?
Click to expand...
Click to collapse
at the moment this is the only way
so that the imei is not lost, then a custom kernel should be made, since the problem is that the ramdisk of the boot.img of the 32 version is in a different format than the one used by magisk
Hi, I did what you said to install magisk and it worked, but I can't activate wi-fi anymore.can you help me?; -;
Fastoh said:
Hi guys, this guide is for how to root Moto E6 Plus in the variant 32/2 and 64/4
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device,
* I will laugh at you.
*
*/
Prerequisites:
-Your bootloader must be unlocked.
-Have installed a custom recovery.
-Recovey.img for patch (32/2 variant only).
-Magisk.
Spoiler: PROCESS IN THE VARIANT 32/2
WARNING: In this variant when the root is active, the phone does not read the IMEI (I mean the mobile data won't work), this is fixed by simply rebooting normally, but yes reboot normally you won't have root.
Download and install the Magisk application.
In the section "Magisk" click on "Install" and select "Recovery Mode", then next and select "Select and Patch a File" and search recovery.img file (it can be the recovery twrp or the recovery stock), select "Let's Go" and wait for the process to finish. Once finish the process, the file patched will be in the folder Downloads.
Then reboot on TWRP, once there go to "Install", select "Install Image" and then select the file patched what is in /sdcard/Downloads and install it like "Recovery", then reboot into recovery mode and you will have root .
Spoiler: PROCESS IN THE VARIANT 64/4
Download the zip file of the GitHub of Magisk.
Reboot in TWRP, select "Install" and then search the zip file of Magisk and flash it.
Then reboot normally and you will have root .
If any part was misunderstood, sorry, I'm not very good at English ;-;
Credits: Me, @topjohnwu
Click to expand...
Click to collapse
Hi, I did what you said to install magisk and it worked, but I can't activate wi-fi anymore.can you help me?; -;
Knznn 009 said:
Hi, I did what you said to install magisk and it worked, but I can't activate wi-fi anymore.can you help me?; -;
Hi, I did what you said to install magisk and it worked, but I can't activate wi-fi anymore.can you help me?; -;
Click to expand...
Click to collapse
hi, what variant do you have?
Fastoh said:
hi, what variant do you have?
Click to expand...
Click to collapse
Hi, I have variant 32
Knznn 009 said:
Hi, I have variant 32
Click to expand...
Click to collapse
Wi-fi or mobile data doesn't work for you?
because if you have the 32/2 variant then the wifi will work
what would not work would be the mobile data
Fastoh said:
Wi-fi or mobile data doesn't work for you?
Click to expand...
Click to collapse
The wifi is not working
Knznn 009 said:
The wifi is not working
Click to expand...
Click to collapse
try reinstalling the corresponding boot.img
and if it doesn't work try to change gsi
thank you, it helped a lot

Make any GSI work fully on the Xiaomi Redmi 8

Code:
/*
* Your warranty is now void lol.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tutorial
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial
Forgot to mention that magisk WONT WORK on roms that use android 11!!
Its a limitation of android 11 and i cannot fix this.
Seems promising. Would try on weekend and cast vote.
Thanks for you efforts for community.
Realized once again that you dont even need to boot, just flash the lineageOS rom, then the GSI on top.
thank you very much its working the problem i always encounter is my bluetooth but now its working fine sorry for my bad english BTW i use havoc <3
I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?
thanks, in the evening I will check and tell exactly what works and what does not work, probably all GSIs are giving me some problems (problem with brightness or bluetooth headphones)
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped everything formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Dragonnuu said:
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Click to expand...
Click to collapse
We need LOLZ because the lineage kernel gets carried over and its broken (Try booting lineage clear, you wont get far)
mwaseem851 said:
I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?
Click to expand...
Click to collapse
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.
I have done lots of experimentation since last post and finally settled with Havoc OS 3.12 (all android 11 roms are still buggy).
Thanks.
boofiboi said:
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.
Click to expand...
Click to collapse
boofiboi said:
Code:
/*
* Your warranty is now void lol.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tutorial
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial
Click to expand...
Click to collapse
Can you flash the AOSP beta GSIs from released on the Android website? For example the Android 12 Beta GSI?
I tried installing Android 12 on Redmi 8 but it did something perplexing.
TWRP said no OS was installed. Rebooting had the phone boot back into TWRP. I tried installing through both fastboot and TWRP. Installations were successful tho.

[LINUX][FAJITA]Ubuntu 22.04 Desktop[WIP]

Code:
*** Disclamer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Introduction
This is Ubuntu 22.04 desktop for OnePlus 6t
Click to expand...
Click to collapse
WARNING THIS INSTALLER ZIP WILL MODIFY THE PARITION TABLE OF YOUR DEVICE BACKUP ANY IMPORTANT DATA AS IT WILL BE LOST AFTER INSTALL.
THIS IS DUALBOOT SO YOUR ANDROID WILL STAY IF YOU WANT TO REBOOT INTO ANDROID USE THE BUILD IN SLOT SWITCHER IN EDK2 OR CHANGE THE SLOT WITH TWRP OR FASTBOOT
Installation instructions
1. Install oos 11 stock rom if you were not on it before
2. do fastboot boot pathoftwrpimghere with the twrp image linked in downloads
3. Download the Installer.zip
4. In TWRP hit advanced -> adb sideload -> swipe
5. On your computer do adb sideload pathtothedownloadedinstaller.zip
6. When the flash is done in TWRP select reboot and check your active slot if its a press button that shows b and then reboot if slot is b hit the button that shows a and then reboot
7. Setup your user
8. Profit
Click to expand...
Click to collapse
Download
ROM
RECOVERY
Click to expand...
Click to collapse
Changelog
Code:
Current changelog:31.05.2022
[note] 1st Release of Ubuntu 22.04 Desktop
[new] Ubuntu 22.04 Desktop with 5.18 mainline kernel
Click to expand...
Click to collapse
FAQ
What doesnt work ?
camera, audio (will be fixed eta soon), sensors , modem (mobile data, sms will be fixed in next release), calls
This rom is for fajita only
Click to expand...
Click to collapse
Thanks To/Credits
Code:
@calebcc
Sources
Code:
[URL="https://gitlab.com/sdm845-mainline/linux"]Kernel[/URL]
[URL="https://gitlab.com/sdm845-mainline/firmware-oneplus-sdm845"]Firmware[/URL]
This work on 6 too?
anhenrique said:
This work on 6 too?
Click to expand...
Click to collapse
i guess it could , i will send you a new esp.zip for enchilada later so you can test
when i send it to you just flash the zip like described and then in twrp do "adb push esp.zip /tmp && adb shell 'mkdir /esp && mount/dev/block/sda17 /esp && rm -rf /esp* && mv /tmp/esp.zip /esp/ && cd /esp && unzip esp.zip"
The is awesome.. thank you for sharing
Dang, now I can carry a development machine in my pocket. Thanks man!
Oh boy I'm excited to try this out! This'll be great if I don't have to carry around my pi anymore. Thanks my guy!
Cant download it android file host says all the time no mirrors found
anybody still have the zip and be able to upload? or.. if OP still here.. pretty please, with a cherry on top, reupload? i lost my backup of the rom zip, and with updates with edk2 and orange fox duelboot. i would like to test with this again. anyone that see's this TIA
Yeah. Still no mirror, would also appreciate another upload.
coreycusick said:
Yeah. Still no mirror, would also appreciate another upload.
Click to expand...
Click to collapse
Well I eventually just reversed what I’ve seen. Eventually got Ubuntu to boot. I needed to do a lot of work tho. So it’s possible. GPU doesn’t seem to fully work tho. Pretty unusable. Do not really think it’s feasible to be completely functional.

Categories

Resources