[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)

Aug 2, 2018
10
1
0
i cant seem to install salt because im unable to use (install actually) gksu. my lubuntu cannot find it and wont allow me to install a .deb...
what should i do? (gksu is removed from ubuntu for obsoleteness or something...)

also i cant seem to find in my firmware:
  • pmic
  • sdi
  • hyp
is this normal? ( i have lg k20 plus mp260)
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,593
14,810
263
i cant seem to install salt because im unable to use (install actually) gksu. my lubuntu cannot find it and wont allow me to install a .deb...
what should i do? (gksu is removed from ubuntu for obsoleteness or something...)

also i cant seem to find in my firmware:
pmic
sdi
hyp

is this normal? ( i have lg k20 plus mp260)
LG seems to name on every device partitions different.. So I can't say if you have those and how they are named.. You can run SALT and open the advanced menu to list all partitions on your phone.

Start SALT from the cli is a workaround for your issue. It will use sudo as a fallback.
To fix it in the shortcut you need to add a sudoers rule and start with sudo or use pkexec like I do in FWUL https://github.com/Carbon-Fusion/build_fwul/commit/8dadd2edb688f9b6f60e01aa7192dc01a843c503 or use one of the graphical gksu replacements.


Sent from my LG-H815 using XDA Labs
 
Aug 2, 2018
10
1
0
Start SALT from the cli is a workaround for your issue. It will use sudo as a fallback.
To fix it in the shortcut you need to add a sudoers rule and start with sudo or use pkexec like I do in FWUL https://github.com/Carbon-Fusion/build_fwul/commit/8dadd2edb688f9b6f60e01aa7192dc01a843c503 or use one of the graphical gksu replacements.
my deepest apologies, but this is my first time ever using a linux os, so i have no idea what your talking about in the work around and how to do it:p
 
Aug 2, 2018
10
1
0
If that's the case why tampering around with a random linux? Just use FWUL.
When I try to boot it (via USB), it gives me an error:
'/Dev/disk/by-lable/fwulforever' device did not show up after 30 seconds...
Falling back to interactive prompt
You can try to fix this problem manually, log when you are finished
Sh: can't access tty; job control turned off
[Rootfs ]#_


I'm using a lower end computer which might be the problem...
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,593
14,810
263
When I try to boot it (via USB), it gives me an error:
'/Dev/disk/by-lable/fwulforever' device did not show up after 30 seconds...
Falling back to interactive prompt
You can try to fix this problem manually, log when you are finished
Sh: can't access tty; job control turned off
[Rootfs ]#_

I'm using a lower end computer which might be the problem...
Ok one last question as this is going to be completely off Topic now:

is your computer 32-bit or 64-bit?

If it is 32-bit FWUL will not work that's true.
if it is 64 bit then the way you flashed it went wrong and so ask for support in the FWUL thread

If you better want to go on with the Linux you have or if your computer is 32-bit then ask in the SALT thread for further support


Sent from my LG-H815 using XDA Labs
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,593
14,810
263
Aug 8, 2018
11
0
0
Please Help USUd Device 9008 mode Unbrick

[*]11. Now everything is prepared. Take out your sdcard. Take out the battery and disconnect cable. Plugin the external sdcard. Put battery back.
Press volume up (only this) and keep it pressed.
Then connect USB cable while still keep the pressure on volume up for 20 seconds.
The download mode should come up. Congrats you can now use lgup to completely unbrick.
[/LIST]

Have fun! :highfive:[/QUOTE]

HI,

