Hello. I have an unlocked G8342, and I'm trying installing phh's GSI. But after I flashed the system image, I cannot boot my phone. It just shows "SONY" and then rebooted automatically.
I tried flashing the SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_yoshino.img or SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_yoshino.img.
Before I unlock my phone, I've upgraded to the official Pie release. But what I'm installing is Oreo. Does this matter? Or what should I do in order to make it work?
Balthild said:
Hello. I have an unlocked G8342, and I'm trying installing phh's GSI. But after I flashed the system image, I cannot boot my phone. It just shows "SONY" and then rebooted automatically.
Before I unlock my phone, I've upgraded to the official Pie release. But what I'm installing is Oreo. Does this matter? Or what should I do in order to make it work?
Click to expand...
Click to collapse
if u dont backup ur TA partition before unlocking your bootloader, camera will not work on oreo gsi roms. I recommend u can try pie gsi roms, but it has worse camera quality and stability issues..
arslancn said:
if u dont backup ur TA partition before unlocking your bootloader, camera will not work on oreo gsi roms. I recommend u can try pie gsi roms, but it has worse camera quality and stability issues..
Click to expand...
Click to collapse
I just cannot even boot the GSI ROM. The camera might have issues, but it's not important right now...
Balthild said:
I just cannot even boot the GSI ROM. The camera might have issues, but it's not important right now...
Click to expand...
Click to collapse
I am having the same issue as you, I can't boot every gsi, even the 9.0 ones
yuezhengbaizhi said:
I am having the same issue as you, I can't boot every gsi, even the 9.0 ones
Click to expand...
Click to collapse
what gsi rom are you trying to flash? Do you have TWRP installed? I have a SOV36 (Japan AU version) and it boots with most of all gsi's. Currently using omni rom.
Here is my steps for flashing.
1. boot into twrp
2. goto wipe and factory reset (don't wipe data, system or cache just factory reset)
3. flash img
3a. optional: goto wipe; repair and resize system (if you want gapps)
4. flash gapps
5. flash magisk if you want root
6. reboot
Hope this helps
sinkoo1979 said:
what gsi rom are you trying to flash? Do you have TWRP installed? I have a SOV36 (Japan AU version) and it boots with most of all gsi's. Currently using omni rom.
Here is my steps for flashing.
1. boot into twrp
2. goto wipe and factory reset (don't wipe data, system or cache just factory reset)
3. flash img
3a. optional: goto wipe; repair and resize system (if you want gapps)
4. flash gapps
5. flash magisk if you want root
6. reboot
Hope this helps
Click to expand...
Click to collapse
I have tried the Phh's latest 9.0 GSI and RR's GSI and ERFAN's Q GSI and the official q GSI from Google.
None of them work, all stuck on the Sony boot logo
yuezhengbaizhi said:
I have tried the Phh's latest 9.0 GSI and RR's GSI and ERFAN's Q GSI and the official q GSI from Google.
None of them work, all stuck on the Sony boot logo
Click to expand...
Click to collapse
latest RR gsi did not work for me either but roms like omni, bootleggers, lineage 16 all booted on my SOV 36
Flash the lastest pie ftf, then follow sinkoo1979, instructions, also be sure you only flash ARM64-A versions.. I know Omni, Bliss and bootleggers work with imo bootleggers was the nicest but the unofficial one here has ceased development.. Use open camera for your pics...
The Roms are a hit or miss...make and keep a twrp backup handy...
Related
Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !
Hello Friends,
After a lot of search and read I am confused. What is complete set of steps required to flash MM rom (non Miui)? What precautions I should take since I unlocked unofficially?
My needs for daily driver is
Good battery life
Working GPS
Working Camera
Root (for titanium backup and adblock)
Current status
Unlocked - UNOFFICIALLY
Recover - ALKA
Rom - Miui LP Global stable
Security - Fingerprint + Pin
Steps I have collated so far
* Remove pin and delete fingerprints
* Do I need to do something about encryption ?
* Goto recovery
** Should I flash another recovery ??
** Nandroid backup
** Wipe cache/dalvik/data/system
** Flash
**** CM13 Firmware
**** Rom (Example RR 5.7.4)
**** Kernel (Example Radon)
**** Gapps
** Clear Dalvik
** Reboot
If fingerprint issue
* Goto recovery
** Flash
**** Goodix Fp8 ( First check if Goodix)
**** Kernel
** Wipe Dalvik
** Reboot
Thanks for your inputs on above. Please also suggest MM rom suitable for my needs.
I'd suggedlst you use Cyanogenmod 13 by TheStrix.
All are stable, I haven't encountered any issues.
What you need to do
-Phone's bootloader needs to be unlocked
-Flash CM13 Firmware (if you're coming from MIUI8, no need to flash this)
-Flash CM13 ROM (Snapshot)
-Flash GAPPS
-Flash Radon Kernel latest version. (I recommend you to usre Radon Kernel because the stock kernel has battery reading issues, it decreases by 2%)
exce1ia said:
-Flash CM13 Firmware (if you're coming from MIUI8, no need to flash this)
Click to expand...
Click to collapse
Thanks.
* I'm at MIUI 8 but Lollypop .. so if I get you correctly, I need not flash CM13 firmware.
* Another query - is there no extra precaution required for Unofficial unlock and no need to use any other TWRP?
hyperorb said:
Thanks.
* I'm at MIUI 8 but Lollypop .. so if I get you correctly, I need not flash CM13 firmware.
* Another query - is there no extra precaution required for Unofficial unlock and no need to use any other TWRP?
Click to expand...
Click to collapse
I had a problem with unofficially unlocking maybe because the unofficial unlock requires to flash Lollipop Global ROM and I was running MM. What I did is find a way that requires to flash MM Dev ROM to unlock. Maybe you won't have a problem if you're gonna flash it using Dev ROM.
exce1ia said:
I had a problem with unofficially unlocking maybe because the unofficial unlock requires to flash Lollipop Global ROM and I was running MM. What I did is find a way that requires to flash MM Dev ROM to unlock. Maybe you won't have a problem if you're gonna flash it using Dev ROM.
Click to expand...
Click to collapse
I'm not on dev rom but on Global Stable MIUI8 Lollipop
kenzo_global_images_V8.0.6.0.LHOMIDG_20161025.0000_5.1_global_e45dc39209
hyperorb said:
I'm not on dev rom but on Global Stable MIUI8 Lollipop
kenzo_global_images_V8.0.6.0.LHOMIDG_20161025.0000_5.1_global_e45dc39209
Click to expand...
Click to collapse
Try and see if you'll get no problem.
i currently on RR 5.7.4 work smooth and stable thanks to developer
i preffer use zcx recovery, because never tried other haha
but dont forget to mount every single time boot to recovery
1. Full Wipe System, Data, Cache, Dalvik, (Internal Storage (optional))
2. Reboot Recovery
3. Flash 8.1.1 Global Stable Rom Marshmallow Based ( Recovery Rom )
4. let the rom boot first till home screen but dont login miui account
5. Turn off and boot to recovery
6. Do Wipe System, Data, Chache, Dalvik again
7. Reboot to recovery again
8. Flash Rom that you want
9. Flash GAPPS
10. Wipe dalvik chache
11. Done reboot system ( i use fpc but if u have goodix should patch the goodix first)
my device was unlocked officialy
ozan6661 said:
i currently on RR 5.7.4 work smooth and stable thanks to developer
i preffer use zcx recovery, because never tried other haha
but dont forget to mount every single time boot to recovery
1. Full Wipe System, Data, Cache, Dalvik, (Internal Storage (optional))
2. Reboot Recovery
3. Flash 8.1.1 Global Stable Rom Marshmallow Based ( Recovery Rom )
4. let the rom boot first till home screen but dont login miui account
5. Turn off and boot to recovery
6. Do Wipe System, Data, Chache, Dalvik again
7. Reboot to recovery again
8. Flash Rom that you want
9. Flash GAPPS
10. Wipe dalvik chache
11. Done reboot system ( i use fpc but if u have goodix should patch the goodix first)
my device was unlocked officialy
Click to expand...
Click to collapse
Thanks.
I think since mine is unofficial then Step 3 requires removal of emmc_appsboot.mbn before flashing. Also I will need to remove recovery.img from the miui rom to avoid TWRP being overwritten
I get the idea that we need to flash miui mm rom first so that partitions are created. But doesn't that can be taken care by flashing CM13 firmware?
hyperorb said:
Thanks.
I think since mine is unofficial then Step 3 requires removal of emmc_appsboot.mbn before flashing. Also I will need to remove recovery.img from the miui rom to avoid TWRP being overwritten
I get the idea that we need to flash miui mm rom first so that partitions are created. But doesn't that can be taken care by flashing CM13 firmware?
Click to expand...
Click to collapse
did u know how to remove emmc_appsboot or replace that ? is the recovery rom will replace the TWRP if flash the rom recovery ?
yup is better to flash miui mm first and unlocked bootloader, CM13 is to old and didnt get update firmware today, so i didnt flashed CM13 Firmware.
why didnt unlock officialy ?
*sorry my english is not really good*
ozan6661 said:
did u know how to remove emmc_appsboot or replace that ? is the recovery rom will replace the TWRP if flash the rom recovery ?
yup is better to flash miui mm first and unlocked bootloader, CM13 is to old and didnt get update firmware today, so i didnt flashed CM13 Firmware.
why didnt unlock officialy ?
*sorry my english is not really good*
Click to expand...
Click to collapse
For emmc .. there are guides
https://forum.xda-developers.com/re...nlock-twrp-t3494833/post69484805#post69484805
https://forum.xda-developers.com/redmi-note-3/help/confused-how-to-root-rn3-india-sd-650-t3512484
I think recovery rom will update both bootloader and recovery, if those files are not removed
Ok so I want to flash Miui PRO but I'm on a treble twrp.
How can I go back ? Just flash normal twrp and go from there ?
Robert- said:
Ok so I want to flash Miui PRO but I'm on a treble twrp.
How can I go back ? Just flash normal twrp and go from there ?
Click to expand...
Click to collapse
If you are using akabhishek's treble TWRP, it also support standard ROMs, so you shouldn't need to change TWRP. I think you just need to wipe data, etc., and the vendor partition, and then flash your miui ROM. But you might also need to flash lazyflasher after flashing the miui ROM, otherwise, miui may not boot.
I heard that I can't flash Miui based roms using the treble twrp..
I successfully followed a guide to rooting my phone using TWRP, DisableForceEncryption (DFE), and Magisk. I now want to flash the latest (stock) ROM and re-apply DFE.
But there seem to be many versions of DFE available, some with/without version numbers, and some with/without the word "treble". And all are anonymous uploads on file-locker sites... :-/
What does "treble" mean? Does the DFE version number correspond to the Magisk version? I couldn't find a DEF v20 anywhere...
Who produces DFE -- is there an official website/source for the latest version(s)?
Cheers
For the latest MIUI Stock Rom you don't need dfe.
ConradB said:
For the latest MIUI Stock Rom you don't need dfe.
Click to expand...
Click to collapse
Thanks. So, I can just just flash the latest ROM in TWRP, and... it won't overwrite TWRP, or lose root access, or cause any boot/encryption problems...?
Presumably I'd need to re-flash Magisk (after flashing the ROM) to retain root access...?
Will the phone be re-encrypted after updating to the latest stock ROM?
esuhl said:
Thanks. So, I can just just flash the latest ROM in TWRP, and... it won't overwrite TWRP, or lose root access, or cause any boot/encryption problems...?
Presumably I'd need to re-flash Magisk (after flashing the ROM) to retain root access...?
Will the phone be re-encrypted after updating to the latest stock ROM?
Click to expand...
Click to collapse
Which version is at the moment installed?
IF by latest stockrom you mean miui 10.3.8 then when i flashed the vendor firmware and didnt flash dfe, i was locked out and I lost all the data!
In Miui Roms firmware and vendor are always integrated. There is IMHO no reason to flash only the vendor.
ConradB said:
Which version is at the moment installed?
Click to expand...
Click to collapse
I have MIUI 10.3.7.0 and want to upgrade to MIUI 10.3.8.0. The file I have downloaded is miui_POCOF1Global_V10.3.8.0.PEJMIXM_b5d72aa3ba_9.0.zip.
YasuHamed said:
IF by latest stockrom you mean miui 10.3.8 then when i flashed the vendor firmware and didnt flash dfe, i was locked out and I lost all the data!
Click to expand...
Click to collapse
Yes -- all the guides I've read say that, having installed a custom recovery to root the device, all subsequent ROM updates need to have DFE (or some similar software) applied in order to prevent a boot-loop. This article gives a lot of information, although most of it goes over my head.
https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/
ConradB said:
In Miui Roms firmware and vendor are always integrated. There is IMHO no reason to flash only the vendor.
Click to expand...
Click to collapse
What do you mean by "flashing the vendor"...?
esuhl said:
I have MIUI 10.3.7.0 and want to upgrade to MIUI 10.3.8.0. The file I have downloaded is miui_POCOF1Global_V10.3.8.0.PEJMIXM_b5d72aa3ba_9.0.zip.
Yes -- all the guides I've read say that, having installed a custom recovery to root the device, all subsequent ROM updates need to have DFE (or some similar software) applied in order to prevent a boot-loop. This article gives a lot of information, although most of it goes over my head.
https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/
What do you mean by "flashing the vendor"...?
Click to expand...
Click to collapse
First backup your data
Flash 10.3.8.0 dirty in twrp
wipe cache, dalvik cache in twrp
reboot the device (not rooted)
reboot into twrp and flash magisk 19.3 (i don´t know if the newer Versions will work with MIUI Rom)
reboot into system
thats it
the other guy flashed the vendor partition only, without a reason in miui and ran into encryption.
Here is a very good site "Globe Rom" https://mi-globe.com/miui-firmware-rom-builder-features/65/
Click on MIUI 9.6.27 and Change to MIUI 10.3.8.0 then create your own rom with including Magisk and other nice tools.
You can flash the Globe Rom according to the same instructions as above and Magisk is after the first reeboot
immediately active.
ConradB said:
First backup your data
Flash 10.3.8.0 dirty in twrp
wipe cache, dalvik cache in twrp
reboot the device (not rooted)
reboot into twrp and flash magisk 19.3 (i don´t know if the newer Versions will work with MIUI Rom)
reboot into system
thats it
Click to expand...
Click to collapse
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
esuhl said:
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
Click to expand...
Click to collapse
Just it of curiosity what does it say about encryption under Settings -> Security?
Sent from my POCO F1 using XDA Labs
esuhl said:
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
Click to expand...
Click to collapse
If you flash Miui-Roms than no dfe needed.
If you flash a custom rom you should flash dfe.
guhvanoh said:
Just it of curiosity what does it say about encryption under Settings -> Security?
Click to expand...
Click to collapse
Settings -> "Security status" just shows:
Find device -- Off
Security update -- 2019-09-01
Google Play Protect > (Looks fine / No harmful apps found)
"Additional settings" -> Privacy -> "Encrypted & credentials" shows as "Encrypted".
However, the sub-option "Encrypt device using lock screen password" is turned off.
So just remember that if you want to move to another custom ROM you're going to have to format data. You're system is encrypted.
Sent from my POCO F1 using XDA Labs
i am using this
Disable force Encryption treble + Magisk20.2.zip (JAN 2020)
YasuHamed said:
i am using this
Disable force Encryption treble + Magisk20.2.zip (JAN 2020)
Click to expand...
Click to collapse
I only found DFE uploaded by someone. How can I get latest version? Isn't here any thread of it?
Hello, I'm trying to install a GSI ROM on my Exynos S21 SM-G991N, since there weren't any custom ROMs for it. Is it possible to install a GSI ROM to S21? and how can I install one?
Hi, yes I was able to installs various GSIs successfully by installing TWRP and flashing the GSI with this guide from this thread:
How to make GSI Flasher for Samsung Galaxy A51 Super Partition Image
How to convert a gsi image so that it can be installed on a dynamic partition or super image partition. It may be work for other Android devices. This tool will help you to install gsi image on Dynamic Partition or Super Image Partition...
forum.xda-developers.com
Thanks!
Vailskier said:
Hi, yes I was able to installs various GSIs successfully by installing TWRP and flashing the GSI with this guide from this thread:
How to make GSI Flasher for Samsung Galaxy A51 Super Partition Image
How to convert a gsi image so that it can be installed on a dynamic partition or super image partition. It may be work for other Android devices. This tool will help you to install gsi image on Dynamic Partition or Super Image Partition...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried it and I successfully installed a ROM, but I'm stuck in a bootloop. Can I know which GSI did you use?
hayang1027 said:
I tried it and I successfully installed a ROM, but I'm stuck in a bootloop. Can I know which GSI did you use?
Click to expand...
Click to collapse
I used the official Havoc GSI (the unofficial somehow didn't work), but I was also able to install the Linage GSI and PHH GSI. I think you have to pick the A/B variant and for me only the NON-vndklite version worked. I also usually restore a stock backup first (without recovery to keep TWRP), then I format data and after that install the GSI (without magisk).
I hope this helps
Vailskier said:
I used the official Havoc GSI (the unofficial somehow didn't work), but I was also able to install the Linage GSI and PHH GSI. I think you have to pick the A/B variant and for me only the NON-vndklite version worked. I also usually restore a stock backup first (without recovery to keep TWRP), then I format data and after that install the GSI (without magisk).
I hope this helps
Click to expand...
Click to collapse
I used the Official Havoc-OS 4.1 A/B, but I couldn't boot with it. Maybe it is different depending on the model?
I have experienced this sometimes as well, key for me was to restore the super partition to stock, format data and then flash the gsi with the zip mentioned in the comment above. I have the exynos variant.
Vailskier said:
I have experienced this sometimes as well, key for me was to restore the super partition to stock, format data and then flash the gsi with the zip mentioned in the comment above. I have the exynos variant.
Click to expand...
Click to collapse
I finally installed it! Thanks for helping!
(deleted)
Vailskier said:
I have experienced this sometimes as well, key for me was to restore the super partition to stock, format data and then flash the gsi with the zip mentioned in the comment above. I have the exynos variant.
Click to expand...
Click to collapse
I cannot enroll fingerprint because on-screen fingerprint sensor is not working. Also, I can't use 5G or LTE (only H+)
Is there a way to make any of them work?
Fingerprint sadly does not work for me either. I was able to switch to LTE in the mobile data settings. I hope the GSIs will soon support fingerprint for S21
Vailskier said:
Fingerprint sadly does not work for me either. I was able to switch to LTE in the mobile data settings. I hope the GSIs will soon support fingerprint for S21
Click to expand...
Click to collapse
The LTE unavailable thingie was a problem of all Korean carriers on a VoLTE unsupported ROM. I just ended up customizing One UI