Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here.
Boot with AB only. Seems this was due to some ROM compatibility issue and the FW of Samsung that time. Any Treble based ROM, based on our partition structure works now.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Thanks for your guide. I appreciate your persistence.
We must try relentlessly to get working stuff!
Incredible work testing GSI's, I might flash myself to test out
Snapshots!
Attaching few snapshots for the build and successful flash.
Akhil99 said:
Thanks for your guide. I appreciate your persistence.
We must try relentlessly to get working stuff!
Incredible work testing GSI's, I might flash myself to test out
Click to expand...
Click to collapse
Thanks mate. This guide should work on M30 all variants, ideally.
I will post once PHH gives an update and see how it goes with Dirty Flash or if I need to flash it again. Hopefully dirty flash should work.
vdbhb59 said:
Thanks mate. This guide should work on M30 all variants, ideally.
I will post once PHH gives an update and see how it goes with Dirty Flash or if I need to flash it again. Hopefully dirty flash should work.
Click to expand...
Click to collapse
Which gsi did you flash? I will flash the same for first boot for safety...
And also make a telegram group for samsung m30, so others can post their problems.
nareshfree said:
Which gsi did you flash? I will flash the same for first boot for safety...
And also make a telegram group for samsung m30, so others can post their problems.
Click to expand...
Click to collapse
I flashed the GSI by PHH (phhusson), the FLOSS one.
https://github.com/phhusson/treble_experimentations/releases
There are few groups on TG. I am no longer on TG (left a week/2 ago). I am available here for anything.
System partition or System image?
veekay said:
System partition or System image?
Click to expand...
Click to collapse
Flash as /system image.. By system partition I meant the /system portion of the OS.
Any chance you would be able to take a screenshot of the partition list that is shown after you select the image? I am trying to do this on another Samsung device and am wondering if the issue comes down to the TWRP options shown as I don't have just System - only System Image
veekay said:
Any chance you would be able to take a screenshot of the partition list that is shown after you select the image? I am trying to do this on another Samsung device and am wondering if the issue comes down to the TWRP options shown as I don't have just System - only System Image
Click to expand...
Click to collapse
It is the system image. Dont have Samsung turned on or fully setup to give snap.
There you go.. /system image..
One suggestion. Even with GSI do not try to flash any experimental zips from say Android 9 on Android 10. I just landed on bootloop and had to reflash system Magisk and DM again.
I switched to Havoc. Much more stable and has loads of features..
Couple of Havoc snaps..
vdbhb59 said:
Couple of Havoc snaps..
Click to expand...
Click to collapse
How is your use at hovac ?? Is the lock screen working?
Can you make and receive calls normally?
MiyamuraNEET said:
How is your use at hovac ?? Is the lock screen working?
Can you make and receive calls normally?
Click to expand...
Click to collapse
Nope for both. Calls only on 2G, not even 3G. Audio on speakers is not working. SMS on LTE does not work, but works only on 3G or 2G.
If anything is moved manually to /priv-app or /etc it bootloops on the next reboot.
vdbhb59 said:
Nope for both. Calls only on 2G, not even 3G. Audio on speakers is not working. SMS on LTE does not work, but works only on 3G or 2G.
If anything is moved manually to /priv-app or /etc it bootloops on the next reboot.
Click to expand...
Click to collapse
This is a matter of time soon customs will appear!
MiyamuraNEET said:
This is a matter of time soon customs will appear!
Click to expand...
Click to collapse
True. Just waiting for it. Will see if I can get to help Akhil, Sahil and Aditya.
Flashing the GAPPS build works only until one reboot after which the phone goes into boot loop. also, VOLTE does not work.
thvardhan said:
Flashing the GAPPS build works only until one reboot after which the phone goes into boot loop. also, VOLTE does not work.
Click to expand...
Click to collapse
I do not use gaaps, so not sure, but it does stick around on several reboots as well. Only time it will go to bootloop if you try to manually place any file within "/system/app" and "/system/priv-app" folders. Somehow, it ticks boot and does not start beyond Android logo.
could you please tell which phh to download exactly
vdbhb59 said:
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here. Boot with AB only.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Click to expand...
Click to collapse
It would be very kind of you if yould could tell me exactly which phh to download from github?
---------- Post added at 09:34 AM ---------- Previous post was at 08:46 AM ----------
vdbhb59 said:
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here. Boot with AB only.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Click to expand...
Click to collapse
when I am installing twrp and then formating data and the rebooting to system it is causing bootloop.Please help
Related
OFFICAL TWRP RELEASED, this thread is no longer active. 3-30-2018
https://twrp.me/motorola/motorolamotox4.html
---
UNOFFICIAL BUILDS -- USE AT YOUR OWN RISK AND KNOW HOW TO GET YOURSELF OUT OF TROUBLE IF IT ARISES. I ASSUME NO RESPONSIBILITY FOR YOUR BROKEN THINGS.
UPDATED 01-11-2018
There are now 7.1 based and 8.0 based builds. Obviously, be careful to select the proper download. While I don't think flashing/booting the wrong one would permanently brick the device, let's not find out
For now I will not be attempting to make data decryption work. It is REQUIRED that you unencrypt your device by formatting userdata, so back up your stuff first.
IMPORTANT NOTES: TWRP for OREO is a bit of a pain as it currently requires manually editing your fstab. I have tried to automate this process, but it breaks stuff. So just be aware before you begin that it is a rather time consuming process.
If you make any change to your boot partition after flashing SuperSU, you will need to reflash it or you will get a bootloop.
8.0 OREO TWRP INSTALLATION:
OREO SEEMS VERY FINICKY AND DOES NOT LIKE CHANGES TO ITS FILESYSTEM -- BE PREPARED TO REFLASH STOCK.
0. FLASH OREO FACTORY IMAGE (may work otherwise, but we should be starting from fresh stock here)
1. Download FASTBOOT BOOTABLE TWRP for 8.0/OREO below
2. Download SuperSU 2.82 SR5 below
3. Move SuperSU to external SD or USB OTG
4. From bootloader, fasboot BOOT TWRP
5. Flash SuperSU (note: do not format /data now... not necessary and will cause errors on boot)
6. Reboot system
7. With any root file editor/text editor (Amaze, Total Commander, etc) open /system/vendor/etc/fstab.qcom as a text file for editing.
8. At the end of the /data partition entry, delete "fileencryption=ice" and replace it with "encryptable=footer".
9. Save fstab.qcom (and make sure it is actually saved properly!)
10. Reboot to bootloader and fasboot BOOT TWRP
11. Go to Wipe, hit the FORMAT DATA button, and type "yes" to format /data. This will erase your data, obviously:silly:
12. Reboot system (should now be unencrypted, verify in Settings>Security or by booting TWRP and checking /data with File Manager.
If you later choose to flash TWRP (not the bootable we used here!), you may need to flash SuperSU again to avoid bootloops.
7.1.1 NOUGAT TWRP INSTALLATION:
1. Download current TWRP for 7.1.1 build below
2. Download SuperSU 2.85 SR5 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3. Move SuperSU to your external Micro SD card.
4. Fastboot flash the TWRP image.
5. Reboot to TWRP.
6. FORMAT data (not wipe...use the "FORMAT DATA" button and type "yes". OBVIOUSLY THIS WILL ERASE YOUR DATA)
7. Install SuperSU 2.85 SR5
8. Reboot to system (it WILL bootloop a couple times...don't panic!) and confirm that device is unencrypted by checking that SETTINGS>SECURITY>ENCRYPTION now prompts "encrypt" (don't do it).
DOWNLOADS:
TWRP FOR 7.1.1 (Nougat) DOWNLOAD: https://drive.google.com/open?id=1Et-AQgCNx7WDAwzihlI51euUa2ixKHEP
TWRP FOR 8.0 (Oreo) DOWNLOAD: https://drive.google.com/open?id=1WcVS_3rloF7jxPulj_jKxfsp3zy5pB5N
FASTBOOT BOOTABLE TWRP IMAGE (OREO BASED): https://drive.google.com/open?id=12ClviqtEjtflB63UQ1CZQNKEqkprBO0u **For temporary TWRP boot using "fastboot boot". Do not flash or you will be stuck in recovery!**
DEVICE TREE: https://github.com/mightysween/android_device_motorola_payton (NEEDS TO BE UPDATED WITH OREO BRANCH)
changelog:
BETA4
-reverted to 3.2.0 for current build (release candidate rebased to 3.2.1).
-fixed "format data" button
-finalized fstab for OTG/SD/INTERNAL mounting
-target is now UNENCRYPTED devices only (/data decrypt will not be fixed)
BETA3
-Rebased to TWRP 3.2.1
-USB OTG working
-all partitions mounting correctly
-considered working except for decrypt and MTP/ADB
BETA2
-fixed internal storage mount
BETA1
- updated source to TWRP 3.2.0
ALPHA3
- Fixed USB mounting (adb/mtp still nonfunctional) BROKEN IN BETA1
ALPHA2
- SD Card fixed
ALPHA1
- /system is now properly mounted.
- now plays nice with our working root method.
- ramdisk is patched to prevent first boot encryption once /data is decrypted (now requires flashable ZIP)
NOT WORKING:
adb/mtp/sideload
/data decryption (abandoned -- /data access requires unencryption)
CREDITS: @kraatus90 for kernel fix, @Chainfire for SuperSU, @jcadduono for no-verity-opt-encrypt scripts.
---
Thanks so much for all your work!
hi,
you said this is really unstable and could brick the device easily. however, you seem to be testing and experimenting with your device a lot, so i'd like to ask if you have any particual unbrick method that you use when something goes wrong.. like, a via fastboot flashable image or something simmilar...?
thanks for your work!
Thanks for you work. If you have any unbrick methods pls tell.appreciated your work ?
I am not going to provide step by step "unbrick" methods, because until the partitioning is properly set up, TWRP has potential access to things that can not be fixed.
Again, this is still highly experimental.
All that said, my entire process to protect any device remains the same: Have a backup for every partition you will be testing, make as few changes as possible at a time, test boot images before flashing (fastboot boot), and test restore methods frequently (flashing back to stock or backups), and don't do anything unless you are highly certain of the outcome.
By those standards, there is nothing to gain by installing TWRP right now, as its basic function (install/backup/restore) is not set up yet.
Found the BoardConfig flag to enable FBE (TW_INCLUDE_CRYPTO_FBE := true) but do not have the lib it is dependent on (libe4crypt) and I don't see it anywhere yet...
For reference (not sure this is most current, but it demonstrates the process)
https://github.com/nijel8/TWRP/commit/bd7492de28963b7e74e8e5d3f17ec9a5a287d9c3
I have confirmed that FBE support is present in the source, dependent on this missing module... so need to figure out where/how to enable it.
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Obvious workaround is to not be encrypted to begin with -- but that isn't a "solution".
mightysween said:
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Click to expand...
Click to collapse
This appears to be the case, unfortunately. Seems that the TWRP FBE support was built specifically for the Google implementation of FBE which was merged into kernel sources for Nexus and Pixel. Not even using the qseecomd I assumed it was... will remove on next build.
Info on FBE:
https://source.android.com/security/encryption/file-based
Will be testing options to disable forced encryption, and if necessary dm-verity...
Anyone who wants to dig through kernel for related flags and props, it would be greatly appreciated!
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Making good progress this morning.
Seem to have a build with properly decrypted /system, and working SD Card. I also have patched the boot.img to disable forced encryption on the first boot. But now, I can not find a safe way to fully format (not "wipe") the /data partition. As mentioned in the previous post, the "FORMAT DATA" button is missing. The fastboot command "fastboot format userdata" returns an error that it does not support RAW format.
Need to figure out why this is happening... and once I do, I believe I can reformat /data without encryption and then will have an almost fully working TWRP build. Obviously, the ideal solution would be to have TWRP work out of the gate with an encrypted /data, but until then this is going to be our best option.
Will post an updated test build in the OP soon.... needs further testing before I would recommend non-expert users to try it.
Getting very close now!
UPDATE: ADDED NEW BUILD TO OP
---
Also, just occurred to me that the ramdisk will need to be patched every time, so now that I have SD card support will be testing some of the existing flashable ZIPs out there that are designed specificially to prevent first-boot encryption and/or disable dm-verity.
---
mightysween said:
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Click to expand...
Click to collapse
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
mightysween said:
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
Click to expand...
Click to collapse
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
johnjingle said:
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
Click to expand...
Click to collapse
I have 3.1.1-0 (same version I am building here) on several other devices, and the button is there. It has to be triggered by something during compile, but I can't figure it out. Driving me nuts
Looking through TWRP source, and can find actions for every other button (wipe, backup, restore, install, etc) but not for format. Hmm.
I posted over on an old but semi-active TWRP flags thread, maybe someone will have some insight.
Wondering if I make a stock boot image without the encryption tag in fstab, and then wipe data and reboot... then flash my image. That may make it so the data partition is never encrypted in the first place and allow TWRP to work.
But that is an ugly, non-user friendly fix. Why can't we just format /data?
---
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
No crypto support was compiled into this build.
Click to expand...
Click to collapse
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
mightysween said:
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
Click to expand...
Click to collapse
Thanks for doing all of this! I wish I had the time and knowledge to help.
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
mightysween said:
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
Click to expand...
Click to collapse
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
vivek638 said:
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
Click to expand...
Click to collapse
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
mightysween said:
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
Click to expand...
Click to collapse
Keep searching. wish i could have helped but dont know anything about compiling n all..
I'm not much of a programmer, but I can look through the files. Is there anything in particular we're searching for?
**** Disclaimer: I'm not responsible if you destroy your device. Learn at your own risk!!! ****
Alright, So I am a bit Moderately skilled to Custom Development. I do not know a lot of in-depth either.
However, I do know enough to help other new beginners out.
As I continue to learn more info and details, I will update this post frequently.
Completed guide, I'm saving and typing as not to lose progress. Last Updated- 01/03/2021
Please do note, CROSS-VERIFY if the info here is correct before following it.
What is a Custom ROM?
Simply put, it is a new Operating System [OS].
People find their stock (the one you got with your phone) to be boring, or they dislike it or want more customization and optimization, lesser bloatware (useless unwanted system apps).
Thus some Developers made their own ROM (aka OS). Then others made it compatible with our phone. Sometimes this works perfectly, most of the time it doesn't. Thus Asking people how the ROM is, is always good to ask.
STABLE means almost no errors, UNSTABLE means a few/lots of errors.
OFFICIAL means the Developer in charge will keep updating it and has been granted the task officially. EOL means End Of Life, aka Developer, won't work on it anymore.
FOD means finger on display icon, FP means fingerprint sensor, SOT means screen on time or how long your battery will last.BB means Battery backup, or how long the battery will last.
Click to expand...
Click to collapse
How To Get a Custom ROM?
So, to flash (insert) a new Custom ROM, we first need to unlock the Bootloader. The Bootloader is what allows us to wipe (remove/erase) our data, and current OS and flash a different one.
Then we flash a Recovery. (A software that makes flashing and wiping and other stuff easy)
Then flash the ROM, Then (if needed) vendor+firmware, gapps, magisk.
So in k20 pro/Mi 9t pro, there are 5 vendors. Indians use Indian Vendor, Chinese users use Chinese Vendor, similarly for EEA, Russian, and Global.
In this Vendor zip file, nowadays, the firmware is included in them, so it isn't required to flash it separately.
If you are coming from miui 11 and want to flash custom ROM you don't need to flash the vendor.
If you are coming from miui 10 to custom ROM Android 10, you need to flash the miui 11 vendor along with the ROM.
Click to expand...
Click to collapse
How To Unlock Bootloader?
So, you should first update your software to the latest miui OS [current: MIUI 11].
Go to Settings > About Phone > tap on MIUI Version 7 times -> you unlock developer settings
Go to Settings > Additional Settings > Developer Options > enable (switch on) USB Debugging > OEM Unlocking > click on MI Unlock status > link account and device.
To link the account, you must first have a Xiaomi MI account. You can make this in settings, or head to https://account.xiaomi.com
Wait 7-15 days
Once 7-15 days have passed,
USING WINDOWS PC
BACKUP ALL FILES, CONTACTS, WHATSAPP, ANY APP settings (if any), AND SYNC/LINK accounts to cloud => YOU WILL LOSE EVERYTHING NOW
Now download the Mi Unlock tool onto your PC https://xiaomitools.com/mi-unlock-tool-en/
IN A SEPERATE FOLDER
Then download Platform Tools from attachments below.
Then download TWRP (team win recovery project) from https://dl.twrp.me/raphael/
Then download Orange Fox Recovery (OFRP) from https://files.orangefox.tech/OrangeFox-Stable/raphael/ and download the latest file. [Currently: OrangeFox-R-10.1_3-Stable-raphael.zip]
Then download Disable force encrypt zip file from attachments below
Then download adb drivers from https://www.xda-developers.com/what-is-adb/ version 1.4.3 onto your PC and run the application. (Follow from How do I install ADB?) (Or you can skip that and just get the file from attachments below and extract it to C drive as a separate folder directly)
Then download the ROM (links are given below)
Then download gapps (optional). from https://opengapps.org/ and select ARMx64 and PICO then the download button.
Then download Magisk (optional). from https://github.com/topjohnwu/Magisk/releases download the Latest Magisk-vXX.xx.zip file there.[Currently: Magisk-v20.4.zip]
Download the latest vendor file from the below links. (make sure it's the proper file for your device's variant.)
Vendor and firmware are both combined and included in the same zip file.
Global, EEA (Europe), China, Russia Q Vendor: https://xiaomifirmwareupdater.com/archive/vendor/raphael/
Indian Q Vendor: https://xiaomifirmwareupdater.com/archive/vendor/raphaelin/
Check my third comment to learn how to recognize which device variant is yours, and what vendor to download and flash.
NOW! GET READY!
Now, connect your device.
Use your cable included in the box (the charging wire) and connect it to your phone and PC.
Go to 'adb' folder in your C-drive, (on that address bar thing where it shows) This PC >OS(C> adb click on it and type cmd . This will open a Command prompt to that folder.
Type adb devices and on your phone tap on the authorize button that pops up when unlocked. Now type adb devices again.
you will get
Code:
List of devices attached
365278234e device
Now, Switch off your phone.
Open the MI Unlock Tool on your PC, run the file that is an application. Read through everything, click on unlock, confirm.
Wait till the phone fully reboots itself. DON'T TOUCH IT NOW!
Congrats, the phone is now unlocked, and you have stock MIUI 11.
Now skip everything in the setup (we wanna add a custom ROM now remember, why stop here?)
again do the adb devices. You should get the same results.
Now, on your PC
Extract the Platform Tools zip file so you get its folder.
Move the TWRP.img file into the folder.
Open that folder. on that address bar, type cmd to get a new command prompt window.
There type dir *img to confirm the file is found properly.
Now switch off your phone again.
press and hold the power button + volume down button.
you will soon enter fastboot mode.
Now, on the new command prompt where you typed dir *img
type fastboot devices and you will get an output like
Code:
342524356 fastboot
Then type fastboot flash recovery twrp(press the TAB key to autofill)
Now it's done! you have TWRP, but it isn't permanent.
Now, TWRP usage.
Now press and hold power key + volume up to enter TWRP.
Once in TWRP, unlock it.
Go to MOUNT and check if MTP is enabled..... click on "enable MTP" button.
Now copy the ofox.zip (orange fox recovery zip file) to your phone from your PC via your PC.
Now go to INSTALL tap the ofox.zip file, then flash it!
YAY now, orangefox is your Permanent Recovery.
Now go to MENU > Manage Partitions > select only data > format data
Now go to MENU > Reboot > Recovery
Now, to Flash your first Custom Rom.
Now from your PC copy the ROM zip file, Disable decrypt zip file, gapps ( if specified, optional), magisk ( if you want to root, optional)
Now go to MENU > Reboot > Recovery
Now go to FILES > tap on the ROM zip > add to queue > tap disable decrypt zip file > add to queue > (add gapps , magisk if needed) > flash
Now wait for a while (approx 10mins) till ROM boots up and complete the setup process.
Congrats you have your new ROM.
Now just let google download all your apps
Before you change settings like dark mode or use custom launchers etc...
Reboot once for the heck of it. Then Customize the way you like.
**** Backup Your Persist and save it on your PC always. ****
You can backup persist by having root then downloading a terminal app from Playstore. then typing these two commands
Code:
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Click to expand...
Click to collapse
How To Change My ROM? I wanna Try them all!
Now is the easy part, since all the setup is done!
First remove all passwords, fingerprints, and so forth.
For AOSP ROMs: (MIUI below)
AOSP ROMs will not break your L1
First Download the AOSP ROM you want, given below are some examples. (MIUI below)
Each of these might have instructions, usually saying...
Go to your Recovery, (press and hold Power + Volume Up buttons).
Then go to WIPE > select Dalvik, Cache, System, Data > then wipe them all.
Then go to [Files in OFX] [Install in TWRP] and
Only If you are coming from miui and flashing AOSP, go to orangefox settings > manage partitions > data > format > type yes (you lose everything in internal storage) then
Select the Vendor (if it's needed) (not required if moving between any android 10 ROMs) (Just make sure it's the right Vendor for your device/region) (If the previous AOSP rom uses OSS vendor, then you need to wipe vendor as well and flash the stock before proceeding) and flash it.
Select the ROM (Then > add to queue, else if you only needed ROM, just flash. and set-up! yay!)
DFE (not required if you want to be encrypted, which is not recommended.) (A must if you formatted data via orangefox settings and did that typing 'yes' thing)
Gapps (if it isn't already included in the ROM, ask first).
and Magisk (optional if you want root).
For MIUI ROMs: (AOSP above)
First Download the MIUI based ROM you want ( stock, EU, MortalOS, etc), given below are some examples.
Each of these might have instructions, usually saying...
Go to your Recovery, (press and hold Power + Volume Up buttons).
Select the Vendor (if it's needed) (not required if it's currently the proper Vendor, cause EU ROMs to use a custom vendor that works on all devices) (Just make sure it's the right Vendor for your device/region) and flash it.
Then go to WIPE > select Dalvik, Cache, System, Data, Vendor > then wipe them all. (make sure you are on your device's vendor region before wiping it.)
Then go to [Files in OFX] [Install in TWRP] and
Only If you are coming from AOSP and flashing MIUI, go to orangefox settings > manage partitions > data > format > type yes (you lose everything in internal storage) then
Select the ROM (Then > add to queue, else if you only needed ROM, just flash. and set-up! yay!)
DFE (A must if you formatted data via orangefox settings and did that typing 'yes' thing)
Magisk (optional if you want root).
Some Android ROMs
With ROMs being built, changed, and modified on a daily/weekly basis. Some changing to Mi9 fod or LOS fod or using Stock or OSS vendors. Sometimes maintainers shifting or 2 devs building the same rom. The below list is not being maintained anymore. We currently have 50 ROMs. YAY Raphael!
Update: I'm removing most of the ROMs listed here and only adding my personal favorite ROMs
AOSP ROMs
DerpfestOS (two variants, I like em both) - by @Raaj52 -> https://forum.xda-developers.com/k20-pro/development/rom-derpfest-t4132757
SuperiorOS by @HSgod -> https://forum.xda-developers.com/k20-pro/development/rom-superioros-t4130867
MortalOS (miui12) by @Raaj52 -> https://forum.xda-developers.com/k20-pro/development/rom-havoc-os-3-3-t4063081
LineageOS, Pixel Experience, PE+, PE+ Fan Edition, ParanoidOS, MookeOS, TitaniumOS, MSM Xtended, OxygenOS, OmniOS, TreskMod, AOSIP, ColtOS, ArrowOS, BootleggersOS, ExtendedUI (exui), CRdroidOS, RevengeOS, IonOS, AICP, BlissOS, CorvusOS, DerpfestOS, HavocOS, NitrogenOS, HentaiOS, Corvus, TitianiumOS, CygnusOS, CesiumOS, Project 404, DescendantOS, SyberiaOS, EvolutionX, AOSPA, POSP, LegionOS, AncientOS, RebellionOS, SuperiorOS, ShapeshiftOS, WrathOS, ZenX, AIM OS, ConquerOS, PixelDustOS, CygnusOS, StagOS, Ressurection Remix OS, Quartz, PixysOS, PePlusUI, MalluOS, StatixOS, GrapheneOS, ShapeshiftOS, MortalOS, SuperiorOS, AwakenOS, DotOS, Lemon Branch, FluidOS, LiquidOS + more!
MIUI ROMs
EU ROMs, MortalOS, RevolutionOS, Miroom, MMX, Masik + 5 other ROMs
Kernels
Perf (miui kernel), F1xy, Immensity, Englezos, Marisa, R4v3n, Void, NotKernel, Smurf, Candy, Supermad, Antarctica, Evira
MY SUPPORT
I got help from multiple telegram guys for this.
Shoutout to @ishtiak02, @ComicoX, @logosA, Bruce Wayne, SSS, @Noobmaster69 @Lacentix @Raaj52 @nevoness @joshuah1971 and a lot of others teaching me about ROMs and answering my numerous questions.
I am using the Indian variant K20 pro (aka Raphaelin)
You can always ask in the Our Telegram Group, or me, or in the comments. (not allowed to link telegram group I think)
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Reverting Back to PIE, moving from Android 10+ to Android 9 -Just don't- (RIN users)
Right, so Anti-Rollback protection is not implemented for k20 pro or mi 9tp. YOU CAN REVERT IF YOU WANT TO.
This is confirmed by users who have reverted, and by Xiaomi.eu website. Which I trust regarding this.
We've done experiments regarding this and have concluded this applies to raphaelin users (Indian variant devices) only. Unsure why, and how it is not affecting the mi9tp variant. (no confirmation with RCN)
However,
When moving from an Android 10 vendor to an Android 9 vendor, your SENSORS will break!
You can fix this simply by flashing your persist img (Hope you took that backup).
You can also fix your sensors by flashing someone else's persist img. BUT YOU WILL LOSE L1 FOREVER.
You can get L1 back by replacing the motherboard which can be done via your warranty at a service center, or by playing a hefty sum of money. nearly half the cost of the phone. NO OTHER WAY. Also, they open your phone, so it isn't SPLASHPROOF as much anymore.
You can also fix sensors by simply updating back to android 10 via the OTA method, which is found in your settings remember. (Unsure if this will retain your L1 though)
BOTTOM LINE, IF YOU ARE ON ANDROID 10, don't go to ANDROID 9 back.
Stuck at Fastboot Fix
Best Recovery
So regarding Recoveries. Choose the one you like the most.
I prefer the latest OrangeFox recovery cause it looks better, has a better UI, better settings, more functionality, and so forth. https://files.orangefox.tech/OrangeFox-Stable/raphael/
You can also choose TWRP if you like. Completely your choice. You can get that from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363 and choose the most recent one, and follow the instructions given there.
If you are just comfortable with TWRP. Always use Mauronofrio's, which is recognized as OFFICIAL.
To flash either recovery, just download the zip file, and simply flash it directly in your recovery like you do for a rom (no need to wipe anything) and it will auto-reboot into your desired recovery.
All credits to those who made the recoveries and those people who helped them.
Stuck in Stock Recovery when Rebooting Fix
Full credits to @ SivSomRao (telegram handle, since no XDA)
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, I was scared half out of my mind. A guy named Shivsom helped me.
Basically what he made me do was
Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder in my WindowsOS C drive.
Now, on your PC. Copy your TWRP.img file, or your OrangeFox.img (I prefer the TWRP.img file by Mauronofrio.)
Open the Command prompt in that folder
You can do this by clicking on the address bar of File Explorer and typing > cmd > then Enter
There type dir *img to confirm the file is found properly.
Now switch off your phone again.
Press and hold the power button + volume down button.
you will soon enter fastboot mode.
Now, on the new command prompt where you typed dir *img
type fastboot devices and you will get an output like
Code:
3e2f2d356 fastboot
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery
Now, TWRP usage.
Now press and hold the power key + volume up to enter TWRP.
Once in TWRP, unlock it.
Go to MOUNT and check if MTP is enabled..... click on the "enable MTP" button.
Now copy the ofox.zip (orange fox recovery zip file) to your phone from your PC via your PC.
Now go to INSTALL tap the ofox.zip file, then flash it!
YAY now, orangefox is your Permanent Recovery.
Now go to MENU > Manage Partitions > select only data > format data > type 'yes' (This will delete everything in your Internal Storage so Caution)
Then quickly flash the latest miui vendor,
Now go to MENU > Reboot > Recovery
I was OverJoyed when this worked.
Now you can flash your Favourite ROM (normal clean flash, tutorial is given above), and then boot the ROM.
This was a nasty disaster. Glad I got through it.
Right, so I tried LR-twrp (it's in Chinese, but I can change the language to English). PitchBlack and PitchBlack-old Both broke my phone to get stuck in fastboot mode no matter what I did.
HENCE I conclude that for all Xiaomi devices, OrangeFox [OFX] is the best recovery. TWRP is suited for Samsung.
ERROR 7 fix and how to modify UpdaterScript
WHAT IS ERROR 7? :
Error 7 is an error that says the ROM you are flashing is not meant for your device.
It does so by comparing the phone's codenames.....
k20p and mi9tp have two codenames, one is RAPHAEL and the other is RAPHAELIN (the Indian variant)
Flashing the Raphael/raphaelin ROM on either device won't cause any problems at all.
feel free to flash it.
Latest orangefox 10.8 works with Raphael (global and Chinese variant) and orangefox 10.6 works with Rapahelin (Indian variant).
Alternatively, It could also be caused because you are required to flash the latest vendor, which you may have not.
So please read the one-line error message that appears above the ERROR 7 red message for more details
SOLUTION to ERROR 7:
I'd recommend flashing the orangefox 10.6 recovery as it's a lot simpler.
However if this doesn't work you can try updating script.
Right, so instead of using a different recovery, you choose to update the updater-script.
Copy the zip folder of the ROM to your PC
You can use 7zip software on your Windows PC. Download this software if you don't have it.
Double click the zip (don't extract it!!!) to open the zip.
Navigate to meta_info> com > Google > Android > you'll find update_script
Find the updater-script. Right-click on it, and choose the "EDIT" option. And edit the word Raphael to raphaelin (if you have the Indian variant of the phone)
Save and exit.
Click to expand...
Click to collapse
Creating Backups
Creating backups is always the safest thing to do, and you can do so via your recovery (OrangeFox or TWRP)
First, make sure you have everything working, nothing is broken in the ROM.
Second, go to your recovery and tap on Backup. Then Click on Create Backup, rename the file if you want to.
Third, Select all the partitions, cause why not, and let it finish creating the Backup.
Finally copy the backup file created to your PC in a safe location, and later when and 'if' you mess up, you can copy the backup file back and restore it.
You can restore by first wiping everything and formatting. (For safety) Then using the same recovery you used to create the backup, Flash the backup file. DO NO FLASH SOMEONE ELSE'S BACKUP FILES!!!!!! ONLY YOURS!!!!!!
How to Decrypt Your Phone.
So encryption is the safest thing for devices, It uses a secret code/key that only your phone knows to read data and information. However, when in Recovery, we Custom ROM enthusiasts like to have our data DECRYPTED. Now, This is because we can access our files from the recovery, flash ROMs only when decrypted, and transfer files. (If we have MTP enabled in recovery)
Somehow you've found yourself encrypted, which means all the files in your recovery are showing random letters + alphabets. and you cant transfer files to your phone via recovery anymore!
To solve this, or decrypt yourself. You will have to format your data partition (this will delete everything in your internal storage, so I hope you have a backup of your photos, vids, gifs, contacts, and so forth)
Just a bit of quick advice, If you can boot into your OS, go there, and transfer all your internal storage to your PC or laptop before formatting to avoid losing your stuff.
If you can't boot into your ROM, then you'll have to lose all your data in internal storage. No known method is known YET to help without losing the files.
Now the SOLUTION: Go to Orangefox settings > manage partitions > select data > tap on format > type 'YES' > swipe to confirm > you lose all your internal storage data contents, and you are now successfully decrypted.
OR if you are using TWRP. Go to WIPE > (right side button) FORMAT DATA > type 'YES' > you lose all your internal storage data contents, and you are now successfully decrypted.
You can now transfer files to your phone properly.
To stay decrypted and not get encrypted again, flash the DFE (Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip) from attachments below (or from the file attachment called disable_force_encrypt.zip above in the first post/comment) and then boot into your ROM, or if you are flashing a new custom ROM, follow the tutorial above(first post/comment)
If you want to stay encrypted. (I advise against this) Just don't flash the DFE file.
The newer latest updated dfe file I have attached in this comment is from https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 and all credits for the file go to him. The dfe file in the first comment/post is different and also works.
How to Recognize Which Device You Have And What Vendor Should You Use?
Global, EEA, China, Indian, Russian variant?
All credits for this list go to @joshuah1971 aka Superuser1958 on telegram.
Box Packaging
k20 pro-China: purple+black box with Chinese writing.
k20 pro-India: angled photo of the phone on top+ white box (NO NFC capability. hardware, not software), identifier: raphaelin.
mi 9t pro-Global: black box+ picture of the device on top, English text on side sticker. (model: M1903F11G)
mi 9t pro-RU: same as global but with Russian text+ orange sticker on the phone.
mi 9t pro-EEA: white box.
Software Differences
miui Global: version number will include "QFKMIXM", google dialer, and messages.
miui EEA: version number will include "QFKEUXM", google dialer, and messages.
miui China: version number will include "QFKCNXM", miui dialer, and messages.
miui India: version number will include "QFKINXM", miui dialer, and messages.
miui Russia: version number will include "QFKRUXM", miui dialer, and messages.
So check which device variant it is, and use the appropriate Vendor when flashing. (Go to ROM's Settings-> About phone-> MIUI Version [code in the brackets])
Vendor Links
So regarding Vendors. Choose the one your device needs.
Namely, The Indian Variant is called Raphaelin. So get your vendor from https://xiaomifirmwareupdater.com/vendor/raphaelin/
The Global, Europe, China, and Russian Vendors are gotten from https://xiaomifirmwareupdater.com/vendor/raphael/
What is OSS Vendor? How to switch to the F2FS file system on OSS ROMs only?
What is OSS Vendor?
So our device has 5 variants.
Xiaomi firmware website has all 5 official (firmware+vendor) zip files.
"Always flash your variants vendor."
"Xiaomi never showed us what's in them. Aka closed source"
But this is so confusing for some people. Idky.
Therefore, some devs decided to make a universal vendor that will work on all variants. Since they are making it. They can optimize it and also always know what's in it.
This universal vendor is called an OSS vendor. (Open Source Software) (It's not yet perfect though)
Some custom ROMs don't include vendor (cause OSS isn't perfect yet)
Some custom ROMs include OSS vendor (so we can observe how good it is in daily use)
It's always good to know if the rom is using OSS or if we have to flash the official.
Currently. Since OSS isn't perfect yet. If the rom doesn't include vendor (or it's a custom miui) do not flash/use OSS with it.
How to switch to F2FS File system?
• Go to the rightmost tab on orange fox recovery > manage partitions > data > change FS > tap on f2fs > change FS
• Now reboot recovery
• Now reboot recovery again
• You are now f2fs.
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Info about Persist and why it is IMPORTANT to make a Backup
To make a Backup: Go to orangefox/TWRP recovery and select the Backup option and choose the persist.img option and back that up. Make a copy on your PC for added protection.
Persist.img is "persist" which contains data that shouldn't be changed after the device shipped, for example, calibration data of chips(wifi, bt, camera, etc.), certificates, and other security-related files. Persist is having keys to decrypt several pieces of stuff, it is device-specific and you shouldn't flash persist of others, very very bad idea.
How you are losing L1? By flashing someone else persist.img file, and if you have done that you already lost it. You cannot recover it. You can still restore your own old persist back up, and if you are lucky you will get L1 back. Never play with the persist partition it has important information specific to your device.
In case you've just lost it, and you've realized it immediately (cause sensors, pop-up, L1 are broken), & haven't done anything to modify yet. Then you can try to restore the context. Try doing this in a terminal emulator like termux (case-sensitive) Termux is an app on play store (requires root):
Code:
su
restorecon -F -R /mnt/vendor/persist/
There is also this really nice guide by William Feng that explains the same but a bit better here:
Backup and restore persist on K20 Pro and 9T Pro
Pop-up Camera Stuck Open Fix
Does not work on MIUI based ROMs. The App must be used on AOSP ROMs
Due to some reason you did, your phone's pop-up camera is stuck open. Too scared to push it down, or it isn't going down.
Download the apk k20pro_motor.apk from attachments below > Install it > when you open it, the dialog box will inform you to set the current state of the camera. Then click on the button to get the pop-up camera down.
Enjoy. Complete Credits to @acervenky from https://forum.xda-developers.com/k20-pro/themes/app-xiaomi-motor-control-k20-pro-t3984181
Xiaomi.eu and other Custom MIUI ROMs
Right, so Xiaomi.eu is a forum like XDA where devs make miui like ROMs without the Mi ads and tracking and are more optimized.
The website is: https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Under there, you go to MIUI 11 ROMs > stable ROMs > download the proper ROM zip file.
The direct download link is https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv11/ or you can use: https://androidfilehost.com/?w=files&flid=300229
Now download xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip CAUTION, the word PRO has to be there. we have k20p not k20.
This works for only Raphael users, not Indian raphaelin users. (For raphaelin users use Orangefox 10.6 it will work then.)
The difference between Stable and beta is that in beta, newer features, security is implemented and tested, this has bugs, once those features are stable, it becomes a STABLE rom, then the next batch of features are added to the beta. Get STABLE though, it's better, the beta has weekly 2GB updates.
Now flashing is easy, Follow the rules in the first post/comment on how to flash a miui ROM.
Equally, you may also choose to use MortalOS which is a debloated MIUI ROM which can be found here -> https://forum.xda-developers.com/k20-pro/development/memeui-12-rc5-09-05-2020-t4097469
Issues Related to L1, restoring, and china-based miui roms
Thanks to @Raaj52 for conducting experiments to confirm and collect this information.
You must have a global/Indian variant phone which currently has widevine working properly to have a chance at restoring it later. China phones can't get L1 (or at least, I haven't learned a way to do so yet.)
What is Widevine L1 and L3?:
Right, so L1 or widevine L1 is a DRM security made by google after they noticed people use root, etc to steal copyrighted videos and movies in full HD and post them somewhere else for free. (Netflix and Amazon prime video app being affected.)
Losing this, means you get L3, and widevine L3 does not allow you to stream Full HD videos anymore, but you can stream SD low-quality videos. Which is never ideal.[
Now, EU latest stable, MortalOS uses modified china vendor with k20p L1 patch
So how do I save my L1 then? L1 Retention?:
Fortunately @Raaj52 found out that if you take a full Ofox or TWRP backup or everything from EU rom, (making a save on the PC, just in case) before moving to those aforementioned China-based ROMs is good.
When you try flashing miui EU latest stable after losing it by flashing a MIUI custom ROM based on China vendors, your phone gets L1, it shows you have L1 too, however, the apps on your phone DO NOT recognize it, technically the phone recognizes the widevine L1 as broken, and somehow considers it L3.
Here is where the Backup you made comes in handy, Clean flashing the backup completely and perfectly restores your L1. He also states that moving from China-based ROMs to AOSP ROMs like EvoX via clean flash (wiping vendor as well and flashing the proper vendor before flashing the AOSP ROM in the recovery) will also restore L1 (remember to format data partition when moving from miui to AOSP)
Now, It should be noted that cross-flashing vendors is very DANGEROUS, as this may break your Fingerprint Sensor, DTBO and proximity sensors. Therefore you must always flash the proper vendor for your phone (global, Indian, china) don't try flashing a vendor that isn't for your device. Unless if it's a custom MIUI rom as custom MIUI Roms come included with a Vendor. (wipe vendor before flashing custom miui ROM, after flash, don't touch the vendor)
Global vendor and Indian vendor are partially similar, and we have reason to believe that EU stable uses a modified vendor that works for both Raphael and Rapahelin. This is why EU ROMs works on both devices (MI 9t-pro and K20-pro)
Some Things to be Cautious about and to note:
Quoting our messages on telegram here:
The basic is, EU rom comes with vendor file so no need to flash a separate vendor for them. Flashing any vendor over the EU might break something because we don't know really which vendor they are using, assuming stables are global and betas are china.
On the other hand, AOSP comes without any vendor file, so it becomes mandatory to flash a vendor based on your device default vendor.
We flash vendors only when we flash AOSP's. In miui custom ROMs vendor is included.
Exception: If something is broken, clean wipe, flash your vendor, and then (advance wipe everything, including vendor) clean flash miui custom/AOSP.
Practically speaking, if you are moving from your stable own rom to Evox or any AOSP, no need to flash vendor since it is already having the default files but this is double confirm that the vendor is correct and it will not harm anyone. (AOSP to AOSP, not required to wipe vendor, but you can if you want to, I recommend wiping it and flashing your vendor again)
These are separate partitions and it will not override but to be on the safer side most rom devs prefer vendor and then rom.
If you flash an AOSP rom and want to move to a custom/stock miui rom make sure that you are own correct vendor. (Prior to wiping it in advance wipe) If not sure flash your vendor once again, then clean wipe and flash miui based rom.
Click to expand...
Click to collapse
How Get Back To My Stock ROM and/or Lock Bootloader?
To get back to your stock ROM, you have two methods, namely recovery zip ROM flash or fastboot ROM flash.
Get your stock rom from https://xiaomifirmwareupdater.com/archive/miui/raphael/
or if you need the Indian variant, Get your stock rom from https://xiaomifirmwareupdater.com/archive/miui/raphaelin/
Now, AND THIS IS SUPER IMPORTANT. Make sure you double-check and download the proper device's Region, codename, android version, and THE TYPE!!! (there are two types: recovery and fastboot types, choose the one you need)
Now for the recovery method, flash the recovery type .zip file the same way you flash any miui custom ROM. Check guide in first post/comment for method.
Now for the fastboot method, go to your mi-flash tool and enter fastboot on your device, and flash the rom there. (Now, I personally never did this method, so I can't guide the exact steps for this method, sorry)
LOCKING BOOTLOADER: You must first be using the proper stock vendor, stock rom via fastboot, and not have magisk or any MODs running on your phone. If you violate these, you WILL Hard brick your device. It is because of this I VERY STRONGLY advise against locking your bootloader for any reason whatsoever. JUST DON'T!!!
However, you can you the mi-flash tool (safest) or the debloater tool to lock your bootloader if you definitely must do it.
• Download MiFlash tool from MiFlashTool Website . The latest is the top left, marked with a NEW tag.
extract the file, and run the program "XiaoMiFlash.exe"
• Download the stock fastboot miui rom from Fastboot Website and extract the file (if its a .tgz or .tar extract again) you'll end up with a folder with one folder and 11 files (images, flash_all.bat.......misc.txt)
• Now in whatever rom you are on, go to developer settings, enable "OEM Unlocking" and "USB Debugging"
• Now boot into fastboot mode
• Connect your device to your PC
• Now in MiFlash tool, at the bottom, choose Clean all (and dont LOCK IT, I repeat do not choose to lock)
• Then on the top click on the "select" button and navigate to the folder with the 11 files & 1 folder and choose that folder.
• Click on the "Refresh" button and check if your device is shown (indicated by random numbers/letters)
• Now (recheck if its only CLEAN ALL only, and NOT lock or anything else)
• Now flash
• Wait 420s approx, or more, or less.
• It'll finish with an error and the message will say
• "error: Not catch checkpoint (\$fastboot -s . ' lock),flash is not done"
• This is cause it did not lock your bootloader. THIS IS GOOD.
• Now wait 5-10mins while miui 12.5 loads up/boots, it takes a while.
• Now, close MiFlash program, its done, no more needed.
• Now that's done, use miui 12.5 if you want, or go to recovery
• You'll see you have stock recovery now
• So go to fastboot mode, (phone connected to PC)
and flash the ofox recovery.img to get ofox recovery. via the cmd command like usual.
• Then go to recovery ofox.
• Go to wipe > format > type yes > format data to decrypt
• Reboot to recovery
• Now copy your ofox zip file to phone,
• Now flash that file to make OFOX permanent
• Now reboot to recovery again.
Click to expand...
Click to collapse
Latest MIUI-CN builds and miui custom ROMs soft bricking your device? (Mostly Raphaelin users)
Right, so this is a Xiaomi thing, which happens to many Xiaomi-based devices. It was later observed by a member on telegram that this usually happens to devices without NFC. In our case of Raphael - This would be Indian devices or Raphaelin devices.
I personally haven't experienced this, so I can't give a personal experienced-based guide on fixing this. However, another user on telegram @rockyanexpert solved his problem and shared this guide given below with me.
[
System has been destroyed. What I did:
1. Panicked a little
2. Started my lappy
3. MiUnlock Tool was pre-installed v3.xx
4. It took almost 10 minutes to show the login prompt. The connected device in fastboot. It failed to recognize the device. Started MiFlash. It did recognize the device.
5. Downloaded the latest MiUnlock. It too failed to recognize the device.
6. Downloaded XiaoMiTool v2
7. It detected the device fastboot serial correctly
8. Manually selected model Raphael.
9. Started with My device is bricked
10. It detected a locked bootloader. Opened its own version of Unlock Tool. Logged in to binded Mi Account. (My Mi Account n the binded one is the same)
11. Unlocked.
12. Tool went on ahead with waiting for the device to boot in fastboot mode.
13. I removed the device n forced boot in recovery mode. Ofox showed "Updating" n booted in orange ofox screen.
14. Rebooted system
15. Newly flashed Eu 21.2.3 started initial setup.
No data lost.
Click to expand...
Click to collapse
By these same people, they made a guide here: System destroyed issues
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
nice work @Sandeeep Kiran, keep it up.
Just got my 12/512 yesterday but my wait time is 15days (it said 360hours).:fingers-crossed:
Hi, probably today i wil try to flash xiaomi.eu rom but i have some doubt, why you are saying that wipe system is required for flash a custom rom? i have read in several thread that this wipe is not rquired
salva93 said:
Hi, probably today i wil try to flash xiaomi.eu rom but i have some doubt, why you are saying that wipe system is required for flash a custom rom? i have read in several thread that this wipe is not rquired
Click to expand...
Click to collapse
Right, so I actually had the same doubt for a while. Noone in the group seemed to properly answer this.
Some said you should, some said you shouldn't.
So I talked to the devs of note 2 (my old phone, most members now have xiaomi phones)
They all said system is required to be wiped.
However before they answered. I can already listened to our group members and figured, I will not wipe system and flash my ROM as it is.
When I did this. I noticed the recovery throwing an error from magisk. That magisk modules aren't linked to anything, and this will/may cause problems.
After reading that message I realised. System wipes everything. And if you are dirty flashing/ clean flash with no mods. System is not required to be wiped.
However most people use magisk modules. Root changes, 75hz mods and so forth. This is when system is required to be wiped.
Now. As a general rule. It is good to wipe system. No harm is being done in wiping it. Hence I reccomend it.
Although, if anyone does have a particular reason that system shouldn't be wiped. I'd love to hear the explanation of it. But this is what I know of after research. I'm still no expert in everything.
Sandeeep Kiran said:
Right, so I actually had the same doubt for a while. Noone in the group seemed to properly answer this.
Some said you should, some said you shouldn't.
So I talked to the devs of note 2 (my old phone, most members now have xiaomi phones)
They all said system is required to be wiped.
However before they answered. I can already listened to our group members and figured, I will not wipe system and flash my ROM as it is.
When I did this. I noticed the recovery throwing an error from magisk. That magisk modules aren't linked to anything, and this will/may cause problems.
After reading that message I realised. System wipes everything. And if you are dirty flashing/ clean flash with no mods. System is not required to be wiped.
However most people use magisk modules. Root changes, 75hz mods and so forth. This is when system is required to be wiped.
Now. As a general rule. It is good to wipe system. No harm is being done in wiping it. Hence I reccomend it.
Although, if anyone does have a particular reason that system shouldn't be wiped. I'd love to hear the explanation of it. But this is what I know of after research. I'm still no expert in everything.
Click to expand...
Click to collapse
Many thanks for your answer, so for now i will not risk and i will follow instructions on xioami.eu website, i'm in clean situation so i should not have any issue
bump
Good guide. Have a bump.
But till this day (Jan 6, 2020), no custom roms are stable or bugfree enough for the exception of xiaomi.eu
Default MIUIrom just works. But I hope in the near future we get to see bugfree roms and I will certainly try it! I have always used PE on my previous phones.
Cheers!!!!
bumpity bump
Nice infomation dude
whatsapp dark
root user used
Swift Installer - Themes & color engine
just share my opinion
Good guide, thx.
Guys, one question, i have to mount System/Vendor and other to wipe, or can i simple wipe without mount?
bigatim said:
Good guide, thx.
Guys, one question, i have to mount System/Vendor and other to wipe, or can i simple wipe without mount?
Click to expand...
Click to collapse
Nah, Mount is to send/transfer files.
Since you arent doing that, you dont have to mount system or vendor, but mount your internal storage though.
and for the L1 flash, mount vendor for that only, soon a magisk mod will be available for it.
So when do we need to flash disable force encryption?
If I am correct, you can simply format data and get rid of your encryption. In this case you do not need to flash disable force encryption. Also, can't you just decrypt before starting the flashing process?
I've tried RevOS and I came back to mmx.
And widevine L1 is not break. Everything gone fine.
Krullendhaar said:
So when do we need to flash disable force encryption?
If I am correct, you can simply format data and get rid of your encryption. In this case, you do not need to flash disable force encryption. Also, can't you just decrypt before starting the flashing process?
Click to expand...
Click to collapse
DFE is to remove encryption.
when you format data partition, you remove the dfe. You do this when moving from AOSP to miui or vice versa.
you can't decrypt before flashing cause there isn't a system or any data to decrypt. After you add a ROM or data, you can decrypt that.
yes, the format will get rid of your encryption. (but you also lose all your data) so flashing dfe helps retain your data. If you're scared someone will go to your recovery and steal data, add an orangefox password in its settings. Alternatively, you also have the dm-verity settings in orangefox settings you can enable. But redundant as its all included together in the dfe file I've attached.
Sandeeep Kiran said:
L3 Fix, Getting L1 after getting L3 for Global and Indian Users.
@Raaj52 Found a solution to fix L3 and get L1 again.
This fix however only works on Global and Indian vendors. (i.e mi 9t pro and k20p Indian variant)
No such solution has been found for china phones, using china vendor, DO NOT CROSS FLASH VENDORS!! it will cause a bootloop.
This patch was made for the latest EU beta, miroom. We hope it also works for future versions, and previous versions, but we are unsure. You can experiment and inform us though in the comments below.
Always have a proper fully working backup of everything rom. As caution. It's always good to take precautions.
Pop-up Camera Stuck Open Fix
Does not work on MIUI based ROMs. The App must be used on AOSP ROMs
Due to some reason you did, your phone's pop-up camera is stuck open. Too scared to push it down, or it isn't going down.
Download the apk k20pro_motor.apk from attachments below > Install it > when you open it, the dialog box will inform you to set the current state of the camera. Then click on the button to get the pop-up camera down.
Enjoy. Complete Credits to @acervenky from https://forum.xda-developers.com/k20-pro/themes/app-xiaomi-motor-control-k20-pro-t3984181
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Click to expand...
Click to collapse
hi, I followed the instructions. Netflix black screen problem still continues.What should I do ?
masik x 9.4 - black screen problem - security patch January
mi room 20.1.16 it works fine - security patch is still 2019.12.01
please masik x 9.4 fixed black screen problem.
thank you.
uurturk said:
hi, I followed the instructions. Netflix black screen problem still continues.What should I do ?
masik x 9.4 - black screen problem - security patch January
mi room 20.1.16 it works fine - security patch is still 2019.12.01
please masik x 9.4 fixed black screen problem.
thank you.
Click to expand...
Click to collapse
The patch was intended to work on security patch Jan 20th and above, which maisk is not yet updated too.
(however, @ QasimXAli in the official telegram group did manage to make it work. you can tag and ask him there.)
Currently, the person who made the mod is still working to converting it to a perfect magisk module so it's easier to flash. Also, he is waiting for the next stable update to check whether the magisk module patch will continue to work.
We just gotta wait a bit longer.
ghaf85 said:
Nice infomation dude
whatsapp dark
root user used
Swift Installer - Themes & color engine
just share my opinion
Click to expand...
Click to collapse
Thanks.
Under add-ons, I added how to get WhatsApp dark (currently in WhatsApp official beta, which will roll out to stable in three months.)
For root, everyone just uses magisk latest stable.
and Solid Explorer or Mi-explorer
I like swift, liv and flux too. but those are straight-forward. I can add them to "add-ons" if you like.
Galaxy Tab A 10.5 SM-T590/SM-T595/SM-T597
TWRP and Lineage 16/17.1 for (SM-T590/SM-T595/SM-T597)!!!!!!!!!!!!!!!!!!!!!
BROUGHT TO YOU BY: MrHomebrew
BIG CREDIT TO: Rupansh (For his time, work: dedication and discovery on how to achieve TWRP on these devices).
THANK YOU TO: Cale (For his time, findings and testing).
READ ENTIRE POST!!!!!!!!
READ ENTIRE POST!!!!!!!!
READ ENTIRE POST!!!!!!!!
THIS IS AT YOUR OWN DESCRETION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT COULD GO WRONG (for example a BRICKED DEVICE)!!!!!!!!
EXPECIALLY IF YOU CAN NOT FALLOW INSTRUCTIONS PROPERLY!!!!!!!!
THIS IS SIMPLY A GUIDE AND IF YOU ARE WILLING TO ATTEMPT ON YOUR OWN DEVICE THAT IS FULLY YOUR CHOICE, RESPONSIBILY and DESCRETION!!!!!!!!
IF YOU ARE STUCK IN A BOOTLOOP REBOOT TO DOWNLOAD MODE AND FLASH STOCK SAMSUNG ROM IN ODIN AND IF YOU WOULD LIKE, TRY AGAIN!!!!
1.
Download stock/unmodded Odin:
https://forum.xda-developers.com/attachment.php?attachmentid=4946889&d=1581302091
Install stock SM-T590/T595/T597 PIE rom with stock/unmodded Odin in download mode
(POWER OFF TABLET AND BOOT WITH VOLUME UP, DOWN AND POWER BUTTON WELL PLUGGED IN TO YOUR PC THROUGH USB).
2.
Finish setup SKIP ALL and enable OEM UNLOCK in developer options/settings.
(If developer options/settings is not viewable tap build number in settings/about a bunch of times)
(Then go back and you should see developer options in settings and ENABLE OEM UNLOCK).
3.
Download patched/modded Odin:
https://forum.xda-developers.com/attachment.php?attachmentid=4952061&d=1581888388
Reboot to recovery (POWER OFF TABLET AND BOOT WITH VOLUME UP AND POWER BUTTON).
Select wipe data/factory reset in recovery (THIS WILL WIPE THE TABLET).
THEN SELECT REBOOT TO BOOTLOADER (DO NOT REBOOT THE DEVICE TO THE SYSTEM, STRAIGHT TO THE BOOTLOADER/DOWNLOAD MODE)
(BLACK LOOKING SCREEN THIS TIME).
4.
Download TWRP:
(SM-T590)
Mega - https://mega.nz/#!nVIknQrB!-Zb_xBWy2_Ruj0TBMHPQGvND1uA_LtOvwdRkmV9sFnQ
Zippyshare - https://www15.zippyshare.com/v/dLVoxicq/file.html
(SM-T595/SM-T597)
Mega - https://mega.nz/#!GQQWnASY!T0oJEkwu9m2rviVYFHy_E5tfithsqLYUTjcIW04iGzw
Zippyshare - https://www45.zippyshare.com/v/2VGMIYyb/file.html
Well in download mode open patched/modded Odin.
Select options in patched/modded odin and UNCHECK Auto Reboot and F. Reset Time.
Select recovery.tar.md5 (SPECIFIC FOR YOUR DEVICE MODEL SM-T590 or SM-T595/SM-T597) in the AP tab of patched/modded odin.
Flash recovery.tar.md5 to your tablet.
WHEN FINISHED MAKE SURE TO REBOOT TO RECOVERY MODE/TWRP(STEPS BELOW).
HOLD (VOLUME DOWN AND POWER BUTTON) AND AS SOON AS THE TABLET TURNS OFF HOLD (VOLUME UP AND THE POWER BUTTON) TO FORCE RECOVERY MODE/TWRP
(DO NOT REBOOT THE DEVICE TO THE SYSTEM, STRAIGHT TO RECOVERY MODE/TWRP).
5.
Download Lineage 16 Download Lineage 16 and unpack the .xz so you are left with a .img file (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
(SM-T590/SM-T595/SM-T597)
Sourceforge - https://sourceforge.net/projects/an...017-UNOFFICIAL-treble_a64_avN.img.xz/download
Download Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
Mega - https://mega.nz/#!eUpj3AAR!B-3_dgBX9nEj4PJufCnCl7FsiS5bJXy-XvNsBg2KQXg
Zippyshare - https://www120.zippyshare.com/v/fDpBrVte/file.html
Download open_gapps-arm-9.0-nano (SELECT AND DOWNLOAD ARM, 9.0 nano VARIANT) (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
https://opengapps.org/
Unmount your micro sd in TWRP, remove CURRENT/MAIN micro sd card from your tablet and replace with the SECONDARY micro sd.
In recovery/twrp select wipe tab, then format data and type yes fallowed by enter (THIS WILL FORMAT/ERASE ALL DATA ON THE TABLET).
Go back to main TWRP menu, select reboot and then REBOOT TO RECOVERY.
Once Rebooted to RECOVERY/TWRP select install and at the bottom select install img.
Find the lineage-16.0-20191017-UNOFFICIAL-treble_a64_avN.img select and install it to SYSTEM IMAGE (MAKE SURE YOU SELECT SYSTEM IMAGE FOR INSTALL LOCATION!!!!).
Go back and select wipe then advanced wipe. Toggle System partition, select repair or change partition and then Resize File System.
(Swipe to resize).
Go back select install and at the bottom select install zip.
Then install open_gapps-arm-9.0-nano zip file in TWRP (AND THEN WIPE CACHE/DALVIK).
Go back select install and install Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip in TWRP.
Unmount your micro sd in TWRP, remove SECONDARY micro sd from your tablet and replace it with the MAIN micro sd card.
6.
REBOOT TO SYSTEM AND SEE THE MAGIC HAPPEN (NOT DONE YET IF YOU WANT ANDROID 10 ALONG WITH ADOPTABLE STORAGE!!!!).
Setup device
FORMAT your MAIN micro sd card in android (SHOULD SEE A NOTIFICATION TO FORMAT MICRO SD CARD).
Select the formatting notification, dismiss the first popup and select adoptable/internal storage. (Be Patient and let it finish formatting).
(IF LINEAGE 16 DOES NOT ASK TO FORMAT MICRO SD CARD EJECT THEN PLACE IT IN A WINDOWS COMPUTER AND FORMAT TO SOMETHING ANDROID DOES NOT LIKE AND TRY AGAIN)
(FALLOWING INSTRUCTIONS BELOW)!!!!
Then insert your MAIN micro sd card (THAT IS FORMATTED IN A WAY THAT FORCES YOU TO HAVE TO REFORMAT) the MAIN micro sd card in Lineage 16
(SHOULD SEE A NOTIFICATION TO FORMAT MICRO SD CARD).
Select the formatting notification, dismiss the first popup and select adoptable/internal storage. (Be Patient and let it finish formatting).
7.
Download Lineage 17.1 and unpack the .xz so you are left with a .img file (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
(SM-T590/SM-T595/SM-T597)
Sourceforge - https://sourceforge.net/projects/an...111-UNOFFICIAL-treble_a64_avN.img.xz/download
Download open_gapps-arm-10.0-nano (SELECT AND DOWNLOAD ARM, 10.0 nano VARIANT) (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD):
https://opengapps.org/
Download PHH-Magisk (PLACE IT ON A SECONDARY/SPARE MICRO SD CARD)
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
Power off or reboot to twrp (VOLUME UP AND THE POWER BUTTON).
Unmount your micro sd in TWRP, remove MAIN micro sd card (NOW USED AS ADOPTABLE STORAGE) from your tablet and replace with the SECONDARY micro sd.
Now select install and at the bottom select install img.
Find the lineage-17.1-20200111-UNOFFICIAL-treble_a64_avN.img select and install it to SYSTEM IMAGE (MAKE SURE YOU SELECT SYSTEM IMAGE FOR INSTALL LOCATION!!!!).
Go back and select wipe then advanced wipe. Toggle System partition, select repair or change partition and then Resize File System.
(Swipe to resize).
Go back select install and at the bottom select install zip.
Then install open_gapps-arm-10.0-nano zip file in TWRP (AND THEN WIPE CACHE/DALVIK).
Go back select install and YOU MUST INSTALL Magisk-v20.2-b29f0ca4-phh.zip (OR ELSE LINEAGE 17.1 WILL NOT BOOT).
Go back select install and install Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip in TWRP.
Unmount your micro sd in TWRP, remove SECONDARY micro sd from your tablet and replace it with the MAIN micro sd card (STILL USED AS ADOPTABLE STORAGE).
8.
(VERY IMPORTANT YOU CAN UPDATE (MAGISK MANAGER) BUT NOT (MAGISK) ITSELF!!!! DO NOT UPDATE MAGISK!!!!) YOU WILL END UP IN A BOOT LOOP).
(VERY IMPORTANT) REBOOT TO SYSTEM AND GO IN TO MAGISK MANAGER.
Go to modules in Magisk Manager and install Busybox for Android NDK (DO NOT REBOOT) and also install MagiskHide Props Config (NOW REBOOT).
After reboot go to developer options/settings (System/Advanced/Developer options) and enable Local terminal.
(If developer options is not viewable tap build number in settings/about a bunch of times till it enables)
(Then go back and you should see developer options in settings).
9.
Return to home screen and launch terminal app.
In terminal app type "su" (WITHOUT QUOTES) and hit enter (ALWAYS HIT ENTER TO EXECUTE THE COMMAND).
Accept Magisk/Superuser popup for terminal.
(If you accidentally deny/miss permission go to Magisk a enable Superuser for terminal).
In terminal app type "props" (WITHOUT QUOTES).
Select option "1" (WITHOUT QUOTES), then select option "f" (WITHOUT QUOTES) and then select option "23" (WITHOUT QUOTES).
Now select (ONE OF THESE 3) options "45" (WITHOUT QUOTES) for SM-T590 / option "46" (WITHOUT QUOTES) for SM-T595 / or option "47" (WITHOUT QUOTES) for SM-T597.
Finally select "y" (WITHOUT QUOTES) to accept and then select "y" (WITHOUT QUOTES) to restart.
FINISHED!!!!
YOU ARE DONE!!!!
Hope you enjoy, a lot of work has gone in to making this possible on the Galaxy Tab A 10.5 SM-T590/SM-T595/SM-T597.
BUGS/ISSUES:
Encryption
Lockscreen password NOT WORKING (DO NOT SET A PASSWORD)
MTP not working in TWRP
Two out of four speakers WORKING
Can only enable adoptable storage in Lineage 16 and carry it over to Lineage 17.1
DEMONSTRATION/REVIEW VIDEO COMING SOON!!!!
BROUGHT TO YOU BY THE ONE AND ONLY: MrHomebrew
Contributors: MrHomebrew, Rupansh and Cale.
Source Code Used To Help Build TWRP For SM-T590/SM-T595/SM-T597
https://github.com/rupansh/android_kernel_samsung_gta2xl
Magisk_PHH and Lineage 16/17.1 GSI: AndyYan
XDA:DevDB Information
[RECOVERY][ROM][ROOT][UNOFFICAL] TWRP 3.3.1-0 + Lineage [SM-T590/SM-T595/SM-T597], Kernel for the Samsung Galaxy Tab A series
Contributors
Leonidas87, rupanshji, AndyYan, Cale
Source Code: https://github.com/rupansh/android_kernel_samsung_gta2xl
Kernel Special Features:
Version Information
Status: Stable
Created 2020-02-20
Last Updated 2020-02-20
confirmed working on sm - t590.
many thanks !
supelele said:
confirmed working on sm - t590.
many thanks !
Click to expand...
Click to collapse
You are welcome, thanks for confirming you had success on your end :good:
One issue. Wifi does not stay enabled.
Connection gets disconnected here.
supelele said:
One issue. Wifi does not stay enabled.
Connection gets disconnected here.
Click to expand...
Click to collapse
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
MrHomebrew said:
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
Click to expand...
Click to collapse
Did try that. It keeps remembered and after a resstart it is connected. But after 2 Minutes it goes to disconnected and stays there.
Tried 2 wifis. Tried aswell reflashing line 17.
No success :/
MrHomebrew said:
Try forgetting the network in wifi settings. Reboot and then connect to the network again with the password. Might help, I noticed that one time during testing
Click to expand...
Click to collapse
Disableing location did the trick
Want to try but...
Firstly, thank you for this. I can only imagine the time and effort to figure this out.
How the hell you guys do this I'll never know. Kudos.
Now, what if I want to install LineageOS 16 without the adoptable storage and get root? Is there a reason one needs adoptable storage for this process?
Nervous about having an eventually-to-fail sd card in there and no spare sd card slot to add storage.
All I really want (sorry, would like) right now is root so I can fiddle with my device. It seems all other attempts at pure root result in bootloop and having to reflash stock. I know, I tried https://forum.xda-developers.com/showthread.php?p=81286251#post81286251 and posted my results.
Is there a method to just install LlineageOS/Gapps, Magisk, Busybox/su?
Not wanting to knock your efforts, but a slimmed down LinOS16 with root installation instr. will be fantastic!
Is there a benefit to having to do the system install with adoptable storage?
Thanks again.
T
TrinityTrip54 said:
Is there a method to just install LlineageOS/Gapps, Magisk, Busybox/su?
Not wanting to knock your efforts, but a slimmed down LinOS16 with root installation instr. will be fantastic!
Is there a benefit to having to do the system install with adoptable storage?
Thanks again.
T
Click to expand...
Click to collapse
You don't have to use adoptable storage it's just an option really. If you want to use lineage 16 you can just fine with even magisk canary builds, might want try out some other GSI a64a ( ARM 32-bit with 64-bit binder, A-only) builds with an AOSP base and see what works. The only benefit would be having extra install space for loads of apps and full access to storage. As far as lineage 17 goes you must flash the magisk-phh for it to even boot but adoptable storage you don't need. Still follow the instructions minus adoptable storage and you'll achieve root in no time. As of right now there's been weekly builds of lineage GSI. Hopefully we'll get a real build of lineage 17 eventually.
Highly recommend orange fox recovery.
whenever i try to flash the recovery i get an error only official released binaries are allowed to be flashed how do i resolve this problem?
Mikxx said:
whenever i try to flash the recovery i get an error only official released binaries are allowed to be flashed how do i resolve this problem?
Click to expand...
Click to collapse
https://www.the***********.com/prenormal-rmm-state-on-samsung-galaxy-guide/
dm.homelinux.com said:
https://www.the***********.com/prenormal-rmm-state-on-samsung-galaxy-guide/
Click to expand...
Click to collapse
link broken but it still helped me out thanks
Boot loop after installing Busybox for Android NDK and MagiskHide Props Config
8.
(VERY IMPORTANT YOU CAN UPDATE (MAGISK MANAGER) BUT NOT (MAGISK) ITSELF!!!! DO NOT UPDATE MAGISK!!!!) YOU WILL END UP IN A BOOT LOOP).
(VERY IMPORTANT) REBOOT TO SYSTEM AND GO IN TO MAGISK MANAGER.
Go to modules in Magisk Manager and install Busybox for Android NDK (DO NOT REBOOT) and also install MagiskHide Props Config (NOW REBOOT).
After reboot go to developer options/settings (System/Advanced/Developer options) and enable Local terminal.
(If developer options is not viewable tap build number in settings/about a bunch of times till it enables)
(Then go back and you should see developer options in settings).
Click to expand...
Click to collapse
Hello community,
I am now at this point. I have installed just Linage 17, without Linage 16 without gapps, because i dont need them.
So, lineage 17 is starting, now I have to prepare Magisk.
I have updated _JUST_ Magisk Manager (see screenshot) and installed two recommended modules (Busybox for Android NDK and MagiskHide Props Config)
After reboot ends up in a boot loop. Interim solution is start to recovery and make factory reset. In this case is Magisk not available. After Magisk installation there is again a loop. I tried this 3 times. What I am doing wrong?
dm.homelinux.com said:
Hello community,
I am now at this point. I have installed just Linage 17, without Linage 16 without gapps, because i dont need them.
So, lineage 17 is starting, now I have to prepare Magisk.
I have updated _JUST_ Magisk Manager (see screenshot) and installed two recommended modules (Busybox for Android NDK and MagiskHide Props Config)
After reboot ends up in a boot loop. Interim solution is start to recovery and make factory reset. In this case is Magisk not available. After Magisk installation there is again a loop. I tried this 3 times. What I am doing wrong?
Click to expand...
Click to collapse
Are you using magisk-phh? Also try using magisk manager Canary
Yes. Step 7
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
What ist Magisk Manager canary?
Edit: many thx
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
It semms to be stable, after I installed this apk. Magisk is now available as app, i can see the installed modules and the system starts correctly.
Do I ned the next steps with su?
The rom works great, but one question, is it possible to get the assistant ambient mode on this device when i place it in my pogodock?
Mikxx said:
The rom works great, but one question, is it possible to get the assistant ambient mode on this device when i place it in my pogodock?
Click to expand...
Click to collapse
As far as I know probably not. These are GSI builds and are not exactly fully supported for our devices but still function pretty good.
---------- Post added at 08:53 AM ---------- Previous post was at 08:53 AM ----------
dm.homelinux.com said:
Yes. Step 7
https://sourceforge.net/projects/de...magisk/Magisk-v20.2-b29f0ca4-phh.zip/download
What ist Magisk Manager canary?
Edit: many thx
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
It semms to be stable, after I installed this apk. Magisk is now available as app, i can see the installed modules and the system starts correctly.
Do I ned the next steps with su?
Click to expand...
Click to collapse
Next steps for su? Which steps are you referring too? As soon as you have magisk-phh flashed with Canary manager on 17 you have SU. As far as 17 goes do not update magisk just manager. 16 you can use any magisk up to Canary
koobie777 said:
Next steps for su? Which steps are you referring too? As soon as you have magisk-phh flashed with Canary manager on 17 you have SU. As far as 17 goes do not update magisk just manager. 16 you can use any magisk up to Canary
Click to expand...
Click to collapse
I refer to step 9 in this manual on page 1.
But su is indeed over Magisk configuration. ROM works very well
Magisk also working with LineageOS 16 ?
jb44 said:
Magisk also working with LineageOS 16 ?
Click to expand...
Click to collapse
Yes up to Canary. Use magisk-phh for 17
---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------
dm.homelinux.com said:
I refer to step 9 in this manual on page 1.
But su is indeed over Magisk configuration. ROM works very well
Click to expand...
Click to collapse
Step 9 is recommended for safteynet
Moto-Lite Stock Nougat ROM
Android 7.0 / NPHS25.200-23-1
Moto X Pure Edition XT1575
TWRP Flashable Installer
Rooted, Debloated, Optimized
•••••••••••••••••••••••••••••••••••••••••••••••••••••
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's Moto-Lite?
Moto-Lite is an entirely stock-based Motorola ROM, with performance optimizations, systemless root, and some moderate debloating. This ROM is intended to give users a clean, slimmed down stock experience -- via a TWRP flashable installer.
_______________________________________
DISCLAIMER:
By proceeding further, you are assuming full responsibility for your device. Although this ROM has been thoroughly tested, I assume no liability in the event you damage your device or otherwise render it inoperable. Follow the simple instructions and things should go smoothly.
_______________________________________
BUILD INFO:
•Android Version: 7.0 Nougat
•Build No. NPHS25.200-23-1
•System Version: 25.211.1
•API Level: 24
•Build Date: October 30, 2017
•Security Patch Level: October 1, 2017
•Kernel Version: 3.10.84-perf
•Bootloader Version: AO.52
_______________________________________
FEATURES:
•Rooted with Magisk 20.4-Stable
•Static BusyBox Binaries: v1.31.1
•Moderately Debloated
•Safety Net Pass (ctsProfile/basicintegrity)
•Force Encrypt Disabled (Opt Encrypt)
•dm-verity/AVB 2.0 Disabled
•Custom Moto Boot Logo
•Optimized for RAM Efficiency
•su.d Support
•Fully Odexed per Stock Config
_______________________________________
Official Motorola Firmware for XT1575:
This firmware repo encompasses official firmware packages that originated from Motorola's servers. This link includes Android 5.1.1, Android 6.0 and Android 7.0-based firmware builds, including the NPHS25.200-23-1 build upon which this Moto-Lite ROM is based.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Kernel Source Code:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPH25.200-15
_______________________________________
PREREQUISITES:
Per the general rule of thumb, you will need an unlocked bootloader and a custom recovery such as TWRP. I recommend using the most current official TWRP build from here: https://dl.twrp.me/clark/
In order to circumvent force encryption during installation, you will need external storage such as a microSD card or an OTG USB storage device. (The /userdata partition must be formatted prior to installation; hence, all files and data stored on your device will be erased.) If you do not have, or do not wish to use, an external storage medium, alternative install instructions have been provided, for which you will need a PC or laptop computer and a good quality micro USB to USB syncing/charging cabke
NOTE: The below instructions assume that your device's firmware has been updated to the NPHS25.200-23 firmware build. It is also assumed that your device's modem/baseband version is M8992_1255331.29.01.88.09R SUPER_NA (the most current version).
_______________________________________
Instructions for installation are outlined under two separate headings: A. INSTRUCTIONS - STANDARD INSTALL, which apply to users who have an external micro SD card or an OTG supported external storage medium; and B. INSTRUCTIONS - NO EXTERNAL STORAGE, which should be used by those who do not have, or do not wish to use, a micro SD card or an OTG supported external storage device. For the latter you will need a laptop or computer and a good quality micro USB to USB syncing cable, for transferring the ROM zip file to your phone during the process
A. INSTRUCTIONS - STANDARD INSTALL:
1. Download the ROM zip from the below link and save it to external storage;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Select INSTALL, select the ROM zip, and commence installation;
5. Once the ROM is installed, the installation script will patch the stock boot image via Magisk v20.4-Stable to enable systemless root. BusyBox v1.31.1 static binaries will also be installed;
6. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
7. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions on your part;
8. Enjoy & profit...
B. INSTRUCTIONS - NO EXTERNAL STORAGE DEVICE
1. Download the ROM zip from the below link and save it to your computer;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Transfer the ROM.zip the file from its saved location on your computer to the now-formatted internal storage directory on your phone (via a micro USB to USB syncing/charging cable);
5. Reboot Recovery;
6. Select INSTALL, select the ROM zip, and commence installation ;
7. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
8. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions;
8. Enjoy & profit...
At the time I cooked up this ROM, the latest stable Magisk version was v20.4, so my systemless root installer encompassed within the ROM installer employs Magisk v20.4 stable. After installing the ROM, booting up and completing initial setup, open the Magisk Manager app to update Magisk to the most current version.
_______________________________________
THANK YOU:
Thanks to the amazing @osm0sis for his static BusyBox binary installer. And many thanks to @topjohnwu, the genius developer and creator of Magisk. Huge thanks to @pitflyer, who gave feedback and input on methods of install, and who revisited and outlined the steps for an alternative installation without using a micro SD or OTG supported storage device.
Thanks to @sd_shadow for his input and guidance on installation.
_______________________________________
BUGS:
Since this ROM is based entirely on an official Motorola stock firmware build, no significant bugs or instabilities should be expected. I have tested this ROM thoroughly after performing some optimizations (RAM, I/O Schedule tweaks. Entropy tweaks, etc.), moderate debloating and Magisk installation. I have noted no remarkable bugs, instabilities or performance flaws. However, please leave a comment in the event you discover flaws or bugs. I will look into the issue and try to resolve it. If possible, submit a bug report. Otherwise, list as much detail and specifics as possible regarding the issue.
_______________________________________
DOWNLOAD LINKS:
Moto-Lite XT1575 Android 7.0 ROM
**V2 updated ROM: Magisk v24.3, Busybox v1.34.1 static binaries, some additional debloating and some more RAM optimizations made on the kernel level.
V2 Moto-Lite xt1575 Android 7.0 ROM
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
bronkish said:
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
Click to expand...
Click to collapse
Thanks for your input on this. I'll take a look at the Moto Voice service and see if I have debloated a system app or process that is Moto Voice dependent. Did you notice the Moto Voice issue before installing Xposed & GravityBox? Yeah I absolutely love SD Maid Pro. A great system-level tweaking tool with many uses.
Gravitybox, yessir. I typically get my dumps in order, reboot to twrp, wipe it all, flash a ROM, reboot, initial setup, dev mode and those settings, airplane mode, reboot, flash xposed, reboot, set up my phone. You know, if I do it that way.
Lol, I got no time to see if your kung-fu works right before I fuk it up with xposed. I can't answer the only and perfect question that you asked me. What's even more perfect than that failure is that I bought a g power the other day and haven't used my Xpure since last week. This g power has a burn't pixel though. WTF. I had it 8 days to replace the phone I used 5 years.....sigh.
THanks for responding, sorry I can't help you help me. Probably going to return the g power and use the x pure again and wait for a sweet-ass black-friday deal to replace it. There's a 7T on craigslist winking at me, though... I probably won't reset anything on the Xpure though, runs sweet. Hard phone to replace.
Edit - yeah - been using SD maid for years - love it, use the hsit out of it. ONly realized yesterday that I can dump apks of all installed apps at one go. It just keeps on giving.
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
mddunner said:
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
Click to expand...
Click to collapse
Thank you for your feedback and kind words. Glad to hear the ROM worked well on your device.
thank you works great and its rooted.
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
pitflyer said:
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
Click to expand...
Click to collapse
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not have external storage mediums or, like many users, may want to expedite the installation process. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Hodgdon said:
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
Click to expand...
Click to collapse
Happens to the best of us. Is the ROM working ok for you?
Viva La Android said:
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not own an OTG based external storage device. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Click to expand...
Click to collapse
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
pitflyer said:
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
Click to expand...
Click to collapse
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Viva La Android said:
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Click to expand...
Click to collapse
No problem and thank you for sharing the updated ROM!
This looks like the solution I need ...
Could y'all PLEASE define exactly which TWRP yer using to get this from the SDcard into the phone?
Essentially, I UL my BL via moto, fastbooted TWRP (3.1? I'd heard going past 3.2 invited a.b partition foibles) however this still gives me the "Unlocked Bootloader" BSOD, ergo cannot USE twrp - it simply reboots into a functional fone (but obviously NOT secure)
The XT1575 came (used) with stock Nougat ... can supply logcat etc if that's of any use to removing this stupid VIBRATOR screen that won't let me get into TWRP at all
TYVM
VW
You may use any version of TWRP you wish for installing this ROM. I would personally recommend the latest official TWRP v3.5.2-9.0, released just last month. TWRP for the xt1575 Clark was built using device-specific kernel source code. Thus, no matter which version of TWRP you encounter, A/B partitioning will not be a factor because the Clark does not now, nor has it ever, used the A/B partitioning scheme.
So try these steps exactly: download TWRP v3.5.2-9.0 from here https://dl.twrp.me/clark/ , rename it to twrp.img and store the image in your ADB/Fastboot directory on your PC. Also, save a copy of this renamed TWRP image on your xt1575. Boot your Moto into fastboot mode and connect the device to your PC using an adequate data sync cable. Open a command window on your PC in the path of your ADB/Fastboot directory. After confirming.a proper sync, flash TWRP by executing this command:
fastboot flash recovery twrp.img
Now boot to TWRP using:
fastboot boot twrp.img
Once booted into TWRP, select Install, tap the Install Image option in the lower-right of the display, navigate to the saved location of twrp.img you saved earlier and select it. Now, select Recovery from the partition options presented. Commence installation. When finished, TWRP should be installed properly on your /recovery partition. To ensure its persistence as properly installed, choose Reboot and Recovery.
Now you may install the ROM by the instructions outlined in this thread.
NOTE: There have been reports for years of xt1575 owners encountering difficulty with "making TWRP stick" while using the stock Android OS; i.e., TWRP being overwritten or replaced by stock recovery upon the first reboot to the Android OS following TWRP installation via fastboot. This is a common occurrence on many Motorola devices when TWRP is installed alongside the stock OS. (The best I can recall, this glitch is related to a "boot.p" script present in the stock Android ROM.) The instructions I outlined above can be used as a workaround to this issue to prevent custom recovery from being replaced or overwritten by stock recovery.
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
mddunner said:
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
Click to expand...
Click to collapse
Yeah it's an older version, but other than the upstream codebase, the newer versions for the Clark (built on the Android 9 Pie tree) are not remarkably different in terms of the GUI. For purposes of what we are doing here --installing a stock ROM archived package --pretty well any TWRP or OrangeFox custom recovery build will suffice.
For any members interested, I have updated this build to include Magisk v24.3, BusyBox v1.34.1, and I've done a bit more debloating and added some RAM tweaks on the kernel level. I'll need testers as I no longer own this device. Let me know by leaving a reply if you would like to test. I am posting a link in the downloads section for the updated ROM, but again I emphasize, this is of yet untested.
Note
Before getting started, I'm not a developer and I'm not on that level yet but being an enthusiast of Android ROMs especially my favorite ROM Pixel Experience (PE). However what I can contribute (as of now) is to guide newbies and answer people who is confusing with flashing PE ROM, any custom kernels, mods, Gcam and help you out from problems while trying these things.
Tons credits to @jhenrique09, without his great effort there is no born of Pixel Experience project, and we would not have a taste of stock and pure Pixel ROM without having an actual Pixel phone.
It is good that you attempt new things and seek into the freedom of pure Android experience, and the whole world of Android development, though there's some risk when you try something new.
!!! Warning: I am not responsible for any bricked devices, it is your choice to modify your device software.
Pixel Experience ROM official thread - by Henrique Silva @jhenrique09
How to unlock bootloader?
https://xiaomiwiki.github.io/wiki/Unlock_the_bootloader.html
Official ROM downloads:
Download from Pixel Experience website
Screenshots
Check telegraph here!
Pixel Experience Official Wiki Page for Redmi K20 Pro/Mi 9T Pro - Info about raphael & raphaelin
Appreciation to
@jhenrique09, founder and lead developer of Pixel Experience, and maintainer for raphael & raphaelin (Redmi K20 Pro & Mi 9T Pro Series).
@WasikFahim, a friend of mine who assists me for creating this thread.
Thanks to all developers I have been know so far.
And all developers and original creators of the attached files below and for all of the following posts.
Special thanks to @Sandeeep Kiran (TG handle @ sandeeep, due to request from him), who has proposed the idea of creating this new thread for me.
Reserved.
Nice Thread ?
How To Flash Custom Kernels
Hello Guys Hope You're Fine, Today We're Going To Learn How To Flash Custom Kernels In Recovery, So Without Further Due Let's Jump Into It:
I'm Using PitchBlack Recovery
Prerequisite:
*Backup Stock Kernel [Boot.img & Dtbo(Optional)] Image=> 1 & 2
Steps For Flashing Custom Kernels:
1.Go To Recovery.
2.For OF(Go To Files) For TWRP/PBRP(Go To Install). Image=> 3
3.Select Kernel And Swipe to Install. Image=> 4 & 5
4.Wipe Dalvic/Cache.(Optional)
5.Reboot To System.
Enjoy!!!!!! :good::fingers-crossed:
Here Are Some Recommended Kernels:
We Use LOS FOD Implementation.
Gaming & Decent Battery = F1xy
Battery Backup & Decent Gaming = Immensity
Decent Performance + Battery = Englezos (Less gaming)
Mods tutorials
ANX Camera
ANX Camera TWRP
ANX Camera magisk
Working version of ANX magisk: 185
48MP fix for ANX camera magisk module: 181
Which ones should I download? Check attached screenshots below this post.
How to install and setup MIUI camera on PE?
* For ANX Camera TWRP
1. Save zip file to internal storage (/sdcard) and reboot to recovery.
2. For orangefox go to "files", for TWRP or Pitchblack recovery go to "install".
3. Swipe button to install.
4. Reboot to system.
5. Give all permissions to ANX camera, launch and quit app for at least 3 times.
6. You're all done.
* For ANX Camera magisk modules
1. Save both camera and 48MP fix modules to internal storage (/sdcard).
2. Open magisk manager, hamburger icon on top left corner, modules, tap on "+" icon and find ANX camera zip.
3. Same goes with 48MP fix module.
4. Reboot, give all permissions to ANX camera app, then launch & quit app for at least 3 times.
5. You're all done.
* 48MP fix is already included in ANX Camera TWRP, do NOT flash the 48MP fix magisk module.
* No root needed.
+ Credits to ANX developers and contributors, @HSgod, @nuub1k, for porting and debugging MIUI camera to AOSP ROMs.
Custom boot logo
MS drive Downloads
Head to XDA thread for more info, credits for @mouhannadsukkar creating boot logo collection.
Disable force encryption
Force Encrytion and difference compared with decrypted storage
1. All ROMs have force encryption by default for now, which should be enabled while booting the device for the first time.
2. Therefore DFE, also known as "disable force encryption", which shall force the device to be decrypted (Use #-dfe to get the DFE file).
3. If you format data, it will decrypt the encrypted storage, while everything on data partition including internal storage, also known as /sdcard directory, will be erased.
4. However if you already got a decrypted storage, simply wipe data and internal storage won't have any effects, unless you do a format.
5. To keep the storage decrypted, if you want, you will need to flash DFE for every ROM and vendor update.
6. Format data only if you flash custom ROM from stock MIUI, if you want to keep your storage decrypted or you want encrypted without flashing DFE while flashing custom ROMs and vendors (if the ROM uses MIUI vendor).
7. In short formatting data is to remove encryption for an encrypted device.
How to flash DFE?
IMPORTANT: Please make sure you perform a data FORMAT (NOT wipe) via recovery before flashing DFE, otherwise device may end up with bootloop or stuck in bootloader! Everything including all files on internal storage will lost so please backup everything to elsewhere. You have been warned, I am not responsible for data loss.
1. Go to recovery and format data (NOT wiping it, the place where you will type "yes" and confirm formatting).
2. Since internal storage is purged too, copy DFE from your PC or OTG storage etc., flash via recovery.
3. The recovery console will ask you to press volume buttons for picking options, so the recommended key combination is:
+ (vol up)
- (vol down)
- (vol down)
+ (vol up)
4. Done, reboot to system and see if storage is decrypted.
F2FS
What is F2FS?
F2FS, which stands for "Flash-Friendly File System", it was invented by Samsung coorperation, mainly focus on improving random read/write efficiency of flash storage and somewhat extends its lifespan.
Notice!!!
Currently, almost all known custom ROMs support F2FS on cache and data partitions but not system for compatibility and disk quota reasons, usually there's no writing actions to system partitions except flashing/updating ROM or using root access to modify it so keep system partition as EXT4.
How to enable F2FS?
You will lose all of your data including internal storage.
1. In recovery, convert data partition to F2FS via advanced wipe, same for cache partition (Do not convert system partition to F2FS to avoid some possible problems).
2. Flash f2fs-patched-fstab.zip (attached below) via recovery.
3. Reboot.
Note: You will have to flash patch again whenever flashing/wiping vendor, otherwise you will stuck at boot animation.
Fix low microphone problem (magisk needed)
Description
Sometimes, you might feel the microphone sensitivity isn't good enough on AOSP ROMs including Pixel Experience, this might related to device tree (or source code) of K20 Pro/9T Pro series. For instance you make or pick a phone call, using voice call of some IM apps the other side might not hear you clearly, that's the time when you can have a workaround if you have magisk installed.
How to fix?
Same as you install any magisk modules via magisk manager.
magisk_iem_mic_gain_0.3.zip attached below.
Magisk manager recovery mode
What to do if my device stuck at boot animation?
Sometimes, your device might stuck at boot animation because you flashed a buggy magisk module, for obvious reasons you have to delete that for letting your device boot into OS, so what about removing it via recovery? That's how this zip comes - Magisk Manager Recovery Mode.
How?
1. Boot your device to recovery, flash provided zip file.
2. Go to advanced => terminal.
3. Type this command to launch program:
sh /sdcard/mm
4. Type l to list all installed magisk modules, locate the one which might causes the problem.
5. Type r, enter, then the name of module name as the output shown, case-sensitive!
For example:
module[]
You should type:
module
Then enter.
6. If you see there's an X inside brackets like:
module[X]
Then you're good to go.
7. Reboot your phone and that's it.
Troubleshoot and advanced guides
Stuck at bootloader
Sometimes when you flashed ROM, custom recoveries, or updating vendor and try rebooting your device thereafter, your device does not boot into system or recovery but fall into bootloader (fastboot) screen. This is due to verified boot of our device being triggered, so flashing a custom vbmeta will usually get the problem solved.
How to flash vbmeta?
You need a working PC or laptop, USB cable and install fastboot driver if you are using Windows.
1. Download attached vbmeta file to your PC, connect your phone with USB cable, make sure PC has detected the phone and it's connected properly.
2. Open CMD (if using Windows) or terminal (Linux/Mac).
3. Type the following command:
Code:
fastboot flash --disable-verity --disable-verification vbmeta fake_vbmeta_williamfeng.img
4. Reboot your device to either recovery or system, it should work fine now.
Upgrade vendor
Note: You will not lose your data so you don't need to wipe anything, just flash vendor on top of current one, no matter if device is encrypted
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Reboot to system.
Downgrade vendor
Note: Before you downgrade your vendor you're suggested to backup all your data (including internal storage) elsewhere in case you lose them while doing so.
If your device is decrypted (NOT encrypted), the steps are same as you upgrade vendor.
Otherwise:
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Format data partition in your recovery (the place where you'll type "yes" and confirm formatting).
5. Reboot to system.
How to update PE ROM?
You don't need to download full zip file on PE, it gives small OTA which can be downloaded from "settings => system => system updater". After downloading simply tap on 'apply/install update', then the device will boot into recovery, update and reboot back into system.
WARNING: Make sure your device always have enough charge (30% or more is suggested) for updating process.
* The update file will be downloaded to /data/system_updates
Error 7 when updating PE
- If you see updating ROM doesn't work and the recovery shows you error 7, please make sure you update vendor to correct one first.
- Try updating your recovery (TWRP/OFOX).
If it still happens, try flashing full ROM zip of latest build instead of using built-in updater from ROM.
Miscellaneous info of Pixel Experience
Changing animation of Pixel Experience - just like you have a real Pixel device!
Power-off your phone and plug into changer, you'll see that.
Video link