What is wrong? Could you please help. It is LG G4 US991 USUd. Salt compatible: LG Unfortunately flashed H811 20v Bootloader stack, modem and Lineage OS ROM. It is 9008/QDL mode. I followed your instruction carefully to unbrick. But nothing happens. Neither goes to Fastboot nor Download mode. Below is the Terminal commands I did. Thanks in advance.
[email protected] ~]$ cd /tmp/extracteddz
[[email protected] extracteddz]$ sudo -s
[fwul extracteddz]# dd if=PrimaryGPT.gpt of=/dev/mmcblk0
34+0 records in
34+0 records out
17408 bytes (17 kB, 17 KiB) copied, 0.00024933 s, 69.8 MB/s
[fwul extracteddz]# sync
[fwul extracteddz]# ls -la /dev/disk/by-partlabel/sbl1
-rw-r--r-- 1 root root 1048576 Sep 5 01:05 /dev/disk/by-partlabel/sbl1
[fwul extracteddz]# cd /tmp/extracteddz
[fwul extracteddz]# dd if=sbl1.image of=/dev/disk/by-partlabel/sbl1
2048+0 records in
2048+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.00484891 s, 216 MB/s
[fwul extracteddz]# dd if=hyp.image of=/dev/disk/by-partlabel/hyp
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0.00407234 s, 129 MB/s
[fwul extracteddz]# dd if=pmic.image of=/dev/disk/by-partlabel/pmic
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0.00384574 s, 136 MB/s
[fwul extracteddz]# dd if=rpm.image of=/dev/disk/by-partlabel/rpm
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0.00436034 s, 120 MB/s
[fwul extracteddz]# dd if=tz.image of=/dev/disk/by-partlabel/tz
2048+0 records in
2048+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0068827 s, 152 MB/s
[fwul extracteddz]# dd if=sdi.image of=/dev/disk/by-partlabel/sdi
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0.00276343 s, 190 MB/s
[fwul extracteddz]# dd if=laf_UsU.img of=/dev/disk/by-partlabel/laf
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 0.262063 s, 192 MB/s
[fwul extracteddz]# dd if=aboot_UsU.img of=/dev/disk/by-partlabel/aboot
4096+0 records in
4096+0 records out
2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.012583 s, 167 MB/s
[fwul extracteddz]# dd if=rawres_UsU.img of=/dev/disk/by-partlabel/raw_resources
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0204343 s, 205 MB/s
[fwul extracteddz]# sync
[fwul extracteddz]# sudo fdisk -l /dev/mmcblk0
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/mmcblk0: 59.6 GiB, 64021856256 bytes, 125042688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 98101B32-BBE2-4BF2-A06E-2BB33D000C20

