Database Develop

[HELP] [URGENT] ONLY OxygenOS not Booting up !!!!

Hi guys
I am having a weird issue , I am able to flash ANY custom ROM ( mark my words "any") be it skydragon os, havoc os, lineage os but I am unable to flash OxygenOS (tried 5.0.7 and 5.0.8) . When I start the first boot after flashing the OOS zip file, it always get stuck on boot animation and the animation goes on forever. Please Help !!!!!
Note:
- Have tried with different versions of TWRP but no success
- Always Did a clean install
- When after being stuck at boot animation for 40 mins , i FORCE restarted my phone to recovery and found that all system files and folders have been made as normally so i think there was no error in flashing process but still ROM not booting up.
Also:
- If someone has successfully booted the latest OOS from scratch ( I mean clean install) so please can you provide your ( links !)
1. TWRP file
2. OOS zip file

PreciousPulkit said:
Hi guys
I am having a weird issue , I am able to flash ANY custom ROM ( mark my words "any") be it skydragon os, havoc os, lineage os but I am unable to flash OxygenOS (tried 5.0.7 and 5.0.8) . When I start the first boot after flashing the OOS zip file, it always get stuck on boot animation and the animation goes on forever. Please Help !!!!!
Note:
- Have tried with different versions of TWRP but no success
- Always Did a clean install
- When after being stuck at boot animation for 40 mins , i FORCE restarted my phone to recovery and found that all system files and folders have been made as normally so i think there was no error in flashing process but still ROM not booting up.
Also:
- If someone has successfully booted the latest OOS from scratch ( I mean clean install) so please can you provide your ( links !)
1. TWRP file
2. OOS zip file
Click to expand...
Click to collapse
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs

BillGoss said:
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Exactly How Much Time can the re-encryption process could take?? Cause I gave it good 1 hour
Also to make sure i am getting it right , you mean to say that i should use the TWRP file you mentioned below your statement
"-------update 2" or is it some (img file) that i need to flash through TWRP

BillGoss said:
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
To Avoid Any Further Confusion , Could You Give me step by step instructions for what to do , please?
Please also give me details to which TWRP to use and all the configurations ( like ext4 or f2fs on system or data , whether to use format button, or advanced wipe) all that! Thanks in advance

Issue solved !!
How I solved ?
1. Using TWRP 3.2.2-0 I first Formatted data.
2.Then used advanced wipe to clean everything.
3.Then using change file system option in WIPE category changed my "data" partition from whatever to f2fs.
4.Then changed back to ext4.
5.Then changed back to f2fs.
6.Using PC transferred OOS zip file (5.0.8) to internal storage.
7.Flashed The file
8.Bingo !!! Phone booted up without a problem
Thanks @BillGoss , your provided links helped alot, though i used nothing from it but they helped me to recognize what the problem was, it was i think an encyption as well as changed file system format issue due to my previous flashing of pie roms.:good:

PreciousPulkit said:
How I solved ?
1. Using TWRP 3.2.2-0 I first Formatted data.
2.Then used advanced wipe to clean everything.
3.Then using change file system option in WIPE category changed my "data" partition from whatever to f2fs.
4.Then changed back to ext4.
5.Then changed back to f2fs.
6.Using PC transferred OOS zip file (5.0.8) to internal storage.
7.Flashed The file
8.Bingo !!! Phone booted up without a problem
Thanks @BillGoss , your provided links helped alot, though i used nothing from it but they helped me to recognize what the problem was, it was i think an encyption as well as changed file system format issue due to my previous flashing of pie roms.:good:
Click to expand...
Click to collapse
Well done. And because you worked this out yourself, you've learnt a lot.
Sent from my OnePlus3T using XDA Labs

Updater process ended with ERROR: 1

Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:

Have unlocked boot loader?

Need to format data first

xStatiZx said:
Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:
Click to expand...
Click to collapse
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:

Matthewwwww1998 said:
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:
Click to expand...
Click to collapse
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.

murph187 said:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Click to expand...
Click to collapse
You're a GOD. Thank You!!!!!

updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs

I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP

i try and didnt work how to extract boot image in steps ??

magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
which version you use

