DISCONTINUED [TWRP] Samsung Galaxy A20 Custom Recovery (Android 9) - Samsung Galaxy A20 ROMs, Kernels, Recoveries, & Ot

Moved here
https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423

steps
Installation Instructions.
There is never only one way to do anything. The following steps have worked for me.
Before you start, make sure you have rooted the A20
https://forum.xda-developers.com/android/development/root-samsung-galaxy-a20-rooting-guide-t3954872
This part may not be necessary if you're recovering from a crash.
To install TWRP
1. Download the U2 custom recovery from here
https://androidfilehost.com/?fid=1899786940962574261
2. On the PC rename the unpatched recovery as recovery.img
3. Use 7zip to make it into recovery.tar
(right click and choose add to archive)
4. Use 7zip to add your patched boot.img to recovery.tar
(right click and choose add to archive and choose recovery.tar)
5. Download vbmeta.tar from here (https://forum.xda-developers.com/showpost.php?p=80188834&postcount=237) and extract vbmeta.img
6. Use 7zip to add vbmeta.img to recovery.tar
(right click and choose add to archive and choose recovery.tar)
7. Install recovery.tar to ap slot using Odin.
If you are getting messages about being unable to flash the recovery try this.
https://forum.xda-developers.com/showpost.php?p=80216465&postcount=276
8. Boot the A20 into TWRP and mount everything that you can.
9. Format Data (not just wipe) - this will remove the encryption of the data partition.
10. Flash this zip View attachment Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
11. Reboot into Recovery. It may reboot into download mode. If it goes to TWRP skip step 12. If you already have a backup, you can go to step 16.
12. On the pc install recovery.tar to ap slot using Odin.
13. Reboot phone and re-enter all data.
14. Reboot into Recovery.
15. Backup only 3 parts: boot, data & system (not system image)
16. You can now restore boot, data & system from TWRP after any crash, but you may need to forget your wifi and go back in to it.
You can now move on to installing a new GSI ROM .
It you get stuck you can come back to Samsung by using your backup.
GSI ROMs are here.
https://forum.xda-developers.com/android/development/gsi-galaxy-a20-t3964546

Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around

jajk said:
Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around
Click to expand...
Click to collapse
How did you get a copy of the stock recovery?

@physwizz Stock recovery is in the AP image in the ROM.

jajk said:
@physwizz Stock recovery is in the AP image in the ROM.
Click to expand...
Click to collapse
I'll get grab it now.

jajk said:
Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around
Click to expand...
Click to collapse
After hitting dead ends with Mac and Windows, I succeeded in installing Android Kitchen on Ubuntu and unpack the s9 image.
Next step is to try to modify it to fit the A20
Hmmm...

Look at S10 Exynos TWRP versions also.

jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
Thanks

jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
Now I just need to work out how to repack it.

@jajk
AIK now wants an update-script and I can't repack the recovery.img without one.
Edit: went back to the Mac and worked it out.
Didn't install [email protected]

-deleted-

@TBM 13 Can you help build?

physwizz said:
@TBM 13 Can you help build?
Click to expand...
Click to collapse
I don't actually have the device yet. I will probably buy it in like two weeks (but i won't make nothing to it once i get bored, my parents will kill me if i brick it lol).
I can build TWRP, but i only have LOS 14.1 source (i'm not sure if that version of the source can work for a device with Android Pie).
I'm also a little bit noob on this.

TBM 13 said:
I don't actually have the device yet. I will probably buy it in like two weeks (but i won't make nothing to it once i get bored, my parents will kill me if i brick it lol).
I can build TWRP, but i only have LOS 14.1 source (i'm not sure if that version of the source can work for a device with Android Pie).
I'm also a little bit noob on this.
Click to expand...
Click to collapse
???

Does this device have a Telegram group?

TBM 13 said:
Does this device have a Telegram group?
Click to expand...
Click to collapse
No, not at this stage.

jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
The A30 have 2 versions of twrp.
https://forum.xda-developers.com/galaxy-a30/development/team-win-recovery-project-3-3-1-0-t3940850

@physwizz A30 TWRP appears never to have worked.
Kiss of death to have an off forum Telegram group - should be banned

Helpful Info
Download Odin Flash Tool For Android Phone, Then Extract It
Now Download >> TWRP Recovery
Then Go To Settings >> About Phone >> Tap On Build Number 5 To 7 Times You Will See Developer Option
Now Tap On Developer Option >> Then Enable USB Debugging And Also Enable OEM Unlocking
Now Boot Your Smartphone In >> TWRP Recovery Mode
To Boot Phone In Recovery Mode You Have To Turn Of Your Smartphone Then Press Volume Up + Power Botton Together To Turn On >> Recovery Mode
Then Select >> Reboot To Bootloader, After Some Time You Will See Downloading Mode
Now Cannect Your Smartphone To Computer Using USB Cable, Then Open >> Odin Flash Tool In Your PC
Now ID:COM Tab On Your Odin Will Turn Blue Which Means Your Phone Is Successfully Recognized By Odin Flash Tool, If It Doesn’t Reconnect Your Device And Check Again
Now Tap On >> AP Button On Odin Flash Tool And Select >> TWRP Recovery For Smartphone You Downloaded Earlier
Now Tap On >> Start Button
After Some Time You Will See “Pass” Button On Screen, It Means TWRP Recovery Successfully Installed On Smartphone

Related

[TWRP OFFICIAL] [3.2.1-0] c9ltechn/SM-C9000 Galaxy C9 Pro

TWRP for C9LTECHN/SM-C9000 Galaxy C9 Pro
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
PLEASE BEFORE YOU FLASH ROMS MAKE A COMPLETE BACKUP OF YOUR SYSTEM INCLUDING EFS SO YOU DO NOT BRICK YOUR MOBILE
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to intall TWRP using ODIN
1) Go to Settings » About phone » and tap “Build number” seven times to enable “Developer options”.
2) Go back to the main Settings page, scroll to bottom and select“Developer options” from there.
3) Under Developer options, look for “Enable OEM unlock”checkbox/toggle and make sure you Check it or turn it ON.
4) Now Boot your Samsung Android device into Download mode.To Do So Follow the steps below
5) Switch off your device.
6) Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Once your device is in download mode, connect it to the PC with a USB cable. The Odin will automatically detect the device and show an “Added!!” message. If not then your device is not connected properly
7) Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
8) Click the Start button on Odin to start Flashing and wait for it to finish the process.
Once it finished successfully, a pass message on the Odin screen will pop up
Your device will automatically reboot when Odin is done flashing. Now You can disconnect your device.
Done!!! TWRP is now installed on your device
NOTE: YOU MAY HAVE TO UNCHECK AUTO REBOOT IN THE OPTIONS TAB IN ODIN
TWRP source code: https://github.com/TeamWin
Source code device tree: https://github.com/travismills82/twrp_android_device_samsung_c9ltechn https://github.com/TeamWin/android_device_samsung_c9ltechn/
TWRP Nougat Download: https://www.androidfilehost.com/?fid=889964283620775437
TWRP Oreo Download: https://www.androidfilehost.com/?fid=1322778262903985796
no-verity-no-encrypt: https://www.androidfilehost.com/?fid=745425885120752506
ROOT OPTIONS:
SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Contributors @travis82 @k2wl @deadman96385
I can confirm this works. backup, mount data, restore, otg usb, install.
I am runnung it now
Does this work on a SM-C9000?
Flavio said:
Does this work on a SM-C9000?
Click to expand...
Click to collapse
That's already for C9000. Can't you see the c9ltechn article. That's c9 pro's code
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Flavio said:
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Click to expand...
Click to collapse
You can flash any file still that just an article but you can't mount data anymore or backup data
I can flash files but cannot mount Data. I presume it is still encrypted despite being formatted twice?
Format data and reboot to recovery
ivanox1972 said:
Format data and reboot to recovery
Click to expand...
Click to collapse
So in TWRP format Data and then reboot again in TWRP.
And then flash SuperSU and no_verity?
Ok, I formatted Data twice in TWRP. Mounting Data works.
I flashed SuperSU in TWRP. Mounting Data works.
I flashed no_verity. Mounting Data works.
I rebooted into TWRP. Mounting Data works.
I rebooted into system and then switched off and rebooted into TWRP. Mounting Data does not work.
What am I doing wrong?
Correction:
I have now used this no-verity-no-encrypt_ashyx file:
https://www.androidfilehost.com/?fid=24591000424951049
And now Data stays decrypted!
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
I tested it few days, it works perfect and it is perfectly debloated
Please share Travis. Thank you for your work.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
can you share it please ???
I presume you would have to flash GApps separately with this ROM?
Flavio said:
I presume you would have to flash GApps separately with this ROM?
Click to expand...
Click to collapse
no god no, HK firmware has gapps built in like normal. I'll tweak it up some more and release it today on a separate thread. Right now I'm trying to get kernels to boot-up since they compile fine.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
I am interested, currently I just using the package disabler to disable all bloat samsung app..
do you have flashable s8 systemui for c9pro.. thanks
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
travis82 said:
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
Click to expand...
Click to collapse
Awesome work buddy, ill try to make my own ROM for this device :highfive:
will be pushing f2fs and ntfs support soon too when TWRP becomes official.