Device Start End Sectors Size Type
/dev/mmcblk0p1 32768 208895 176128 86M Microsoft basic data
/dev/mmcblk0p2 229376 230399 1024 512K unknown
/dev/mmcblk0p3 230400 232447 2048 1M unknown
/dev/mmcblk0p4 232448 234495 2048 1M unknown
/dev/mmcblk0p5 234496 235519 1024 512K unknown
/dev/mmcblk0p6 235520 236543 1024 512K unknown
/dev/mmcblk0p7 236544 237567 1024 512K unknown
/dev/mmcblk0p8 237568 241663 4096 2M unknown
/dev/mmcblk0p9 241664 243711 2048 1M unknown
/dev/mmcblk0p10 243712 244735 1024 512K unknown
/dev/mmcblk0p11 244736 246783 2048 1M unknown
/dev/mmcblk0p12 246784 247807 1024 512K unknown
/dev/mmcblk0p13 247808 248831 1024 512K unknown
/dev/mmcblk0p14 248832 252927 4096 2M unknown
/dev/mmcblk0p15 252928 253951 1024 512K unknown
/dev/mmcblk0p16 253952 254975 1024 512K unknown
/dev/mmcblk0p17 254976 255999 1024 512K unknown
/dev/mmcblk0p18 256000 257023 1024 512K unknown
/dev/mmcblk0p19 257024 258047 1024 512K unknown
/dev/mmcblk0p20 258048 259071 1024 512K unknown
/dev/mmcblk0p21 259072 262143 3072 1.5M unknown
/dev/mmcblk0p22 262144 294911 32768 16M unknown
/dev/mmcblk0p23 294912 360447 65536 32M unknown
/dev/mmcblk0p24 360448 363519 3072 1.5M unknown
/dev/mmcblk0p25 363520 366591 3072 1.5M unknown
/dev/mmcblk0p26 366592 369663 3072 1.5M unknown
/dev/mmcblk0p27 369664 370687 1024 512K unknown
/dev/mmcblk0p28 370688 371711 1024 512K unknown
/dev/mmcblk0p29 371712 372735 1024 512K unknown
/dev/mmcblk0p30 372736 376831 4096 2M unknown
/dev/mmcblk0p31 376832 377855 1024 512K unknown
/dev/mmcblk0p32 377856 378879 1024 512K unknown
/dev/mmcblk0p33 378880 379903 1024 512K unknown
/dev/mmcblk0p34 379904 380927 1024 512K unknown
/dev/mmcblk0p35 380928 385023 4096 2M Microsoft basic data
/dev/mmcblk0p36 385024 393215 8192 4M unknown
/dev/mmcblk0p37 393216 491519 98304 48M unknown
/dev/mmcblk0p38 491520 573439 81920 40M unknown
/dev/mmcblk0p39 573440 655359 81920 40M unknown
/dev/mmcblk0p40 655360 671743 16384 8M Microsoft basic data
/dev/mmcblk0p41 671744 688127 16384 8M Microsoft basic data
/dev/mmcblk0p42 688128 753663 65536 32M Microsoft basic data
/dev/mmcblk0p43 753664 770047 16384 8M Microsoft basic data
/dev/mmcblk0p44 770048 778239 8192 4M unknown
/dev/mmcblk0p45 778240 786431 8192 4M unknown
/dev/mmcblk0p46 786432 819199 32768 16M Microsoft basic data
/dev/mmcblk0p47 819200 901119 81920 40M Microsoft basic data
/dev/mmcblk0p48 901120 917503 16384 8M Microsoft basic data
/dev/mmcblk0p49 917504 1011711 94208 46M unknown
/dev/mmcblk0p50 1011712 1015807 4096 2M unknown
/dev/mmcblk0p51 1015808 1036287 20480 10M unknown
/dev/mmcblk0p52 1036288 1048575 12288 6M unknown
/dev/mmcblk0p53 1048576 9822207 8773632 4.2G unknown
/dev/mmcblk0p54 9822208 12345343 2523136 1.2G unknown
/dev/mmcblk0p55 12345344 61046783 48701440 23.2G unknown
/dev/mmcblk0p56 61046784 61071326 24543 12M Microsoft basic data
 

Hotdogint

Member
Aug 22, 2014
25
3
23
I think I was trying to flash the h811 modem to the h812 to fix the hardware issues. At that point I tried 20+ different combinations of installing modems with kernals and roms. I figured since the rom compabilty said h811 I could use the h811 modem on it, I was very wrong. I might have played around with the boot although I do not 100% remember if I actaully did
drive DOT google DOT com/open?id=1_vtDBsT9m1LpB14iKQkBGwGtL3JQzq6A
I was playing around with the phone and I noticed that the back of the phone indicates its an h810. Is there any possibility that the LG repair service replaced the phone with a different motherboard than the one I sent in (h812)?
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,593
14,810
263
I was playing around with the phone and I noticed that the back of the phone indicates its an h810. Is there any possibility that the LG repair service replaced the phone with a different motherboard than the one I sent in (h812)?
yes and that happened dozens of times already and those devices are what we call Frankensteins.
You have to disassemble it to find out the truth --> https://www.ifixit.com/Guide/LG+G4+Motherboard+Replacement/51202

.
 

Hotdogint

Member
Aug 22, 2014
25
3
23
yes and that happened dozens of times already and those devices are what we call Frankensteins.
You have to disassemble it to find out the truth --> https://www.ifixit.com/Guide/LG+G4+Motherboard+Replacement/51202

.
OK, I'll verify when I get home. Let's say it is the h810 anti-rollback v0, would I just need to follow the instruction for the h810 and LGUP and so on and it will unbrick my phone (unbricked without sd card)? Or considering my situation, is my phone always bricked unless I use an sd card?
 