murph187 said:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Click to expand...
Click to collapse
Hi, which option may i have to choose? there are 4 options

magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
3.2.2 worked for me.

In my case unmounting all the partitions fixed it for me, the boot.img method didn't work.

magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
I had flashed new version on firmware but forgot to update TWRP recovery that is why I was getting this error. I updated TWRP recovery. also flashed boot.img image then I was able to fix this issue.

guys please help me i have xiaomi mi a2 lite whit twrp 3.5.0_9 installed and unlocked bootloader i downloaded android 11 rom link: https://forum.xda-developers.com/t/rom-11-0-daisy-aosp-11-0.4167961/. When i go to recovery mode i flash the rom and appears this error: Updater process ended whit error: 1 to flash additional zips please reboot recovery to switch to the updated slots. Error installing zip file rom.zip. please help me.
THANKS

samyxy said:
guys please help me i have xiaomi mi a2 lite whit twrp 3.5.0_9 installed and unlocked bootloader i downloaded android 11 rom link: https://forum.xda-developers.com/t/rom-11-0-daisy-aosp-11-0.4167961/. When i go to recovery mode i flash the rom and appears this error: Updater process ended whit error: 1 to flash additional zips please reboot recovery to switch to the updated slots. Error installing zip file rom.zip. please help me.
THANKS
Click to expand...
Click to collapse
I was having the same issue... After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation... I don't know if this was the correct approach, but after many tries this is what worked for me
Sorry about my bad english...

Sometimes it is caused due to corrupted file. While transferring file through MTP it is likely to corrupt large files. I had the same problem. Then I tried copying file while in TWRP (sure it is also MTP) and it worked.

PendiukG said:
I was having the same issue... After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation... I don't know if this was the correct approach, but after many tries this is what worked for me
Sorry about my bad english...
Click to expand...
Click to collapse
It's legit procedure. Also you don't need to manage slots here, caz recovery automatically does that for you.

Hello guys, i'm from Russia, sorry for my bad English. I using Poco X3 Pro, and i have some troubles. I wanted to install custom firmware. First ROM
delivered successfully, unlike the second. After clearing all sections except sd cart and otg, I tried to install the original MIUI build, but it didn't work. I downloaded the original MIUI, but still. When installing, it says: "Update process ended with ERROR: 1" The methods from the top didn't help, please help!

Sushanthn94 said:
updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs
Click to expand...
Click to collapse
Kali Nethunter on redmi 4x (santoni) is updated here:
Releases · Neternels/android_kernel_xiaomi_msm8937
Redmi 4X (santoni) NetHunter Kernel. Contribute to Neternels/android_kernel_xiaomi_msm8937 development by creating an account on GitHub.
github.com
Follow it and flash firmwares (if needed).

Install GSI on S9 Exynos

Guys I successfully installed HAVOC-OS located https://forum.xda-developers.com/project-treble/trebleenabled-device-development/gsi-havoc-os-t3930030. The steps I followed are mentioned below
1. Wipe everything except internal storage.
2. Flashed BRK3 Vendor https://mega.nz/#F!wFFQUYbI!GZvNOBSn1wVn8U9mQDzBiw!IQsjlYzA
2. Installed Endurance GSI kernel https://forum.xda-developers.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/kernel-endurance-kernel-v1-0-t3849434
3. Flashed the system image for ARM 64 A only
4. Boot system
5. Reboot to recovery and Flashed Mgisk
6. Gapps will fail to install at first. Just goto wipe -> Adv wipe -> system partition -> Resize. Reboot to recovery and flash Gapps
7. Reboot and enjoy
8. You can test other GSI Roms also and report. The thread is located at https://forum.xda-developers.com/project-treble/trebleenabled-device-development

Thanks buddy. I was looking for the ways to run the GSI. And the method works. Good job

thanks for the guide! im still on an unrooted s9, but if everything works ill definetly make the jump. Can you tell us more about stability, bugs and if there are things not working

