Related
Hi guys, need a bit of help. I followed the following guide and seems like a new recovery has been installed on my note 2 but no root or twrp. Any ideas ?
http://xiaomitips.com/guide/how-to-root-and-unroot-redmi-note-2/
Phone is fine but i do need to root and have twrp installed on it. Alternatively, do you have a link where I can achieve this easily as I want to put a a new rom on my phone. Sorry for the amateurish questions, its been a while since i have installed custom roms
Many thanks
This guide is old.
When I received my RN2 I installed TWRP from the Updated app, but now this is not possible anymore.
You have to flash TWRP image via fastboot.
Look at Fastboot Install Method here: https://twrp.me/devices/xiaomiredminote2.html
The image could be downloaded from: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
Remember to keep vol+ pressed when you'll restart using fastboot reboot until it enter TWRP to prevent original recovery from restoring.
Once you are done, you'll be able to flash SuperSU.
Ok, ill try that. Thing is that I have lost fastboot, when i do power + volume up, i get to the TWRP 2.8.7 screen. Is this a problem ?
gnazio said:
This guide is old.
When I received my RN2 I installed TWRP from the Updated app, but now this is not possible anymore.
You have to flash TWRP image via fastboot.
Look at Fastboot Install Method here: https://twrp.me/devices/xiaomiredminote2.html
The image could be downloaded from: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
Remember to keep vol+ pressed when you'll restart using fastboot reboot until it enter TWRP to prevent original recovery from restoring.
Once you are done, you'll be able to flash SuperSU.
Click to expand...
Click to collapse
power + volume up is to enter recovery
To enter fastboot use power + volume down.
EDIT:
if with power + volume up you are entering TWRP, there is not need to do other than install supersu (unless you want to update TWRP).
Many thanks. Got this sorted. Running cm at the mo, cool. What is the best rom in ur opinion by the way? Any oxygen based roms?
I don't know the current status of CM on RN2, but generally speaking, IMHO ported ROM are not better then official ROM because there is always something not working.
Unfortunately there are no sources for RN2.
Requirements / Downloads
Honor 10 view BKL-09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk BKL
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager canary build to your phone and install.
2. Change in Magisk settings the update channel to "custom" inserting this URL. https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
3. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
4.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
ORIGINAL RECOVERY_RAMDISK BKL-09 PIE version 9.0.0.162 C432
5. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Thanks
Thanks a lot for this great guide!
Hello, will this also be on my bkl-l09c432? I have rom
blazios said:
Hello, will this also be on my bkl-l09c432? I have rom
Click to expand...
Click to collapse
If your device is on pie ?, yes
What should I use twrp?
blazios said:
What should I use twrp?
Click to expand...
Click to collapse
OP never mentioned anything about twrp. That is not needed
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
BlueMan_86 said:
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
Click to expand...
Click to collapse
Flash in bootloader mode. Not in twrp.
Android pie not work with twrp for now.
I am on ROOTED EMUI 8.0 (BKL-L09 8.0.0.130). How do I update to pie and then root? First unroot than update than root? or just update and root with the instructions in post#1?
Sadly it does not work for me. Tried it with your patches bootimage and with my own. Flashing the ramdisk works fine but after restart I don't have root.
I dont need Magisk installed if I use the pre patches bootimage right? Nevertheless I tried with Magisk installed and without. In the Huawei Mate Forum I read that one might need to shutdown the phone after flashing and then to start it with Volume Up and Power Button pressed. But this also does not work. Or any Idea how exactly to start with this Key combination?
Any other suggestions?
Today I updated from OREO with root to PIE same version as you have in pictures 9.0.0.162(C432E4R1P9). Tried both steps (with your patched file and me patching file) to root my phone but even I always got OK in fastboot mode I still have no root
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
I get the same error
any advise ?
Worked like a breeze for me. Shoutout to @ante0 and @shashank1320 who kept their calm in guiding me through and suggesting me this method.
@ante0 made things easier for me and it worked excellently for me. The steps are-
Download and install Magisk canary builds from the mentioned link. Change in Magisk settings the update channel to "custom" inserting*this*URL.*https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
Check "force encryption" and "AVB 2.0" boxes.
Transfer stock recovery ramdisk to phone, open Magisk Mnager and hit install - > patch boot image, select recovery_ramdisk.img. Take patched_boot.img from /sdcard/Download/ and transfer to computer, reboot to fastboot and flash patched_boot.img to recovery_ramdisk. Unplug USB, holv vol up + power to reboot to recovery, which will now boot phone with Magisk. If you reboot and don't hold vol up it will boot to system without root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Huge thanks @fabio84
Finally have root privileges on Pie.
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
davidsiv said:
I get the same error
any advise ?
Click to expand...
Click to collapse
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Not flash ramdisk. Need flash recovery_ramdisk!
worked, thanks
fabio84 said:
Not flash ramdisk. Need flash recovery_ramdisk!
Click to expand...
Click to collapse
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
ankan1993 said:
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
Click to expand...
Click to collapse
Update: @ante0 helped me yet again to figure it out. Apparently was because of pie's aggressive background restrictions. Root is now working full fledgedly. Thanks everyone. Big cheers to @ante0
Hello,
It finally worked for me. Thank you so much!
ante0 said:
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Click to expand...
Click to collapse
Hi,
I have a stock ANE-LX1 9.1.0.355(C55E8R1P6)
I just can't root the phone!!!!
I tried both flashing the Magisk zip from TWRP and patching the recovery_ramdis.img from the app and then flashing from fastboot, but
Magisk Manager just doesn't see Magisk.
Plz help, thanks
David
DP FH said:
Hi,
I have a stock ANE-LX1 9.1.0.355(C55E8R1P6)
I just can't root the phone!!!!
I tried both flashing the Magisk zip from TWRP and patching the recovery_ramdis.img from the app and then flashing from fastboot, but
Magisk Manager just doesn't see Magisk.
Plz help, thanks
David
Click to expand...
Click to collapse
Hey dude try this way out...
- Download Magisk manager apk. , patched recovery_ramdisk and TWRP for 9.1:
https://mega.nz/#!ohkgwSzb!xD32btG_3Sax-V7bn6xbWR5fH0crPrry06cCxusf5Hg
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
https://mega.nz/#!xkd2ibKY!JCLNMNKRI1e0FI1bJ4YI5Lr9Hdg9eo4A9kv0MhxgIdA
Copy TWRP and patched recovery_ramdisk to SD Card, install Magisk manager apk.
- Install TWRP over eRecovery: flash downloaded TWRP 9.1 from fastboot, boot in TWRP, select storage - SD Card, select "Install image". Find TWRP-9.1.img file , mark eRecovery and confirm. Reboot system.
- When the yellow unlocked phone warning appears, press and hold Volume Up , phone will boot into TWRP.
- Select Install image, find Recovery_ramdisk-patch.img , mark Recovery, confirm.
- Go back to the main TWRP's menu > Reboot > Reboot recovery. Phone will reboot via Recovery , but not into Recovery mode. Now every time you want to boot phone with root access must hold volume up and power at the beginning . if you boot phone normaly (not thro recovery comand) your phone will not be rooted!
Now you have a rooted phone with TWRP on board.
Ok thanks, isn't it possible to workaround the volume up stuff? How do I boot twrp after I finished? Vol+ and power button or vol+ and cable? To my understanding, this boots two different recoveries?? Why is it so complicated lol
DP FH said:
Ok thanks, isn't it possible to workaround the volume up stuff? How do I boot twrp after I finished? Vol+ and power button or vol+ and cable? To my understanding, this boots two different recoveries?? Why is it so complicated lol
Click to expand...
Click to collapse
Is your patched_ramdisk "universal" ? I meant will it work on phone with different cust (mine is c55, most have c432 and maybe with different emui version? Where did you get it?)
- it is just an alternative, the method with patched recovery_ramdisk and fastboot should also work. Maybe you're doing something wrong.
- It is complicated due to emui 9.1, the ramdisk partition no longer exists. As a workaround, Magisk will be installed to the recovery_ramdisk partition.
- AFAIK partitions Recovery and eRecovery are the same for all build numbers and regions (we are talking about ANE- models and EMUI 9.1), so it should work.
- "How do I boot twrp after I finished?" - read carefully please: " Reboot system. When the yellow unlocked phone warning appears, press and hold Volume Up , phone will boot into TWRP."
P.S.: I never try to convince anyone of anything, it's your choice .
If you do not understand something here, than the tutorial might not be suitable for you.
There are plenty of guides on how to do these things. GL!
-Alf- said:
-the method with patched recovery_ramdisk and fastboot should also work.
Click to expand...
Click to collapse
I tried the following:
Booting into TWRP, getting recovery_ramdisk with dd, patching image with manager, boot into twrp, flash new recovery_ramdisk with dd, reboot.
Getting recovery_ramdisk from official update, patching etc.
Flashing official Magisk v21.1 with zip. The new image is flashed because the second time it will say "magisk patched image detected" (even if i reboot into twrp again), but still no root.
Sincerely I do not understand what I'm doing wrong. I know myself it should be easy.
I understand the tutorial (and thank you for it, you are a very kind person) I just don't understand why huawei made things so unnecesarely complicated. How does the phone boot without a ramdisk? Is "normal" ramdisk included in the kernel partition or in the recovery_ramdisk partition? Ok I get it, if there is no ramdisk the phone boots directly from the system on root partition, so magisk should mod that partition but it can't because it defeats the purpose of "systemless". Right?
There are plenty of guides, yeah, but everyone says the same thing (magisk zip or patched ramdisk) and people just say it works... but in my case it just... doesn't
Will try to follow your guide to the letter... Thank you again...
Ramdisk is included in the recovery_ramdisk, that's why Magisk will be installed to the recovery_ramdisk partition. Read carefully bro
Note: if you want use TWRP on rooted EMUI 9.1, you MUST install TWRP over eRecovery.
DP FH said:
I tried the following:
Flashing official Magisk v21.1 with zip.
Click to expand...
Click to collapse
Try with lower version , v20.0 or v20.4
Ok, thank you for your tips. I will update you once I have time to spend on this.
TWRP 3.5.0 One UI 3.1 for Samsung Galaxy A50 Android 11. How to Root Samsung Galaxy A50 Android 11 with TWRP 3.5.0 + Magisk. The TWRP Recovery support Galaxy A50 One UI 3.1 Android 11 firmware. It may be works for SM-A505F, SM-A505FN, SM-A505G, SM-A505GN. The TWRP 3.5.0 comes with Magisk Patched. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
LET ME KNOW IF IT WORKS FOR:
SM-A505FN, SM-A505G, SM-A505GN
Manual Instructions for Flashing and Rooting
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing TWRP as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Appears.
Format data
Install multidisabler-samsung-2.6.zip
Reboot to Recovery
When SAMSUNG logo appears wait for a few minutes or more then press and hold volume down + power key until the screen blank
Setup the phone
Connect Phone to Internet
Install Magisk-v22.0.apk and Open it. Magisk will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Video Instructions - Details
Download
TWRP 3.5.0 A11
Magisk22 app
Thanks to:
@neel0210 for Kernel Source
@Enzoaquino for OrangeFox
Good work
Thanks for twrp
Thank you
Flashing this @ A505GN. Hope it works
The twrp works but the multi disabler didn't work
This is a505gn
I reverted back to 3.4 because I encountered an issue. I'm stuck in bootloop, cannot access twrp nor download mode. Had to remove the back of my phone and unplug the ribbon connecting the battery to the phone just to power it off.
I already flashed the twrp via Odin but when I installed Magick on the phone this came up. Did I done something wrong?
q1pa said:
I already flashed the twrp via Odin but when I installed Magick on the phone this came up. Did I done something wrong?
Click to expand...
Click to collapse
it happens to me sometimes
just rebbot to revocery in twrp
Thank you @redymedan for the recovery. I'm glad to say that
your "how to android" channel is great.
I have a question Please clarify the following.
In this recovery Can we update magisk to latest? (When it released)
Sharath Mane said:
Thank you @redymedan for the recovery. I'm glad to say that
your "how to android" channel is great.
I have a question Please clarify the following.
In this recovery Can we update magisk to latest? (When it released)
Click to expand...
Click to collapse
Yes, you can update it from magisk apps
It worked!
I had to run a patched AP first for magisk to work
Im on a A505G/DS
It worked just fine on my A505FN! Thanks!
Worked perfectly on A505W !
Had to use Multidisabler 3.1 instead.
I have an A505FN and I'm not able to root it with Magisk. If I try to install the linked TWRP_v3.5.0_A505_A11_Magisk.tar with Odin, then I can't reboot into Recovery afterwards - instead the Download-Mode appears again.
With RR-TWRP_v3.4.0_A505_CUBC_OneUI.tar from another Thread, it's possible to start into TWRP after flashing it with Odin. But if I boot into System (LOS 18.1) and start the already preinstalled Magisk, Magisk updates itself and after restart of Magisk I can try to install Magisk and in the first screen "Recovery Mode" is checked. If I click on "Next step", the Option "Recovery Mode" disappears and I can choose a file to patch.
I don't know where I'm wrong.
IngolfN said:
I have an A505FN and I'm not able to root it with Magisk. If I try to install the linked TWRP_v3.5.0_A505_A11_Magisk.tar with Odin, then I can't reboot into Recovery afterwards - instead the Download-Mode appears again.
With RR-TWRP_v3.4.0_A505_CUBC_OneUI.tar from another Thread, it's possible to start into TWRP after flashing it with Odin. But if I boot into System (LOS 18.1) and start the already preinstalled Magisk, Magisk updates itself and after restart of Magisk I can try to install Magisk and in the first screen "Recovery Mode" is checked. If I click on "Next step", the Option "Recovery Mode" disappears and I can choose a file to patch.
I don't know where I'm wrong.
Click to expand...
Click to collapse
Flash stock rom with odin
Reboot. Do not login to google. Check oem grayed out.
Reboot to download mode
Select 3.5.0 twrp as ap. (You should Untick autorestart in options) . Start.
By connecting cable reboot into recovery by using button combo. Do not reboot to system. Do not remove cable.
After entering twrp.
Format data. Next flash multidisabler.
Now select reboot to recovery.
Wait for few minutes, if doesn't boot,force restart by using volume down and power buttons. It will bootup.
You can finish ur setup now.
You can flash other roms . To enter twrp you need to connect cable with pc and use buttons.
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
IngolfN said:
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
Click to expand...
Click to collapse
you will edit your ini.environ.rc
watch it in youtube
IngolfN said:
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
Click to expand...
Click to collapse
Goto twrp and select reboot recovery
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 TrebleSupport 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=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_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 supportedMagisk: 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 TrebleSupport 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=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_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 supportedMagisk: 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