Hello
I am trying to update for a while now, but I just cannot get it installed.
I already have TRWP 3.3.0.0 running on a rooted Pocophone F1.
I am still kind of newbie using LOS, sorry. Some stuff I still don't understand even though spending lots of time reading and googling and reading...
What I do:
I start TRWP and wipe: WIPE ADVANCE Dalvik,Cache,System,Data
I install in the following order:
beryllium-V10.3.6.0.PEJMIXM-9.0-vendor-firmware
lineage-16.0-20191003-nightly-beryllium-signed
Disable_Dm-Verity_ForceEncrypt_02.04.2019
Magisk-v19.4
open_gapps-arm64-9.0-mini-20191003
then I reboot, stare a while on the working LOS-installing-log and...
boot to TRWP
I am experiencing problems while installation for some time, so I already tried:
- wiping dalvik after each zip during installation
- Magisk-v19.3
- leave out open-gapps
- beryllium-9.6.27-9.0-vendor-firmware
- lineage-16.0-20190807-nightly-beryllium-signed
- lineage-16.0-20190929-nightly-beryllium-signed
Where do I find information on which corresponding vendor/firmware to be used for LOS16?
Looking at the screen while installation of lineage-16.0-20191003-nightly-beryllium-signed, I read: "... Target: ...V10.2.3.0.PEJMIXM..."
So I guess I should flash that mentioned vendor/firmware version for that mentioned LOS version, but I just don't know where to download that vendor/firmware. It is not available on the server of akhilnarang...
Maybe I'm wrong and there might be another problem, I just do not know what to do.
Best regards
what rom your using before you installed los?
Clean flash would be needed ..you should wipe internal too to get it working , dont forget to remove all you password , fingerprint and face unlock.
Boot to recovery wipe system/dalvik/data/cache/internal before doing this you need to do a nandrioid back up..
do this:
download the lastest vendor:
beryllium-V10.3.8.0.PEJMIXM-9.0-vendor-firmware
next the LOS rom:
lineage-16.0-20191003-nightly-beryllium-signed
open_gapps-arm64-9.0-mini-20191003
and then
download the latest DFE version 19.3:
you can download it in telegram pocof1 group chat
and then wipe dalvik cache after that reboot system
first boot reboot to twrp recovery and the flash magisk v19.3 the reboot system....
i hope this method will help you..goodluck!!!
Prior to now, I had a 6 month old LOS working up to now.
My last attempt:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
says: "If you plan to install custom kernels, flash the zip AFTER installing Magisk".
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Zackptg5 says:"If you're not encrypted: flash all of your stuff, then FLASH THIS ZIP LAST"
I use the most recent DFE Disable_Dm-Verity_ForceEncrypt_10.01.2019 from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page64
most actual vendor/firmware i find here: https://xiaomifirmwareupdater.com/firmware/beryllium/
is: fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
I have not found a trustworthy source for the very new 10.3.8.0, but this should not be an issue...
So then, my new order is:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- Magisk-v19.4
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
Done that and REBOOT SYSTEM and....
Pocophone boots into FASTBOOT...
I am really pissed off at this point.
I can still enter TRWP 3.3.0.0 by pressing ON+VOLUP
I don't know any further.
So then, my new order is:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- Magisk-v19.4
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
Done that and REBOOT SYSTEM and....
Pocophone boots into FASTBOOT...
Why you didn't follow my instructions? clearly you dont understand ...
Oh...
I read your reply again, so is it correct you want me to:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT to RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
? ok in this order?
Sorry, found another mistake in my last description, now I tried:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT SYSTEM
-> after REBOOT SYSTEM, Poco F1 instantly starts into FASTBOOT. I then press ON+VOLUP to enter RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
-> still, Poco F1 instantly starts into FASTBOOT again.
That is where I am stuck now.
Andi900rr said:
Sorry, found another mistake in my last description, now I tried:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT SYSTEM
-> after REBOOT SYSTEM, Poco F1 instantly starts into FASTBOOT. I then press ON+VOLUP to enter RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
-> still, Poco F1 instantly starts into FASTBOOT again.
That is where I am stuck now.
Click to expand...
Click to collapse
install a global rom via twrp the latest one with 10.3.8.0 recovery flashable
go to twrp
flash the miui stable ..and then flash magisk 19.3 ..format data then reboot ... and then follow the steps i already given..
watch this for your reference https://www.google.com/url?sa=t&sou...BMAF6BAgFEAk&usg=AOvVaw09B7QXYvADkv7ZyNQtvH1K
Ok, will do that next day, thank you for your help and patience!!
In Recovery, I cannot "Swipe to unlock" anymore...
The touchscreen is not working. I had that issue several times in the past already. Rebooting to Recovery sometimes helps, but not now.
Andi900rr said:
In Recovery, I cannot "Swipe to unlock" anymore...
The touchscreen is not working. I had that issue several times in the past already. Rebooting to Recovery sometimes helps, but not now.
Click to expand...
Click to collapse
ok so its time to flash rom via fastboot ..just download the latest stable 10.3.8 fastboot rom after you install back up everthing first before flashing so you can restore if anything happens..back up only Boot , Recovery , System image , Vendor image , Efs and your good to go.. watch these and download are already included in this video https://www.google.com/url?sa=t&sou...BMAJ6BAgFEA4&usg=AOvVaw2naYU5q2jUaE5qUeskrBed[/url]
Before anything else ..use the twrp 3.2.3.0 recovery
Man, flash MIUI 10.3.8.0 on fastboot. ONLY MIUI. then boot... if it boot, tell us
Success flashing:
miui_POCOF1Global_V10.3.8.0.
recovery-20181211
Magisk-v19.3
rebootet to recovery, now into TWRP 3.2.3-0
I still wonder what was the problem and what was the solution...
Maybe formatting data was the solution?
From here, I backed up:
Boot
Recovery
System.image
Vendor.image
Efs
Backup created successfully; also copied to PC.
I wonder when installing LOS again from here on, if I should...
- update to TWRP 3.3.0-0
- update to Magisk-v19.4
or not.
bamz1117 said:
what rom your using before you installed los?
Clean flash would be needed ..you should wipe internal too to get it working , dont forget to remove all you password , fingerprint and face unlock.
Boot to recovery wipe system/dalvik/data/cache/internal before doing this you need to do a nandrioid back up..
do this:
download the lastest vendor:
beryllium-V10.3.8.0.PEJMIXM-9.0-vendor-firmware
next the LOS rom:
lineage-16.0-20191003-nightly-beryllium-signed
open_gapps-arm64-9.0-mini-20191003
and then
download the latest DFE version 19.3:
you can download it in telegram pocof1 group chat
and then wipe dalvik cache after that reboot system
first boot reboot to twrp recovery and the flash magisk v19.3 the reboot system....
i hope this method will help you..goodluck!!!
Click to expand...
Click to collapse
you can download it in telegram pocof1 group chat
Click to expand...
Click to collapse
please guide me to the group
****
I did the exact order bamz1117 wrote:
flashed:
-beryllium-V10.3.7.0.PEJMIXM
-lineage-16.0-20191003-nightly-beryllium-signed
-open_gapps-arm64-9.0-mini-20191003
-DFE 19.3
wipe dalvik
reboot system
and back into FASTBOOT...
Seems I am back where a was coming from? I am confused.
I have the suspicion that one of my zips is corrupted/defective/unproper version, but I have no idea which one.
When I flash
- beryllium-V10.3.6.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- Disable_Dm-Verity_ForceEncrypt_02.04.2019
wipe dalvik
reboot
- Magisk-v19.3
at least I see the LOS install logo working for quite a long time, but after that it reboots to TWRP recovery.
I noticed the following things:
concerning FW/vendor:
- beryllium-V10.3.6.0.PEJMIXM
I downloaded from https://mirror.akhilnarang.me/MIUI/beryllium/
is 451MB in size
- the newer ones:
fw_beryllium_miui_POCOF1Global_V10.2.3.0.PEJMIXM_a0319918c1_9.0
fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM_aa86bd1d08_9.0
are 91 MB each, I downloaded from https://xiaomifirmwareupdater.com/firmware/beryllium/
are those files fake?
Where to download V10.3.8.0 from a trustworthy source?
Would someone please explain me the proper order for a clean re-install (while rooted and TWRP recovery already installed) AND explain the reason behind that particular order?
My current understanding, which might be wrong:
1. Firmware/vendor first (obvioulsy this is giving hardware support to the operating system like with a PC), then
2. Lineage OS (this is the operating system) and
3. openGapps third (this modifies the operating system and includes google apps)
4. DFE (a kind of a script? which modifies the operating system by disabling verity/encryption/quota when setting the filename of the zip accordingly)
5. Magisk (offers services in order to hide rooting etc. to prevent apps with higher security e.g. online banking to detect security nonconformity and thus stop working)
Please correct me where and why I am wrong in that order - I want to understand it.
Thank you.
I dont know why but I lost TWRP meanwhile.
My Pocophone only starts into fastboot mode, I cannot invoke TWRP Recovery anymore.
I tried to flash the latest stock rom with "Tool all in one", which tells me bootloader is still unlocked.
But when I try to flash, a command window opens and closes immediately and nothing happens.
I try to run "Tool all in one" as admin, but it does not start.
I dont know what to do.
Was able to flash twrp 3.3.0-0 via fastboot... If I enter Recovery, it shows twrp 3.2.3-0 .... idk,wtf
I am able to restore Miui10 from backup! It runs!
But flashing vendor/LOS/DFE/Magisk is not working! WTF! No idea why.
Still have THE SAME fastboot-loop issue after flashing vendor/LOS/DFE/Magisk I STARTED WITH the first post.
Related
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
11 IF YOU WANT TO UPDATE TO B02 : use this methode https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me? Forgot to mention I have 3.0.4 twrp
HTC55555 said:
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me?
Click to expand...
Click to collapse
Don't know exactly.
For G users the latest update before 7.0 was the B10. Therefore B10 is the necessary flash before G users can flash N
As long as you keep TWRP running ( as far as i know do not wipe system etc...therefore i mentioned earlier to not wipe anything) and your latest backup, you can always restore it.
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Choose an username... said:
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Click to expand...
Click to collapse
Perhaps this will help : https://forum.xda-developers.com/showpost.php?p=71444519&postcount=494
unplug usb when you give command to flash twrp recovery, otherwise it always reflashes stock recovery....
Hope that helps
Thanks for the reply! I'll have to figure out how to make axon7tool work now. Much appreciated
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
ValVK said:
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
Click to expand...
Click to collapse
IMO you have to flash b10 too. Would do no harm though as long as you don't fully wipe system to keep twrp. As long as you keep a backup of twrp you can always go back. In worst case you have to flash twrp again in edl axon7tool.
@ValVK I flashed B03, then B08, then B10, and THEN B01, like any normal update. That because I don't know if B10 is only an incremental update
But after you flash the stock system, remember to root! You'll lose TWRP otherwise
Thanks all for responces! If i will go that way-flash in Twrp b08, then b10 and then Nuga, what should i wipe first in Twrp-all inclusive System, or just Factory reset? And if i will go that way, should my Twrp still intakt? (I would like avoid to Flash Twrp again, seems bit risky for me).
I had the official bootloader unlock but it broke the com.android.phone process on 7.1.1.
They are working on getting it fixed and once fixed will make the root publicly avialble.
The official root works on b10 marshmallow and is very easy to install.
@ValVK o sorry, I only flashed B03 :silly:
You should flash B03 THEN update via the native sdcard update on mifavor
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Oliver Aa said:
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Click to expand...
Click to collapse
I suggest you wait for the 7.1.1 OTA update when you're not rooted etc.
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
S0wL said:
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
Click to expand...
Click to collapse
Did you follow my steps ? From which version did you come ? Were you already rooted....
Perhaps flash SU 2.79 (!) in edl mode and when it is resetting for a reboot, unplug your phone before it can reboot. You get a black screen. Just press Vol+/Power and when you see ZTE logo you release. Normaly you should/can enter TWRP.
But normaly my guide should work if you were rooted, BL unlocked and on stock ROM (B08 or earlier). I do not know which steps you already performed so it's just gessing.
What you guys think??
I want to know if I update my phone to this version, can I continue using xposed
Hello, can someone create TWRP files from the new B02 image?
Gesendet von meinem ZTE A2017G mit Tapatalk
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
dnlilas said:
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
Click to expand...
Click to collapse
IMO step 8 can not be skipped due to the fact you have to have 7.0 first. Could be wrong, but then again, it only last for a minute or so
I will ad the link to upgrade B01 to B02.
Thnx !
ps : did you get B02 with my method ? Pls post on thread if succeeded - thnx !
Hello everyone, im kinda new here and i have a question:
How do i correctly root my phone? I know that ill still be able to get updates since its xiaomi, but i dont really know how to do it since i dont trust supersu and kingoroot, could you help me out?
If you need any technical info from my phone, just ask in the comments
install twrp 3.2.3 and magisk 17.2 files to your pc and flash twrp to your phone using adb. After u flashed twrp to your phone enter it and flash magisk file from sd card or flash drive with otg cable. (your data might be deleted)
Kaanarchy said:
install twrp 3.2.3 and magisk 17.2 files to your pc and flash twrp to your phone using adb. After u flashed twrp to your phone enter it and flash magisk file from sd card or flash drive with otg cable. (your data might be deleted)
Click to expand...
Click to collapse
umm, eh, i didnt understand a word you were saying after "flash twrp"
I did this. Coming from miui 10.0.4
- Restart in fastboot mode.
- Flash TWRP
- Enter recovery. Flash magisk. Maybe here u will got a problem with data partition... ( I have it.. my solution was using orange fox).
- After this u got your device rooted... Restart in system. Install magisk APK.
If you have that problem with the data partition...
Here in the forum there is a lot of info about that.
After you flashed twrp from adb via "fastboot flash recovery twrp.img" command; hold volume up + power on/off button until you see the teamwin title from your phone. So you must be in twrp now.. Your data will be crypted because using twrp for the first time. Go to wipe - format data, write "yes" and confirm. Reboot recovery by going to ‘Reboot’ -> ‘Recovery’. go to the ‘Mount’ menu. press the ‘Enable MTP’ button. Transfer Magisk 17.2 to your phone's internal storage (check other posts for guide, you will use adb sideload) or you can just move your magisk file to your sd card or your flash drive(you will need otg cable to connect flash drive to phone) . Return to menu, go to install, press magisk.zip and then swipe to flash it. When the installation is complete, press the ‘Wipe Cache/Dalvik’ button. And that's it now just reboot your system
foxmonter said:
I did this. Coming from miui 10.0.4
- Restart in fastboot mode.
- Flash TWRP
- Enter recovery. Flash magisk. Maybe here u will got a problem with data partition... ( I have it.. my solution was using orange fox).
- After this u got your device rooted... Restart in system. Install magisk APK.
If you have that problem with the data partition...
Here in the forum there is a lot of info about that.
Click to expand...
Click to collapse
I'm stuck on Orange Fox for hours now. In twrp there is a chance for loosing my data, so I am using orange fox. After unlocking the bootloader I flashed the Orange Fox recovery and while performing a nandroid backup, it shows me a error saying "error on uevent". But the nandroid backup finished and so I carried on with the process. Now I wiped my data, system and dalvik and normal cache. I clicked on install and on the ROM(arrow) and swiped right. The installation after sometime of progress abruptly ends giving Error 7. So I thought of Restoring back my nandroid backup and it did complete but with an error 255. Can you help me?
Yeshu_bablu said:
I'm stuck on Orange Fox for hours now. In twrp there is a chance for loosing my data, so I am using orange fox. After unlocking the bootloader I flashed the Orange Fox recovery and while performing a nandroid backup, it shows me a error saying "error on uevent". But the nandroid backup finished and so I carried on with the process. Now I wiped my data, system and dalvik and normal cache. I clicked on install and on the ROM(arrow) and swiped right. The installation after sometime of progress abruptly ends giving Error 7. So I thought of Restoring back my nandroid backup and it did complete but with an error 255. Can you help me?
Click to expand...
Click to collapse
All your answers are here: https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
PS: I hope you rebooted the recovery after doing all that wiping, and before doing anything else.
Hello,
Since MIUI 10.3.1.0 (PEIMIXM) was launched, I tried to update my device. After the update, when the smartphone rebooted it kept stuck in Mi logo sreen (Android loading wasn't also appearing). I tried to use MiFlash to reflash the ROM and the same happended.
Thinking it was a random problem of MIUI I decided to move to Pixel Experience because I had used it before and I liked. In the same day of MIUI 10.3.1.0 (PEIMIXM) launch, Pixel Experience also launched a new whyred version (in the beggining of June, i think).
I did what was needed to successfully install the ROM according to the dev's thread:
-I downloaded all the needed files (MIUI 10.3.1.0 PEIMIXM firmware, Pixel Experience ROM, recommended modified TWRP version of the developer);
-Initially, I installed TWRP via fastboot mode;
-I flashed the firmware;
-I wiped the partitions Cache Dalvik / ART, System, Cache, Data, vendor;
-I flashed Pixel Experience ROM;
-I wiped Internal Storage;
-I rebooted the device.
After those steps, I couldn't get access to my "homescreen". Basically, my phone stays stuck at the Mi logo screen. And nothing happens.
Considering it could be a recovery problem, I tried to use Pitch Black Recovery (the latest version available for whyred) that supports Oreo and Pie. I used TWRP to flash this one, and after that I made all the steps above again and the same happened.
I'm now only available to flash MIUI (if it is Android 8.1). I can only flash Pixel experience versions that were released before the MIUI Pie stable for this device.
I really appreciate if you could help me!
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
htchd2sucks said:
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
Click to expand...
Click to collapse
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
floater3 said:
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
Click to expand...
Click to collapse
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
htchd2sucks said:
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
Click to expand...
Click to collapse
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
floater3 said:
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
Click to expand...
Click to collapse
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
htchd2sucks said:
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
Click to expand...
Click to collapse
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
floater3 said:
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
Click to expand...
Click to collapse
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
htchd2sucks said:
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
Click to expand...
Click to collapse
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
floater3 said:
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
Click to expand...
Click to collapse
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
htchd2sucks said:
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
Click to expand...
Click to collapse
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
floater3 said:
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
Click to expand...
Click to collapse
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
htchd2sucks said:
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
Click to expand...
Click to collapse
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
floater3 said:
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
Click to expand...
Click to collapse
It's clearly not related to recovery, at least, not directly.
-Check what "wipes" you have done, and ideally do all of them + format data (you can always reencrypt later). Then, reboot, and redo the flashing of everything.
-Another option would be to flash with "miflash" which I think will also restore some boot things. In that scenario, you are on your own because I don't know about ARB in your case and all potential issues.
I can only say that I did a "miflash" when I used to have ARBv3, and it went fine (I had to redo the recovery, etc... after).
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