So after testing the ROM for 2 days I can say that
1. It is very stable and can be used as a daily driver
2. Everything works, I am not sure about Bluetooth audio though, haven't checked it
3. It can be heavily customized. Unlike LOS, where we have only few of these features available
4. Battery life is the best I got using any other ROM out there (check the screens below). and I am the guy who gets 3 hrs of SOT, when others claimed 5+ hrs on the same ROM.
5. Security patch is latest even as compared to the TW ROMs
6. Regarding camera... Its the same as LOS pie. Use gcam by idan 3.5 fixed and you are good to go.

fingerprint working?

andreMusers said:
fingerprint working?
Click to expand...
Click to collapse
Yes it is

Thanks for trying this out. I'm only a few months in with my exynos S9 on android pie, so I haven't yet learned the details about rooting/recovery for this phone.
I'll wait for your next update regarding daily use, and would love a more detailed step-by-step for installation if that's not too much trouble. I'm honestly loving those screenshots.

How about IMEI, BRK3 Vendor safe..?

Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.

burninitup said:
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
Click to expand...
Click to collapse
Thanks for the extra instruction man, will test this out soon.

burninitup said:
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
Click to expand...
Click to collapse
Doesn't work. Stuck on boot logo, loading forever.

Zwulf said:
Doesn't work. Stuck on boot logo, loading forever.
Click to expand...
Click to collapse
me too dont know any fix
EDIT: Somehow i managed to boot the rom but sim won't get detected

Double tap and AOD - work correctly? On snap it does not work well

My Baseband version is now unknown
I have an SM-G960F and its german
EDIT:I just flashed the latest firmware from soldier and now sim card gets detected

Masterofchicken said:
My Baseband version is now unknown
I have an SM-G960F and its german
EDIT:I just flashed the latest firmware from soldier and now sim card gets detected
Click to expand...
Click to collapse
So camera isn't working ,root is still present with magisk and i couldn't disable it with the adb command so safetynet doesn't pass ,i'll say it's not really usable ?

Has anyone found a fix for getting stuck at the s9 logo?..wanting to move to GSI ROMs

I have tried this,
After flash GSI rom, reboot recovery, reboot system and I have bootloop with the first logo Galaxy S9. Can anybody please help me?

@arunrawat2112
Finally I was able to flash some roms but none of them work properly. Can you please help me?

[GUIDE] GSI for US V40

