Related
History:
About 4 months ago, I was going to install Omar Avelar's latest ROM onto my phone. I had an older version and thought it was a good time to upgrade. For some stupid reason, I figured I would do a clean install and wipe my phone clean before proceeding.
In CWM 6.0.1.9, I decided to wipe data/factory reset, wipe cache partition, wipe dalvik cache, wipe battery stats, format /system, format /cache, format /data and format /sdcard. Then I proceeded to install the custom ROM file using "install zip from sdcard". This wasn't the first time I had flashed the phone so I figured it would go off without a hitch like it did in the past but I was wrong.
Current State:
After it finished installing, it was booting as normal and then RESTART right before it loaded. I cleared the dalvik cache and this is what happened:
youtube.com/watch?v=hbBf0u6KSsg (I dont have enough posts to link video)
Now no matter what I do, I cannot avoid this boot loop and I have no Idea how to fix it. I have tried EVERY other ROM in the development forum including ROMs by: OmarAvelar, Anerik, max_choco, Aleeexr, arman68 with the exact same result. My knowledge of the android operating system is not advanced enough to solve this so I need help.
What does work:
I can install the stock image using RSD Lite. I can install PiLlama v1.4 using fastboot (because it uses an ext4 file instead of .zip).
If I try to install any of the aforementioned ROMs on top of stock/pillama1.4, it will go back into the same boot loop.
There is a fix for a mystery bootloop problem on roms, on the omars rom forum, its on the download, check that, i cant post the direct link right now but its on the first comment
Enviado desde mi XT890 mediante Tapatalk
I am not sure to which post you are talking about. The first post I see in Omar's ROM post is:
coldtech said:
Thanks for the effort!
Can I use this with an odexed ROM (the official JB OTA)?
If not, any way to still get the Gallery app?
Click to expand...
Click to collapse
Is the file called "fix.zip" by any chance? I have a file named that in my folder that I got while downloading all the ROMs to try.
xd69 said:
I am not sure to which post you are talking about. The first post I see in Omar's ROM post is:
Is the file called "fix.zip" by any chance? I have a file named that in my folder that I got while downloading all the ROMs to try.
Click to expand...
Click to collapse
Nop the first post of Omar, wich have the downlad folder of old version, i think the files name is : mysterybootloop_fix
I think, i never had to use it
Enviado desde mi XT890 mediante Tapatalk
xd69 said:
I am not sure to which post you are talking about. The first post I see in Omar's ROM post is:
Is the file called "fix.zip" by any chance? I have a file named that in my folder that I got while downloading all the ROMs to try.
Click to expand...
Click to collapse
This file.
Mar-25.bootloop_mysterious_fix.zip
Here.
http://haxr.org/omar/android/Razr i/OLD/
But read this:
http://forum.xda-developers.com/showpost.php?p=50614918&postcount=3800
Hello just a simple question about format data in twrp, i can't find a real answer on google, if i format data to get rid of encryption (not only factory reset) will my os still be there or i'll have to flash a rom to get my device booting as usual?
That means if i format data can i reboot my phone right after normally? I know all my pics apps etc will be lost but os will still be there?
I suggest u upgrade twrp to 3.1.0.1 and you will not have to format data.
if you will saty on your twrp and format data your os will stay there, dont worry....
t.h.i said:
I suggest u upgrade twrp to 3.1.0.1 and you will not have to format data.
if you will saty on your twrp and format data your os will stay there, dont worry....
Click to expand...
Click to collapse
So no need to format data if i want to install lineage for example? I'm already on latest twrp 3.1.0-1 . I ask this cause last time i tried to install lineage it ended up with a softbrick and had to install a fastboot rom and setting up my phone from scratch.
...also, take a look at the FAQ page of twrp website
here: https://twrp.me/FAQ/
from that list: this entry has the title "What should I wipe in TWRP?"
https://twrp.me/faq/whattowipe.html
advice: first do a backup in twrp; a full one chosing sysimage instead of system ...so if something goes wrong you can go back.
note: in the twrp faq page there is an entry related to the backup procedure.
Good read and tell us about your progress.
glogal said:
...also, take a look at the FAQ page of twrp website
here: https://twrp.me/FAQ/
from that list: this entry has the title "What should I wipe in TWRP?"
https://twrp.me/faq/whattowipe.html
advice: first do a backup in twrp; a full one chosing sysimage instead of system ...so if something goes wrong you can go back.
note: in the twrp faq page there is an entry related to the backup procedure.
Good read and tell us about your progress.
Click to expand...
Click to collapse
Thx for the info i already read this, but i'm french and i couldn't find a real explanation between wipe and format and what was left on the system after each operation , even in french forum it wasn't clear!! Anyway i format data and installed last RR build running good so far!!
Steps to install Treble ROMs on Galaxy J7 Prime.
Prerequisite:
1. Flash TWRP recovery. For Treble Project I suggest version 3.2.1 here because there is an issue about mounting /preload partition with 3.2.3+. You can try newer versions for your choices. If you see /preload error, Some suggested to ignore this error.
2. For emergency, please download Stock ROM here. If you accidentally mess up your partitions or consistently bricks, Stock ROM will reset everything back to start.
Needed Files:
1. Files from Project Spaget X here.
Exynos7870_CreateVendor.zip is to create /vendor partition.
Exynos7870_ProjectSpaget_V3.0.zip is to install necessary for Treble Project.
Exynos7870_RevertVendor.zip is to delete /vendor partition, in case of uninstalling Treble Project.
2. Treble ROM with ARM64 A only here. My favorite Treble ROMs are Lineage, Arrow and Havoc. I am currently using Arrow.
3. ARM64 GAPPS here.
4. Kraken Kernal here or here. Please download for Treble only. RC12 is universal.
5. Magisk here.
Step I Flash Treble project:
1. boot TWRP recovery
2. wipe Data, Cache, Dalvik, System
3. flash Exynos7870_CreateVendor.zip and reboot to recovery
4. flash Exynos7870_ProjectSpaget_V3.0.zip
Step II Flash Treble ROM:
1. flash Treble ROM ARM64 A only, no need to reboot to recovery in order to install the ROM.
Edit: Reboot to Recovery > Install > press Install Image > choose your Rom.img
2. After flashing the ROM, I usually reboot to system in order to test whether or not the flashed ROM can boot nicely.
2.1 If the flashed ROM cannot boot or brick or bootloop in Logo, press Home + Power + Vol Down to force reboot to Bootloader and boot to recovery.
2.2 Back to recovery. wipe Data, Cache, Dalvik, System
2.3 flash Exynos7870_ProjectSpaget_V3.0.zip before flashing new Treble ROM.
Step III Flash ARM64 GAPPS:
1. Choose Wipe > Advanced Wipe > choose System > Repair > Resize. Sometimes you need to do this twice in order to resize since the first time will show error.
2. flash GAPPS
Step IV Flash Kraken Kernal:
1. Mount > System and Vendor partitions
2. flash KRAKEN-Kernel-RC12-universal7870-Treble-20200314.zip (The latest version of Kraken)
3. reboot to system
I usually reboot once to system before flashing Magisk.
Step V Flash Magisk:
1. Mount > System and Vendor partitions
2. flash Magisk to root
3. reboot to system
4. run Play Store and set up your account
5. run Magisk Manager. When you press Tap to start SafetyNet check, you will find out that ctsProfile: false.
Please note that Usually it will be installed when you have GAPPS installed. If not, you can install Magisk Manager manually.
6. choose Downloads > search "SafetyPatch by hackintosh" > download and install > reboot This will fix ctsProfile false to be true.
Now you are done the basice steps to flash Treble ROMs for your J7 Prime. Any questions please leave a message under the thread.
Cheers, :highfive::highfive::highfive:
Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
---------- Post added at 05:11 PM ---------- Previous post was at 04:53 PM ----------
dctviphb2 said:
Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
Click to expand...
Click to collapse
i can flash now but when i flashed system.img completed, TWRP said that no OS installed, what can i do. thanks for your help
dctviphb2 said:
Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
---------- Post added at 05:11 PM ---------- Previous post was at 04:53 PM ----------
i can flash now but when i flashed system.img completed, TWRP said that no OS installed, what can i do. thanks for your help
Click to expand...
Click to collapse
Please follow the attached screentshot.
1. In the main menu of TWRP, choose Install.
2. Choose your ROM.img
3. Select System Image. This step will tell TWRP to flash your ROM.img to the /system partition.
Note: Attached Screenshots #1-3 is to show steps to mount your /system and /vendor partition. Before your can do these steps, you need to flash Spaget X in the step I of my original post.
Hope this help.
siamese007 said:
Please follow the attached screentshot.
1. In the main menu of TWRP, choose Install.
2. Choose your ROM.img
3. Select System Image. This step will tell TWRP to flash your ROM.img to the /system partition.
Note: Attached Screenshots #1-3 is to show steps to mount your /system and /vendor partition. Before your can do these steps, you need to flash Spaget X in the step I of my original post.
Hope this help.
Click to expand...
Click to collapse
Thank you. I just remember that when i flash spaget my TWRP said "symlink: some symlink faild. Error 7". I have tried both TWRP 3.2.1 and 3.2.3 but both of them didnot work. I think i will try another version, or if you have any idea please tell me. Thank you so much
dctviphb2 said:
Thank you. I just remember that when i flash spaget my TWRP said "symlink: some symlink faild. Error 7". I have tried both TWRP 3.2.1 and 3.2.3 but both of them didnot work. I think i will try another version, or if you have any idea please tell me. Thank you so much
Click to expand...
Click to collapse
You're welcome. I honestly never experience this kind of error.
I found a solution about this error on youtube.
This solution is to extract ROM file and edit updater-script file with notepad++.
Edit: try this Spaget X file. I followed this youtube tutorial trying to fix error 7 that you got when flashing Spaget X.
Another possibility of this error is Partition messed up.
I would try to flash stock ROM with Odin to reset everything to factory default.
Caution: Back up your data before flashing Stock ROM.
Follow the instruction of how to flash Stock ROM in the Stock ROM page or here. Flashing Stock ROM will also remove TWRP recovery and re-partition.
Hope one of this solution help, :highfive::highfive::highfive:
Thank you so much. I think the problem is I am using HROM, which has Repatition.zip, so I think that my partition has messed up, that the reason I face the issue. I will try to solve it with your idea. Thanks so much for helping me, if I can solve the problem I will tell you
Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much
dctviphb2 said:
Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much
Click to expand...
Click to collapse
That's great NEWS. You've managed to find a solution for No OS installed error.
By the way, for the deep sleep problem that you mentioned, I also experience the same thing. My solution is to press home button to immediately wake the phone up from deep sleep.
[HELP]Treble Incompatible device (J7 PRIME)
I'm also using J7 prime G610F...but when i used Treble Checker is showed my device is Treble Incompatible...I don't understand why it is not working for me while you guys have the same phone and its working...also i'm using a custom rom (reserruction remix) so perhaps should i load up my stock system then try? I also tried to install the Treble project using the steps above but i couldn't flash the image...twrp was only detecting zip files and when i clicked in INSTALL IMAGE it would.nt show any image file which i transferred in my phone
hussain_mdj said:
I'm also using J7 prime G610F...but when i used Treble Checker is showed my device is Treble Incompatible...I don't understand why it is not working for me while you guys have the same phone and its working...also i'm using a custom rom (reserruction remix) so perhaps should i load up my stock system then try? I also tried to install the Treble project using the steps above but i couldn't flash the image...twrp was only detecting zip files and when i clicked in INSTALL IMAGE it would.nt show any image file which i transferred in my phone
Click to expand...
Click to collapse
Unpack .xz file
TWRP still doesn't detect the image
thanhphat95 said:
Unpack .xz file
Click to expand...
Click to collapse
...
---------- Post added at 12:53 AM ---------- Previous post was at 12:48 AM ----------
thanhphat95 said:
Unpack .xz file
Click to expand...
Click to collapse
i'm dummy dum so forgive and thenk
dctviphb2 said:
Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much
Click to expand...
Click to collapse
There is a solution...in phh treble settings go to doze then turn on out of pocket feature....works like a charm for me.....
------------
HAPPY TO HELP..
After trying to update to a newer version of a custom rom, crDroid 6.4, I can no longer boot into the system. The phone only boots into recovery. TWRP no longer asks for a password in order to decrypt the phone, as it has done before. I have tried wiping Data, Cache, and Dalvik, and flashed the rom again, with no luck. Is it a way for me to force decrytion or something?
Any help is much appreciated! I am new to this, and still learning.
Ukulelen said:
After trying to update to a newer version of a custom rom, crDroid 6.4, I can no longer boot into the system. The phone only boots into recovery. TWRP no longer asks for a password in order to decrypt the phone, as it has done before. I have tried wiping Data, Cache, and Dalvik, and flashed the rom again, with no luck. Is it a way for me to force decrytion or something?
Any help is much appreciated! I am new to this, and still learning.
Click to expand...
Click to collapse
I assume that the data partition is actually still encrypted and you see random folder names in TWRP. If so, try formatting data in TWRP (not wipe, but format) then reboot to the ROM.
Robbo.5000 said:
I assume that the data partition is actually still encrypted and you see random folder names in TWRP. If so, try formatting data in TWRP (not wipe, but format) then reboot to the ROM.
Click to expand...
Click to collapse
Will this delete all my files?
Also, I'm not sure if I am flashing the ROM correctly. I have the ROM, magisk and other files on my computer. I use "ADB Sideload" under advanced in TWRP and "adb sideload romname.zip" on my computer.
Ukulelen said:
Will this delete all my files?
Also, I'm not sure if I am flashing the ROM correctly. I have the ROM, magisk and other files on my computer. I use "ADB Sideload" under advanced in TWRP and "adb sideload romname.zip" on my computer.
Click to expand...
Click to collapse
Yes it will delete all your files. If you boot to TWRP and it doesn't ask for the PIN, etc., but you see all your folders have random encrypted names, then everything is lost anyway. There is nothing you can do to recover that data.
In future just copy the ROMs onto the phone and flash them directly off the phone in TWRP, using the install menu.
Robbo.5000 said:
Yes it will delete all your files. If you boot to TWRP and it doesn't ask for the PIN, etc., but you see all your folders have random encrypted names, then everything is lost anyway. There is nothing you can do to recover that data.
In future just copy the ROMs onto the phone and flash them directly off the phone in TWRP, using the install menu.
Click to expand...
Click to collapse
Thanks for your help. Luckily I had backed up all my photos. I am up and running with a new rom. I am testing omni rom as it now comes with microg prebuild.
Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
exactly which file do I have to download among ASSETS of any release?
Thank you very much
Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
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
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com
Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again
It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.
Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...
Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article
nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again
Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Maybe I have to try with sideload ?
Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.