[recovery][unofficial] twrp 3.2.3-0 sm-t530 / nu

Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
DJABHipHop said:
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
Click to expand...
Click to collapse
I always disable screen timeout in the settings of TWRP so I haven't run into that issue. Im not sure why you would say its buggy as hell. I dont think a screen timeout bug qualifies it for all that. Just disable screen timeout in twrp settings and move on. Certainly not a reason to downgrade, but to each their own I guess.
some one please port it to t330nu ...
MTP
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Reshan Kariyawasam said:
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Click to expand...
Click to collapse
Let me know if the camera and mic work
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
mrdreamers said:
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
Click to expand...
Click to collapse
Thats really odd!
As of right now I've seccessfuly fixed the microphone but its still really quite witch requird more digging all soulutions are welcome at this time freas build comming today for t530&t530nu user new thread started by to posted all device fixes and rom tweaks to The Samsung Galaxy Tab 4 in general.
https://drive.google.com/drive/folders/1F3qVR2Gy-SCqFwg5El7-aeGn6UhX-_-_?usp=sharing
DJABHipHop said:
Thats really odd!
Click to expand...
Click to collapse
ya i just odin firmware and started over no root no recovery, its a x-mas gift to my sister and law anyway she don't need all that, she's not nerdy like us lol!!!!
How it look?
How's the recovery doing? Is it working fully?
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
PizzaG said:
Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Click to expand...
Click to collapse
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
srialmaster said:
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
Click to expand...
Click to collapse
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
nico3dd said:
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
Click to expand...
Click to collapse
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
PizzaG said:
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
Click to expand...
Click to collapse
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
nico3dd said:
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
Click to expand...
Click to collapse
At this point I would probably start over from scratch and flash stock with Odin. How did you try installing updated TWRP?
If you want me to update the tar file with newer TWRP so it can be flashed with Odin, send me the tar file of old twrp and the newer twrp img file and i'll get that done for you.
can you please port the twrp to the t330nu?
zuhero said:
can you please port the twrp to the t330nu?
Click to expand...
Click to collapse
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
PizzaG said:
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
Click to expand...
Click to collapse
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Delete
---------- Post added at 06:12 AM ---------- Previous post was at 06:08 AM ----------
zuhero said:
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Click to expand...
Click to collapse
If you know how to get skype working on the tab 4 for matisse & milet device hit me up on tellgrem @DJABHipHop I can sure use the help with fixing all the little but anoying bugs.
Thenk in advance.

