Database Info

please help a117 owners, you experiance is needed.

Hello xda friends.... im new here and i need a help from u guys. Please help mee..
i just bricked my micromax magnus a117. What i did--- rooted my phone then installed an app meteos6589 (something like that) to increase app storage. Then i restarded my phone(with usb debugging off(if it afffects anything )). And after that it is showing micromax logo only.
so anyway i downloaded stock rom v4 from mounlisky. and tried to flash with sp tools. But but but problem is arising something like "pmt didnt mathched...................." . So sp tools is saying to select and do format+download option. But i have nothing in backup only microsd and internal sd data.
So the point is i dont have backup of nvram or anything else, phone is bricked at micromx logo, usb debugging off. So how do i get my phone back to life.
anyone please....
Any detailed help is appreciated.. thank you..

so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?

ranganitesh said:
so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?
Click to expand...
Click to collapse
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.

syserr said:
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.
Click to expand...
Click to collapse
So what files are needed to be backup along with mtk droid tool, just wanna know.

ranganitesh said:
So what files are needed to be backup along with mtk droid tool, just wanna know.
Click to expand...
Click to collapse
I don't use MTKDT at all. I do see some uses for it though. SPFT is a pain, but I wish every device (SoC maker) had an SPFT so you could read or write any chunk of flash.
If you look at a scatter file you will see lots of blocks/partitions that the flash is divided into. Each of these has a purpose of course, but the one marked NVRAM (a horrible confusing name) is the most important to get backed up, it has unique "calibration data" for your specific unit. You may find a "nvram.bin" that MTKDT created... this may be exactly what SPFT would backup too... if you are lucky.
So if MTKDT made a nvram.bin that is about 100x better than having a nvram.tgz or however he archives the /data/nvram files.

[Completed] [HELP] Lenovo a606 uknown baseband/invalid imei mtk6582 nothing works

I got this phone (Lenovo A606) about a month ago with the following problems:
1) Modem (the one with the SIM card) doesn't work, status in the about section shows "invalid IMEI" and "unknown baseband". SIM card settings are greyed out in the settings.
2) Wi-fi works fine, but i always have an additional SSID in wifi menu that says 0x010 something error
According to previous owner, it went bad after bad flash or update, but he might have been lying and modem is physically dead due to some reason.
3) Serial number is also a blank
So far i've tried:
1) Flashing different stock firmwares with full flash format and DA DL flags checked/unchecked in SP Flash tool
2) Fixing nvram/trying to restore IMEI and SN through numerous tools of different versions: Maui Meta 3g, SN Writer tool, SN Station Writer tool, infinity box CM2MTK, etc - every one of tools that i've tried (i've also tried different versions of the same tools) show me different errors, best solutions online for which are "check your drivers, change usb cable or change computer" all of which i've obviously tried with the exact same result
3) Fixing nvram by deleting nvram folder in /dev/nvram
4) Replacing MP0B_001 in the nvram folder (rather putting it in, the target folder is empty after stock flashing)
5) Using nvram fixes through both custom and stock recovery menus prepared by the poor bastards like me, but with more knowledge about this stuff
6) Flashing nvram from a donor working phone through SP Flash tool
And since i'm making this post nothing of the above has worked.
So far i've came up with two possibilities:
1) The modem is physically dead and i lost in total 72 hours of my life on a goose chase. If this case is true, how can I make sure of it? Is there a low-level recovery menu or a factory mode that can confirm/deny it?
2) I'm doing something wrong and there is a simple fix for it. In this case, I ask for help guide me in the right direction, if possible with exact instructions.

fdxcd said:
I got this phone (Lenovo A606) about a month ago with the following problems:
1) Modem (the one with the SIM card) doesn't work, status in the about section shows "invalid IMEI" and "unknown baseband". SIM card settings are greyed out in the settings.
2) Wi-fi works fine, but i always have an additional SSID in wifi menu that says 0x010 something error
According to previous owner, it went bad after bad flash or update, but he might have been lying and modem is physically dead due to some reason.
3) Serial number is also a blank
So far i've tried:
1) Flashing different stock firmwares with full flash format and DA DL flags checked/unchecked in SP Flash tool
2) Fixing nvram/trying to restore IMEI and SN through numerous tools of different versions: Maui Meta 3g, SN Writer tool, SN Station Writer tool, infinity box CM2MTK, etc - every one of tools that i've tried (i've also tried different versions of the same tools) show me different errors, best solutions online for which are "check your drivers, change usb cable or change computer" all of which i've obviously tried with the exact same result
3) Fixing nvram by deleting nvram folder in /dev/nvram
4) Replacing MP0B_001 in the nvram folder (rather putting it in, the target folder is empty after stock flashing)
5) Using nvram fixes through both custom and stock recovery menus prepared by the poor bastards like me, but with more knowledge about this stuff
6) Flashing nvram from a donor working phone through SP Flash tool
And since i'm making this post nothing of the above has worked.
So far i've came up with two possibilities:
1) The modem is physically dead and i lost in total 72 hours of my life on a goose chase. If this case is true, how can I make sure of it? Is there a low-level recovery menu or a factory mode that can confirm/deny it?
2) I'm doing something wrong and there is a simple fix for it. In this case, I ask for help guide me in the right direction, if possible with exact instructions.
Click to expand...
Click to collapse
Greetings and welcome to assist. Changing IMEI numbers is illegal and can not be discussed on xda so we have to be careful. If you have the original IMEI number it may be possible to restore it with an octoplus box or something similar but we are limited to what can be discussed on xda
Regards
Sawdoctor

sawdoctor said:
Greetings and welcome to assist. Changing IMEI numbers is illegal and can not be discussed on xda so we have to be careful. If you have the original IMEI number it may be possible to restore it with an octoplus box or something similar but we are limited to what can be discussed on xda
Regards
Sawdoctor
Click to expand...
Click to collapse
Never tried to change it, since there wasn't any imei in the firmware to begin with. I only fruitlessly trying to return sim functionality

Bootloader in developer options showing as locked

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.

I am in TROUBLE! Help me for GOD, Redmi 6a!!!

Anyone left with some humanity is requested to PLEASE HELP ME if you have a Redmi 6a device or know a guy with redmi 6a device.
I actually bricked my device unintentionally and did found a way to get out using SP Flash Tool, However the thing I am stuck in right now is worse than bricking a phone.
Both SIM Cards are not working. I did a lot of research and found that I need two files:
[nvdata.img] [nvram.bin]
Unfortunately I don't have any backup for this. Now what I am looking for is some kind hearted person who can take a backup of their [nvdata] [nvram] partition and give it to me and I'll replace all their data like IMEI numbers etc with my own. I have my IMEI numbers ready to be feeded. I did a lot of try using those engineering ROMS and Tools. NOTHING WORKS!
I regret my decision of jumping in something I don't know about. I want you to please have pity on me so that I don't have to live without my phone.
==============CURRENTLY ON NEGHBOURS WIFI WHO CAN CHANGE PASSWORD ANYTHIME IF HE GETS TO KNOW THAT I HAVE HIS PASSWORD BEFORE HE DOES THIS PLEASE GET ME OUT OF THIS SO THAT I CAN USE MY OWN PHONE FOR INTERNET. I AM COMPLETELY DEPENDENT ON CELLULAR DATA!===============
====YA I AM THIS MUCH POOR!!!==== NO MONEY FOR A NEW PHONE====I AM NOT STEALING ANYONE'S IMEI====PLEASE HELP!=====PLEASE HELP FOR HUMANITY

Edit : root your phone, and then follow this page https://forum.hovatek.com/thread-25458.html it worked for me

Tab E said:
Edit : root your phone, and then follow this page https://forum.hovatek.com/thread-25458.html it worked for me
Click to expand...
Click to collapse
I tried it but it still shows imei unknown. What device is your fixed mobile phone? xiaomi or some other?

IMEI gets added to mobile device when it's built. It's stored in device's /EFS and/or /NVRAM partition. If you haven't backed up this partition before you flashed a new ROM then you have lost unless the IMEI is printed on the box in which device has been delivered.

jwoegerbauer said:
IMEI gets added to mobile device when it's built. It's stored in device's /EFS and/or /NVRAM partition. If you haven't backed up this partition before you flashed a new ROM then you have lost unless the IMEI is printed on the box in which device has been delivered.
Click to expand...
Click to collapse
I have both imei numbers on the phone's box, Thank God, but the problem is how to have them working in the phone

Look inside here:
(2023) How To Change IMEI Number of Android Phones (Latest)
Latest tricks to change the IMEI number of android phones easily without rooting your android phone. so change a serial number of your android device in 2023.
itechhacks.com

Question Is it possible to save the unlock key after unlocking the bootloader?

Hello guys/girls,
After using the official "Unlock Device App" to unlock the bootloader on any of the ROG/Zen Phones (and of course, get your phone blacklisted from future OTAs and warranty), is it possible to save the key so that I can unlock the device in the future again after relocking offline so that I don't rely on the server's key generator? This would allow your phone to be unlocked indefinitely even after having the signing server going offline (let's hope this won't happen).
I am asking for this because so far I have seen two companies that probably destroyed their fanbase by shutting down their keygen servers, such as Huawei and LG, and more companies may do that in the near or far future. I hope ASUS does not go on the same path in the future.

In theory, can't you just make a full backup of all of your partitions? Worst case scenario, you would use your own images in place of any generic ones using the EDL restore software.
The only reason an EDL restore requires you to unlock again after is that you are using generic images for a stock (locked) phone.
This is, of course, theoretical. I haven't looked into the images enough to know if there is more to them than simply being stock images (with a few extras not part of regular firmware) wrapped in a low-level flash process.

twistedumbrella said:
In theory, can't you just make a full backup of all of your partitions? Worst case scenario, you would use your own images in place of any generic ones using the EDL restore software.
The only reason an EDL restore requires you to unlock again after is that you are using generic images for a stock (locked) phone.
This is, of course, theoretical. I haven't looked into the images enough to know if there is more to them than simply being stock images (with a few extras not part of regular firmware) wrapped in a low-level flash process.
Click to expand...
Click to collapse
@twistedumbrella I haven't done EDL back/restore before, but I did Clonezilla backup/restore on PC/laptop. Let's say I bought 512GB version ASUS ROG Phone 5S, wouldn't EDL backup have to backup the entire 512GB because it is encrypted (encrypted partitions are just one complete block, even if it is barely used)? Can you backup only what you used, including the unlock key, with EDL?

falhumai96 said:
@twistedumbrella I haven't done EDL back/restore before, but I did Clonezilla backup/restore on PC/laptop. Let's say I bought 512GB version ASUS ROG Phone 5S, wouldn't EDL backup have to backup the entire 512GB because it is encrypted (encrypted partitions are just one complete block, even if it is barely used)? Can you backup only what you used, including the unlock key, with EDL?
Click to expand...
Click to collapse
I probably should have been a bit more specific. I didn't mean backing up your system, boot, and data images. I meant the stuff that makes your phone your specific phone, such as your radio, bootloader, and vendor.
Anything that can be restored with an install should be left as the default to minimize the number of variables being thrown into it. Again, this is all theory. I haven't tried it with this phone, but cloning the image for a blind write is more or less the premise of a "full backup" that has been done in recovery images for years.

twistedumbrella said:
I probably should have been a bit more specific. I didn't mean backing up your system, boot, and data images. I meant the stuff that makes your phone your specific phone, such as your radio, bootloader, and vendor.
Anything that can be restored with an install should be left as the default to minimize the number of variables being thrown into it. Again, this is all theory. I haven't tried it with this phone, but cloning the image for a blind write is more or less the premise of a "full backup" that has been done in recovery images for years.
Click to expand...
Click to collapse
@twistedumbrella Can we use QFIL tool (https://qfiltool.com/), for example, to backup/restore partitions? Also, do we have the firehouse programmer for the ASUS ROG Phone 5S?