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?
Hello all,
I'm trying to enable avb on a user build and I don't really know where to start.
I signed the build with my own keys and I also wrote the key to the device (fastboot flash avb_custom_key).
I presume I also have to sign the vendor.img file as well. That is not included in the LOS build as it sits in its own partition. But I can extract it in img format with dd.
How should I go about this? Found barely any info on this subject. Asked around LineageOS channels but got no info on this.
As it stands the LOS build is not enforcing avb. I can basically modify anything in /vendor or /system and it persists on reboot.
If someone understands the whole thing any info is very appreciated.
I presume I must add my key to vbmeta.img?
Thank you
@mad_rock
You mean ADB?
jwoegerbauer said:
@mad_rock
You mean ADB?
Click to expand...
Click to collapse
nah, adb is ok.
avb as in Android Verified Boot
trying to figure out how to set it up properly.
found a flag in build config that's disabling avb but I need to understand the rest of the stuff so I can configure it properly before I remove the flag.
as I see it, vbmeta is using a testkey from the build sources, not using any key that I generated to sign apks/builds etc.
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
Important information:
This thread is for LineageOS 18.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
Installation:
If you are on the stock OS, you will first need a custom recovery. You can get the recommended Lineage recovery here.
If you are coming from stock or other ROMs, you need to do a factory reset, and resize your partitions with this tool.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on wt88047
Download link:
Google Drive
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
Google Drive
Changelog:
Changes for wt88047x
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to nicknitewolf
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@nicknitewolf, Lineage Team
ROM OS Version: 11.x R
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M8936FAAAANUZM-1.33887.1.41528.1
Based On: LineageOS
Please do note that you HAVE to resize your partition with the tool above, otherwise the ROM will NOT install.
If the link above wasn’t clear enough:
nicknitewolf said:
Please do note that you HAVE to resize your partition with the tool above, otherwise the ROM will NOT install.
Click to expand...
Click to collapse
Hey brother, First of all thanks a lot for keeping this device alive! Any idea about LTE? It seems to not be working in my device, the ROM is fluid smooth and works without any bugs! Thanks brother!
Oops! forget to mention few things for the people who want to install this ROM:
1.You have to RESIZE the SYSTEM PARTITION! without doing so, the ROM won't install!!!
2. How to resize the system partition? Here's how:
[TWRP][AROMA][WT88047] Resize System partition Easily
With this tool is possible resize the system partition. Precautions and warnings: This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups. Increasing the size of the system will...
forum.xda-developers.com
Go to the above link and follow the instructions to resize your system partition.
(Recommended resize gb is 2.00gb)
3. After installing the ROM, it could take 40 to 45 minutes to boot into the system (mine took 30 min).
4. When you boot into the ROM, it might be very laggy and the device might heat up very rapidly, it's not a problem, wait for 10min or so for the device to cool down then start using your device. It'll become smooth like butter.
HUGE THANKS TO THE DEVELOPER (@nicknitewolf) OF THIS ROM FOR KEEPING REDMI 2/ REDMI 2 PRIME ALIVE!!!!
THANKS @nicknitewolf !!!!!!!
Thank you master
thank you, bro
nicknitewolf said:
Please do note that you HAVE to resize your partition with the tool above, otherwise the ROM will NOT install.
Click to expand...
Click to collapse
I got an error when executing the resize partition script, it said unknown partition detected (or something like that). I did that with latest official TWRP.
So I try to download the reccomended TWRP from the OP, but the link seems not working.
Any suggest to past that error? I don't try the other partition resizer methode yet... Thanks in advance
didhiy said:
I got an error when executing the resize partition script, it said unknown partition detected (or something like that). I did that with latest official TWRP.
So I try to download the reccomended TWRP from the OP, but the link seems not working.
Any suggest to past that error? I don't try the other partition resizer methode yet... Thanks in advance
Click to expand...
Click to collapse
I got the same problem as you mentioned above, please use this link and follow the methods to resize the partition:
[TWRP][AROMA][WT88047] Resize System partition Easily
With this tool is possible resize the system partition. Precautions and warnings: This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups. Increasing the size of the system will...
forum.xda-developers.com
This should resize your partition.
thanks dev, good rom even if the features are not many ... it is enough to change the system size to 1.5gb to install this rom. 1 day of use has not found a bug.
Initial impressions of LOS 18.1
1. Rom runs smoothly without gapps (i think gapps are causing higher boot time)
2. No bugs till now using for more than a day.(i will report if anything found)
3. system partition of minimum 1.5 gb required to install.
What's about battery ?? It's completes fast or it's better ?
Nicknitewolf pls reply why battery is draining fast in custom roms ??
didhiy said:
I got an error when executing the resize partition script, it said unknown partition detected (or something like that). I did that with latest official TWRP.
So I try to download the reccomended TWRP from the OP, but the link seems not working.
Any suggest to past that error? I don't try the other partition resizer methode yet... Thanks in advance
Click to expand...
Click to collapse
Thats you have resized your partitions before. You have to have the original partition layout before you are able to flash my script in OP
resize_v2_wt88047x.zip
drive.google.com
ilikephones98 said:
Hey brother, First of all thanks a lot for keeping this device alive! Any idea about LTE? It seems to not be working in my device, the ROM is fluid smooth and works without any bugs! Thanks brother!
Oops! forget to mention few things for the people who want to install this ROM:
1.You have to RESIZE the SYSTEM PARTITION! without doing so, the ROM won't install!!!
2. How to resize the system partition? Here's how:
[TWRP][AROMA][WT88047] Resize System partition Easily
With this tool is possible resize the system partition. Precautions and warnings: This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups. Increasing the size of the system will...
forum.xda-developers.com
Go to the above link and follow the instructions to resize your system partition.
(Recommended resize gb is 2.00gb)
3. After installing the ROM, it could take 40 to 45 minutes to boot into the system (mine took 30 min).
4. When you boot into the ROM, it might be very laggy and the device might heat up very rapidly, it's not a problem, wait for 10min or so for the device to cool down then start using your device. It'll become smooth like butter.
HUGE THANKS TO THE DEVELOPER (@nicknitewolf) OF THIS ROM FOR KEEPING REDMI 2/ REDMI 2 PRIME ALIVE!!!!
THANKS @nicknitewolf !!!!!!!
Click to expand...
Click to collapse
Please do not use this method… I will not be supporting it. Consider using my tool here:
resize_v2_wt88047x.zip
drive.google.com
I guess it was too buried in my OP
nicknitewolf said:
Please do not use this method… I will not be supporting it. Consider using my tool here:
resize_v2_wt88047x.zip
drive.google.com
I guess it was too buried in my OP
Click to expand...
Click to collapse
Hi Nick devoloper, can you provide information or instructions how to use resizev2 tool .just need flash zip from twrp or extract zip,use some instructions to extended partitions.
Update.2---ok I got it .just flash zip.forgot above question.
nicknitewolf said:
Please do not use this method… I will not be supporting it. Consider using my tool here:
resize_v2_wt88047x.zip
drive.google.com
I guess it was too buried in my OP
Click to expand...
Click to collapse
Just asking:
I know the resize tool will make the OEM partition bigger than stock, but it's still too small for vendor image without compressed using squashfs.
Why didn't you make it to fit uncompressed vendor image altogether?
How to install digital wellbeing on mindgapps gapps.opengapp have option to download microgapp to get Google digital wellbeing.Here playstore didn't search offical Google digital welling .is their another version of mindgapps including digital wellbeing to get digital wellbeing features?
nicknitewolf said:
Thats you have resized your partitions before. You have to have the original partition layout before you are able to flash my script in OP
resize_v2_wt88047x.zip
drive.google.com
Click to expand...
Click to collapse
Nope, I never resizing my partition before.. I believe I still have the original partition layout.
This guy before me have the same error then he try the unsupported methode, while I still figure out how to pass the error on official tool.
Additional info, mine is 1/8 not 2/16 model...
ilikephones98 said:
I got the same problem as you mentioned above, please use this link and follow the methods to resize the partition:
[TWRP][AROMA][WT88047] Resize System partition Easily
With this tool is possible resize the system partition. Precautions and warnings: This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups. Increasing the size of the system will...
forum.xda-developers.com
This should resize your partition layout
Click to expand...
Click to collapse
didhiy said:
Nope, I never resizing my partition before.. I believe I still have the original partition layout.
This guy before me have the same error then he try the unsupported methode, while I still figure out how to pass the error on official tool.
Additional info, mine is 1/8 not 2/16 model...
Click to expand...
Click to collapse
@nicknitewolf
Same here too. And i used unsupported method to resize partition after failed attempts with the official one.
My device is 1/8 one.
If anyone want Gapps and try above nano for arm for andriod 11.
OpenGApps - Browse /arm/test/20210110 at SourceForge.net
OpenGApps daily releases
sourceforge.net
dabakale said:
@nicknitewolf
Same here too. And i used unsupported method to resize partition after failed attempts with the official one.
My device is 1/8 one.
Click to expand...
Click to collapse
I can’t really test the 8gb version. I would need the original partition layout. (I HAVE TO EMPHASISE TO USE THE ORIGINAL UNMODIFIED PARTITIONS BEFORE DOING THE FOLLOWING)
Import parted into recovery as per this thread: https://forum.xda-developers.com/t/wt88047-redmi-2-resize-system-partition.3612933/
Code:
./parted /dev/block/mmcblk0
u b p
Reply with the output.
EonJone said:
If anyone want Gapps and try above nano for arm for andriod 11.
OpenGApps - Browse /arm/test/20210110 at SourceForge.net
OpenGApps daily releases
sourceforge.net
Click to expand...
Click to collapse
Use MindTheGapps
nicknitewolf said:
I can’t really test the 8gb version. I would need the original partition layout. (I HAVE TO EMPHASISE TO USE THE ORIGINAL UNMODIFIED PARTITIONS BEFORE DOING THE FOLLOWING)
Import parted into recovery as per this thread: https://forum.xda-developers.com/t/wt88047-redmi-2-resize-system-partition.3612933/
Code:
./parted /dev/block/mmcblk0
u b p
Reply with the output.
Use MindTheGapps
Click to expand...
Click to collapse
@nicknitewolf
Here is my partition layout (I first reverted to stock rom by flashing through Mi flash then took this)
And the error screenshot.
Hi everyone and Happy New Year,
I am trying to open ROM_0 file created with SP Flash tool. I have tried ROM explorer 0.9.1, I have tried various option converting with simg2img and opening with 7zip but nothing has worked so far.
The file is about 100GB and it is a SP Flash tool backup of my userdata on which I have a lot of images which i need to save.
I was using Dot OS 5.2 general image and a message popped up about trying Android 12 and I have clicked on it just to get rid of it but I assume it has triggered a download. My phone crashed yesterday evening when I started the cmera app and once restarted it was in a boot loop mode stuck on the dot os logo.
So far I have tried various options unsuccessful - I have reflashed the image which I originally flashed, I have set the partitions active - a and b and reverted to the initial active one which was "a".
I have also flashed system.img (with the treble general image) but still it is in a boot loop mode.
I have just decided to flash back the super.img image from the stock and guess what - still stuck.
Flashed the stock boot.img again thinking there might be an issue with the kernel but that didn't help.
I understand that it is the case of fully flashing back the stock ROM which will lock the bootloader and delete all my userdata in order to have the phone back.
However the phone IS NOT important, the ONLY IMPORTANT thing are the images in the userdata.
I have created the backup of it straight after the boot loop appeared. Tried to read here on XDA but it is not clear what format is that file and how I can access the data on it.
Looked for a recovery partition but there is none. Potentially hidden as you can get into stock recovery via fastbootd. But the options there are only to wipe the partitions/reset.
The phone is Umidigi Bison Pro and I have been having all but troubles with it.
Any help greatly appreciated it.
Regards
s80_gad said:
Hi everyone and Happy New Year,
I am trying to open ROM_0 file created with SP Flash tool. I have tried ROM explorer 0.9.1, I have tried various option converting with simg2img and opening with 7zip but nothing has worked so far.
The file is about 100GB and it is a SP Flash tool backup of my userdata on which I have a lot of images which i need to save.
I was using Dot OS 5.2 general image and a message popped up about trying Android 12 and I have clicked on it just to get rid of it but I assume it has triggered a download. My phone crashed yesterday evening when I started the cmera app and once restarted it was in a boot loop mode stuck on the dot os logo.
So far I have tried various options unsuccessful - I have reflashed the image which I originally flashed, I have set the partitions active - a and b and reverted to the initial active one which was "a".
I have also flashed system.img (with the treble general image) but still it is in a boot loop mode.
I have just decided to flash back the super.img image from the stock and guess what - still stuck.
Flashed the stock boot.img again thinking there might be an issue with the kernel but that didn't help.
I understand that it is the case of fully flashing back the stock ROM which will lock the bootloader and delete all my userdata in order to have the phone back.
However the phone IS NOT important, the ONLY IMPORTANT thing are the images in the userdata.
I have created the backup of it straight after the boot loop appeared. Tried to read here on XDA but it is not clear what format is that file and how I can access the data on it.
Looked for a recovery partition but there is none. Potentially hidden as you can get into stock recovery via fastbootd. But the options there are only to wipe the partitions/reset.
The phone is Umidigi Bison Pro and I have been having all but troubles with it.
Any help greatly appreciated it.
Regards
Click to expand...
Click to collapse
May I'm wrong, but I guess that if you didn't give it an extension then the file doesn't have a format; when you make a backup of a partition using SP Flash tool you should give it an extension, for example userdata_backup.img will work, in some devices, for some partition the .bin extension is used.
And to restore the device to a working state without losing data you could flash the stock ROM unchecking the userdata partition and using Download only option won't re-lock your bootloader.
If actually your userdata was not overwritten you still can try a second attempt to preserve it using mtk-client, search for it in GitHub, also consider what I stated about re-flash your original ROM preserving the userdata partition.
Thanks SubwayChamp, I appreciate your comment.
I have tried .img, .bin, ext4 etc but cannot open it - I am not sure if there is another application that can convert it in a readable format or maybe if we can mount it and access the files.
I had the impression that if you flash the stock rom the bootloader is locked and you loose everything.
But thanks for your advice - I will flash everything apart from the userdata partition which is last in the order anyway. Should I select or deselect the preloader partition- will that make a difference?
Regards
Just flashed the full stock rom without the userdata partition - still stuck on the logo in a boot loop . I really need to open the userdata backup file from SP flash tool as I feel I have to do a full reset/wipe.
Any other suggestions about explorer for the sp flash dump file, please?
Regards
s80_gad said:
Just flashed the full stock rom without the userdata partition - still stuck on the logo in a boot loop . I really need to open the userdata backup file from SP flash tool as I feel I have to do a full reset/wipe.
Any other suggestions about explorer for the sp flash dump file, please?
Regards
Click to expand...
Click to collapse
No, I didn't say to change the extension now and try it in various format, unfortunately I feel that if you didn't give you the extension at the time to make a backup then the file is unreadable, what I mean is that when you make the dump through SP Flash tool you have to give to the file a name and an extension, not letting it as is offered by SP Flash tool, for example you did see the name ROM_0 or similar, but you have to give it a name and an extension, in this case userdata_backup.img would work.
Did you check mtk-client?, you can read (dump) the userdata partition through this CLI tool, and after that you can restore it at any time.
Using the download option (only) you never re-lock your bootloader.
But wait a minute, keep in mind that your device is A/b, so you have to double-try all the things, for example, if you want to flash a specific partition like boot you have to be sure in which partition you are right now BUT unfortunately you don't know which partition is the working one, so better use fastboot to flash the missed partition, target to both slots.
And what about the option to get to a custom recovery? (I guess you had it previously to flash CR Droid) either taking a backup of userdata or re-flashing the same CR Droid that was functional previously.
Thanks SubwayChamp for your reply.
So I will try to dump the userdata again then - I still haven't touched it so I hope the partition and the data on it is fine.
I assume it is that mtkclient you are referring to. Will see if I can get some time today to try the live cd first as I am on Windows at this moment.
So my device is indeed A/B - the system is on "a" and I have flashed dot os using fastbootd and overwriting the system.img within the super.img. It worked fine for about 20 days until that crash (I only assume it is due to the update - nothing else has happened that could create trouble).
Also tried to set the b partition active but didn't help so switched back to "a".
Unfortunately there is no recovery partition, from what I learned the recovery is within the boot img. I have tried to load temporary unofficial twrp - fastboot boot twrp.img - and the first step is ok, but then it crashes. so no luck to load custom recovery even temporary in order to save the userdata on sdcard.
Tried to get to the contents trough adb shell but while some directories are listed, I get access denied to the userdata - I think maybe the links are broken?
I will try with the mtk to see if I can back it up - and what I'll do is I'll flash the full stock rom including the userdata and potentially will try to flash the old userdata through fastboot or sp flash or mtk.
TBH I don't understand why the phone is still in a bootloop - can't be only because I haven't cleared the userdata?
Regards
s80_gad said:
Thanks SubwayChamp for your reply.
So I will try to dump the userdata again then - I still haven't touched it so I hope the partition and the data on it is fine.
I assume it is that mtkclient you are referring to. Will see if I can get some time today to try the live cd first as I am on Windows at this moment.
Click to expand...
Click to collapse
It works on Windows though.
s80_gad said:
So my device is indeed A/B - the system is on "a" and I have flashed dot os using fastbootd and overwriting the system.img within the super.img. It worked fine for about 20 days until that crash (I only assume it is due to the update - nothing else has happened that could create trouble).
Click to expand...
Click to collapse
The issue was originated due to the lack of the other system files that also occupy this space; vendor, odm, product (may vary depending on the device), can be fixed flashing the super.img using fastbootd again.
s80_gad said:
Also tried to set the b partition active but didn't help so switched back to "a".
Unfortunately there is no recovery partition, from what I learned the recovery is within the boot img. I have tried to load temporary unofficial twrp - fastboot boot twrp.img - and the first step is ok, but then it crashes. so no luck to load custom recovery even temporary in order to save the userdata on sdcard.
Click to expand...
Click to collapse
Yes, this device doesn't have a dedicated recovery partition, but it is placed in a tiny portion of the boot image (usually the ramdisk) you can try by flashing the TWRP image onto the boot partition (flashing, not booting only) then boot to it, do the stuff you need through TWRP, from there you could solve the bootloop. To can boot to Android again you should need to flash a boot image.
s80_gad said:
Tried to get to the contents trough adb shell but while some directories are listed, I get access denied to the userdata - I think maybe the links are broken?
Click to expand...
Click to collapse
No, it's encrypted.
s80_gad said:
I will try with the mtk to see if I can back it up - and what I'll do is I'll flash the full stock rom including the userdata and potentially will try to flash the old userdata through fastboot or sp flash or mtk.
TBH I don't understand why the phone is still in a bootloop - can't be only because I haven't cleared the userdata?
Regards
Click to expand...
Click to collapse
When you flashed a system image onto the super partition the other partitions that are set dynamically didn't find a place to be recreated or couldn't play its role, added to this, a different system image that which is contained in the super image can differ in sizes either logical and/or dynamical (virtual sized).
SubwayChamp said:
The issue was originated due to the lack of the other system files that also occupy this space; vendor, odm, product (may vary depending on the device), can be fixed flashing the super.img using fastbootd again.
Click to expand...
Click to collapse
Flashed already the original stock rom super. img and everything else apart from userdata - it doesn't work.
see below
{
"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"
}
SubwayChamp said:
Yes, this device doesn't have a dedicated recovery partition, but it is placed in a tiny portion of the boot image (usually the ramdisk) you can try by flashing the TWRP image onto the boot partition (flashing, not booting only) then boot to it, do the stuff you need through TWRP, from there you could solve the bootloop. To can boot to Android again you should need to flash a boot image.
Click to expand...
Click to collapse
Tried to flash it - it just restarts the phone straight away - in fact replaced it with sp flash tool as well which recognises only the "a" partition and flashes it there.
SubwayChamp said:
No, it's encrypted.
Click to expand...
Click to collapse
I see
SubwayChamp said:
When you flashed a system image onto the super partition the other partitions that are set dynamically didn't find a place to be recreated or couldn't play its role, added to this, a different system image that which is contained in the super image can differ in sizes either logical and/or dynamical (virtual sized).
Click to expand...
Click to collapse
I am guessing this is why I have to reflash the whole rom incl userdata in order to make the phone usable.
What I'll do is I'll try to dump userdata with mtk and then will reflash everything with the stock rom ()hopefully the phone will boot) and then will flash the dumped userdata with mtk. Hopefully that will work.
I'll see if I can somehow mount the mtk .bin file to see if I can get to the contents of it
Will have to use the live dvd as I have win 7 and python 3.9 cannot run on win 7.
EDIT: Can't start anything through the live dvd - is there any workaround for win 7 or is there a direct executable file which I can get to start the mtkclient?
Regards
Hello,
I also have an Umidigi Bison Pro that I am going to use as a daily driver. (It's a pity that it's unpopular it would be a great device for modding, it's cheap, rugged and has source code availability of the official ROM and kernel). I created a Telegram group about this phone if you want to join is https://t.me/UmidigiBisonPro
About your problem you can read this guide (it describes how to backup and extract from the file created by SP Flash Tool even the partitions that not visible such as the b slots) https://www.hovatek.com/forum/thread-21970.html
To give you an idea on my Bison Pro a total of 52 partitions were extracted.
If you have the full backup from before the bootloop (before the upgrade, when it was still working) my advice is to restore all partitions.
I consider myself a novice regarding modding but it is likely that after the upgrade the userdata partition is no longer readable.
I have read that you should not update the GSI ROMs but repeat the whole flash sequence.
I also recommend removing the forced encryption of the userdata partition (you can do this when rooting) to avoid exactly these problems where you have the partition backup but not the decryption key.
s80_gad said:
Flashed already the original stock rom super. img and everything else apart from userdata - it doesn't work.
see below
View attachment 5499133
Tried to flash it - it just restarts the phone straight away - in fact replaced it with sp flash tool as well which recognises only the "a" partition and flashes it there.
I see
I am guessing this is why I have to reflash the whole rom incl userdata in order to make the phone usable.
What I'll do is I'll try to dump userdata with mtk and then will reflash everything with the stock rom ()hopefully the phone will boot) and then will flash the dumped userdata with mtk. Hopefully that will work.
I'll see if I can somehow mount the mtk .bin file to see if I can get to the contents of it
Will have to use the live dvd as I have win 7 and python 3.9 cannot run on win 7.
EDIT: Can't start anything through the live dvd - is there any workaround for win 7 or is there a direct executable file which I can get to start the mtkclient?
Regards
Click to expand...
Click to collapse
Sorry for delay, I didn't receive any notification on this (or I didn't notice it), I hope you sorted out your issue, if not, let me know.
SubwayChamp said:
Sorry for delay, I didn't receive any notification on this (or I didn't notice it), I hope you sorted out your issue, if not, let me know.
Click to expand...
Click to collapse
I didn't received notification too on your message and I found out on profile account that the notification for new message on a thread are default disabled.
I recently had some problems and experimented with partitions.
Reducing the possible cases I think the decryption key for the userdata partition might be in these partitions: super , misc , nvdata , nvcfg , md_udc
and I noticed that if one of them is corrupted/different version the dm-verity check fails (in my case it is written on the screen) and it was necessary to reflash all partitions except userdata (I don't know if there is a faster combination, from the few tests done in this case I didn't find any)
Do you have more information about where the decryption key might be between those partitions?
I have made a brief description of the role of all the partitions encountered but I still don't know some of them:
boot_para
gz_a (/ gz_b)
md_udc
otp
spmfw_a (/ spmfw_b)
sspm_a (/ sspm_b)
teksunhw_a (/ teksunhw_b)
Werve said:
I didn't received notification too on your message and I found out on profile account that the notification for new message on a thread are default disabled.
I recently had some problems and experimented with partitions.
Reducing the possible cases I think the decryption key for the userdata partition might be in these partitions: super , misc , nvdata , nvcfg , md_udc
and I noticed that if one of them is corrupted/different version the dm-verity check fails (in my case it is written on the screen) and it was necessary to reflash all partitions except userdata (I don't know if there is a faster combination, from the few tests done in this case I didn't find any)
Do you have more information about where the decryption key might be between those partitions?
I have made a brief description of the role of all the partitions encountered but I still don't know some of them:
boot_para
gz_a (/ gz_b)
md_udc
otp
spmfw_a (/ spmfw_b)
sspm_a (/ sspm_b)
teksunhw_a (/ teksunhw_b)
Click to expand...
Click to collapse
Why do you think userdata has a decryption key? Unless the user set it in a backup done through a custom recovery or through the device itself, I don't think so, may I'm wrong, but which is your scenario?
SubwayChamp said:
Why do you think userdata has a decryption key? Unless the user set it in a backup done through a custom recovery or through the device itself, I don't think so, may I'm wrong, but which is your scenario?
Click to expand...
Click to collapse
Since the userdata partition is now usually encrypted either with FBE or FDE but once the system loads the files are readable and moveable even externally then it is clear that somehow the data has been decrypted precisely using the relevant decryption key, AES encryption usually.
So if the user has not specified any key this must be derived from the information already in the partitions from the factory.
Then by restoring the right combination of partitions the system can boot correctly by decrypting the userdata partition. Hence the tests and the report I wrote in my last post.
At the moment I was able to remove the forced encryption of the userdata partition by modifying super (specifically fstab present in the /vendor sub partition) but I would like to achieve the same systemless modification using Magisk (to be OTA compatible). Unfortunately, the options to remove dm-verity and forceencrypt have been hidden in the latest versions of Magisk to avoid problems with inexperienced uses.
Since I don't have a custom recovery on the Umidigi Bison Pro I can't force flag those options in the .magisk file so I have to find another way.
Werve said:
Since the userdata partition is now usually encrypted either with FBE or FDE but once the system loads the files are readable and moveable even externally then it is clear that somehow the data has been decrypted precisely using the relevant decryption key, AES encryption usually.
So if the user has not specified any key this must be derived from the information already in the partitions from the factory.
Then by restoring the right combination of partitions the system can boot correctly by decrypting the userdata partition. Hence the tests and the report I wrote in my last post.
At the moment I was able to remove the forced encryption of the userdata partition by modifying syper (specifically fstab present in the /vendor sub partition) but I would like to achieve the same systemless modification using Magisk (to be OTA compatible). Unfortunately, the options to remove dm-verity and forceencrypt have been hidden in the latest versions of Magisk to avoid problems with inexperienced uses.
Since I don't have a custom recovery on the Umidigi Bison Pro I can't force flag those options in the .magisk file so I have to find another way
Click to expand...
Click to collapse
Well, what I said is a different thing, the other user had a different interest than this. They did want to access to some data from a backup in a non-booting device, I referred to that, the userdata image backed up doesn't have an encryption by default, unless the user set one through a custom recovery, suppose that someone did take a backup from the userdata partition, this userdata image can be opened/readable for anyone with minimum skills and the appropriate tool.
In regard to your issue, I don't think, the userdata partition has any kind of restrictions to take OTA updates, most likely this resides in the bootloader, kernel or even a "silent/hidden" partition with no more functions than that.
As a side note, you should check some custom recoveries, specially in Xiaomi devices that easily allow taking OTA updates, for example I always can take OTA, when I use Orange Fox recovery, although I'm not interested, so I make updates manually, to be sure that all run fine.
SubwayChamp said:
Well, what I said is a different thing, the other user had a different interest than this. They did want to access to some data from a backup in a non-booting device, I referred to that, the userdata image backed up doesn't have an encryption by default, unless the user set one through a custom recovery, suppose that someone did take a backup from the userdata partition, this userdata image can be opened/readable for anyone with minimum skills and the appropriate tool.
In regard to your issue, I don't think, the userdata partition has any kind of restrictions to take OTA updates, most likely this resides in the bootloader, kernel or even a "silent/hidden" partition with no more functions than that.
As a side note, you should check some custom recoveries, specially in Xiaomi devices that easily allow taking OTA updates, for example I always can take OTA, when I use Orange Fox recovery, although I'm not interested, so I make updates manually, to be sure that all run fine.
Click to expand...
Click to collapse
The methodology I was referring to that is not OTA supported is to modify the super partition (the dynamic partition that from Android 8? contains system, vendor, product--for Project Treble) to disable the forced encryption of the userdata partition. In my case FBE (File Based Encryption) Android 11 encryption.
Even having disabled the dm-verity if you apply an OTA update the super partition is replaced with the one that does not have the modification to remove the forced encryption and from the tests I have done this refuses to read unencrypted partitions and asks to do a factory reset.
So, the userdata partition makes the OTA update problematic (it doesn't block it, but you lose your personal data).
I am sure that instead of modifying the super partition to disable encryption you can achieve the same result via Magisk and a modified boot partition.
Unfortunately despite many trials due to my inexperience with Magisk I could not do it.
I wanted to do all this to avoid problems as described in the case of this thread that is, have the userdata partition intact but not the rest to be able to describe it. But seems I must let the encryption and do a backup after every OTA update.
Werve said:
The methodology I was referring to that is not OTA supported is to modify the super partition (the dynamic partition that from Android 8? contains system, vendor, product--for Project Treble) to disable the forced encryption of the userdata partition. In my case FBE (File Based Encryption) Android 11 encryption.
Even having disabled the dm-verity if you apply an OTA update the super partition is replaced with the one that does not have the modification to remove the forced encryption and from the tests I have done this refuses to read unencrypted partitions and asks to do a factory reset.
So, the userdata partition makes the OTA update problematic (it doesn't block it, but you lose your personal data).
I am sure that instead of modifying the super partition to disable encryption you can achieve the same result via Magisk and a modified boot partition.
Unfortunately despite many trials due to my inexperience with Magisk I could not do it.
I wanted to do all this to avoid problems as described in the case of this thread that is, have the userdata partition intact but not the rest to be able to describe it. But seems I must let the encryption and do a backup after every OTA update.
Click to expand...
Click to collapse
If you want to apply an OEM vendor stock update then it is a restriction from the OEM itself, and if you want to apply a GSI based update, it's a different approach, not sure if the restriction is FBE related or if the userdata is encrypted or not but probably related to AVB.
There are some tools/scripts you should search for, that can unpack and repack super partition, maybe you find something in the ODM or product image, this is assuming that the super partition it is the culprit.
Just know that it's a nonsense that an order (script) to restore a specific partition, be placed just there, but in other partition.
You should check what the OTA update contains, try to catch the OTA update through some ADB script, then unpack it, and see inside.
Also, you can try backing up every partition, and restoring them one by one, seeing if it boots.
SubwayChamp said:
If you want to apply an OEM vendor stock update then it is a restriction from the OEM itself, and if you want to apply a GSI based update, it's a different approach, not sure if the restriction is FBE related or if the userdata is encrypted or not but probably related to AVB.
There are some tools/scripts you should search for, that can unpack and repack super partition, maybe you find something in the ODM or product image, this is assuming that the super partition it is the culprit.
Just know that it's a nonsense that an order (script) to restore a specific partition, be placed just there, but in other partition.
You should check what the OTA update contains, try to catch the OTA update through some ADB script, then unpack it, and see inside.
Also, you can try backing up every partition, and restoring them one by one, seeing if it boots.
Click to expand...
Click to collapse
I have already done these tests, not with an OTA update but with a different version of the firmware for all partitions, and set out the conclusions.
Obviously it's an OEM restriction since it left the forced FBE encryption on and the way it was created (so I guess also from AOSP) it refuses to read the userdata partition if it doesn't find it encrypted.