Related
Hi,
my Samsung GT-I9001 runs with LineageOS 14.1 (Nougat 7.1.2):
https://forum.xda-developers.com/ga...opment/i9001-lineageos-galaxy-s-plus-t3793783
As recovery TWRP 2.8.1.0 (F2FS-support) is installed.
Wenn trying to install Magisk 19.3 using magisk-v19.3.zip via TWRP it does not work: Error message ""Error execute updater binary in zip" and no flash is done.
Any idea what is the reason? The TWRP 2.8.1.0 is the latest version I found for the I9001.
The I tried patching the stock-bootloader via the Magisk-Manager. The bootloader-file is a .tar-file, e.g. in
https://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330.
Magisk works with .tar, too, but seems to exspect an .img-file inside. But inside the I9001-"Boot_loader.tar" is no .img-file but 3 .mbn-files and 1 .bin-file.
So I am asking for help. Is there no way using Magisk with the I9001 (and LineageOS 14.1/TWRP)?
You're not supposed to use the bootloader, but the boot image. Two very different parts of the system setup...
And since you have such an old TWRP you're going to have to use the patching method, but it is very far from certain that your device is compatible. Only way to know is to try though.
Oops. Sorry, my mistake. I am a newbie with this and until I was not aware of boot.img ... I supposed it as the "real" filename of the bootloader. And again learning something new. Thank a lot for teaching.
Fortunately I have made a backup of the stock-ROM with TWRP before flashing the ROM. In the backup I find the file boot.emmc.win. This seems to be the stock-boot.img. Is it corrcect that I only have to rename the file to boot.img?
If the I9001 is not compatible with Magisk, means patching of the boot.img would result in a not working code/boot.img (the patching-procedure itself worked w/o errors, but does thos mean, that the result is o.k.?) - is the real risk bricking the device?
That should be the boot image and it should work fine by just renaming it. But, if it's the boot image from the stock Samsung system it won't work with LineageOS. You'll find the boot image for the ROM inside the ROM zip.
If the boot image is incompatible the Manager will let you know by an error message. Save the installation log if that happens and it could possibly tell you in more detail what went wrong.
If everything goes smoothly and the Manager manages to patch the file without issue and you still end up not being able to boot your device after flashing it you can simply restore the unpatched boot image and everything will be back to normal again.
Thanks for the further explanations. But I am not sure understanding correct.
In my understanding of the Magisk-installation manual I have to use the original boot.img always, in every case.
Do I understand correct that this understanding is wrong and that I have to use for patching with the Magisk-Manager the specific boot.img of the actual running OS? So I have to extract the boot.img of the lineageos-14.1-.tar-file (or rename the boot.emmc.win from one of my later backups of the lineagos-14.1-system)?
I have tested patching meanwhile with the "original" boot.img from the old ("original") backup and also with a boot.img extracted from a complete stock-ROM I have found in the web. Magisk Manager patched both fles w/o problems.
btw: Need the patched file the name "boot.img" or doesn´t matter the ame of the patched file (when flashing with fastboot or Odin)?
Unfortunately - or fortunately - I was not able to flash the patched boot.img to the i9001:
adb can communicate with the i9001 when it is running normal (USB debug enabled) and attached via USB. But although Odin is realizing the i9001 attached in download-mode (what means that the USB-cable is working and the driver are installed) fastboot does not realize the i9001 attached in download-mode. I have tested a lot of cables, ports and USB-drivers - no success.
So I tried to flash the boot.img with Odin. For this the boot.img must be converted to a .tar- (or .tar.md5-)file. When searching for converting-tools I found the explanation how to change the output-format of the patched boot.img in Magisk-Manager to .tar. Unfortunately I do not find this option in the current/latest version of Magisk-Manager. What is wrong - is there a secret, a hidden way to activate this option or is this option available in older versions of Magisk Manager only - and if so can I use an older version only for patching and getting a .tar-boot-image-file?
What the documentation is talking about is indeed the untouched boot image of your currently running OS. Don't mix and match.
When flashing with Odin the image indeed need to be in tar-format. With the current Manager there is no option to change the output format because the Manager will take care of that itself. Feed it a tar file and it'll output a tar file. Unfortunately you'll likely get plain image files from the TWRP backups, so those files will be no good unless you convert them before patching.
But, you might not have to use Odin since you have TWRP. It can flash the patched boot image for you. No computer required...
Again thanks a lot for this teaching. I am a newbie in modifying, tuning, flashing smartphones, and although I have learned a lot in the last weeks there are yet a lot of thing I do not know.
I know that I can flash new OS as .zip-file with TWRP (and other files if the manual says that I have/can do it with TWRP ) but I did not know that I can flash with TWRP a boot.img-file. So I would like to ask for a brief guide how to do this. Or is this the same procedure as flashing any .zip-file?
Addition 1: TWRP 2.8.1.0 does not see/list the .img-Files ....
O.k., found in the web: Directly flashing .img: Version 2.8.4.0 and above ....
So I am back again where I started ... fastboot does not see the i9001 and Odin needs a .tar ...
Addition 2: In reg. of the boot.img of the actual used OS:
I have looked into the "original" flashed lineage-14.1-20180523-UNOFFICIAL-ariesve.zip and found the boot.img. But this boot.img is smaller (4.670 byte) than the boot.emmc.win of it´s backup (5.120 byte). In fact every boot.emmc.win of every TWRP-backup (doesn´t matter what OS I have tested) ist 5.120 bytes and larger than the boot.img of the .tar/.zip-file for flashing (different sizes). So if the files are not identical - how can just simply renaming the boot.emmc.win in boot.img result in a valid boot.img?
It's practically the same thing. You just have to switch to "Image" after choosing the install option and then pick what partition to flash to after selecting the file.
Didgeridoohan said:
It's practically the same thing. You just have to switch to "Image" after choosing the install option and then pick what partition to flash to after selecting the file.
Click to expand...
Click to collapse
But not in version 2.8.1.0 - and there is no newer TWRP for the i9001.
MarkFalk said:
But not in version 2.8.1.0 - and there is no newer TWRP for the i9001.
Click to expand...
Click to collapse
Yes. I'm going to forcefully introduce my palm to my face for a moment... Forgot about that tiny but crucial detail.
Just use the boot image file from the LineageOS zip. Patch it and flash the patched image to your device. If you can't get that working I'm going to have to hand this over to someone else, because I have practically zero knowledge on working with Samsung devices and their shenanigans.
Thanks. The small detail of "flashing" into the i9001 is the remaining problem.
As said fastboot does not see the i9001 in it´s download-mode although Odin sees the device and can flash e.g. the bootloader. Odin on the other hand needs a .tar-file and I do not find a way how to converting the (patched) boot.img into a .tar-file that Odin would accept as valid file.
In these cases I usually ask someone like @jenslody or @ianmacd. They usually have a lot more knowledge about Samsung stuff...
I have found a workaround:
1. Make a pure boot-backup with TWRP
2. Copy the backup-folder into/with a new name
3. Copy boot.emmc.win and boot.emmc.win.md5 from the backup to pc or root
4. Rename boot.emmc.win to boot.img
5. Patch boot.img with Magisk-Manager
6. Rename the result to boot.emmc.win
7. Copy boot.emmc.win to the new backup-folder
8. Make a RD5-hash of boot.emmc.win
9. Replace the hash in boot.emmc.win.rd5 with the new hash
10. Copy boot.emmc.win.rd5 to the new backup-folder
11. Boot into TWRP and restore boot from the new folder
It works with the i9001 and lineageOS14.1 and TWRP 2.8.1.0 and the newest Magisk, but it should work with all devices.
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?
This is a bit late but why not. THIS IS A COMPILATION OF ALL THE OS METHODS YOU NEED FOR THE OP6/6T.
ENJOY my guide
DISCLAIMER:
*I am not responsible for bricked devices, damage to your device*
Sorry for a long list of methods, some work for others and some don't. But I recommend to pick a method and stick to it. Maybe read the part at the top as some have notes about mine or someone else's experience/recommendation. Don't skip steps and follow each step.
If stuck, just ask and I or anyone else will try and help
I am here to post methods for anyone who is interested/need help. I have tested these myself and helped others who may be struggling
Download
The guide has loads of files/ zips/ tools to use/flash/install. But no worries as everything can be downloaded and there are links AT THE BOTTOM OF THIS THREAD (NOT COMMENTS) to where to download:
SDK Platform Tools (Fastboot tools) from Developer Android
TWRP from mauronofrio
Magisk from topjohnwu
Gapps (Google Apps) from NikGapps. I recommend omni for ROMs that don't include Gapps.
Fastboot ROM for OP6 + OP6T from mauronofrio
MSMDownload tools for OP6 + OP6T from Some_Random_Username
IMPORTANT NOTES!
YOU REQUIRE Platform Tools (Fastboot Tools) IN ORDER TO USE THE METHODS IN THIS GUIDE AS TWRP NEEDS TO BE INSTALLED!
YOU NEED TO HAVE A UNLOCKED BOOTLOADER AS WELL!
For GAPPS, u can use the same or a updated version of the package. But has to be the same type u used to install it like (stock, full, Omni, basic, etc). ONLY FLASH/INSTALL IF the RESTORE SCRIPT DIDN'T SHOW UP during a DIRTY FLASH/UPDATE AND ONLY FLASH AFTER REBOOTING TO RECOVERY AFTER FLASHING/INSTALLING A OS/BUILD ZIP FILE!
How to get Platform Tools
These tools are used to install TWRP, to unlock the bootloader of your device and is needed to use the METHODS in this guide.
Download the platform tools.zip of your software platform (Mac, Windows, Linux)
Extract the platform-tools.zip
To use it go into your platform-tools folder
Press shift + right-click and choose command prompt or PowerShell
Connect your device when it's in fastboot mode and done
How to install TWRP
Sadly this Guide is for Windows, but other platforms like Mac or Linux can be found online.
YOU CAN USE THIS METHOD TO INSTALL A NEWER VERSION OF TWRP TOO
You need to have downloaded Platform Tools which the link is attached below.
Transfer the TWRP.img file into the platform-tools folder
Now transfer TWRP.zip into your device's internal storage. (connect -> allow file transfer -> drag and drop files)
If you want root download and transfer magisk.apk and the link is supplied below. Also, RENAME from .apk to .zip
Now we must boot into fastboot mode. (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Now connect your device to a Windows device
Press shift + right-click. Choose command prompt or PowerShell
Enter "fastboot devices" and your device should be displayed if it's connected
Type "fastboot boot twrp" file name (do twrp + press tab) and press enter
Then you should be booted into TWRP
Enter the password and swipe to allow modifications
Press install and find your TWRP.zip file
Swipe to confirm Flash
If you want root do this
Press the back arrow and find your magisk.zip
Swipe to confirm Flash
Reboot to the system and done
Otherwise, just reboot to system. Up to u
Installing a Custom ROM
Install Custom ROM on OP6T from OOS
Make sure u have BACKED UP your device and have the latest OOS installed in both slots. If u do, go to Method 3.
If u have finalize.zip, go to Method 2.
Method 1
If u don't have OOS installed in both slots or finalize.zip, use this method.
Transfer OOS.zip file, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot TWRP
Flash OOS + TWRP
reboot recovery
Flash OOS + TWRP
Reboot recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
If u have finalize.zip, do this method. Using finalize is way quicker as there's less flashing and rebooting.
Transfer OOS.zip file, finalize.zip, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash OOS + finalize
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 3
Once you have installed OOS in both slots do this part.
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Installing Custom Rom not from OOS
You can use finalize method or just flash OOS + TWRP way. The finalize way is there for some who like less flashing and rebooting.
Using the methods in Install Custom ROM on OP6T from OOS
Using the old way, use Method 1
Using finalize.zip, use Method 2
Remember to factory reset (wipe, but no need to wipe internal storage)
Backing Up OOS and Custom ROM
Make sure u have installed the latest TWRP version from mauronofrio
You should use TitaniumBackup or Migrate to back up your apps and contacts.
Also, have a copy of your Internal Storage folders if u have important files.
TWRP Backup backs up your OS like Apps, settings and set up, but not internal storage.
NEVER BACKUP SYSTEM AND VENDOR! ONLY SYSTEM.IMG or VENDOR.IMG IF YOU HAVE TO!
Restoring it makes going back way easier like you have never left
Or you can go manually and try and restore everything, but why do that when you got TWRP?
I do both ways of backing up
Backing up OOS
Boot TWRP recovery
Choose Backup
Choose boot, data. YOU DO NOT NEED TO BACKUP System.img and Vendor.img!
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Backing up a Custom ROM
Boot TWRP recovery
Choose Backup
Choose boot, data, system.img, vendor.img
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Restoring OOS and Custom ROM
Restoring OOS TWRP Backup
To restore OOS use either fastboot ROM or MSM. Fastboot is the fastest and easiest way if u have a TWRP backup which there's a method to how to make one in this guide. BUT if you are restoring to go back to stock OOS then use MSM
I use Fastboot ROM restore for that too as we are restoring our data anyways and also for switching/installing a custom ROM. Much easier in my experience.
DOWNLOAD FULL ZIP OF OOS version of your TWRP backup otherwise you could risk doing the whole restore method again OR setup from SCRATCH! IF you aren't restoring a TWRP backup, I recommend either TRANSFER or DOWNLOAD via WiFi or oxygen updater, a UPDATED version of OOS AFTER doing either fastboot ROM or MSM restore methods. As they restore a old version of OOS!
Restoring using Fastboot ROM
Download fastboot ROM of your choice using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Restoring using MSM Download Tool
Download latest MSM version of your choice using the link in the Download Link section.
Extract/ un-zip
Click on MSM tool .exe file
Turn off device
HOLD BOTH volume buttons
Connect your phone
Wait for your device to be connected and it should show as green
Click verify to check and press start
Wait till phone reboots
The setup device and u can carrying on restoring your device if u don't want a unlock bootloader or return to what your device was like before.
Go into developer options
Allow OEM unlocking
Reboot to bootloader
Enter "fastboot devices" to check your device is connected
Enter "fastboot oem unlock"
Swipe for yes
Then it will reboot again
continue to the next method
For both fastboot and MSM
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore only boot and data
Swipe to restore
If you have backed up your internal storage folders do this
Reboot to recovery
Transfer all your internal storage folders
Reboot to system and done
Otherwise, just reboot to system. U can update OOS as well if it's outdated. The method is below to update OOS with ROOT. Up to u
RESTORING TWRP BACKUP HAS ISSUES ON THESE ROMs
CrDroid (Method 1 + 2 don't work). Method 3 works (install Gapps if the ROM doesn't have it!)
Restoring a Custom ROM TWRP backup 1
I tried using this method, but it didn't work for me.
You can use this method to switch ROMs too
Boot TWRP Recovery
Flash OOS + Finalize
Boot to bootloader, boot TWRP
Flash TWRP
Reboot Recovery
Transfer twrp backup
Restore System.img, Vendor.img and boot
Boot to system and setup system
Reboot to recovery
Restore data
Reboot system. Done
I had an issue with this method where rebooting system it was from fresh and my data didn't restore. If this happened to you, then do method 2 (Restoring a Custom ROM TWRP Backup 2)
Restoring a Custom ROM TWRP Backup 2
The first method didn't work for me. But this method did
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up briefly and DO NOT RESTORE ANYTHING.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore everything (System.img, vendor.img, boot.img and data)
Swipe to restore. If data couldn't restore then boot system, setup system, boot TWRP and restore data.
Reboot system. The first reboot might go dodgy and it did for me.
Reboot system and transfer all your internal storage stuff
done
If this did not work still. Then do the 3rd method...
Restoring a Custom ROM TWRP backup 3
If the previous 2 methods has failed for you. Then try this.
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot to Recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Otherwise, just Format data -> reboot to recovery. Up to u
Reboot Recovery
Transfer twrp backup
Restore data
Reboot system. Done
If it still fails, repeat steps 1 to 15. But restore everything and you should be back on your custom ROM like you never left.
Updating OOS and Custom ROM
Update OOS with Root (Magisk)
Always do a TWRP backup before updating your OS in case
Download the full zip file of the latest OOS, transfer the zip file to internal storage NOT IN ANY FOLDER
Download and transfer twrp.zip file to internal storage
Go into settings, system update, update via local upgrade and choose the file
Wait till the installation has finished. If failed TRY AGAIN!
DO NOT REBOOT!
Go into Magisk Manager, modules
Find the twrp zip file and install TWRP
DO NOT REBOOT!
Go into Magisk Home
Press install
Press install via inactive slot
Reboot system and done
You will reboot into the next slot
You don’t have to repeat the installation to install the latest OOS in the other slot. But you should and I use this method many times and has never let me down.
Updating OOS without root
Go to System Update -> find the update install and reboot.
Or download the zip -> transfer to internal storage -> update via local upgrade -> reboot and done
Update a Custom ROM
Method 1
Always do a TWRP backup before updating your OS in case
Use this method just to update the ROM.
Boot recovery
Flash new version + twrp
Reboot recovery
Flash new version + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
This method uses finalize.zip
Boot recovery
Flash new version + finalize + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Updating vendor
Use Method 1 and 2 for ROMs with Gapps. Use Method 3 for ROMs with no Gapps included.
Method 1
If u haven’t updated your Custom ROM and your Vendor… You can use this method to update both or just the vendor.
Boot recovery
Flash OOS + twrp
Reboot recovery
Flash OOS + twrp
Reboot recovery
Flash Custom ROM + twrp
Reboot recovery
Flash Custom ROM + twrp
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 2
This method uses finalize.zip
Boot recovery
Flash OOS + finalize + twrp
Reboot recovery
Flash Custom ROM + finalize + twrp
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 3
This method is for ROMs with no Gapps included
You can use this method as well for updating to a vendor that has a NEWER ANDROID version like from OOS 10 to OOS 11 vendor.
Boot recovery
Flash OOS + Custom ROM + twrp
Reboot recovery
Flash OOS + Custom ROM + twrp
If u flashed GApps, the restore script should show up during the installation of the ROM.zip
If the GApps script didn't show up do this
Otherwise, skip step 3
Flash Magisk if u want root, otherwise skip step 2
Reboot to recovery
Flash Magisk
Flash Gapps
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
OOS versions for OP6 (under Signed Flashable zips) Here
OOS versions for OP6T (under Signed Flashable zips) Here
TWRP for OP6 Here
TWRP for OP6T Here
Magisk Here
NikGapps Here
Stock Fastboot ROM for OP6 Here
Stock Fastboot ROM for OP6T Here
MSMDownloadTool for OP6 Here
MSMDownloadTool for OP6T Here
TitanumBackup App Here
Migrate App Here
Credits:
@mauronofrio For his amazing work on the TWRP recovery and Stock Fastboot ROMs for OP6/6T
@topjohnwu For his work on Magisk
@Nikgapps For their work on creating Gapps
@Some_Random_Username For his Collection of MSMDownloadTool for OP6/6T
@OPTeam For the collection of OOS zips for OP6/6T
@dreamwhite For the method (Method 3) of updating the vendor which works wonders for ROMs with no GApps included
First
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
plepew said:
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
View attachment 5319753
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
Click to expand...
Click to collapse
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Extreme_Ninja2099 said:
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Click to expand...
Click to collapse
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
plepew said:
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
Click to expand...
Click to collapse
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Extreme_Ninja2099 said:
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Click to expand...
Click to collapse
Thank you!!
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
thanking you guys in advance for you help & guidance!
plepew said:
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
View attachment 5320971
thanking you guys in advance for you help & guidance!
Click to expand...
Click to collapse
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Extreme_Ninja2099 said:
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Click to expand...
Click to collapse
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
plepew said:
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
Click to expand...
Click to collapse
Cool and at least that was a easy fix
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
jas84701 said:
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Click to expand...
Click to collapse
Well u posted this twice which isn't necessary and people will try and reply. But I'm not sure if there is a way to know and as long as u copied the whole TWRP folder for that backup, u should be fine restoring it with a newer version of TWRP. If it really matters to you, then maybe try and find the latest TWRP on the date you did the backup? I think just using a newer TWRP version should be fine
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Waynenolan92 said:
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Click to expand...
Click to collapse
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this helps
Extreme_Ninja2099 said:
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this help
Click to expand...
Click to collapse
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Waynenolan92 said:
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Click to expand...
Click to collapse
U can... But it doesn't really matter as a updated package works fine and u only need to use it if the nikgapps restore script doesn't show up when updating the ROM or vendor/base (OOS underneath)
I want to CHANGE custom ROMs (havoc to Lineage OS a11 to a12) I have taken TWRP back up of boot+data+system.img+ vendor.img. once I flash the new a12 Lineage plus Nikapps core plus magisk. What steps to restore data? any response is appreciated in advance. Thank you.
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.
As you know, you need to upgrade the modem and radio firmware from 6.0.1 Android version to make the latest LineageOS or other ROM to work.
You can't do this for this specific device, SM-G900X (Galaxy S5 Live Demo Unit), as the ODIN will fail to flash the files.
But you can modify the ROM to make it past boot-loop quite easy.
Here's what you need to do in order to make it work:
Install latest TWRP for TWRP for KLTE;
You can do this with both ODIN or direct upgrade using TWRP image inside TWRP;
Boot into the TWRP;
Load a ROM .zip on the device like crDroid;
You can upload to SDCard using USB while on TWRP;
Wipe everything (except Internal SD Card);
Install the ROM;
Check if it boot-loop;
Now you need to fix the ROM, which is quite easy:
Boot back into the TWRP recovery;
Go to: Mount -> System (check);
Go back;
Go to: Advanced -> File Manager;
Navigate to: /system/vendor/lib;
Delete or rename: libsec-ril.gsm.so, libsec-ril.usc.so, libsec-ril.vzw.so;
Reboot and enjoy .
what if those files are not present in vondor/lib folder and still is boot loop
G900X is on snapdragon or exynos?