Hi
My device is rooted an i accidentally deleted NVRAM Partition And now imei is null and not signal
NVRAM Partition is not in FTF file so, I kindly ask if someone with a rooted Xperia M5 running stock firmare (the firmware version/device variant doesn't matter, it can be from doul SIM devices too) could run the following commands from ADB and then upload the file that will be pulled from the phone here:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/nvram of=/data/local/tmp/nvram.img"
adb shell su -c "chmod 777 /data/local/tmp/nvram.img"
adb pull /data/local/tmp/nvram.img"
DO NOT EVER flash the NVRAM or TA partition of another device, even if it's from exactly the same model. You'll hard brick your device by doing that, those partitions are unique to each unit, that's why they're not available in FTF...
mbc07 said:
DO NOT EVER flash the NVRAM or TA partition of another device, even if it's from exactly the same model. You'll hard brick your device by doing that, those partitions are unique to each unit, that's why they're not available in FTF...
Click to expand...
Click to collapse
I have a backup of TA partitions can this help me to solve this problem?
what i do to restore it?
What do you think I should do?
(sorry for my poor English)
Related
As with newer Samsung Android phones it is practically essential that if you go to the modding scene and start uploading custom roms you should have a backup of your efs
For simple backup of efs partition
by sishgupta
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
and for a full image of your brand new phone
as various users have stated there are other more correct ways of backing up your new efs partition,
the one i liked the most is this one by because it backs up all your partitions
by c0ns0le
Code:
IF YOU HAVE BUSY BOX INSTALLED
adb shell
su -
for i in $(ls /dev/block/platform/omap/omap_hsmmc.0/by-name/ | grep -v user)
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
NO BUSYBOX:
adb shell
su -
for i in boot cache dgs efs metadata misc param radio recovery sbl system xloader
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
deprecated just staying here because this started all the correct backup commands for your efs
In order to do this for your galaxy nexus you should have adb working on your machine and also debugging enabled in your phone
this is practically easy, your phone must be rooted, or at least booted with the boot.img of this thread How to Root GALAXY NEXUS
Code:
adb root
adb remount
adb pull /factory
and now backup that file to at least 2 places lol
I always get paranoid with this
have fun installing custom roms
i don't think that works for GN
Samsung changed their EFS recently on the new released phones
it's no longer how it was with the Galaxy S line of phones
No one know if we really can backup and restore /factory (EFS)?
this should put an .img file in /sdcard. It's the same method as the one in the sgs2 section but with different paths.
Code:
adb shell
su
cat /dev/block/platform/omap/omap_hsmmc.0/by-name/efs > /sdcard/efs.img
edit: you'll need to be root, obviously
edit again:
this is technically better but does the same thing:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
Out of curiosity, what is efs?
I am pretty familiar with flashing my HTC Desire, but there is not an efs partition (AFAIK)?
Cheers!
It backs up your imei information in case it gets corrupted by flashing custom roms and mods
Sent from my GT-I9000 using xda premium
420SYN said:
It backs up your imei information in case it gets corrupted by flashing custom roms and mods
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Cool thanks!
Stew
Is this something specific to Samsung phones? I have been rooting and flashing since the nexus one and have never needed this.
Doesn't clockwork mod back this up? If not, why not?
Sent from my LG-P999
dave_t321 said:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
Click to expand...
Click to collapse
Would it be if=/dev/block/platform/omap/omap_hsmmc.0/by-name/factory since this partition is named "factory" now?
If the efs is really in the /factory folder and its not hardlinked files sitting somewhere else is there a better way to save the files and keeping the permissions?
Using tar or gzip on them before?
So which method to follow in order to backup my efs folder?All information is under /factory
use
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
this is the right command as if you run ls on the by-name folder you can see that it is still efs not factory
factory must be a link to this
omg, i have a 0049... IMEI after flashing ICL53F via fastboot!
how could i restore my old IMEI?
edit: jippie, i got my IMEI back after flashing the ITL41F odin version from this post!
i suggest everyone to backup the efs before flashing other firmwares!
Could someone provide the correct commands to restore the efs folder please Ive backed it up just need to know how to restore it if something bad happens
There is a guide for it on these forums. Google 'efs restore android' and you should find it.
There is also an efs restore application that will use img files (like how we made in this guide) instead of just the nv_data.bin
Sent from my Galaxy Nexus using XDA App
does it actually work with this phone?
fun w/ shellfoo
Code:
IF YOU HAVE BUSY BOX INSTALLED
adb shell
su -
for i in $(ls /dev/block/platform/omap/omap_hsmmc.0/by-name/ | grep -v user)
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
NO BUSYBOX:
adb shell
su -
for i in boot cache dgs efs metadata misc param radio recovery sbl system xloader
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
---------- Post added at 03:43 PM ---------- Previous post was at 03:15 PM ----------
[/COLOR]
dave_t321 said:
this should put an .img file in /sdcard. It's the same method as the one in the sgs2 section but with different paths.
Code:
adb shell
su
cat /dev/block/platform/omap/omap_hsmmc.0/by-name/efs > /sdcard/efs.img
edit: you'll need to be root, obviously
edit again:
this is technically better but does the same thing:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
Click to expand...
Click to collapse
i've foud this one..wich is better?
adb shell
su
busybox dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/data/media/my_efs_backup.img
They are the same with different output locations. The one that leads with busy box is for a configuration where the commands are not aliased for a busy box setup.
Sent from my Galaxy Nexus using XDA App
Similar thing happened to me. I got a 2nd nexus, decided to restore a nandroid from my 1st nexus onto the 2nd one. Restore went fine, it was like a clone of the 1st phone except the IMEI was corrupt with a generic 0049... one. I flashed the phone back to a google factory ITL41D and the IMEI was restored. Needless to say I won't be doing that again!
paratox said:
omg, i have a 0049... IMEI after flashing ICL53F via fastboot!
how could i restore my old IMEI?
edit: jippie, i got my IMEI back after flashing the ITL41F odin version from this post!
i suggest everyone to backup the efs before flashing other firmwares!
Click to expand...
Click to collapse
Hello Defy Mini Users, I'm going to write a tutorial on how to fix a burnt NAND.
My overclock became unstable and I had bad blocks everywhere so I decided to recover my NAND. @cute_prince method fixed by phone.
@MauroSZ @Bernd.Defy @wilberfish @conrad0
Thanks to cute_prince tutorial for HTC Explorer NAND recovery. I have just adapted to Defy Mini XT320/XT321.
Now in cmd type in these commands:
Code:
adb reboot bootloader
Code:
fastboot boot twrp.img
Code:
adb shell mount -a
Code:
adb push flash_erase /system/xbin
Code:
adb shell cd /system/xbin
Code:
adb shell chmod 755 flash_erase
Code:
adb shell ./flash_erase -N /dev/mtd/mtd9 0 0
Code:
adb shell ./flash_erase -N /dev/mtd/mtd11 0 0
Code:
adb shell ./flash_erase -N /dev/mtd/mtd12 0 0
Code:
adb reboot bootloader
Code:
fastboot erase userdata
Code:
fastboot erase cache
Code:
fastboot erase system
Now flash back your SBF via RSD-Lite.
on this step "adb shell chmod 755 flash_erase"
I get chmod: flash_erase: no such file or directory.
What am i missing?
@rootdefyxt320, Theoretical question:
Any idea what happens recovering nandroid instead flashing a SBF via RSD Lite ?
MauroSZ said:
@rootdefyxt320, Theoretical question:
Any idea what happens recovering nandroid instead flashing a SBF via RSD Lite ?
Click to expand...
Click to collapse
You restore a nandroid backup that has a corrupted NAND, which is what you don't want. Flashing an SBF doesn't give a corrupted NAND as it is fresh. But you must flash_erase before you flash an SBF otherwise you will still have a burnt NAND.
wilberfish said:
on this step "adb shell chmod 755 flash_erase"
I get chmod: flash_erase: no such file or directory.
What am i missing?
Click to expand...
Click to collapse
Did you push flash_erase to /system/xbin? This fixes the missing file issue. Otherwise you can mount /system manually in TWRP.
Yes, fixed it. Silly mistake.
Thanks it works brilliantly.
wilberfish said:
Yes, fixed it. Silly mistake.
Thanks it works brilliantly.
Click to expand...
Click to collapse
So your NAND is fixed now?
rootdefyxt320 said:
So your NAND is fixed now?
Click to expand...
Click to collapse
Is correct supposing the android automatically avoids bad blocks using others normal blocks instead ? Is journaling correlated ? If true, does make sense flash a sbf first and restore a nandroid just after getting fastboot ? Or do you recommend anorher backup way like titanium ? Or maybe a mixed way using a old nandroid made when the nand was not burnt and Titanium just after to make the device state more recent ?
Is there a easy and quick test to know if the nand is burnt ?
Sent by Smartphone Using Tapatalk 2
rootdefyxt320 said:
So your NAND is fixed now?
Click to expand...
Click to collapse
Yes seems so. Didn't have time to check but after clean install and updates back to 73mb free
Sent from my HTC Desire C using xda app-developers app
---------- Post added at 09:24 PM ---------- Previous post was at 09:17 PM ----------
Originally Posted by rootdefyxt320
So your NAND is fixed now?
Click to expand...
Click to collapse
Is correct supposing the android automatically avoids bad blocks using others normal blocks instead ? Is journaling correlated ? If true, does make sense flash a sbf first and restore a nandroid just after getting fastboot ? Or do you recommend anorher backup way like titanium ? Or maybe a mixed way using a old nandroid made when the nand was not burnt and Titanium just after to make the device state more recent ?
Is there a easy and quick test to know if the nand is burnt ?
Sent by Smartphone Using Tapatalk 2
Click to expand...
Click to collapse
adb shell dmesg will give you a report, scroll down and you will see if you have bad blocks.
Yes it avoids bad blocks automatically. As for backup I have no idea, sorry.
MauroSZ said:
Is correct supposing the android automatically avoids bad blocks using others normal blocks instead ? Is journaling correlated ? If true, does make sense flash a sbf first and restore a nandroid just after getting fastboot ? Or do you recommend anorher backup way like titanium ? Or maybe a mixed way using a old nandroid made when the nand was not burnt and Titanium just after to make the device state more recent ?
Is there a easy and quick test to know if the nand is burnt ?
Sent by Smartphone Using Tapatalk 2
Click to expand...
Click to collapse
The problem with nandroid backups is when you back it up. I backup my phone before overclocking so I can restore my NANDROID backup. You can restore your nandroid if you backup before overclocking. Don't restore your NANDROID if you backed it up after overclocking. Basically YAFFS2 filesystem uses 'blocks' to store the data. It won't write to the 'bad blocks' so you lose storage. Basically a YAFFS2 NANDROID backup also backups the bad blocks which is what you don't want. You can read more about YAFFS Filesystem here: http://en.wikipedia.org/wiki/YAFFS
@rootdefyxt320 thanks for the link, but if i backup just after a minute i overclocked, i am supposed it will not sufficient time to burn the nand, right ? And i can avoid all a process to overclock again if i have to recovery my nand.
It seems the CWM backup creates a continuous nand image containing good and bad blocks. The android skips bad blocks writing data. Then i'm supposed backup apps as Titanium do a good job in this case because (i am also supposed) they don't work with image.
Sent by Smartphone Using Tapatalk 2
MauroSZ said:
@rootdefyxt320 thanks for the link, but if i backup just after a minute i overclocked, i am supposed it will not sufficient time to burn the nand, right ? And i can avoid all a process to overclock again if i have to recovery my nand.
It seems the CWM backup creates a continuous nand image containing good and bad blocks. The android skips bad blocks writing data. Then i'm supposed backup apps as Titanium do a good job in this case because (i am also supposed) they don't work with image.
Sent by Smartphone Using Tapatalk 2
Click to expand...
Click to collapse
Yeah, it won't have that much effect. The effect happens after a couple of weeks of overclocking.
After adb push flash_erase /system/xbin the commands should use full path, mine didn't work with CD.
Also shell commands didn't work first time, maybe because touched some buttons on TWRP screen.
Code:
Code:
adb reboot bootloader
fastboot boot twrp.img
adb shell mount -a
adb push flash_erase /system/xbin
adb shell cd /system/xbin
adb shell chmod 755 /system/xbin/flash_erase
adb shell /system/xbin/flash_erase -N /dev/mtd/mtd9 0 0
adb shell /system/xbin/flash_erase -N /dev/mtd/mtd11 0 0
adb shell /system/xbin/flash_erase -N /dev/mtd/mtd12 0 0
adb reboot bootloader
fastboot erase userdata
fastboot erase cache
fastboot erase system
After repartition of internal memory i cant enable wifi and bluetooth.From that i understand the script didnt make proper backup and restore of
:customfs.img
fsc.img
fsg.img
parinfo.img
persist.img
ssd.img
Does anyone know how to flash again these file or whole system?
I had already used:
1)nandroid restore from previous condition
2)flash stock rom from stock recovery with no success...
Every opinion will be helpful......
i flash manually the files from recovery so now im ok.
Steps
1)Download this file (has everything you need) http://d-h.st/RLS
2)Unzip it
3)Boot Into recovery
4)Open a command promt on the unziped folder
5)Copy paste one by one these commands into command promt
Code:
adb shell mkdir /storage/sdcard1
adb shell mount /dev/block/mmcblk1p1 /storage/sdcard1 -t vfat
adb push part1.sh /tmp/part1.sh
adb shell chmod 0777 /tmp/part1.sh
adb shell /tmp/part1.sh
adb push persist /storage/sdcard1/persist
adb push customfs /storage/sdcard1/customfs
adb push fsg /storage/sdcard1/fsg
adb push fsc /storage/sdcard1/fsc
adb push ssd /storage/sdcard1/ssd
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/persist if=/storage/sdcard1/persist
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/customfs if=/storage/sdcard1/customfs
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/fsg if=/storage/sdcard1/fsg
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/fsc if=/storage/sdcard1/fsc
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/ssd if=/storage/sdcard1/ssd
You are ready
i have same problem with z7 max but in mine situation i cant see sim cards
can i use the same?
Petros_tigra said:
After repartition of internal memory i cant enable wifi and bluetooth.From that i understand the script didnt make proper backup and restore of
:customfs.img
fsc.img
fsg.img
parinfo.img
persist.img
ssd.img
Does anyone know how to flash again these file or whole system?
I had already used:
1)nandroid restore from previous condition
2)flash stock rom from stock recovery with no success...
Every opinion will be helpful......
Click to expand...
Click to collapse
hi ,
i have zte nubia z7 mini and i was installing z5s mini miui rom in my phone. when the process done phone went to off and hard to turn it on. when i connect to pc it doesn't even detect the phone usb and asking for installing phones usb drivers... please help me if its possible
Thank you Sir!
Your intelligence has saved my Z7 Max running stock ROM v1.59. Now the WiFi and Bluetooth is working as usual....
Can you please help me about this, i tried to repartiton the phone and i got the same situation phone works but wifi and bluetooth doesnt work, i try to download that link but it says link doesnt work any more files are missing. can you please help me about this.
Hi my freinds
my sim1 and 2 not work
i understand this problem come by delete the nvram Partition
if anyone have rooted xperia m5 (e5633) can help me to solve this proablem run the following commands from ADB and then upload the file that will be pulled from the phone here:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/nvram of=/data/local/tmp/nvram.img"
adb shell su -c "chmod 777 /data/local/tmp/nvram.img"
adb pull /data/local/tmp/nvram.img"
Hi my freinds
my sim1 and 2 not work
i understand this problem come by delete the nvram Partition
if anyone have rooted xperia m5 (e5633) can help me to solve this proablem run the following commands from ADB and then upload the file that will be pulled from the phone here:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/nvram of=/data/local/tmp/nvram.img"
adb shell su -c "chmod 777 /data/local/tmp/nvram.img"
adb pull /data/local/tmp/nvram.img"
i couldn't find that folder
Just reflash your fw i u want the imei show up
but no prob when your imei null stats
Bennybtc said:
i couldn't find that folder
Click to expand...
Click to collapse
Hi
your device will be rooted
and copy this folder from root/data/nvram
please help me aim not find any solution for this one
farshad9500gy said:
Hi
your device will be rooted
and copy this folder from root/data/nvram
please help me aim not find any solution for this one
Click to expand...
Click to collapse
It tooks me quite a while to understand what are you saying:silly:
Anyway i'm not rooted, still in MM. Just reflash your fw or repair it via pc companion
meliacentrum said:
Just reflash your fw i u want the imei show up
but no prob when your imei null stats
Click to expand...
Click to collapse
i reflashed my phone and still imei is null
if you have rooted Xperia M5 running stock firmare (the firmware version/device variant doesn't matter, it can be from doul SIM devices too) could run the following commands from ADB and then upload the file that will be pulled from the phone here:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/nvram of=/data/local/tmp/nvram.img"
adb shell su -c "chmod 777 /data/local/tmp/nvram.img"
adb pull /data/local/tmp/nvram.img"
Follow this step:
http://www.androidrooting.org/how-to-recover-your-phone-when-you-have-lost-your-imei/
Or
http://www.wtfandroid.com/how-to-change-imei-number-easily-on-android-100-working/
Hope get it back
Hi, i was trying to repair my imei but i accidentally typed dd if=/dev/zero of=/dev/block/sdf and my baseband, imei, wifi, bluetooth all gone so i tried to write new qcn but qpst just failing so i need /sdf backup if anyone has an same device just type this command dd if=/dev/block/sdf of=/sdcard/sdf.bin and upload it.
Thanks in advance.
Here is the sdf.bin file for fix your device just type following to adb shell;
sdf.bin
download file and put it to your device
adb shell
su
dd if=/dev/block/sdf of=/sdcard/corruptedsdf.bin ( backup your corrupted sdf partition just in case )
dd if=/sdcard/sdf.bin of=/dev/block/sdf
i have same proplem my phone is redmi 9s curtana please help i need sdf.bin
or need sdf backup comands from another working phone