Database Users

Backing up phone before de-branding/modding

WARNING: DO NOT TRY THIS! IT'S A WORK IN PROGRESS AND WON'T WORK AT THIS STAGE!
A lot of people in this forum would like to try flashing custom ROMs or just de-branding their phone to an unbranded stock ROM but are concerned about voiding their warranty. I'm one of those.
Information on how to backup and restore back to original condition seems difficult to find so I thought I'd create a post that could be updated to form an easy-to-follow guide. There's a lot of gaps to fill in so please contribute if you can. Progress so far...
1. Backing up your original hboot, boot and recovery. I think this script should do it (modified from sfjuocekr's post /showthread.php?t=835746). Run from ConnectBot or similar terminal emulator on your phone (or ADB - just drop 'busybox' from the md5sum command):
Code:
#!/system/bin/sh
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_orig0.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_orig1.img
dd if=/dev/block/mmcblk0p21 of=/sdcard/DHD/recovery_orig0.img
dd if=/dev/block/mmcblk0p21 of=/sdcard/DHD/recovery_orig1.img
dd if=/dev/block/mmcblk0p22 of=/sdcard/DHD/boot_orig0.img
dd if=/dev/block/mmcblk0p22 of=/sdcard/DHD/boot_orig1.img
busybox md5sum /sdcard/DHD/*.img
echo ""
echo "IF THE ABOVE MD5 SUMS DO NOT MATCH"
echo "SOMETHING IS WRONG WITH YOUR BACKUP"
2. Permroot with VISIONary r12.
3. Load Clockwork MOD Recovery and make Nandroid backup. I need help with this section.
[Questions: Does it require S-OFF? Can you load the current test Clockwork recovery using 'fastboot boot' and run Nandroid from that?]
4. To restore, use the normal Nandroid restore procedure and then dd your backup files back to their original locations.
[Questions: Is it better to use 'fastboot flash boot boot.img'? I'm assuming I'll still have to use dd for the hboot and the phone will have to be in bootloader mode?]
Finally, will this work? Is this more complicated than it needs to be? Can you simply use dd to backup/restore the system and userdata partitions too?
Sorry if this is out of place. I thought I'd put in the initial effort and people who actually know what they are talking about might be so kind as to fill in the blanks.

[Recovery] RA Revamped for Iconia HC&ICS

Note 3.16 and below are for HoneyComb bootloader 3.17 & up are for ICS patched bootloader.
This is built from my forked Amon Ra recovery source.
WARNING UNLESS YOU ARE VERY FAMILIAR AND COMFORTABLE USING COMMANDLINE/TERMINAL DO NOT MESS WITH THE EXT3|EXT4 MENU. MESSING WITH THE PARTITION FORMATS CAN LEAVE YOUR ICONIA IN A STATE THAT IS UNABLE TO BOOT NORMALLY AND REQUIRES FIXING VIA COMMANDLINE. Fix for ignoring this warning is done by running "iconia_repair.sh help" from command line in recovery.
Full source for both Apache licensed recovery and GPL licensed kernel & busybox are here
Recovery Features:
Special features for acer iconia :
Touch enabled UI
Can use usb flash drive or normal sdcard as sdcard to flash roms and to use in nandroid backup/restore.
Automatically runs itsmagic on boot
External sdcard mass storage works on iconia
Automatically backs up usb serial (uuid) and the start of mmcblk0 in nandroid backup.
Will not remove /data/media unless full ext wipe option is selected (off by default)
ADB as root user
USB-MS Toggle :mounts sdcard as mass storage
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup items with [X] to restore
Nand Restore Clockwork : browse to and restore cwm backup
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse.
Toggle Signature Verify : Toggle on/off signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all (data, cache, android_secure & dalvik if outside of /data)
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe system
Wipe sdcard
Wipe .android secure : Wipes froyo+ native .android_secure on sdcard
Toggle full ext wipe: Toggles full or quick wipe of ext partitions
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (
Mounts:
Gui mounts to avoid typing in terminal to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix Permissions
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Check Battery Lvl
Ext3|4 menu: Formatting and re-formatting of partitions
Developer menu:
Make and flash boot from zImage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
Trouble Shooting:
Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log which will be on your external sdcard. It should have detailed cause of error if its not self-explainatory upload it here as an attachment and then post details about the error. Posts without the log are a complete waste of my time and will be ignored as there is no usable info to assist me in troubleshooting it. You will also be told to go visit /dev/null.
Special Thanks:
Thanks to :
Amon Ra
Koush
Sc2k for itsmagic and getuid.ko
Gweedo767 & CEnnis91 for the touch ui
Skrilax_CZ for patched ICS bootloader & setbootmode

Download Section:
To flash on HC bootloader(requires root):
run itsmagic then
Code:
adb push recovery-ra-iconia-3.13-gnm.img /sdcard
adb shell
su
dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
To flash on ICS Patched Bootloader:
fastboot flash recovery nameofrecovery.img
V3.17 Recovery flashable zip : recovery-ra-iconia-3.17-gnm.zip
ICS recovery-ra-iconia-3.17-gnm.img
md5sum e74dd63395baed6d00c724024ab2d5cc recovery-ra-iconia-3.17-gnm.img
recovery-ra-iconia-3.16-gnm.img
md5sum 357a7033171585005db89d505b6b7c65 recovery-ra-iconia-3.16-gnm.img
recovery-ra-iconia-3.15-gnm.img
md5sum f40fc8fe8708df75583338d09be33ea0 recovery-ra-iconia-3.15-gnm.img
recovery-ra-iconia-3.14-gnm.img
md5sum d69390b62dd914a440ca2ae90ff95a0a recovery-ra-iconia-3.14-gnm.img
recovery-ra-iconia-3.13-gnm.img
md5sum 292d0a37cc7971baab2b32d6dae0d74c recovery-ra-iconia-3.13-gnm.img
Flashable zip for 3.13 is here http://forum.xda-developers.com/showpost.php?p=21727826&postcount=13
Changelog 3.14 :
Added menu option to wipe flexrom and also included it in the default wipe all
Added option to flash a zip from internal storage
Added warnings on using the ext3|4 menu
Added recovery shell script called iconia_repair.sh for users that ignore the above warning and have corrupted their partitions. To use call "iconia_repair.sh help" from adb shell in recovery.
Changelog 3.15
Fixed wipe boot option on emmc devices
Fixed ext3|ext4 format menu for iconia & updated the iconia_repair.sh script to match (still may error 1st time if users used this option on 3.13 or 3.14 to format use script to repair and it will work properly from there out)
Itsmagic is now built into recovery binary
Sdcard is now unmounted after flashing a zip from it.
Changelog 3.16
Fixed nandroid restore from usb stick
Added ability to nandroid restore a cwm backup from usb stick
Changelog 3.17
Updated for ICS patched bootloader
Removed auto run of itsmagic (still there from cmd line)
Updated Mass storage in recovery to 2.6.39 kernel
Compiled setbootmode into recovery -- call setbootmode from cmd line to use
Default quick wipe and nandroid backup skips /data/linux directory if present -- toggling full ext wipe will still remove and reformat 100% of /data
Note: nandroid backup folder is changed from nvmem=* to your devices serial # so you may need to manually move old RA backups into new folder.
Updated su & superuser.apk to current

Seems cool ill try it out in am.
Sent from my HTC Inspire 4G using Tapatalk

Thanks bro. Just downloaded it. Will give it a try in the am. Off to bed!

Just gave it a quick test. Seemed to work fine (touch controls & backup). Haven't tried a restore yet, which is the true test.
Much thanks! This looks extremely promising.

just curious, being a first time venturing a little bit with my a500, how does one run "itsmagic"? i'm having issues with my windows 7 x64 pc recognizing my tablet running thor's latest ICS build 89 over adb, so would it be possible for somebody to make this as a flashable zip from the recovery i already have installed? or is that crazy... i flash new recoveries all the time for my fascinate or droid 1 in CWMR so I'm just curious. thanks!

Same here ive looked at the old its magic thread from way back and still not sure how to call it.
would some one be able to put together s CWM .zip for us to save alot of the same posts?

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push recovery-ra-i
conia-3.13-gnm.img /sdcard
1665 KB/s (5001216 bytes in 2.932s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # su
su
[email protected]:/ # dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmc
blk0p1
a-3.13-gnm.img of=/dev/block/mmcblk0p1 <
/sdcard/recovery-ra-iconia-3.13-gnm.img: cannot open for read: Not a directory
1|[email protected]:/ # sync
sync
[email protected]:/ # sudo
sudo
sh: sudo: not found
127|[email protected]:/ # su
su
[email protected]:/ # exit
exit
[email protected]:/ # ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # itsmagic
itsmagic
sh: itsmagic: not found
127|[email protected]:/ # ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push recovery-ra-i
conia-3.13-gnm.img /sdcard
1932 KB/s (5001216 bytes in 2.527s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmc
blk0p1
a-3.13-gnm.img of=/dev/block/mmcblk0p1 <
/sdcard/recovery-ra-iconia-3.13-gnm.img: cannot open for read: Not a directory
1|[email protected]:/ #
this is what i get. not a directory? Does thor's ICS have something set up differently? I'd love to get a legit recovery up in here. Thanks.
---------- Post added at 11:56 AM ---------- Previous post was at 11:43 AM ----------
just for anyone looking in, joe9002 for example, I followed the steps from here to find out you have to run the second set of command in the terminal on the tablet. much easier with a usb keyboard, i might add. got it installed and running nicely. it ain't pretty, but the touch does work. I guess i was expecting more like TWRP with big icons, but not having to use the way too recessed volume buttons is awesome. thanks guys!!!!!

please provide a flashable zip....lazy kid)

easy install
i have used acer recovery installer
http://forum.xda-developers.com/showthread.php?t=1226191

josinpaul said:
please provide a flashable zip....lazy kid)
Click to expand...
Click to collapse
+1, would someone please do a cwm flashable zip for this ?
Thank a million
Sent from my A500 using Tapatalk

If This is a .img. put on your sd card at the same place as the cwm thors recovery .. Acer Recovery installer should See and Install this.. Or am i missing something..
DO NOT TRY JUST BECAUSE I AM ASKING THIS.. But sounds logical.

I just created and tested a CWM flashable file of this image. There's one in the attachment of this post, or you can download it HERE

erica_renee said:
If This is a .img. put on your sd card at the same place as the cwm thors recovery .. Acer Recovery installer should See and Install this.. Or am i missing something..
DO NOT TRY JUST BECAUSE I AM ASKING THIS.. But sounds logical.
Click to expand...
Click to collapse
NOT logical at all!
You need a script run to install it. See post above!!!!

kjy2010 said:
I just created and tested a CWM flashable file of this image. There's one in the attachment of this post, or you can download it HERE
Click to expand...
Click to collapse
You rock! Thanks a ton, as I don't do ADB since I have too many Android devices in this house, and every time I get one connected to my desktop it breaks the connection of the others.
Now, am I reading correctly that we have to manually run itsmagic with this or does it automatically do it? I think I speak for more than just myself when I say I have no idea how or even when to do this.
Has anyone done a successful recover?

internetpilot said:
You rock! Thanks a ton, as I don't do ADB since I have too many Android devices in this house, and every time I get one connected to my desktop it breaks the connection of the others.
Now, am I reading correctly that we have to manually run itsmagic with this or does it automatically do it? I think I speak for more than just myself when I say I have no idea how or even when to do this.
Has anyone done a successful recover?
Click to expand...
Click to collapse
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it

kjy2010 said:
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
Click to expand...
Click to collapse
Oops...see that now in the OP. Thanks. Sorry, the running itsmagic as part of the install process through me for a loop. I know that I've seen Thor's CWM recovery automatically loading it, and I was worried that with this recovery we'd have to do it manually.
Alright. Maybe I'll be the guinea pig and try a restore.

kjy2010 said:
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
Click to expand...
Click to collapse
Yes itsmagic is needed to call the bootloader re-write of partition checksums. Itsmagic is executed in both my recovery and thor's on boot. To call it manually in either recovery which is not needed as its already done you would do either "itsmagic" from adb shell in recovery or from updater-script run_program("/sbin/itsmagic"); or call it in a script in a flashable zip.
internetpilot said:
Alright. Maybe I'll be the guinea pig and try a restore.
Click to expand...
Click to collapse
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.

drellisdee said:
Yes itsmagic is needed to call the bootloader re-write of partition checksums. Itsmagic is executed in both my recovery and thor's on boot. To call it manually in either recovery which is not needed as its already done you would do either "itsmagic" from adb shell in recovery or from updater-script run_program("/sbin/itsmagic"); or call it in a script in a flashable zip.
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.
Click to expand...
Click to collapse
Thanks again dell! We needed an alternative to the GPL non-compliant CWM that we had!
Your work is GREATLY appreciated and the touch screen is an added bonus!

Very nice addition to the A500, thanks for the hard work.

[Guide][NOOB-Friendly] How to share your Nandroid Backup and Modem

As we are having a lot of Jelly Bean leaks lately, a lot of users want to share the Nandroid backup to others but sometimes they make mistakes which ends up in md5 mismatches or some of them don't know how to create a share-able zip.
I have tried to create this guide to enable them in doing so. Hope this will help everyone.
Requirement:
CWM Recovery
7zip, Winrar or any file compressing tool
ADB setup in your PC
Click to expand...
Click to collapse
Once you have applied the OTA and done a factory reset, Follow the process given below:-
If your have ClockworkMod Touch Recovery 6.0.1.2 (Believe me it is easier and better in Touch recovery - Get it from here) follow these:-
In CWM Recovery
Reboot into Recovery => Hold Volume Up + Home + Power buttons together for about 5-7 seconds, release the buttons when you see the recovery menu
Choose -> Backup and Restore
Chooose -> Choose Backup Format (Optional)
Change Backup format to tar (Optional)
Choose -> Create image.zip
This will create an image.zip and an image folder in your Internal Sdcard inside the clockworkmod>backup folder
Copy the image.zip file to your PC, rename it to the software version you are sharing for e.g. GT-I9300-XXXXXXXX. Important do not put spaces in the name.
Upload this zip to whichever Filehosting site you want to share with.
*this image.zip can be flashed in CWM directly without having the need to extract the files inside*
Click to expand...
Click to collapse
If you have ClockworkMod Recovery 5.5 (Get it from here) Follow these:-
In CWM Recovery
Reboot into Recovery => Hold Volume Up + Home + Power buttons together for about 5-7 seconds, release the buttons when you see the recovery menu
Choose -> Backup and Restore
Choose -> Backup (either Internal or External SDcard by default it will backup to ExtSDcar)
Your Backup will now be there inside the clockworkmod>backup folder, Copy this folder to your PC
Zip the Folder and give it a name for e.g. GT-I9300-XXXXXX (Dont use spaces)
Now you can upload this zip to any filehosting service of your choice
Click to expand...
Click to collapse
How to extract the modem:-
For extracting the modem you need to be rooted (If you are not or want to know how go here)
Using ADB (Go here if you want to know how to set up ADB)
Connect your phone to you PC (Please ensure that ADB debugging option is checked in Developer Options)
Type
Code:
adb devices
You will get something like this:
Code:
List of devices attached
XXXXXXXXXXXXXX device
It shows your device is connected via ADB
Type
Code:
adb shell
You will get a output like this:
Code:
C:\adb>adb shell
[email protected]:/ $
Type
Code:
su
You will get:
Code:
su
[email protected]:/ #
(Those who are using Terminal Emulator can start from this step)
Type
Code:
dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
You will get
Code:
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
8192+0 records in
8192+0 records out
33554432 bytes transferred in 2.892 secs (11602500 bytes/sec)
[email protected]:/ #
Your modem.bin file is copied to the root of your sdcard, copy it to your PC and upload it to the file hosting site of your choice
Click to expand...
Click to collapse
I have tried to write everything to the best of my knowledge. If anyone feels that I have missed something or I have written something wrong please let me know. I will make the changes.

Thanx for this very useful
Sent from my GT-I9300 using Tapatalk 2

anurag549 said:
Thanx for this very useful
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
will be helpful for many ... nice work buddy

Q: When I dump modem I get a modem.bin and its ~30mb, while shipped modems in stock fw is ~12mb, why is this?

Perka said:
Q: When I dump modem I get a modem.bin and its ~30mb, while shipped modems in stock fw is ~12mb, why is this?
Click to expand...
Click to collapse
Well that escapes me..may be someone knowledgeable can shed some light on it..
Sorry..
Maybe the that provided with the firmware is a patch..I know OTA files are patches but can't say much about full firmwares..

I'm trying to do this using the terminal emulator in Rom toolbox and u keep getting permission denied?
(from what I understood we had two ways of doing this correct? A computer and adb or TE, correct?)

Danielhammons1 said:
I'm trying to do this using the terminal emulator in Rom toolbox and u keep getting permission denied?
(from what I understood we had two ways of doing this correct? A computer and adb or TE, correct?)
Click to expand...
Click to collapse
You have to type su in terminal to gain root access. It's just like a standard Linux terminal.

can I flash my efs.img via odin?

can't boot my phone cause I have deleted my efs folder becasue in one of the guides here someone said that if you had full recovery of your efs and you sure that your efs folder is damged than delete the folder and recover, well so I did... (I downgrade from lolipop to 4.4.2, lost my imei in the "process"
I had the efs.img backup on my computer and I moved it to my phone, I deleted my efs folder using root browser and than I used some adb app to type the commend "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096" and I restred my phone, but it never left samsmung logo and I can't boot up my phone I tried to go to stock channgeing roms, nothing helps, in recovery mode it says "E:/can't mount efs" something like that.. and the phone won't boot up, just stuck on samsung logo.
somone have any Idea what can i do?

After flashing a stock ROM, did you perform a factory wipe before booting the phone for the first time?

audit13 said:
After flashing a stock ROM, did you perform a factory wipe before booting the phone for the first time?
Click to expand...
Click to collapse
you mean when I downgrade from lolipop to the stcok rom?, if yes Than I didn't and that what cause me losing my imei and started this whole efs problem...

Did you try flashing back to stock LP? Flashing stock kk would not normally damage the efs.

audit13 said:
Did you try flashing back to stock LP? Flashing stock kk would not normally damage the efs.
Click to expand...
Click to collapse
yey I manged to fix ti!!!! god that was hard **** yes!! to me!
if someone will see this so this is what I did
1) I flashed to stock rom based lolipop but still had the issue of "E:failed to mount /efs" cause it didn't recvoer the folder and my phone still won't boot up, so I found a fix
right here http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
adb shell
Code:
mke2fs /dev/block/mmcblk0p3
Code:
mount -w -t ext4 /dev/block/mmcblk0p3 (this line dind't even work for me so I skipped it)
Code:
reboot
affter I did it phone boot up finally but I still had a fake Imei so next I used this guide (this time I ain't deleting the efs folder like he wrote"
2)http://forum.xda-developers.com/showthread.php?t=2392632, I alredy had efs.img as back up so all I did is install latest "su" and the latest busybox than I installed "Terminal Emulator"
and used the second method
"Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
my phone rebooted and now I have my imei back!

Congratulations on your success and posting your solution!

worked for me
okdark4 said:
"Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
my phone rebooted and now I have my imei back!
Click to expand...
Click to collapse
Hi okdark4,
thanks for sharing!
For me, I hat to use a slightly different command - just for the others to know:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3
reboot
That's it!

[Help] fix the Corrupted EFS on 900P

Hi mates, thank you for helping!
Really a complicated story mine, had on this phone already issues with baseband (when I bought it had LL 5.01) when I upgraded it to RR 7.1.2, then I figured out I needed to upload the latest stock 6.0.1 G900PVPS3CQD1 to have it working, I also PITted the phone before, it worked for 5-6 monts, then the signal went off.
I've tried different solutions:
1) in TWRP typed in its terminal the commands I've found here:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
It said "not enough space" but it looks in the end it copied around 3MB. Rebbited but no changes
2) Again thr TWRP:
dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=efs.bak
dd if=/dev/block/bootdevice/by-name/modemst1 of=modemst1.bak bs=4096
dd if=/dev/block/bootdevice/by-name/modemst2 of=modemst2.bak bs=4096
find /efs -exec ls -l {} \; > efs-permissions
nothing changed
3) updated to lineage 15.1, it says "no sim card" (the sim works fine in another 900V) with rooted ADB shell tried the "dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1" but no such file. Then I decided to flash stock LL 5.01 BOK but like in stock 6.01 says "invalid sim card".
4) I run in adb:
adb shell
mount
and can't see /stl4 /efs so this is why I assume that efs is corrupted.
Somebody says to flash (under Odin PDA) EFS-Fix-regalstreak.tar.md5, but I won't risk to flash other phones data on my phone, including its IMEI.
Someone else says I have to backup EFS (I suppose this is possibile because when I executed adb commands it never said me that the files don't exist) and reflash it to fix the corruption. How this is possible to do? Thank you!
PS: I attached the backupof EFS made by TWRP, seems all good (not corrupted), why sim doesn't work?

I'm now on stock LL BOK, using in adb mount I have this
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0