root android 9.0 sm-g965f

Hey guys , i have been looking on the forum ,i already have a rooted s9+ but on 8.0, i want to go over to 9.0 but i cant find a guide how to and what i need for it , maby im oberlooking the threads but maby someone can hel me out ?
Wesley_NL said:
Hey guys , i have been looking on the forum ,i already have a rooted s9+ but on 8.0, i want to go over to 9.0 but i cant find a guide how to and what i need for it , maby im oberlooking the threads but maby someone can hel me out ?
Click to expand...
Click to collapse
Just use the method you used on Oreo.
spawnlives said:
Just use the method you used on Oreo.
Click to expand...
Click to collapse
though i forgot its been a while , and somehow i can remember little doing with odin3 i needed serval fiiles
Wesley_NL said:
though i forgot its been a while , and somehow i can remember little doing with odin3 i needed serval fiiles
Click to expand...
Click to collapse
Yes you will need Odin. If you are going to use magisk then either flash twrp or use the patch method. Either way require Odin.
Personally I use twrp. You can copy all files needed ( on to SD card ) and flash within twrp.
spawnlives said:
Yes you will need Odin. If you are going to use magisk then either flash twrp or use the patch method. Either way require Odin.
Personally I use twrp. You can copy all files needed ( on to SD card ) and flash within twrp.
Click to expand...
Click to collapse
yes that was my plan stay magisks with twrp ,
altough i dont remember i did this when i installed twrp on mines
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop). Alternatively flash my stock patched kernel to the boot partition (install, install img, check the kernel, check boot partition, done). Find the patch kernel here
6. To disable encryption you need to format data
Wesley_NL said:
yes that was my plan stay magisks with twrp ,
altough i dont remember i did this when i installed twrp on mines
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop). Alternatively flash my stock patched kernel to the boot partition (install, install img, check the kernel, check boot partition, done). Find the patch kernel here
6. To disable encryption you need to format data
Click to expand...
Click to collapse
Basically yes. I would first do a backup ( I know but the amount of people not doing it and then wanting to know how to retrieve the lost data ).
In download mode check kg/rmm state is NOT in prenormal state.
Step 5 - allowing system to be modified - that's up to you. I normally allow modifications.
Then format data reboot back into twrp.
Flash/install - no verity zip, rmm bypass zip, magisk .
Hey i have a problem, i downloaded latest rom but my bt wont save bt pairings, what can i do about it

