Ive soft bricked following
http://forum.xda-developers.com/showthread.php?t=3170550
original prewarning instructions for F500L flashing rooted system.img 10w over 10a.
Some have been able to successfully boot their devices using H815 10b kdz but loose or have faint signal strength.
So here's where I need help backing up my modem(s) before hand.
I've tried LG bridge to restore to stock as well as other LG support tools to.no avail.
Any help or suggestions would be great.
EDIT:Ended up flashing H810 10A KDZ, it booted but had the same problems others had with H815 10B, no signal. Flashing the modem.img from F500L backup did not flash back/restore. I ended up trying H811 KDZ and rendered my phone useless. After it completed flashing, it reset to dark screen. Lost download mode. It still has "QHSUSB__BULK", there seems to be a way to recover from here, there are instructions for the Nexus 6 and LG G3, but none for G4. I gave up and bought a replacement H811.
You are probably going to have to wait for a kdz. You might as well try and flash away. As long as you don't f-up download mode, you haven't much to lose.
You should be able to run the below using send_command.exe. This will back modem up to your internal storage. You can't use sdcard because it would have to be mounted.
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modem of=/data/media/0/modem.img
---------- Post added at 10:37 AM ---------- Previous post was at 10:21 AM ----------
To be safe, do your EFS partitions too:
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modemst1 of=/data/media/0/modemst1.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modemst2 of=/data/media/0/modemst2.img
tabp0le said:
You are probably going to have to wait for a kdz. You might as well try and flash away. As long as you don't f-up download mode, you haven't much to lose.
You should be able to run the below using send_command.exe. This will back modem up to your internal storage. You can't use sdcard because it would have to be mounted.
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modem of=/data/media/0/modem.img
---------- Post added at 10:37 AM ---------- Previous post was at 10:21 AM ----------
To be safe, do your EFS partitions too:
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modemst1 of=/data/media/0/modemst1.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modemst2 of=/data/media/0/modemst2.img
Click to expand...
Click to collapse
I think there are 3 modem partitions, have to search. It was posted here somewhere.
Awesome ill try.
I have a backup of my original system.img as well but dont know if or how to get it back on to internal memory of the phone. Unfortunately did a hard rest to troubleshoot the bootloop.
clockcycle said:
I think there are 3 modem partitions, have to search. It was posted here somewhere.
Awesome ill try.
I have a backup of my original system.img as well but dont know if or how to get it back on to internal memory of the phone. Unfortunately did a hard rest to troubleshoot the bootloop.
Click to expand...
Click to collapse
Unfortunately there is no way to get it back on the phone's internal storage.
I have an idea though. Try backing up ALL your partitions. Then flash KDZ. Then copy old system.img you had backed up to internal storage. Reflash ALL your partitions in DL mode.
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/boot of=/data/media/0/boot.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/recovery.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/carrier of=/data/media/0/carrier.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/aboot of=/data/media/0/aboot.img
tabp0le said:
Unfortunately there is no way to get it back on the phone's internal storage.
I have an idea though. Try backing up ALL your partitions. Then flash KDZ. Then copy old system.img you had backed up to internal storage. Reflash ALL your partitions in DL mode.
Click to expand...
Click to collapse
Yea ill do that. Will do some research on here to find that partition list. Then figure out how to back each up.
Once ive got that ill do the test with kdz.
clockcycle said:
Yea ill do that. Will do some research on here to find that partition list. Then figure out how to back each up.
Once ive got that ill do the test with kdz.
Click to expand...
Click to collapse
I just included a few of them with commands in my previous post. You're model is different than mine, so not everything will be the same. But, you will have the same partitions, just slightly different placement. Here is a list of my partitions:
Code:
[email protected]:/ # ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 2015-02-18 13:46 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-02-18 13:46 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-02-18 13:46 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-02-18 13:46 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-02-18 13:46 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-02-18 13:46 cache -> /dev/block/mmcblk0p54
lrwxrwxrwx root root 2015-02-18 13:46 carrier -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-02-18 13:46 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-02-18 13:46 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-02-18 13:46 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-02-18 13:46 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-02-18 13:46 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-02-18 13:46 eri -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-02-18 13:46 factory -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-02-18 13:46 felica -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-02-18 13:46 fota -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-02-18 13:46 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-02-18 13:46 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-02-18 13:46 grow -> /dev/block/mmcblk0p56
lrwxrwxrwx root root 2015-02-18 13:46 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-02-18 13:46 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-02-18 13:46 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-02-18 13:46 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-02-18 13:46 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-02-18 13:46 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-02-18 13:46 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-02-18 13:46 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-02-18 13:46 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-02-18 13:46 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-02-18 13:46 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-02-18 13:46 operatorlogging -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-02-18 13:46 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-02-18 13:46 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-02-18 13:46 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-02-18 13:46 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-02-18 13:46 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-02-18 13:46 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-02-18 13:46 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-02-18 13:46 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-02-18 13:46 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-02-18 13:46 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-02-18 13:46 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-02-18 13:46 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-02-18 13:46 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-02-18 13:46 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-02-18 13:46 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-02-18 13:46 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-02-18 13:46 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-02-18 13:46 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-02-18 13:46 spare3 -> /dev/block/mmcblk0p50
lrwxrwxrwx root root 2015-02-18 13:46 spare4 -> /dev/block/mmcblk0p52
lrwxrwxrwx root root 2015-02-18 13:46 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-02-18 13:46 system -> /dev/block/mmcblk0p53
lrwxrwxrwx root root 2015-02-18 13:46 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-02-18 13:46 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-02-18 13:46 userdata -> /dev/block/mmcblk0p55
---------- Post added at 11:28 AM ---------- Previous post was at 11:18 AM ----------
fyi, you probably don't have to include the spare partitions or userdata. @autoprime could probably tell us there are others that don't need to be included.
tabp0le said:
I just included a few of them with commands in my previous post. You're model is different than mine, so not everything will be the same. But, you will have the same partitions, just slightly different placement. Here is a list of my partitions:
[/COLOR]fyi, you probably don't have to include the spare partitions or userdata. @autoprime could probably tell us there are others that don't need to be included.
Click to expand...
Click to collapse
So let me clarify, by different placement, you mean altho I backup named recovery.img partition, it might actually not be recovery. But as long as I back up the parition regardless of what I name it, and recover it to same partition, it should be ok, correct?
Or are they same named partitions, except physically placed on device in different locations? But as long as I backup up name it should backup regardless of physical location and restore the same?
clockcycle said:
So let me clarify, by different placement, you mean altho I backup named recovery.img partition, it might actually not be recovery. But as long as I back up the parition regardless of what I name it, and recover it to same partition, it should be ok, correct?
Or are they same named partitions, except physically placed on device in different locations? But as long as I backup up name it should backup regardless of physical location and restore the same?
Click to expand...
Click to collapse
They are located on slightly different blocks of memory. The names are the same. If you back it up by name, it doesn't matter what you name the .img file. As long as you restore it to the proper location.
ie.
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/recovery.img
could be run as
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/blahblahblah.img
as long as you restore blahblahblah.img back to the recovery partition.
tabp0le said:
They are located on slightly different blocks of memory. The names are the same. If you back it up by name, it doesn't matter what you name the .img file. As long as you restore it to the proper location.
(ie. dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/recovery.img could be run as dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/blahblahblah.img
as long as you restore blahblahblah.img back to the recovery partition.
Click to expand...
Click to collapse
Awesome appreciate your help. Ill get on this task
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=TYPE_YOUR_ESN_HERE
I was hoping this would return a KDZ
@tabp0le
Bad news, phone isn't doing anything when I type commands to back up, it just returns to #
EDIT: I checked /dev/block/platform/ nothing found. I ran dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img" and it works.
clockcycle said:
@tabp0le
Bad news, phone isn't doing anything when I type commands to back up, it just returns to #
EDIT: I checked /dev/block/platform/ nothing found. I ran dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img" and it works.
Click to expand...
Click to collapse
Hmm. Try substituting the /dev/block/platform for the actual partition names... (make sure you have the right ones for your device) example below.
For my modem, I would try:
Code:
dd if=/dev/block/mmcblk0p1 of=/data/media/0/modem.img
I think you should only need your modems, system and boot partitions.
tabp0le said:
Hmm. Try substituting the /dev/block/platform for the actual partition names... (make sure you have the right ones for your device) example below.
For my modem, I would try:
Code:
dd if=/dev/block/mmcblk0p1 of=/data/media/0/modem.img
Click to expand...
Click to collapse
Tried that, returns to #, no modem.img in /data/media/0/
Need to figure out how to calculate bs, skip, count ect.. Of each partition. Not sure exact what we absolutely need. Assuming system, boot, modems at minimum.
clockcycle said:
Need to figure out how to calculate bs, skip, count ect.. Of each partition. Not sure exact what we absolutely need. Assuming system, boot, modems at minimum.
Click to expand...
Click to collapse
Yeah, boot and modems is what we need. I don't know how to calculate those numbers. I can't seem to get a response from anyone either. Nothing on Google that I have found either!
dd if=/sdcard/modem.img bs=8192 seek=65536 count=11008 of=/dev/block/mmcblk0p1
kwan788 said:
dd if=/sdcard/modem.img bs=8192 seek=65536 count=11008 of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
How did you get the numbers?
Sent from my LGLS991 using XDA Free mobile app
kwan788 said:
dd if=/sdcard/modem.img bs=8192 seek=65536 count=11008 of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
How did you calculate? Need boot.img, modem st1 and st2 bs, skip,count to back up too.
We're so close..
tabp0le said:
How did you get the numbers?
Sent from my LGLS991 using XDA Free mobile app
Click to expand...
Click to collapse
clockcycle said:
How did you calculate? Need boot.img, modem st1 and st2 bs, skip,count to back up too.
We're so close..
Click to expand...
Click to collapse
Another forumer send me the command..and i try flashed..then after reboot stuck at logo.. the forumer say H815 partition size is not same with F500L so will stuck at logo..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wonder if any other variant will boot, work better, or if 815 our only hope.
Related
LG Optimus G EFS Backup/Restore
Every rooted Optimus G user should backup their EFS partitions! Included in this thread is a flashable EFS backup script and terminal/adb commands if you want to do it manually. The script automates the entire backup of all 3 EFS partitions and then packs the files into a flashable zip for easy restoring later. Place this zip somewhere safe other than your sdcard!
Thanks goes to toastcfh for the script help and everyone in #lg-optimus-g that helped out with EFS testing.
Original Optimus G EFS Thread(ZERO EFS) - HERE
Background
You never know when your NV/EFS may stop working correctly. Restoring your WORKING EFS may save the day. A few users in the #lg-optimus-g IRC channel have run into issues and found their phone unusable, myself included. Our issues could have been fixed if an EFS backup was made while the phone was still in working order.
m9kefs1 seems to be radio related
m9kefs2 contains your unique phone identifiers: IMEI, phone number, etc
m9kefs3 seems to be blank 00s
Backing up EFS
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar). Confirmed working on TWRP 2.3.2.3/2.4.1.0 and CWM 6.0.2.7. Confirmed NOT working on CWM 6.0.1.5. Please check to make sure the backup zip worked and actually made a .zip file in /sdcard/EFS_Backup. Any issues please list what recovery and version you are using and please post the recovery.log.
If you don't like convenience this can also be done manually with adb or terminal with the commands below.. root required.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/sdcard/m9kefs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/sdcard/m9kefs2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/sdcard/m9kefs3.img
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder.
If you don't like convenience this can also be done manually with adb or terminal with the commands below. Adjust the "dd if=/sdcard/" command depending on where your backup EFS .img files are located.
Code:
su
dd if=/sdcard/m9kefs1.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
dd if=/sdcard/m9kefs2.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
dd if=/sdcard/m9kefs3.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
Code:
[B]Changelog[/B]
[I]v1 EFS backup zip[/I]:
backed up m9kefs1.img and m9kefs2.img then .tar'd them.
[I]v2 EFS backup zip[/I]:
backed up EFS then creates a flashable .zip containing the EFS partitions.
[I]v3 EFS backup zip[/I]:
zip script is now "safer" and should work on all Optimus G variants.
[I]v4 EFS backup zip[/I]:
backup zip now backs up m9kefs3. this is for "completeness" only.
I believe m9kefs3 contains no worthwhile data.
Thanks for posting this, it is very much needed and all OG users must have their EFS partitions backed up. And i can confirm that m9kefs3 doesnt contains anything except zeroes, still its good to have it backed up
I'm on CWM 6.0.1.5, what is the newest CWM version that works the the Canadian LGOG variants that doesn't give sd-ext mount errors?
I tried 6.0.1.7 but got constant errors.
jiexi said:
I'm on CWM 6.0.1.5, what is the newest CWM version that works the the Canadian LGOG variants that doesn't give sd-ext mount errors?
I tried 6.0.1.7 but got constant errors.
Click to expand...
Click to collapse
I also get sd-ext mount errors on my Sprint Optimus G(ls970). The errors don't seem to get in the way of anything.. seems it's just visually annoying. I'd love to see official TWRP versions for LGOG device.
autoprime said:
I also get sd-ext mount errors on my Sprint Optimus G(ls970). The errors don't seem to get in the way of anything.. seems it's just visually annoying. I'd love to see official TWRP versions for LGOG device.
Click to expand...
Click to collapse
Exactly! 720p screen for viewing errors
Some information: flashable zip does work correctly on official at&t twrp 2.4.2.0 on my rogers e971. sdcard/EFS_Backup only the 3 .img files and no zip
billybest said:
Some information: flashable zip does work correctly on official at&t twrp 2.4.2.0 on my rogers e971. sdcard/EFS_Backup only the 3 .img files and no zip
Click to expand...
Click to collapse
Thanks for the update. Apparently the 7z binary Im using in the script is dynamic.. and won't work with everyones setup. All my tests were done using CFX 4.2.2... seems there's stuff in that rom not found in some other LGOG roms. You will just have to dd the partitions if you ever need to restore. I guess at this point.. consider a working flashable .zip a "bonus" :-/
Also... the newest FreeGee app in the Play store supports EFS backup.. also backs up 3 separate .img files. :good:
The official TWRP for the Sprint LGOG also has EFS backup support added into the normal backup section. I would *think* this would run on Canadian LGOG's... you guy's don't have external SD right?
We have external sd. There is no sd card slot on my Canadian Rogers E971 phone.
Just backed em up using the FreeGee app.. Aren't EFS flashed every time you flash a ROM?
geokilla said:
Just backed em up using the FreeGee app.. Aren't EFS flashed every time you flash a ROM?
Click to expand...
Click to collapse
No.
Thanks for this great tutorial!
I've been having an issue with LTE on my Rogers LGOG. I've tried KDZ-ing back to stock, factory resets multiple times, many different ROMs, and I can't seem to get LTE any longer. It was working before the data partition got damaged though, causing me to need to factory reset for the first time a couple days ago. I believe after that this started to happed.
Just wondering if anyone has a stock clean Rogers EFS backup I could use, or modify and use, if possible. Or if there is something else I could try. I've tried various radios, wiping caches in between, ensured everything like APN and setting were correct, even got Rogers to re-push my account. My SIM is fine in my roommate's HTC One X for LTE right away, and his SIM card is NOT fine in my LGOG, no LTE.
Not sure if the EFS is the only thing left or not. Even after multiple factory resets and everything it seems like this is the only thing left that will solve the issue!
Thanks to all!
Sent from my Optimus G using xda app-developers app
hv6478 said:
Thanks for this great tutorial!
I've been having an issue with LTE on my Rogers LGOG. I've tried KDZ-ing back to stock, factory resets multiple times, many different ROMs, and I can't seem to get LTE any longer. It was working before the data partition got damaged though, causing me to need to factory reset for the first time a couple days ago. I believe after that this started to happed.
Just wondering if anyone has a stock clean Rogers EFS backup I could use, or modify and use, if possible. Or if there is something else I could try. I've tried various radios, wiping caches in between, ensured everything like APN and setting were correct, even got Rogers to re-push my account. My SIM is fine in my roommate's HTC One X for LTE right away, and his SIM card is NOT fine in my LGOG, no LTE.
Not sure if the EFS is the only thing left or not. Even after multiple factory resets and everything it seems like this is the only thing left that will solve the issue!
Thanks to all!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Just wanted to mention this has now been FIXED! Thanks to some hard work from autoprime, Paulicat and a little by me (lol) I'm fully back on LTE. Will have some documentation about this issue in the next little while as we confirm more information about the issue.
need help no 3G/LTE
I bought an F180L from Hong-Kong. It is a Korean version (U+) LG Optimus G. When I turned on the phone (before I put sim into) offered me to upgrade it. After upgrade there is no 3G/LTE. I have tried almost everything (rooted, unlocked bootloader, installed KDZ, intsalled stock and other ROMs) nothing worked.
I read about backup/restore efs, but I don't have efs backed up, so nothing to restore it. I tried to find old ROM (F180L 10q) to make a backup of efs, but I wasn't able to find any KDZ file to make 3G/LTE working.
I'm not a beginner rooting, unlocking phones but I need a tutorial how to make it working. Luckily I know my IMEI, Baseband, kernel, software version, but nothing else. Is it possible to fix this problem.
[email protected]
Best,
Cope007
autoprime said:
LG Optimus G EFS Backup/Restore
Every rooted Optimus G user should backup their EFS partitions! Included in this thread is a flashable EFS backup script and terminal/adb commands if you want to do it manually. The script automates the entire backup of all 3 EFS partitions and then packs the files into a flashable zip for easy restoring later. Place this zip somewhere safe other than your sdcard!
Thanks goes to toastcfh for the script help and everyone in #lg-optimus-g that helped out with EFS testing.
Original Optimus G EFS Thread(ZERO EFS) - HERE
Background
You never know when your NV/EFS may stop working correctly. Restoring your WORKING EFS may save the day. A few users in the #lg-optimus-g IRC channel have run into issues and found their phone unusable, myself included. Our issues could have been fixed if an EFS backup was made while the phone was still in working order.
m9kefs1 seems to be radio related
m9kefs2 contains your unique phone identifiers: IMEI, phone number, etc
m9kefs3 seems to be blank 00s
Backing up EFS
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar). Confirmed working on TWRP 2.3.2.3/2.4.1.0 and CWM 6.0.2.7. Confirmed NOT working on CWM 6.0.1.5. Please check to make sure the backup zip worked and actually made a .zip file in /sdcard/EFS_Backup. Any issues please list what recovery and version you are using and please post the recovery.log.
If you don't like convenience this can also be done manually with adb or terminal with the commands below.. root required.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/sdcard/m9kefs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/sdcard/m9kefs2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/sdcard/m9kefs3.img
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder.
If you don't like convenience this can also be done manually with adb or terminal with the commands below. Adjust the "dd if=/sdcard/" command depending on where your backup EFS .img files are located.
Code:
su
dd if=/sdcard/m9kefs1.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
dd if=/sdcard/m9kefs2.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
dd if=/sdcard/m9kefs3.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
Code:
[B]Changelog[/B]
[I]v1 EFS backup zip[/I]:
backed up m9kefs1.img and m9kefs2.img then .tar'd them.
[I]v2 EFS backup zip[/I]:
backed up EFS then creates a flashable .zip containing the EFS partitions.
[I]v3 EFS backup zip[/I]:
zip script is now "safer" and should work on all Optimus G variants.
[I]v4 EFS backup zip[/I]:
backup zip now backs up m9kefs3. this is for "completeness" only.
I believe m9kefs3 contains no worthwhile data.
Click to expand...
Click to collapse
Will this work on the LG Options G Pro E980?
n0rthstar88 said:
Will this work on the LG Options G Pro E980?
Click to expand...
Click to collapse
probably not.. but id need a partition list from the optimus pro first to correctly respond.
my efs backup script for the lg optimus g might work instead. btu again.. ill have to see your partition list first.
run the code below in adb shell. paste output in pastebin.. post link here.
ls -al /dev/block/platform/msm_sdcc.1/by-name/
autoprime said:
probably not.. but id need a partition list from the optimus pro first to correctly respond.
my efs backup script for the lg optimus g might work instead. btu again.. ill have to see your partition list first.
run the code below in adb shell. paste output in pastebin.. post link here.
ls -al /dev/block/platform/msm_sdcc.1/by-name/
Click to expand...
Click to collapse
I ran the command and this is what I got. I have F240L!
Code:
lrwxrwxrwx root root 1970-01-02 15:05 DDR -> /dev/block/mmcblk0
p30
lrwxrwxrwx root root 1970-01-02 15:05 aboot -> /dev/block/mmcbl
k0p5
lrwxrwxrwx root root 1970-01-02 15:05 bnr -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 1970-01-02 15:05 boot -> /dev/block/mmcblk
0p7
lrwxrwxrwx root root 1970-01-02 15:05 cache -> /dev/block/mmcbl
k0p24
lrwxrwxrwx root root 1970-01-02 15:05 drm -> /dev/block/mmcblk0
p15
lrwxrwxrwx root root 1970-01-02 15:05 eksst -> /dev/block/mmcbl
k0p22
lrwxrwxrwx root root 1970-01-02 15:05 encrypt -> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 1970-01-02 15:05 factory -> /dev/block/mmc
blk0p19
lrwxrwxrwx root root 1970-01-02 15:05 fota -> /dev/block/mmcblk
0p31
lrwxrwxrwx root root 1970-01-02 15:05 fsg -> /dev/block/mmcblk0
p29
lrwxrwxrwx root root 1970-01-02 15:05 grow -> /dev/block/mmcblk
0p38
lrwxrwxrwx root root 1970-01-02 15:05 lcdlog -> /dev/block/mmcb
lk0p36
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs1 -> /dev/block/mmc
blk0p12
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs2 -> /dev/block/mmc
blk0p13
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs3 -> /dev/block/mmc
blk0p14
lrwxrwxrwx root root 1970-01-02 15:05 misc -> /dev/block/mmcblk
0p18
lrwxrwxrwx root root 1970-01-02 15:05 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1970-01-02 15:05 modemst1 -> /dev/block/mm
cblk0p10
lrwxrwxrwx root root 1970-01-02 15:05 modemst2 -> /dev/block/mm
cblk0p11
lrwxrwxrwx root root 1970-01-02 15:05 mpt -> /dev/block/mmcblk0
p32
lrwxrwxrwx root root 1970-01-02 15:05 pad -> /dev/block/mmcblk0
p9
lrwxrwxrwx root root 1970-01-02 15:05 persist -> /dev/block/mmc
blk0p26
lrwxrwxrwx root root 1970-01-02 15:05 rct -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 1970-01-02 15:05 recovery -> /dev/block/mm
cblk0p28
lrwxrwxrwx root root 1970-01-02 15:05 reserved -> /dev/block/mm
cblk0p37
lrwxrwxrwx root root 1970-01-02 15:05 rpm -> /dev/block/mmcblk0
p6
lrwxrwxrwx root root 1970-01-02 15:05 rpmbak -> /dev/block/mmcb
lk0p34
lrwxrwxrwx root root 1970-01-02 15:05 sbl1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1970-01-02 15:05 sbl2 -> /dev/block/mmcblk
0p3
lrwxrwxrwx root root 1970-01-02 15:05 sbl3 -> /dev/block/mmcblk
0p4
lrwxrwxrwx root root 1970-01-02 15:05 sns -> /dev/block/mmcblk0
p16
lrwxrwxrwx root root 1970-01-02 15:05 ssd -> /dev/block/mmcblk0
p17
lrwxrwxrwx root root 1970-01-02 15:05 system -> /dev/block/mmcb
lk0p23
lrwxrwxrwx root root 1970-01-02 15:05 tombstones -> /dev/block/
mmcblk0p27
lrwxrwxrwx root root 1970-01-02 15:05 tz -> /dev/block/mmcblk0p
8
lrwxrwxrwx root root 1970-01-02 15:05 tzbak -> /dev/block/mmcbl
k0p33
lrwxrwxrwx root root 1970-01-02 15:05 userdata -> /dev/block/mm
cblk0p25
aatish said:
I ran the command and this is what I got. I have F240L!
Code:
lrwxrwxrwx root root 1970-01-02 15:05 DDR -> /dev/block/mmcblk0
p30
lrwxrwxrwx root root 1970-01-02 15:05 aboot -> /dev/block/mmcbl
k0p5
lrwxrwxrwx root root 1970-01-02 15:05 bnr -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 1970-01-02 15:05 boot -> /dev/block/mmcblk
0p7
lrwxrwxrwx root root 1970-01-02 15:05 cache -> /dev/block/mmcbl
k0p24
lrwxrwxrwx root root 1970-01-02 15:05 drm -> /dev/block/mmcblk0
p15
lrwxrwxrwx root root 1970-01-02 15:05 eksst -> /dev/block/mmcbl
k0p22
lrwxrwxrwx root root 1970-01-02 15:05 encrypt -> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 1970-01-02 15:05 factory -> /dev/block/mmc
blk0p19
lrwxrwxrwx root root 1970-01-02 15:05 fota -> /dev/block/mmcblk
0p31
lrwxrwxrwx root root 1970-01-02 15:05 fsg -> /dev/block/mmcblk0
p29
lrwxrwxrwx root root 1970-01-02 15:05 grow -> /dev/block/mmcblk
0p38
lrwxrwxrwx root root 1970-01-02 15:05 lcdlog -> /dev/block/mmcb
lk0p36
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs1 -> /dev/block/mmc
blk0p12
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs2 -> /dev/block/mmc
blk0p13
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs3 -> /dev/block/mmc
blk0p14
lrwxrwxrwx root root 1970-01-02 15:05 misc -> /dev/block/mmcblk
0p18
lrwxrwxrwx root root 1970-01-02 15:05 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1970-01-02 15:05 modemst1 -> /dev/block/mm
cblk0p10
lrwxrwxrwx root root 1970-01-02 15:05 modemst2 -> /dev/block/mm
cblk0p11
lrwxrwxrwx root root 1970-01-02 15:05 mpt -> /dev/block/mmcblk0
p32
lrwxrwxrwx root root 1970-01-02 15:05 pad -> /dev/block/mmcblk0
p9
lrwxrwxrwx root root 1970-01-02 15:05 persist -> /dev/block/mmc
blk0p26
lrwxrwxrwx root root 1970-01-02 15:05 rct -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 1970-01-02 15:05 recovery -> /dev/block/mm
cblk0p28
lrwxrwxrwx root root 1970-01-02 15:05 reserved -> /dev/block/mm
cblk0p37
lrwxrwxrwx root root 1970-01-02 15:05 rpm -> /dev/block/mmcblk0
p6
lrwxrwxrwx root root 1970-01-02 15:05 rpmbak -> /dev/block/mmcb
lk0p34
lrwxrwxrwx root root 1970-01-02 15:05 sbl1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1970-01-02 15:05 sbl2 -> /dev/block/mmcblk
0p3
lrwxrwxrwx root root 1970-01-02 15:05 sbl3 -> /dev/block/mmcblk
0p4
lrwxrwxrwx root root 1970-01-02 15:05 sns -> /dev/block/mmcblk0
p16
lrwxrwxrwx root root 1970-01-02 15:05 ssd -> /dev/block/mmcblk0
p17
lrwxrwxrwx root root 1970-01-02 15:05 system -> /dev/block/mmcb
lk0p23
lrwxrwxrwx root root 1970-01-02 15:05 tombstones -> /dev/block/
mmcblk0p27
lrwxrwxrwx root root 1970-01-02 15:05 tz -> /dev/block/mmcblk0p
8
lrwxrwxrwx root root 1970-01-02 15:05 tzbak -> /dev/block/mmcbl
k0p33
lrwxrwxrwx root root 1970-01-02 15:05 userdata -> /dev/block/mm
cblk0p25
Click to expand...
Click to collapse
ok going to be hard to say without actually seeing the actual partitions... because you have both m9kefs1/2/3 and modemst1/2 . your efs is either m9kefs1/2/3 or modemst1/2... the optimus g used m9kefs1/2/3... the g2/nexus 5 uses modemst1/2.
im going to guess and say lg og pro uses m9kefs1/2/3 tho(same as lgog)...
if not.. then the g2/nexus 5 efs backup would work - http://forum.xda-developers.com/showthread.php?t=2514095
if u wanna run both.. then send me the backup zips it creates.. i could look thru them and give you an exact answer on which one to keep. again.. im leaning towards your efs being in m9kefs1/2/3 tho.. which means this lgog backup method would work.
autoprime said:
ok going to be hard to say without actually seeing the actual partitions... because you have both m9kefs1/2/3 and modemst1/2 . your efs is either m9kefs1/2/3 or modemst1/2... the optimus g used m9kefs1/2/3... the g2/nexus 5 uses modemst1/2.
im going to guess and say lg og pro uses m9kefs1/2/3 tho(same as lgog)...
if not.. then the g2/nexus 5 efs backup would work - http://forum.xda-developers.com/showthread.php?t=2514095
if u wanna run both.. then send me the backup zips it creates.. i could look thru them and give you an exact answer on which one to keep. again.. im leaning towards your efs being in m9kefs1/2/3 tho.. which means this lgog backup method would work.
Click to expand...
Click to collapse
I have actually able to extract my efs modem file using a script which was made for LGOG i got back 3 files one is larger 65Meg file others are 3 mb each approx.
I think you are right that it uses m9kefs1/2/3 though I am not sure what it means but can you help me in one thing? I want to flash other stock rom than my own which has less carrier stuff (specially korean U+) and is in english entierly including the dialpad, sms limit and annoying call to korea or local call options!
but i have like tried telcel, claro, panama, hong kong and indian roms on my cell but after flashing the modem i can't seem to get it working. e.g. panama takes the modem i get the signal but when i tried dialing or pickup a call it crashes!
I am going back to korean f240L but i really like to leave it!
here is the link to download modem
https://www.dropbox.com/s/9p9dz3p0dyd1m65/modemBackup.rar
thank you in advance!
is this possible to do with LG Optimus LTE2? Can you tell me how to actually find the EFS parition to be sure to backup?
pls help
buddy, i need some help from you...i have messed up my E970 phone's network.
Actually, i messed up with its EFS parititon and now i am not getting any network in my phone. My phone is ON, everything working but it is not detecting any sim
i read on XDA forum and got that i need to replace my EFS paritions again with system actual EFS partition file.
Any user friend who has E970 and who is rooted, pls download below file and run in recovery to back up the phone's EFS parition, then pls mail me that backed up EFS parition file so that i can replace it to run my sim card:
http://dl.xda-developers.com/attach.../8/4/9/9/Optimus_G_Create_Flashable_EFSv4.zip
pls download, its only 1 MB file and it will create a single file of small size (in KBs), that file will be placed in /sd card/ EFS_backup
pls mail me that file to save my phone...pls help ppl...it will not take much of your time...help
I want to know if anyone could share the content of this file. I tried looking at the fstab and translate it to the file but I haven't got it to work and the sgs4mini isn't supported by kitchen (but many people have made rom flashables for the mini, although I'm not sure if using the kitchen). Could anyone provide us one?
Which model? I9190, I9192 or I9195?
ladislav.heller said:
Which model? I9190, I9192 or I9195?
Click to expand...
Click to collapse
Sorry, I forgot to add that, it's I9190. Although having them all in one post would be really helpful to anyone needing one in the future for another version of the phone.
rpgdev said:
Sorry, I forgot to add that, it's I9190. Although having them all in one post would be really helpful to anyone needing one in the future for another version of the phone.
Click to expand...
Click to collapse
Send me the output of command:
ls -la /dev/block/platform/msm_sdcc.1/by-name
ladislav.heller said:
Send me the output of command:
ls -la /dev/block/platform/msm_sdcc.1/by-name
Click to expand...
Click to collapse
It wasn't clear where so I did it on my cm installation:
Code:
lrwxrwxrwx root root 2014-04-18 23:56 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-04-18 23:56 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-04-18 23:56 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-04-18 23:56 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-04-18 23:56 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-04-18 23:56 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-04-18 23:56 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-04-18 23:56 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-04-18 23:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-04-18 23:56 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-04-18 23:56 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-04-18 23:56 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-04-18 23:56 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-04-18 23:56 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-04-18 23:56 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-04-18 23:56 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-04-18 23:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-04-18 23:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-04-18 23:56 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-04-18 23:56 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-04-18 23:56 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-04-18 23:56 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-04-18 23:56 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-04-18 23:56 userdata -> /dev/block/mmcblk0p24
rpgdev said:
It wasn't clear where so I did it on my cm installation:
Code:
lrwxrwxrwx root root 2014-04-18 23:56 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-04-18 23:56 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-04-18 23:56 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-04-18 23:56 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-04-18 23:56 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-04-18 23:56 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-04-18 23:56 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-04-18 23:56 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-04-18 23:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-04-18 23:56 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-04-18 23:56 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-04-18 23:56 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-04-18 23:56 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-04-18 23:56 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-04-18 23:56 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-04-18 23:56 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-04-18 23:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-04-18 23:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-04-18 23:56 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-04-18 23:56 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-04-18 23:56 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-04-18 23:56 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-04-18 23:56 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-04-18 23:56 userdata -> /dev/block/mmcblk0p24
Click to expand...
Click to collapse
Attached...
ladislav.heller said:
Attached...
Click to expand...
Click to collapse
It worked thank you! Your script's content is very different from the other galaxy files included in the kitchen tho I would have never guessed!
I could flash the rom and it booted (although it took a long time even after the third boot up) and the wifi didn't work even though I have flashed the same (but stock) rom with Odin and everything works just fine since it's the one my phone came with originally. The thread main topic is solved tho, thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are for the H815 variant only. Files are from software version 10A.
Included below: a stock rom.. a stock rooted rom.. and flashable boot, modem and bootloader zips.
Requirements:
You must have TWRP 2.8.7+ installed to use these files. Thanks to Dees_Troy as always for that. And, of course, you must have your bootloader unlocked for TWRP to work. Please do not ask if "model x" is supported... did you unlock via LG's official unlock tool? Yes? then you can use it. No? then you can't.
Downloads:
ROMS:
Your options are 100% stock rom or 100% stock rom + root. No customizations here. Rom is odexed. Zip flashable in TWRP.
LG-H81510A-Flashable.System.Boot.zip
100% stock untouched system/rom and stock boot.img (kernel + dtb + ramdisk).
Not going to upload a rooted image this time... just a waste of space. Easier to just flash stock/untouched rom then flash the SuperSU zip from Chainfire... or just let TWRP root it (when you go to reset to system, if TWRP detects no root it will ask if you want TWRP to root you).
Latest SuperSu zip can always be downloaded here - download.chainfire.eu/supersu
Thanks as always to Chainfire for maintaining SuperSU!
Extras:
TWRP-Flashable stock extras. If you ever need to restore the modem, boot or bootloader.. these are the files that make it easy.
LG-H81510A-Flashable.Modem.zip
This is a flashable stock 10A modem.
LG-H81510A-Flashable.Boot.zip
This is a flashable stock 10A boot.img. Boot.img contains kernel + dtb + ramdisk.
LG-H81510A-Flashable.Bootloader.zip
This is a flashable stock 10A bootloader. It contains aboot, factory, hyp, laf, rpm, sbl1, sdi, sec and tz.
Also, all stock images are available from @wolfgart's CODEFIRE DIRECTORY
#TEAMCODEFIRE
Click to expand...
Click to collapse
y u quote OP?
?
Sent from my Nexus 6 using Tapatalk
Yo
Sent from my LG G4
Second ROM is on the way..
So, with this ROM we can return the phone to locked/stock bootloader? What does the 10A stand for? Sorry I haven't ROM'ed in a few years (since a few HTC's ago), been just rooting for the last few years and using Nova Launcher. Is this still only for H815 EU's (which are able to have the BL unlocked via LG) or is this for all H815's?
thank you sir
TWRP-Link dont work on me.
But if it is the modified with simlink from @Wolfgart, than recovery works (backup/recovery), tested much times, all fine
http://techerrata.com/dees_troy/p1.img
Example: tried Xposed arm64 = bootloop! !!! dont test Xposed yet!!! all testers got bootloop
--> recovery and back in the world
most know, BUT FIRST after getting unlock and TWRP --> do a NANDROID!!! and TEST it!!!
Since most of us don't have root, me including(H815-L) i wonder if we somehow can install it via LG Flash tool, like a KDZ file?
i messed up..
its flashing of "LG-H81510A-Flashable.RootedSystem.Boot.zip" enough, or do i need to flash modem, bootloader too
masze said:
i messed up..
its flashing of "LG-H81510A-Flashable.RootedSystem.Boot.zip" enough, or do i need to flash modem, bootloader too
Click to expand...
Click to collapse
if you just have all other partitions stock and cleaned you only have to flash "LG-H81510A-Flashable.RootedSystem.Boot.zip" (system and boot img included).
wolfgart said:
if you just have all other partitions stock and cleaned you only have to flash "LG-H81510A-Flashable.RootedSystem.Boot.zip" (system and boot img included).
Click to expand...
Click to collapse
its totally wiped and erased.. nothing!!
im reach twrp thru Hard reset..
masze said:
its totally wiped and erased.. nothing!!
Click to expand...
Click to collapse
mhh ?
which is your situation now. It's not clear reading your post.
wolfgart said:
mhh ?
which is your situation now. It's not clear reading your post.
Click to expand...
Click to collapse
not booting, but i can get into twrp via hard reset button comb.. so im able to flash
(i know this is a f***** mess)
do think i can rescue my phone?
do i need to flash more files you think..
system, boot, modem and bootloader!! in that order?
masze said:
not booting, but i can get into twrp via hard reset button comb.. so im able to flash
Click to expand...
Click to collapse
ah ok.
so upload in your sdcard :
LG-H81510A-Flashable.Bootloader.zip
LG-H81510A-Flashable.Modem.zip
LG-H81510A-Flashable.RootedSystem.Boot.zip (if you want stock rooted one or other zip if you want unrooted one)
and flash in this order. Before flash all this job make a system/dalvik/cache wipe from TWRP
after all flash ended reboot your G4
wolfgart said:
ah ok.
so upload in your sdcard :
LG-H81510A-Flashable.Bootloader.zip
LG-H81510A-Flashable.Modem.zip
LG-H81510A-Flashable.RootedSystem.Boot.zip (if you want stock rooted one or other zip if you want unrooted one)
and flash in this order. Before flash all this job make a system/dalvik/cache wipe from TWRP
Click to expand...
Click to collapse
i love you! thanks bro
Can i send you a donation?
---------- Post added at 10:05 AM ---------- Previous post was at 09:58 AM ----------
ok, here it goes! all files on sd.
im report back, how it goes!
EDIT:
Fail to flash bootloader!
E:error executing updater binare in zip LG-H81510A-Flashable.bootloader.zip
EDIT2:
Skipped to flash bootloader.. flashed RootedSystem.Boot and modem...
and my phone booted up!!!!
YES!!!!!!
can give a detailed instructions on what to do? too scared i might missed on something that could potentially brick my phone
Sent from my LG-H815 using Tapatalk 2
@wolfgart
Could you list partition of H815 EU to me ? Maybe I will devs adb tools for LGG4 like LGG2.
ll /dev/block/platform/soc.0/by-name
Did you do this rom with a TWRP backup or do you have the official KDZ file? I formatted system partition, so no more recovery or OS and I can't us ADB
somboons said:
@wolfgart
Could you list partition of H815 EU to me ? Maybe I will devs adb tools for LGG4 like LGG2.
ll /dev/block/platform/soc.0/by-name
Click to expand...
Click to collapse
just done on the first day....
http://pastebin.com/7jJT96Rn
Make attention that on booted OS you can see platform name as : f9824900.sdhci
Accessing adb shell from TWRP Recovery you will have platform's name as : soc.0
wolfgart said:
just done on the first day....
http://pastebin.com/7jJT96Rn
Make attention that on booted OS you can see platform name as : f9824900.sdhci
Accessing adb shell from TWRP Recovery you will have platform's name as : soc.0
Click to expand...
Click to collapse
Thank you.like H818P
ll /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 2015-01-09 15:04 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-09 15:04 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-09 15:04 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-09 15:04 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-09 15:04 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-09 15:04 cache -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-09 15:04 cust -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-09 15:04 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-09 15:04 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-09 15:04 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-01-09 15:04 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-09 15:04 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-09 15:04 factory -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-09 15:04 fota -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-09 15:04 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-09 15:04 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-09 15:04 grow -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-09 15:04 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-09 15:04 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-09 15:04 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-09 15:04 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-09 15:04 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-09 15:04 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-09 15:04 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-09 15:04 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-09 15:04 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-09 15:04 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-09 15:04 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-09 15:04 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-09 15:04 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-09 15:04 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-09 15:04 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-09 15:04 raw_resources -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-01-09 15:04 raw_resourcesbak -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-01-09 15:04 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-09 15:04 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-09 15:04 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-09 15:04 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-09 15:04 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-09 15:04 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-09 15:04 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-09 15:04 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-09 15:04 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-09 15:04 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-09 15:04 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-09 15:04 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-09 15:04 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-09 15:04 system -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-09 15:04 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-09 15:04 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-09 15:04 userdata -> /dev/block/mmcblk0p50
[email protected]:/ $
Click to expand...
Click to collapse
Hello.
So, as I described here, I success got root on this device. Now, I want a full backup in case things going bad. And obvious, a way to restore this backup.
I was searching for days for a ROM, but it simply don't exist (yet). This model have an identification (alps l1 mp6 v2 gxq6580 weg l p69) wich is used in some other devices (includings Samsung clones), so, I checked all the ROMs I found looking into /system partition on my device and comparing with /system image of the ROMs (I used SuperR's Kitchen), and none of them are equal, I mean, a lot of files (includind build.prop) are different, so there is a great chance to brick my phone if I use it.
Even if it is found, I can't restore with SP Flash Tools, because it don't work with this phone. I tried to readback, but it recognizes but never start. As the phone is a MT6580 based SoC, maybe is compatability issue also. MTK Droid Tools don't work also. It recognizes, but can't do anything (don't generate scatter, don't root, don't nothing), again maybe a compatibility also.
The stock recovery have no option to backup, and I'm afraid to flash a CWM or TWRP, because I don't know much about porting these things, and I don't have much information about partitions and these things yet. ADB while in recovery give me an unauthorized device, by the way.
The phone accept fastboot commands, but don't accept the 'fastboot boot image.img", to try a temporary recovery, it only accept the 'fastboot flash image.img'. As sayed on the thread above, the bootloader is now unlocked, by the way.
So... this the situation... Can't have backup for now. If it help you to help me, there is the result of ls -all /dev/block/platform/mtk-msdc.0/by-name/ command in adb shell:
Code:
1|[email protected]_weg_l:/ # ls -all /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2017-03-30 00:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-03-30 00:16 cache -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-03-30 00:16 expdb -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-03-30 00:16 flashinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-03-30 00:16 frp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-03-30 00:16 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-03-30 00:16 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-03-30 00:16 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-03-30 00:16 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-03-30 00:16 nvdata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-03-30 00:16 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-03-30 00:16 oemkeystore -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-03-30 00:16 para -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-03-30 00:16 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-03-30 00:16 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-03-30 00:16 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-03-30 00:16 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-03-30 00:16 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-03-30 00:16 secro -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-03-30 00:16 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-03-30 00:16 userdata -> /dev/block/mmcblk0p20
[email protected]_weg_l:/ #
I sucessfully (I think) dump a boot image with dd command (dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img), but I'm not sure it is 100% perfect and if it can be safely used to restore (and how to restore... maybe 'fastboot flash'?). Maybe I can dump some other images, but I don't tried yet.
If you need any other information, I reply in almost same time.
Thanks in advice.
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
romulocarlos said:
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
Click to expand...
Click to collapse
Hello, i have recently posted a complete ROM on needrom. https://www.needrom.com/download/sony-xperia-c6-clone-mt6580/
i guess that is the one your are looking for. Good luck and sorry for my bad englich.
Help
Rom is corrupted, is not it? It's working? tell me how to download, I thank you
I have a problem with my Mi A2 Lite.
I have installed the Lineage OS ROM: https://forum.xda-developers.com/mi-a2-lite/development/lineageos-16-0-xiaomi-mi-a2-lite-t3919060
It seems that works only one slot, the slot B.
I flash the updates of the rom following this guide: https://github.com/tkchn/daisyinstall/blob/master/README.md
If the active slot is the slot B, when I install an update of the rom in the slot A and then change the active slot to slot A in TWRP, then reboot and the phone goes in bootloop with the androidone logo.
Then I reboot the phone holding the power button, boot to fastboot and boot to recovery.
As this point I repeat the whole process, flashing the rom to slot B and changing the active slot to slot B and now if I reboot the phone all work.
I had this problem with all the updates that I have done.
You have probably different firmware versions on each partition. You can fix that by writing the B partitions into the A ones.
Go to twrp, and through either 'adb shell' or the recovery shell:
Code:
su
dd if=/dev/block/mmcblk0p32 of=/dev/block/mmcblk0p31
dd if=/dev/block/mmcblk0p27 of=/dev/block/mmcblk0p26
dd if=/dev/block/mmcblk0p25 of=/dev/block/mmcblk0p24
dd if=/dev/block/mmcblk0p14 of=/dev/block/mmcblk0p13
dd if=/dev/block/mmcblk0p45 of=/dev/block/mmcblk0p44
dd if=/dev/block/mmcblk0p29 of=/dev/block/mmcblk0p28
dd if=/dev/block/mmcblk0p48 of=/dev/block/mmcblk0p47
dd if=/dev/block/mmcblk0p55 of=/dev/block/mmcblk0p54
dd if=/dev/block/mmcblk0p20 of=/dev/block/mmcblk0p19
dd if=/dev/block/mmcblk0p18 of=/dev/block/mmcblk0p17
dd if=/dev/block/mmcblk0p59 of=/dev/block/mmcblk0p58
You should have exactly similar A/B partitions after this (except for system and boot, the ones updated), and there should be no problem.
With custom rom...
Install the rom , TWRP and disable encryption in slot A
Install gapps, magisk, kernel, etc in slot B
The device only boots in B slot
In stock rom boots in A slot
Its ok
GDFI said:
You have probably different firmware versions on each partition. You can fix that by writing the B partitions into the A ones.
Go to twrp, and through either 'adb shell' or the recovery shell:
Code:
su
dd if=/dev/block/mmcblk0p32 of=/dev/block/mmcblk0p31
dd if=/dev/block/mmcblk0p27 of=/dev/block/mmcblk0p26
dd if=/dev/block/mmcblk0p25 of=/dev/block/mmcblk0p24
dd if=/dev/block/mmcblk0p14 of=/dev/block/mmcblk0p13
dd if=/dev/block/mmcblk0p45 of=/dev/block/mmcblk0p44
dd if=/dev/block/mmcblk0p29 of=/dev/block/mmcblk0p28
dd if=/dev/block/mmcblk0p48 of=/dev/block/mmcblk0p47
dd if=/dev/block/mmcblk0p55 of=/dev/block/mmcblk0p54
dd if=/dev/block/mmcblk0p20 of=/dev/block/mmcblk0p19
dd if=/dev/block/mmcblk0p18 of=/dev/block/mmcblk0p17
dd if=/dev/block/mmcblk0p59 of=/dev/block/mmcblk0p58
You should have exactly similar A/B partitions after this (except for system and boot, the ones updated), and there should be no problem.
Click to expand...
Click to collapse
Thank you very much @GDFI!
Probably I have android 8 in slot A and android 9 in slot B.
I will try to do this. Will all my data and settings survive this?
For knowledge, is there a list to understand what mmcblk**** partitions match?
leechgid said:
With custom rom...
Install the rom , TWRP and disable encryption in slot A
Install gapps, magisk, kernel, etc in slot B
The device only boots in B slot
In stock rom boots in A slot
Its ok
Click to expand...
Click to collapse
I don't understand, can you explain better?
I found how to see the list of partitions of the Mi A2 Lite:
Code:
daisy:/ # ls -l /dev/block/platform/soc/7824900.sdhci/by-name/
total 0
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 DDR -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 aboot_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 aboot_b -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 apdp -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 bk1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 bk2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 bk3 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 bk4 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 bk5 -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 bk6 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 boot_a -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 boot_b -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 cmnlib64_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 cmnlib64_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 cmnlib_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 cmnlib_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 config -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 devcfg_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 devcfg_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 devinfo -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 dip -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 dpo -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 dsp_a -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 dsp_b -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 fsc -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 fsg -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 keymaster_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 keymaster_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 keystore -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 limits -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 lksecapp -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 lksecappbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 logdump -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 mcfg -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 mdtp_a -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 mdtp_b -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 modem_a -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 modem_b -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 modemst1 -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 modemst2 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 mota -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 msadp -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 persist -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 persistbak -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 rpm_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 rpm_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 sbl1_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 sbl1_b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 sec -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 splash -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 ssd -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 syscfg -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 system_a -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 system_b -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_a -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_b -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 userdata -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 vendor_a -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 vendor_b -> /dev/block/mmcblk0p59
@GDFI You have omitted three partitions: system, boot, tz.
I understand system and boot, but what is the tz partition?
Should not be copied?
Code:
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_a -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_b -> /dev/block/mmcblk0p36
epcesp said:
@GDFI You have omitted three partitions: system, boot, tz.
I understand system and boot, but what is the tz partition?
Should not be copied?
Code:
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_a -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_b -> /dev/block/mmcblk0p36
Click to expand...
Click to collapse
Sorry I omitted the TZ partition by error, it must be copied from b to a too. (not important here but if you want to have an idea about every partition "role" : https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565 )
For the boot and system partitions, you can also flash them from the B slot to the A one if you want, but when you flash an update from the B slot, the new system.img and boot.img from the update will be flashed into the A partitions ; so there's no absolute need to copy them manually unless you want to try booting from the A slot without updating. (I hope I am somehow clear lol )
Oh and it won't affect your data at all!
GDFI said:
Sorry I omitted the TZ partition by error, it must be copied from b to a too. (not important here but if you want to have an idea about every partition "role" : https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565 )
For the boot and system partitions, you can also flash them from the B slot to the A one if you want, but when you flash an update from the B slot, the new system.img and boot.img from the update will be flashed into the A partitions ; so there's no absolute need to copy them manually unless you want to try booting from the A slot without updating. (I hope I am somehow clear lol )
Oh and it won't affect your data at all!
Click to expand...
Click to collapse
Thanks, you were very clear!
Definitely, I used these commands:
Code:
su
dd if=/dev/block/mmcblk0p32 of=/dev/block/mmcblk0p31 # aboot_b -> aboot_a
dd if=/dev/block/mmcblk0p52 of=/dev/block/mmcblk0p51 # boot_b -> boot_a
dd if=/dev/block/mmcblk0p27 of=/dev/block/mmcblk0p26 # cmnlib64_b -> cmnlib64_a
dd if=/dev/block/mmcblk0p25 of=/dev/block/mmcblk0p24 # cmnlib_b -> cmnlib_a
dd if=/dev/block/mmcblk0p14 of=/dev/block/mmcblk0p13 # devcfg_b -> devcfg_a
dd if=/dev/block/mmcblk0p45 of=/dev/block/mmcblk0p44 # dsp_b -> dsp_a
dd if=/dev/block/mmcblk0p29 of=/dev/block/mmcblk0p28 # keymaster_b -> keymaster_a
dd if=/dev/block/mmcblk0p48 of=/dev/block/mmcblk0p47 # mdtp_b -> mdtp_a
dd if=/dev/block/mmcblk0p55 of=/dev/block/mmcblk0p54 # modem_b -> modem_a
dd if=/dev/block/mmcblk0p20 of=/dev/block/mmcblk0p19 # rpm_b -> rpm_a
dd if=/dev/block/mmcblk0p18 of=/dev/block/mmcblk0p17 # sbl1_b -> sbl1_a
dd if=/dev/block/mmcblk0p57 of=/dev/block/mmcblk0p56 # system_b -> system_a
dd if=/dev/block/mmcblk0p36 of=/dev/block/mmcblk0p35 # tz_b -> tz_a
dd if=/dev/block/mmcblk0p59 of=/dev/block/mmcblk0p58 # vendor_b -> vendor_a
Now I have to wait the next update to see if it works.
I have a doubt, if the custom roms only change the system and boot partitions, does that mean that without having the original rom the other partitions will no longer be updated?
epcesp said:
Now I have to wait the next update to see if it works.
I have a doubt, if the custom roms only change the system and boot partitions, does that mean that without having the original rom the other partitions will no longer be updated?
Click to expand...
Click to collapse
Nice!
Yep, the custom roms rely on stock vendor, modem etc... and if you install one on the top of 10.0.0.3 stock for example, the vendor, modem, about, and other partitions will keep the same version and won't be updated with the custom rom updates.
You can update them manually by flashing newer images of those partitions (that can be extracted from ota updates), as long as the new version is still compatible with the rom ; for example a custom rom made to be compatible with an Oreo vendor may not work if the vendor is updated to its Pie version (The vendor having an Oreo version in the slot A might be the reason you couldn't boot :v ). Some developers recommend to use certain versions sometimes.
In short, those partitions won't be updated unless you want to do it manually
Clear, but if I want to update to latest version, mantaining my data and my rom, which partitions should I flash?
All except system and boot?
Yes, you flash everything except system and boot.
But one important thing is : if you have disabled encryption, flashing an update of vendor partition will re-enable forced encryption, so you would need to go to TWRP just after flashing and install Encryption disabler zip BEFORE the first boot, otherwise your data would be encrypted directly after first booting.
I made an update of the rom and now the phone works also in slot a, thanks @GDFI!
GDFI said:
Yes, you flash everything except system and boot.
But one important thing is : if you have disabled encryption, flashing an update of vendor partition will re-enable forced encryption, so you would need to go to TWRP just after flashing and install Encryption disabler zip BEFORE the first boot, otherwise your data would be encrypted directly after first booting.
Click to expand...
Click to collapse
What happens if I have my data already encrypted? I encrypted the phone from android settings.
When I installed the rom for the first time I flashed also force encryption disabled, as reported in the installation guide. Then in the rom from android security settings I encrypted the phone.
I'm not very sure about the purpouse of force encryption disabler.
epcesp said:
What happens if I have my data already encrypted? I encrypted the phone from android settings.
When I installed the rom for the first time I flashed also force encryption disabled, as reported in the installation guide. Then in the rom from android security settings I encrypted the phone.
I'm not very sure about the purpouse of force encryption disabler.
Click to expand...
Click to collapse
Happy it worked
Some ROMs don't support encryption, and TWRP especially cannot read encrypted data so most people prefer disable it. Since you're already encrypted, you can ignore the Disabler stuff!
Ok, thank you very much for all the support!