Related
Hey guys, Dual Boot Patcher for the Zuk Z2 Pro is officially supported! Check it out here!
Here's the guide:
First of all download these files from here:
DualBootPatcher.apk;
DualBoot tilities.zip;
DualBootPatcher for Windows (only if you want to patch files from windows instead of Android).
Important: Copy DualBootUtilities.zip into your internal memory because if something goes wrong you can "save" your phone thanks to it via recovery.
Install DualBootPatcher.apk;
Open it and give the root permission;
You will be asked to set the kernel in order to use it, confirm of course;
Now you have to tap on "Patch zip file";
After that select the FAB button than "Add flashable zip" and navigate to add the ROM/file that you want to patch;
You have to select the right device and choose "Dataslot" giving a name to the ROM;
Once is done you're ready to install you ROM/file;
Go to ROMs section and again click on the FAB button, "+" and than "Add patched file" and navigate to add the file that you've just patched;
"Keep Location" at the new prompt;
Now just tap on the tick on the top to start. At the end you will have the last 3/4 rows in green with return "0". Return 0 means "everything is ok";
Click on the ROM you want to boot the phone and reboot;
If something goes wrong you can use DualBootUtilities.zip to switch to your primary rom.
Reboot into recovery (press and hold the power button for 15 seconds);
Select recovery and than navigate and find "DualBootPatcher" that you have already copied to your internal memory and install it;
You will have an AROMA Interface to manage everysingle part of your ROMs;
Code:
[url]https://tlgur.com/d/MGanXyEg[/url]
(I noticed that AROMA interface is overturned, if you've got the same bug you have to try to get the right button on the screen via the volume buttons and power button).
Go next and select your primary ROM;
Code:
[url]https://tlgur.com/d/p8DkWkX4[/url]
Than select and press on "Switch to";
Code:
[url]https://tlgur.com/d/74yyryn4[/url]
Now, just click next until finish;
Code:
[url]https://tlgur.com/d/q8leDoyG[/url]
Reboot your device and you're ok.
Code:
[url]https://tlgur.com/d/MGanXyEg[/url]
Q&A:
Q: How can I update my primary ROM?
A: Just patch the file and select "PrimaryROM Updgrade". Flash it.
Q: How can I flash gapps on my secondary ROM?
A: Patch the gapps using as location "Dataslot" with the correct name that you've got for the ROM.
Q: How can I flash Xposed/Magisk on my secondary ROM?
A: Patch the file using as location "Dataslot" with the correct name that you've got for the ROM.
lucaam said:
Do you want a guide to use it?
Click to expand...
Click to collapse
Yes, please
Inviato dal mio Z2 Pro utilizzando Tapatalk
Works great. I'm on Lineage 13 and MIUI 8
Sent from my Z2 Pro using Tapatalk
HOLY CRAP WHERE WAS THIS ALL MY LIFE (or at least the last few months)?!
Instead of losing HOURS and HOURS out of my life just trying to finish running Titanium backups, TWRP backups, copying to computer, rebooting EDL, QFIL firehosing, waiting for ZUI boot, rebooting bootloader, reinstalling TWRP, installing a custom rom, GApps, Magisk/SuperSU/whatever, signing back into Google, doing settings and disabling built-in Chinese crapware, etc. OVER and OVER again... I can just patch the installer and make a new Data Slot? And switch back to ZUI as primary when it's time to get back to work? This is wonderful! Not quite a VM as far as sandboxing it, but still; such a timesaver!
I've never even seen it before, but patching a couple ROMs (AICP June 3 - Magisk removed from zukfans.eu and Mokee 712 June 6), osmosis' UnSU script, OpenGapps current pico release, and current SuperSU, checking free space, creating two Data slots, installing the ROMs with working Gapps and SuperSU into Data Slots 1 & 2, booting both, signing in to my Google account, and getting DBP loaded into both of them so I could switch around between testing environments and going back to ZUI as Primary ROM took all of about an hour and a half.
Daaaaang!
_____
Update: One obnoxious thing - you'll lose your PIN/fingerprint lock once you switch back to primary. As in, you'll put in the correct PIN, and it won't take it, and I presume won't let you in with fingerprint either; same as if you restore a nandroid backup with device protection enabled. To fix: via ADB or custom recovery file manager, you need to delete /data/system/locksettings.db (thanks to @srnoth via this post ).
That's correct, but only happens once when you install a secondary ROM and then switch back to your primary. Switching between the two works flawlessly afterwards. App Sharing works wonderfully. Apk has to be installed on both systems and the option has to be enabled both times. Then the same directory is used across the two systems.
Sent from my Z2 Pro using Tapatalk
Does anybody know how to install Xposed SDK into secondary ROM?
Sent from my ZUK Z2121 using Tapatalk
Great work!
Can we install two stock like: Android 6 in primary and Android 7 as seconde boot?
Thanks !
ZaK512 said:
Great work!
Can we install two stock like: Android 6 in primary and Android 7 as seconde boot?
Thanks !
Click to expand...
Click to collapse
Just added guide.
Can´t flash Lineage 13.
lucaam said:
Just added guide.
Click to expand...
Click to collapse
Can´t flash Lineage 13.
I have AICP 7.1.2 as primary and I flash lineage 13 exactly as you writte in tutorial but when i make reboot to lineage 13 the blue light turns on and it cant boot.
Is possible to use dualboot patcher with nougat and marshmallow custom roms?
almmpt said:
Can´t flash Lineage 13.
I have AICP 7.1.2 as primary and I flash lineage 13 exactly as you writte in tutorial but when i make reboot to lineage 13 the blue light turns on and it cant boot.
Is possible to use dualboot patcher with nougat and marshmallow custom roms?
Click to expand...
Click to collapse
You can because I was on Mokee 7.1.2 and I flashed Flyme that is 6.0. Maybe the problem is the version of Lineage 13. Try another 6.0 ROM.
Thanks
lucaam said:
You can because I was on Mokee 7.1.2 and I flashed Flyme that is 6.0. Maybe the problem is the version of Lineage 13. Try another 6.0 ROM.
Click to expand...
Click to collapse
Tomorrow I try MoKee 6.01 and othe Lineage 13.
Thanks.
Can't install Xposed into secondary ROM: /system can't be mounted. Any suggestions?
Sent from my Z2 Pro using Tapatalk
I cant install Lineage 13 as second rom.
I try with AICP 7.1.2 and MoKee 7.1.2 as primary rom but the second rom Lineage 13 cant boot sstem and only light a fixed blue led.
Anybody know why it is not possible to boot?
May be i have 7.1.2 as primary and 6.0.1 as secundary is the answer for that issue.
Thanks.
if your primary ROM is android 7 based then every secondary ROM need to be android 7 based. same for primary android 6 -> secondary need to be android 6
---------- Post added at 04:36 PM ---------- Previous post was at 04:22 PM ----------
there is a multirom recovery for the zuk z2 pro avalible, too.
what is the better solution in your opinion?
with multirom i have the possibility to select the ROM when i am booting
Multirom recovery?
Where I can find it?
With that multirom TWRP is possible to have dual boot with 7.1.2 and 6.0.1 custom ROMs working?
you'll find it on zukfans*eu and NO it is NOT possible to use 7.1.2/6.0.1 together. its because of the used modem etc. images ...
m45k said:
you'll find it on zukfans*eu and NO it is NOT possible to use 7.1.2/6.0.1 together. its because of the used modem etc. images ...
Click to expand...
Click to collapse
How can you explain 7.1.2 as primary and flyme based on 6.0 as secondary?
It's not possible. Even if this question is asked a thousand times
Has anybody tried wiping and reinstalling their primary room? I have some issues on my primary so I have to do a clean reinstall.
Also, is app sharing possible with multi rom TWRP?
Sent from my Z2 Pro using Tapatalk
Hi!
- Is possible to have the zui as primary rom and another custom as secondary?
- The custom roms as more time of battery?
Thanks
(short) Tutorial in getting your Xiaomi Mi MIX2 encrypted with latest Android 9 (Pie) ROM released by xiaomi.eu (and propably also with the beta ROMs released by Xiaomi/miui.com)
Preparations:
- your phone is unlocked
- a custom recovery is installed on your phone already
- download OrangeFox recovery 9.0-1 or later (others may work too but had not tested for this tutorial / TWRP 3.3.0-0 may produce errors)
- download force-enryption script for Mi MIX2 Android Pie
- download NO enryption restore script for Mi MIX2 Android Pie (reverts fstab config to default - wipe of data needed)
- download latest Android 9 Pie based MIUI ROM (tested only with the modified ROM from xiaomi.eu - official beta ROM may work too)
- optional: download latest Magisk to receive root (may needed by your backup/recovery app to restore your apps within android)
CAUTION!
When folliging this procedure you will loose all current data on your device! DO A APP-BASED BACKUP IN ANDROID FIRST!!! (TWRP or OrangeFox recovery based backups won't work for this procedure!)
Have done your Backup? No? DO IT NOW! really!
Let the phone boot and encrypt itself after flashing the scipt linked in HowTo.
Up to now (bug has been reported) it is to be mentioned that encrypting Xiaomi.EU rom via setting/privacy/encrypt leads direct to PHONE RESET.
FORMAT DATA is required then to get it back to life. @lolo9393 thanks for that hint!
Exact proceedings:
1. you've done a backup eh? - good
2. ... did you save that backup on a other device than your phone? Remember you'll loose all data stored on the phone!!!
3. reboot your phone in your currently installed recovery
3.1 copy the OrangeFox recovery to your device
3.2 select "Install" and choose the OrangeFox recovery .zip file to install (replace your current recovery)
3.3 OrangeFox installer will reboot the recovery after its install
4. Select "Wipe"
4.1 Select "Advanced Wipe"
4.2 Select every Partition exept USB-OTG
4.3 Swipe to Wipe
5. reboot your recovery to recovery again
6. Select "Wipe"
6.1 Select "Advanced Wipe"
6.2 Select "Format Data"
6.3 type in "yes" and confirm that step
7. reboot your recovery to recovery again
8. copy the latest Android 9 Pie based MIUI ROM to your phone
9. copy the latest version of the force-enryption script to your phone
10. Select "Install" and select the Android ROM first then "Add to queue" and select the force-encryption script as second item to flash
10.1 Swipe to Install
11. reboot to system
11.1 go to "Settings"
11.2 scroll down to "SYSTEM SETTINGS" area
11.3 select "Additional settings"
11.4 select "Privacy"
11.5 scroll down to "ADVANCED" area
11.6 check the status of "Encryption & credentials" - it should state "Encrypted"
12. now continue in setting up your system (e.g. enable developer mode, enable advanced power menu, usb debugging if needed, ...)
13. DONE ...
... ok, maybe you're missing your apps and settings - here is a possible way to restore them ... (i personally prefer Titanium Backup)
Root & how to restore apps & app data
14. copy Magisk installer to your device
14.1 reboot your device to recovery
14.2 select "Install" and choose the Latest Magisk-vXX.X.zip file to install (in the log you should read something about "keep forced encryption" - this is good )
14.3 when done - reboot to system again
15. Install Titanium Backup (from a store or as APK from file)
15.1 copy your Titanium Backup or TWRP backup (that could be restored by Titanium Backup Pro) to insternal storage
15.2 restore apps & app data with Titanium Backup (for a detailed HowTo please visit official Titanium Backup Website: https://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-user-guide.html#restore)
15.3 Profit!
That guide may has helped you ...
... say thanks and/or donate for my massive Whiskey consumption -> https://forum.xda-developers.com/donatetome.php?u=496297 :fingers-crossed:
FAQ
Q: Is that procedure ROM update safe? / What if xiaomi.eu releases an ROM update or my ROM has to be reinstalled?
A: When Xiaomi.eu releases an update you have to flash that script right afterwards that update in your favorite recovery. - No further actions should be needed. This procedure has to be repeated for every ROM update or reinstall.
Procedure is verified as working with update 9.5.9 up to 9.6.27Q: Does TWRP recovery work also?
A: There is feedback that TWRP 3.3.0-0 does not work as intended (THX @mguz on post 11 for the feedback)
Maybe TWRP 3.3.1-0 that was released short ago solves that problem ...
How to update later?
cineq said:
How to update later?
Click to expand...
Click to collapse
... hmm sorry did not get what you like to do - could you please describe in detail what you mean/like to achieve?
When there will be next build of xiaomi.eu what is the procedure to update it? Just install new in recovery without any wipes? Is force-encryption script needed when updating?
cineq said:
When there will be next build of xiaomi.eu what is the procedure to update it? Just install new in recovery without any wipes? Is force-encryption script needed when updating?
Click to expand...
Click to collapse
When Xiaomi.eu releases an update you have to flash that script right afterwards that update in your favorite recovery.
No further actions should be needed.
Thanks for the hint - will update the guide with that question/answer
raupe said:
When Xiaomi.eu releases an update you have to flash that script right afterwards that update in your favorite recovery.
No further actions should be needed.
Thanks for the hint - will update the guide with that question/answer
Click to expand...
Click to collapse
Procedure is verified as working with update 9.5.9 -> 9.5.16
raupe said:
(short) Tutorial in getting your Xiaomi Mi MIX2 encrypted with latest Android 9 (Pie) ROM released by xiaomi.eu (and propably also with the beta ROMs released by Xiaomi/miui.com)
@raupe
VERY good work.
Very useful for people having security concern when using a TWRP.
My comments:
-This procedure is valid with any latest 3.3. TWRP version that can decrypt now. (?)
- This is applicable to all XIAOMI phone under PIE. (Fstab must be exchanged in the zip tool in order to fit with the phone model)
- NOTE :
Up to now (bug has been reported) it is to be mentioned that encrypting EU rom via setting/privacy/encrypt leads direct to PHONE RESET and FORMAT DATA required.
Regards
Click to expand...
Click to collapse
Hi,
- download force-enryption script for Mi MIX2 Android Pie
- download NO enryption restore script for Mi MIX2 Android Pie
both links are down, re-upload possible ?
EDIT: Links are working now
Help out a noob. Why would one need to have phone encrypted? Whats the purpose of encryption?
I'd like to update to 9.5.x Xiaomi.eu Pie but hear complaints of GCam, SuperSU, FindDevice, fingerprint, etc not working. Would encryption help these issues?
stoshie said:
Help out a noob. Why would one need to have phone encrypted? Whats the purpose of encryption?
I'd like to update to 9.5.x Xiaomi.eu Pie but hear complaints of GCam, SuperSU, FindDevice, fingerprint, etc not working. Would encryption help these issues?
Click to expand...
Click to collapse
Its not about encr. Problems.Pie uses vendor for most stuff now and for gcam is needed additional line in build prop to make it work.magisk 19 can root it without problems
Hi,
thank you for this helpful tutorial.
First time I tried with TWRP 3.3.1-0 and it did not work (Bootloop).
With OrangeFox Recovery it works as described.
Regards
On official TWRP-3.3.1-1 works as intended, thanks!
I recently started experimenting with Android 10 and found a fully working setup. So I'm deciding to share my current setup
#USE THIS AT YOUR OWN RISK!
I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE DUE TO A BAD ROM FILE OR ELSE!#
#BUGS: NFC isn't working on downloadable build
You tell me#
NOTE: you can also use his newer builds. BUT those aren't preconfigured. For patches that you will need see 3rd post!
Requirements: latest twrp from official source,
Oreo firmware.
This Google play services APK:
https://drive.google.com/file/d/1V8ByPJx_hOoPpQNrG0LQcXzhHpFflN-I/view
I think that's it
Step 1: Download jarlpenguin's latest treble build here:
https://github.com/MontanaDevelopme.../lineage-16.0-20190713-UNOFFICIAL-montana.zip
Install it and wait for it to go into the lineage is setup screen. Reboot to recovery (you can download a rom by just going through setup, but all installed apps will be wiped!)
Step 2: if you haven't already download a rom of choice with a build date similar to this: 201910##
These builds should work with sim-card and possibly gapps
But I recommend this rom (please extract it first, otherwise you won't be able to flash this) : https://mega.nz/#!EE11mZyC!_45oKcdNv8djsA8CEh2ZVoTDkic3BCpLfFfU9TLUhes
Step 3: wipe system and data and head to the install section
Step 4: hit "install image" in the bottom right corner and navigate to the location of the extracted .img file
Step 5: select "system image" after pressing it and swipe to flash
Step 6: wait for it to boot (this can take quite a while so, please be patient!)
Step 7: when the device is booted, immediately head into the files application and install the Google play services app from the folder you put it in.
Step 8: after a while, the "completing system update" message should disappear. But there still is one problem... As this is a ported rom (I know I didn't mention this before) this still has the "system updater" app. So, you might disable that, otherwise it flashes a incompatible rom file.
ENJOY!
###ROOT###
to root the ROM, you need phh magisk, you should easily find it on Google or a search engine of choice. THE NORMAL BUILDS DON'T WORK, phh magisk is made for Android 10 treble builds using phhussons base or patches. That's why the normal version doesn't work
If you need help, feel free to contact me on telegram! @Rush
Sneak 100 profile picture
###GCAM###
To use gcam you should flash a Magisk module called:
"Several fixes for Moto G5/G5s"
Some apks may still not work though... As I haven't figured one out which 100% works
###Alternative ROMs###
To use alternative ROMs you will need to (most of the time) use a different lineage OS version by JarlPenguin together with only the boot & vendor images listed below:
https://drive.google.com/folderview?id=1QztsGvkhURcoCp-FjI40mvUpLp5NHSpj
Also, you know that a room won't boot when TWRP crashes, so don't even try, and no, even though the lineage 17.1 alpha build does "support" project treble, it doesn't have any better compatibility with Android 10 ROMs,
The only ROMs with at least some features I could get running is really just Pixeldust X ported from the pixel 1 using erfans tools
And this also works, of you are using (again) a newer or the latest build together with patches (see boot&vendor images above):
https://sourceforge.net/projects/zj...el-Aonly-10-20191120-GSI.img-1640.7z/download
Don't forget to extract this first! /\
Note: this newer build has NO MOTO GESTURES AT ALL
Sadly, I don't think there is a fix to that
### EVOLUTION X ###
I finally found a build which is working but. Uhhhh is kind complicated to bit to it first time
Basically you follow the normal tutorial, and then replace the advertised build with the latest 202001xx build by jarl
then wait for boot
Then reboot to recovery, and wipe system and data.
Reboot (I know that nothing is installed rn)
Select recovery and boot
Flash the evolution X .IMG fine and hope for it to but crash
Sadly,
There isn't even a guaranteed boot if you do that
But it will do the job good enough
Also, you won't need the GMS services APK anymore as this has everything already updated to ****
Please DONT flash the vendor and boot image patches as these will not allow the device to boot for some godforsaken reason
Link (please extract first):
https://sourceforge.net/projects/de...lution-X_3.3_20191111_ARM64-A.img.xz/download
First of all this is not my work is just tried this rom and its preety stable. Thanks to developers @phhusson @Magendanz
DESCLAIMER :use it your own risk.
So finally this rom booted on galaxy tab SM-T515 everything thing is working with small bugs as mentioned below.
Download files given below:
Bugs :
1)voLTE: not working tried phh treble settings to solve the issue but no luck.
Other networks, data calling works perfectly
2)MTP: mtp not working but you can transfer files after booting device in TWRP mode
3)audio not recording in videos use open camera app and go to settings and set default audio as a source.
4)For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Reverting to Samsung oneui:
For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Download firmware using this app:
Download link for Android/Linux/Mac/Windows:
Releases · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Linageos18.1 user restore your oneui backup using twrp or use ODIN firmware.
Except these you can check and tell me I didn't found anything till now
Download this gsi fileonly this is compatible)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20211010-UNOFFICIAL-treble_a64_bvS-vndklite.img.xz/download
Download arm 32 android 11 gapps :
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Linageos 19 android 12Gapps included)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.0-20220114-UNOFFICIAL-treble_a64_bgS.img.xz/download
Download magisk zip:
https://dl.magiskapp.com/MagiskZip/Magisk-v23.0.zip
If you gets device certification error follow this post:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
XZ file extractor android app:
GZ & XZ Extract - File Opener - Apps on Google Play
Extractor tool for tar, tar.gz, gz, gz2 & xz files. Just few taps for result
play.google.com
Process :
1)Download all files given first extract xz file gsi file using xz extractor you gets img file.
2)Now transfer gsi.img, gapps and magisk file in tablet.
3)boot tablet to TWRP MODE
4)Now first select wipe >advance wipe>select system> slide
5) now go back click install click install img you will see your file click on it and select system partition and enter.
6) now we have to install gapps but we need to first resize system partition so
First click mount and mount system Partation now go to wipe>advance wipe>select system >clcik repair >click resize
7)now click install and. Select gapps and flash.
8)now go back install magisk and hit reboot.
After reboot you may face device certification error so to solve this go to magisk and install magisk hide props configuration module and reboot your phone.
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Follow this video i will update thread soon
Android 11 Linageos 18.1
Android 12 lineageOS 19
How's the battery life?
works offline charge?
Pinage said:
How's the battery life?
Click to expand...
Click to collapse
Best battery life
Spawacz_Reduktor said:
works offline charge
Click to expand...
Click to collapse
Yes
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Sukrith said:
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Click to expand...
Click to collapse
Yes same time but that has grafix shutter issue same like gsi
pankspoo said:
Yes same time but that has grafix shutter issue same like gsi
Click to expand...
Click to collapse
There seems to be a new build, can you maybe try? It's based on 6th November build.
Sukrith said:
There seems to be a new build, can you maybe try? It's based on 6th November build.
Click to expand...
Click to collapse
Ok
In January I installed 17.1 using this ROM. Do I need to go through the whole process of resizing the partition, since I already did it for 17.1?
Never mind! I went ahead and installed it following the instruction . It works, thanks!
bedwere said:
Never mind! I went ahead and installed it following the instruction . It works, thanks!
Click to expand...
Click to collapse
Are you happy with this ROM?
Krekle said:
Are you happy with this ROM?
Click to expand...
Click to collapse
Yes, it's very stable.
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Shawnashley said:
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Click to expand...
Click to collapse
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
HansMampf said:
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
Click to expand...
Click to collapse
I can only answer some of your questions:
- Magisk is only used for root. It's not required.
- Mounting /system in TWRP or in a File explorer doesn't seem to be possible.
- GApps is built in to roms with "...bgS.img.xz". For vanilla roms without gapps download the "...bvS.img.xz"file.
- For LOS 19, I flashed treble_a64_bgS and didn't have an issue. I can't comment on the vndklite version or what it's used for since I never tried it.
betacrypt said:
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
Click to expand...
Click to collapse
Any idea about success of I am running Megadanz 11.0 ROM?
Shawnashley said:
Any idea about success of I am running Megadanz 11.0 ROM?
Click to expand...
Click to collapse
It's a good rom and works very well. I was using it before I upgraded to LOS19.1.
Hey there!
I Installed this a couple of weeks ago, but has to reinstall nexus stock 11.0 pretty quickly, as after spending an evening trying to fix issues, it just wouldn't work.
Issues:
1) App crashes are constant. I cannot open Chrome, YouTube, Google Podcasts, Twitter - they all crash to launcher. - Cache, dalvik and data was cleared, still nothing
2) Gesture Navigation is missing - is it meant to be?
3) Magisk installs successfully,, but is then not recognised by the app, meaning no modules. - Is that normal?
Does anyone have any idea on how I could fix these issues, so I can install again?
Many thanks
I've managed to successfully install LineageOS 19.1 on my Zenfone 8 but I didn't realise you needed an entirely different release to use MicroG.
So I am now trying to install the LineageOS for MicroG release but I'm running into problems:
The MicroG release is a few weeks older than the LineageOS one. When I tried installing it I got an error "SPL is considered a downgrade" and it wouldn't let me install it.
The MicroG release doesn't provide a `vendor_boot.img` file which is required according to the LineageOS instructions. I tried using the file from the regular LineageOS release and it seemed to work the first time but now it won't boot into the recovery mode at all; it just boots into the bootloader menu.
I saw people saying that the MicroG release is missing some img files but I used the payload-extractor Python script and I cannot see any difference between the list of files in the MicroG release and the original LineageOS one. They both contain 29 img files.
I saw posts in the development thread that people are having similar struggles so I'm not sure how to proceed.
Ultimately, my request is: can someone please outline an easy-to-follow approach on how to install LineageOS with MicroG on the Zenfone 8?
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Therefor I would recommend to install another OS:
OmniROM https://omnirom.org/
The OS images for OmniROM for the Zenfone 8 can be downloaded here:
https://dl.omnirom.org/zenfone8/
A new OS image of OmniROM with MicroG is created every Sunday.
The OmniROM image can be installed via sideload using the recovery image from the LineageOS.
And it works without problems (including MicroG) You can even install a patched version of the original playstore that will work with MicroG.
In case you want to stay with the LineageOS I recommend to use the LineageOS image without MicroG and use the NanoDroid image (which contains MicroG) from https://nanolx.org/
I used NanoDroid (installed as Magisk Module) on my previous phone several years for which no OS image with integrated MicroG exists.
regards
Bernd
bnsmb said:
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Therefor I would recommend to install another OS:
OmniROM https://omnirom.org/
The OS images for OmniROM for the Zenfone 8 can be downloaded here:
https://dl.omnirom.org/zenfone8/
A new OS image of OmniROM with MicroG is created every Sunday.
The OmniROM image can be installed via sideload using the recovery image from the LineageOS.
And it works without problems (including MicroG) You can even install a patched version of the original playstore that will work with MicroG.
In case you want to stay with the LineageOS I recommend to use the LineageOS image without MicroG and use the NanoDroid image (which contains MicroG) from https://nanolx.org/
I used NanoDroid (installed as Magisk Module) on my previous phone several years for which no OS image with integrated MicroG exists.
regards
Bernd
Click to expand...
Click to collapse
Thanks for the recommendation. I would prefer to stick with LineageOS because of the larger community.
NanoDroid looks good but I don't think it'll be suitable. It looks very complicated and talks about patching ROMs for signature-spoofing support. It also doesn't actually say how to install it (the documentation literally just says "install NanoDroid" as one of the steps...) and finally it only supports Android 11 at the moment.
If anyone else has hints about using MicroG with LineageOS on a Zenfone 8 please let me know. I feel like it really shouldn't be this hard.
hawkins22 said:
Thanks for the recommendation. I would prefer to stick with LineageOS because of the larger community.
NanoDroid looks good but I don't think it'll be suitable. It looks very complicated and talks about patching ROMs for signature-spoofing support. It also doesn't actually say how to install it (the documentation literally just says "install NanoDroid" as one of the steps...) and finally it only supports Android 11 at the moment.
If anyone else has hints about using MicroG with LineageOS on a Zenfone 8 please let me know. I feel like it really shouldn't be this hard.
Click to expand...
Click to collapse
I would prefer to stick with LineageOS because of the larger community.
Click to expand...
Click to collapse
Understand
But for the records:
Signature-spoofing is only required to use all features of MicroG , e.g. to use the patched Playstore. If you don't need that you can ignore this.
The best method (IMHO) to install NanoDroid is:
- install Magisk into the booot partition
- install the ZIP file with NanoDroid using TWRP
Nanodroid will then install MicroG as Magisk Module .
regards
Bernd
Hello,
The issue is due to the fact that LOS+MicroG has a long delay in releases (at the time of this message, the latest LOS version is 2023-02-03 and the latest LOS+MicroG 2022-12-22). I think it is an issue because the main site announces a build every two weeks, and there are some tickets in their Git repository about this.
Anyway, I had the same issue few weeks ago and I managed to install LOS+MicroG using an old vendor_boot image; indeed you have to use the one provided by the LineageOS wiki, but you have to use one older than the LOS+MicroG release to avoid the SPL issue.
Unfortunately, I had a look and the previous version was deleted on their website since I installed my phone and I can't provide the one I used because I removed the file...
So I'm afraid you have to wait a new LOS+MicroG build or find a old vendor_boot.img to proceed.
But I agree with you: it's a shame that there is no straightforward way to install LOS+MicroG. It was easy in the time, but now it's more complicated to manage due to phones specification (I guess, I'm not a ROM dev) - but yes I think that discourage a lot of people to use it.
Good luck.
bnsmb said:
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Click to expand...
Click to collapse
Yeah, that's why "LineageOS for microG" exists in the first place. It is a fork of LineageOS where signature spoofing was enabled. So, there is no issue using LineageOS for microG. Please educate yourself before posting things like this.
"I saw people saying that the MicroG release is missing some img files but I used the payload-extractor Python script and I cannot see any difference between the list of files in the MicroG release and the original LineageOS one. They both contain 29 img files."
Click to expand...
Click to collapse
There are (or at least in the past were) indeed some files missing from "LineageOS for MicroG" for the Asus Zenfone 8. It is/was a bug confirmed by the developers. I reported it to them, maybe they fixed it in the meantime. This would be good news! I haven't checked for a while.
However, then I don't understand why you say "The MicroG release doesn't provide a `vendor_boot.img`". So why exactly is this file missing and where did you find it in the official LineageOS? And for what step do you need it? I don't remeber that I was using this file for installing LineageOS. Only Magisk needed that file. But it was easy to retrieve from the extracted payload.
I managed to install it successfully using TWRP instead of Lineage's own recovery image. Maybe TWRP simply doesn't care if you're "downgrading" and lets you flash anyway?
The final step-by-step process I used was something like this:
Unlock the phone's bootloader using the official ASUS unlocking tool APK.
Restore the phone to its stock Android 12 state using the ASUS "raw" image (instructions):
https://dlcdnets.asus.com/pub/ASUS/...KS-31.1010.0410.61-MR0-2204-user-20220422.zip
Flash the "vendor_boot.img" file from the regular LineageOS release as detailed in the instructions.
Install TWRP recovery instead of the LineageOS recovery image.
Use TWRP recovery to flash the LineageOS-MicroG ROM.
Mario545 said:
However, then I don't understand why you say "The MicroG release doesn't provide a `vendor_boot.img`". So why exactly is this file missing and where did you find it in the official LineageOS? And for what step do you need it? I don't remeber that I was using this file for installing LineageOS. Only Magisk needed that file. But it was easy to retrieve from the extracted payload.
Click to expand...
Click to collapse
The vendor_boot.img is required according to the LineageOS installation instructions and is provided as a separate download on the same page.
However after extracting both the LineageOS and the LineageOS-MicroG releases, I believe the vendor_boot.img files are actually identical (same filesize) so you can probably use them interchangably anyway.
I see, probably was not required when I was installing an earlier version of LineageOS.
Anyway, vendor_boot.img should additionally be included in your payload file from the archive. The one they provide for download is probably just an extracted one to make it easier.
Mario545 said:
I see, probably was not required when I was installing an earlier version of LineageOS.
Anyway, vendor_boot.img should additionally be included in your payload file from the archive. The one they provide for download is probably just an extracted one to make it easier.
Click to expand...
Click to collapse
AFAIK the vendor_boot.img is also required by the LineageOS recovery image necessary to install the LineageOS image.
Therefor it must be installed before booting the LineageOS recovery.
regards
Bernd