My bootloader is unlocked as when I start my phone the 'lock sign' shows as unlocked lock icon.
However, when I go into developer options the 'OEM unlocking' option is not greyed out like it should be. I can toggle it on.
The mi unlock status also shows it is locked.
Is this because I removed my poco x3 from being associated with my MIUI account?
The reason being, I also have a mi 10t lite so used the same sim to unlock the bootloader but the mi 10t lite has been associated with my MIUI account as I unlocked my Poco first.
I am not logged into my MIUI account on any of the devices also.
What shall I do? My only concern is if I wanted to install a custom rom in future.
I guessing I have to unlock the Poco again and will lose all my data?
If it helps my Poco x3 is rooted.
Thanks
jinz24 said:
My bootloader is unlocked as when I start my phone the 'lock sign' shows as unlocked lock icon.
However, when I go into developer options the 'OEM unlocking' option is not greyed out like it should be. I can toggle it on.
The mi unlock status also shows it is locked.
Is this because I removed my poco x3 from being associated with my MIUI account?
The reason being, I also have a mi 10t lite so used the same sim to unlock the bootloader but the mi 10t lite has been associated with my MIUI account as I unlocked my Poco first.
I am not logged into my MIUI account on any of the devices also.
What shall I do? My only concern is if I wanted to install a custom rom in future.
I guessing I have to unlock the Poco again and will lose all my data?
If it helps my Poco x3 is rooted.
Thanks
Click to expand...
Click to collapse
You mentioned being rooted, so I will assume you have flashed a Safetynet fix as well. If you did, then these props:
Code:
ro.boot.flash.locked=1
ro.boot.verifiedbootstate=green
ro.boot.veritymode=enforcing
ro.boot.vbmeta.device_state=locked
would have been changed like above to trick the system into thinking your bootloader is locked. However, having said that, these changes are not made directly to the Bootloader, but only to Super.img.
In short, don't worry, nothing is wrong with your device and it has nothing to do with your MIUI account. Only the unlock part in developer options is spoofed so to speak
@Slim K
That's great to hear thanks mate for the explanation.
Yes you are correct, I flashed a safety net fix that says 'success, basicintergity, ctsprofile are both ticked and evaltype says 'basic'
So If I wanted to flash a custom rom, there will be no issues?
jinz24 said:
@Slim K
That's great to hear thanks mate for the explanation.
Yes you are correct, I flashed a safety net fix that says 'success, basicintergity, ctsprofile are both ticked and evaltype says 'basic'
So If I wanted to flash a custom rom, there will be no issues?
Click to expand...
Click to collapse
You would encounter no issues flashing a custom ROM, since your device is not Locked in a true sense. Having spoofed that is how Play CTS can come to pass in the first place. Using fastboot to flash anything will work normally, Using TWRP will work flawlessly as well.
If you want to check if bootloader is locked or not, you can use the command in fastboot mode:
Code:
fastboot oem device-info
The output on your PC's CLI should look like:
Code:
<bootloader> device unlocked: true
<bootloader> device critical unlocked: true
which means device is unlocked. I should also mention that long ago I noticed the same thing happened in MIUI for me (the unlock option in settings app) and here I am rocking a custom ROM, so no worries my friend.
@Slim K Thanks for all of your help, appreciate it.
A noob question but I know how to make my phone go into fastboot mode but how/what tool do I need to do the below, it is using powershell or cmd?
If you want to check if bootloader is locked or not, you can use the command in fastboot mode:
Code:
fastboot oem device-info
In addition to this, If I flash a custom rom, I know you have to format the data but does this wipe Magisk/your root access?
I have a Mi 10t Lite also, which is on stock rom, but I need to root it. It seems harder to do compared to the Poco X3 NFC.
Just a question for my knowlege...
For my Poco X3 NFC after installing TWRP I installed a .zip called 'Disable Dm-Verity-ForceEncrypt.Zip'
Do I need to do this for the Mi 10T lite?
I read up on this 'Disable Dm-Verity-ForceEncrypt.Zip' file but was just wondering if I need to do this step also.
im currently not using my mi 10t lite with an SD card in, so when trying to flash magisk also i can only put it on the internal storage which is encrypted any help?
jinz24 said:
@Slim K Thanks for all of your help, appreciate it.
A noob question but I know how to make my phone go into fastboot mode but how/what tool do I need to do the below, it is using powershell or cmd?
If you want to check if bootloader is locked or not, you can use the command in fastboot mode:
Code:
fastboot oem device-info
In addition to this, If I flash a custom rom, I know you have to format the data but does this wipe Magisk/your root access?
I have a Mi 10t Lite also, which is on stock rom, but I need to root it. It seems harder to do compared to the Poco X3 NFC.
Just a question for my knowlege...
For my Poco X3 NFC after installing TWRP I installed a .zip called 'Disable Dm-Verity-ForceEncrypt.Zip'
Do I need to do this for the Mi 10T lite?
I read up on this 'Disable Dm-Verity-ForceEncrypt.Zip' file but was just wondering if I need to do this step also.
im currently not using my mi 10t lite with an SD card in, so when trying to flash magisk also i can only put it on the internal storage which is encrypted any help?
Click to expand...
Click to collapse
here is what I know in short:
When you boot your device into fastboot mode and connect it to a windows 10 pc with an internet connection, it should automatically download and install the necessary drivers. In CMD you can type:
Code:
fastboot devices
and have an output like this:
Code:
fastboot <device unique id>
If it say unknown command, then search the internet for how to install platform-tools (I don't use windows so I can't help much in this regard).
Yes. Flashing a Custom ROM overwrites the Super.img, Which deletes the su Binary usually found in /sbin and will remove magisk entirely. Formatting /data will also delete the folder /data/adb/, which is where most of the Magisk app Scripts/modules are located and will break functionality (Magisk will prompt you to reinstall).
After Android 7.0, a feature called forward error correction (FEC) was added to dm-verity which restores corrupted memory blocks in case of boot failure. Flashing that .zip is not necessary if you followed the correct directions for flashing TWRP. Ofc your custom recovery should have been built correctly to not trigger verified boot and should "stick" (or not be overwritten by stock recovery). (I personally didn't need to flash it)
Regarding your MI 10T lite, if you can't flash magisk through a TWRP (Which is easiest and fastest), you can do it like this:
Learn how to use fastboot !!! (important!!!) (use the command fastboot --help to get list of commands)
Download your stock fastboot ROM from here. It should have the Type fastboot and is in .tgz format. (good to have on hand in case of future screw-ups). Download the same MIUI version/region or a slightly newer one.
Extract that firmware file, inside search for boot.img, then transfer that .img to your MI 10T lite device.
Download and install Magisk Manager to your device. When opening it, it'll prompt you to install magisk, Pick the option: Select and patch a file . Choose your boot.img from where you've put it.
You will get a magisk_patched.img in the root of internal storage as a result, transfer that to your PC and rename to boot.img
Connect your device in fastboot mode and flash the patched boot.img by openning a CMD inside that folder and using:
Code:
fastboot flash boot boot.img
Done!!!
The above process works for every device as long as you have a stock boot.img on hand. Hope I helped clarify some things for you.
@Slim K Wow, thanks mate you are a legend!
Very, very helpful and most important I understand what you mean.
I just have two last questions that have been bugging me:
I was using my mi 10t lite with an SD card in, so when i tried to flash magisk via twrp I could put the magisk.zip files, etc in the sd storage which is fine, however it was an issue when putting files on the internal storage as it was encrypted for some reason even though I have not PIN/fingerpint set up.
My main concern is, every time I went in to 'internal storage' that data shows as encrypted. So I boot into twrp go to wipe>format the data>reboot and do my phone setup again but how can I make it where every time I go into twrp>install>internal storage the data is no longer encrypted for when I want to flash other files such as custom roms in future? I hope that makes sense.
2. I have the Poco X3 on Android 10 and the Mi 10t lite on Android 11, both on stock MIUI roms (EEA) and both phones are now rooted (thanks to you). Do you know of any backup software so I can simply copy my setup from my Poco X3 to my mi 10 lite? Well most settings like apps, app data, system settings, etc
I was worried about the phones being on Android 11 and 10 as well as different roms.
I did hear about titanium backup but not sure if it's still good these days.
My Poco X3 is set up to exactly how I want it, however my mi 10t lite is literally on stock rom and rooted, no apps, settings, etc are on there atm. I just do not want to do it all manually again. As both phones are now rooted I though they may be something out there to help me with copying the data from one phone to the other.
Much appreciated for your help.
jinz24 said:
@Slim K Wow, thanks mate you are a legend!
Very, very helpful and most important I understand what you mean.
I just have two last questions that have been bugging me:
I was using my mi 10t lite with an SD card in, so when i tried to flash magisk via twrp I could put the magisk.zip files, etc in the sd storage which is fine, however it was an issue when putting files on the internal storage as it was encrypted for some reason even though I have not PIN/fingerpint set up.
My main concern is, every time I went in to 'internal storage' that data shows as encrypted. So I boot into twrp go to wipe>format the data>reboot and do my phone setup again but how can I make it where every time I go into twrp>install>internal storage the data is no longer encrypted for when I want to flash other files such as custom roms in future? I hope that makes sense.
2. I have the Poco X3 on Android 10 and the Mi 10t lite on Android 11, both on stock MIUI roms (EEA) and both phones are now rooted (thanks to you). Do you know of any backup software so I can simply copy my setup from my Poco X3 to my mi 10 lite? Well most settings like apps, app data, system settings, etc
I was worried about the phones being on Android 11 and 10 as well as different roms.
I did hear about titanium backup but not sure if it's still good these days.
My Poco X3 is set up to exactly how I want it, however my mi 10t lite is literally on stock rom and rooted, no apps, settings, etc are on there atm. I just do not want to do it all manually again. As both phones are now rooted I though they may be something out there to help me with copying the data from one phone to the other.
Much appreciated for your help.
Click to expand...
Click to collapse
so when looking at your internal storage in TWRP you see a bunch of folders with random long stringed names? if you do, then try these:
Try setting a simple pin for your lock screen, maybe "0000" and boot to TWRP. It should ask you at the start to decrypt Data partition.
If you type adb devices while in TWRP through your PC and it is enabled, then try this command:
Code:
adb shell "recovery --set_encrypted_filesystem=off"
to disable encryption in recovery. Maybe that'll work (used to work on A9 devices and lower) or try that command while booted to system.
If the above doesn't work then your TWRP may have issues retrieving keystore and cannot mount data correctly. In that case I apologize as I can't help you further.
Titanium backup supports up to A10, but A11 is also backwards compatible with A10 apps and the /data partition layout is not very different, so it should theoretically work. My personal fav method of backup and restore is using Migrate, but I have only tried it on custom ROMs.
jinz24 said:
@Slim K Wow, thanks mate you are a legend!
Very, very helpful and most important I understand what you mean.
I just have two last questions that have been bugging me:
I was using my mi 10t lite with an SD card in, so when i tried to flash magisk via twrp I could put the magisk.zip files, etc in the sd storage which is fine, however it was an issue when putting files on the internal storage as it was encrypted for some reason even though I have not PIN/fingerpint set up.
My main concern is, every time I went in to 'internal storage' that data shows as encrypted. So I boot into twrp go to wipe>format the data>reboot and do my phone setup again but how can I make it where every time I go into twrp>install>internal storage the data is no longer encrypted for when I want to flash other files such as custom roms in future? I hope that makes sense.
2. I have the Poco X3 on Android 10 and the Mi 10t lite on Android 11, both on stock MIUI roms (EEA) and both phones are now rooted (thanks to you). Do you know of any backup software so I can simply copy my setup from my Poco X3 to my mi 10 lite? Well most settings like apps, app data, system settings, etc
I was worried about the phones being on Android 11 and 10 as well as different roms.
I did hear about titanium backup but not sure if it's still good these days.
My Poco X3 is set up to exactly how I want it, however my mi 10t lite is literally on stock rom and rooted, no apps, settings, etc are on there atm. I just do not want to do it all manually again. As both phones are now rooted I though they may be something out there to help me with copying the data from one phone to the other.
Much appreciated for your help.
Click to expand...
Click to collapse
1. If u have problem to decrypt ur internal storage in TWRP is because u use an old version of TWRP. Flash a newer version like TWRP by brigudav or flash OrangeFox recovery beta (search them in this thread https://forum.xda-developers.com/f/xiaomi-poco-x3-nfc-guides-news-discussion.11529/).
2. To transfer apps and others from Poco to M10 u can try Mi Mover app. I never use it, to be honest, but as I can see, this app could be what u want.
Related
Hey all,
I unlocked bootloader, installed TWRP and installed Magisk just fine.
As far as I was aware, I had disabled encryption on the sdcard, and this makes sense as I flashed Magisk from its installation zip in my sdcard.
However, I just rebooted to recovery in order to make a backup
It prompts me to input password in order to decrypt data.
I don't need to input password, I can click cancel and get to TWRP, but then, using its file manager, I see that all file names are in gibberish. Obviously the personal data Partition is also read only
I don't know how it got encrypted, and it was after I installed Magisk from sdcard, showing it was not encrypted at some point.
Well I can't make a TWRP back in this state.
Anyone know how it got encrypted again and how to undo that so I can make backups?
for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.
Ajaykumar21066 said:
for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.
Click to expand...
Click to collapse
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone. ?
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs
drakenabarion said:
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone.
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
only change was you didnt have any lockscreen pin setup on your phone, And now you have one i think. its the same pin twrp is asking for.
Ajaykumar21066 said:
only change was you didnt have any lockscreen pin setup on your phone, And you have one i think. its the same pin twrp is asking for.
Click to expand...
Click to collapse
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison! ??
Sent from my OnePlus 6 using XDA Labs
drakenabarion said:
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.
Ajaykumar21066 said:
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.
Click to expand...
Click to collapse
The important thing for me now is that I have a stable backup. It can take me days to setup a new phone to my comfortable default setting, so now I feel secure that I have a saved image of my idea of a good install. So thank you for helping with that!
But it will be interesting to see how custom roms not based on OOS will be.
Up until my last phone (Honor 6x - proprietary soc, therefore limited rom support), I would flash a custom rom ASAP (typically LineageOS or before that, CyanogenMod). But I already get that kind of experience (with good historical reasons I guess) from OOS. It would take a bit to tempt to flash something else. ?
Sent from my OnePlus 6 using XDA Labs
And might I just say that woohoo for large storage! My previous 32gb phone took 10 gb for firmware and left me struggling after installing a normal set of apps, typically leaving me about 10gb to put music etc into. My backup that I just made took 18gb, because I installed alot of games I couldn't before, is bigger in general than base free space before!
I was frustrated by the huawei encryption and decided to get rid of it once and for all.
At first I faced many bootloops but i finally figured out what was going on. Formatting user data through TWRP is not enough because after booting the device, encryption is still there. This happens because the kernel encrypts the device when booting up. Simply modifying the boot.img file to remove file encryption also doesn't work because you still boot into an already encrypted stock user data. So the answer was pretty obvious by now.
The trick is to format data using TWRP AND THEN boot to bootloader to flash a modified boot without encryption. So let's get to it.
How to create a modified boot.img without file encryption/dm-verity
1. Find and download your current firmware from Huawei Firmware Finder Dtabase (Team MT), or from a source that you trust. (Using a firmware with different cust version or a different update will most likely not work).
2. Download Huawei Update Extractor and use it to extract the stock boot.img file from UPDATE.APP
3. Download ASSAYYED_KITCHEN.
4. Place your stock boot.img file in the "WORK" folder of ASSAYYED_KITCHEN.
5. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 1st one (Unpacking Kernel).
6. The ASSAYYED options don't work for me so i did it manually. Go to your work folder and open the folder boot_unpacked\ramdisk.
7. You will see a file named "fstab.qcom", open it using WordPad.
8. Find the line:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryption
and delete ",fileencryption".It should now look like that:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check
9. (This step is optional,follow it only if you also want dm-verity removed) Use the same method to remove dm-verity.
Code:
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/product /product ext4 ro,barrier=1 wait, verify
(Just delete the ",verify" part.)
10. Save the file.
11. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 2nd one (Packing Kernel).
12. Follow the instructions below to properly flash your modified boot.img and get rid of encryption.
Removing file encryption/dm-verity from the device
1. Unlock your device.
2. Flash this TWRP on AGS-W09 or the appropriate custom recovery for your device.
3. Boot to TWRP and FORMAT user data (note that it is very important to format data and not just wipe it). •WARNING• this will delete all your data!
4. Go back to the reboot menu of TWRP and select reboot booloader (it's important to not allow your device to boot into system yet).
5. Using fastboot, flash your modified boot.img that you created earlier.
6. Reboot your device (you might get a bootloop on the first boot but force rebooting your device again by holding the power button will fix that).
7. After booting up, your device should not be encrypted anymore.
8. You can now use the root method that you like to root your device and internal storage should be visible on TWRP. TWRP backup should also work normally.
How to fix Magisk modules not showing up on Magisk Manager (! /data/adb/magisk_merge.img mount failed error)
I am not going to get into the technical staff you can find more info here
Edit: As of Magisk 19.0, the following method becomes obsolete. Magisk modules should now work as expected without issues. This method now concerns those who want to stick to an older version of Magisk
1. Download f2fsfix-2018.9.2.zip provided by VR25 on the thread above.
2. Download all the magisk modules that you need to flash and place them on your device.
3. Download the latest Magisk uninstaller along with the latest installer.
4. Boot to TWRP and flash Magisk uninstaller. (If you don't have Magisk already installed, skip this step)
5. Wipe Davlik Cache.
6. Install the latest Magisk.
7. Wipe Davlik Cache.
8. Flash the "f2fsfix-2018.9.2.zip" immediately followed by your modules.
9. Reboot (it should take more than usual).
10. Open Magisk Manager and check your Modules. Hopefully they'll show as installed and function correctly.
Note: This method should also work on similar devices. Just make sure you know how to recover your device in case something goes wrong.
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
TRS_80 said:
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
Click to expand...
Click to collapse
Glad it worked for you. Yes this is the downside. The device already comes with an encrypted userdata, so it needs to be formatted. So anything you do before that becomes obsolete. That's why this procedure is much more convenient when it happens after the unlock,when the userdata is wiped by the stock recovery to get a stock condition.
AGS-L09 LTE
I just followed your detailed guide to my tablet and finished all the processes perfectly.
Working..Twrp, Magisk, removed encryption & verify from boot.img and from Data successfully.
A big THANKS for your guide, links and trick all in one post!!!!.
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
mr_fingy said:
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
Click to expand...
Click to collapse
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device here. If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Thanostsak said:
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device . If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Click to expand...
Click to collapse
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
mr_fingy said:
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
Click to expand...
Click to collapse
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Thanostsak said:
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Click to expand...
Click to collapse
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
mr_fingy said:
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
Click to expand...
Click to collapse
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Thanostsak said:
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Click to expand...
Click to collapse
On it now before work
Extracted stock_boot_(IDremoved).img.gz which contains the img
Will run your guide against this img
---------- Post added at 09:20 AM ---------- Previous post was at 08:33 AM ----------
All done. Nice and easy
No issues other than sweaty palms on Huawei long boot screen after flash :silly:
No reboot loop and no Magisk errors
Much appreciated for the help
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
mr_fingy said:
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
Click to expand...
Click to collapse
Great! If you need anything feel free to ask.
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
TimYuan said:
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
Click to expand...
Click to collapse
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
VR25 said:
Those getting everything broken after a second reboot, try the following workaround...
After the first reboot (right after installing), remove </sbin/.core/img/f2fs*bla*bla/service.sh>, </data/adb/magisk_merge.img> and </cache/magisk_merge_.img>.
Note that after doing this, you'll only be able to install modules and update Magisk from TWRP.
Click to expand...
Click to collapse
Thanostsak said:
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
Click to expand...
Click to collapse
It works!!! You are my hero!
TimYuan said:
It works!!! You are my hero!
Click to expand...
Click to collapse
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Thanostsak said:
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Click to expand...
Click to collapse
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
an-_-dro said:
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
Click to expand...
Click to collapse
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Thanostsak said:
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Click to expand...
Click to collapse
encryption is not a problem. since the first place already done with that data partition.
my problem is system partition, every time i made a change to system (for example deleting chrome.apk), something triggered that makes my system weird (magisk forceclose, all file manager become malfunction because system become read only). something lock my system partition if system change.
i thought change fstab.qcom <mnt_flags and options> ro,errors=panic to >> errors=continue (deleting ro/read only) will change my system behaviour, but it's not
Hi,
Finally I had time to finish my work on Xcover 4. I couldn't disable ForceEncryption by any flashable tool so I prepared 2 version of firmware (Oreo and Pie), both prerooted (Magisk) and free from Force Encryption. Everything except boot.img left untouched, both ROMs are BTU so no brand.
Just flash it with Odin 3.13.3. I recommend to flash CSC_BTU instead of HOME_CSC_BTU. HOME BTU should work as well but then probably You gonna have to format data with TWRP. CSC_BTU is already tested and there are no problems with Encryption.
After flashing just install Lastest Magisk Manager. SafetyNet Passed.
Oreo: G390FXXU4BSB3_BTU_G390FBTU4BSC1_Patched_By_Chamelleon
Code:
https://mega.nz/#!ONoFTIhD!rBOhDR0j874zpyeLiDVwfwOcodRi5OhdxyF0ZTRMslE
PIE: G390FXXU4CSF9_BTU_G390FBTU4CSFA_Patched_by_Chamelleon
Code:
https://mega.nz/#!XBhnRCCY!_IOOtXcLsGZQfVY17JD4YxxzaAWJqy2NoxVSrsJRs5M
If You need TWRP (not necessary to flash this ROMs) flash this version:
TWRP: TWRP-3.1.1_SM-G390F_by_nemo-nemo
Code:
https://mega.nz/#!DIo1SSBT!w4dPPAF3BEcfQmsy7mANO33Lb5Gj4jzDkrrPfbH56uo
Working on both versions, Oreo and Pie. I didn't test backup and recovery options but flashing is working on both. ADB and MTP are not working.
To remove Security Log Agent notifications use SecurityLogAgent Disable. It will disable this annoying app completely.
Hello!
Can you explain because i would like only to root my phone in oreo 8.1 without losing apps and data. Is it possible with your method?
thank you for your answer.
Would anyone happen to know if I can use TWRP for SM-G390F's on SM-G390W's? (the only differences I know of between them are the supported LTE frequencies)
You can try to flash it, just backup your data and if something goes wrong just flash it with back with stock firmware.
Updated main thread
Hi mates
very interesting matter. Will like to make it from a ubuntu 18.04 system? Did someone had tried it ?
Yea, it's a normal ROM so you can flash it with Heimdal.
Chamelleon said:
Yea, it's a normal ROM so you can flash it with Heimdal.
Click to expand...
Click to collapse
thank you C for this fast answer .
Here is the second point :
IS this rom free from google , I mean enough
And the third
any visible amelioration from the XCOV 2 Model in battery standing . I do not care about photos for my purpose .
Only memory, increased by SD, and lasting time
It's completely stock rom without any modifications except integrated Magisk and disabled force encryption. Rest is untouched.
I don't understand what file I should use to flash with Odin.. in the link you posted sends to a download of a zip file of almost 2gb in which there are many files, so from those files which one should I set in Odin?
Flash it like any other stock ROM:
BL file in BL
AP file in AP
CP file in CP
CSC_BTU file in CSC
Everything works great:]
Thanks man.
Hi Chamelleon and thanks for all the effort you've made already!
I successfully flashed the Pie variant of the two ROMs and got it to work. However, turned out that in an app that I'm developing, for some reason, when my device is equipped with G390FXXU4CSF9_BTU_G390FBTU4CSFA, the app doesn't behave in the same way as when G390FXXU4CSF9_ G390FXEO4CSFA has been installed. That's why I would like to be able to root the XEO-version of the firmware. Moreover, there will be many other non-rooted devices equipped with the XEO-version using the app in the near future.
Having flashed my device with G390FXXU4CSF9_ G390FXEO4CSFA, I tried installing the version of TWRP you have provided but I can't figure out how to install Magisk from there. By default, TWRP can't find the Magisk zip-file that I push onto the device. I tried formatting data, as per this post. The post lead me to believe that the files could be found after formatting but even though there were now plenty of TWRP-related folders, I couldn't find the zip. And as ADB and MTP don't seem to work in recovery mode, I'm unable to get the zip file on board after formatting. Booting to system doesn't work either after allowing modifications for TWRP, which might be due to dm-verity preventing boot, but franky I don't understand much of that topic.
You mentioned that you couldn't disable Force Encryption with any flashable tool. Is that the reason why TWRP (or any other tool) couldn't reach the zip file for Magisk?
This is the first time I've attempted rooting a phone so my knowledge regarding the topic is pretty basic.
So I suppose preparing a prerooted and Force Encryption free version of the firmware might be a possibility? I have no idea how to patch a ROM though. Any advice on how to proceed?
Hi, I had no time to play with this during Christmas. If you send me your boot.img I can modify it for you. If You just flash magisk with TWRP it will root your phone but after first reboot whole data partition will be encrypted again and you wont be able to flash anything with twrp or modify data partition without full wipe. For some unknown reason this and probably more Samsung models have different structure of files responsible for encryption and because of this none of pre-made patches are working. Only manual kernel modification can safe from encryption, at least for now.
I'm not a developer so I don't know how to prepare patch for this to allow anyone to flash it, I just found few lines of code in kernel You need to modify to disable encryption.
Chamelleon said:
Hi, I had no time to play with this during Christmas. If you send me your boot.img I can modify it for you. If You just flash magisk with TWRP it will root your phone but after first reboot whole data partition will be encrypted again and you wont be able to flash anything with twrp or modify data partition without full wipe. For some unknown reason this and probably more Samsung models have different structure of files responsible for encryption and because of this none of pre-made patches are working. Only manual kernel modification can safe from encryption, at least for now.
I'm not a developer so I don't know how to prepare patch for this to allow anyone to flash it, I just found few lines of code in kernel You need to modify to disable encryption.
Click to expand...
Click to collapse
Hi, I really appreciate the help!
I sent the boot.img to your paypal donation email. Let me know if you want me to send it to you some other way.
How to flash firmware on linux?
I know that i have to use heimdall but how to load these files into the program because filenames say basically nothing to me.
Thanks in advance.
Also does it delete user data?
SpurguX said:
Hi, I really appreciate the help!
I sent the boot.img to your paypal donation email. Let me know if you want me to send it to you some other way.
Click to expand...
Click to collapse
1. Flash clean ROM, same as boot you send me)
2. Enable OEM Unlock in Developer settings
3. Flash patched boot with Odin as AP/PDA.
4. Install Magisk Manager app
5. Install TWRP and format data partition, option where you need to type "YES"
6. Reboot system and then back to TWRP. If you can mount data and there are no errors it's done.
AndroidBroker said:
How to flash firmware on linux?
I know that i have to use heimdall but how to load these files into the program because filenames say basically nothing to me.
Thanks in advance.
Also does it delete user data?
Click to expand...
Click to collapse
Sorry but I never had a chance to use Heimdall. You can't dirty flash this because when your phone is encrypted and you can't replace kernel corrupting data.
But do I lose my data(Apps settings etc.)?
I'm OK with setting everything up back ,but it would be cool if it kept data.
(I'm going to use other computer that has windows on it btw, and I'm going to flash it with odin)
If your data partition is encrypted you gonna corrupt it by changing kernel. It means You wont be able to access, so yes, you will loose it.
What you mean by encryption some option in the Android or what?
If that's what you mean I haven't set up anything like this
In context of Oneplus 7 can anyone good soul explain me:
1. What exactly are we doing when we r using twrp?
2. What exactly we are doing when rooting?
3. Can we root without twrp?
4. Can we twrp without root
5. What is this active inactive slot
Pls could someone explain to me as a starting point
Hi,
More simply for you if you watch video on Youtube to have all your answers commented and explained...
sunandoghosh said:
In context of Oneplus 7 can anyone good soul explain me:
1. What exactly are we doing when we r using twrp?
2. What exactly we are doing when rooting?
3. Can we root without twrp?
4. Can we twrp without root
5. What is this active inactive slot
Pls could someone explain to me as a starting point
Click to expand...
Click to collapse
Well, let's answer each part:
1. When we use twrp, we're just using a different image file, which will load every custom config made by twrp team, so that we're able to do more things like install .zip or .img files into some defined partition of the device (that's just one example of the capabilities of twrp)
2. Actually the act of rooting is not the same as installing an root manager. Rooting, means we are giving the user, the capability of doing stuffs a common user couldn't. Like, installing apps as a system app, uninstalling system apps etc. I don't have all the knowledge on that matters, but I think that when you flash a root.zip file, you are adding a new binary file with some settings which will create the sudo(admin) user. When we use the root manager, we are just seeing an UI to manage which app will actually get the permission of root.
3. Yes, surely we can. All you need is to push the boot.img from your device with some adb commands(you can find it easily on XDA), install the Magisk Manager, and use the install button to patch boot image. After the process, you will se a patched_boot.img on your device storage, just put it on your PC, boot to fastboot, and fastboot boot the patched boot.img, now you can install the real magisk using the Magisk manager. There's a better tutorial here on XDA for that
4. Yes, twrp is 100% independent of root, the point is that, you will still need unlocking the BL. Also, I don't see a point to use twrp but not root, because you will not be able to do many things, like use some bank apps, play some games, use netflix etc...
5. Now the android is split in 2 slots, A and B. Imagine that when you buy the device, you have the same build (e.g. oos 10.0.5) on both slots, but you'll boot only to slot A. When you install an update, it will be installed on slot B, so that you will be forced to boot to slot B next time and all next boots (this can be reversed I think, using TWRP). So, the active slot is the one you're using, the other is inactive. When you install any kind of OTA, it will always be installed to the inactive slot, and the one you are using, will be kept as it was before the update. Remember it does not change your storage.
I don't know if that's all, and if anything's wrong, pls tell me
Hello, my poco x3 nfc (surya) bootloops and i'm very desperate.
I tried MIUI 13.0.1.0, NitrogenOS and PixelOS but they all show the poco logo , phone vibrates, after a few seconds it reboots.
Yes I obviously did format data and MIUI is the fastboot ROM, which flashes all partitions.
What do I do? TWRP works.
Solved (yes it was very fast!)
Flash persist.img from TWRP, not from fastboot
(read here) https://forum.xda-developers.com/t/...ing-flashing-custom-rom.4274891/post-85030381
Update: Flashed NitrogenOS, but modem does not start. Did I erase my IMEI? It shows up as "0" in settings.
It can read the SIM (sim vendor shows up), but it can't scan for networks.
DP FH said:
Update: Flashed NitrogenOS, but modem does not start. Did I erase my IMEI? It shows up as "0" in settings.
It can read the SIM (sim vendor shows up), but it can't scan for networks.
Click to expand...
Click to collapse
Luckily I had an EFS backup laying around
Ok so postmortem of the incident:
I restored a TWRP backup from a corrupted microSD without enabling digest verification. Obviously, this destroyed eveything on the phone, the most two important stuff being the bootloader and the EFS.
For the first one I had to pay a guy on Telegram to flash with EDL (thank you xiaomi for this very good policy).
For the second one I very luckily had, as written above, a working TWRP backup.
The only other way to restore the IMEIs is to use a Qualcomm tool, but you need to have a device-specific .qcn file (and the associated programs to change imeis in file and restore)
I couldn't find it on the Internet (for free - there are websites asking 40 USD for it!), so I decided to share my .qcn here for free.
Poco X3 NFC (surya) 6/128
DP FH said:
Ok so postmortem of the incident:
I restored a TWRP backup from a corrupted microSD without enabling digest verification. Obviously, this destroyed eveything on the phone, the most two important stuff being the bootloader and the EFS.
For the first one I had to pay a guy on Telegram to flash with EDL (thank you xiaomi for this very good policy).
For the second one I very luckily had, as written above, a working TWRP backup.
The only other way to restore the IMEIs is to use a Qualcomm tool, but you need to have a .qcn file (and the associated programs to change imeis in file and restore)
I couldn't find it on the Internet (for free - there are websites asking 40 USD for it!), so I decided to share my .qcn here for free.
Poco X3 NFC (surya) 6/128
Click to expand...
Click to collapse
Thank you, I appreciate you.