Related
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
codearm2 said:
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
Click to expand...
Click to collapse
-Format data
-wipe
-use otg drive since format data delete everything
-flash firmware newest 8.5.10 minimum requirment for oreo
-flash rom
-flash gapps
-reboot
evanlocked said:
-Format data
-wipe
-use otg drive since format data delete everything
-flash firmware newest 8.5.10 minimum requirment for oreo
-flash rom
-flash gapps
-reboot
Click to expand...
Click to collapse
tried it all, still bootloop
codearm2 said:
tried it all, still bootloop
Click to expand...
Click to collapse
flash any miui dev rom beyond 8.5.10 using miflash
reboot once ...
flash twrp ...
push any oreo rom (ie. LOS 15.1) and gapps while in recovery ...
Install that rom and gapps ...
reboot to twrp ...
format data ...
reboot again to twrp ...
reboot to system ...
3Dota said:
flash any miui dev rom beyond 8.5.10 using miflash
reboot once ...
flash twrp ...
push any oreo rom (ie. LOS 15.1) and gapps while in recovery ...
Install that rom and gapps ...
reboot to twrp ...
format data ...
reboot again to twrp ...
reboot to system ...
Click to expand...
Click to collapse
not working
Flashed 8.5.10 rom, ended in bootloop
flashed the LOS 15.1 and GAPPS, still bootloop
so, any one?
codearm2 said:
so, any one?
Click to expand...
Click to collapse
Your custom recovery needs to be an Oreo version compatible, so you can install oreo based roms on it.
Try to update to early version.
Regards.
codearm2 said:
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
Click to expand...
Click to collapse
try updating firmware and twrp and flash lazy flasher zip after rom instalation hope it fix . *Lazy Flasher zip is must
Steffanom said:
Your custom recovery needs to be an Oreo version compatible, so you can install oreo based roms on it.
Try to update to early version.
Regards.
Click to expand...
Click to collapse
already 3.2.3 version which I believe supports oreo rom
Tsuzan said:
try updating firmware and twrp and flash lazy flasher zip after rom instalation hope it fix . *Lazy Flasher zip is must
Click to expand...
Click to collapse
didnt work, still bootloop
codearm2 said:
so, any one?
Click to expand...
Click to collapse
so ... what last rom boot fine in your Mi5?
3Dota said:
so ... what last rom boot fine in your Mi5?
Click to expand...
Click to collapse
any nougat rom works well
tried flashed 8.5.10 rom, still bootloop
codearm2 said:
any nougat rom works well
tried flashed 8.5.10 rom, still bootloop
Click to expand...
Click to collapse
this is quite weird ... since if you install any nougat ... you'll sure receive OTA update to oreo (dev or stable) ...
why dont you take that OTA?
3Dota said:
this is quite weird ... since if you install any nougat ... you'll sure receive OTA update to oreo (dev or stable) ...
why dont you take that OTA?
Click to expand...
Click to collapse
yes, installing the OTA based on OREO update also cause bootloop happens
basically, anything OREO based, whether it's ota or flashing it manually through TWRP, ZCX TWRP, or Mi Flash cause bootloop
Have you wipe your internal partition?
I think we need to wipe all partition after installing firmware when come from nougat to Oreo, because Oreo have new vendor partition.
At least you should use twrp-3.2.1-1-gemini
Sent from my MI 5 using Tapatalk
codearm2 said:
not working
Flashed 8.5.10 rom, ended in bootloop
flashed the LOS 15.1 and GAPPS, still bootloop
Click to expand...
Click to collapse
Try reflashing latest twrp via fastboot (not from within twrp).
After wiping all partitions (also mount and wipe vendor) and formatting data, reboot to recovery before flashing the ROM to access the data partition correctly again.
Then also try to boot (would go with a custom ROM) without any gapps, mods or root first, to further center the problem.
What happens now?
Have the same problem
Try to install latest build via fastboot --> failed
Try to install miui nougat based work, ota update to oreo based -->bootloop
Also try to flash all included internal storage but the problem still occured
Any miui nougat based and aex mod 5.1 work fine in my phone
Install lazy flasher before installing anything like SuperSU...
masruri03 said:
Have you wipe your internal partition?
I think we need to wipe all partition after installing firmware when come from nougat to Oreo, because Oreo have new vendor partition.
At least you should use twrp-3.2.1-1-gemini
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
already wiped, still not working
Phil_Smith said:
Try reflashing latest twrp via fastboot (not from within twrp).
After wiping all partitions (also mount and wipe vendor) and formatting data, reboot to recovery before flashing the ROM to access the data partition correctly again.
Then also try to boot (would go with a custom ROM) without any gapps, mods or root first, to further center the problem.
What happens now?
Click to expand...
Click to collapse
flashed latest twrp via fastboot, also already wiped all partition included mount and wipe vendor, also formated the data and reboot first before flashing the rom, boot without any gapps, still it doesnt work
reysack said:
Have the same problem
Try to install latest build via fastboot --> failed
Try to install miui nougat based work, ota update to oreo based -->bootloop
Also try to flash all included internal storage but the problem still occured
Any miui nougat based and aex mod 5.1 work fine in my phone
Click to expand...
Click to collapse
yeah, practically the same with mine
brhnahmad05 said:
Install lazy flasher before installing anything like SuperSU...
Click to expand...
Click to collapse
tried, doenst work
codearm2 said:
flashed latest twrp via fastboot, also already wiped all partition included mount and wipe vendor, also formated the data and reboot first before flashing the rom, boot without any gapps, still it doesnt work
Click to expand...
Click to collapse
Puh, don't know.
Do you have an old backup of your efs partition lying around?
If so, try restoring that.
If that also doesn't help, I'm through with my math here, I think...
Flash a Lineage OS 14.1 build without GApps but with a firmware that supports Oreo. Then, go to developer settings, turn on ADB and run adb devices on your computer so that the RSA Fingerprint pops up. There, make sure you tap on remember this computer and click ok.
Now, do an update to Lineage 15.1 without wiping anything. As soon as you reboot your phone, connect it to your PC and try to get a logcat. Paste the logcat here and we'll be able to see what's actually going on.
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Did you tried another recovery? Try Batik Recovery!
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Amir_espie said:
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Click to expand...
Click to collapse
Sure,will give it a go
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Solved Magisk Error!
I've been using Pixys OS on my Redmi 4A and it works fine smoothly. I recommended to clean wipe before installing. Android Pie us amazing and I've installed stable version. Do backup before clean wipe.
For Magisk I recommended this: https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html?m=1
It worked for me. Also go through this step before any custom ROM. Do let me know the status
Anirudh15 said:
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Click to expand...
Click to collapse
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
You have two problems.
Anirudh15 said:
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
You need to flash the twrp separated vendor version by my friend Offain https://androidfilehost.com/?fid=962187416754475993
The other problem with the decryption:
You must enter in the twrp press wipe and format data. Type yes and then reboot into twrp again. After that flash the rom and gapps and you will not have the decryption problem again
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
I had the same problem. Its because your phone is encrypted. The only solution I found is to boot the device into fastboot and using command: [fastboot format userdata] on PC. This will wipe all data off your phone so do backup. It removes encryption and now you can install any custom rom.
Decrypt ur phone first then flash, use twrp vendor
athish said:
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
Click to expand...
Click to collapse
Format Data was the only thing that worked for me. First backup everything on your mass storage.
Hi everyone,
I'm new here though but am a Xiaomi user from the beggining of Xiaomi into devices with Redmi Note 3G Enhanced.
Currently, I own a Redmi 4X and I would like your expert lights please. I've flashed the latest twrp from twrp.me for my santoni device. Then flashed the latest build from LineageOS Official source + Gapps before booting up for first time. Everything was working perfectly until I decided to flash the latest update of LineageOS as I've seen in my updater it was released. So, I downloaded it through the updater and tried to flash it...
I came up with this "Failed to unmount /system (device or resource busy)" after that re-booted to LineageOS and everything was messed up with Google Services & Apps etc. Then I went back to twrp recovery and tried to flash again the rom but I was still getting that message so I understood something am doing wrong. Also santoni has dm-verity enabled which I know something about but just an info. I really wanna stick with LineageOS on my Redmi 4X forever but I'm afraid to flash it again. I've flashed MIUI 10 Beta by fastboot but now I wanna go back to LineageOS forever (addicted).
My only problem is: After successfuly flashing LineageOS and Gapps, I cannot apply (flash) updates to update the ROM to the latest nightly build due to this error above.
Kind regards,
peryson
Try with different recovery. For example with this
Harukey said:
Try with different recovery. For example with this
Click to expand...
Click to collapse
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
peryson said:
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
Click to expand...
Click to collapse
You can download latest Lineage OS build and dirty flash it (without any wipes) (so you can unmout system parition). And I don't see any issue in using unoffical twrp.
I also have experienced same error once during upgrade "failed to unmount /system"
Eventually I wiped everything and did clean flash from scratch. This is really annoying issue and demonstrates that upgrade system is not 100% reliable for some reason.
I'm not sure however is it Lineage or twrp issue.
Device variant: XT19121-2 James
Chipset: MSM8920
After repeated failed flashes I am on stock firmware using this guide. Phone boots and works normally right now, but I can't seem to flash any Custom ROMs on to my phone. I was using this post to flash Lineage OS 15.1, which worked successfully at first, but the WiFi wasn't working so I reflashed it. It still didn't work so I did it again, wiping Dalvik/Cache too. After the second flash attempt, my phone began to only flicker on and off. I made sure to always clean flash, factory resetting, wiping Cache and Dalvik, even formatting data, but no matter what I do it doesn't work. Also attempted other GSI images (arm, A-only) like AOSP, ResurrectionRemix and phhusson's Lineage OS 15.1 But they all failed too. I am using TWRP for James v 3.3.1 although I did also try other TWRP images like v 3.2.1 . But it makes no difference. Also used Magisk v19 like some guides suggested but whether I have Magisk or not, it doesn't work. Even made sure to push the fstab.qcom file to /vendor. Anytime a Custom ROM is flashed whether zip or GSI img it goes past the initial "bad key" or "N/A" screen and starts flickering on and off. Bootloader and TWRP works fine, but that's about it. Everytime a flash fails I go back to stock firmware (which always works) and try another ROM. I wonder why the first attempt worked but doesn't anymore even if I mirror the exact steps I took from stock. If anyone has any solutions I would be really grateful. Let me know if you need any more information.
have you taken any recent OTA updates?
mikeshutte said:
have you taken any recent OTA updates?
Click to expand...
Click to collapse
Nope. Still on the 8.0.0 version the stock firmware comes in.
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
I also just noticed you are using the latest version of TWRP 3.3.1. I'm not sure if you originally rooted and installed TWRP with the original patched version by Cody or not, but if so make sure with the new version that you format your data partition to f2fs. As this will ensure correct mounting of the data partition.
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
I am having the same issue
Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere
I eventually got RR to boot on the james xt-1921-3 I installed XT1921-3_JAMES_T_MPCS_8.0.0_OCPS27.91-150-5-1-3_cid21 as a base, then used boot and vendor partitions from JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC and it finally worked.
tkhan7916 said:
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
Click to expand...
Click to collapse
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Download the file from this post https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 , then using fastboot, flash the vendor and boot img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
then boot into recovery and flash the file from that post to disable dm-verity and force encrytion, after that flash magisk, then reboot to bootloader, at command prompt-
fastboot erase userdata
fastboot erase cache
fastboot reboot
that should get you booted - profit
mrbox23 said:
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Click to expand...
Click to collapse
Do you still have that back up by any chance and could ypu send it to me?
I have been using custom roms for years.
I wanted to try flashing GSI images, and i decided to start with Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img
I installed twrp-3.5.2_9-0-z2_row
I completely wiped everything, system/cache/data etc.
I flashed Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img then NikGapps-basic-arm64-11-20210514-signed.zip.
Rebooted.
Phone is instantly resetting right after the ZUK logo goes away. stuck in boot loop. Am i doing something wrong ?
hash02 said:
I have been using custom roms for years.
I wanted to try flashing GSI images, and i decided to start with Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img
I installed twrp-3.5.2_9-0-z2_row
I completely wiped everything, system/cache/data etc.
I flashed Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img then NikGapps-basic-arm64-11-20210514-signed.zip.
Rebooted.
Phone is instantly resetting right after the ZUK logo goes away. stuck in boot loop. Am i doing something wrong ?
Click to expand...
Click to collapse
Can you send me the link of the thread where you saw your rom?. Pretty sure theres a tutorial in it.. You are missing some important step like flashing create vendor.zip or repartitioner.zip and some other stuff.. Give me the link...
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Your question is a bit weird because this is a GSI. it's not model specific and should apply to things treble.
So it's not "my rom" it's just a gsi rom that should just work, right ? (unless i did something wrong)
Procedure was standard, clean, no dirty flashing.
Flash img, then gapps, then reboot.
I remember the instructions were for an older version of havoc, i just took the latest build because that's what you usually do ???
Regardless, this is not a HAVOC issue, I later tried with caos build caos-v307-210507-arm64-agZ.img. The exact same behavior happened.
hash02 said:
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Your question is a bit weird because this is a GSI. it's not model specific and should apply to things treble.
So it's not "my rom" it's just a gsi rom that should just work, right ? (unless i did something wrong)
Procedure was standard, clean, no dirty flashing.
Flash img, then gapps, then reboot.
I remember the instructions were for an older version of havoc, i just took the latest build because that's what you usually do ???
Regardless, this is not a HAVOC issue, I later tried with caos build caos-v307-210507-arm64-agZ.img. The exact same behavior happened.
Click to expand...
Click to collapse
Redo the process and try to flash the gsi only without gaps then boot..
r
ivanjudge said:
Redo the process and try to flash the gsi only without gaps then boot.. You can check this out also maybe it will help? https://forum.xda-developers.com/t/zuk-z2-pro-project-treble-android-10-11-12-gsi-ab.4197355/
Click to expand...
Click to collapse
to flash a GSI image first you should wipe all except internal storage.
then install a Vendor ie; Basic roms like AEX, ARROW OS according to the GSI Version
if you GSI image is based on Android 10 then you should flash a android 10 rom from aex or arrow, then flash the gsi to system, then reboot
prc.kailas said:
to flash a GSI image first you should wipe all except internal storage.
then install a Vendor ie; Basic roms like AEX, ARROW OS according to the GSI Version
if you GSI image is based on Android 10 then you should flash a android 10 rom from aex or arrow, then flash the gsi to system, then reboot
Click to expand...
Click to collapse
So, the gsi flashing just copies the image-byte-by-byte to the /system partition ?
Just like dd on linux ? Blind transfer from one direction to the other ?Is this why you recommend flashing "basic roms", so that by flashing the zips all other partitions are updated accordingly ? like /vendor and so on ?Please clarify and keep it technical, i want to learn
ivanjudge said:
Redo the process and try to flash the gsi only without gaps then boot..
Click to expand...
Click to collapse
I already did
right now i am on aospextended android 11 version. since it's not a gsi image it worked. but it is unstable and i really want to try the gsi images and make it work primarily out of technical curiosity
hash02 said:
I already did
right now i am on aospextended android 11 version. since it's not a gsi image it worked. but it is unstable and i really want to try the gsi images and make it work primarily out of technical curiosity
Click to expand...
Click to collapse
Try what @hash02 said you can check the link i gave you above to view the full detail and to avoid boot loops reboot to recovery after flashing the gsi then flash the gapss then factory reset then reboot...And dont use nikgaps instead use other Gapps..
ivanjudge said:
Try what @hash02 said you can check the link i gave you above to view the full detail and to avoid boot loops reboot to recovery after flashing the gsi then flash the gapss then factory reset then reboot...And dont use nikgaps instead use other Gapps..
Click to expand...
Click to collapse
Well, Ok but where do i find android 11 opengapps ?
I didn't find any other gapps for Android 11.
However I tried your method even if it makes absolutely no sense at all. This device is a-only not a/b. Can you explain that or is that an elephant in the room that you dont want to talk about ?
In any case, the device does not bootloop anymore, it just sits in fastboot mode.
These are the steps to flash a gsi on zuk z2 pro correctly:
Wipe clean all partitions excluding user data
Then flash https://forum.xda-developers.com/t/radio-modem-basebands-for-zuk-z2-pro-only.3715835/ latest baseband
Flash boot image [ linked below - it is the boot image extracted from a mokee 9.0 rom ]
flash vendor image [ copied from another thread ]
flash gsi image [which ever you want]
reboot to recovery again [ sometimes it doesnt work unless you do ]
reboot to system
https://mega.nz/folder/E55iTZQJ#jNsa9d7WxLKr-9q_LFPS1A saved here for anyone else's convenience.
hash02 said:
So, the gsi flashing just copies the image-byte-by-byte to the /system partition ?
Just like dd on linux ? Blind transfer from one direction to the other ?Is this why you recommend flashing "basic roms", so that by flashing the zips all other partitions are updated accordingly ? like /vendor and so on ?Please clarify and keep it technical, i want to learn
Click to expand...
Click to collapse
by flashing gsi no vendor is updated or modified. because gsi's are generic rom with only system image, no other partitions. so flashing a basic rom (especially made for your device) , that will update every partition, and then replacing system by gsi system thats all.
prc.kailas said:
by flashing gsi no vendor is updated or modified. because gsi's are generic rom with only system image, no other partitions. so flashing a basic rom (especially made for your device) , that will update every partition, and then replacing system by gsi system thats all.
Click to expand...
Click to collapse
Thank you, I figured as much as I did a lot of testing trial and error and flashed lots of files yesterday. Got it working booting etc. Unfortunately the ROMs don't support fingerprint scanner out of the box and didn't bother to make it work. Just wanted something stable to use my phone. Thx
hash02 said:
superior-arm64-bvN-userdebug.img with AEX 7.3 works awesome and stable enough.
Click to expand...
Click to collapse
havoc-arm64-bvN-vndklite.img with AEX 7.3 works
hash02 said:
Thank you, I figured as much as I did a lot of testing trial and error and flashed lots of files yesterday. Got it working booting etc. Unfortunately the ROMs don't support fingerprint scanner out of the box and didn't bother to make it work. Just wanted something stable to use my phone. Thx
Click to expand...
Click to collapse
for me AEX 8.1 is awesome, but none of custom support Uhealth with Sp02 sensor. its very usefull at this time.