Related
Hello,
i've tried to backup the EFS Partition of my new Galaxy S3 with EFS Pro v1.8.3. My Busybox version is 1.20.2.
While trying to backup I get the following error:
Code:
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Failed!
Device MD5 Hash: md5sum: can't open 'mountpoint:'
Backup Data MD5 Hash: md5sum: can't open '/sdcard/EFSP
Error: MD5 Checksum Mismatch!!!
DO NOT USE THIS BACKUP!!!
Operation Finished!
Device-Info:
Code:
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
ROM Build: m0xx-user 4.0.4 IMM76D I9300XXALE8 release-keys
Android Version: 4.0.4
BusyBox Version: 1.20.2-Stericson
SU Binary Version: 0.91:SUPERSU
I tried to post in the EFS Pro Thread, but I don't have ther permission to.
So maybe you can help me here?
Yours
Cryptomaniac
I also get this too!
I have the same problem:
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
ROM Build: m0xx-user 4.0.4 IMM76D I9300XXALE8 release-keys
Android Version: 4.0.4
BusyBox Version: 1.20.2-Stericson
SU Binary Version: 0.93:SUPERSU
This error shows up when I choose the img format: (on local and device backup path)
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Failed!
Device MD5 Hash: md5sum: can't open 'mountpoint:'
Backup Data MD5 Hash: md5sum: can't open '/sdcard/EFSP
Error: MD5 Checksum Mismatch!!!
DO NOT USE THIS BACKUP!!!
Operation Finished!
When I choose the tar format or disable the MD5 check the procedure runs through but only creates a faulty file with about 4k size:
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Copying EFS Backup To PC Storage... Okay.
Copied: remote object '/sdcard/EFSProBackup/EFS_201275_185620.img' does not exist
Deleting Temporary EFS Backup From Device... Okay!
Operation Finished!
any help is much appreciated
the new version fixed the problem for me
EFS Pro v1.8.6 has now been released!
Improved Nexus S / Galaxy Nexus Support and fixed the bug that caused the detection of the partition location to fail for some devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1308546
I am facing some issues with my Galaxy Note, I can't write in EFS Pro thread too. I backup my efs with EFS Pro. Now my imei become null and baseband unknown because of flashing roms. I can't restore backup, it show mount point error. Someone help me.
EFS Pro 2.0.12: Unable to Create Archive
I am a new user to EFS Pro, and am using v2.0.12. I tried other older versions, and am getting the same error, and that is when I start the backup, I get an error that it cannot create the archive.
My S3 Tmobile (SGH-T999) is rooted and currently running CM10.1 1/24 nightly. I also enabled USB & ADB debugging. The program accesses the phone OK, it seems that the problem is just in the final saving of the file.
I thought perhaps it was a permission issue with the program not being able to write to my disk, however I have it running with Administrator privileges. I'm stumped. Oh and my O/S is Windows 7 Pro, 64-bit.
grogargh said:
I am a new user to EFS Pro, and am using v2.0.12. I tried other older versions, and am getting the same error, and that is when I start the backup, I get an error that it cannot create the archive.
My S3 Tmobile (SGH-T999) is rooted and currently running CM10.1 1/24 nightly. I also enabled USB & ADB debugging. The program accesses the phone OK, it seems that the problem is just in the final saving of the file.
I thought perhaps it was a permission issue with the program not being able to write to my disk, however I have it running with Administrator privileges. I'm stumped. Oh and my O/S is Windows 7 Pro, 64-bit.
Click to expand...
Click to collapse
I have the same problem. Help please. Thanks!
Edit: solved the problem downgrading busybox to the latest stable version.
BrMBr said:
I have the same problem. Help please. Thanks!
Edit: solved the problem downgrading busybox to the latest stable version.
Click to expand...
Click to collapse
I have the same issue, but the busybox change didn't help
Device Info:
---------- Hardware Information ----------
Connected Device SN.: 3832E63FECEC00EC
Device Manufacturer: SAMSUNG
Device Model: GT-I9000
Product Code: GT-I9000HKDKOR
Hardware Version: MP 0.800
---------- Firmware Information ----------
PDA Version: I9000XXJVQ
Baseband Version: I9000XXJVQ
CSC Version: I9000OXAJVQ
---------- Software Information ----------
Kernel Release: 2.6.35.7-I9000XXJVQ-CL281085
Kernel Version: #DarkCore_2.9.2_JVQ PREEMPT Sat Jul 23 19:19:57 EEST 2011
ROM Build: GT-I9000-user 2.3.4 GINGERBREAD XXJVQ release-keys
Android Version: 2.3.4
BusyBox Version: 1.20.0-Stericson
SU Binary Version: 2.3.1-ef
LOG
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Okay.
Checking backup folder location... Okay.
Backing up selected partition(s)...
Creating archive: GT-I9000_201366_154523.tar.gz...
Operation failed!
Any Idea ?
AROMA/TWRP version of SPFlash Tools.
This tool is for MTK devices with a GPT layout - (MT6732, MT6752 and their variants).
With some testing it may be possible to add some some support for the older devices using an MBR.
Requirements:Copy SPFlash contents to /sdcard/SPFlash
Rename *scatter.txt to scatter.txt
Run .zip from TWRPMTK-64bit_SoCs-v*.zip:During testing there will only be info displayed on screen, nothing should be modified. (Unless otherwise stated)SPFlash-v*.zip:This will install all .img/.bin in SPFlash folder if partition is large enoughDownloads:GDrive FolderChangelogs:SPFlash
v10 - Readded internal sd - fixed aroma exit/about screen - (a few cosmetic issues introduced).
v8 - Aroma menus updated
v7 - Create 'flashable' zip from backed up partitions.
v6 - Zipped backups added
v4 - Backup + Install fixed -- Aroma "Quit Installation" stalls
v3 - Backup function added - untested -- backup works / install from v2 broken
v2 - Menu Select Added
v1 - Initial Release
MTK-64bit_SoCs
v8 - attempts to fix unrelated menu/alert
v7 - calculations done quicker
v6 - script rewrite/reorder
v1 - v5: Initial test builds
Only follow menu Partition Related -> Scatter Information
Other menus/option are broken/dead ends...
Other things in the MTK folder:simg2img/img2simg are arm source compiled binaries to handle sparse files
file/magic were taken from @osm0sis's AIK (I can't seem to get file to compile)
MTKsplit is used to split boot/recovery images into it's individual parts. Normal images will split into 3; 1 = img ANDROID! header, 3 = kernel (zImage) and 5 = ramdisk (ramdisk). MTK images split into 5; 1,3,5 as before with 2 and 4 being additional headers.
XDA:DevDB Information
TWRP/AROMA SPFlasher, Tool/Utility for all devices (see above for details)
Contributors
HypoTurtle
Source Code: https://drive.google.com/open?id=0B8WPOq9wZyKxfktHVWgxbW9nYmtJd1ZWc2RIM1NXUU5pSXpramg0bVBYYUdyRDhid3hwM3c
Version Information
Status: Testing
Current Stable Version: V8
Stable Release Date: 2015-09-03
Created 2015-09-03
Last Updated 2015-09-03
Current StatusMTK-64bit_SoCs-v8 .zip will output the partitions that it deems are incorrectly sized in the scatter.txt and will also check the .img/.bins in the SPFlash folder and determine what should go where and will determine if the partition is large enough for the respective .img/.bin
SPFlash-v1.zip will flash the entire contents of /sdcard/SPFlash folder
SPFlash-v3.zip allows selection of files /sdcard/SPFlash folder to install and has a backup option
Improvements NeededFor SPFlash-v2 will add a basic menu select option for what you want to flash...
In future versions will add backup option and partition resize
Will start to look at resize...
Derivative Work - using scatt and part from #1
ScatterfixGenerating a fixed scatter from a 'broken one'
Code:
[size=1]#!/sbin/sh
ldr=`pwd`
scatterfix(){
scatt \${b} \${c} \${d}
part \${p} \${q} \${r}
scttrbfr=`cat "${scatterloc:-$ldr}/scatter.txt"`
while IFS=" " read -r a b c && read -r d e f <&3; do
if [ $a = $d ]; then
if [[ ! ${b} = "DONT_USE" && ${b} != ${e} ]]; then
scttrafter="${scttrbfr//${b}/${e}}"
scttrbfr=`echo "${scttrafter}"`
fi
if [[ ! ${c} = "DONT_USE" && ${c} != ${f} ]]; then
scttrafter="${scttrbfr//${c}/${f}}"
scttrbfr=`echo "${scttrafter}"`
fi
fi
echo "${scttrbfr}" > ${scatterloc:-$ldr}/scatter-new.txt
done </tmp/scatter 3</tmp/parted-new
}
scatterfix
diff ${scatterloc:-$ldr}/scatter.txt ${scatterloc:-$ldr}/scatter-new.txt[/size]
Problems to fixThe code will change any hex value deemed wrong to a new calculated value - there is a chance that 4 values are the same but only one/two are wrong - to fix will need to add a loop through scatterfix until the scatter-new.txt generated is actually correct.Resize Userdata/IntsdMore of a precursor - bugs fixed and maintained by @odigitech
Thread located here
Some Dev. QuestionsBefore adding the resizing partitions (Firmware Upgrade) option:
1. Is the preloader header custom or generic; and does it change when flashing the proloader?
2. Is there an actual function to the BPLGU/APDB files other than some sort of device/system check?
For v7 trying to add a backup + make installable zip option:
Have done it with basic dd backups; would prefer to use sparse/simg2img but simgimg can't seem to use zipped .img's; have looked into using dat/sdat2img but that would require getting python to run in recovery (unless I'm mistaken).
Have added the simplistic option as v7...
odigitech said:
@HypoTurtle I have made a modified version of MTKsplit with more human-friendly names, its in my Drive folder, if it's any use.
Click to expand...
Click to collapse
Thanks, I have updated mine to support non-MTK header-ed boot/recovery.imgs -- can't hurt to make it human readable I suppose.
MTKsplit will be used in the next uploaded version (v8) in the form of a simplistic porting tool...
Should be uploaded on Monday/Tuesday
odigitech said:
You made it work for non-MTK also? Nice one, is it on your Drive?
Sent from my thl 2015 using XDA Free mobile app
Click to expand...
Click to collapse
Should be... but I'll update it with the human-readable version now.
It's not vigorously tested; and not as robust as the (un)mkbootimg binaries out there but it seems to do the job.
@HypoTurtle: on my Jiayu s3, the Germans have been working on android 5.1.1 for it and so far it is great. I installed beta 3 and the next day they released beta 4. Rather then getting out the laptop, I thought I'd use your script, so I got the files needed, I got your script and set it up as the instructions. But when I ran the script, it didn't find the system.img file, and didn't give it to me as an option. I verified that the file was there on disk, but I was never given a check box to select it for flashing. Any logs I can send you to try and figure out why?
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
@HypoTurtle: on my Jiayu s3, the Germans have been working on android 5.1.1 for it and so far it is great. I installed beta 3 and the next day they released beta 4. Rather then getting out the laptop, I thought I'd use your script, so I got the files needed, I got your script and set it up as the instructions. But when I ran the script, it didn't find the system.img file, and didn't give it to me as an option. I verified that the file was there on disk, but I was never given a check box to select it for flashing. Any logs I can send you to try and figure out why?
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is it just the system.img that doesn't appear? And are you using internal or external SD?
HypoTurtle said:
Is it just the system.img that doesn't appear? And are you using internal or external SD?
Click to expand...
Click to collapse
Just system.img, and external_sd
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Just system.img, and external_sd
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you post the scatter; the menu items are just an existence check.
[ if *.img/*.bin from scatter exists in SPFlash folder then you are given the option to flash it ]
(Just noticed that it will stall if you try and install and there are no valid img/bin files present)
HypoTurtle said:
Can you post the scatter; the menu items are just an existence check.
[ if *.img/*.bin from scatter exists in SPFlash folder then you are given the option to flash it ]
(Just noticed that it will stall if you try and install and there are no valid img/bin files present)
Click to expand...
Click to collapse
Screenshot of the folder, and the scatter. I checked it and it looked fine.
AlexZap said:
Screenshot of the folder, and the scatter. I checked it and it looked fine.
Click to expand...
Click to collapse
Ah yes - this problem is caused by the amount of items shown - I have it set to show 3, 5 or 12. It will only show 12 (more than 5) if there are 12 things to flash. From your screenshot you have 7 items to be flashed (trustzone gets flashed twice), so you will miss two items - the second flash of trustzone.bin and system.img.
Hope that makes sense; I can alter it to work with 6+; but you should be able to adjust it to work as described above. the reason I did it this way was that otherwise it would look a bit messy - I suppose I could add a 7 option.
HypoTurtle said:
Ah yes - this problem is caused by the amount of items shown - I have it set to show 3, 5 or 12. It will only show 12 (more than 5) if there are 12 things to flash. From your screenshot you have 7 items to be flashed (trustzone gets flashed twice), so you will miss two items - the second flash of trustzone.bin and system.img.
Hope that makes sense; I can alter it to work with 6+; but you should be able to adjust it to work as described above. the reason I did it this way was that otherwise it would look a bit messy - I suppose I could add a 7 option.
Click to expand...
Click to collapse
Ahhh... Not a. Problem then. I don't really need to flash anything besides system and boot. I just included the rest for completness. I'll take one out and let you know how it goes.
On a side note, any reason for these (3, 5, and 12)? An not just everything that is there?
Sent from my JY-S3 using XDA Premium 4 mobile app
HypoTurtle said:
Some Dev. QuestionsBefore adding the resizing partitions (Firmware Upgrade) option:
Q1. Is the preloader header custom or generic; and does it change when flashing the proloader?
Q2. Is there an actual function to the BPLGU/APDB files other than some sort of device/system check?
Click to expand...
Click to collapse
A1 - Generic, MTK preloader has been the same since armv7 to armv8. Yes, dd backup copy needs to be clean up of the header & footer, more info then checkout with AlexZap... :good:
A2 - Not all MTK firmware include it, it contains the IMEI refer to here for more info or a single link that explained everything... :good:
AlexZap said:
Ahhh... Not a. Problem then. I don't really need to flash anything besides system and boot. I just included the rest for completness. I'll take one out and let you know how it goes.
On a side note, any reason for these (3, 5, and 12)? An not just everything that is there?
Sent from my JY-S3 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure if you missed the edit. It was more for cosmetic reasons - I could have had say 12 files being displayed but if there's only one file to flash you would have a screen with a lot of blank entries. 3, 5 and 12 seemed the most appropriate without going down the route of creating a menu for all possible entries.
3 being typical install (system/boot and perhaps blank cache/userdata to wipe); 5 as 3 but with custom etc.
I figured that anyone with more than 5 flashable items in there would have dumped the entire SPFlash ROM which I calculated as ~12 items.
yuweng said:
A1 - Generic, MTK preloader has been the same since armv7 to armv8. Yes, dd backup copy needs to be clean up of the header & footer, more info then checkout with AlexZap... :good:
A2 - Not all MTK firmware include it, it contains the IMEI refer to here for more info or a single link that explained everything... :good:
Click to expand...
Click to collapse
A2. I don't thing it contains the IMEI - but it is the database that the IMEI is coded against; I'm not aware of any devices (other than the P6000) suggesting that you recode the IMEI on an upgrade from KK to LP so there is probably not an issue here.
i never use it myself, typically MDRT is able to recover it on mine, feedbacks from fellow XDA member is that, that is the only way that they manage to recover IMEI on their MTK...
On 2nd thought, BTW, i'm using intel nowadays :laugh: IMEI & calibration info is at a hidden partition, same as Samsung & Qualcomm devices that reside at /efs partition, how did MTK IMEI survive Factory Reset since it is at /data/nvram, i wonder, never really thought about it...
yuweng said:
i never use it myself, typically MDRT is able to recover it on mine, feedbacks from fellow XDA member is that, that is the only way that they manage to recover IMEI on their MTK...
On 2nd thought, BTW, i'm using intel nowadays :laugh: IMEI & calibration info is at a hidden partition, same as Samsung & Qualcomm devices that reside at /efs partition, how did MTK IMEI survive Factory Reset since it is at /data/nvram, i wonder, never really thought about it...
Click to expand...
Click to collapse
On the 64bits at least it is also on a hidden partition (nvram) - and it just gets copied to /data/nvram or something (ie. its not mounted but it's files are there). The DB files etc are present in /system as well as in the full SPFlash ROM so I guess things like MTKEng and apps like chamelephon use that when setting/'fixing' the IMEI.
What are the file formats used by intel stock ROMS? This tool isn't really MTK dependant - it's GPT partition dependant (with a scatter for validity check- I'll post a bear minimum of what a 'scatter.txt' needs to have).
Anyway v8 added - so that files to flash aren't hidden (max. 12 files).
Hmm, further digging seems MTK IMEI is at /dev/nvram, same thing happening on intel, users just never spell out everything, they use the format/ erase flash/ emmc that wipes out the IMEI partition but never tell...
i think on the X3, its not possible as its NOT an Android image file but proprietary fls file which they got it when they acquire infineon i think...
Manual fastboot/ dd backup/ restore & you'll end up with a brick device, ATM, no custom recoveries that boot on the x3, i haven't figure out how to repack its recovery that has three separate different region that requires three proprietary download file that packs it together into a fls file & only their FlashTool_E2 is able to download it correctly...
Can't really understand infineon/ intel for developing such cheap device but with such high end software tools...
Hello XDA, longtime reader, first time poster.
I tried flashing a custom ROM the other day, but something went wrong, and I now have a device that bootloops (unlocked screen, SONY logo, followed by a "the software update failed" message). I think the cause of all of this came from a few missing drivers that Flashtool/Windows 7 didn't install properly. I'm not sure if this matters, but this happened after trying to update to the latest stock nougat firmware (downloaded via Xperifirm) from a custom 6.0.1 ROM.
I went through as many solution threads as possible, but I'm still having trouble. The last thing I did just before this post was create an ftf via Flashtool, added "41.fsc" script when asked, prepared flash with full wipe/no exclusions, connected phone to USB via Flash Mode, selected F83XX when prompted for device, and this was the log I received...
29/021/2017 00:21:58 - INFO - Device connected in flash mode
29/021/2017 00:21:59 - INFO - Opening device for R/W
29/022/2017 00:22:00 - INFO - Reading device information
29/022/2017 00:22:00 - INFO - Phone ready for flashmode operations.
29/022/2017 00:22:00 - INFO - Opening TA partition 2
29/022/2017 00:22:00 - INFO - Start Flashing
29/022/2017 00:22:00 - INFO - No loader in the bundle. Searching for one
29/022/2017 00:22:44 - INFO - No matching loader found
29/022/2017 00:22:44 - WARN - No loader found or set manually. Skipping loader
29/022/2017 00:22:44 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_40 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_40 / Bootloader status : ROOTED
29/022/2017 00:22:44 - INFO - Max packet size set to 4M
29/022/2017 00:22:44 - INFO - USB buffer size set to 512K
29/022/2017 00:22:54 - INFO - Parsing boot delivery
29/022/2017 00:22:54 - INFO - Found a template session. Using it : C:\Users\[name]\.flashTool\firmwares\prepared\41.fsc
29/022/2017 00:22:54 - INFO - Set loader configuration : [00 01 00 00 00 0C]
29/022/2017 00:22:54 - INFO - Flashing finished.
29/022/2017 00:22:54 - INFO - Please unplug and start your phone
29/022/2017 00:22:54 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Extra information...
PC
- Windows 7 64-bit
- Flashtool 0.9.23.2 installed
- As far as I know, every driver I need has been downloaded and installed (Sony's website, Flashtool-drivers.exe)
(↑ "Sony sa0115 ADB Interface Driver" under Device Manager reads "This device cannot start. (Code 10)", if that makes any difference)
- Xperia Companion doesn't detect my phone, so I can't use their "software repair" option
Phone
- F8332
- Bootloader unlocked
- *Backup TA missing*
- Device rooted
- TWRP 3.1.1-0 installed
- Android 6.0.1 (firmware unknown)
Files
- Latest Nougat firmware (F8332_Customized FR_1305-9679_41.2.A.7.76_R1D) -- folder only (ftf can be created anytime, just need to know what to keep/exclude. I've been seeing different answers regarding when to add "41.fsc" to ftf (before/after flashing, or adding at all), and excluding .sin files before flashing, so if anyone has a definite answer to these, I'd really appreciate it.)
Otherwise, if none of that matters and the problem lies somewhere else, I'm all ears.
Thank you in advance.
@simpleflips
wow - your post should stand out as a prototype for HOW TO ASK FOR HELP!
I had the same problem recently when trying to flash my F8331 under Windows 10. Did not try Linux on the same machine since there are some issues with Mono here.
My drivers where not giving me any clues (PC-Manager, logging under Windows?).
So I dug out my spare laptop (Win 7 bitness?): installed the XZ-driver and it worked there after a full wipe in TWRP (I had encrypted the device and TWRP did not take the key properly).
You can try the drivers I link in my Guide.
Under both Windows installations I had no problems with adb and fastboot.
So I can only guess that my "solution" was the full wipe or some unkwon differences in driver magic between the notebooks used.
@DHGE
Apologies for the delay, thank you for the words and response. I should've noted that before my OP and bootloop, I tried to flash the custom Nougat ROM via TWRP, but got an error. (Zip file is corrupt! Error installing zip file '/sdcard1/[rom].zip') (Tested after transferring the file via AirDroid, don't remember if I even downloaded directly from my phone.) Now if I run a full wipe through TWRP and re-flash the original 6.0.1 ROM that's in my microSD, it *does* install, but bootloop still exists. I tried wiping/flashing the custom ROM via fastboot out of curiosity, and received the following:
wipe (entered bootloader mode from my Downloads folder, where the ROM is found)
C:\Users\[name]\Downloads>fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (status read failed (Too many open files in system))
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command failed (Invalid argument))
erasing 'userdata'...
FAILED (command write failed (No such device or address))
finished. total time: 0.020s
(Afterward, I get a message saying fastboot.exe has stopped working. Not on Minimal ADB, though.)
flash
C:\Users\[name]\Downloads>fastboot update [rom].zip
'archive does not contain 'android-info.txt' ,
error: update package '[rom].zip' has no android-info.txt
Do these errors relate with each other? Was my file just not downloaded properly?
Regarding the drivers, I downloaded the official Xperia XZ ADB interface driver (Sony sa0115) from SONY's website, and installed via Device Manager, but get the Code 10 Error mentioned in OP. According to some user posts, the solution was changing their phone's USB configuration to MIDI, afterward Windows would properly detect and install the Sony sa0115 driver. (I reckon that's not possible on a soft bricked device, is it...?) No devices are found after entering adb devices in command prompt, so I'm going to presume installing/flashing anything via ADB is out of the question. Right now, Device Manager shows 2 devices-- One of them being the actual XZ when connected in fastboot mode (labeled "Android Phone"), the other being the Sony sa0115 driver I downloaded/installed. The trick now is mounting the two together.
At this point, fastboot/TWRP seem to be the only way out of this. The custom ROM notes that no kernel flashing is necessary, but your guide includes a link to the AndroPlus kernels (for stock, and other roms, I take it). Unfortunately, until I figure out how to properly flash the firmware via Flashtool, AndroPlus will have to wait. (Unless there's a way to find out what firmware my phone is using right now.) The next option is to directly send the custom 7.1.1 ROM from my PC to the microSD card, but I can't find my SD card adapter right now, so I'll update later this week.
simpleflips said:
@DHGE
At this point, fastboot/TWRP seem to be the only way out of this
Click to expand...
Click to collapse
Unfortunately this is not a way out. And what you wrote above sounds rather weird for me...
The only way out is to flash a SONY ROM properly. THE tool for this is flashtool.
There are some mentions of SONY's recovery tool(s?) but last time I tried one I could not get it to work. Flashtool to my rescue.
Maybe you can take your phone to a qualified repair shop and they flash you a SONY ROM.
Hello, recently I looked into LG backup and restore application using static analysis.
Note: this is based on version lg bnr 8.0.26 from 2020-02-13, tested with 7.0.20 from 2008-12-31
Here is the extract tool:
https://github.com/Mysak0CZ/LBFtool
And here is the technical part (you don't need to read this, if you just want to extract your data):
The file contains 2 headers (one of them is referred to as "new")
These are XML documents encrypted using AES/ECB/PKCS5Padding + SHA256 and null IV with static password
Code:
cd562f61-5399-3978-ac76-7c54b0508010
And they look like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<BackUp>
<Common>
<Name>LGBackup_200217_1</Name> <!-- Name of the backup file -->
<Id>Randomly generated UUID</Id> <!-- Id of the backup file -->
<IsNew>True</IsNew> <!-- IsNew is same in new and old header -->
<Version>1.00</Version>
<Attr Name="product_model">LM-X525</Attr>
<Attr Name="os_version">9</Attr>
<!-- And other attributes including google email -->
</Common>
<BackupItem Category="settings_DB" StartOffset="59392" DataSize="136626" />
<BackupItem Category="MEDIA_DB" StartOffset="901169" DataSize="78393344" FileName="external.db" />
<!-- Other backuped items -->
</BackUp>
The "new" header has more information than original header, but same structure.
The attribute "IsNew" signals the presence of the new header. (and is True in both files)
All numbers inside file are in Big-endian.
And this is the structure of the file (decimal position):
Code:
0: Unknown - 0x00 for me
1: Int32 - size of the new header
5: Int64 - offset to the new header (usually 13)
13 ... EOF-33: data
EOF-33: 20 bytes - SHA1 hash of the password (if present, otherwise still data)
EOF-13: Int64 - offset to the (old) header
EOF-5: Int32 - size of the (old) header
EOF-1: Bool - Lock byte - the file is (0x01) or isn't (0x00) protected by password
The password is only checked during import, not used to encrypt data (so to remove password, just set the last byte to 0)
Every "BackupItem" entry has a "Category".
Special case is Category="APPLICATION" with this structure:
Code:
<BackupItem Category="APPLICATION">
<APPLICATION Name="com.lge.ime" StartOffset="19221586" DataSize="2385983" Package="com.lge.ime">
<Attr Name="com.lge.ime">com.lge.ime</Attr>
</APPLICATION>
<APPLICATION Name="org.exmple.app" StartOffset="1429652009" DataSize="3420160" FileName="org.exmple.app.tar" Package="org.exmple.app">
<Attr Name="org.exmple.app">org.exmple.app</Attr>
</APPLICATION>
<!-- ... -->
</BackupItem>
All applications are tar files that contain 2 folders:
app - contains the apk file
data - application's internal data
All other items have:
StartOffset - Offset inside file
DataSize - Self explanatory
FileName - Not all have this, but most do; it is the original name of the backuped file.
The files are not compressed nor encrypted.
Footnote: This is my first post on XDA, so sorry for any mistakes I made (including my english) and feel free to correct me/give me advice.
Mysak0CZ said:
Hello, recently I looked into LG backup and restore application using static analysis.
Note: this is based on version lg bnr 8.0.26 from 2020-02-13, tested with 7.0.20 from 2008-12-31
Here is the extract tool:
And here is the technical part (you don't need to read this, if you just want to extract your data):
The file contains 2 headers (one of them is referred to as "new")
These are XML documents encrypted using AES/ECB/PKCS5Padding + SHA256 and null IV with static password
And they look like this:
The "new" header has more information than original header, but same structure.
The attribute "IsNew" signals the presence of the new header. (and is True in both files)
All numbers inside file are in Big-endian.
And this is the structure of the file (decimal position):
The password is only checked during import, not used to encrypt data (so to remove password, just set the last byte to 0)
Every "BackupItem" entry has a "Category".
Special case is Category="APPLICATION" with this structure:
All applications are tar files that contain 2 folders:
app - contains the apk file
data - application's internal data
All other items have:
StartOffset - Offset inside file
DataSize - Self explanatory
FileName - Not all have this, but most do; it is the original name of the backuped file.
The files are not compressed nor encrypted.
Footnote: This is my first post on XDA, so sorry for any mistakes I made (including my english) and feel free to correct me/give me advice.
Click to expand...
Click to collapse
Nice job dude! just a the quick recommendation: I would suggest that you put your code on gitlab or GitHub so it will become easier for others to contribute
Sent from my OnePlus 6T using XDA Labs
Hi. I'm trying to use this tool but I don't know how to use it. I followed the instructions and downloaded Python. but none of the other steps are working for me. I have my backup on my PC and am trying to extract my files into normal formats as I wish to move away from the LG platform. Thank you.
---------- Post added at 07:20 AM ---------- Previous post was at 06:57 AM ----------
Nevermind, I found a work around.
For anyone else in the future wondering: If you select backup with the app on the phone and backup to the internal memory, it will create .pdf files of all text/images in internal storage>>Quickmemo+. This doesn't help to retrieve the audio or video recordings, but at least that way you can retrieve your text files/images.
Tried script on old backup, failed with error.
Mysak0CZ said:
Hello, recently I looked into LG backup and restore application using static analysis.
Note: this is based on version lg bnr 8.0.26 from 2020-02-13, tested with 7.0.20 from 2008-12-31
Here is the extract tool:
And here is the technical part (you don't need to read this, if you just want to extract your data):
The file contains 2 headers (one of them is referred to as "new")
These are XML documents encrypted using AES/ECB/PKCS5Padding + SHA256 and null IV with static password
Code:
cd562f61-5399-3978-ac76-7c54b0508010
...
[/CODE]
All applications are tar files that contain 2 folders:
app - contains the apk file
data - application's internal data
All other items have:
StartOffset - Offset inside file
DataSize - Self explanatory
FileName - Not all have this, but most do; it is the original name of the backuped file.
The files are not compressed nor encrypted.
Footnote: This is my first post on XDA, so sorry for any mistakes I made (including my english) and feel free to correct me/give me advice.
Click to expand...
Click to collapse
My first post as well. Thanks for the script. I ran it on an old backup I was hoping to extract contacts from. See excerpt with error below.
C:\Temp\LG G4\Backup>python extract.py LGBackup_190218.lbf
[+] Backup size: 597864605
Parsing...
Reading header
[*] Header start offset: 597792768
[*] Header length: 71824
[+] Header read OK
Reading header (new)
[*] Header start offset: 7021235167904623918
Traceback (most recent call last):
File "extract.py", line 125, in <module>
root = readHeader(True)
File "extract.py", line 99, in readHeader
size = getBackupInfoSize(isNew)
File "extract.py", line 88, in getBackupInfoSize
raise Exception("Invalid header length.")
Exception: Invalid header length.
C:\Temp\LG G4\Backup>
Click to expand...
Click to collapse
I'm a complete newbie with Python, haven't done any coding in over a decade. Where do I go from here?
Ninja_Toad said:
My first post as well. Thanks for the script. I ran it on an old backup I was hoping to extract contacts from. See excerpt with error below.
I'm a complete newbie with Python, haven't done any coding in over a decade. Where do I go from here?
Click to expand...
Click to collapse
Hi! Your backup seem to be at least partially corrupted. (The new header position seems to start at 7021235167904623918, however the file is only 597864605 bytes long). Fortunatly there are two headers in the backup and the old one seems to be ok (You got "[+] Header read OK" for the old header). So you can try ignoring the "new" header.
To ignore the faulty header just set the relevant "FORCE_*_HEADER" to True in the script header. In your case just set "FORCE_OLD_HEADER = True".
Also note, that extracting contacts in readable format is beyond this script's current scope. This can however be done manually. After you get your data successfully extracted, look for export/data/contacts_DB file. This is a TAR file in which you need to find file "data/data/user/0/com.android.providers.contacts/databases/contacts2.db". This is the contact database as your phone stores it. To actually extract the contacts, you will need to find a way to convert the database to some other format (I have't looked into how the contacts are stored, you will need to do your own googling)
Files extracted but...
hello guys,
I also managed to extract my files using the hack mentioned above (force old headers to TRUE) since by using the default script i was also getting a similar error as above.
However now all of my files (pictures in particular) are corrupted and i cannot seem to be able to open them using several editors.
Anyone else had the same issue?
Thanks in advance!
serlal said:
hello guys,
I also managed to extract my files using the hack mentioned above (force old headers to TRUE) since by using the default script i was also getting a similar error as above.
However now all of my files (pictures in particular) are corrupted and i cannot seem to be able to open them using several editors.
Anyone else had the same issue?
Thanks in advance!
Click to expand...
Click to collapse
Yes I have exactly same issue as you have. All exported files cannot be read.
Hello @tking2000 and @serlal, this script was written based on versions that are available to me. There are two possibilities of what is happening:
1) The file was badly corruped, however the old header stayed itact. (This is the likely case, if you are trying this tool because your phone refused to restore the backup)
2) The file was made by version that does something differently and the script doesn't account for it.
In the first case there is nothing anyone can do (short of trying some corrupted file recovery software hoping the corruption is only minor)
In the second case, you can try sending me a PM with following information, so I can have a look and confirm whether this is truly the case (and improve the script)
1) The script's output
2a) The <Version> and <Attr Name="settingVersionName"> from the <Common> part of the header
2b) If you aren't concerned about privacy or it is just easier for you: just send the whole header file
3) The version of the com.lge.bnr app (LG Mobile Switch); this is not necessary, but may help me
Feel free to censor anything you are sending with [CENSORED] (like your email or filenames)
I have no experience with python, but I have one of these lbf files and I'm trying to figure out how to make it work and all I get is couldn't get library pycryptodome. How do I get Python 3.8.3 to get this library?
Multipart backups
Hello everyone,
I just finished an update, that should enable the tool to extract backups that have multiple files.
If you received "Exception: Invalid header length." in the past and your backup has multiple files, try the script now; your backups are likely to extract correctly now.
This is the likely case for: @Ninja_Toad @serlal and @tking2000
This was made possible thanks to @cheesyzombie who sent me the data I asked for.
@kamikazkid, You don't need to know Python to use this tool, the easiest way is to enter the commands in quotes on the github page into the console (To open the console Shift+Right click in the folder with backups and choose "Open command window here").
Just:
Download the zip on the github page (Under "Code" button)
Make sure the extract.py and your backup are in the same folder
Follow the usage, skip the 4th step and replace xxxxxx to match your backup name.
I figured it out, it was something with windows 10 and the version of python installation I used. Microsoft garbaging things up as usual, thanks for the help though. Thanks, I recovered my files from my old phone successfully.
I have no experience withc++, but I have one of these lbf files and I'm trying to figure out how to make it work, it is a great this forum
Is there a way to import the _DB files (contacts, messages, call logs etc.) back to a phone?
I asked before:
https://forum.xda-developers.com/lg-g3/general/restore-backup-lbf-lineage-17-t4172483#post83644281
Thank you so much for this! I was able to extract the Messaging data from an LG G8 ThinQ. Does anybody know the easiest way to view that data on my PC?
Hi, you can follow these steps to extract data fron _db files:
1) Send the _db files like contacts_db, messages_db to any android phone
2) Double tap on the file and open it using File Manager (which is by default on Mi phones)
3) The file will now open as a folder. Continue opening the folders until you reach to the last file.
4) The last file is the database file. It won't open directly. Select the file and extract the file.
5) Now transfer the file to computer and you can now view it using SQLite DB Browser if its a contacts file or you can use any VMG reader if its a messages file.
Hope this helps you.
Hi @Mysak0CZ, just follow your instructions on GitHub but when I run the command on Command Prompt, nothing happens. Just like this:
F:\>python -m pip install pycryptodome
F:\>python extract.py LGBackup-201031.lbf
When I enter nothing happened. Kindly help to advise for this.
Thank you
Problem in powershell
Mysak0CZ said:
Hi! Your backup seem to be at least partially corrupted. (The new header position seems to start at 7021235167904623918, however the file is only 597864605 bytes long). Fortunatly there are two headers in the backup and the old one seems to be ok (You got "[+] Header read OK" for the old header). So you can try ignoring the "new" header.
To ignore the faulty header just set the relevant "FORCE_*_HEADER" to True in the script header. In your case just set "FORCE_OLD_HEADER = True".
Also note, that extracting contacts in readable format is beyond this script's current scope. This can however be done manually. After you get your data successfully extracted, look for export/data/contacts_DB file. This is a TAR file in which you need to find file "data/data/user/0/com.android.providers.contacts/databases/contacts2.db". This is the contact database as your phone stores it. To actually extract the contacts, you will need to find a way to convert the database to some other format (I have't looked into how the contacts are stored, you will need to do your own googling)
Click to expand...
Click to collapse
Hi, I am trying to extract via your method but in the power shell in sending the command "python extract.py LGBackup_1x0x07.lbf" it does not execute and brings me back the initial path line. Do you have solutions in this regard? Thanks in advance
Ps. I use Win10
Worked so well. I only needed to recover images and audio recordings after realizing that LG backup tool won't restore on other brand phones.
Thank you!!
Mysak0CZ said:
Hello, recently I looked into LG backup and restore application using static analysis.
Note: this is based on version lg bnr 8.0.26 from 2020-02-13, tested with 7.0.20 from 2008-12-31
Here is the extract tool:
https://github.com/Mysak0CZ/LBFtool
And here is the technical part (you don't need to read this, if you just want to extract your data):
The file contains 2 headers (one of them is referred to as "new")
These are XML documents encrypted using AES/ECB/PKCS5Padding + SHA256 and null IV with static password
Code:
cd562f61-5399-3978-ac76-7c54b0508010
And they look like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<BackUp>
<Common>
<Name>LGBackup_200217_1</Name> <!-- Name of the backup file -->
<Id>Randomly generated UUID</Id> <!-- Id of the backup file -->
<IsNew>True</IsNew> <!-- IsNew is same in new and old header -->
<Version>1.00</Version>
<Attr Name="product_model">LM-X525</Attr>
<Attr Name="os_version">9</Attr>
<!-- And other attributes including google email -->
</Common>
<BackupItem Category="settings_DB" StartOffset="59392" DataSize="136626" />
<BackupItem Category="MEDIA_DB" StartOffset="901169" DataSize="78393344" FileName="external.db" />
<!-- Other backuped items -->
</BackUp>
The "new" header has more information than original header, but same structure.
The attribute "IsNew" signals the presence of the new header. (and is True in both files)
All numbers inside file are in Big-endian.
And this is the structure of the file (decimal position):
Code:
0: Unknown - 0x00 for me
1: Int32 - size of the new header
5: Int64 - offset to the new header (usually 13)
13 ... EOF-33: data
EOF-33: 20 bytes - SHA1 hash of the password (if present, otherwise still data)
EOF-13: Int64 - offset to the (old) header
EOF-5: Int32 - size of the (old) header
EOF-1: Bool - Lock byte - the file is (0x01) or isn't (0x00) protected by password
The password is only checked during import, not used to encrypt data (so to remove password, just set the last byte to 0)
Every "BackupItem" entry has a "Category".
Special case is Category="APPLICATION" with this structure:
Code:
<BackupItem Category="APPLICATION">
<APPLICATION Name="com.lge.ime" StartOffset="19221586" DataSize="2385983" Package="com.lge.ime">
<Attr Name="com.lge.ime">com.lge.ime</Attr>
</APPLICATION>
<APPLICATION Name="org.exmple.app" StartOffset="1429652009" DataSize="3420160" FileName="org.exmple.app.tar" Package="org.exmple.app">
<Attr Name="org.exmple.app">org.exmple.app</Attr>
</APPLICATION>
<!-- ... -->
</BackupItem>
All applications are tar files that contain 2 folders:
app - contains the apk file
data - application's internal data
All other items have:
StartOffset - Offset inside file
DataSize - Self explanatory
FileName - Not all have this, but most do; it is the original name of the backuped file.
The files are not compressed nor encrypted.
Footnote: This is my first post on XDA, so sorry for any mistakes I made (including my english) and feel free to correct me/give me advice.
Click to expand...
Click to collapse
ok I am so lost. And here is the technical part (you don't need to read this, if you just want to extract your data):
that statement would make it appear easy. well the link only takes you to the code, there is no tool and nothing with "new" as header. so ive tried deciphering what to do for hours now and i cant figure npthing out. rooted and flashed my lgv20 and did a backup with lg bridge beforehand. trying to restore and phone connects to computer fine but doesnt regster in lg bridge so that is why i need to extract .lbf file. can someone make this easier?
hello..it ended up successful.but there is no jpeg or mp4 file on DCIM folder..how can i restore them?should i do somthing with the script? i don't know pyton
I was trying to enable the privacy wifi feature that changes the MAC address of the wifi adapter on every connection (see https://github.com/phhusson/vendor_hardware_overlay/pull/610 as an alternative to https://github.com/Magisk-Modules-Alt-Repo/MacRandomizationEnabler).
While doing this, I encountered an issue that all of a sudden, the phone would not connect to cellular (IMEIs were gone) and GPS would not work anymore. This is quite frustrating and could essentially render your phone unusable with respect to its main functionality.
I was not aware of the fact an efs backup is required. However, I had backed up efs and sec_efs right after the problem.
I also found that the problem could occur just due to the use of Magisk (after some weeks).
The public documentation on efs in general is already sparse, but the one for the Exynos based models is close to non-existent from what I found. That's why I thought I would share my journey and findings.
This is how I went ahead to restore the functionality. In particular, due to the Exynos chip, things are different to other tutorials which either rely on MediaTek or Qualcomm chipsets, which store the NVRAM (responsible for IMEI, ...) in a different way (not in Samsungs own encrypted and obfuscated .bin format) and have more accessible ways of setting IMEI (via serial console, external tools, ...). There, the restore process is different.
Prerequisites
Backup (potentially corrupted) of efs and sec_efs
TWRP
How to proceed
Code:
- Remove any root app that might infringe with the "efs" data, such as MAC address changers, ...
- Restore both "efs" and "sec_efs" partitions with TWRP (with no intermediate reboot)
In my case, the most recent "nv_data.bin" inside the "efs" backup was corrupt (as I backed it up AFTER the corruption), so I needed to continue as follows
Code:
- Do not reboot to system directly after restore
- In TWRP, reboot to "fastboot" and enter ADB
- Run "adb shell"
- cd /mnt
- mkdir test
- mount /dev/block/by-name/efs test
- cd test
- ls -al
in addition to "nv.log" (just a log file), "nv_data.bin", "nv_data.bin.md5" (the corrupted ones), ensure there is also ".nv_data.bak", ".nv_data.bak.md5" (the timestamps of which were in the future, but that's ok)
- mv nv_data.bin nv_data_corrupt.bin
- mv nv_data.bin.md5 nv_data_corrupt.bin.md5
this will cause "nv_data.bin" and "nv_data.bin.md5" to be restored from the ".nv_data.bak", ".nv_data.bak.md5" files on the next reboot, observe this later in the "nv.log" by the following lines
[none]DATE:Not exist secure efs
[none]DATE:Nv restored 3
- cd ..
- umount test
- rmdir test
- Turn the phone FULLY off
- Reboot
- Cellular connectivity and GPS should be working again!
- Make an immediate backup of "efs" and "sec_efs"
In theory, you should also backup "persist", but I didn't find a corresponding partition.
- (Optional) Remove the corrupt ".bin" and ".bin.md5" files in "efs"
I hope this gives some insights on nv_data on Exynos chips and potentially helps anybody in a similar situation.
Spoiler: Useful resources that helped me along my journey
Fix for missing IMEI & Baseband
https://forum.xda-developers.com/t/imei.4419517/#post-86621473 Thanks to @MauriJ2001 for suggesting this guide. It worked for A12 too. I am currently on BVB4 firmware version with IMEI & Baseband working. Hopefully it works for everyone else tho.
forum.xda-developers.com
Imei
I lost imei/baseband after flashing stock ROM Build number: A125FXXU2BVB4
forum.xda-developers.com
[fixed] rooted a325m suddenly no imei, no sim
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now...
forum.xda-developers.com
Need nvram donors
We need a donor nvram. All you need is files: nvram.bin, nvdata. img, persist. img, nvcfg. img, protect1. img, protect2. img, as well as pc. Goal: We will not take your imei. The most important thing for us is to understand what imei format miui...
forum.xda-developers.com
Wifi don't work? Flash this! /Persist Repair
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions). Before this zip, you have to copy the...
forum.xda-developers.com
reverse-engineering nv_data.bin
I have a rooted Galaxy Nexus GSM (Maguro) running ClockworkMod and the stable version of CM9. I've been trying to find out how exactly the IMEI is stored --- whether it's baked into the radio component or whether it's controllable from firmware...
forum.xda-developers.com
Docomo SIM unlock: Jup's Grand Theory of Permanent SIM Unlock
This theory now seems to be confirmed by number of successful applications & my additional research. It should be generally safe to try both experiments. However, it still requires you know basics of shell. Above all, backup. And as allways, I am...
forum.xda-developers.com
[SOLVED] suddenly unknown imei
ok so, i was using my phone normally yesterday, but out of nowhere, my SIM card stopped working and i couldn't use mobile internet/calls anymore. So i checked my settings and i saw my IMEI was marked as unknown, the same with baseband. The A32...
forum.xda-developers.com
[Fixed] Repair IMEI and fix deleted EFS folder for Note10+ N975F
Hi bros First of all I am not a developer, the EFS folder of my Note10+ was deleted by mistake and I lost my IMEI numbers, after a lot of concern, researches and tests I fixed my Note10+ and I want to share my very hard and bad experience maybe...
forum.xda-developers.com
Lost my efs backup.. can I use another one?
So basically I dont have my efs backup.. and twrp messed up my efs partition.. Is it possible to use another efs?
forum.xda-developers.com
How to mount TWRP backup files in Linux
Hello, I want to inspect backup files create by TWRP backup. The file structure is this: $ ll /mnt/HD403LJ/oneplus5t/TWRP/BACKUPS/b94a5888/2019-05-27--00-44-45 .rwxr-xr-x root root 1.0 MB Fri Apr 3 20:13:36 2020 bluetooth.emmc.win .rwxr-xr-x...
forum.xda-developers.com
[V1.0]01.05.14 EFS/IMEI Tool G900M/F/T Cmplete backup EFS + Modemst1 and 2 - Galaxy S 5 Android Development (Snapdragon)
[V1.0]01.05.14 EFS/IMEI Tool G900M/F/T Cmplete backup EFS + Modemst1 and 2 - Galaxy S 5 Android Development (Snapdragon)
www.bettermobileapp.com
subject:"\[Replicant\] \[libsamsung\-ipc\] \[PATCH\] nv_data\-imei\: indicate that write\-imei may or may not work"
[HOW-TO] Sim-Unlock via nv_data.bin!
Also den xdaLeuten hats geholfen! Ich dachte mir ich übersetze es für euch! Edit: Hier gibt's eine App die das ganze erleichtern soll: https://play.google.com/store/apps/details?id=org.projectvoodoo.simunlock&hl=de ALS ERSTES: Android Hilfe.de und Ich übernehmen keine Haftung wenn etwas schief...
www.android-hilfe.de