sliiip1

New member
Oct 11, 2018
2
0
0
Hi. I buy a h811 (ref) with h81120o fw.
(h810_MAIN_1.0 on MB)
I flash LOS 15.1 (with fastboot boot twrp.image i didn't flash twrp).
Then i try to roll back and bricked a phone. I use sd card and finally boot. But its works only with sd card. I try many stock roms and none of them boot w\o sd card. So I try to flash LOS again (as last functional rom) aaand bricked like never before.
I can go download mode from sd card but pc dont recognize them:

dmesg with sd card in download mode:
Code:
[ 5283.198032] usb 1-5: new high-speed USB device number 13 using ehci-pci
[ 5288.532096] usb 1-5: device descriptor read/64, error -110
dmesg when i plug phone without sd card with vol up(black screen):
Code:
[ 5315.882438] qcserial 1-5:1.0: Qualcomm USB modem converter detected
[ 5315.882606] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB0
Do the bridge method helps me or i need to go to service center and reball emmc?
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,593
14,810
263
Hi. I buy a h811 (ref) with h81120o fw.
(h810_MAIN_1.0 on MB)
I flash LOS 15.1 (with fastboot boot twrp.image i didn't flash twrp).
Then i try to roll back and bricked a phone. I use sd card and finally boot. But its works only with sd card. I try many stock roms and none of them boot w\o sd card. So I try to flash LOS again (as last functional rom) aaand bricked like never before.
I can go download mode from sd card but pc dont recognize them:

dmesg with sd card in download mode:


dmesg when i plug phone without sd card with vol up(black screen):


Do the bridge method helps me or i need to go to service center and reball emmc?
If you want help meet on IRC from Mondays to Fridays.
The OP for FWUL, TWRP or SALT lists how to easily access IRC.


Sent from my LG-H815 using XDA Labs
 

synescu

Senior Member
Jan 22, 2013
186
115
0
Anyone in this thread ever succeeded with an LG G5 phone or newer? I am struggling for 7 month's now with the G5 h840 I even tried restoring a complete backup off mmcblk0 frome a working (rooted) h840 in tho a 32GB sdcard My phone have the entire mmcblk0 erased. Any advice?
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,593
14,810
263
Anyone in this thread ever succeeded with an LG G5 phone or newer? I am struggling for 7 month's now with the G5 h840 I even tried restoring a complete backup off mmcblk0 frome a working (rooted) h840 in tho a 32GB sdcard My phone have the entire mmcblk0 erased. Any advice?
Do you have tried this method here already?


Sent from my LG-H815 using XDA Labs
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,593
14,810
263
Yes I tried but unfortunately it didn't work for me
Your ARB matches? Thats the most important part. If you flash files with lower ARB it won't work.
The other thing is use a bigger sdcard then your internal storage, i.e. if your storage is 32gb use a 64gb card. The reason is that many manufactors sell cards which are a little bit lower then it's specs(e.g 31.5gb) and that will fail as well.


Sent from my LG-H815 using XDA Labs
 

synescu

Senior Member
Jan 22, 2013
186
115
0
I will try with a bigger sdcard. Thank you for your time
Your ARB matches? Thats the most important part. If you flash files with lower ARB it won't work.
The other thing is use a bigger sdcard then your internal storage, i.e. if your storage is 32gb use a 64gb card. The reason is that many manufactors sell cards which are a little bit lower then it's specs(e.g 31.5gb) and that will fail as well.


Sent from my LG-H815 using XDA Labs
Sent from my XT1580 using Tapatalk
 

noel_Fs

Senior Member
Aug 9, 2017
63
1
8
Hey there, so i bricked a LeEco Le Pro 3, sd820. We have the QFIL but the thing is that I basically erased the nand so I can't even boot to edl. I was wondering would a sdcard adapter using this method work? Flashing gpt_both and the firmware files to the sdcard and then trying to figure out which points to short on the motherboard? I know it's a bit yikes. Any help would be appreciated.