Lost root somehow, please help me fix it.

Hello everyone, my phone is samsung note 10 plus, I have twrp installed and rooted with magisk, I'm on Android 9, I somehow lost root, have no idea how, I'm very careful not to allow updates or google to install something there might affect my root.
when I go to magisk I'm getting the image that I've attached, when I click on install magisk, download the zip file and try to install it I get an an error as show in the 2nd image, saying unsupported/unknown image forma. I've also attached the log file. Is there any way for me to fix this without flashing the rom and start from scratch? Can I repair it somehow, maybe with TWRP?
Thank you all in advance
you have boot.img of the device?
i thought you can only install magisk in 2 way by flashing boot.img unto magisk or flashing magisk.zip unto TWRP as recovery partition
#edit how did you install magisk in the beginning? thats how you will install it again
there a chance you will get your device brick if you install magisk wrong way (A/B partition) but since you already install it previously just reinstall it back
Hmmm, where should I have the boot. Img you mean as if I backed it up on my pc? Or I can download it and use it?
Now I'm confused :/
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
ineedroot69 said:
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
Click to expand...
Click to collapse
Thank you very much.
OK, I tried method 2 and didn't work. I downloaded my stock firmware and I have the image file, I can try the first one to place the image in the root of the phone, patch the file with magisk and reflesh it with Odin?
Will I lose all my stuff on the phone by doing this? Thank you
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
ineedroot69 said:
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
Click to expand...
Click to collapse
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
drazenm said:
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
Click to expand...
Click to collapse
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
flash713 said:
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I can re root it, that's not the problem, i can do it with the patched magisk boot image through Odin, im asking if that's gonna wipe off everything on my phone. Because i can't backup certain things without titanium backup, and titanium requires root access. Thank you for your help and everyone's else's im well aware and grateful for the attempts, suggestions etc.
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
ineedroot69 said:
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
Click to expand...
Click to collapse
Thanks for the help, please correct me if im wrong.
Im supposed to copy the AP . md5 file to the root directory of my phone, patch it with magisk, get the patched file, copy it on the pc, connect phone to the pc, get it into download mode, flash the patched file with Odin and that should be it?
Or maybe i can do it with twrp?
Any suggestions?
drazenm said:
Any suggestions?
Click to expand...
Click to collapse
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
ineedroot69 said:
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Click to expand...
Click to collapse
Thanks so much for your help, but i just want to get root back on my phone as i had it rooted already, i dont want to wipe off everything and lose my stuff. There are things that i can only backup with titanium backup, which i can't use now without root privileges :/ can i repair root somehow?
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
ineedroot69 said:
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
Click to expand...
Click to collapse
I didn't do the update, but something did mess up the root aa you can see on the photos that I've attached at the beginning of the topic. I just want to reroot my phone again but not to loose all my current stuff on it.
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
thank you for taking your time to help me out, i appreciate it.
here is the link to the firmware file:
https://androidfilehost.com/?fid=6006931924117937015
inside are these files:
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
Any luck?
drazenm said:
Any luck?
Click to expand...
Click to collapse
sorry for late reply i'm kinda busy but to make it easier on my part (downloading 5GB file would take me 5 hours) can you just upload the following ?
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_ REV01_user_low_ship.tar.md5

