Database Users

LG G2 after OTA nothing works. Help!

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

Partition problems, no ERI, Unknown IMEI, no USB

I was attempting to troubleshoot another phone I had and it was suggested somewhere on here that I back up my efs partition and gave directions to use the command "reboot nvbackup". Well the result was not good. I've searched the forums for over a week and have decided to finally post as I'm out of ideas.
I followed radionerd's thread here and was able to get the Baseband back but I still do not have anything in "Hardware Version", and show "0" in PRL version, "None" in ERI version, "Unknown" in IMEI. The kicker is that somehow my USB no longer works when connecting to the PC. The cord works fine with other phones and it charges this phone but gives a "USB device is not recognized" error when connecting, under device manager it shows up as "Device Descriptor Request Failed".
I have been able to flash back to a stock ROM using TWRP (RUEOF1 is what I've been flashing) but that hasn't helped at all. I've attempted to copy mmcblk1 from the sd but it always fails, both from TWRP file manager and from the ES File Explorer. I'm guessing if I was able to flash a new PIT file I'd be good but I have no idea how to do that without having USB support. I do have working WIFI and SD card access, along with a good operating system.
I've tried a lot of stuff over the past week so I apologize if I haven't already mentioned it but I'm looking for help to see if anyone has an idea about what can be done.
Thanks!

If you unlocked your bootloader using the "standard method" then the "debrick" image you created on the SD card has a backup of literally every partition EXCEPT the ones that you would normally flash with Odin (or a ROM, e.g. boot, system, userdata, cache etc).
The reason that that unlocking method created a debrick image is so that people could save it so they would have it for emergencies. Such as the one you created.
Even the PIT data is included in a hidden partition inside the debrick image. But having a PIT file only allows you to re-partition flash memory, which you don't need; it's partitioned already. Re-writing the PIT is not going to magically recreate data inside those partitions that you erased.
Here's the bottom line: factory images, just like ROM files have NEVER had 100% of the partitions needed to restore the phone back to working condition. So there's darn good reasons to have backups or avoid wiping all of memory.
I think that @hsbadr had posted some debrick images taken during older ROM releases (N* series, I think) on his AFH (androidfilehost.com) site. Whether or not substituting some subset of those partitions (e.g. efs, persist, etc) onto your device will work correctly or not, but it's certainly worth a try at this point.
Skills you need to learn: figuring out byte offsets from the GPT partition table at the beginning of the debrick file to get the partition offsets in the "debrick" blob, and "dd" command options for grabbing exactly the byte ranges you want out of a single large blob file containing many partitions. (e.g. "skip=", "bs=", "count=").
Note also that the Unix GPT partitioning tools "gdisk" will let you examine the Primary GPT (UEFI?) partition table in the debrick image even though the secondary GPT is not present. That way, you can figure out the exact length and initial offset of partitions that you want to copy out of the debrick image into your device. (The reason for the missing secondary GPT is that the GPT/UEFI partition table indicates the presence of very large partitions such as /system, /cache, and /userdata, and the secondary GPT is always near the very end of the disk. Because the "debrick" image is literally a byte-for-byte copy of only the first 256 MB of the mmcblk0 flash device, there is no secondary GPT some 32GB "later" then the beginning of the debrick image.
red indicates partitions in debrick not appearing in Odin factory Images
Code:
$ gdisk /tmp/mj7-debrick-unlocked.img
Command (? for help): p
Disk /tmp/mj7-debrick-unlocked.img: 524288 sectors, 256.0 MiB
Logical sector size: 512 bytes
Disk identifier (GUID): NNNNNNNN-NNNN-NNNN-NNNN-NNNNNNNNNNNN
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071326
Partitions will be aligned on 2-sector boundaries
Total free space is 8158 sectors (4.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 8192 38911 15.0 MiB 8300 apnhlos
2 38912 156543 57.4 MiB 0700 modem
3 156544 157567 512.0 KiB FFFF sbl1
4 157568 157631 32.0 KiB FFFF dbi
5 157632 157695 32.0 KiB FFFF ddr
6 157696 161791 2.0 MiB FFFF aboot
7 161792 162815 512.0 KiB FFFF rpm
8 162816 163839 512.0 KiB FFFF tz
[color=red] 9 163840 184319 10.0 MiB FFFF pad
10 184320 204799 10.0 MiB 8300 param
11 204800 233471 14.0 MiB 8300 efs
12 233472 239615 3.0 MiB FFFF modemst1
13 239616 245759 3.0 MiB FFFF modemst2[/color]
14 245760 268287 11.0 MiB FFFF boot
15 268288 294911 13.0 MiB FFFF recovery
[color=red] 16 294912 321535 13.0 MiB FFFF fota
17 321536 335853 7.0 MiB 8300 backup
18 335854 341997 3.0 MiB FFFF fsg
19 341998 341999 1024 bytes FFFF fsc
20 342000 342015 8.0 KiB FFFF ssd
21 342016 358399 8.0 MiB 8300 persist
22 358400 376831 9.0 MiB 8300 persdata [/color]
--------- debrick image ends ~72 MB into the start of the system partition --------
23 376832 5931007 2.6 GiB 8300 system
24 5931008 8028159 1024.0 MiB 8300 cache
25 8028160 61071326 25.3 GiB 8300 userdata
I would start by restoring as few partitions are necessary e.g. "efs" and "persist" before I would bother with the others.
Example using data given above. (You should check your own work.)
efs partition: blocks 204800 to 233471 in debrick image, blocks are 512 bytes.
check length:
(233471-204800+1)*512 = 14680064
14680064 / (1024 * 1024) = 14 O.K.
so:
# dd if=/sdcard/debrick.img bs=512 skip=204800 count=28672 of=/dev/block/platform/msm_sdcc.1/by-name/efs
(or get clever and faster)
# dd if=/sdcard/debrick.img bs=1048576 skip=100 count=14 of=/dev/block/platform/msm_sdcc.1/by-name/efs
You should be pretty sure what you are doing with byte offset calculations with the "dd" command. Fortunately you are relying on the partitioning already present on the output side of things, so the worst that you could do is write misaligned garbage to a partition. So long as you don't do something incredibly stupid like overwrite a bootloader partition you should be OK.
cheers

Thanks for the reply, I forgot to subscribe so I just saw the post.
I have been able to copy all of the partitions from another phone but it hasn't helped. I'm now wondering if I'm missing a hidden partition.

LG G2 bricked, partition table corrupt

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:

Resizing /system and /userdata in Note 3 SM-N9005

Hello to all.
I am trying to resize the partition /system using the parted and gdisk commands. But none of these commands succeed in changing mmcblk0 partitions after execution.
The things I do are as follows:
- install adb and fastboot and put them to the system variables.
- enable Settings>developer options>USB debugging and Root debugging
- install TWRP recovery.
- run cmd in adminitsrator permission.
- write these command in CMD :
adb root
adb reboot recovery
adb push gdisk /sbin
adb push parted /sbin
adb shell chmod 777 /sbin/gdisk
adb shell chmod 777 /sbin/parted
adb shell
~#> cd /dev/block
dev/block> gdisk mmcblk0
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
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 61071326
Partitions will be aligned on 2-sector boundaries
Total free space is 8158 sectors (4.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 8192 38911 15.0 MiB 8300 apnhlos
2 38912 156543 57.4 MiB 0700 modem
3 156544 157567 512.0 KiB FFFF sbl1
4 157568 157631 32.0 KiB FFFF dbi
5 157632 157695 32.0 KiB FFFF ddr
6 157696 161791 2.0 MiB FFFF aboot
7 161792 162815 512.0 KiB FFFF rpm
8 162816 163839 512.0 KiB FFFF tz
9 163840 184319 10.0 MiB FFFF pad
10 184320 204799 10.0 MiB 8300 param
11 204800 233471 14.0 MiB 8300 efs
12 233472 239615 3.0 MiB FFFF modemst1
13 239616 245759 3.0 MiB FFFF modemst2
14 245760 268287 11.0 MiB FFFF boot
15 268288 294911 13.0 MiB FFFF recovery
16 294912 321535 13.0 MiB FFFF fota
17 321536 335853 7.0 MiB 8300 backup
18 335854 341997 3.0 MiB FFFF fsg
19 341998 341999 1024 bytes FFFF fsc
20 342000 342015 8.0 KiB FFFF ssd
21 342016 358399 8.0 MiB 8300 persist
22 358400 376831 9.0 MiB 8300 persdata
23 376832 5095423 2.3 GiB 8300 system
24 5095424 5709823 300.0 MiB 8300 cache
25 5709824 5730303 10.0 MiB 8300 hidden
26 5730304 61071326 26.4 GiB 8300 userdata
Command (? for help): d
Partition number (1-26): 26
Command (? for help):w
(curser blinking) and device goes to hang!!!!!
anyone can help me? I do this in parted command. It is like above.
after restarting the device, all of the partition are there, like before...

I also used PIT file with different partition sizes, but nothing change. Odin shown : RQT_CLOSE!!

B2017G - new Motherboard

Hello community,
I bought once an Axon 7 mini, installed TWRP and LineageOS (android 9). It was with Stock Rom 6.01, single SIM. As far I remember I had troubles, crashed several times a day. Then I flashed a dual SIM Version of the stock Rom, Android version was I think was 7.1 much better (update via stock recovery). Then I was able to install TWRP, install Lineage, root it.
Now that b2017g died, couldn't see any net.
I bought the same with a defective USB port cheaply, took out the motherboard, build it in in my old - works perfectly with Android version 6.01.
But I can't find a stock rom to upgrade to 7.1 that I need to install TWRP, all downloads have been deleted.
Now I have a backup from all partitions - what to I have to flash to the new MB? Boot, recovery, System?
The Partitions I have from the old b2017g (working beside of a hardware defect on the MB):
Disk /dev/block/mmcblk0: 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 1330412 sectors (649.6 MiB)
Number Start (sector) End (sector) Size Code Name
1 131072 303103 84.0 MiB 0700 modem
2 393216 393217 1024 bytes FFFF fsc
3 393218 393233 8.0 KiB FFFF ssd
4 393234 394257 512.0 KiB FFFF sbl1
5 394258 395281 512.0 KiB FFFF rpm
6 395282 399377 2.0 MiB FFFF tz
7 399378 400401 512.0 KiB FFFF hyp
8 400402 433169 16.0 MiB 0700 dsp
9 524288 527359 1.5 MiB FFFF fsg
10 655360 658431 1.5 MiB FFFF modemst1
11 658432 661503 1.5 MiB FFFF modemst2
12 786432 786495 32.0 KiB FFFF DDR
13 786496 786527 16.0 KiB FFFF sec
14 917504 958463 20.0 MiB FFFF splash
15 1048576 1050623 1024.0 KiB FFFF aboot
16 1050624 1181695 64.0 MiB FFFF boot
17 1181696 1312767 64.0 MiB FFFF recovery
18 1312768 1314815 1024.0 KiB FFFF devinfo
19 1314816 9703423 4.0 GiB FFFF system
20 9830400 10444799 300.0 MiB FFFF cache
21 10444800 10510335 32.0 MiB FFFF persist
22 10510336 10512383 1024.0 KiB FFFF misc
23 10512384 10513407 512.0 KiB FFFF keystore
24 10513408 10513471 32.0 KiB FFFF config
25 10513472 10644543 64.0 MiB FFFF oem
26 10747904 10747967 32.0 KiB FFFF limits
27 10878976 10879999 512.0 KiB FFFF mota
28 10880000 10880511 256.0 KiB FFFF devcfg
29 10880512 10882559 1024.0 KiB FFFF dip
30 10882560 10948095 32.0 MiB FFFF mdtp
31 10948096 10949119 512.0 KiB FFFF syscfg
32 10949120 10957311 4.0 MiB FFFF mcfg
33 11010048 11010559 256.0 KiB FFFF cmnlib
34 11010560 11011071 256.0 KiB FFFF keymaster
35 11141120 11141631 256.0 KiB FFFF apdp
36 11141632 11142143 256.0 KiB FFFF msadp
37 11142144 11142159 8.0 KiB FFFF dpo
38 11142160 11404303 128.0 MiB FFFF logs
39 11404304 61071326 23.7 GiB FFFF userdata
Without having a stock rom, what should I flash to the new MB? Recovery, boot, system?
Have you any valid link to an update from Android V6.01 to 7.1 or 7.11 just using stock ROM?
I use Linux Mint and own no Windows (except maybe WinXP).
regards, any help is welcome...