I am not able to boot secondary rom with dual boot patcher. But can boot in my redmi note 3 and moto G4 plus. Why is it not possible with redmi note 4?
Dual boot patcher latest version working well with mido. I had also extended as primary and in data slot RR 5.8.3 , discovery rom, lineage os rom , all booted well . No issues
https://dbp.noobdev.io/downloads/
drmuruga said:
Dual boot patcher latest version working well with mido. I had also extended as primary and in data slot RR 5.8.3 , discovery rom, lineage os rom , all booted well . No issues
https://dbp.noobdev.io/downloads/[/QUOTE
hello can you pls tell me what to do to make it work i need miui is primary and aosp is secondary rom thanks a lot
Click to expand...
Click to collapse
akino553 said:
drmuruga said:
Dual boot patcher latest version working well with mido. I had also extended as primary and in data slot RR 5.8.3 , discovery rom, lineage os rom , all booted well . No issues
https://dbp.noobdev.io/downloads/[/QUOTE
hello can you pls tell me what to do to make it work i need miui is primary and aosp is secondary rom thanks a lot
Click to expand...
Click to collapse
Yes , I flashed miui.eu nougat ROM as primary and RR 5.8.3 as secondary in data slot now booted well and able to switch between primary and secondary. Cool.
Install dual boot patcher application and give root permission in miui ROM ( should be nougat)
then open patch zip file, and press + add flashable zip, select ROM, long press over ROM file,select open , patcher options popped out,
Select partition configuration , select data slot, add name to this ROM partition ( I give data1,data2 etc) save, select ✓mark in upper part of screen to patch , then add which ever files you need ,then flash via twrp or in app flash by select Roms folder in open page , select a red button with downward arrow ,sect ok select + ,add previously patched files and flash, in app flashing sometimes give error, then you have to flash via twrp recovery .
In twrp no wipe, just select your patched files in order and flash , finally select dual boot utilities zip flash select your needed ROM ,select switch to..., Reboot.....
(Use latest patcher app).
ANYBODY KNOWS HOW TO CHANGE THE TITLE?
,
Click to expand...
Click to collapse
drmuruga said:
akino553 said:
Yes , I flashed miui.eu nougat ROM as primary and RR 5.8.3 as secondary in data slot now booted well and able to switch between primary and secondary. Cool.
Install dual boot patcher application and give root permission in miui ROM ( should be nougat)
then open patch zip file, and press + add flashable zip, select ROM, long press over ROM file,select open , patcher options popped out,
Select partition configuration , select data slot, add name to this ROM partition ( I give data1,data2 etc) save, select ✓mark in upper part of screen to patch , then add which ever files you need ,then flash via twrp or in app flash by select Roms folder in open page , select a red button with downward arrow ,sect ok select + ,add previously patched files and flash, in app flashing sometimes give error, then you have to flash via twrp recovery .
In twrp no wipe, just select your patched files in order and flash , finally select dual boot utilities zip flash select your needed ROM ,select switch to..., Reboot.....
(Use latest patcher app).
ANYBODY KNOWS HOW TO CHANGE THE TITLE?
,
Click to expand...
Click to collapse
Can I use miui as secondary ROM??
Not the miui.eu ROM the official one...
I'm currently on aospe ROM and I wanna keep it as my primary ROM with official miui 8 as secondary....
Can I do it???
Click to expand...
Click to collapse
drmuruga said:
akino553 said:
Yes , I flashed miui.eu nougat ROM as primary and RR 5.8.3 as secondary in data slot now booted well and able to switch between primary and secondary. Cool.
Install dual boot patcher application and give root permission in miui ROM ( should be nougat)
then open patch zip file, and press + add flashable zip, select ROM, long press over ROM file,select open , patcher options popped out,
Select partition configuration , select data slot, add name to this ROM partition ( I give data1,data2 etc) save, select ✓mark in upper part of screen to patch , then add which ever files you need ,then flash via twrp or in app flash by select Roms folder in open page , select a red button with downward arrow ,sect ok select + ,add previously patched files and flash, in app flashing sometimes give error, then you have to flash via twrp recovery .
In twrp no wipe, just select your patched files in order and flash , finally select dual boot utilities zip flash select your needed ROM ,select switch to..., Reboot.....
(Use latest patcher app).
ANYBODY KNOWS HOW TO CHANGE THE TITLE?
,
Click to expand...
Click to collapse
thank you very much well test it now :good::good:
Click to expand...
Click to collapse
leo_pard2331 said:
drmuruga said:
Can I use miui as secondary ROM??
Not the miui.eu ROM the official one...
I'm currently on aospe ROM and I wanna keep it as my primary ROM with official miui 8 as secondary....
Can I do it???
Click to expand...
Click to collapse
Yes, you can.
Click to expand...
Click to collapse
drmuruga said:
akino553 said:
Yes , I flashed miui.eu nougat ROM as primary and RR 5.8.3 as secondary in data slot now booted well and able to switch between primary and secondary. Cool.
Install dual boot patcher application and give root permission in miui ROM ( should be nougat)
then open patch zip file, and press + add flashable zip, select ROM, long press over ROM file,select open , patcher options popped out,
Select partition configuration , select data slot, add name to this ROM partition ( I give data1,data2 etc) save, select ✓mark in upper part of screen to patch , then add which ever files you need ,then flash via twrp or in app flash by select Roms folder in open page , select a red button with downward arrow ,sect ok select + ,add previously patched files and flash, in app flashing sometimes give error, then you have to flash via twrp recovery .
In twrp no wipe, just select your patched files in order and flash , finally select dual boot utilities zip flash select your needed ROM ,select switch to..., Reboot.....
(Use latest patcher app).
ANYBODY KNOWS HOW TO CHANGE THE TITLE?
,
Click to expand...
Click to collapse
not working sir my device vibrite on boot and reboot
Click to expand...
Click to collapse
Are you use latest dual boot patcher and utilities ? Because I had same problem with older versions
Are you give root permission to dual boot patcher app?
Are you use latest dual boot patcher and utilities ? Because I had same problem with older versions
Are you give root permission to dual boot patcher app?
drmuruga said:
Are you use latest dual boot patcher and utilities ? Because I had same problem with older versions
Are you give root permission to dual boot patcher app?
Click to expand...
Click to collapse
yes i use the latest version but not work
akino553 said:
yes i use the latest version but not work
Click to expand...
Click to collapse
Same thing happening with me. Vibrate and reboot even with the latest app.
This tutorial is useful to use dual boot patcher
https://m.youtube.com/watch?v=IYBNkWtQkVg
drmuruga said:
This tutorial is useful to use dual boot patcher
https://m.youtube.com/watch?v=IYBNkWtQkVg
Click to expand...
Click to collapse
thank you a lot will test it now
dragneelfps said:
Same thing happening with me. Vibrate and reboot even with the latest app.
Click to expand...
Click to collapse
Same with me
dragneelfps said:
Same thing happening with me. Vibrate and reboot even with the latest app.
Click to expand...
Click to collapse
Me too T.T im is new member in house xda..im live at vietnam and my English is so bad
Im like and thank to xda because xda is help me long time ago im thank xda
Nice to meet all member in house xda
akino553 said:
drmuruga said:
not working sir my device vibrite on boot and reboot
Click to expand...
Click to collapse
You have to format data in twrp. It will wipe your internal data too. Your device is encrypted so it doesnt boot.
Click to expand...
Click to collapse
It's very old thread, dual Boot patcher is working well now.
From searches
1)if you want to keep one rom as miui then firstly install miui. miui cant installed over other apps.
2)dont use official rom as primary rom
Then what is officical rom ???
Related
I have ported EFIDroid (developed by @m11kkaa) for the Nexus 5.
@m11kkaa's original EFIDroid thread here: https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466.
This is an unofficial port of beta software. I am not responsible for anything that may happen to your device. Use at your own risk.
NOTE: This has been tested with last LineageOS Build (21/03/2017) and TWRP 3.1.0-0. All other configurations are untested by me, but should work.
Working ROMs
[Here I will post the ROM's that are working for multiboot (Of course I will need people's feedback to fullfill this list)]
LineageOS 14.1 (As primary, as secondary with SELinux permissive option)
DU 11.2 (As primary, as secondary with SELinux permissive option) tested by @AndresOrue
PureNexus 7.1.1 (Should work as primary but not tested, as secondary with SELinux permissive option) tested by @AndresOrue
Lineage OS DarkRom by Dark_Eyes (As primary, not tested as secondary-should work with SELinux permissive option) tested by @willyinpr4u
AlmostVanillaAOSP Marshmallow (As primary, not tested as secondary-should work with SELinux permissive option) tested by @alessio89g
AOSP Nougat (Should work as primary but not tested, as secondary with SELinux permissive option) tested by @alessio89g
UntouchedAOSP 6.0.1 tested by @BreckZeBoulay
MiUI 8 tested by @sa4ni
Euclidean OS tested by @willyinpr4u
Xenon HD AOSP tested by @willyinpr4u
AICP 12.1 7.1.2 tested by @phpbb3
Elixr-hammerhead-V1.1-20140420 tested by @playerkirk1
Plasma-Mobile tested by me
Installation
Install the attached EFIDroid Manager apk. Since this is an unofficial port, the EFIDroid Manager app from the Play Store won't work. (This is modified to use my unofficial server)
Open the EFIDroid Manager app, open the menu (at the top left), and click "Install/Update".
Click the big orange Install button.
And voila, you're done in 3 easy steps! Reboot to see your new 2nd-stage bootloader!
Post below with your installed ROM if you have success.
To update EFIDroid, just repeat step 2, and the click the big orange Update button.
The app won't automatically check for updates, so I'll post an announcement on this thread whenever an important update is available.
Migrating from MultiROM
TWRP Backups should work fine but as /sdcard gets mocked on TWRP for secondary ROMs to prevent an "accidental" wipe there is some steps to follow
1-Create a new slot
2-Go to /data/media/0/multiboot/your_new_slot/data
3-Create folder media/0/TWRP/BACKUPS
4-Move/copy your backup to the created folder -remember the backup folder is the one that look like a hash (like "'03480ffg04395g234")
5-Boot TWRP from EFIDroid for the new slot
6-Format System
7-Flash your backup
Multibooting
You can use EFIDroid as a multiboot manager. To add a multiboot ROM, do the following:
Open the EFIDroid Manager app. Press the plus button at the bottom right side of the screen to start adding a multiboot slot.
Under "Location", there should be a couple paths. Select the one containing "/data/media/0".
You can give the slot a name/description by using the appropriate fields.
Press the checkmark at the top right side of the screen to create the multiboot slot.
Reboot. When EFIDroid comes up, select TWRP, then select the newly created slot.
Go to the "Wipe > Advanced Wipe" menu. Select "System", then swipe to wipe.
Install all the zips you want on that slot.
NOTE: To prevent accidentall data loss when booting in recovery the real /sdcard gets mocked so you are not going to find your .zips as usual under TWRP's /sdcard. To acces the "real" /sdcard go to /multiboot/data/media/0
Reboot, and when EFIDroid comes up, your new slot should automatically be selected. Press the power button to boot, and enjoy!
IMPORTANT:your main ROM should boot without changing any configuration on EFIDroid but secondary ROM's are used to fail because of selinux denials. I strongly reccomend you to enable Force SELinux to permissive under EFIDroid options (the Gear icon in the main screen placed at the top right) - Once you kwon your secondary ROM is working you can try to boot without this option disabled - If you end up in a bootloop logcat and dmesg are welcome.
Troubleshooting
If you are unable to boot the OS/recovery from EFIDroid, do the following (you do have a working boot.img (from your main OS) and recovery.img (TWRP 3.1.0-0 recommended), right?)
This assumes you have fastboot properly setup. (Ubuntu: sudo apt-get install android-tools-fastboot - Windows: just google for the binaries)
OPTION 1:
In EFIDroid, use the volume keys to navigate to "Fastboot", the press the power key to select it.
There should only be one entry in the Fastboot menu. Press the power key to select it.
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot oem exit
In EFIDroid, use the volume keys to navigate to the back button at the top of the screen. Press the power key to select.
Use the volume keys to navigate to "Reboot", then press the power key to select.
OPTION 2:
Enter LG's Fastboot Mode (Volume Down + Power Off)
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot reboot-bootloader
Use the volume keys to navigate and select "Start" or "Recovery", then press the power key to select.
You should be able to boot the installed OS/recovery now. If this doesn't work, you can always enter Fastboot Mode (Volume Down + Power Off) and then flash your recovery and boot from there.
Clarifications
When Installing EFIDroid boot and recovery partitions are flashed so you only can enter recovery through EFIDroid to prevent any confusion
To enter Recovery just select your recovery on EFIDroid and then select the ROM you want the recovery to apply the .zip you are going to flash (EFIDroid properly patches TWRP ramdisk to affect the desire slot/ROM)
How does this work?
Well I'm going to explain it a little:
Right now you have your ROM kernel (boot.img) custom or stock ( it don't mind) in your boot partition and your recovery.img (I think TWRP) in your recovery partition. UEFIDroid is a kernel but it is not a linux kernel, it's based on Little Kernel aka LK... Qualcom port LK to Snapdragon chipsets and developed their custom bootloader, then the EFIDroid developer take this and implemented UEFI over the Qualcom's LK port.
Whe you install EFIDroid this is what happens:
-EFIDroid Manager backups your boot.img and recovery.img in /data/media/0/UEFIESP folder
-EFIDroid Manager flash EFIDroid in your boot and your recovery partitions (the recovery is flashed to prevent you using your recovery without booting it from EFIDroid)
Then the next time you boot the stock bootloader aka aboot loads UEFIDroid that is flashed in your boot partition, LK kernel boots and execute UEFI. Then the UEFI looks for the original boot.img (for booting your actual ROM aka Internal) and looks for your actual recovery.img, remember both were saved into /data/media/0/UEFIESP.
And finally it looks for slots/ROMs in /data/media/0/multiboot (of course these are the slots for multibooting a lot of ROMs).
A slot for a ROM is composed by a data folder, a system.img(1GB) and a boot.img (these are the ones used/mounted to boot the ROM you select in multiboot menu) -slots are added from EFIDroid Manager app.
In the last step it shows you the Menu to select what you want to boot and it applies the propers patchs to ramdisk to use the correct data folder and system.img, then boot the correct boot.img using libboot (the usually used by android bootloaders)
Recoveries
I personally tested EFIDroid with TWRP and TWRP CAF in their 3.1.0.0 versions and they worked great.
As I stated before, your current recovery is backed up to /data/media/0/partition_recovery.img so if you somehow ended having trouble to boot your recovery, you can boot to your main OS and replace /data/media/0/partition_recovery.img with another recovery (ofc change the name of the new recovery to partition_recovery.img) - YOU NEED A ROOT BROWSER -
Custom Kernels
Well custom kernels are known to break things, so to say that a ROM is working I need you to test with the stock kernel that comes with it, then of course if you want to test custom kernels you're welcome and I will update this post with your feedback.
NOT WORKING CUSTOM KERNELS:
ElementalX 7.09 (Don't pass EFIDroid boot Splash Screen) tested by @AndresOrue with DU 11.2 (It should not matter because it's not booting the ROM at all) -may be ramdisk patching problem-
WORKING CUSTOM KERNELS:
BluSpark r122 tested by @AndresOrue
Franco.Kernel r105 tested by @alessio89g
ElementalX 8.00 tested by me
Credits
-All credit goes to @m11kkaa for doing all the hard work in developing EFIDroid.
-@abraha2d for the help with porting and giving permission to use his post for Note 4 as the base for this one!
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
EFI Specification: 2.60
Beta Release Date: 2017-03-27
Created 2017-03-28
Last Updated 2017-04-17
-Initial Release 2017-03-27
Bugs:
ElementalX 7.09 Kernel not booting (may be ramdisk compression incompatibility)
Screen blinks when using AROMA Installers in TWRP (no details) - AROMA Installer is usable but in a very annoying way :/
Flashable scripts logs are not shown in TWRP console when flashing in a secondary ROM (no details)
Thank you mate for it, i will try it as soon as i can and i let you know how it works.
Edited: app installed, works ok so far
Edit2: @lukss12 mate the new boot Menu works but the phone don't boot anymore. I don't try to install new roms only reboot the phone but it only says rebooting android 7.1.1 internal .
I solved the problem, i dirty flash my rom ( du 11.2).
My rom: DU 11.2 android 7.1.1
Anyway at night i will try again
The prospect of an alternative to multirom is exciting. The great hammerhead lives on!
AndresOrue said:
Thank you mate for it, i will try it as soon as i can and i let you know how it works.
Edited: app installed, works ok so far
Edit2: @lukss12 mate the new boot Menu works but the phone don't boot anymore. I don't try to install new roms only reboot the phone but it only says rebooting android 7.1.1 internal .
I solved the problem, i dirty flash my rom ( du 11.2).
My rom: DU 11.2 android 7.1.1
Anyway at night i will try again
Click to expand...
Click to collapse
Great you could solve ur problem, yes flashing boot.img from your actual ROM will boot the device. Remember EFIDroid is also installed in your recovery partition, you can boot TWRP from there but if you want to revert back to "stock" DU with TWRP you need to flash TWRP to recovery partition.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
Did you try to set Force Selinux permissive option in Efidroid?
Also for the internal ROM you can try unpatched boot... For this boot efidroid and long press the power button on the Entry for your ROM.
lukss12 said:
Great you could solve ur problem, yes flashing boot.img from your actual ROM will boot the device. Remember EFIDroid is also installed in your recovery partition, you can boot TWRP from there but if you want to revert back to "stock" DU with TWRP you need to flash TWRP to recovery partition.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
Did you try to set Force Selinux permissive option in Efidroid?
Also for the internal ROM you can try unpatched boot... For this boot efidroid and long press the power button on the Entry for your ROM.
Click to expand...
Click to collapse
Did you try to set Force Selinux permissive option in Efidroid?
No i will try it at night.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
For me 5 min and nothing.
Also i need to read a little more to avoid problems.. and also i think when flash suspersu breaks the boot but i need to confirm it
AndresOrue said:
Did you try to set Force Selinux permissive option in Efidroid?
No i will try it at night.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
For me 5 min and nothing.
Also i need to read a little more to avoid problems.. and also i think when flash suspersu breaks the boot but i need to confirm it
Click to expand...
Click to collapse
Yep I recommend reading the full OP once or twice before starting....well is good to see that the app and installation is working... It's weird that you can't boot internal - please if you can try the unpatched boot option-
lukss12 said:
Yep I recommend reading the full OP once or twice before starting....well is good to see that the app and installation is working... It's weird that you can't boot internal - please if you can try the unpatched boot option-
Click to expand...
Click to collapse
Questions:
What is lf laf recovery?
I flashed twrp from my pc but i still have this new boot, other way to deleted?
How can i deleted this app completely? flashing stock rom is ok or i can flash a custom rom with full wipe?
Anyway now i am doing a backup of my app So I can try it without problems
AndresOrue said:
Questions:
What is lf laf recovery?
I flashed twrp from my pc but i still have this new boot, other way to deleted?
How can i deleted this app completely? flashing stock rom is ok or i can flash a custom rom with full wipe?
Anyway now i am doing a backup of my app So I can try it without problems
Click to expand...
Click to collapse
Enter fastboot mode (volume down + power off)
fastboot flash recovery twrp.img
fastboot reboot-bootloader
Select recovery
Flash your ROM zip
Or extract boot.img from your ROM zip
Enter fastboot mode
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Both of those options will revert your boot and recovery partition to "stock"
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
lukss12 said:
Enter fastboot mode (volume down + power off)
fastboot flash recovery twrp.img
fastboot reboot-bootloader
Select recovery
Flash your ROM zip
Or extract boot.img from your ROM zip
Enter fastboot mode
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Both of those options will revert your boot and recovery partition to "stock"
Click to expand...
Click to collapse
A few things:
To revert to stock recovery, I had to repeat two times the process of flashing the boot.img and twrp.
Obviously you lose root at this time.
Installed EFIdroid again and now first rom boot ok , no more "booting android internal" for 5 min anymore. I dont know if it because I reflashed the boot image again or maybe was the custom kernel because now i have stock DU kernel.
Now i try to add a second rom:
1) Steps from EFIdroid to create second rom works great.
2) rebooting ok
3) I selected twrp and install DU 11.2
4) installation was ok
5) Rebooting into second rom , bootloop in bootanimation after five minutes it freeze and reboot
6)edited here ( i forgot the part of change selinux to permissive )
7) wipe and installed again the second rom and finally second rom boot ok , using DU 11.2 as second rom.
8) Supersu was intalled and works ok in second rom too.
I can confirm now that the reason that the first and second rom dont boot was elementalX kernel. With the stock DU kernel works perfect. primary and secondary rom.
I hope it helps...
Questions:
how i delete second rom completely ? only with full wipe?
---------- Post added at 09:02 PM ---------- Previous post was at 08:57 PM ----------
MINECRAFT4PDA said:
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
Click to expand...
Click to collapse
the first time that i installed EFIdroid i was using elementalx 7.09 and it installed ok but first rom dont boot anymore. The second time, after i reflashed the boot image from DU the rom boot fine
edited: I can confirm now that with elementalX the rom dont boot
MINECRAFT4PDA said:
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
Click to expand...
Click to collapse
Well I'm going to explain it a little:
Right now you have your ROM kernel (boot.img) custom or stock ( it don't mind) in your boot partition and your recovery.img (I think TWRP) in your recovery partition. UEFIDroid is a kernel but it is not a linux kernel, it's based on Little Kernel aka LK... Qualcom port LK to Snapdragon chipsets and developed their custom bootloader, the EFIDroid developer take this and implemented UEFI over the Qualcom's LK port.
Whe you install EFIDroid this is what happens:
-EFIDroid backups your boot.img and recovery.img in /data/media/0/UEFIESP folder
-EFIDroid Manager flash EFIDroid in your boot and your recovery partitions (the recovery is flashed to prevent you using your recovery without booting it from EFIDroid)
Then the next time you boot the stock bootloader aka aboot loads UEFIDroid that is flashed in your boot partition, LK kernel boot and execute UEFI. Then the UEFI looks for the original boot.img (for booting your actual ROM aka Internal) and looks for your actual recovery.img, remember both were saved into /data/media/0/UEFIESP.
And finally it looks for slots/ROMs in /data/media/0/multiboot (of course these are the slots for multibooting a lot of ROMs).
-An slot for a ROM is composed by a data folder, a system.img(1GB) and a boot.img (these are the ones used/mounted to boot the ROM you select in multiboot menu) -slots are added from EFIDroid Manager app.
In the last step it shows you the Menu to select what you want to boot. It applies the propers patchs to ramdisk to use the correct data folder and system.img and boot the correct boot.img using libaboot (the usually used by android bootloaders)
Deleted
AndresOrue said:
Installed EFIdroid again and now first rom boot ok , no more "booting android internal" for 5 min anymore. I dont know if it because I reflashed the boot image again or maybe was the custom kernel because now i have stock DU kernel.
Click to expand...
Click to collapse
Great so DU works as internal , and secondary with SELinux permissive
AndresOrue said:
I can confirm now that the reason that the first and second rom dont boot was elementalX kernel. With the stock DU kernel works perfect. primary and secondary rom.
Click to expand...
Click to collapse
Yes it is possible that a custom kernel is making problem to patch ramdisk
AndresOrue said:
Questions:
how i delete second rom completely ? only with full wipe?
Click to expand...
Click to collapse
No, you don't need full wipe. Slots/ROMs are stored ind /data/media/0/multiboot/your_rom, just delete "your_rom" folder with a root browser and goodbye ROM.
AndresOrue said:
Deleted
Click to expand...
Click to collapse
Sorry I was on the phone and it's a little slow to write and QUOTE there.
I have not tested custom kernels because I don't use them, I think is possible that the custom kernel makes ramdisk patching to fail
lukss12 said:
Sorry I was on the phone and it's a little slow to write and QUOTE there.
I have not tested custom kernels because I don't use them, I think is possible that the custom kernel makes ramdisk patching to fail
Click to expand...
Click to collapse
Sorry too mate I posted it before I read that you replied to me... yes DU11.2 works as primary and secondary rom. I will try others roms tomorrow but so far all is working great in secondary rom.
Thank you for you work!!!
AndresOrue said:
Sorry too mate I posted it before I read that you replied to me... yes DU11.2 works as primary and secondary rom. I will try others roms tomorrow but so far all is working great in secondary rom.
Thank you for you work!!!
Click to expand...
Click to collapse
There is no need to thank I'm doing this for fun
It' can be usefull if you got us some dmesg and logcat logs when the secondary ROM is bootlooping because of the SELinux permissive option not enabled. - you can get this with adb, the ROM bootloops but adb should get started at some point (of course you need to properly boot to the ROM the first time and enable adb and authorize your computer -
Thanks for the testing and wathever you have to share about using EFIDroid is usefull
lukss12 said:
There is no need to thank I'm doing this for fun
It' can be usefull if you got us some dmesg and logcat logs when the secondary ROM is bootlooping because of the SELinux permissive option not enabled. - you can get this with adb, the ROM bootloops but adb should get started at some point (of course you need to properly boot to the ROM the first time and enable adb and authorize your computer -
Thanks for the testing and wathever you have to share about using EFIDroid is usefull
Click to expand...
Click to collapse
Here is the log from second rom with selinux permissive not enable.
Also I confirm that the first rom boot ok with selinux permissive not enable ( selinux as enforcing ).
tell me if the log are correct, if not i try again.
Edited: i did some more test:
I tried as secondary pure nexus rom version : purenexus_hammerhead-7.1.1-20170216-HOMEMADE and boot ok in permissive enable
Also as secondary and permissive enable, I tried DU11.2 with the kernel blu_spark_r122_hammerhead_5472df4 and here boot ok too. It Does not hang up, with the massage " booting android 7.1.1" ( so elementalX 7.09 doesn't work so far).
Thanks for taking the time for this amazing work.
Just downloaded the .apk and installed, boot to EFIDroid, I guess, because I saw a never before seen menu with my internal ROM, TWRP, etc...
As of now it's late where I'm from, but I will download a secondary ROM later and post results.
Thanks.
willyinpr4u said:
Thanks for taking the time for this amazing work.
Just downloaded the .apk and installed, boot to EFIDroid, I guess, because I saw a never before seen menu with my internal ROM, TWRP, etc...
As of now it's late where I'm from, but I will download a secondary ROM later and post results.
Thanks.
Click to expand...
Click to collapse
Yep that "never seen before menu" is EFIDroid hehe, so your primary ROM is booting ok, please share what ROM you are using. And remember to enable Force SELinux permissive when booting a secondary ROM to prevent a SELinux denial bootloop, then you can try with the option disabled. But if the LineageOS kernel, that is the most "normal" kernel I know, couldn't do it I don't think any other could boot with SELinux enforced as secondary ROM. Anyways logcat and dmesg from a bootloop are useful and welcome.
Android "P" is the upcoming ninth major version of the Android operating system. It was first announced by Google on March 7, 2018, and the first developer preview was released on the same day. The second developer preview is expected to be released at the next Google I/O developer conference.
Requirements :
Qcom fully treblized device with 8.1 vendor
Global Bugs :
VoLTE
Device specific Bugs :
Mi5 = Reboot Loop into TWRP (Fixed by restore files)
ANDROID P DP3
installation :
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP3-sGSI.img HERE
- Flash POST-sGSI_1_v0.9.zip HERE
- Flash POST-sGSI_2_v0.12.zip HERE
- Flash POST-sGSI_3.zip HERE
- Flash P-lag-fix.zip file below thread
- Flash incall2.zip HERE
- Reboot
When flashing POST-sGSI untill incall shown error in twrp, Go back to TWRP Home > Mount > check vendor and system
After bootup, you need to install Google Play services 12.8.72 (100400-202717283) HERE
If you are facing with bug Reboot Loop(always reboot into TWRP) you need to restore this backup file from me.
Unzip and put that folder at TWRP/Backups
Goto TWRP > Restore > Check system and vendor only > Reboot.
SECOND METHOD : Restore before 1st boot.
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP3-sGSI.img HERE
- Flash POST-sGSI_1_v0.9.zip HERE
- Flash POST-sGSI_2_v0.12.zip HERE
- Flash POST-sGSI_3.zip HERE
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2101MB).
- Flash P-lag-fix.zip file below thread
- Flash incall2.zip HERE
- Reboot (If stuck at google logo about 3-5mins, try to force shutdown your phone, and turn it on again... it should be work.)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
ANDROID P DP4
CLEAN FLASH IS HIGHLY RECOMMEND
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP4-sGSI-Aonly.zip HERE
- Flash POST-sGSI_1_v0.11.zip HERE
- Flash POST-sGSI_2_v0.14.zip HERE
- Flash POST-sGSI_3.zip HERE
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
- Incall.zip already included. Dont need to flash it.
- Flash p-lag-fix DP4.zip file below thread
- Reboot
If your device become reboot loop into TWRP, like in DP3
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
Click to expand...
Click to collapse
ANDROID P DP5
CLEAN FLASH IS HIGHLY RECOMMEND
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP5-sGSI-Aonly.zip HERE
- Flash POST-sGSI_1_v0.13.zip HERE
- Flash POST-sGSI_2_v0.16.zip HERE
- Flash POST-sGSI_3 v0.2.zip HERE
- Flash lag-fix-DP5 attached below.
- Mount Vendor on TWRP
- Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
- Reboot to System
IF YOU STILL REBOOT INTO RECOVERY AFTER 1ST BOOT.
after flash POST-sGSI_3 v0.2.zip
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
- Incall.zip already included. Dont need to flash it.
- Flash lag-fix-DP5 attached below.
- Reboot
Click to expand...
Click to collapse
Android P Public Release 1 (PR1)
1. Flash JDCTeam Full Treble Support Project
2. UNZIP and flash Pie A-only as System Image.
3. Mount System and Vendor on TWRP
4. Flash POST-sGSI_1_v0.14.zip
5. Flash POST-sGSI_2_v0.17.zip
6. Flash POST-sGSI_3_v0.2.zip
7. Mount System and Vendor on TWRP
8. Flash p-lag-fix.zip (Attached Below)
9. Mount Vendor on TWRP
10. Go to TWRP Advanced - Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
11. Reboot to System
12. Install Google Play Services Apk, reboot and proceed normally.
Click to expand...
Click to collapse
REBOOT LOOP THIRD METHOD by mlira1 and Maixf
1. Flash JDCTeam Full Treble Support Project
2. Flashi DP3/DP4 System Image
3. Mount System and Vendor on TWRP
4. Flash POST-sGSI_1
5. Flash POST-sGSI_2
6. Flash POST-sGSI_3 (skip if going to flash custom kernel)
7. (only if going to flash custom kernel) Flash fix.zip (attached below)
8. (optional) Flash custom kernel
9. (optional) Flash Magisk
10. Mount System and Vendor on TWRP
11. (only if flashed custom kernel) Flash POST-sGSI_3
12. Flash p-lag-fix DP3/4/5.zip
13. Mount Vendor on TWRP
14. Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
15. Reboot to System
16. Install Google Play Services Apk, reboot and proceed normally
Click to expand...
Click to collapse
TIPS
Mi5 'Fingerprint Always On' On Android P (Unlock when screen off, and without press any button. Just touch it FP)
- Root your Mi5 with 16.4/16.6 Treble version
- Install Karnel Auditor
- Go to Tab, Select Custom Control
- Press "+", and import this .json file
- Press 3 dots at there, check 'on boot'
- Reboot
Click to expand...
Click to collapse
Mi5 Fingerprint as Home by rmrbpt
- Root your Mi5 with 16.4/16.6 Treble version
- Install Karnel Auditor
- Go to Tab, Select Custom Control
- Press "+", and import this .json file
- Press 3 dots at there, check 'on boot'
- Reboot
Click to expand...
Click to collapse
Mi5 Double Tap to Wakeup Android P
- Root your mi5 with 16.4/16.6 Treble version
- Open Karnel Auditor
- Go to Tab
- Find 'Wake'
- Turn it on, and apply on boot
- Reboot
Click to expand...
Click to collapse
Disable backlight button
Flash Disable Backlight.zip from Magisk !
Attached below.
Click to expand...
Click to collapse
Fix Battery Drain Issue
Still working on it
Alternative for it
- Dissable Dev Mode in Setting
or
- Try custom karnel
Click to expand...
Click to collapse
Get Blue accent / Pixel theme
Add this to your /vendor/build.prop, save and reboot:
Code:
ro.boot.vendor.overlay.theme=com.google.android.theme.pixel
Click to expand...
Click to collapse
MTP Not Detected
- Goto Setting
- System > Advanced > Dev Options > Choose File Transfer at USB Default Configuration
Click to expand...
Click to collapse
How to flash custom kernel on P GSI
FLASHING CUSTOM KARNEL CAUSING YOU CANNOT ENABLE MTP FORVER AND CHARGING FROM PC/LAPTOP
- Follow instruction from flashing JDC untill POST GSI 2, dont flash POST GSI 3.
- Flash Custom Karnel
- Reboot
- Clean Flash is the only way to fix it for now
Click to expand...
Click to collapse
Fix/Solution Arnova/BSG/other dev Gcam lag when changging between front and back camera on P
- Flash Camera Switch Lag Fix.zip, attached below.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Terribly sorry but at what point did you make that "backup file"? I couldn't fix bootloop without your backup. Just wondering, since it's so large and probably mi5-only maybe you could just give us instructions how to make a working system without using someone else's backup?
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
mansonstein said:
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
Click to expand...
Click to collapse
Try select system only. goodluck.
mansonstein said:
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
Click to expand...
Click to collapse
dont choose system image and vendor image.
but system and vendor only
bukandenny said:
dont choose system image and vendor image.
but system and vendor only
Click to expand...
Click to collapse
Yes, exactly, and I tried just system and just vendor, all stucked in G logo. Someway else to try? What causes reboot loop? Thx
If anyone successed, please let me know how you did it.
mansonstein said:
If anyone successed, please let me know how you did it.
Click to expand...
Click to collapse
3 times i used that way, and always work.
asking someone to do that, its work.
mansonstein said:
If anyone successed, please let me know how you did it.
Click to expand...
Click to collapse
try second methode above.
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
The above link has the images of the issue.
It would be really helpful if someone can help me boot this rom up. Thank you.
Santosh Kolur said:
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
Click to expand...
Click to collapse
Start from beginning.
you need to FORMAT DATA (not wipe data)
then start from beginning dude.
Santosh Kolur said:
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
The above link has the images of the issue.
It would be really helpful if someone can help me boot this rom up. Thank you.
Click to expand...
Click to collapse
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
bukandenny said:
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
Click to expand...
Click to collapse
Thank you. I got it to boot using your solution.
Santosh Kolur said:
Thank you. I got it to boot using your solution.
Click to expand...
Click to collapse
Decrypting internal storage fixes reboots?
Yes it did for me.
First method did it for me, too. I had the bootloop after first reboot and it did the trick, everything is working fine, a bit laggy, but Android P is running smooth on my phone!! I think that's very importat that after first boot you install Play Services as stated in OP and let Google finish its whole Pixel Configuration and updates, then you can try and reboot the phone, if you're hit by the bug, just follow what's in OP.
Few things if you install the GSI and have these issues:
- for Magisk, install version 16.4, just install that after you have set up the phone and stuff, you reboot to twrp and flash it, that's the way it works for me;
- if you have missing network on SIM, just go and configure your apn manually, it'll do the trick;
- for MTP, it's not working for me out of the box, the trick is to enable developers options, go to "Default USB Configuration" or something similar (I have it on italian, so I think that's how it's in English) and select the first one option;
Edit: also there's fingerprint that cannot wake the device, I've read in Telegram groups that some fixes are around for fingerprint, I'll check it out later and report if I find something interesting.
I've suceeded but my FP isn't working, already sent the logcat to the main xda page of GSI
g33k0 b3lk0w said:
I've suceeded but my FP isn't working, already sent the logcat to the main xda page of GSI
Click to expand...
Click to collapse
Cool! So I think there's no solution to this issue at the moment?
aittamattia said:
Cool! So I think there's no solution to this issue at the moment?
Click to expand...
Click to collapse
wait ill upload, u can see my chat on group
HI there, total newbie here. Looked around here and on google but didn't find a solution.
I'm following various step by step guides to install Android Pie on my Poco F1 but I get stuck once the phone boots up in TWRP and asks me password, I cancel and try to install but when I press install the zip files that I have saved on the phone internal storage are not there (Magisk and Disable Force Encryption Treble). ANyone has a similar problem?
Used a different Twrp to root my S8 and didn't have any problem seein the zip files saved in the phone internal storage.
Can someone help please?
THanks a lot,
MAnuel
Dedalus73 said:
HI there, total newbie here. Looked around here and on google but didn't find a solution.
I'm following various step by step guides to install Android Pie on my Poco F1 but I get stuck once the phone boots up in TWRP and asks me password, I cancel and try to install but when I press install the zip files that I have saved on the phone internal storage are not there (Magisk and Disable Force Encryption Treble). ANyone has a similar problem?
Used a different Twrp to root my S8 and didn't have any problem seein the zip files saved in the phone internal storage.
Can someone help please?
THanks a lot,
MAnuel
Click to expand...
Click to collapse
Im facing the same issues like you. here is what i did.
1) Flash back stable miui rom.
2) setup as usual and DONT PUT ANY LOCKSCREEN on it.
3) install twrp recovery with description support.
4) flash disable force encryption. format data , and reboot recovery again.
5) install magisk.
6) install beta miui rom based on android Pie.
success
Sent from my POCOPHONE F1 using Tapatalk
Mohd Haikal said:
Im facing the same issues like you. here is what i did.
1) Flash back stable miui rom.
2) setup as usual and DONT PUT ANY LOCKSCREEN on it.
3) install twrp recovery with description support.
4) flash disable force encryption. format data , and reboot recovery again.
5) install magisk.
6) install beta miui rom based on android Pie.
success
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Thanks for your answer but from point 3 onwards I cannot understand how to do it. What does it mean with description support? How do I disable force encrypition and reboot recovery agfain?
Dedalus73 said:
Thanks for your answer but from point 3 onwards I cannot understand how to do it. What does it mean with description support? How do I disable force encrypition and reboot recovery agfain?
Click to expand...
Click to collapse
im sorry for the typo. i mean decryption support not description.
download at here . find the decrytion support version recovery from @CosmicDan
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
next flash disable force enryption and format your data. then press reboot and select reboot recovery.
Sent from my [device_name] using XDA-Developers Legacy app
Mohd Haikal said:
im sorry for the typo. i mean decryption support not description.
download at here . find the decrytion support version recovery from @CosmicDan
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
next flash disable force enryption and format your data. then press reboot and select reboot recovery.
Click to expand...
Click to collapse
I didn't do the decryption supported one. The correct and original link for the working TWRP is https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004
Dont worry guys if u got confused with the flashing steps of encryption and decryption
[Flashing process from miui or any Custom rom] :-
Install Ptwrp
Format data By typing "YES"
Flash latest Chinese wkly fw
Flash ROM
Flash GAPPS (Optional)
Flash Fcrypt (Optional) [This will make u decrypted]
Reboot
Enjoy
In Custom ROMS Encryption To Encryption :
If you are encrypted and want to switch roms:
1. Remove lock screen password
2. Back up your apps and stuffs
3. Boot to recovery
4. Wipe only Data in advance wipe
5. Flash new ROM and stuffs (Make sure it is properly wrappedkey supported) else can get error or worst.
5. Reboot
6 Done. Profit :good:
Encryption to Decryption :
If u are encrypted and want to get decrypted :
1. First format data (by typing yes)
2. Flash latest Chinese wkly fw
3. Flash rom then gapps then fcrypt zip and
4. Done.. (Magisk is optional after 1st boot).
5. Profit :good:
[ Decryption to Decryption ]
If decrypted and want to stay decrypted
1. Go adv. wipe :- wipe [data, system, vendor , dalvik, caches]
2. Flash ROM
3. Flash GAPPS (Optional)
4. Flash Fcrypt
5. Reboot
6. Enjoy
Note : Make sure you you flash latest Chinese wkly fw.?
Well if you found it useful then Hit the thanks button (it's FREE of Cost)
WELL, IF U LIKE MY WORK Then HIT the Thanks Button . KThanks.
Thanks a lot buddy really needed this. U helped me a lot . Kudos 2 ur hardwork #lifesaver
Hey..what are the steps to move from custom rom (decrypted) to MIUI (decrypted) ?
Thanks ?
sujju said:
Hey..what are the steps to move from custom rom (decrypted) to MIUI (decrypted) ?
Click to expand...
Click to collapse
Who wants to go to miui hahahaha..
anyways
1. Format data
2. Flash Miui recovery zip
3. Flash “no-verity-force-encrypt.zip” file.
4. Reboot
5. ENJOY :good:
RupeshRN said:
Thanks
Click to expand...
Click to collapse
:angel::angel:
sourav24071999 said:
Who wants to go to miui hahahaha..
anyways
1. Format data
2. Flash Miui recovery zip
3. Flash “no-verity-force-encrypt.zip” file.
4. Reboot
5. ENJOY :good:
Click to expand...
Click to collapse
Thanks..
Just to be sure, formatting data would erase internal storage. You mean then I would sideload the zips through TWRP?
sujju said:
Thanks..
Just to be sure, formatting data would erase internal storage. You mean then I would sideload the zips through TWRP?
Click to expand...
Click to collapse
Yes formattinfg data will erase ur storage . NO sideload
sourav24071999 said:
Dont worry guys if u got confused with the flashing steps of encryption and decryption
[Flashing process from miui or any Custom rom] :-
Install Ptwrp
Format data By typing "YES"
Flash latest Chinese wkly fw
Flash ROM
Flash GAPPS (Optional)
Flash Fcrypt (Optional) [This will make u decrypted]
Reboot
Enjoy
In Custom ROMS Encryption To Encryption :
If you are encrypted and want to switch roms:
1. Remove lock screen password
2. Back up your apps and stuffs
3. Boot to recovery
4. Wipe only Data in advance wipe
5. Flash new ROM and stuffs (Make sure it is properly wrappedkey supported) else can get error or worst.
5. Reboot
6 Done. Profit :good:
Encryption to Decryption :
If u are encrypted and want to get decrypted :
1. First format data (by typing yes)
2. Flash latest Chinese wkly fw
3. Flash rom then gapps then fcrypt zip and
4. Done.. (Magisk is optional after 1st boot).
5. Profit :good:
[ Decryption to Decryption ]
If decrypted and want to stay decrypted
1. Go adv. wipe :- wipe [data, system, vendor , dalvik, caches]
2. Flash ROM
3. Flash GAPPS (Optional)
4. Flash Fcrypt
5. Reboot
6. Enjoy
Note : Make sure you you flash latest Chinese wkly fw.?
Click to expand...
Click to collapse
Damn the community really needed this. Good job man.
Could you also add steps to move from MIUI to Custom? (Both encrypted) and vice versa.
im on the previous weekly build of xiaomi.eu rom and i haven't flashed fcrypt disabler, Now how should i update my rom to the latest weekly build? can i use the built-in updater app or should i follow some other procedure? also is it fine to stay encrypted?
Naveenthemi said:
Damn the community really needed this. Good job man.
Could you also add steps to move from MIUI to Custom? (Both encrypted) and vice versa.
Click to expand...
Click to collapse
?? Welcome
Sachin ET said:
im on the previous weekly build of xiaomi.eu rom and i haven't flashed fcrypt disabler, Now how should i update my rom to the latest weekly build? can i use the built-in updater app or should i follow some other procedure? also is it fine to stay encrypted?
Click to expand...
Click to collapse
Use in build ota updater
Hi, can somebody link the fcrypt zip?
Hello,
I was on MIUI , then flashed PE 10,
switched back to MIUI.
Sensors aren't working now !
I tried with MIUI Fastboot rom as well as ZIP file.
still no luck
suggestions please !
How to go back to miui 11 from pe 10 rom
I was in miui 11 encrypted , then i came to pe 10 encrypted , now how can i go back to miui 11 without losing sensor?
rasik107 said:
Hello,
I was on MIUI , then flashed PE 10,
switched back to MIUI.
Sensors aren't working now !
I tried with MIUI Fastboot rom as well as ZIP file.
still no luck
suggestions please !
Click to expand...
Click to collapse
Ofc it wont be wrking.. y dont u guys read changelogs or imp notes if u flash pe then roll back to miui rip to sensors and L1 . For fix check violet official grp. or pe for violet grp.
John878 said:
I was in miui 11 encrypted , then i came to pe 10 encrypted , now how can i go back to miui 11 without losing sensor?
Click to expand...
Click to collapse
Stick to Andriod 10 roms.
sourav24071999 said:
Stick to Andriod 10 roms.
Click to expand...
Click to collapse
That means once you came to PE, than no way to go back to MIUI?
drjmvgami said:
That means once you came to PE, than no way to go back to MIUI?
Click to expand...
Click to collapse
No.. untill memeui fix this
Is it gona encrypt havoc os because it already decrypted?
Hi all and sorry for my bad english in first!!
i live in italy and i've buyed(but still not recieved) one oneplus 9r from china whit oxygenos rom on board..
When it comes i want to root & debloat it, but i've some queustion cause in last year i've used only device with custom rom!.
first of all i wan't to root the phone, but preserve the possibility to update the OS with ota. if i understand right it's possible with magisk, can please someone tell me the correct step to make?
after root i vant to uninstall not necessary app for my utilization (facebook/instagram/netflix, red cable and oneplus account, google app, gdrive, google photo and most of BigG apps cause i'm using only gmail/yt/maps/ an store!).
the question is.... if i uninstall this app it will be re installed in future ota?
Thanks in advice!
Step1 : unlock bootloader, this will wipe the storage, then setup the device once again then enable usb debugging in developer options.
You can use this
Tool to make (tool all in one) your life easier : https://sourceforge.net/projects/tool-all-in-one/files/TOOL_ALL_IN_ONE_1.0.6.1.zip/download
you should select 8t as 9r is not supported officially
at the moment.
Step2: update the phone to latest version , right now it's 11.2.5.5
Step 3: download the same version of the oxygen is ota wether from xda, OnePlus official site , oxygen updater ( make sure it is full version).
Step4: on pc now extract only the payload.bin file in the input of the payload extracter ,
Now use the payload extracter ,
Run .exe and get boot.img .
payload_dumper_tool_by_ius.zip
drive.google.com
(MAKE SURE THE PHONE OS VERSION AND BOOT IMG VERSION IS SAME)
Step 5: install magisk manager on phone, now patch the boot.img that you extracted earlier. Copy this patched boot.img in platforms tool folder(I hope that u have installed the platform tools and adb & fastboot ).
Step 6: open terminal there in platform tools , use the tool all in one to boot your phone in fast boot mode,then flash patched boot.img using.
Fastboot devices
Fastboot flash boot_a patched.img
Fastboot flash boot_b patched.img
Bingo got rooted.
Step 7( optional) : now properly restart the phone by opening magisk , then install universal safety net fix, debloat modules in magisk.
You can use lucky patcher to debloat unnecessary things (which don't exist as it is oxygen os)
Now in future if your phone gets ota make sure you disable all magisk modules then download the full version of ota from oxygen updater & update it locally & do not restart.
go to magisk ,
flash magisk to inactive slot.
restart now,
REnable the modules. (Tip don't enable the lucky patcher module this will put you in bootloop)
enjoy the ota .
@Rajveer chauhan
Do you have instructions to install TWRP?
I even tried to read the thread on the 8t forum, but I didn't understand it very well.
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Rajveer chauhan said:
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Click to expand...
Click to collapse
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
lvints said:
@Rajveer chauhan
Do you have instructions to install TWRP?
I even tried to read the thread on the 8t forum, but I didn't understand it very well.
Click to expand...
Click to collapse
lvints said:
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
Click to expand...
Click to collapse
Way better than twrp just follow the steps u won't lose anything
lvints said:
Is Orange Fox easy to use as TWRP?
Just flash via fastboot? Because I want to keep magisk/root.
Click to expand...
Click to collapse
So how did it go?
Rajveer chauhan said:
So how did it go?
Click to expand...
Click to collapse
I've already downloaded the files, but I haven't tested them yet.
I'll leave it for the weekend, if there's a problem I can solve it with peace of mind.
Sir have you tried changing the font of your 9R?
I've been looking on the magisk forums or some app but I haven't had success.
Yeah I actually use the Einstein font the font manager by androidacy seems to work for me.
Rajveer chauhan said:
Yeah I actually use the Einstein font the font manager by androidacy seems to work for me.
Click to expand...
Click to collapse
I tried this module too, only with Komika font, my favorite.
What version of the module do you use? I tried with the last one (5.5.6) and the font doesn't seem to have been applied.
I'm on OOS 11.2.7.7.
Same version
lvints said:
I tried this module too, only with Komika font, my favorite.
What version of the module do you use? I tried with the last one (5.5.6) and the font doesn't seem to have been applied.
I'm on OOS 11.2.7.7.
Click to expand...
Click to collapse
.
Rajveer chauhan said:
So, 1st of all make sure u are on oos , then simply boot in to bootloader then flash this ofox img file , using the command
fastboot flash recovery name.img then boot into recovery it will ask u your screen lock, then flash this ofox zip file .
this or any recovery are in beta phase , everything works but not 100/100 times.
unzip this and flash the img cuz the img could not be uploaded
this will only work on oos not on any custom rom, uwill not require to format data
& trust me i am not a hacker
Click to expand...
Click to collapse
I flashed the img file and it booted to OrangeFox but I cannot press anything as the screen does not react. What is the solution for it?
It's is compatible with oos 11
Not with oos 12, any custom roms
Rajveer chauhan said:
It's is compatible with oos 11
Not with oos 12, any custom roms
Click to expand...
Click to collapse
I was on OOS 11. The 11.2.8.8.LE28DA.
Flashed it, boot up but cannot press anything. How can I go back to the original boot?
U can unzip the payload.bin and extract the recovery file and flash it in the bootloader and everything goes normal
Rajveer chauhan said:
U can unzip the payload.bin and extract the recovery file and flash it in the bootloader and everything goes normal
Click to expand...
Click to collapse
Thanks I got back to the original boot, but now how can I root with Magisk?
@Rajveer chauhan
Hello sr
Have you updated your 9r for A12 ? If yes, how did you do it? Would it be possible to go from A11 (11.2.8.8) to A12 (C.33)?