Related
For experimental purpose, I renamed /dev/block to /dev/block.bak, but after a restart it just came back to /dev/block, I wonder how that works?
nicedog said:
For experimental purpose, I renamed /dev/block to /dev/block.bak, but after a restart it just came back to /dev/block, I wonder how that works?
Click to expand...
Click to collapse
Because it's not a fike...it's a device and gets rebuilt on every boot.
Sent from my Note 3 via Tapatalk
Thanks, but rebuild from where? I'm asking is because the phone shows null baseband and I'm not getting any signal. I use EFS professional to
restore EFS, FSG and some other stuff, sometime it works, but sometime after a restart, I'm getting the same issue again.
nicedog said:
Thanks, but rebuild from where? I'm asking is because the phone shows null baseband and I'm not getting any signal. I use EFS professional to
restore EFS, FSG and some other stuff, sometime it works, but sometime after a restart, I'm getting the same issue again.
Click to expand...
Click to collapse
Part of the UNIX/LINUX init process is to rebuild the list of attached devices which is what /dev is...an interface between software and hardware
Sent from my Note 3 via Tapatalk
This guide is for those who have lost their IMEI, have corrupted EFS, or erased EFS partition. So, follow these under your own risk, it may or may not work, and if something happens or doesn't happen, then i am not to blame. So, once again i will not take credit for bricked phones or something along those lines, however i will take full credit if this works for you. I will also provide assistance to those who could not restore their EFS following this guide.
Before proceeding with this guide, backup what you have left. Use twrp to backup and in case something goes wrong and your problem escalates, you can restore using twrp backup.
Restore EFS
Change IMEI Number
Restore EFS
Do this if and only if you believe your EFS is corrupted, or you somehow erased it. If you are not sure about it, then simply follow the next guide to change you IMEI number. In most cases people loose their IMEI only and not the whole partition. Again, it may or may not work, so do this on your risk, and i am not to blame if anything bad happens, but if you do succeed, then don't forget to give me credit.
Note:
If your EFS is erased or corrupted, your IMEI and Baseband will be shown as unknown. In this case recover the EFS following this post, and then change the IMEI following the next post. If your IMEI is shown as 0, then you EFS is safe and most probably your IMEI is gone. In that case, no need to recover EFS, only change the IMEI number following my next post.
In TWRP, backup of kate wont show on kenzo and the backup up kenzo wont show on kate. In case no backup is shown even if you are using the right device, then try the dump flashing method or try changing the TWRP recovery.
Flashing this will only restore your EFS partition, but the IMEI will still be gone, so you will have to follow the next guide to change your IMEI.
Even after flashing a new EFS, you Mac and BT address will not recovery. The android system will assign a software generated address to both devices. Dont worry cause even without the EFS partition there will be a Mac and BT address assigned to your device and both the things will work normally.
If your Baseband is still unknown, even after flashing a new EFS, then try flashing latest radio file. It can be found in any firmware update package, either the official or the one from the strix.
1. Download the required files from the link given below.
EFS Backup[Kenzo] - Contact me if someone has backup of this.
EFS Backup[Kate] - Contact me if someone has backup of this.
2. Extract the Dump Backup files and flash them using the following commands.
Code:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
3. Now reboot and voila you have you a new EFS partition at your disposal.
Change IMEI Number
Requirements:
Root
USB Debugging is turn on
Windows Driver Signature is turned off
ADB and Fastboot Binary Files
Latest MiFlash Installed for the latest drivers
1. Connect your device to pc and open the adb folder. Then open a command promt window.
Code:
>> [B]Shift + Right Click[/B] anywhere in the adb folder
>> Click on [B]Open Command Window Here[/B]
2. Type the following command to enable Diagnostics mode. Allow debugging if asked.
Code:
adb shell
su
setprop sys.usb.config diag,adb
4. Download the IMEI Changer from the link given below.
IMEI Changer [Credit: Archeolot]
5. Now, open the imei changer, and enter imei number in both the fields. And click on start. After a moment it will show as passed. If it fails make sure that you have followed the points i stated.
Note: Make sure that the driver in driver management under ports is listed as "Qualcom HS-USB Android DIAG 901D" and not as "Marshall London HS-USB Android DIAG 901D". If it is listed in any other name, then go to driver management and update driver. Select browse driver, then let me pick driver from a list. Then select "Qualcom HS-USB Android DIAG 901D" and then finish.
WOW.. Thanks mate..
It's gonna very Helpful for me & other ppl.. ??
Sent from my Redmi Note 3 using Tapatalk
didn't work..
showing error as no diag even after typing those commands
kindly help me
nuk.nama said:
showing error as no diag even after typing those commands
kindly help me
Click to expand...
Click to collapse
At what part, the imei change or flashing.
The simplest, and the fastest guide to restoring EFS and IMEI! I haven't backed up my EFS and this revived my phone! Much apprecieated!
Broski32 said:
The simplest, and the fastest guide to restoring EFS and IMEI! I haven't backed up my EFS and this revived my phone! Much apprecieated!
Click to expand...
Click to collapse
Glad i could help mate. Can you confirm your mac address and bluetooth address, whether it is same or changed.
archit.bajpai.ab said:
Glad i could help mate. Can you confirm your mac address and bluetooth address, whether it is same or changed.
Click to expand...
Click to collapse
Can't confirm. My EFS partition was so corrupted from trying other tutorials to restore my IMEI that I didn't even bother backing it up because I thought that it could have been changed already (tried writing to NVRAM with QPST). Since I don't have my original mac and bluetooth addresses written down anywhere (I haven't written them down myself and I don't think they are to be found anywhere on the box or on the phone) I think the only way to check it would be to compare my current addresses on the phone to the addresses contained in your EFS backup. Can you extract them so I can check if they match or not?
Broski32 said:
Can't confirm. My EFS partition was so corrupted from trying other tutorials to restore my IMEI that I didn't even bother backing it up because I thought that it could have been changed already (tried writing to NVRAM with QPST). Since I don't have my original mac and bluetooth addresses written down anywhere (I haven't written them down myself and I don't think they are to be found anywhere on the box or on the phone) I think the only way to check it would be to compare my current addresses on the phone to the addresses contained in your EFS backup. Can you extract them so I can check if they match or not?
Click to expand...
Click to collapse
The mac address and bluetooth address in the efs are my own. I only changed the imei so that no one else can copy it, i didnt know anyway to change mac address. Besides the mac address doesnt matter that much, and i dont think that we will ever be on the same wifi network.
If you dont know then i can explain, that the mac address is required to maintain switches and broadcast in the router, so it technically does not matter.
You can change it later with some apps or use it like that if you wish, if i find any way to restore you mac i will post it too. In the mean time just post a snapshot of wifi mac and bluetooth address so that i can compare them with my own.
So, using this way, one can change the IMEI no. also?
mGforCe said:
So, using this way, one can change the IMEI no. also?
Click to expand...
Click to collapse
Yes, just use the imei changer in the rar file to change your imei. But make sure to backup or atleast note down your imei before doing so.
archit.bajpai.ab said:
The mac address and bluetooth address in the efs are my own. I only changed the imei so that no one else can copy it, i didnt know anyway to change mac address. Besides the mac address doesnt matter that much, and i dont think that we will ever be on the same wifi network.
If you dont know then i can explain, that the mac address is required to maintain switches and broadcast in the router, so it technically does not matter.
You can change it later with some apps or use it like that if you wish, if i find any way to restore you mac i will post it too. In the mean time just post a snapshot of wifi mac and bluetooth address so that i can compare them with my own.
Click to expand...
Click to collapse
Current addresses on my phone:
MAC - 00:0a:f5:a9:XX:XX
Bluetooth - 7C:7F:F0:82:XX:XX
Left out some numbers just in case they are mine. For the purpose of checking that will still be enough
Broski32 said:
Current addresses on my phone:
MAC - 00:0a:f5:a9:XX:XX
Bluetooth - 7C:7F:F0:82:XX:XX
Left out some numbers just in case they are mine. For the purpose of checking that will still be enough
Click to expand...
Click to collapse
Yup, they are not mine. Mine start with 64:cc and so on for both mac and bluetooth. They may be software generated or may be your own, technically i am not sure.
Edit: did you use imei changer to change imei no. Or are you using the default values. If you are using the default values, pls post them too. If you change them, then give your review, ie was it hard or easy, did you encointer any problem, stuff like that.
archit.bajpai.ab said:
Yup, they are not mine. Mine start with 64:cc and so on for both mac and bluetooth. They may be software generated or may be your own, technically i am not sure.
Edit: did you use imei changer to change imei no. Or are you using the default values. If you are using the default values, pls post them too. If you change them, then give your review, ie was it hard or easy, did you encointer any problem, stuff like that.
Click to expand...
Click to collapse
After flashing your EFS backup both IMEI values were set to "0". On the default values I don't think the phone would be able to register on any network with the sim inside, but I haven't tried that. Then I flashed my IMEI with the app you provided in the .rar. Set my IMEI same for both slots because I've got only one written down on the box so I think it is set how it should be out of the box. After that I've rebooted to EDL and flashed global developer rom. And it's all working, I'm able to make calls from both sim slots, however didn't try having 2 sims inside.
All in all the process is very easy, definitely the easiest out there. I haven't encountered any problems, however I think others may have a problem with drivers to get "Qualcom HS-USB Android DIAG 901D" working. Mine was working already because I tried this tutorial before. Thank you for this guide, and providing your backup
Broski32 said:
After flashing your EFS backup both IMEI values were set to "0". On the default values I don't think the phone would be able to register on any network with the sim inside, but I haven't tried that. Then I flashed my IMEI with the app you provided in the .rar. Set my IMEI same for both slots because I've got only one written down on the box so I think it is set how it should be out of the box. After that I've rebooted to EDL and flashed global developer rom. And it's all working, I'm able to make calls from both sim slots, however didn't try having 2 sims inside.
All in all the process is very easy, definitely the easiest out there. I haven't encountered any problems, however I think others may have a problem with drivers to get "Qualcom HS-USB Android DIAG 901D" working. Mine was working already because I tried this tutorial before. Thank you for this guide, and providing your backup
Click to expand...
Click to collapse
Enjoy your revived phone buddy.
Thanks buddy!!!!! you saved my phone
pandyajoe said:
Thanks buddy!!!!! you saved my phone
Click to expand...
Click to collapse
It do what i can do buddy...
Guys. I messed up my phone by restoring a nandroid backup from a different one.
I was able to restore my IMEI using some qualcomm tools. My problem now is that fingerprint scanner won't work on any rom, even official.
Any idea what else I have messed Up? I don't think restoring this efs will fix my fingerprint scanner. Is fingerprint scanner info in a different partition?
chr0m said:
Guys. I messed up my phone by restoring a nandroid backup from a different one.
I was able to restore my IMEI using some qualcomm tools. My problem now is that fingerprint scanner won't work on any rom, even official.
Any idea what else I have messed Up? I don't think restoring this efs will fix my fingerprint scanner. Is fingerprint scanner info in a different partition?
Click to expand...
Click to collapse
Have you checked with miui7 stock rom. As far as i know there are three sensor modules for fingerprint, on of them is goodfix which is currently not supported by many roms. If your is goodfix then it will not be supported too. You can flash miui rom to check whether the fingerprint works or not...
If it doesnot work, then try to resotre your nandroid backup agaian. This tym simply untick efs.
WARNING: I am not responsible for damage to your phone through this guide, follow at your own risk.
Its only tested on EU Singlesim devices!!!!
First of all, thanks to @ilovemeow and @tomparr ! :good:
We all know, it was on the Moto X Play easy to "unlock" the DualSim ability by flash a firmware with including a DSDS Baseband. But Moto changed the Firmware layout. On the Moto Z Play are all basebands in the /fsg folder and after a modem wipe (dualsim=true or false) loads the matching baseband to modemst1 and modemst2. The settings for dualsim=true and the software channel are not editable right now.
So the trick is to get the baseband for dualsim in to the modem. I found a easy but dirty way to get the DSDS baseband loaded.
You need a Moto Z Play SingleSim Device (Mine is from Germany with RETEU)
Now the step by step guide:
1. boot in to twrp open the terminal and type
Code:
setprop persist.radio.multisim.config dsds
(thx to @ilovemeow again )
2. boot and make sure you got the Dualsim options in the Settings. If yes goto 3. If not load a Terminal Emulator from playstore and type there the command from 1.
3. Got to the settings and look which baseband you use now! Its important to note that!!
3. Open the RootExplorer and navigate tot he fsg Folder. You will find there a bunch of im.gz files (like addison_2.img.gz and addison_dsds_2.img.gz and so on…)
4. You must make sure which file for your phone is the right one (For the EU Phones its Addison_ROW and addisson_2.img.gz) You will see that the numbered files are linked to the other file in the folder. See the Picture.
5. Now you have to delete the baseband your phone use normally. At the EU Devices addisson_2.img.gz and addisson_row.img.gz
6. Now comes the magic! xD Just rename the dsds files from addisson_dsds_2.img.gz to adisson_2.img.gz and addison_dsds_row.img to addison_row.img.gz.
7. Reboot to bootloader and enter
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot reboot
now you can use both cards! :highfive: :victory:
NOTES:
1. there some bugs in the dialer! You cant save the settings that a specific number automatic called by sim1 or sim2
2. Second SIM Card/Modem only got IMEI 0! But works in German Networks without a problem.
3. You can loose your of sim1/modem IMEI if you do something wrong!
4. You got a bit more battary drain.
5. You can restore the default settings with just flashing the fsg.mbn file!
If you like my work give me adfree or buy me a beer
---- reserved -----
WOW
Thanks a lor for your work, bro.
I will to try today night.
Thanks again!
Can you confirm the command in your first "code" box is actually supposed to be "steprop" and not SETPROP?
Thanks for figuring this out - if I ever decide to unlock, I'll be giving it a shot!
Arg wrong typo thx
Thank you. It worked!
hassanfarroq92 said:
Thank you. It worked!
Click to expand...
Click to collapse
What Software channel is your device?
@all If you got it working on your device, let us know!
-=MoRpH=- said:
What Software channel is your device?
@all If you got it working on your device, let us know!
Click to expand...
Click to collapse
Retgb
? thanks mate, actually thats was thr idea of someone in x play forum
btw I cant find any files in /fsg folder
ilovemeow said:
? thanks mate, actually thats was thr idea of someone in x play forum
btw I cant find any files in /fsg folder
Click to expand...
Click to collapse
Did u use the "RootExplorer? https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
Total Commander should work also and is free of cost and ads. You may want to try this one first.
tag68 said:
Total Commander should work also and is free of cost and ads. You may want to try this one first.
Click to expand...
Click to collapse
I didn't try totalcommander, because I had fear loosing the links between the files. If that happen, the baseband couldn't be loading right and you got no signal on both cards.
-=MoRpH=- said:
Did u use the "RootExplorer? https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
Click to expand...
Click to collapse
it's look ok now, it take 15sec to load those file
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
trying to reboot now, let's see in 2mins
---------- Post added at 07:46 PM ---------- Previous post was at 07:44 PM ----------
all working thank mate,
so this trick needed to root
Anyone with build.prop from native dualsim device?
Only camera is giving issues reset is working as it should.
I'm getting restart error
How can the second phone line work without IMEI?
Many networks don't have IMEI Checks, so you can use it with a 0 IMEI.
-=MoRpH=- said:
Did u use the "RootExplorer? https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
Click to expand...
Click to collapse
yyp
and es explorer pro can do as well
left native dualsim, retapac
right reteu
and the 2nd pic, both sim lose imei, dont give a shxx as long as both sim work
ilovemeow said:
left native dualsim, retapac
right reteu
and the 2nd pic, both sim lose imei, dont give a shxx as long as both sim work
Click to expand...
Click to collapse
??
Did you loose the IMEI because of the dualsim mod?
can anyone who has root access provide me with a dump of the misc partition from their H918 LGV20? I flashed a ROM that apparently included the misc.bin from the KDZ and now mine is wiped. HELP! the command to use would be the following
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/backup/misc.img
I unpacked the 10K KDZ, surprisingly there was a misc.bin there. It was not on the previous 10J I checked.
Anyway, here you go. I'm bricked so this is all I can give you. I assume it will be fine.
Hmm... I just looked at it, and it's zeroed-out. But it must be supposed to, right? If you flash the KDZ then that is what happens.
Edit: Or maybe it's only included by accident, and isn't actually flashed...hmm I'll leave it here until you respond, if it's not what you need I'll remove it, so not to detract from you request
Edit2: Removed
askermk2000 said:
I unpacked the 10K KDZ, surprisingly there was a misc.bin there. It was not on the previous 10J I checked.
Anyway, here you go. I'm bricked so this is all I can give you. I assume it will be fine.
Hmm... I just looked at it, and it's zeroed-out. But it must be supposed to, right? If you flash the KDZ then that is what happens.
Edit: Or maybe it's only included by accident, and isn't actually flashed...hmm I'll leave it here until you respond, if it's not what you need I'll remove it, so not to detract from you request
Click to expand...
Click to collapse
thanks, however I believe the KDZ was what caused mine to be zeroed out... now my phone's MAC address is no longer fixed and keeps changing as a result of no misc partition
Wow. You flashed this *H91810k.zip* right? I used that one too while my phone was functioning. And yes I noticed that exact problem with the MAC address because I was using FTP server on the phone. DAMN
How do we fix it? Manual edit of misc partition to insert our original MAC?
Ok I see you wrote KDZ. I flashed a TWRP H918 10K rom from the forum. I suppose many will have this problem.
MISC partition. What does it do
China user
andy_zhang said:
MISC partition. What does it do
China user
Click to expand...
Click to collapse
misc partition contains device info like WiFi and BT MAC addresses, device IMEI and serial number... if you want to help me out, it may be best to open up the file in a hex editor after creating it to block out those information.
Your device is 100% usable without a misc partition. i regularly wiped mine because twrp stores its config there.
me2151 said:
Your device is 100% usable without a misc partition. i regularly wiped mine because twrp stores its config there.
Click to expand...
Click to collapse
So you're saying the IP address changing at every reboot is not related to this?
askermk2000 said:
So you're saying the IP address changing at every reboot is not related to this?
Click to expand...
Click to collapse
IP address changing is related to the DHCP server of your network changing your IP. If you mean MAC changing at every boot its a issue with custom roms. Not the Misc Partition.
me2151 said:
IP address changing is related to the DHCP server of your network changing your IP. If you mean MAC changing at every boot its a issue with custom roms. Not the Misc Partition.
Click to expand...
Click to collapse
Yes the MAC address is changing, therefore IP address changes as a consequence. That is what I meant.
We thought this was because the misc partition was wiped. (I was using stock 10k)
askermk2000 said:
Yes the MAC address is changing, therefore IP address changes as a consequence. That is what I meant.
We thought this was because the misc partition was wiped. (I was using stock 10k)
Click to expand...
Click to collapse
There IS a possibility that the MAC is stored in MISC but im pretty sure its stored in the FIRMWARE partition. Regardless. If you use someone elses MISC partition that you mean you would have their MAC address IF its stored in there. You would still not have yours.
me2151 said:
There IS a possibility that the MAC is stored in MISC but im pretty sure its stored in the FIRMWARE partition. Regardless. If you use someone elses MISC partition that you mean you would have their MAC address IF its stored in there. You would still not have yours.
Click to expand...
Click to collapse
Yes, well it was not my idea to get a misc backup from someone. But @dimm0k did bring to my attention the MAC address problem, and it just seemed very logical that it was caused by that botched 10K KDZ file.
askermk2000 said:
Yes, well it was not my idea to get a misc backup from someone. But @dimm0k did bring to my attention the MAC address problem, and it just seemed very logical that it was caused by that botched 10K KDZ file.
Click to expand...
Click to collapse
The MAC address issue is on almost every aosp rom and aosp roms dont touch MISC so its probably not caused but the MISC partition. Yes theres always a possibility but still. There might be other stuff going on.
@me2151 @askermk2000
while I'm a novice to all of this, I can say with 100% certainty that on the LGV20 the MAC address is tied to the misc partition, which looks to be the /dev/block/sda5 partition. as mentioned, the H91810k KDZ contained a misc.bin that I had in my original release of the TWRP flashable 10k zip. because of this my MAC address has been constantly changing after a reboot to that of something beginning with 00:90:4c. I don't know much about AOSP so I can't comment on that, but because I have 2 LGV20s of different variants I was able to get a dump from the US996 variant for the misc partition and compare that to the "damaged" misc partition on the H918. The size is exactly the same, 32MB, with the beginning parts being different between the two dumps. I was able to restore my MAC address by hex editing the "damaged" misc using the same location from the US996 variant's misc partition as a reference. I was also able to restore the BT MAC address and serial number using the same method. prior to these edits my WiFi and BT MAC addresses kept changing and the serial number was actually missing in the Settings > About Phone section. after these edits they have been constant to what I set them as. the only reason I want the misc partition now is so that I can compare to see if there was anything else in the misc partition that I need to restore that's specific to the H918. the misc partition isn't crucial for the device to work, but it is needed to avoid random MAC addresses that I know for sure.
that said, askermk2000, do you happen to have a misc dump for the US996? that would help me confirm what's missing from the H918 as I have a good US996 misc dump.
This was very enlightening. I was with @me2151 as far as the misc partition goes. I have wiped it many times, for various reasons -- just thought it was used by the stock recovery. One being forgetting to turn off auto updates, and getting caught in a boot loop (wiping fota wasn't enough). But I never used my phone as a server, so no need to consistently get the same address from a DHCP server. Once I get my H918, I will definitely go through it and see what else is in there.
Doing some searching, apparently on older phones it was possible to re-lock your boot loader without wiping data if you dumped the misc partition before and after unlocking. Just flash the "locked" version back, and viola, locked boot loader. This may come in handy on the H918 since T-Mobile allows unlocking, and can't use the eng boot loader that claims it is locked when it isn't.
-- Brian
dimm0k said:
misc partition contains device info like WiFi and BT MAC addresses, device IMEI and serial number... if you want to help me out, it may be best to open up the file in a hex editor after creating it to block out those information.
Click to expand...
Click to collapse
I have uploaded two types of files
China user
andy_zhang said:
I have uploaded two types of files
China user
Click to expand...
Click to collapse
two types of files? can you give more details, as well as the location?
dimm0k said:
two types of files? can you give more details, as well as the location?
Click to expand...
Click to collapse
我可以用工具提取手机底层。
996 的TOT,但是刷不进去。lgv20 刷不进tot.
China user
---------- Post added at 03:17 AM ---------- Previous post was at 03:17 AM ----------
andy_zhang said:
我可以用工具提取手机底层。
996 的TOT,但是刷不进去。lgv20 刷不进tot.
China user
Click to expand...
Click to collapse
https://mega.nz/#F!I4IHTQbR!8Pf3kwL-jirY7zrnia3cow
China user
I am pretty sure the MAC address (& IMEI) is stored in the modemst1 & modemst2 partitions.
I was able to easily change them when I wiped those on my H990DS.
Try going to dialpad & type *#546368#*918# (it is *#546368#*990# for my H990DS)-->SVC Menu-->CRCWIZARD Test-->Auto MID-->MID Setting
(should be able to set with wiped modemst1 & modemst2 partitions however option wasn't available when I restored those partitions)
Prowler_gr said:
I am pretty sure the MAC address (& IMEI) is stored in the modemst1 & modemst2 partitions.
I was able to easily change them when I wiped those on my H990DS.
Try going to dialpad & type *#546368#*918# (it is *#546368#*990# for my H990DS)-->SVC Menu-->CRCWIZARD Test-->Auto MID-->MID Setting
(should be able to set with wiped modemst1 & modemst2 partitions however option wasn't available when I restored those partitions)
Click to expand...
Click to collapse
That is not the point. It's just a shadow copy in the misc, probably for easy access by apps. But as a courtesy to the users wanting to help, he mentions it, though I wouldn't sweat about that imei stuff.
Who cares? I've been reading smartphone forums en-mass for a long time now, and there's no shortage of people posting their imei for various reasons. Or go to Ebay and look at almost every phone listing, you will find the IMEI so ppl can check if it's blacklisted.
You can even generate your own imei if you really wanna change it.
Edit: He already said that he fixed his wlan & bt mac address by editing the misc partition.
After considering the pros and cons of upgrading (mainly I would like to see if it fixes issues that I am experiencing with custom roms), I have decided that I would like to upgrade the firmware on my G4 to v29a. However, I would like to make a backup of my current firmware (I believe booloader and modem are the parts that cannot be backed up with TWRP), and I was wondering how I would back those up.
Also, should I need to restore these backups, how would I do it?
Thanks
ThePiGuy said:
After considering the pros and cons of upgrading (mainly I would like to see if it fixes issues that I am experiencing with custom roms), I have decided that I would like to upgrade the firmware on my G4 to v29a. However, I would like to make a backup of my current firmware (I believe booloader and modem are the parts that cannot be backed up with TWRP), and I was wondering how I would back those up.
Also, should I need to restore these backups, how would I do it?
Thanks
Click to expand...
Click to collapse
Latest unofficial TWRP backups bootloader and firmware (if you select it)
Nevertheless I ALWAYS recommend to do a backup with SALT at least once as this backups really EVERYTHING ( full mode can even backup your full internal storage which can NOT be done with TWRP) . A SALT backup is just a double protection as a full TWRP backup is usually all you need.
Restore in TWRP your TWRP backup and for SALT backup files you would use TWRP plus the dd command in an adb shell if needed (e.g. dd if=/sdcard/cust.image of=/dev/block/bootdevice/by-name/cust).
But again: restoring SALT backup files is for the worst case only.. But for that case it's good to have them..
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Latest unofficial TWRP backups bootloader and firmware (if you select it)
Click to expand...
Click to collapse
Would you recommend latest Marshmallow or Nougat unofficial TWRP (I'm backing up Marshmallow but I would be restoring it from Nougat or Oreo)?
ThePiGuy said:
Would you recommend latest Marshmallow or Nougat unofficial TWRP (I'm backing up Marshmallow but I would be restoring it from Nougat or Oreo)?
Click to expand...
Click to collapse
If you do not encrypt just choose latest N one. Regardless of which ROM you currently use or will use in the future.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
If you do not encrypt just choose latest N one. Regardless of which ROM you currently use or will use in the future.
Click to expand...
Click to collapse
Ok thanks. I just booted into it and had a look at the backup - I can see bootloader, and I can also see Carrier. Is the Carrier option the modem that is referred to in the v29a update?
ThePiGuy said:
Ok thanks. I just booted into it and had a look at the backup - I can see bootloader, and I can also see Carrier. Is the Carrier option the modem that is referred to in the v29a update?
Click to expand...
Click to collapse
Nope. Firmware = Modem
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Nevertheless I ALWAYS recommend to do a backup with SALT at least once as this backups really EVERYTHING ( full mode can even backup your full internal storage which can NOT be done with TWRP) . A SALT backup is just a double protection as a full TWRP backup is usually all you need.
Restore in TWRP your TWRP backup and for SALT backup files you would use TWRP plus the dd command in an adb shell if needed (e.g. dd if=/sdcard/cust.image of=/dev/block/bootdevice/by-name/cust).
But again: restoring SALT backup files is for the worst case only.. But for that case it's good to have them.
Click to expand...
Click to collapse
I have just tried to do a backup with SALT, and it was working really well and then it froze on the System backup. Looking in the log, it appears there has been a timeout error. Could this have been because my Ubuntu VM locked whilst the backup was happening?
ThePiGuy said:
I have just tried to do a backup with SALT, and it was working really well and then it froze on the System backup. Looking in the log, it appears there has been a timeout error. Could this have been because my Ubuntu VM locked whilst the backup was happening?
Click to expand...
Click to collapse
Well there is one open issue in SALT atm: it does not warn you about too less disk space. The result is it freezes on backup if you have not 32 GB disk space available and choosen the full backup.
In VirtualBox you can setup shared folders which then can be auto mounted on FWUL (choose persistent folder and to auto mount in vbox settings)
Choose a folder with at least 32 GB free space and choose that one in SALT.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Well there is one open issue in SALT atm: it does not warn you about too less disk space. The result is it freezes on backup if you have not 32 GB disk space available and choosen the full backup.
In VirtualBox you can setup shared folders which then can be auto mounted on FWUL (choose persistent folder and to auto mount in vbox settings)
Choose a folder with at least 32 GB free space and choose that one in SALT.
Click to expand...
Click to collapse
My VM has 58GB free space at the moment. The python error in the log was a usb timeout error
ThePiGuy said:
My VM has 58GB free space at the moment. The python error in the log was a usb timeout error
Click to expand...
Click to collapse
What FWUL version? Persistent or forgetful? If forgetful the disk size is defined by the RAM. If persistent the max avail is 30 GB. So out of the box none of them can handle a full backup atm without modifications..
...or do you have mounted a 58 GB disk in vbox and store the backup there?
Some devices / firmwares got a timeout issue like you describe in big partitions. I adjusted the timeouts already and fixed it for the most ppl. If that happens go to advanced menu and grab the log. Use a pastebin service like hastebin or pastebin and share the link
Sent from my LG-H815 using XDA Labs
steadfasterX said:
What FWUL version? Persistent or forgetful? If forgetful the disk size is defined by the RAM. If persistent the max avail is 30 GB. So out of the box none of them can handle a full backup atm without modifications..
...or do you have mounted a 58 GB disk in vbox and store the backup there?
Some devices / firmwares got a timeout issue like you describe in big partitions. I adjusted the timeouts already and fixed it for the most ppl. If that happens go to advanced menu and grab the log. Use a pastebin service like hastebin or pastebin and share the link
Click to expand...
Click to collapse
I wasn't running it in FWUL - I already had a Ubuntu 16.04.3 LTS VM set up so I was backing up in there, and the allocated disk space for the VM had 58GB free. It only had 4GB RAM allocated though, so maybe this caused an issue. I can try again on a true Ubuntu machine to see if the VM was the issue
ThePiGuy said:
I wasn't running it in FWUL - I already had a Ubuntu 16.04.3 LTS VM set up so I was backing up in there, and the allocated disk space for the VM had 58GB free. It only had 4GB RAM allocated though, so maybe this caused an issue. I can try again on a true Ubuntu machine to see if the VM was the issue
Click to expand...
Click to collapse
Just use your Ubuntu one is fine!
The RAM is just interesting when we talk about FWUL forgetful.
So just do it again and when it happens again grab the log as mentioned above.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Just use your Ubuntu one is fine!
The RAM is just interesting when we talk about FWUL forgetful.
So just do it again and when it happens again grab the log as mentioned above.
Click to expand...
Click to collapse
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Just out of interest, looking at the files, I can see a modem file (and also modemst1 and modemst2 - If I use the modem backup, do I need to flash these as well?), but I can't see a bootloader file. Is it under a different name?
Finally, now that I have a backup, where would you recommend getting the v29a files and how would you recommend flashing them?
Thanks for all your help
ThePiGuy said:
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Click to expand...
Click to collapse
Having said that, I just got an md5 mismatch error on my userdata.bin. Is there any way to backup just that partition rather than the entire thing again?
ThePiGuy said:
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Just out of interest, looking at the files, I can see a modem file (and also modemst1 and modemst2 - If I use the modem backup, do I need to flash these as well?), but I can't see a bootloader file. Is it under a different name?
Finally, now that I have a backup, where would you recommend getting the v29a files and how would you recommend flashing them?
Thanks for all your help
Click to expand...
Click to collapse
Nope modemst1 and 2 are when you have issues with your imei. Nothing which you need to restore usually. Those are also get backuped by TWRP when you choose EFS.
Regarding the way to go to N? Well when you're unlocked and you have TWRP: flash the zip from @kessaras . If you flash the full ROM ensure that it does not contain the recovery image as it would overwrite TWRP. I would also remove the laf file from there to ensure SALT will continue to work (some ppl have issues on N laf).
ThePiGuy said:
Having said that, I just got an md5 mismatch error on my userdata.bin. Is there any way to backup just that partition rather than the entire thing again?
Click to expand...
Click to collapse
Was it really a mismatch so ERROR or a warning?
Yes but not in the GUI (yet):
Open a terminal
sudo -s
cd /root/programs/lglafng
sudo python3 partitions.py --dump YOURBACKUPFOLDER/userdata.bin userdata
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Nope modemst1 and 2 are when you have issues with your imei. Nothing which you need to restore usually. Those are also get backuped by TWRP when you choose EFS.
Regarding the way to go to N? Well when you're unlocked and you have TWRP: flash the zip from @kessaras . If you flash the full ROM ensure that it does not contain the recovery image as it would overwrite TWRP. I would also remove the laf file from there to ensure SALT will continue to work (some ppl have issues on N laf).
Click to expand...
Click to collapse
Ok thanks - I'll get going
steadfasterX said:
Was it really a mismatch so ERROR or a warning?
Click to expand...
Click to collapse
Unfortunately it was definitely an error. I reran the entire backup and I got the same error - "These files are corrupt (md5 mismatch): userdata.bin" under the errors tab after md5 verification
ThePiGuy said:
Ok thanks - I'll get going
Unfortunately it was definitely an error. I reran the entire backup and I got the same error - "These files are corrupt (md5 mismatch): userdata.bin" under the errors tab after md5 verification
Click to expand...
Click to collapse
Share the log
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Share the log
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I would but I made the mistake of closing and reopening SALT and it all got deleted. Would you like me to run a third backup to get the log again?
ThePiGuy said:
I would but I made the mistake of closing and reopening SALT and it all got deleted. Would you like me to run a third backup to get the log again?
Click to expand...
Click to collapse
If you don't mind.. Maybe it's an issue I can fix. Up to you.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
If you don't mind.. Maybe it's an issue I can fix. Up to you.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'll get it going