Database Info

[Q] Imei lost but i have efs.img

Hi guys
Last night i was messing with my GPS and Ndrive gave me an error saying invalid ID, after researching i found that my imei was set to unknown, a reboot solved the issue and it was with the original imei. This morning i wanted to try trinity kernel so i booted in recovery, wiped cache and installed Trinity. After boot Whatsapp gave me an error that my number was changed bla bla to try to recover bu resending me a SMS but the SMS never came and i noticed this time that my IMEI was a generic one starting with 0049.
All fine since i have a efs.img backup, but for some reason i just can't change it back. I tried to delete the efs folder with root explorer with r/w permission but outputs a error that cannot delete. I tried the many tools around but one doesn't recognize my efs.img backup and the other outputs an error about permissions.
I also tried cat /mnt/sdcard/efs.img >> /dev/block/mtdblock6
It doesn't output any error, but after reboot the IMEI is still the generic one. I really need to fix this asap because it's my only working phone available atm.
Any idea?

I have some ideas. Firstly though, can you provide any .nv.log files you have? There shouldn't be any identifiable info but check to make sure anyway. New, old, anything will help.
Otherwise, after flashing with cat, delete nv_data.bin and rename nv_data.bak to nv_data.bin. Delete all .md5 files.
I have not had any need to replace these files nor experience with lost imeis so feel free not to take my advice. There is little you can do to raise hell at this stage since you already have a backup.

Harbb said:
I have some ideas. Firstly though, can you provide any .nv.log files you have? There shouldn't be any identifiable info but check to make sure anyway. New, old, anything will help.
Otherwise, after flashing with cat, delete nv_data.bin and rename nv_data.bak to nv_data.bin. Delete all .md5 files.
I have not had any need to replace these files nor experience with lost imeis so feel free not to take my advice. There is little you can do to raise hell at this stage since you already have a backup.
Click to expand...
Click to collapse
This is the nv.log
Sun Jan 2 05:50:40 2005: No NV backup found. Create one before MD5 on.
Sun Jan 2 05:50:40 2005: NV data back-up begin.
Sun Jan 2 05:50:40 2005: nv_data.bin does not exist.
Sun Jan 2 05:50:40 2005: NV data backup stopped due to NV data size.
Sun Jan 2 05:50:40 2005: MD5 is turned on.
Sun Jan 2 05:50:40 2005: nv_data.bin does not exist.
Sun Jan 2 05:50:40 2005: default NV restored.
Sun Jan 2 06:33:41 2005: MD5 is turned off on 0
Mon Apr 18 17:35:22 2011: NV data back-up begin.
Mon Apr 18 17:35:22 2011: NV data back-up begin.
Mon Apr 18 17:35:22 2011: NV data back-uped.
Mon Apr 18 17:35:22 2011: MD5 is turned on.
Mon Apr 18 22:51:52 2011: MD5 is turned off on 0
Mon Apr 18 22:53:33 2011: NV data back-up begin.
Mon Apr 18 22:53:33 2011: NV data back-up begin.
Mon Apr 18 22:53:33 2011: NV data back-uped.
Mon Apr 18 22:53:33 2011: MD5 is turned on.
Tue Apr 19 07:00:12 2011: MD5 is turned off on 2
Tue Apr 19 12:01:21 2011: enabling MD5 automatically because it was off temporarily.
Tue Apr 19 12:01:21 2011: NV data back-up begin.
Tue Apr 19 12:01:21 2011: NV data back-up begin.
Tue Apr 19 12:01:21 2011: NV data back-uped.
Tue Apr 19 12:01:22 2011: MD5 is turned on.
Tue Apr 19 12:01:36 2011: MD5 is turned off on 0
Tue Apr 19 12:03:21 2011: NV data back-up begin.
Tue Apr 19 12:03:21 2011: NV data back-up begin.
Tue Apr 19 12:03:21 2011: NV data back-uped.
Tue Apr 19 12:03:22 2011: MD5 is turned on.
Tue Apr 19 12:04:08 2011: MD5 is turned off on 0
Tue Apr 19 12:04:50 2011: NV data back-up begin.
Tue Apr 19 12:04:50 2011: NV data back-up begin.
Tue Apr 19 12:04:50 2011: NV data back-uped.
Tue Apr 19 12:04:51 2011: MD5 is turned on.
Tue Apr 19 12:08:01 2011: MD5 is turned off on 2
Tue Apr 19 12:09:37 2011: MD5 is turned off on 0
Tue Apr 19 12:10:01 2011: NV data back-up begin.
Tue Apr 19 12:10:01 2011: NV data back-up begin.
Tue Apr 19 12:10:01 2011: NV data back-uped.
Tue Apr 19 12:10:02 2011: MD5 is turned on.
Tue Apr 19 12:16:06 2011: MD5 is turned off on 2
Tue Apr 19 12:16:14 2011: NV data back-up begin.
Tue Apr 19 12:16:14 2011: NV data back-up begin.
Tue Apr 19 12:16:14 2011: NV data back-uped.
Tue Apr 19 12:16:30 2011: MD5 is turned on.
Tue Apr 19 12:22:29 2011: MD5 is turned off on 2
Tue Apr 19 12:22:37 2011: NV data back-up begin.
Tue Apr 19 12:22:37 2011: NV data back-up begin.
Tue Apr 19 12:22:37 2011: NV data back-uped.
Tue Apr 19 12:22:52 2011: MD5 is turned on.
Click to expand...
Click to collapse
Solved the issue. Wiped the ROM in recovery and reinstalled it after deleting the efs folder.

[Q] nv_data issue