Greetings everyone, i go by the name Ainz Ooal Gown. Here i bring you the a guide to flash GSI roms to your V40
Fist things first if you try this and end up with a brick or your device transforms and tries to take over the world; it's not my fault you messed up not me. So just read all of this thread not just the O.P to, and get out of a bind if you reply with "the thread is too long i wont read it please help" don't expect anything short of "there's a search bar use it"
Requirements
Unlocked bootloader
TWRP
Installation guide:
You need to download Lineage OS 16 by Xsavi i recommend the build "lineage-16.0-20190914-UNOFFICIAL-judypn(More LG Stuff use this).zip". Put into your external SD
You need to download a GSI from here https://forum.xda-developers.com/project-treble/trebleenabled-device-development i personally recommend Havoc OS 2.9 and Resurrection Remix 7.0 download the Arm 64 A/B Variant and what ever recommended Gapps Package is linked.
Extract the GSI you downloaded and copy the extracted Folder into your external SD.
Boot into TWRP and check your active Slot in the reboot menu.
Flash LOS 16 Install -> select the ROM zip -> tick Inject TWRP -> Swipe for install (if you're on a, it will be installed to b, and vice versa).
Go to and select Reboot Menu -> select your inactive slot -> select recovery and you should reboot into your inactive slot.
Go to and select Wipe Menu -> Swipe to factory reset
Select install and navigate to your downloaded GSI -> select install image -> select the GSI image -> select the bubble next to "System Image" -> Swipe to Custom Flash.
Select the wipe menu -> select advanced wipe -> select the square next to "System" -> select "Repair or Change File System" -> select Resize File System -> Swipe to Resize.
Install any Gapps and/or Magisk and reboot.
You will probably have to add your Carriers APN settings for Data and MMS to work.
Thanks to: @SGCMarkus @Xsavi

Ainz_Ooal_Gown said:
Hello here i will be uploading the instructions for running GSI Treble Oreo and Pie roms.
At the moment i'm making sure everything is working before i upload those instructions and links please be patient last thing i want to do is make you device a fancy brick.
Click to expand...
Click to collapse
Hello!
Maybe you have a dump system or stock firmware for twrp?
Or maybe there is an instruction for unpacking the kdz firmware

scrubber said:
Hello!
Maybe you have a dump system or stock firmware for twrp?
Or maybe there is an instruction for unpacking the kdz firmware
Click to expand...
Click to collapse
GSI would be without KDZ...

Ainz_Ooal_Gown said:
GSI would be without KDZ...
Click to expand...
Click to collapse
I know this :fingers-crossed:
I really need a dump to port the sound equalizer of the LGv40
Help me please

Here we go??

The Guide is Finished

scrubber said:
Hello!
Maybe you have a dump system or stock firmware for twrp?
Or maybe there is an instruction for unpacking the kdz firmware
Click to expand...
Click to collapse
To unpack a kdz use SALT on linux, works best for me

When I flash LOS16 into my inactive B slot, I am unable to boot into TWRP on slot B because there's some Lineage recovery in place and no option to flash anything and the sideload option doesn't work; I am checking inject TWRP. Am I missing something?

grandomegabosses said:
When I flash LOS16 into my inactive B slot, I am unable to boot into TWRP on slot B because there's some Lineage recovery in place and no option to flash anything and the sideload option doesn't work; I am checking inject TWRP. Am I missing something?
Click to expand...
Click to collapse
If you injected TWRP and made sure it was checked it should've given you TWRP in slot b I'll pm you with what to do give me a sec

On step 9, I get a failed error on resize. The error is:
Code:
/sbin/e2fsck -fp /dev/block/bootdevice/by-name/
system_b process ended with ERROR: 1
Unable to repair system
Anyone know how to fix this?
EDIT: I tried to install gapps after this, but it failed because of insufficient space. Went to check the /system partition size, and it only has 65MB free out of 1637MB. Is there a way to restore the original partition size and start from scratch?

xPreSiDenT said:
On step 9, I get a failed error on resize. The error is:
Anyone know how to fix this?
EDIT: I tried to install gapps after this, but it failed because of insufficient space. Went to check the /system partition size, and it only has 65MB free out of 1637MB. Is there a way to restore the original partition size and start from scratch?
Click to expand...
Click to collapse
You have 2 things to try, 1st. resize again and see if the error happens again... 2nd. Reboot recovery and try once more I've had this happen to me.

Ainz_Ooal_Gown said:
You have 2 things to try, 1st. resize again and see if the error happens again... 2nd. Reboot recovery and try once more I've had this happen to me.
Click to expand...
Click to collapse
I already booted into the rom. Would that affect anything? I'm gonna try anyway.
Edit: It worked. Gapps flashing now. Hopefully all will be well.

xPreSiDenT said:
I already booted into the rom. Would that affect anything? I'm gonna try anyway.
Edit: It worked. Gapps flashing now. Hopefully all will be well.
Click to expand...
Click to collapse
You can always factory reset after flashing gapps to get all your stuff synced and what not...or just add your account after and it may tell you to finish setting up.

Ooo interesting guide. Nice one :good:

Hey guys any workaround to get pie ? For at&t unlocked v40, currently in malaysia , dont have at&t carriers here .

So this would work with havoc 3 probably? I look forward to trying in a little.

Would this guide work with LOS17 that is currently in the ROMs section?

cavcagamgee said:
Would this guide work with LOS17 that is currently in the ROMs section?
Click to expand...
Click to collapse
If you mean Los 17 from SGC Markus? Then nope his rom has its own instructions and if you mean as a base for GSI well you can try but I haven't had any luck.

Is there a way to remove the GSI without reflashing the whole thing? RR is having an issue with the camera that is still in development. Is there any way to revert to the LOS 16 without losing my data?

cavcagamgee said:
Is there a way to remove the GSI without reflashing the whole thing? RR is having an issue with the camera that is still in development. Is there any way to revert to the LOS 16 without losing my data?
Click to expand...
Click to collapse
Restoring a back up would do it...if you made one...

how downgrade sm-a605fn from android 10 to 9

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.