Was trying to install TWRP with Freegee but that didn't work. Tried ADB to install TWRP and used ADB to boot to recovery. After LG logo everything went black. Disconnect battery and then booted again. Then tried OTA to Kitkat (from JB) and now nothing works. When power on LG logo shows and then just black.
When I plug in the usb, Windows asked to format drives (I think partitions) I,J,K,L,M,N,O,P,Q,R,S,T,V,U in phone before it can read it. Same thing happens when trying download mode. Does it mean everything is corrupted? Beyond saving? Thanks for any suggestions.
I am in the same boat
pakron said:
Was trying to install TWRP with Freegee but that didn't work. Tried ADB to install TWRP and used ADB to boot to recovery. After LG logo everything went black. Disconnect battery and then booted again. Then tried OTA to Kitkat (from JB) and now nothing works. When power on LG logo shows and then just black.
When I plug in the usb, Windows asked to format drives (I think partitions) I,J,K,L,M,N,O,P,Q,R,S,T,V,U in phone before it can read it. Same thing happens when trying download mode. Does it mean everything is corrupted? Beyond saving? Thanks for any suggestions.
Click to expand...
Click to collapse
Keep Calm
and
Don't Format
Then follow this guide http://forum.xda-developers.com/showthread.php?t=2582142
I know nothing about Linux I guess I will just have to live with it. Thanks Drachenminister.
Drachenminister said:
Keep Calm
and
Don't Format
Then follow this guide http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
I have followed the instructions and still not able to get into recovery or download. I append below the scan of my G2 D800.
[email protected]:~# gdisk -l /dev/sdc
GPT fdisk (gdisk) version 0.8.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 40 entries
First usable sector is 34, last usable sector is 61071326
Partitions will be aligned on 2-sector boundaries
Total free space is 237512 sectors (116.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 32768 163839 64.0 MiB 0700 modem
2 163840 165887 1024.0 KiB FFFF sbl1
3 165888 166911 512.0 KiB FFFF dbi
4 196608 197631 512.0 KiB FFFF DDR
5 229376 231423 1024.0 KiB FFFF aboot
6 231424 233471 1024.0 KiB FFFF rpm
7 262144 294911 16.0 MiB FFFF boot
8 294912 296959 1024.0 KiB FFFF tz
9 296960 296961 1024 bytes 0700 pad
10 327680 333823 3.0 MiB FFFF modemst1
11 333824 339967 3.0 MiB FFFF modemst2
12 339968 339969 1024 bytes FFFF pad1
13 360448 393215 16.0 MiB FFFF misc
14 393216 458751 32.0 MiB 0700 persist
15 458752 491519 16.0 MiB FFFF recovery
16 491520 497663 3.0 MiB FFFF fsg
17 524288 525311 512.0 KiB FFFF fsc
18 525312 526335 512.0 KiB FFFF ssd
19 526336 526337 1024 bytes FFFF pad2
20 526338 527361 512.0 KiB FFFF encrypt
21 557056 573439 8.0 MiB 0700 drm
22 573440 589823 8.0 MiB 0700 sns
23 589824 622591 16.0 MiB 0700 ve
24 622592 688127 32.0 MiB FFFF laf
25 688128 753663 32.0 MiB FFFF fota
26 753664 819199 32.0 MiB 0700 mpt
27 819200 884735 32.0 MiB 0700 carrier
28 884736 901119 8.0 MiB 0700 eri
29 901120 905215 2.0 MiB FFFF blus
30 905216 906239 512.0 KiB FFFF dbibak
31 906240 908287 1024.0 KiB FFFF rpmbak
32 908288 910335 1024.0 KiB FFFF tzbak
33 910336 910351 8.0 KiB FFFF rct
34 917504 7733247 3.2 GiB 0700 system
35 7733248 9371647 800.0 MiB 0700 cache
36 9371648 9535487 80.0 MiB 0700 tombstones
37 9535488 9568255 16.0 MiB 0700 spare
38 9568256 61046783 24.5 GiB 0700 userdata
39 61046784 61071326 12.0 MiB 0700 grow
It said the first readable sector is 34 Does it mean everything above is corrupted. As directed have replaced the sbl1, aboot, rpm, tz, laf and twrp recovery files. What else can I try? Thanks.
Update: Fixed. Can't imagine its that simple! I was doing OTA from 10o to 10q when it bricked with symptoms described in this thread. I followed the instructions but still nothing. I also tried TWRP 2.6.3.3 and resulted with boot error. Then I tried the STOCK recovery and rebooted. Phone booted and started to upgrade to 10q which was downloaded before. Hope this helps.
Fixed
Drachenminister said:
Keep Calm
and
Don't Format
Then follow this guide http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Update: Fixed. Can't imagine its that simple! I was doing OTA from 10o to 10q when it bricked with symptoms described in this thread. I followed the instructions but still nothing. I also tried TWRP 2.6.3.3 and resulted with boot error. Then I tried the STOCK recovery and rebooted. Phone booted and started to upgrade to 10q which was downloaded before. Hope this helps.
pakron said:
Update: Fixed. Can't imagine its that simple! I was doing OTA from 10o to 10q when it bricked with symptoms described in this thread. I followed the instructions but still nothing. I also tried TWRP 2.6.3.3 and resulted with boot error. Then I tried the STOCK recovery and rebooted. Phone booted and started to upgrade to 10q which was downloaded before. Hope this helps.
Click to expand...
Click to collapse
Glad to here that you are back in business
Glatzi said:
Glad to here that you are back in business
Click to expand...
Click to collapse
.tot and flash
Note:
This is not bootanimation, this is the splash screen (the 'Huwaei' boot logo which is displayed when device is switched ON)
This is for Huawei Y6 Only..
(For other devices, please send me your splash.img so that I can create a tool for you too.)
NOTE: I think this tool is no longer working for latest firmwares.
Please check this new tool: [GUIDE] Changing boot splash image on the Huawei Y6
Requirements:
1. Rooted Huawei Y6 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create logo.img:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
1. Download & Extract this in computer: Huawei_Y6_Logo_Maker.zip
2. Make sure you have a 720x1280 resolution picture.
3. Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'Create_Logo.bat' to create logo.img , which you can find inside the "output" folder.
STEPS to flash logo.img:
Optional: To backup your original logo.img:
Code:
dd if=/dev/block/bootdevice/by-name/logo of=/sdcard/logo.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the logo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/logo.img of=/dev/block/bootdevice/by-name/logo
c. To flash from Fastboot mode:
Code:
fastboot flash logo logo.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock logo.img from custom recovery or fastboot.
Hit the Thanks :good: button if it worked for you
You're welcome to post the bootlogos that you created..
Thanks to @adam_s_459_ who provided the stock logo.img of his Huawei Y6 (SCL-L04)
Thank you so much for making this tool. I have been wanting to change that screen for so long as it is very ugly ?.
So I followed all of the steps and it made the logo.img but when I Flash it it just doesn't do anything. Just the same old Huawei logo ?
adam_s_459_ said:
So I followed all of the steps and it made the logo.img but when I Flash it it just doesn't do anything. Just the same old Huawei logo
Click to expand...
Click to collapse
Try method b) or c) to install logo.img..
I guess flashing from recovery doesn't work because the path to logo (partition) in the updater-script is wrong..
Or please tell where the "logo" block file is present in the /dev/block/ directory so that I'll edit that in the tool
GokulNC said:
Try method b) or c) to install logo.img..
I guess flashing from recovery doesn't work because the path to logo (partition) in the updater-script is wrong..
Or please tell where the "logo" block file is present in the /dev/block/ directory so that I'll edit that in the tool
Click to expand...
Click to collapse
I cannot find the logo file in that directory. I tried flashing from terminal and it didn't work. And I get an"external command not allowed" error in fastboot
adam_s_459_ said:
I cannot find the logo file in that directory. I tried flashing from terminal and it didn't work.
Click to expand...
Click to collapse
How did you extract the logo.img from your device then?
If you extracted it from stock firmware, please find out how it's flashed into device..
(If it's a flashable zip, send the updater-script.
If it's a fastboot flashable firmware, send me .bat files if there's any)
adam_s_459_ said:
And I get an"external command not allowed" error in fastboot
Click to expand...
Click to collapse
It means you have not setup the fastboot tool properly..
Search and follow the instructions to properly set it up
GokulNC said:
How did you extract the logo.img from your device then?
If you extracted it from stock firmware, please find out how it's flashed into device..
(If it's a flashable zip, send the updater-script.
If it's a fastboot flashable firmware, send me .bat files if there's any)
Click to expand...
Click to collapse
So for some reason I couldn't upload just the updater script but this is the flashable file with it in it. I extracted the logo.img from stock firmware. I don't really know how to find out how is flashed on the device sorry. I don't know where I would find any .Bat files because I am fairly new to this type of thing. I hope this helps. Thanks.
@adam_s_459_ I just examined the partition table of Huawei Y6..
Code:
Number Start (sector) End (sector) Size Code Name
1 34 1057 512.0 KiB FFFF sbl1
2 1058 2081 512.0 KiB FFFF hyp
3 8192 8255 32.0 KiB FFFF sec
4 8256 8319 32.0 KiB FFFF DDR
5 16384 17407 512.0 KiB FFFF rpm
6 17408 18431 512.0 KiB FFFF tz
7 18432 28543 4.9 MiB FFFF aboot
8 28544 30591 1024.0 KiB FFFF pad
9 30592 161663 64.0 MiB FFFF oeminfo
10 161664 169855 4.0 MiB FFFF misc
11 169856 178047 4.0 MiB FFFF modemst1
12 178048 186239 4.0 MiB FFFF modemst2
13 188416 196607 4.0 MiB FFFF fsg
14 196608 606207 200.0 MiB FFFF modem
15 606208 606209 1024 bytes FFFF fsc
16 606210 606225 8.0 KiB FFFF ssd
17 606226 737297 64.0 MiB FFFF log
18 745472 761855 8.0 MiB FFFF persist
19 761856 892927 64.0 MiB FFFF boot
20 892928 991231 48.0 MiB FFFF recovery
21 991232 1089535 48.0 MiB FFFF erecovery
22 1089536 1613823 256.0 MiB FFFF cache
23 1613824 2138111 256.0 MiB FFFF cust
24 2138112 5808127 1.8 GiB FFFF system
25 5808128 5808127 0 bytes 0700 userdata
As far as I can guess, maybe it resides in the misc partition..
Try flashing it to the misc partition.. (Back it up before you do)
Code:
fastboot flash misc logo.img
@adam_s_459_ If you think it's risky for you or if you don't seem to understand, please ask any other experienced ones in this forum to help me out here, to try on their device..
Because I don't own an Huawei Y6 device
GokulNC said:
@adam_s_459_ I just examined the partition table of Huawei Y6..
As far as I can guess, maybe it resides in the misc partition..
Try flashing it to the misc partition.. (Back it up before you do)
If you think it's risky for you or if you don't seem to understand, please ask any other experienced ones in this forum to help me out here, to try on their device..
Because I don't own an Huawei Y6 device
Click to expand...
Click to collapse
I'm going to see if I can Flash the current misc partition in fastboot before I do it. So I fastboot I just enter "fastboot flash misc logo.img"?
Stock Recovery Huawei Y6
I need Stock Recovery Huawei Y6
Please
Are u a huawei y6 developer
Stock Recovery Huawei Y6
Kompesjo said:
I need Stock Recovery Huawei Y6
Please
Click to expand...
Click to collapse
Hi,
I have all that you need but this is for Huawei Y6 (SCL-L02)
this device is a single sim, 8GB ROM & 1GB RAM
if ya need em email me [email protected]
GokulNC said:
@adam_s_459_ I just examined the partition table of Huawei Y6..
Code:
Number Start (sector) End (sector) Size Code Name
1 34 1057 512.0 KiB FFFF sbl1
2 1058 2081 512.0 KiB FFFF hyp
3 8192 8255 32.0 KiB FFFF sec
4 8256 8319 32.0 KiB FFFF DDR
5 16384 17407 512.0 KiB FFFF rpm
6 17408 18431 512.0 KiB FFFF tz
7 18432 28543 4.9 MiB FFFF aboot
8 28544 30591 1024.0 KiB FFFF pad
9 30592 161663 64.0 MiB FFFF oeminfo
10 161664 169855 4.0 MiB FFFF misc
11 169856 178047 4.0 MiB FFFF modemst1
12 178048 186239 4.0 MiB FFFF modemst2
13 188416 196607 4.0 MiB FFFF fsg
14 196608 606207 200.0 MiB FFFF modem
15 606208 606209 1024 bytes FFFF fsc
16 606210 606225 8.0 KiB FFFF ssd
17 606226 737297 64.0 MiB FFFF log
18 745472 761855 8.0 MiB FFFF persist
19 761856 892927 64.0 MiB FFFF boot
20 892928 991231 48.0 MiB FFFF recovery
21 991232 1089535 48.0 MiB FFFF erecovery
22 1089536 1613823 256.0 MiB FFFF cache
23 1613824 2138111 256.0 MiB FFFF cust
24 2138112 5808127 1.8 GiB FFFF system
25 5808128 5808127 0 bytes 0700 userdata
As far as I can guess, maybe it resides in the misc partition..
Try flashing it to the misc partition.. (Back it up before you do)
Code:
fastboot flash misc logo.img
@adam_s_459_ If you think it's risky for you or if you don't seem to understand, please ask any other experienced ones in this forum to help me out here, to try on their device..
Because I don't own an Huawei Y6 device
Click to expand...
Click to collapse
Respected Sir
I Need oeminfo Partition Backup Plz
Will Get Grateful For Help
Thanks Anticipation
shoaibrao said:
@adam_s_459_ I just examined the partition table of Huawei Y6..
As far as I can guess, maybe it resides in the misc partition..
Try flashing it to the misc partition.. (Back it up before you do)
Respected Sir
I Need oeminfo Partition Backup Plz
Will Get Grateful For Help
Thanks Anticipation
Click to expand...
Click to collapse
You should ask this on Huawei Y6 questions and answers
EDIT: I still need the partition listing, and there is still hope. I have a lead on the firehose_8996.mbn used to fix this very problem with the QFIL tool.
If I can get it, then I will need the partition layout in order to make the rawprogram0.xml file.
I am going to leave the post below because it WAS a good idea, and it does work on SD800, 801 and 808 chips. However ,this is no longer possible on 820 and above Snapdragon chips.
I decided to do some research on WHY there would be sda devices instead of mmcblk. sda is a DISK device, and mmcblk is a FLASH device. eMMC is flash. This is what I found...
From ehem's github:
The big problem is the G5 (and presumably other Qualcomm 82x devices) has its on-board flash presented as several physical devices. ie instead of /dev/mmcblk0p{0-56}, it has /dev/sd[a-e]. Each of the /dev/sd[a-e] devices has its own GPT, so undz.py needs to be modified to expect the need to handle multiple GPTs. Then there is the mysterious OP/OP_T slice where they're doing really interesting things.
Click to expand...
Click to collapse
The problem here is that you can't make an SDcard look like multiple whole disk block devices: sda, sdb, sdc, sdd, etc. or even mmcblk0, mmcblk1, etc. Without being able to do that, there is no way to create an image on an SDcard that the 820 chip will ever boot from.
I am not giving up hope. I know that the qfil files are out there (8996.mbn, recovery.xml and patch0.xml). Even if they are for another device, the XML files can be modified with information we can gain from a working V20.
Original post:
I am starting a new thread because I couldn't change the title of the last one, and there was a lot of "static".
So, I need someone with an H915 to run a couple of commands with the end result being that we will end up with an image that can be "burned" onto an SDcard, and recover from 9008 error bricks.
You will know you have a 9008 if your phone suddenly won't turn on, and nothing lights up when hooked to a PC. Another good indication (if you have Windows) is that it will say something like
qdloader / something / 9008 in device manager when the phone is connected (sorry, I use GNU/Linux, so I have no clue what the exact listing in device manager is).
This procedure will work on ANY Qualcomm Snapdragon based phone that has an SDcard slot, and I have successfully tested it on an LG G4, and an LG V10.
I was in the process of testing it on my V20, but my image was corrupt, and I ended up with a brick -- so now I turn to you.
This is for both the H915 and H910, but the reason I need an H915 is because there is a KDZ for the H915. The H910 and H915 are identical hardware.
So what are the risks to you? None as far as there being a risk to your phone, however, I could unintentionally have you send me sensitive data. For example, there is the EFS partition.
This contains your IMEI ... you don't want that out there. Also, there is the DATA partition. I think that one speaks for itself. However, I would never intentionally ask you to send me something,
but more importantly, if I did get something, it would be nulled. I will always list the risk of any command. For example: "Warning: This could contain the EFS partition!".
You can then decide if that is a risk you want to take.
The easiest thing by far would be for someone to just send me an entire dump of their eMMC, but as stated above, that would definitely contain sensitive info.
However, if there is a trusting soul out there that doesn't want to go through the pain below, please send me a PM
So with that disclaimer in mind, I need to start with the partition layout since I don't currently have a working V20.
There is ZERO risk involved with this. It is just a list of the partitions that are on ALL H915 phones.
First need to get into recovery.
Code:
adb reboot recovery
Once the phone is sitting in TWRP you can get the partition listing. The thing is I am not sure of the device name. It is dependent on the kernel you are using.
It could be either mmcblk0 or sda OR something else.
To find out you can run:
Code:
adb shell
ls /dev/block
You will see a bunch of entries, but we need the "whole disk" block device (you can ignore single entries, loop* and ram*). So, if you see a bunch of mmcblk0pXX then you know it is mmcblk0.
If you see a bunch of sdaXX, then you know it is sda. Once you find out, you will execute (replacing mmcblk0 with the appropriate device if needed):
Code:
fdisk -l /dev/block/mmcblk0
or
Code:
fdisk -l /dev/block/sda
Once that is done, please copy and paste the output into a post here. To give you an idea if you are close, this is what it looks like on an LG V10:
Code:
[dev01:~/h901] $ adb reboot recovery
[dev01:~/h901] $ adb shell
~ # fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Code Name
1 16384 192511 86.0M 0700 modem
2 192512 196607 2048K 0700 spare1
3 196608 197631 512K 0700 pmic
4 197632 199679 1024K 0700 sbl1
5 199680 201727 1024K 0700 tz
6 201728 202751 512K 0700 sdi
7 202752 203775 512K 0700 hyp
8 203776 204799 512K 0700 rpm
9 204800 208895 2048K 0700 aboot
10 208896 210943 1024K 0700 sbl1bak
11 210944 211967 512K 0700 pmicbak
12 211968 212991 512K 0700 hypbak
13 212992 215039 1024K 0700 tzbak
14 215040 216063 512K 0700 rpmbak
15 216064 220159 2048K 0700 abootbak
16 220160 221183 512K 0700 sdibak
17 221184 222207 512K 0700 limits
18 222208 223231 512K 0700 apdp
19 223232 224255 512K 0700 msadp
20 224256 225279 512K 0700 dpo
21 225280 229375 2048K 0700 spare2
22 229376 230399 512K 0700 persistent
23 230400 232447 1024K 0700 devinfo
24 232448 245759 6656K 0700 spare3
25 245760 278527 16.0M 0700 misc
26 278528 344063 32.0M 0700 persist
27 344064 347135 1536K 0700 modemst1
28 347136 350207 1536K 0700 modemst2
29 350208 353279 1536K 0700 fsg
30 353280 354303 512K 0700 fsc
31 354304 355327 512K 0700 ssd
32 355328 356351 512K 0700 keystore
33 356352 360447 2048K 0700 DDR
34 360448 361471 512K 0700 sec
35 361472 362495 512K 0700 encrypt
36 362496 363519 512K 0700 eksst
37 363520 364543 512K 0700 rct
38 364544 376831 6144K 0700 spare4
39 376832 475135 48.0M 0700 laf
40 475136 557055 40.0M 0700 boot
41 557056 638975 40.0M 0700 recovery
42 638976 659455 10.0M 0700 drm
43 659456 671743 6144K 0700 sns
44 671744 737279 32.0M 0700 mpt
45 737280 745471 4096K 0700 raw_resources
46 745472 753663 4096K 0700 raw_resourcesbak
47 753664 847871 46.0M 0700 factory
48 847872 851967 2048K 0700 spare5
49 851968 872447 10.0M 0700 fota
50 872448 901119 14.0M 0700 fau
51 901120 9674751 4284M 0700 system
52 9674752 12197887 1232M 0700 cache
53 12197888 122140671 52.4G 0700 userdata
54 122140672 122142686 1007K 0700 grow
RESERVED
Reserved #2
H915 kdz
runningnak3d,
So, there is no way to extract those needed files, the xml files, from a H915 kdz itself on a PC? It has to be on a running H915 kdz V20? I still want this because my V20 is still bricked.
Alan
@alanwid The firehose_8996.mbn is device specific, it is NOT generic unfortunately. I thought I was going to be able to get a copy from a "friend", but no go. As for the XML files, those are not in a KDZ. They MAY be in a TOT file, but even if we had the TOT, and they were in there, we don't have the firehose. But, if we had the firehose, MAKING the XML is easy enough if you have access to a working device.
As for the SDcard method, as I said, starting with the Snapdragon 820, Qualcomm decided to be super D**KS and present the eMMC as multiple physical devices. I say they are super D**KS because there is NO design reason to do this.
In a Snapdragon 808 the eMMC is one device with multiple partitions, so it is very easy to recreate those partitions on an SDcard, and viola, you can debrick.
There are two ways to debrick an 820+ 1: Open it up and short the test pins to put it into 9006 mode. In 9006 mode, when you hook it to a PC, you can see the eMMC, and all the devices that it is presented as, so you can flash them from the PC. or 2: Send it in for repair
runningnak3d said:
@alanwid The firehose_8996.mbn is device specific, it is NOT generic unfortunately. I thought I was going to be able to get a copy from a "friend", but no go. As for the XML files, those are not in a KDZ. They MAY be in a TOT file, but even if we had the TOT, and they were in there, we don't have the firehose. But, if we had the firehose, MAKING the XML is easy enough if you have access to a working device.
As for the SDcard method, as I said, starting with the Snapdragon 820, Qualcomm decided to be super D**KS and present the eMMC as multiple physical devices. I say they are super D**KS because there is NO design reason to do this.
In a Snapdragon 808 the eMMC is one device with multiple partitions, so it is very easy to recreate those partitions on an SDcard, and viola, you can debrick.
There are two ways to debrick an 820+ 1: Open it up and short the test pins to put it into 9006 mode. In 9006 mode, when you hook it to a PC, you can see the eMMC, and all the devices that it is presented as, so you can flash them from the PC. or 2: Send it in for repair
Click to expand...
Click to collapse
Hello there
We are in the same boat. Have you seen this: on Androidforums?
There are very few options it seems, for us.
I hope a newer version of boarddiag or some lg tool is released because this all this fiddling is not good, especially for amateurs We could end up making it worse I suppose. I do have efs backup, but is there other unique partitions..? Idk
I may have found a working firehose elf file for us though. Post here. Don't run that tool, it's not meant for us as I gather, but the the elf file is in the archive.
I have the H918 model myself and I would be interested in partition info, as seen here: xda post.
PS: Do you have any specific info about shorting emmc/ufs pins on our V20 ?
Edit: I looked through you posts, and you returned it to LG...? How did that work, was it warranty free repair? I bough mine from ebay, and I am in Europe. I was thinking about contacting LG on monday.
runningnak3d said:
EDIT: I still need the partition listing, and there is still hope. I have a lead on the firehose_8996.mbn used to fix this very problem with the QFIL tool.
If I can get it, then I will need the partition layout in order to make the rawprogram0.xml file.
I am going to leave the post below because it WAS a good idea, and it does work on SD800, 801 and 808 chips. However ,this is no longer possible on 820 and above Snapdragon chips.
I decided to do some research on WHY there would be sda devices instead of mmcblk. sda is a DISK device, and mmcblk is a FLASH device. eMMC is flash. This is what I found...
From ehem's github:
The problem here is that you can't make an SDcard look like multiple whole disk block devices: sda, sdb, sdc, sdd, etc. or even mmcblk0, mmcblk1, etc. Without being able to do that, there is no way to create an image on an SDcard that the 820 chip will ever boot from.
I am not giving up hope. I know that the qfil files are out there (8996.mbn, recovery.xml and patch0.xml). Even if they are for another device, the XML files can be modified with information we can gain from a working V20.
Original post:
I am starting a new thread because I couldn't change the title of the last one, and there was a lot of "static".
So, I need someone with an H915 to run a couple of commands with the end result being that we will end up with an image that can be "burned" onto an SDcard, and recover from 9008 error bricks.
You will know you have a 9008 if your phone suddenly won't turn on, and nothing lights up when hooked to a PC. Another good indication (if you have Windows) is that it will say something like
qdloader / something / 9008 in device manager when the phone is connected (sorry, I use GNU/Linux, so I have no clue what the exact listing in device manager is).
This procedure will work on ANY Qualcomm Snapdragon based phone that has an SDcard slot, and I have successfully tested it on an LG G4, and an LG V10.
I was in the process of testing it on my V20, but my image was corrupt, and I ended up with a brick -- so now I turn to you.
This is for both the H915 and H910, but the reason I need an H915 is because there is a KDZ for the H915. The H910 and H915 are identical hardware.
So what are the risks to you? None as far as there being a risk to your phone, however, I could unintentionally have you send me sensitive data. For example, there is the EFS partition.
This contains your IMEI ... you don't want that out there. Also, there is the DATA partition. I think that one speaks for itself. However, I would never intentionally ask you to send me something,
but more importantly, if I did get something, it would be nulled. I will always list the risk of any command. For example: "Warning: This could contain the EFS partition!".
You can then decide if that is a risk you want to take.
The easiest thing by far would be for someone to just send me an entire dump of their eMMC, but as stated above, that would definitely contain sensitive info.
However, if there is a trusting soul out there that doesn't want to go through the pain below, please send me a PM
So with that disclaimer in mind, I need to start with the partition layout since I don't currently have a working V20.
There is ZERO risk involved with this. It is just a list of the partitions that are on ALL H915 phones.
First need to get into recovery.
Code:
adb reboot recovery
Once the phone is sitting in TWRP you can get the partition listing. The thing is I am not sure of the device name. It is dependent on the kernel you are using.
It could be either mmcblk0 or sda OR something else.
To find out you can run:
Code:
adb shell
ls /dev/block
You will see a bunch of entries, but we need the "whole disk" block device (you can ignore single entries, loop* and ram*). So, if you see a bunch of mmcblk0pXX then you know it is mmcblk0.
If you see a bunch of sdaXX, then you know it is sda. Once you find out, you will execute (replacing mmcblk0 with the appropriate device if needed):
Code:
fdisk -l /dev/block/mmcblk0
or
Code:
fdisk -l /dev/block/sda
Once that is done, please copy and paste the output into a post here. To give you an idea if you are close, this is what it looks like on an LG V10:
Code:
[dev01:~/h901] $ adb reboot recovery
[dev01:~/h901] $ adb shell
~ # fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Code Name
1 16384 192511 86.0M 0700 modem
2 192512 196607 2048K 0700 spare1
3 196608 197631 512K 0700 pmic
4 197632 199679 1024K 0700 sbl1
5 199680 201727 1024K 0700 tz
6 201728 202751 512K 0700 sdi
7 202752 203775 512K 0700 hyp
8 203776 204799 512K 0700 rpm
9 204800 208895 2048K 0700 aboot
10 208896 210943 1024K 0700 sbl1bak
11 210944 211967 512K 0700 pmicbak
12 211968 212991 512K 0700 hypbak
13 212992 215039 1024K 0700 tzbak
14 215040 216063 512K 0700 rpmbak
15 216064 220159 2048K 0700 abootbak
16 220160 221183 512K 0700 sdibak
17 221184 222207 512K 0700 limits
18 222208 223231 512K 0700 apdp
19 223232 224255 512K 0700 msadp
20 224256 225279 512K 0700 dpo
21 225280 229375 2048K 0700 spare2
22 229376 230399 512K 0700 persistent
23 230400 232447 1024K 0700 devinfo
24 232448 245759 6656K 0700 spare3
25 245760 278527 16.0M 0700 misc
26 278528 344063 32.0M 0700 persist
27 344064 347135 1536K 0700 modemst1
28 347136 350207 1536K 0700 modemst2
29 350208 353279 1536K 0700 fsg
30 353280 354303 512K 0700 fsc
31 354304 355327 512K 0700 ssd
32 355328 356351 512K 0700 keystore
33 356352 360447 2048K 0700 DDR
34 360448 361471 512K 0700 sec
35 361472 362495 512K 0700 encrypt
36 362496 363519 512K 0700 eksst
37 363520 364543 512K 0700 rct
38 364544 376831 6144K 0700 spare4
39 376832 475135 48.0M 0700 laf
40 475136 557055 40.0M 0700 boot
41 557056 638975 40.0M 0700 recovery
42 638976 659455 10.0M 0700 drm
43 659456 671743 6144K 0700 sns
44 671744 737279 32.0M 0700 mpt
45 737280 745471 4096K 0700 raw_resources
46 745472 753663 4096K 0700 raw_resourcesbak
47 753664 847871 46.0M 0700 factory
48 847872 851967 2048K 0700 spare5
49 851968 872447 10.0M 0700 fota
50 872448 901119 14.0M 0700 fau
51 901120 9674751 4284M 0700 system
52 9674752 12197887 1232M 0700 cache
53 12197888 122140671 52.4G 0700 userdata
54 122140672 122142686 1007K 0700 grow
Click to expand...
Click to collapse
Im in this with u on a ls992 g5 msm8996 i have the elf but no mbn i have had several insights on how to make the partion xml but its from linux and i currently havnt a setup. What i do have is a modified lgup that makes a complete partitions dump of phone exactly how it was system and data plus all other .bin
i have dealt with many a hard bricks so hre is one more mind to chuck into the bucket
@runningnak3d
Oh and yes, sorry if it appeared I was calling you an amateur above. That was not the idea, I was talking about myself mainly
Can I ask, did LG re-flash your device or replace the motherboard?
@askermk2000 No worries, I'll be an amateur till the day I die
So I'll try to answer these in order...
I have searched high an low for a board diagram for the v20, and had no luck, which is a real shame since....
Yes, I got my phone back from LG (yep, warranty repair) . They actually replaced the board which makes me think one of three things:
1 - They don't even have the tools to fix these things. As in Qualcomm doesn't release their low level board flashing tools anymore to ANYONE.
2 - It is cheaper for them to tear it apart and replace the board than it is to reflash.
3 - They were just incompetent. I am a little hesitant on this one. I mean in the RMA I flat out stated that I bricked the phone by flashing the aboot partition.
Either way, that doesn't leave me with much hope. I mean if LG can't fix a bricked phone without replacing the board, what hope do we have...
Tis a moot point for me right now because when I got the phone back, OF COURSE it had the latest firmware installed. So, until an exploit is found, there is very little risk of me bricking the phone again.
-- Brian
runningnak3d said:
@askermk2000 No worries, I'll be an amateur till the day I die
So I'll try to answer these in order...
I have searched high an low for a board diagram for the v20, and had no luck, which is a real shame since....
Yes, I got my phone back from LG (yep, warranty repair) . They actually replaced the board which makes me think one of three things:
1 - They don't even have the tools to fix these things. As in Qualcomm doesn't release their low level board flashing tools anymore to ANYONE.
2 - It is cheaper for them to tear it apart and replace the board than it is to reflash.
3 - They were just incompetent. I am a little hesitant on this one. I mean in the RMA I flat out stated that I bricked the phone by flashing the aboot partition.
Either way, that doesn't leave me with much hope. I mean if LG can't fix a bricked phone without replacing the board, what hope do we have...
Tis a moot point for me right now because when I got the phone back, OF COURSE it had the latest firmware installed. So, until an exploit is found, there is very little risk of me bricking the phone again.
-- Brian
Click to expand...
Click to collapse
Wow, you even told them you unlocked and miss-flashed. Do they even read those descriptions, or are they simply, being *reasonable*...
Hehe, I just gotta laugh at hypothesis #2 Doesn't make much sense from a certain point of view.
If I where to guess I'd say that all those certified service centers around the world don't have that type of software/tools. They probably send those motherboards in bulk to a special refurbishing type of workshop.
Maybe because of security, minimize leaking of those tools or something.
Well maybe there is hope for me to RMA mine, but for the fact that I'm not the original buyer... damn shame, but I gotta try at least.
@askermk2000 I was not the original owner either. I would NEVER have bought an AT&T branded phone unless I got a really good deal -- LOL.
If you want to RMA it, and don't have proof of purchase (that is one of the things they want you to attach a photo of if you do it online), then you will need to do what I did, and talk to them (I used online chat so I had a record).
If you want, I will send you the entire conversation so you can see exactly how I handled it.
-- Brian
runningnak3d said:
@askermk2000 I was not the original owner either. I would NEVER have bought an AT&T branded phone unless I got a really good deal -- LOL.
If you want to RMA it, and don't have proof of purchase (that is one of the things they want you to attach a photo of if you do it online), then you will need to do what I did, and talk to them (I used online chat so I had a record).
If you want, I will send you the entire conversation so you can see exactly how I handled it.
-- Brian
Click to expand...
Click to collapse
Plz send it, that could be helpful
sendt a pm
runningnak3d said:
-- Brian
Click to expand...
Click to collapse
Oh, btw, did you somehow convince them that your the original purchaser? Because in that case it may be a bit difficult for me since I live in Europe....
Can someone help me to make the rawprogram0.xml file? I have partition layout for LG G5.
Update:
Somehow, the phone came back, sort of (battery low?!), and I was able to see all partitions again.
So I tried fixing the problem by copying boot.img and laf.img to the respective partitions ... I guess you shouldn't try these things at 1:30 am after already getting yourself in a horrible mess, but here I am. Now the phone is stuck at the LG logo screen, the LED flashes green and blue, and nothing happens. All I can do is to push the power button, and the process repeats.
Naturally, I cannot see any partitions any longer. Now the device seems to be REALLY dead.
Anything I can still try?!
Original problem description
I have tried, after somehow messing things up when following the guide to install LineageOS on the LG G2 (d802, international version with 32 GB), to resurrect my phone using this guide.
However, it failed to solve my problem, and when I tried to boot, the phone still showed only the LG logo, the secure booting error, and then the screen went black, just as before. I guess I should have used dd as well to copy the boot, dbi and laf partitions.
Instead, I figured maybe I should try the TWRP Recovery v2.6.3.2 instead of either TWRP v2.8.7.3 or the LineageOS Recovery image, and that probably has been my (final) mistake. Because, before, the output from gdisk looked liked this:
Code:
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 61071360 sectors, 29.1 GiB
Model: MMC Storage
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 36 entries
Main partition table begins at sector 2 and ends at sector 10
First usable sector is 34, last usable sector is 61071326
Partitions will be aligned on 2-sector boundaries
Total free space is 257992 sectors (126.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 32768 163839 64.0 MiB 0700 modem
2 163840 165887 1024.0 KiB FFFF sbl1
3 165888 166911 512.0 KiB FFFF dbi
4 196608 197631 512.0 KiB FFFF DDR
5 229376 231423 1024.0 KiB FFFF aboot
6 231424 233471 1024.0 KiB FFFF rpm
7 262144 294911 16.0 MiB FFFF boot
8 294912 296959 1024.0 KiB FFFF tz
9 296960 296961 1024 bytes 0700 pad
10 327680 333823 3.0 MiB FFFF modemst1
11 333824 339967 3.0 MiB FFFF modemst2
12 339968 339969 1024 bytes FFFF pad1
13 360448 393215 16.0 MiB FFFF misc
14 393216 458751 32.0 MiB 0700 persist
15 458752 491519 16.0 MiB FFFF recovery
16 491520 497663 3.0 MiB FFFF fsg
17 524288 525311 512.0 KiB FFFF fsc
18 525312 526335 512.0 KiB FFFF ssd
19 526336 526337 1024 bytes FFFF pad2
20 526338 527361 512.0 KiB FFFF encrypt
21 557056 573439 8.0 MiB 0700 drm
22 573440 589823 8.0 MiB 0700 sns
23 589824 655359 32.0 MiB FFFF laf
24 655360 720895 32.0 MiB FFFF fota
25 720896 786431 32.0 MiB 0700 mpt
26 786432 787455 512.0 KiB FFFF dbibak
27 787456 789503 1024.0 KiB FFFF rpmbak
28 789504 791551 1024.0 KiB FFFF tzbak
29 791552 791567 8.0 KiB FFFF rct
30 819200 6488063 2.7 GiB 0700 system
31 6488064 7733247 608.0 MiB 0700 cache
32 7733248 7897087 80.0 MiB 0700 tombstones
33 7897088 7929855 16.0 MiB 0700 spare
34 7929856 8028159 48.0 MiB 0700 cust
35 8028160 60948479 25.2 GiB 0700 userdata
36 60948480 61071326 60.0 MiB 0700 grow
Now, it looks like this, so I am unable to use dd to copy any files to the (now apparently deleted or at least unavailable) partitions of the LG G2:
Code:
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Warning! Main partition table overlaps the first partition by 32 blocks!
You will need to delete this partition or resize it in another utility.
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb: 2014208 sectors, 983.5 MiB
Model: Mighty Drive
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): DEF7EA8F-7D62-49A1-8F27-4F59EF0FDF29
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 2014174
Partitions will be aligned on 2-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 2 2014207 983.5 MiB 0700 Microsoft basic data
I am afraid I have no backup of the partition table other than the output above, because I only learned of this feature of gdisk when looking for solutions of this (last) issue.
Is there any way I can restore the partition table of my device?
Any help in unbricking my phone is, of course, GREATLY appreciated. :fingers-crossed: