I want to update LineageOS and created a backup before attempting the update. Unfortunately the MD5 checksums of the the data partition files data.ext4.win000 and data.ext4.win001 don't check out. Even after several tries.
Is anyone else having this problem?
My TWRP Version is 3.1.1-0-0
seesawCharli said:
I want to update LineageOS and created a backup before attempting the update. Unfortunately the MD5 checksums of the the data partition files data.ext4.win000 and data.ext4.win001 don't check out. Even after several tries.
Is anyone else having this problem?
My TWRP Version is 3.1.1-0-0
Click to expand...
Click to collapse
Do you mean you created a backup successfully but then when you attempt restore the checksum It fails?
Or do you mean during backup?
IronRoo said:
Do you mean you created a backup successfully but then when you attempt restore the checksum It fails?
Or do you mean during backup?
Click to expand...
Click to collapse
The backup runs through without any errors.
When I tried to restore a backup about a month ago the checksum was incorrect and the restore failed. Therefore I reinstalled Lineage OS from scratch.
It was okay because the install was still quite fresh at that time anyway.
This time I wanted the verify the checksums in advance on my pc. The checksums of the boot.emmc.win and system.ext4.win files are fine.
Only the two data partition files fail to verify.
seesawCharli said:
The backup runs through without any errors.
When I tried to restore a backup about a month ago the checksum was incorrect and the restore failed. Therefore I reinstalled Lineage OS from scratch.
It was okay because the install was still quite fresh at that time anyway.
This time I wanted the verify the checksums in advance on my pc. The checksums of the boot.emmc.win and system.ext4.win files are fine.
Only the two data partition files fail to verify.
Click to expand...
Click to collapse
OK, I understand now. I ran a backup with TWRP 3.1.1-3 (tryout) & like you it ran fine. I can't really check md2 checksum at the moment as away on holiday & haven't found a good app that does md2 (tried Hash Droid but it just gives error msg even though permissions set correctly etc).
What are you using on PC to check?
IronRoo said:
OK, I understand now. I ran a backup with TWRP 3.1.1-3 (tryout) & like you it ran fine. I can't really check md2 checksum at the moment as away on holiday & haven't found a good app that does md2 (tried Hash Droid but it just gives error msg even though permissions set correctly etc).
What are you using on PC to check?
Click to expand...
Click to collapse
I'm using Hashtab which nicely integrates into the file property window in Windows.
But you could also use this command line utility which is already part of Windows:
Code:
CertUtil -hashfile C:\TEMP\MyDataFile.img MD5
seesawCharli said:
I'm using Hashtab which nicely integrates into the file property window in Windows.
But you could also use this command line utility which is already part of Windows:
Click to expand...
Click to collapse
OK, will have a look at it when get back to my PC. I've never tried it on PC. I have TWRP set to use SHA2 checksum. Have you tried that?
IronRoo said:
OK, will have a look at it when get back to my PC. I've never tried it on PC. I have TWRP set to use SHA2 checksum. Have you tried that?
Click to expand...
Click to collapse
No, I didn't know I could change the checksum algorithm. I'll try that!
Edit: I couldn't find a setting to change the checksum algorithm. Where can you set it? Maybe the option was introduced in your newer TWRP version?
seesawCharli said:
No, I didn't know I could change the checksum algorithm. I'll try that!
Edit: I couldn't find a setting to change the checksum algorithm. Where can you set it? Maybe the option was introduced in your newer TWRP version?
Click to expand...
Click to collapse
It's the last option in settings, it's partially obscured on my i9195 & I need to scroll up to see it fully (using ne0zone build from XDA thread)
IronRoo said:
It's the last option in settings, it's partially obscured on my i9195 & I need to scroll up to see it fully (using ne0zone build from XDA thread)
Click to expand...
Click to collapse
hmm, I don't seem to have as many settings as you. I don't need to scroll. I've attached a screenshot.
If the hash verification works for you I'll install your twrp version
Related
when im trying to do an advance restore data i get that message, what does this mean?
thanks
andrewt328 said:
when im trying to do an advance restore data i get that message, what does this mean?
thanks
Click to expand...
Click to collapse
If you did not rename your backup then it is possible the backup did not complete properly and the total bytes do not add up to the MD5 sum marked in the beginning of the file.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
If you did not rename your backup then it is possible the backup did not complete properly and the total bytes do not add up to the MD5 sum marked in the beginning of the file.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
is there any way to fix this?
If you have ADB set up you can try these to restore a MD5 mismatch:
http://forum.xda-developers.com/showthread.php?t=976453
http://forum.xda-developers.com/show...1271628&page=2
But they may be corrupted. Since you are trying advanced data restore only it may work.
kennyglass123 said:
If you have ADB set up you can try these to restore a MD5 mismatch:
http://forum.xda-developers.com/showthread.php?t=976453
http://forum.xda-developers.com/show...1271628&page=2
But they may be corrupted. Since you are trying advanced data restore only it may work.
Click to expand...
Click to collapse
I've also replied to past posts with that same fixing method, I think I'm going to hunt down my thread later and post it in my sig.
If it isn't corrupt, then you can also use terminal emulator if you don't want to use adb shell. Just make sure you type in 'su' first to give terminal emulator admin rights.
Sent from my SPH-D700 using XDA App
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.
Thanks... a very useful guide. Bookmarked
WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!
I keep getting "md5sum: not found"
Put this in the general android section as it works across most devices. ..
Sent from my One V
Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.
I fixed it in adb
Sent from my SPH-L710 using xda premium
Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!
thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
CWM showing different versions
-Delete-
maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out
Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app
Thank you so much. You saved my phone.
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)
plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz
ok so im having problem trying to flash C-rom series. How do i flash this rom?
There are two parts that we are suppose to download, the zip file and md5 file.
how do i go ahead and flash this?
i went to recovery mode and tried to install the zip file but didnt work, it said md5 file is missing.
are we suppose to merge those files together first? and create new zip file and then flash it?
Ive seen a lot of roms not include an md5sum. But usually they will still flash. Check the settings in recovery to make sure its not requiring it. The md5 isnt an extra file, its a value based on a hash of the file itself which is them embedded into the files properties if im not mistaken. Its done to ensure file/download integrity. Anyway, you should be able to turn it off somewhere in recovery.
DocHoliday77 said:
Ive seen a lot of roms not include an md5sum. But usually they will still flash. Check the settings in recovery to make sure its not requiring it. The md5 isnt an extra file, its a value based on a hash of the file itself which is them embedded into the files properties if im not mistaken. Its done to ensure file/download integrity. Anyway, you should be able to turn it off somewhere in recovery.
Click to expand...
Click to collapse
thanks a lot for on time reply's! yes md5 is not really required i guess after all. I was able to flash the C-rom series. thanks again!
From The Moderator Oka1 - There are no viable links in this OP therefore, I am closing
Thanks
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC6. 1.41 GB file seems to me like nougat update.
Nougat Update Here S4CQB2-to-U4EQC6
MD5 checksum : 903aa5c5f26f430133481c4a2cfcdb69
Thanks for ABD instruction @ColoMtn
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC6-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
For who may need it this is S4CQA1 to U4QC6 update. File is around 1.5 GB and MD5 is 23d4d4c58330b618001e76fc468732d9
Congratulations! Hopefully 928a will have it soon
vista1984 said:
Congratulations! Hopefully 928a will have it soon
Click to expand...
Click to collapse
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.
I just wanted to thank you for this, going to do it now!!!! This day keeps getting better and better!!!!!
norbarb said:
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC5. 1.41 GB file seems to me like nougat update.
Nougat Update Here
Thanks for ABD instruction @ColoMtn
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC5.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC5.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC5.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
Can anyone show a screen shot of the "About Device" section of the phone settings after applying this update? Thank you in advance!
Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.
ifanr said:
Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.
Click to expand...
Click to collapse
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.
norbarb said:
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.
Click to expand...
Click to collapse
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.
ifanr said:
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.
Click to expand...
Click to collapse
I post it MD5 in first post.
norbarb said:
I post it MD5 in first post.
Click to expand...
Click to collapse
Matched.I'll try some other ways to work it out.Tks.
ifanr said:
Matched.I'll try some other ways to work it out.Tks.
Click to expand...
Click to collapse
You may try removing .zip extension and try again. Sometimes works
i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip
jerrycoffman45 said:
i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip
Click to expand...
Click to collapse
Two resons :
1. corrupted file
2. file in wrong place
norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot
ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
I post it link to raw file try other one or re-download.
ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
jerrycoffman45 said:
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot
Click to expand...
Click to collapse
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.
norbarb said:
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.
Click to expand...
Click to collapse
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.
ifanr said:
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.
Click to expand...
Click to collapse
ALL WHO TRY PLEASE STOP. Seems like uploaded file got corrupted. I'm uploading once more
norbarb said:
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.
Click to expand...
Click to collapse
It's very thoughtful of you. If you have time please post it at your convenience.
Hi,
I did something wrong with my A2 Lite, i've updated the Magisk boot file from the Magisk app. Caused my phone to stop booting Android.
So i tried reflashing it with Mi Flash in EDL mode. That worked but i don't have any signal when i put a SIM in.
It shows my provider in settings so it recognizes the SIM but doesn't do anything with it.
Tried 10.0.13.0 manually and via Mi Flash = no signal
Tried 10.0.2.0 via Mi Flash = no signal
Loaded TWRP, switch A/B = no effect
Does anyone have a clue what i can do now?
Looks like the IMEI numbers are 0.
terrorsource said:
Looks like the IMEI numbers are 0.
Click to expand...
Click to collapse
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.
a1291762 said:
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.
Click to expand...
Click to collapse
Is it possible to write back the IMEI's if i have them?
terrorsource said:
Is it possible to write back the IMEI's if i have them?
Click to expand...
Click to collapse
It might be. In theory. You'd need to know the format of whatever was overwritten.
You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy ?
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).
Noam5651 said:
You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).
Click to expand...
Click to collapse
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...
terrorsource said:
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works partially!
I cannot install the latest "QPST_2.7.453" due to "Installation errors".
If i try "QPST_2.7.422" i can restore the created QCN but i cannot select "Enable Multi-SIM" and it only restores IMEI-1
nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.
terrorsource said:
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.
Click to expand...
Click to collapse
We'll I have never had an issue with losing my IMEI , the manual is not mine ,I'm glad that it worked!