Hi guys.
The problem is gsi is Bootlooping every time in custome vendor stock vendor no matter how much i try to install with different methods by different vendors rom.
Tried formatting many times, changing file system, flashing vbmeta, even flashed on both slots nothing happened same Bootloop.
Even tried flashing no verify decryption zip, magisk.
Don't get it what's the problem its booting but Bootlooping.
If gsi is not supported or corrupt img so it'll not boot right? But booting means it gets installed.
But every time the gsi get stuck at bootanimation
Need help what to do now because it installing successfully everytime but at the end Bootlooping.
Tried ported gsi roms
And official gsi roms
Those are not booting..
Urgent help will be appreciated and I'll be very thankful.
:good:
arya_tech said:
Hi guys.
The problem is gsi is Bootlooping every time in custome vendor stock vendor no matter how much i try to install with different methods by different vendors rom.
Tried formatting many times, changing file system, flashing vbmeta, even flashed on both slots nothing happened same Bootloop.
Even tried flashing no verify decryption zip, magisk.
Don't get it what's the problem its booting but Bootlooping.
If gsi is not supported or corrupt img so it'll not boot right? But booting means it gets installed.
But every time the gsi get stuck at bootanimation
Need help what to do now because it installing successfully everytime but at the end Bootlooping.
Tried ported gsi roms
And official gsi roms
Those are not booting..
Urgent help will be appreciated and I'll be very thankful.
:good:
Click to expand...
Click to collapse
You should try generic gsi from this site https://mirrors.lolinet.com/firmware/gsi/
Choose generic AB.. currently latest one is from 11th July @ Developer Preview 5.
Download Havoc os, flash it on slot A.
Reboot to slot B, wipe everything and reboot to recovery again.
Then flash gsi file, permissiver v4, darkness kernel, magisk canary, and disable force encryption.
Wait for it to boot up. ?
How to reboot to slot B and flash to slot A? Zip files are flashing like custom roms, GSI images are for slot A, slot B and AB. Sorry but I'm noob in flashing GSI roms. I never succeeded with that... ((
Tried Flashing "Havoc-OS-v4.1-20210208-arm64-ab-Official-GApps.img"
was boot looping razer logo
flashed Magisk-v22.1.zip
booted further Secure lock screen no passcode dialer then boot loops.
Can't figure out what's wrong I have arter97 r14.
on a forum somewhere they said to flash through fast boot but whenever I wipe I can't use fast boot so I have to restore to backup not really sure what else to do.
any help is greatly appreciated.
this is where I got the GSI from
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
--edit
so I got havoc os booting and running now
first backed up
wiped through twrp
flashed os
flash magisk and f2fs_fstab from arter 97 and it stalled booting
format device in wipe on twrp and boot do not install twrp app
and I am in
used this post and video for the rest
[GUIDE] Android 11 GSI With GApps and Root (magisk)
DON'T DO THIS ON A RAZER PHONE 1 OR IT WILL BE OMEGA BRICKED! ONLY DO THIS ON A RAZER PHONE 2! This was just an experiment to see if i could cobble together some GSI install guides (that on their own are kinda confusing) to make something...
forum.xda-developers.com
I am no expert so I am not responsible for anything you break in doing this is my first rom on any device Good Luck.
you don't get root from magisk but you need magisk to boot without it goes back to recovery
I used this to get root https://www.recovery-mode.com/root/how-to-root-gsi-android-11-with-magisk-v21.html still don't have magisk working but you can't uninstall it or no boot.
I passed safteynet on my HavocOS install. There is a stupid convoluted method to doing it.
its at the end of my guide: https://forum.xda-developers.com/t/guide-havocos-4-1-with-gapps-and-root-magisk.4351029/
hope this helps!
does the universal safety net fix work on this?
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.
Hello. I will describe it briefly:
I'm about to flash my Redmi 6A(cactus), to Lineage OS 18.1 via GSI using OSS(ALPS)-vendor on arm64. I have read some information and it says that installing Magisk could cause a bootloop. I want to know if it is true.
Which image do I want to use - https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
Image - lineage-18.1-20220715-UNOFFICIAL-arm64_bgS-vndklite.img.xz
P.S. I haven't started flashing yet, I want to consider all the little things and conventions before flashing the phone.
Hi XDAVIANS,
I have the MOTO EDGE 20 - Berlin (XT2143-1). I was trying the new PixelExperience 13+ ROM. However, after flashing the PixelExperience recovery I am getting stuck in a boot loop. It's the same for the Lineage OS recovery for Berlin. The new ones don't work. I tried multiple versions (fresh flash). Ultimately, I am stuck in the bootloop. Finally, I flashed the stock ROM with RSA tool to get back in action. However, in one thread I read some users had the same issue and they were able to solve the issue and flash the recovery with a specific version "lineage-19.1-20221203-recovery-berlin". Can anyone help me with this recovery file. I couldn't find it in any repositories (Seems the older versions were removed).
Thanks in advance. I am bored of A12 and want to switch to A13.
I have a solution since I just did this. LineageOS and Pixel Experience are so similar to the point that the instructions are also the same. Mind you, I have used these exact builds: lineage-20.0-20230211-nightly-berlin-signed.zip, 2023/01/12 release of Pixel Experience 13 Plus Edition. It's simple really: Follow the exact instrucions on LineageOS install guide up until "Installing LineageOS from recovery" where instead of the LineageOS zip file you'll use the Pixel Experience. It will give you two errors on screen about some verification error and system downgrade, just say that you want to continue.
https://wiki.pixelexperience.org/devices/berlin/install, this is the official pixel experience install guide for motorola edge 20 specifically, scroll down to the FLASHING DTBO AND VENDER BOOT PARTITIONS section and follow those steps, and flash the recovery image again. That should solve your issue.
AJ47AJ47 said:
https://wiki.pixelexperience.org/devices/berlin/install, this is the official pixel experience install guide for motorola edge 20 specifically, scroll down to the FLASHING DTBO AND VENDER BOOT PARTITIONS section and follow those steps, and flash the recovery image again. That should solve your issue.
Click to expand...
Click to collapse
Pixel Experience seems to be flashing the system on partition A, while LineageOS is flashing it on B and it's probably why it works. It's just a bug at the moment with Pixel Experience. Make sure you're using Platform Tools instead of Minimal ADB and Fastboot since that one is quite old at this point.
Hi all. Thanks a lot for the valuable suggestions. I solved the issue by flashing the boot.img file after the dtbo and vendor_boot images. That did the trick and I am using Android13 now. Such an amazing experience.
it happended to me aswell.
i was stuck bootloop and the only way to solve that was after i used the dtbo and vendor from lineageOS. For some reason those from Pixel Experience does'nt work