Galaxy A8 Star (SM-G885S/F) GSI ROM Flashing [Android 12 Working]

This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )​Support Project Treble​Support System as root​
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※​Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )​​Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902​​Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/view​​Certification_Patch.zip: (at the attachment)​​Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)​​most rooms with AB partition will be supported​​Magisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)​​6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
[Update#1]
Today I have managed to install the Android Beta 3.1 [ is beta software and I don't recommend using it as your daily os]
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel4a_SBeta3.1%20-%20TBO42ZZ8IF/Pixel4a_SBeta3.1-AB-12-20210727-nippongsi.img.gz/download
you can download the ROM file from Nippon's Sourceforge
every step is the same and you just have to change the rom as this
there's a bug that developer setting crash the settings app and it is working but it does have some lots of bugs, and screen lock is not working but I'll try to fix it and upload the method
if your device get boot looped, press Bixby + power + vol down to boot into download mode and flash the stock AP file using Odin
[I was supposed to edit the upper one but accidentally created as a reply ]
Just go to UPDATE#2
Skuld Norniern said:
Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)
Click to expand...
Click to collapse
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
thongass000 said:
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
Click to expand...
Click to collapse
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Skuld Norniern said:
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Click to expand...
Click to collapse
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
thongass000 said:
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
Click to expand...
Click to collapse
Sorry for being late!!
for me, I do have the same issue with wired audio and I have not been able to find a way to fix it yet
if I manage to fix the issue I will fix the main article
Skuld Norniern said:
Skuld Norniern said:
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )​Support Project Treble​Support System as root​
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※​Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )​​Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902​​Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/view​​Certification_Patch.zip: (at the attachment)​​Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)​​most rooms with AB partition will be supported​​Magisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)​​6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
Click to expand...
Click to collapse
Hello sir i can't find havoc os 4.5 in:https://download.havoc-os.com/?dir=arm64-ab
Click to expand...
Click to collapse
After flashing twrp on my sm g885f, cant get into terp,
mine shows volume down + power to restart, not to enter turn off
how can i enter into twrp
Skuld Norniern said:
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
Click to expand...
Click to collapse
'os.img file' where
, guess i fixed it
when installing Certification_Patch.zip, it shows command error
what i found- this patch is for G885FDXS5CUL1, mine is
G885FDXU5CUG1

Categories

Resources