I'm having issues with my Gnex. I has posted a query regarding the same
[Q] Galaxy Nexus radio/modem failure, baseband ... - XDA Developers
The baseband stopped working on a virgin phone (except OTA updates). So I tried flashing factory images just to try my luck. What I noticed was "Unknow Baseband" IMEI null etc
I managed to get some log files after rooting I found following logs.
***********************************
[email protected]:/factory # cat nv.log
cat nv.log
Sat Jan 1 00:00:34 2000: nv_data.bin does not exist.
Sat Jan 1 00:00:35 2000: default NV restored.
Sat Jan 1 00:00:36 2000: default NV restored.
Sat Jan 1 00:12:06 2000: MD5 is turned off on 0
Fri Feb 17 00:01:15 2012: NV data back-up begin.
Fri Feb 17 00:01:16 2012: secondary NV built.
Fri Feb 17 00:01:16 2012: NV data back-uped.
Fri Feb 17 00:01:16 2012: MD5 is turned on.
Fri Feb 17 23:04:56 2012: MD5 is turned off on 0
Fri Feb 17 23:05:33 2012: NV data back-up begin.
Fri Feb 17 23:05:33 2012: secondary NV built.
Fri Feb 17 23:05:33 2012: NV data back-uped.
Fri Feb 17 23:05:33 2012: MD5 is turned on.
Sat Feb 18 08:43:12 2012: MD5 is turned off on 0
Sat Feb 18 08:44:23 2012: NV data back-up begin.
Sat Feb 18 08:44:23 2012: secondary NV built.
Sat Feb 18 08:44:24 2012: NV data back-uped.
Sat Feb 18 08:44:24 2012: MD5 is turned on.
Sat Feb 18 08:46:42 2012: MD5 is turned off on 2
Sat Feb 18 08:52:38 2012: MD5 is turned off on 0
Sat Feb 18 08:53:32 2012: NV data back-up begin.
Sat Feb 18 08:53:33 2012: secondary NV built.
Sat Feb 18 08:53:33 2012: NV data back-uped.
Sat Feb 18 08:53:33 2012: MD5 is turned on.
Sat Feb 18 08:55:20 2012: MD5 is turned off on 0
Sat Feb 18 08:55:24 2012: NV data back-up begin.
Sat Feb 18 08:55:24 2012: secondary NV built.
Sat Feb 18 08:55:24 2012: NV data back-uped.
Sat Jan 1 00:00:06 2011: NV data back-up begin.
Sat Jan 1 00:00:06 2011: secondary NV built.
Sat Jan 1 00:00:06 2011: NV data back-uped.
Sat Jan 1 00:00:06 2011: MD5 is turned on.
Sat Jan 1 00:01:02 2011: /data/radio/nv_data.bin does not exist.
[email protected]:/factory #
***********************************************************
[email protected]:/data/radio/log # cat nv.log
cat nv.log
Sun Nov 11 11:30:48 2012: /data/radio/nv_data.bin does not exist.
Sun Nov 11 11:30:48 2012: /data/radio/nv_data.bin does not exist.
Sun Nov 11 12:49:31 2012: MD5 fail. orignal md5 '84373eddf2a1617f795b1c1af650f8a
784373eddf2a1617f795b1c1af650f8a7' computed md5 '3eddf2a1617f795b1c1af650f8a7' (
rild)
Sun Nov 11 12:49:31 2012: NV restored.(GED)
[email protected]:/data/radio/log # cd ..
cd ..
[email protected]:/data/radio # cat nv_data.bin.md5
cat nv_data.bin.md5
[email protected]:/data/radio # cat /factory/.nv_dat
a.bin.md5
cat /factory/.nv_data.bin.md5
sh: cat: /factory/.nv_data.bin.md5: No such file or directory
1|[email protected]:/data/radio # cd /factory
cd /factory
******************************************************************
Any clue ?
I found in different forums that there are atleast a few who are having the same issues without doing any manual upgrade.
Thanks
Sanu

[ref] generic imei 004999010640000 fix

It took me a while to understand how the imei system woks but i think i have the gist of it now. i don't know if this works for other models but it must considering i took information from a multitude of sources to work out a solution here's what I did
Before starting this tricky set of commands please make sure your phone has the following settings:
ROOTED
HAS BUSYBOX INSTALLED
HAS EITHER ROOTEXPLORER OR ADB
YOUR PC HAS A PROPER UNIX TEXT EDITOR (NOTEPAD++ OR JEDIT)
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Ensure you have a nv.log with at least one line that looks somewhat like this:
MD5 fail. orignal md5 'XXXXXXXXXXXXXXXXXXXXXX' computed md5 'XXXXXXXXXXXXXXXXXXXXXXXXX' (rild)
where the X's are a bunch of number and letters.
Copy the good nv_data.bin, nv_data.bin.md5 and nv.log to both the sdcard and then via usb put them on your hard drive in a folder called efsbackup
(use either rootexpoler or adb shell to copy the files to the sdcard first)
Open the nv.log and look for the second sting of lines. after the words computed md5 (the first string is the md5 the phone found and the second string is the md5 it was expecting for. if the md5 it was expecting can't be found, it uses the default IMEI 004999010640000
Open nv_data.bin.m5d with a proper unix text editor (I suggest Notepad++ or jedit) and remove the sting of numbers and letters and replace it with the string from the nv.log (the second string after computed md5) and save the file
Go back to the phone and put the phone into Airplane Mode (this turns off the radio)
Copy the files nv_data.bin and nv_data.bin.m5d back to the sdcard overwirting them
Using either rootexplorer or adb shell copy the nv_data.bin and nv_data.bin.md5 back to the original folder (either /efs or /data/radio (for me it was /data/radio that did the trick))
Using either rootexplorer or adb shell ensure both files have the following attributes Owner:radio Group:radio Owner:RWX Group:R Other:R
Using adb shell type ps (this lists all the running processes) find the one that end with rild and remember the pid
Using adb shell type kill pid# where pid# is the rild process (this restarts the radio)
Go back to the phone and take the phone out of Airplane mode
Reboot the phone
Open up the dialer and dial *#06# (the universal way to get your IMEI it SHOULD be equal to the one written under the battery):good:
If you have any problems please list them below and i will do my best to solve them

Thank you for posting. Awesome!
Sent from my SGH-I897 using Tapatalk 2

Saved. My. Ass.
Thanks!

Hi,
I have this problem with my GT-N7100 where I've rooted it, flashed a ROM and somewhere along the way (I think it was when it rooted), I have lost my IMEI to this generic one. I have been following the steps but I'm a little stuck.
I have found nv_data.bin and nv.log in the /efs folder... but the nv.log doesn't have anything about a corrupted MD5?
This is my nv.log file:
Sun Jan 1 00:02:12 2012: nv data does not exist
Sun Jan 1 00:02:12 2012: md5 compute error
Sun Jan 1 00:02:12 2012: md5 compute error
Sun Jan 1 00:02:13 2012: default NV restored
Sun Jan 1 00:02:21 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:02:21 2012: 2nd NV built
Sun Jan 1 00:02:21 2012: NV data back-uped
Sun Jan 1 00:11:44 2012: check off
Tue Mar 26 17:23:05 2013: MD5 status = (OFF)
Sun Jan 1 00:00:02 2012: check off
Sun Jan 1 00:00:02 2012: MD5 status = (OFF)
Sun Jan 1 00:00:07 2012: MD5 status = (OFF)
Sun Jan 1 00:00:08 2012: MD5 status = (OFF)
Sun Jan 1 00:00:13 2012: MD5 status = (OFF)
Sun Jan 1 00:00:13 2012: MD5 status = (OFF)
Sun Jan 1 09:36:24 2012: check off
Sun Jan 1 09:36:24 2012: MD5 status = (OFF)
Sun Jan 1 09:36:29 2012: MD5 status = (OFF)
Sun Jan 1 09:36:29 2012: MD5 status = (OFF)
Sun Jan 1 09:36:34 2012: MD5 status = (OFF)
Sun Jan 1 09:36:34 2012: MD5 status = (OFF)
Wed Mar 27 14:21:54 2013: MD5 status = (OFF)
Wed Mar 27 14:21:54 2013: MD5 status = (OFF)
Wed Mar 27 14:21:55 2013: MD5 status = (OFF)
Wed Mar 27 14:21:55 2013: MD5 status = (OFF)
Wed Mar 27 14:21:59 2013: MD5 status = (OFF)
Wed Mar 27 14:21:59 2013: MD5 status = (OFF)
Wed Mar 27 14:22:18 2013: MD5 status = (OFF)
Wed Mar 27 14:22:18 2013: MD5 status = (OFF)
Wed Mar 27 14:23:47 2013: MD5 status = (OFF)
Wed Mar 27 14:23:47 2013: MD5 status = (OFF)
Wed Mar 27 14:23:57 2013: MD5 status = (OFF)
Wed Mar 27 14:23:57 2013: MD5 status = (OFF)
Wed Mar 27 14:23:58 2013: MD5 status = (OFF)
Wed Mar 27 14:23:59 2013: MD5 status = (OFF)
Wed Mar 27 14:23:59 2013: MD5 status = (OFF)
Wed Mar 27 14:24:00 2013: 2nd NV built
Wed Mar 27 14:24:00 2013: NV data back-uped
Wed Mar 27 14:24:00 2013: check on
Wed Mar 27 14:29:40 2013: check off
Wed Mar 27 14:30:05 2013: 2nd NV built
Wed Mar 27 14:30:05 2013: NV data back-uped
Wed Mar 27 14:30:05 2013: check on
Wed Mar 27 14:30:58 2013: fail - no checksum info
Wed Mar 27 14:30:58 2013: NV restored
Wed Mar 27 14:34:48 2013: OFFSET_FOR_PRESET1 writing input
Wed Mar 27 14:34:48 2013: 2nd NV built
Wed Mar 27 14:34:48 2013: NV data back-uped
Wed Mar 27 14:34:54 2013: OFFSET_FOR_PRESET2 writing input
Wed Mar 27 14:34:54 2013: 2nd NV built
Wed Mar 27 14:34:54 2013: NV data back-uped
Wed Mar 27 14:34:57 2013: OFFSET_FOR_PRESET2 writing input
Wed Mar 27 14:34:57 2013: 2nd NV built
Wed Mar 27 14:34:57 2013: NV data back-uped
Tue Jun 18 14:31:16 2013: input from cp
Tue Jun 18 14:31:16 2013: 2nd NV built
Tue Jun 18 14:31:16 2013: NV data back-uped
Tue Jun 18 19:18:19 2013: OFFSET_FOR_PRESET2 writing input
Tue Jun 18 19:18:19 2013: 2nd NV built
Tue Jun 18 19:18:19 2013: NV data back-uped
Click to expand...
Click to collapse
Any ideas?
Thanks.

readinc cuneiform
I have the same problem, my nv.log is this:
Fri Jun 21 16:54:32 2013: md5 compute error
Fri Jun 21 16:54:32 2013: md5 compute error
Fri Jun 21 16:54:32 2013: default NV restored
Fri Jun 21 16:54:59 2013: OFFSET_FOR_PRESET2 writing input
Fri Jun 21 16:54:59 2013: 2nd NV built
Fri Jun 21 16:54:59 2013: NV data back-uped
Fri Jun 21 17:07:09 2013: input from cp
Fri Jun 21 17:07:09 2013: 2nd NV built
Fri Jun 21 17:07:09 2013: NV data back-uped

Been trying to fix this damn problem for ages. I have two logs, one looks exactly like the post above, the other looks like the one OP posted but just says expected ms5 "" and then the current one. Anywhere else to find the expected one?
Thanks

If your nv.log ends with backup NV restored.(GED) that is good it mean even though the m5d didn't mach the expected md5 hash it still restored the proper IMEI. If however your nv.log end in default NV restored that is a sure indication that the default IMEI i.e 004999901064000 is in use.
With my Nexus S even though my EFS partition is corrupt I was able to restore the proper IMEI from the /data/radio partition. I suspect every Samsung model stores its NV data (i.e the IMEI and Blue Tooth Data) in different places. I have noticed if I try to flash a custom rom like CM10 over a stock rom 4.1.2 JZ054K that is when I loose my NV data.

004999010640000 IMEI on my Samsung N7100
Hi
I downgraded my phone to a previous stock samsung rom via odin, due to battery back up issue and I got this generic IMEI. I had previously used the same rom to downgrade and it all went well(unfortunately it got updated back then :silly: , so I had to downgrade again ). This time it gave me a generic IMEI 004999010640000 and I'm in a fix . My phone has been never ever rooted. I googled and somewhere, it was a mentioned that efs folder should be deleted and then a reboot would do the trick. Don't know how right that was, but I couldn't delete/move/rename the efs folder. Secondly, it shows 0 bytes and is empty.
Pls help me. Thanks in advance!
Dave

i wish this thread had been out back in the summer of 2011... i had such a hard time trying to fix this on my own and ended up just pulling a old switcharoo on bestbuy

imei
ethan_hines said:
If your nv.log ends with backup NV restored.(GED) that is good it mean even though the m5d didn't mach the expected md5 hash it still restored the proper IMEI. If however your nv.log end in default NV restored that is a sure indication that the default IMEI i.e 004999901064000 is in use.
With my Nexus S even though my EFS partition is corrupt I was able to restore the proper IMEI from the /data/radio partition. I suspect every Samsung model stores its NV data (i.e the IMEI and Blue Tooth Data) in different places. I have noticed if I try to flash a custom rom like CM10 over a stock rom 4.1.2 JZ054K that is when I loose my NV data.
Click to expand...
Click to collapse
hi my nv.log ends with backup nv restored but still 00499......should i still do this method:fingers-crossed:

zadia24 said:
hi my nv.log ends with backup nv restored but still 00499......should i still do this method:fingers-crossed:
Click to expand...
Click to collapse
Unfortunately I don't have a correct nv.log and everything is corrupted and I'm in generic IMEI. How can I fix it without efs? Is it possible to use someone else files?
I have a nand backup but after I restored it nothing changed. It seems that efs are not backed up in nand backup. Please help me. I spent more than 12 hours to fix this problem.

Bom dia amigo, não consegui encontrar nenhum arquivos com vários números e letras, exemplo xxxxxxxxxxxx. E meu log está assim:
Sun Jan 1 00:00:30 2012: no nv data
Sun Jan 1 00:00:31 2012: default Nv restored.
Sun Jan 1 00:00:31 2012: Nv created
Sun Jan 1 00:00:42 2012: item 2 written
Sun Jan 1 00:00:42 2012: Nv core done
Sun Jan 1 00:00:42 2012: Nv data backup
Sun Jan 1 00:06:29 2012: checksum off
Wed Apr 17 11:12:47 2013: current checksum status is off
Sun Jan 1 00:00:02 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:01:35 2012: current checksum status is off
Sun Jan 1 00:01:42 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 02:54:29 2012: current checksum status is off
Sun Jan 1 02:54:36 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Thu Apr 18 22:00:10 2013: current checksum status is off
Thu Apr 18 22:00:17 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:57 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:59 2013: Nv core done
Thu Apr 18 14:01:59 2013: Nv data backup
Thu Apr 18 14:01:59 2013: checksum on
Thu Apr 18 14:49:10 2013: checksum off
Thu Apr 18 14:50:06 2013: Nv core done
Thu Apr 18 14:50:07 2013: Nv data backup
Thu Apr 18 14:50:07 2013: checksum on
Thu Apr 18 14:50:09 2013: checksum off
Thu Apr 18 14:50:32 2013: Nv core done
Thu Apr 18 14:50:33 2013: Nv data backup
Thu Apr 18 14:50:33 2013: checksum on
Thu Apr 18 21:20:53 2013: item 1 written
Thu Apr 18 21:20:53 2013: Nv core done
Thu Apr 18 21:20:53 2013: Nv data backup
Thu Apr 18 21:21:02 2013: Nv core done
Thu Apr 18 21:21:02 2013: Nv data backup
Tue Jan 1 08:02:35 2013: item 2 written
Tue Jan 1 08:02:35 2013: Nv core done
Tue Jan 1 08:02:36 2013: Nv data backup
Tue Jan 1 08:02:38 2013: item 2 written
Tue Jan 1 08:02:38 2013: Nv core done
Tue Jan 1 08:02:39 2013: Nv data backup
Tue Jul 30 23:22:40 2013: Nv core done
Tue Jul 30 23:22:40 2013: Nv data backup
Fri Aug 23 13:59:45 2013: item 2 written
Fri Aug 23 13:59:45 2013: Nv core done
Fri Aug 23 13:59:45 2013: Nv data backup
Can you help me please?!
---------- Post added at 08:45 PM ---------- Previous post was at 08:39 PM ----------
Good day friends, I could not find in my Galaxy S4 any files with multiple numbers and letters, eg xxxxxxxxxxxx, just found nv_data.bin, nv_data.bin.md5 and nv.log. And so is my log:
Sun Jan 1 00:00:30 2012: no nv data
Sun Jan 1 00:00:31 2012: default Nv restored.
Sun Jan 1 00:00:31 2012: Nv created
Sun Jan 1 00:00:42 2012: item 2 written
Sun Jan 1 00:00:42 2012: Nv core done
Sun Jan 1 00:00:42 2012: Nv data backup
Sun Jan 1 00:06:29 2012: checksum off
Wed Apr 17 11:12:47 2013: current checksum status is off
Sun Jan 1 00:00:02 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:01:35 2012: current checksum status is off
Sun Jan 1 00:01:42 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 02:54:29 2012: current checksum status is off
Sun Jan 1 02:54:36 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Thu Apr 18 22:00:10 2013: current checksum status is off
Thu Apr 18 22:00:17 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:57 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:59 2013: Nv core done
Thu Apr 18 14:01:59 2013: Nv data backup
Thu Apr 18 14:01:59 2013: checksum on
Thu Apr 18 14:49:10 2013: checksum off
Thu Apr 18 14:50:06 2013: Nv core done
Thu Apr 18 14:50:07 2013: Nv data backup
Thu Apr 18 14:50:07 2013: checksum on
Thu Apr 18 14:50:09 2013: checksum off
Thu Apr 18 14:50:32 2013: Nv core done
Thu Apr 18 14:50:33 2013: Nv data backup
Thu Apr 18 14:50:33 2013: checksum on
Thu Apr 18 21:20:53 2013: item 1 written
Thu Apr 18 21:20:53 2013: Nv core done
Thu Apr 18 21:20:53 2013: Nv data backup
Thu Apr 18 21:21:02 2013: Nv core done
Thu Apr 18 21:21:02 2013: Nv data backup
Tue Jan 1 08:02:35 2013: item 2 written
Tue Jan 1 08:02:35 2013: Nv core done
Tue Jan 1 08:02:36 2013: Nv data backup
Tue Jan 1 08:02:38 2013: item 2 written
Tue Jan 1 08:02:38 2013: Nv core done
Tue Jan 1 08:02:39 2013: Nv data backup
Tue Jul 30 23:22:40 2013: Nv core done
Tue Jul 30 23:22:40 2013: Nv data backup
Fri Aug 23 13:59:45 2013: item 2 written
Fri Aug 23 13:59:45 2013: Nv core done
Fri Aug 23 13:59:45 2013: Nv data backup
Can you help me please?!

Same here
My log says nothing
Fri Aug 23 19:29:02 2013: default NV restored
Fri Aug 23 19:29:40 2013: OFFSET_FOR_PRESET2 writing input
Fri Aug 23 19:29:40 2013: 2nd NV built
Fri Aug 23 19:29:40 2013: NV data back-uped

Hi,
I have the same problem, my log doesn't contain the MD5 failure messages:
Code:
Sun Jan 1 00:02:16 2012: nv data does not exist
Sun Jan 1 00:02:16 2012: default NV restored
Sun Jan 1 00:02:24 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:02:25 2012: 2nd NV built
Sun Jan 1 00:02:25 2012: NV data back-uped
Sun Jan 1 00:08:02 2012: check off
Sun Jan 1 00:00:08 2012: check off
Sun Jan 1 00:00:02 2012: check off
Sun Jan 1 09:27:28 2012: check off
Tue Dec 4 03:45:25 2012: 2nd NV built
Tue Dec 4 03:45:25 2012: NV data back-uped
Tue Dec 4 03:45:25 2012: check on
Tue Dec 4 03:46:13 2012: check off
Tue Dec 4 03:47:36 2012: 2nd NV built
Tue Dec 4 03:47:36 2012: NV data back-uped
Tue Dec 4 03:47:36 2012: check on
Tue Dec 4 03:47:44 2012: check off
Tue Dec 4 03:47:59 2012: 2nd NV built
Tue Dec 4 03:47:59 2012: NV data back-uped
Tue Dec 4 03:47:59 2012: check on
Tue Dec 4 03:48:20 2012: fail - no checksum info
Tue Dec 4 03:48:20 2012: NV restored
Tue Dec 4 03:49:02 2012: OFFSET_FOR_PRESET1 writing input
Tue Dec 4 03:49:02 2012: 2nd NV built
Tue Dec 4 03:49:02 2012: NV data back-uped
Tue Dec 4 03:49:07 2012: OFFSET_FOR_PRESET2 writing input
Tue Dec 4 03:49:07 2012: 2nd NV built
Tue Dec 4 03:49:07 2012: NV data back-uped
Tue Dec 4 03:49:09 2012: OFFSET_FOR_PRESET2 writing input
Tue Dec 4 03:49:09 2012: 2nd NV built
Tue Dec 4 03:49:10 2012: NV data back-uped
Fri Jun 21 10:40:51 2013: input from cp
Fri Jun 21 10:40:51 2013: 2nd NV built
Fri Jun 21 10:40:51 2013: NV data back-uped
Fri Aug 30 03:11:27 2013: OFFSET_FOR_PRESET2 writing input
Fri Aug 30 03:11:28 2013: 2nd NV built
Fri Aug 30 03:11:28 2013: NV data back-uped
I checked /data/radio but there is no folder with that name. Any idea where I can find this file on SG Note2 ?
Any further advice?

ethan_hines said:
It took me a while to understand how the imei system woks but i think i have the gist of it now. i don't know if this works for other models but it must considering i took information from a multitude of sources to work out a solution here's what I did
Before starting this tricky set of commands please make sure your phone has the following settings:
ROOTED
HAS BUSYBOX INSTALLED
HAS EITHER ROOTEXPLORER OR ADB
YOUR PC HAS A PROPER UNIX TEXT EDITOR (NOTEPAD++ OR JEDIT)
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Ensure you have a nv.log with at least one line that looks somewhat like this:
MD5 fail. orignal md5 'XXXXXXXXXXXXXXXXXXXXXX' computed md5 'XXXXXXXXXXXXXXXXXXXXXXXXX' (rild)
where the X's are a bunch of number and letters.
Copy the good nv_data.bin, nv_data.bin.md5 and nv.log to both the sdcard and then via usb put them on your hard drive in a folder called efsbackup
(use either rootexpoler or adb shell to copy the files to the sdcard first)
Open the nv.log and look for the second sting of lines. after the words computed md5 (the first string is the md5 the phone found and the second string is the md5 it was expecting for. if the md5 it was expecting can't be found, it uses the default IMEI 004999010640000
Open nv_data.bin.m5d with a proper unix text editor (I suggest Notepad++ or jedit) and remove the sting of numbers and letters and replace it with the string from the nv.log (the second string after computed md5) and save the file
Go back to the phone and put the phone into Airplane Mode (this turns off the radio)
Copy the files nv_data.bin and nv_data.bin.m5d back to the sdcard overwirting them
Using either rootexplorer or adb shell copy the nv_data.bin and nv_data.bin.md5 back to the original folder (either /efs or /data/radio (for me it was /data/radio that did the trick))
Using either rootexplorer or adb shell ensure both files have the following attributes Owner:radio Group:radio Owner:RWX Group:R Other:R
Using adb shell type ps (this lists all the running processes) find the one that end with rild and remember the pid
Using adb shell type kill pid# where pid# is the rild process (this restarts the radio)
Go back to the phone and take the phone out of Airplane mode
Reboot the phone
Open up the dialer and dial *#06# (the universal way to get your IMEI it SHOULD be equal to the one written under the battery):good:
If you have any problems please list them below and i will do my best to solve them
Click to expand...
Click to collapse
Hey i have the same problem in my I9500. But i dont see the log saying MD5 fail. I am confident from you post that this is why one country's modem is working and my country's is not working. Can you tell me how to find out the MD5 my Country's modem is expecting?

What's the best/preferred method to create a backup for this issue? I tried flashing CM 10.x on my Galaxy S3 (GT-I9300) a few days ago and I had this problem. By some miracle, and after about 30 flash attempts, I got my proper IMEI back. Just in case this happens again, I want to create a suitable backup file(s) to have the option to use this "fix".

when I get my phone back from service is show that imei ...is a problem?

anyone ?

What is the significance of having the generic IMEI?
I'm hoping to hide the identity of a phone by using this. I don't want to use any DATA on A** network, but I don't want to get smashed with a Data plan just because. I just need 2G and 3G voice to work.

I wasn't able to even make phone calls when it had that generic imei.

tibuscrape - Titanium Backup archiver

Here's a new tool for use with Titanium Backup - https://github.com/cjnaz/tibuscrape. I've found this tool to be extremely useful for backing out app revs and recovering older data.
tibuscrape creates an archive of the versions of apps and their latest data files from your Titanium Backup.
Each time that you update an app on your phone, Titanium Backup normally creates a backup of the .apk file and the associated data files (.properties and .tar.gz or .xml.gz). Each successive Titanium Backup run creates new data files up to your rolling "Max backup history" setting, and after that number of runs the older .apk version and it's data files are deleted forever.
For example, I have "Max backup history" set to 4 and run the backup nightly. This means that if I update an app I only have up to four days to find out that I'd rather stay on the older version.
This is where tibuscrape comes in: tibuscrape monitors your local Dropbox or Google Drive copy of the TitaniumBackup "Remote location" backup directory and keeps an "archive" copy of every backed-up .apk version and --the latest-- data files associated with that .apk version. tibuscrape does not modify or delete any files in the TiBU backup directory.​
Code:
$ ./tibuscrape -h
usage: tibuscrape [-h] [-T TIBU_PATH] [-A ARCHIVE_PATH] [-n] [-l]
[--purge [PURGE]] [-s] [-v] [-V]
Titanium Backup Scraper
optional arguments:
-h, --help show this help message and exit
-T TIBU_PATH, --tibu-path TIBU_PATH
Path to the Titanium Backup directory.
-A ARCHIVE_PATH, --archive-path ARCHIVE_PATH
Path to the Archive directory.
-n, --dry-run Copy/delete no files.
-l, --list Print content of the Archive directory and exit.
--purge [PURGE] Keep only n most recent versions in the archive - default 3.
-s, --summary Print an operations summary.
-v, --verbose Print status and activity messages.
-V, --version Return version number and exit.
Example runs
Code:
$ ./tibuscrape -T /<path_to>/Dropbox/TiBU/ -A /<path_to>/TiBuScrapeArchive --summary
Archival transactions tally:
3 saved .apk.gz files
38 saved datafiles
35 deleted datafiles
2 skipped new datafiles (due to missing backup .tar.gz/.xml.gz file usually due to incomplete cloud sync)
Archive integrity checks tally (should all be 0, run with --verbose for more info):
0 missing .apk.gz files (Archive has .properties that references a non-existing .apk.gz)
0 missing .tar.gz/.xml.gz files (Archive has .properties but no matching .tar.gz/.xml.gz)
0 extra .apk.gz files (Archive has no associated .properties/.tar.gz datafiles)
0 extra .tar.gz files (Archive has .tar.gz but no matching .properties)
0 extra .xml.gz files (Archive has .xml.gz but no matching .properties)
0 extra datafiles (More than one datafile set for a given .apk.gz)
Archive contains backups for 76 apps with 214 total versions
Code:
$ ./tibuscrape -A /<path_to>/TiBuScrapeArchive --list
***** Archive current content and integrity checks *****
Amazon Kindle 8.14.1.0 -- Mon Jan 28 11:02:44 2019 -- d9082798a9deee56e5d392220ae2ddec -- com.amazon.kindle-20190128-175851
Amazon Shopping 18.1.0.100 -- Mon Jan 21 02:03:48 2019 -- 2b8027975f3419888e6c0e5e32d58407 -- com.amazon.mShop.android.shopping-20190121-090328
Amazon Shopping 18.2.0.100 -- Mon Jan 28 11:03:00 2019 -- 675a8939665613908ee908fadbbda99c -- com.amazon.mShop.android.shopping-20190128-180244
Bluetooth Connect and Play 3.19 -- Mon Jan 28 11:03:01 2019 -- dc8d7a66d5c2271b2fda8774ba3d1543 -- com.cp2.start.and.play.music.player-20190128-180300
Bluetooth Pairings -- Mon Jan 28 11:03:01 2019 -- none -- com.keramidas.virtual.BLUETOOTH_PAIRINGS-20190128-180301
bVNC Pro v4.0.1 -- Mon Jan 28 02:04:37 2019 -- 347ef1517f5ea7af5c0e5567ca79bc15 -- com.iiordanov.bVNC-20190128-090414
bVNC Pro v4.0.3 -- Mon Jan 28 11:03:25 2019 -- afcdaf4d8b4c670c24126ddc2c9b0edc -- com.iiordanov.bVNC-20190128-180301
b\u00b7hyve 1.7.30 -- Mon Jan 28 11:03:26 2019 -- 981f04bc7ae5b6b4ba64eaed4cdd1481 -- com.orbit.orbitsmarthome-20190128-180325
Calendar 6.0.12-224984167-release -- Thu Jan 24 02:04:35 2019 -- 7eb1f865be1747d48cb08acb5722c124 -- com.google.android.calendar-20190124-090432
Calendar 6.0.18-228718019-release -- Mon Jan 28 11:03:29 2019 -- 236fd5c0321e3fbd97d74995b8bac03e -- com.google.android.calendar-20190128-180326
CamScanner 5.9.0.20190116 -- Sun Jan 27 02:09:16 2019 -- 9a7bce8e67acd25e06385efeb3661fce -- com.intsig.camscanner-20190127-090651
CamScanner 5.9.1.20190126 -- Mon Jan 28 11:05:51 2019 -- 3fdd290f93765b1703c36ba1393fa7eb -- com.intsig.camscanner-20190128-180329
...
Google Play Books 5.0.5_RC04.227721962 -- Mon Jan 28 02:27:39 2019 -- 841e0b13dca884c33bcbec5e26cc628c -- com.google.android.apps.books-20190128-092147
...
Messages (SMS & MMS) -- Sun Oct 6 10:52:22 2019 -- none -- com.keramidas.virtual.XML_MESSAGES-20191006-174511
Plex 7.9.0.8439 -- Mon Jan 28 11:35:04 2019 -- dd229309cb03775a42a45f92b7d57b72 -- com.plexapp.android-20190128-183422
Podcast Republic 19.01.15R -- Sun Jan 27 02:37:17 2019 -- f92a636d822ea0d7fc89ce54f990d36d -- com.itunestoppodcastplayer.app-20190127-093706
Podcast Republic 19.01.28R -- Mon Jan 28 11:35:15 2019 -- 28be82cec85691945f1abe4d12418486 -- com.itunestoppodcastplayer.app-20190128-183504
...
xBrowserSync 1.4.0 -- Mon Jan 28 11:40:50 2019 -- e93715bb65db886a6c5d16b948689d9a -- com.xBrowserSync.android-20190128-184045
Archive integrity checks tally (should all be 0, run with --verbose for more info):
0 missing .apk.gz files (Archive has .properties that references a non-existing .apk.gz)
0 missing .tar.gz/.xml.gz files (Archive has .properties but no matching .tar.gz/.xml.gz)
0 extra .apk.gz files (Archive has no associated .properties/.tar.gz datafiles)
0 extra .tar.gz files (Archive has .tar.gz but no matching .properties)
0 extra .xml.gz files (Archive has .xml.gz but no matching .properties)
0 extra datafiles (More than one datafile set for a given .apk.gz)
Archive contains backups for 76 apps with 214 total versions

Anyone try this yet?

THERAJ12 said:
Anyone try this yet?
Click to expand...
Click to collapse
Apparently only me. I've been running this nightly for months. If the concept makes sense to you, give it a shot. I used it to recover an older "safe" version of CamScanner last September.

[CLOSED] Mount system.ext4 or super.img as read write Android 10+

Mod Edit
New thread is located here: https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
Mod Edit End
So I managed to successfully run the command that @topjohnwu suggested on Twitter
e2fsck -E unshare_blocks system.ext4
directly on the extracted system.ext4 image file (which was extracted from super.img using this amazing tool)
And the image still fails to be mounted as rw using the command below. Mounting as ro works just fine though.
Code:
sudo mount -t ext4 -o loop,rw system.ext4 /mnt/dir
mount: /mnt/dir: wrong fs type, bad option, bad superblock on /dev/loop18, missing codepage or helper program, or other error.
Code:
root:~# e2fsck -E unshare_blocks system.ext4
[...]
/system/lib/libpdfium.so (inode #3345, mod time Thu Jan 1 02:00:00 2009)
/system/lib/libhwui.so (inode #3260, mod time Thu Jan 1 02:00:00 2009)
/system/lib/libchrome.so (inode #3204, mod time Thu Jan 1 02:00:00 2009)
/system/lib/libbluetooth.so (inode #3184, mod time Thu Jan 1 02:00:00 2009)
/system/apex/com.android.runtime.release.apex (inode #119, mod time Thu Jan 1 02:00:00 2009)
clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
Couldn't clone file: Could not allocate block in ext2 filesystem
File /system/usr/keylayout/Vendor_054c_Product_05c4_Version_8100.kl (inode #5649, mod time Thu Jan 1 02:00:00 2009)
has 1 multiply-claimed block(s), shared with 3 file(s):
/system/usr/keylayout/Vendor_054c_Product_09cc_Version_8100.kl (inode #5653, mod time Thu Jan 1 02:00:00 2009)
/system/usr/keylayout/Vendor_054c_Product_09cc_Version_8000.kl (inode #5652, mod time Thu Jan 1 02:00:00 2009)
/system/usr/keylayout/Vendor_054c_Product_05c4_Version_8000.kl (inode #5648, mod time Thu Jan 1 02:00:00 2009)
clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
Couldn't clone file: Could not allocate block in ext2 filesystem
File /system/usr/keylayout/Vendor_054c_Product_05c4_Version_8111.kl (inode #5650, mod time Thu Jan 1 02:00:00 2009)
has 1 multiply-claimed block(s), shared with 1 file(s):
/system/usr/keylayout/Vendor_054c_Product_09cc_Version_8111.kl (inode #5654, mod time Thu Jan 1 02:00:00 2009)
clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
Couldn't clone file: Could not allocate block in ext2 filesystem
File /system/usr/keylayout/Vendor_054c_Product_09cc.kl (inode #5651, mod time Thu Jan 1 02:00:00 2009)
has 1 multiply-claimed block(s), shared with 1 file(s):
/system/usr/keylayout/Vendor_054c_Product_05c4.kl (inode #5647, mod time Thu Jan 1 02:00:00 2009)
clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
Couldn't clone file: Could not allocate block in ext2 filesystem
File /system/usr/keylayout/Vendor_054c_Product_09cc_Version_8000.kl (inode #5652, mod time Thu Jan 1 02:00:00 2009)
has 1 multiply-claimed block(s), shared with 3 file(s):
/system/usr/keylayout/Vendor_054c_Product_09cc_Version_8100.kl (inode #5653, mod time Thu Jan 1 02:00:00 2009)
/system/usr/keylayout/Vendor_054c_Product_05c4_Version_8100.kl (inode #5649, mod time Thu Jan 1 02:00:00 2009)
/system/usr/keylayout/Vendor_054c_Product_05c4_Version_8000.kl (inode #5648, mod time Thu Jan 1 02:00:00 2009)
clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
Couldn't clone file: Could not allocate block in ext2 filesystem
File /system/usr/keylayout/Vendor_054c_Product_09cc_Version_8100.kl (inode #5653, mod time Thu Jan 1 02:00:00 2009)
has 1 multiply-claimed block(s), shared with 3 file(s):
/system/usr/keylayout/Vendor_054c_Product_09cc_Version_8000.kl (inode #5652, mod time Thu Jan 1 02:00:00 2009)
/system/usr/keylayout/Vendor_054c_Product_05c4_Version_8100.kl (inode #5649, mod time Thu Jan 1 02:00:00 2009)
/system/usr/keylayout/Vendor_054c_Product_05c4_Version_8000.kl (inode #5648, mod time Thu Jan 1 02:00:00 2009)
clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
Couldn't clone file: Could not allocate block in ext2 filesystem
File /system/usr/keylayout/Vendor_054c_Product_09cc_Version_8111.kl (inode #5654, mod time Thu Jan 1 02:00:00 2009)
has 1 multiply-claimed block(s), shared with 1 file(s):
/system/usr/keylayout/Vendor_054c_Product_05c4_Version_8111.kl (inode #5650, mod time Thu Jan 1 02:00:00 2009)
clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
Couldn't clone file: Could not allocate block in ext2 filesystem
File /system/usr/share/zoneinfo/tz_version (inode #5688, mod time Thu Jan 1 02:00:00 2009)
has 1 multiply-claimed block(s), shared with 1 file(s):
/system/apex/com.android.runtime.release.apex (inode #119, mod time Thu Jan 1 02:00:00 2009)
Multiply-claimed blocks already reassigned or cloned.
File /system/usr/share/zoneinfo/tzdata (inode #5689, mod time Thu Jan 1 02:00:00 2009)
has 124 multiply-claimed block(s), shared with 1 file(s):
/system/apex/com.android.runtime.release.apex (inode #119, mod time Thu Jan 1 02:00:00 2009)
Multiply-claimed blocks already reassigned or cloned.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Failed to optimize directory /system/fonts (2249): Could not allocate block in ext2 filesystem
Failed to optimize directory /system/lib (2995): Could not allocate block in ext2 filesystem
Failed to optimize directory /system/lib/vndk-29 (3507): Could not allocate block in ext2 filesystem
Failed to optimize directory /system/lib64 (3762): Could not allocate block in ext2 filesystem
Failed to optimize directory /system/lib64/vndk-29 (4434): Could not allocate block in ext2 filesystem
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: ***** FILE SYSTEM WAS MODIFIED *****
/: ********** WARNING: Filesystem still has errors **********
/: 5704/6048 files (20.8% non-contiguous), 655526/655526 blocks

Trying to remove the shared_blocks feature from the extracted system.ext4 is not allowed using the stock tune2fs:
Code:
sudo tune2fs -f -O ^shared_blocks ./system_test.ext4
tune2fs 1.44.6 (5-Mar-2019)
Clearing filesystem feature 'shared_blocks' not supported.

I replaced all 4 occurences of these three bytes in my super.img like suggested here and flashed it to my phone.
It didn't boot probably due to the invalid sha256 checksums as predicted.
Which bytes I must hex edit in the extracted system.ext4 in order to make it rw? I was thinking maybe the shared_blocks feature?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

lol enough with the hex editing already.
Guys this is just a heads up that now there's a 1-click solution for all those enthousiasts that would like to make their Android 10+ system read-write-able again just like it used to be in Android 9 and earlier.
Tested on Xiaomi Poco X3 NFC surya and works great over here!
The solution was burried deep inside the new forum interface and was really hard to find so I decided to write this little automatic bash script for all Linux users that would like to debloat their device a bit more thoroughly.
Check it out here:
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/

Thread was closed! The account of the author of this thread has been permanently suspended. Please, I ask everybody not to promote a banned user or his website, blog, work etc. Thanks very much for your cooperation.
Regards
Oswald Boelcke
Senior Moderator