External storage path
1. TWRP : /external_sd
2. Boot to system : /storage/sdcard1
{
"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"
}
dd command for backup partitions except /system and /userdata
dd if=/dev/block/platform/hi_mci.0/by-name/vrl of=/external_sd/backup/vrl.img
dd if=/dev/block/platform/hi_mci.0/by-name/vrl_backup of=/external_sd/backup/vrl_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/fw_lpm3 of=/external_sd/backup/fw_lpm3.img
dd if=/dev/block/platform/hi_mci.0/by-name/frp of=/external_sd/backup/frp.img
dd if=/dev/block/platform/hi_mci.0/by-name/fastboot of=/external_sd/backup/fastboot.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_factory of=/external_sd/backup/modemnvm_factory.img
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/external_sd/backup/oeminfo.img
dd if=/dev/block/platform/hi_mci.0/by-name/splash of=/external_sd/backup/splash.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/external_sd/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/external_sd/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/external_sd/backup/modemnvm_system.img
dd if=/dev/block/platform/hi_mci.0/by-name/secure_storage of=/external_sd/backup/secure_storage.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodemnvm of=/external_sd/backup/3rdmodemnvm.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodemnvmbkp of=/external_sd/backup/3rdmodemnvmbkp.img
dd if=/dev/block/platform/hi_mci.0/by-name/persist of=/external_sd/backup/persist.img
dd if=/dev/block/platform/hi_mci.0/by-name/reserved1 of=/external_sd/backup/reserved1.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_om of=/external_sd/backup/modem_om.img
dd if=/dev/block/platform/hi_mci.0/by-name/splash2 of=/external_sd/backup/splash2.img
dd if=/dev/block/platform/hi_mci.0/by-name/misc of=/external_sd/backup/misc.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_update of=/external_sd/backup/modemnvm_update.img
dd if=/dev/block/platform/hi_mci.0/by-name/recovery2 of=/external_sd/backup/recovery2.img
dd if=/dev/block/platform/hi_mci.0/by-name/reserved2 of=/external_sd/backup/reserved2.img
dd if=/dev/block/platform/hi_mci.0/by-name/teeos of=/external_sd/backup/teeos.img
dd if=/dev/block/platform/hi_mci.0/by-name/trustfirmware of=/external_sd/backup/trustfirmware.img
dd if=/dev/block/platform/hi_mci.0/by-name/sensorhub of=/external_sd/backup/sensorhub.img
dd if=/dev/block/platform/hi_mci.0/by-name/fw_hifi of=/external_sd/backup/fw_hifi.img
dd if=/dev/block/platform/hi_mci.0/by-name/boot of=/external_sd/backup/boot.img
dd if=/dev/block/platform/hi_mci.0/by-name/recovery of=/external_sd/backup/recovery.img
dd if=/dev/block/platform/hi_mci.0/by-name/dts of=/external_sd/backup/dts.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem of=/external_sd/backup/modem.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_dsp of=/external_sd/backup/modem_dsp.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_dtb of=/external_sd/backup/modem_dtb.img
dd if=/dev/block/platform/hi_mci.0/by-name/dfx of=/external_sd/backup/dfx.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodem of=/external_sd/backup/3rdmodem.img
dd if=/dev/block/platform/hi_mci.0/by-name/cache of=/external_sd/backup/cache.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest0 of=/external_sd/backup/hisitest0.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest1 of=/external_sd/backup/hisitest1.img
dd if=/dev/block/platform/hi_mci.0/by-name/cust of=/external_sd/backup/cust.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest2 of=/external_sd/backup/hisitest2.img
Click to expand...
Click to collapse
Cheers for that. I'm on the al10 and was thinking of force flashing all partitions from the international model just to see if it worked
Sent from my NEXT using Tapatalk
sure works
How would one force flash all partitions? I have the L29 OTA's and I am trying to get my L10 debranded with fastboot as I want to keep stock recovery/unrooted/etc.
u mean u have the AL10? theres YET no option to completely debrand it AND receive OTA updates for the "other" model ure trying to flash it to (in this case, L29)
supposedly, ud have to flash the oeminfo and make changes to build.prop and other system files, as well as flashing all partitions of a proper stock L29 firmware. people are still trying to figure things out.
in the meantime, its no biggie to crossflash roms to at least get the "other" experience manually
jbmc83 said:
u mean u have the AL10? theres YET no option to completely debrand it AND receive OTA updates for the "other" model ure trying to flash it to (in this case, L29)
supposedly, ud have to flash the oeminfo and make changes to build.prop and other system files, as well as flashing all partitions of a proper stock L29 firmware. people are still trying to figure things out.
in the meantime, its no biggie to crossflash roms to at least get the "other" experience manually
Click to expand...
Click to collapse
Yeah, thats what I have been doing. But there are so many .img files in the OTA's that I am not able to flash with fastboot, so I feel like I am missing stuff.
well the number of partitions shouldnt be a problem, it would just take a while to type all commands in fastboot
jbmc83 said:
well the number of partitions shouldnt be a problem, it would just take a while to type all commands in fastboot
Click to expand...
Click to collapse
I tried flashing them all once. Most of them failed with command not supported. The only ones that work are boot cust cache system modem recovery and a couple others.
hm and the erecovery option with update.app in dload folder probably shows u incompatible system , hm?
jbmc83 said:
hm and the erecovery option with update.app in dload folder probably shows u incompatible system , hm?
Click to expand...
Click to collapse
Yeah.
Hi
I try to put my mate 8 AL10 in full L29.
I have extracted all data from update and i have flashed cache, cust, system and oeminfo, all work perfectly.
The phone is recognized in L29 but when i plug it in usb mode developer, it's write Huawei NXT-AL10.
What i need, to pass it in full L29 version ?
Flash crc ? boot ? recovery2 ?trustfirmware ?
thanks for your help
jarod27 said:
Hi
I try to put my mate 8 AL10 in full L29.
I have extracted all data from update and i have flashed cache, cust, system and oeminfo, all work perfectly.
The phone is recognized in L29 but when i plug it in usb mode developer, it's write Huawei NXT-AL10.
What i need, to pass it in full L29 version ?
Flash crc ? boot ? recovery2 ?trustfirmware ?
thanks for your help
Click to expand...
Click to collapse
it could be an idea to get all partition from L29 with "dd if=/dev/block/partitonX of=partitionX.img" and flash it on L10?
can you chek yout custom.bin? is in /data partition. open it with root explorer as text file
no custom.bin in data folder
jarod27 said:
no custom.bin in data folder
Click to expand...
Click to collapse
ok.
do you think that clone all partition from l29 could be a good idea?
maybe
you can do this ?
no, I have not yet bought the mate 8. I 'm studying the situation because if I take it , I take al10 for the 64gb storage. But i prefer the international software because it has a reduced sar value.
the hardware is the same.
I have not bought it yet because I have a doubt about the size: I would not like it's too big to carry in pocket and to use it with only one hand
i thinking
ok
Did someone already tried to crossflash all the partitions?
How would you do that?
Fastboot ist not accepting all partitions.
Is it possible with dd comand from adb or twrp?
Btw. you should better not modify or crossflash NVME as it contains your SN, IMEI, MAC, ...
Backing up partitions
somboons said:
External storage path
1. TWRP : /external_sd
2. Boot to system : /storage/sdcard1
dd command for backup partitions except /system and /userdata
Click to expand...
Click to collapse
Would you mind to explain a noob (me) with a little more detail on how to locate this partitions from my computer and back some of them up?
I want to back up OEMinfo, CUST & NVME.
thanks a lot!
hi , like many other i haved a bricked mate 8 and after using dc phoenix to repair it . the phone work but no signial or network and i think because in start of flashing dc-phoenix erase this three partition modemnvm_backup/modemnvm_factory/modemnvm_system and don't reflash them only erase
so pls can you upload this three partition image if it's possible
thank you any way
Related
/EFS partition contains a lot of information about your phone, f.e: wifi/bt mac address and your IMEI (nv_data.bin).
It's highly recommended to backup the whole partition, or at least copy the files from the efs directory.
CORRUPTED OR NOT?
You can check if the efs is mounted or completly damaged with this command:
adb shell
mount
You will see something like this:
{
"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"
}
Red part means /efs is mounted.
IF YOUR PHONE HAVE CORRECT EFS PARTITION:
1, Root your phone - there are several methods to do this.
2, Install root explorer or Estrongs file explorer and copy /efs dir to your sdcard - this will copy the files.
or
2, Make a backup from the whole partition -this is better if you flash a phone with wrong ops, the only way to restore using this backup.
Backup:
adb shell
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Restore:
Add efs.rfs to an unix compatible tar and flash with odin as efs file:
IF YOUR PHONE /EFS IS CORRUPTED:
Flash the included /efs tar with odin:
This will remount your efs partition and (if you have a backup or fixed nv_data.bin) you just need to overwrite files with a file explorer.
confirm WORKING 100% ... all you just need later is the nv_data.bin fixed
Thanks so much for your efforts
I am using I5801 JPB (with restored bootscreen and Rooted via SuperoneClick)
while using "adb shell" command at Better terminal its showing "adb: not found"
I flashed my I5801 from JP9, JPA and JPB till date..
is it possible to restore the backup now..??
Because you need adb.
If you do on phone (Terminal emualtor) adb shell not needed, just su and the other commands.
Szaby59 said:
Because you need adb.
If you do on phone (Terminal emualtor) adb shell not needed, just su and the other commands.
Click to expand...
Click to collapse
many thnx..
BTW i am not able to get the snaps u attached..
sirtbhopal said:
many thnx..
BTW i am not able to get the snaps u attached..
Click to expand...
Click to collapse
google about install ADB for android phone, so you can follow TUT here... good for you now and future..., long journey to go, m8!
how to make .tar file because backup file is .rfs format help me i want my imei back
ok, using the dd method i made the backup of my /efs to a efs.rfs file that have ~4 MB
But when i go to the efs folder (on / ) or see the copy i've made to my SD card, there is no files at all on this folder. How can we "see" those files (nv_data.bin) ?
Hi
For backup I simply copied my /efs folder to SD card using root explorer.
Then I modified nv_data files to get unlocked.
there was no SSNV in the files.
I have a working unlocked phone now but the problem is that IMEI is all zeros like 000000000!
Can I use that folder to restore my files?
dhruvasoni said:
how to make .tar file because backup file is .rfs format help me i want my imei back
Click to expand...
Click to collapse
Download the Tar Utility from GnuWin32's SourceForge Page.
Code:
hxxp://sourceforge.net/projects/gnuwin32/files/tar/1.13-1/tar-1.13-1-bin.exe/download
(change it to http)
It'll install the tar.exe executable and required dlls in C:\Program Files\GnuWin32\bin
Copy those to where you have your rfs (or you can add the bin folder to your PATH Environment Var, google for help on how to do that)
Now type:
Code:
tar -cf efs.tar efs.rfs
Yes, you can, just copy nv_data to /efs.
Windows users can use IZARC to create tar files.
hey guys
i havn´t backuped my file but i have now imei 0000000000000
i need help help me please!!!
burak721 said:
hey guys
i havn´t backuped my file but i have now imei 0000000000000
i need help help me please!!!
Click to expand...
Click to collapse
If you use a I5801 flash a stock firmware of 2.1...the same applies even if you use I5800...
Sent from my GT-I5800 using XDA App
i have done it but my imei is allways 00000000
pleas help
Burak, what kernel do u use? There was a bug in older fugumod version where eds was not propperly mounted or read, thus the phone displayed bad imei, if u use older fugumod please update to latest version
FadeFx said:
Burak, what kernel do u use? There was a bug in older fugumod version where eds was not propperly mounted or read, thus the phone displayed bad imei, if u use older fugumod please update to latest version
Click to expand...
Click to collapse
I have used fugomod kernel 2.4
Sent from my GT-I5800 using XDA App
my imei is also showing ooooooo.....plss help mee dudes plss
i dont have imei at all!!! and sim card is not recognized,and no signal,phone unknown ....what am i supposed to do?
huzo said:
i dont have imei at all!!! and sim card is not recognized,and no signal,phone unknown ....what am i supposed to do?
Click to expand...
Click to collapse
Pray ...
LOL good answer
So Finally Ive Rooted My G4 F500L on V10o Update and Thought Of Sharing The IMG File With You Guys
And I Edited The Build.prop So We Can Get Rid Of The Korean Junk.
Rooted
No more Korean DialPad
No Korean Apps
No message LIMIT
International Boot animation
60FPS video and Image Quality to 100%
I ONLY TESTED THIS ON F500L. SINCE THE ALL F500 MODELS HAVING THE SAME SYSTEM BLOCK THIS MUST WORK ON ALL S K L MODELS. BUT YOUR MODEL WILL CHANGE TO F500L V10o . YOU CAN CHANGE THAT FROM BUILD.PROP ANYWAYS.
Command to Flash This On F500
PHP:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Follow This Guide To Flash This On Your Device
CLICK HERE!!
SCREENSHOTS
{
"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"
}
DOWNLOAD!
https://drive.google.com/file/d/0B9HJt-5YjecpTFA0Qk1FQlZVRk0/view?usp=sharing
pereradileepa said:
So Finally Ive Rooted My G4 F500L on V10o Update and Thought Of Sharing The IMG File With You Guys
And I Edited The Build.prop So We Can Get Rid Of The Korean Junk.
Rooted
No more Korean DialPad
No Korean Apps
No message LIMIT
International Boot animation
60FPS video and Image Quality to 100%
I ONLY TESTED THIS ON F500L. SINCE THE ALL F500 MODELS HAVING THE SAME SYSTEM BLOCK THIS MUST WORK ON ALL S K L MODELS. BUT YOUR MODEL WILL CHANGE TO F500L V10o . YOU CAN CHANGE THAT FROM BUILD.PROP ANYWAYS.
Command to Flash This On F500
PHP:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Follow This Guide To Flash This On Your Device
CLICK HERE!!
SCREENSHOTS
DOWNLOAD!
https://drive.google.com/file/d/0B9HJt-5YjecpTFA0Qk1FQlZVRk0/view?usp=sharing
Click to expand...
Click to collapse
Why didn't you put this in the other root thread?
Sent from my G4 using your mom
HI,I am having LG F500L,running Android 5.1,build number LMY47D,sofware version F500L09a. At first, I backup my system img to the phone memory. I typed these commands
Send_Command.exe \\.\COM3
then type id
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img.
After done, I opened my phone storage then there is a file named system.img.
Then I downloaded rooted img F500L10w online provided by a forumer. I renamed it to system2.img and copy it to phone storage. Then I open cmd typed these commands
Send_Command.exe \\.\COM3
then type id
dd if=/data/media/0/system.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
After done, my phone reboot and stuck at LG Logo screen.
OK,then i want to flash back my stock system.img. I type these commands again.
Send_Command.exe \\.\COM3
then type id
usually it will show uid=0(root) gid=0(root) context=u:r:recovery:s0 , but there straight show # after 1 seconds.
Then i type dd if=/data/media/0/system.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
after 1 second it show #
Now my phone stuck at LG Logo screen. I cannot flash back to stock img. Can i know how to solve this?Thanks.
Downloaded the file but error when I try to extract it
Upload again?
Downloaded the file but error when I try to extract it can you re upload please
pereradileepa said:
So Finally Ive Rooted My G4 F500L on V10o Update and Thought Of Sharing The IMG File With You Guys
And I Edited The Build.prop So We Can Get Rid Of The Korean Junk.
Rooted
No more Korean DialPad
No Korean Apps
No message LIMIT
International Boot animation
60FPS video and Image Quality to 100%
I ONLY TESTED THIS ON F500L. SINCE THE ALL F500 MODELS HAVING THE SAME SYSTEM BLOCK THIS MUST WORK ON ALL S K L MODELS. BUT YOUR MODEL WILL CHANGE TO F500L V10o . YOU CAN CHANGE THAT FROM BUILD.PROP ANYWAYS.
Command to Flash This On F500
PHP:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Follow This Guide To Flash This On Your Device
CLICK HERE!!
SCREENSHOTS
DOWNLOAD!
https://drive.google.com/file/d/0B9HJt-5YjecpTFA0Qk1FQlZVRk0/view?usp=sharing
Click to expand...
Click to collapse
What was your F500L original version 10a 10b? So far flashing different version then current = soft brick
file is corrupt. reupload pls
Downloaded the file but error when I try to extract it can you re upload please
Can I use this if my phone is on V11D?
--------------
Never mind, this file is corrupted. I tried with both Winrar and 7-zip
clockcycle said:
What was your F500L original version 10a 10b? So far flashing different version then current = soft brick
Click to expand...
Click to collapse
Bro how can i root my lg f500k
hello. my phone is F500 (without any preceding letter S, L or K) with software F50010s. can I flash it with this system image? so far i've been unable to find this model anywhere on the internet.
Hello everyone,
Let me explain veeeery briefly my story.
During an update, the phone froze and I had to turn it off. I'll spare you all that happened next, but in practice "cache" and "persist" partition have failed.
Now, the first one is minor and I could rebuild it and format it without much thought, the second one, unfortunately, I could not retrieve it and I was forced to do the same thing. Too bad that the "persist" partition holds all the necessary configurations to operate the various sensors of the smartphone.
Always avoiding to tell you all the attempts I made (and trust me, I made them all), the last remaining solution, and probably the working one, is to get a dump of the "persist" partition to flash via fastboot. That is, I need a backup of this memory space (taken from a Xiaomi Redmi Notes 4G (Qualcomm) - single SIM, working of course).
Here's how to create this file, then you will have to send it to me (There are few simple steps).
-----------------------------------------------------
Connect the phone to PC with USB.
First, verify that the device is responding ADB (Use ADB while the phone is in recovery mode, as a matter of privileges)
Code:
adb devices
{
"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"
}
If you see a character string, then the device is connected.
Now enter into Shell and check the "persist" partition number
[Each line is a command where to give ENTER - After the # I just put a comment. Type just the previous part.]
Code:
adb shell [B][COLOR="DarkRed"]#Enter into shell[/COLOR][/B]
parted /dev/block/mmcblk0 [B][COLOR="darkred"]#Start a tool to manage partitions[/COLOR][/B]
unit MB [B][COLOR="darkred"]#Set size in MB[/COLOR][/B]
print [B][COLOR="darkred"]#Display the partitions list[/COLOR][/B]
You should see a partitions list. In my case (and probably in all the Xiaomi devices), the "persist" partition is the #26.
At this point it's possible to dump (Backup) that memory space.
If you are still in the "parted" tool, then you need to quit it first, typing "quit", to get back in the shell (but without going further out from the shell)
Code:
quit [B][COLOR="darkred"]#Quit the "parted" tool[/COLOR][/B]
dd if=/dev/block/mmcblk0[COLOR="SeaGreen"][B]p26[/B][/COLOR] of=/sdcard/persist.img [B][COLOR="DarkRed"]#dump from partition #26, one highlighted in green (persist), making a file into internal memory[/COLOR][/B]
Done!
Now you have just to take that file and send it to me. If you want to continue using terminal (since you have already), you can copy the files to your PC as follows:
Code:
exit [B][COLOR="DarkRed"]#if you are still into shell, then you need to exit[/COLOR][/B]
adb pull /sdcard/persist.img C:\
Now you copied the file (that was created into internal memory) to your PC, in the C: \ drive
Please attach this file on reply.
Thank you!
Updated OP
Inviato dal mio Nexus 4 utilizzando Tapatalk
Up
Inviato dal mio Nexus 4 utilizzando Tapatalk
same problem
Attached a zipped persist.img file taken from mmcblk0p26 of dior device. Hope this helps.
MiniBlu
zenida said:
Hello everyone,
Let me explain veeeery briefly my story.
During an update, the phone froze and I had to turn it off. I'll spare you all that happened next, but in practice "cache" and "persist" partition have failed.
Now, the first one is minor and I could rebuild it and format it without much thought, the second one, unfortunately, I could not retrieve it and I was forced to do the same thing. Too bad that the "persist" partition holds all the necessary configurations to operate the various sensors of the smartphone.
Always avoiding to tell you all the attempts I made (and trust me, I made them all), the last remaining solution, and probably the working one, is to get a dump of the "persist" partition to flash via fastboot. That is, I need a backup of this memory space (taken from a Xiaomi Redmi Notes 4G (Qualcomm) - single SIM, working of course).
Here's how to create this file, then you will have to send it to me (There are few simple steps).
-----------------------------------------------------
Connect the phone to PC with USB.
First, verify that the device is responding ADB (Use ADB while the phone is in recovery mode, as a matter of privileges)
Code:
adb devices
If you see a character string, then the device is connected.
Now enter into Shell and check the "persist" partition number
[Each line is a command where to give ENTER - After the # I just put a comment. Type just the previous part.]
Code:
adb shell [B][COLOR="DarkRed"]#Enter into shell[/COLOR][/B]
parted /dev/block/mmcblk0 [B][COLOR="darkred"]#Start a tool to manage partitions[/COLOR][/B]
unit MB [B][COLOR="darkred"]#Set size in MB[/COLOR][/B]
print [B][COLOR="darkred"]#Display the partitions list[/COLOR][/B]
You should see a partitions list. In my case (and probably in all the Xiaomi devices), the "persist" partition is the #26.
At this point it's possible to dump (Backup) that memory space.
If you are still in the "parted" tool, then you need to quit it first, typing "quit", to get back in the shell (but without going further out from the shell)
Code:
quit [B][COLOR="darkred"]#Quit the "parted" tool[/COLOR][/B]
dd if=/dev/block/mmcblk0[COLOR="SeaGreen"][B]p26[/B][/COLOR] of=/sdcard/persist.img [B][COLOR="DarkRed"]#dump from partition #26, one highlighted in green (persist), making a file into internal memory[/COLOR][/B]
Done!
Now you have just to take that file and send it to me. If you want to continue using terminal (since you have already), you can copy the files to your PC as follows:
Code:
exit [B][COLOR="DarkRed"]#if you are still into shell, then you need to exit[/COLOR][/B]
adb pull /sdcard/persist.img C:\
Now you copied the file (that was created into internal memory) to your PC, in the C: \ drive
Please attach this file on reply.
Thank you!
Click to expand...
Click to collapse
mny315 RUS said:
same problem
Click to expand...
Click to collapse
Thanks bro ))
Yeah, sorry I abandoned this thread because I found help from MIUI Italia forum. I should update procedure here but I can't now... I don't know if I can post a link from another forum... Maybe later I'll translate and paste here
Thread on MIUI
Hello everybody.
I am having a big issiue with my G2 right now so i thought that i can fix it asking here.
My problem is that recently i was loosing my mobile network connection and for this reason i decided to restore the stock firmware on my device ( I was using CloudyG2 ).
After i restored the stock firmware the mobile network is working great but after a simple restart or power off and boot again the network itself dissapears. After a couple of tryes i noticed that the fields called Baseband and IMEI are the right ones but after the reboot they both become Unknown. I also noticed that the firmware once installed the stock one is V30d-EUR-xx but after the reboot it is just V30d.
I wanted to ask what can i do to fix the problem? After the reboot i am seeing the ANDROID IS UPDATING screen but for less than 8 seconds. I think this is why the network dissapears and i loose connection and the firmware name changes. Can it be that android updates after it initializes all the applications and this shadow update make my phone unusable?
I wanted also to say that i tryed to use BlissPop or Cyanogen ROMS and the network work perfectly with those, it is not about 3G or LTE band being not compatible. But still i would like to know why i get this problems. I also want to say that i, one time, flashed the phone using the TOT flash method but that flash mode is only for US AT&T phones, so for this reason maybe i loose the network. I returned to stock using the KDZ firmware.
I am ataching the screenshot to explain my problem better, just in case, sorry but they are in italian.
{
"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"
}
Now i really don't know if it is better to send it in assistance or it is just a software problem that i can fix myself. What do you think? The phone itself worked great for almost two years now...
Thank you, if you have any questions please ask me
Maybe the only thing i can do is restore every single partition with a working D802 32GB european phone.
Can someone please run this scripts in a terminal ( phone needs root access ) and share them with mega? Thank you
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/backup/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/backup/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/sdcard/backup/cache.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cust of=/sdcard/backup/cust.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/dbi of=/sdcard/backup/dbi.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/dbibak of=/sdcard/backup/dbibak.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/DDR of=/sdcard/backup/DDR.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/drm of=/sdcard/backup/drm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/encrypt of=/sdcard/backup/encrypt.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/backup/fota.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsc of=/sdcard/backup/fsc.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/backup/fsg.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/grow of=/sdcard/backup/grow.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/backup/laf.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/backup/misc.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/backup/modem.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/efs/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/efs/modemst2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/mpt of=/sdcard/backup/mpt.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/sdcard/backup/pad.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/sdcard/backup/pad1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/sdcard/backup/pad2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/backup/persist.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rct of=/sdcard/backup/rct.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/backup/recovery.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/sdcard/backup/rpm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpmbak of=/sdcard/backup/rpmbak.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/sdcard/backup/sbl1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sns of=/sdcard/backup/sns.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/spare of=/sdcard/backup/spare.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/sdcard/backup/ssd.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/backup/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tombstones of=/sdcard/backup/tombstones.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/sdcard/backup/tz.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tzbak of=/sdcard/backup/tzbak.img
im using lg g2 d802 .i have wifi connection problem.
when i switch on the wifi ,it stays for few second and off again
someone can help me to solve it,[email protected]
McSmoove said:
Hello everybody.
I am having a big issiue with my G2 right now so i thought that i can fix it asking here.
My problem is that recently i was loosing my mobile network connection and for this reason i decided to restore the stock firmware on my device ( I was using CloudyG2 ).
After i restored the stock firmware the mobile network is working great but after a simple restart or power off and boot again the network itself dissapears. After a couple of tryes i noticed that the fields called Baseband and IMEI are the right ones but after the reboot they both become Unknown. I also noticed that the firmware once installed the stock one is V30d-EUR-xx but after the reboot it is just V30d.
I wanted to ask what can i do to fix the problem? After the reboot i am seeing the ANDROID IS UPDATING screen but for less than 8 seconds. I think this is why the network dissapears and i loose connection and the firmware name changes. Can it be that android updates after it initializes all the applications and this shadow update make my phone unusable?
I wanted also to say that i tryed to use BlissPop or Cyanogen ROMS and the network work perfectly with those, it is not about 3G or LTE band being not compatible. But still i would like to know why i get this problems. I also want to say that i, one time, flashed the phone using the TOT flash method but that flash mode is only for US AT&T phones, so for this reason maybe i loose the network. I returned to stock using the KDZ firmware.
I am ataching the screenshot to explain my problem better, just in case, sorry but they are in italian.
Now i really don't know if it is better to send it in assistance or it is just a software problem that i can fix myself. What do you think? The phone itself worked great for almost two years now...
Thank you, if you have any questions please ask me
Click to expand...
Click to collapse
will this help read and see if it does.
http://forum.xda-developers.com/lg-g2/general/imei-baseband-unknown-refurbished-t3076993
Hello experts!
After updating to OOS 2.2.1 through stock updater, after reboot I get:
Code:
OEM_NV_BACKUP The NV partition is invalid!
Of course, no IMEI, no network on both SIMs.
Been googling all day, to no avail.
No root, stock recovery, EFS available.
I have tried:
This one:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
And this one, similar to first one:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21 (Oneplus Two - Solution for Hard Bricked Device).
Is there a hope or I need to send it to repair center?
Tagging @Zyxxeil @Lord Boeffla, maybe some ideas will pop up.
EDIT:
EFS backup restoration in TWRP does not fix it.
Thanks in advance!
Juraj
do you have any back up of your EFS partition in twrp backup?? if you have restore that partition and see.
chintu1234 said:
do you have any back up of your EFS partition in twrp backup?? if you have restore that partition and see.
Click to expand...
Click to collapse
As said....no.
TWRP did not backed it up.
Any other method/idea, ayone?
EDIT:
Just figured out that I have EFS backed up (oem_stanvbk.emmc.win). I will restore it from twrp, lets see how it goes.
jukyO said:
Hello experts!
After updating to OOS 2.2.1 through stock updater, after reboot I get:
Code:
OEM_NV_BACKUP The NV partition is invalid!
Of course, no IMEI, no network on both SIMs.
Been googling all day, to no avail.
No root, stock recovery, EFS available.
I have tried:
This one:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
And this one, similar to first one:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21 (Oneplus Two - Solution for Hard Bricked Device).
Is there a hope or I need to send it to repair center?
Tagging @Zyxxeil @Lord Boeffla, maybe some ideas will pop up.
EDIT:
EFS backup restoration in TWRP does not fix it.
Thanks in advance!
Juraj
Click to expand...
Click to collapse
Any further ideas, as EFS restore from TWRp doeas not work.
Can someone please check what files are inside TWRP EFS backup?
Sent from my A0001 using XDA-Developers mobile app
jukyO said:
Can someone please check what files are inside TWRP EFS backup?
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
{
"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"
}
here is the file that have in my EFS backup from TWRP
lockmunk said:
View attachment 3729740
here is the file that have in my EFS backup from TWRP
Click to expand...
Click to collapse
I have exactly the same.
Why restoration of it does not solve it?
If I pull
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
with dd:
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
to sdcard, they have 1M each, whilst backup is 10M.
Can anyone try the same?
EDIT:
above mmcblk is for OPO, OPT has /dev/block/mmcblk0p20.
And size is ok if I do dd with it.
bump, anyone?
jukyO said:
bump, anyone?
Click to expand...
Click to collapse
bump #2.
got the same issue, damn x) need help, tried the 100% restore backup with qualcomm drivers etc, didnt restore 100%
bump..please help to share your modemst1 & modemst2 please......
androidbrick.com
Nothing on androidbrick...