Somebody smarter than me figure this out - LG G6 Questions and Answers

After working for a long while trying to get a complete Partition Table together for our G6's, I finally got output from a GPT script, just to be stumped by it.
I am going to attach the output from each GPT partition. the problem is, every output starts at LBA 6. which would mean that there are either multiple drives (possibly virtual) or the output is wrong.
Maybe somebody can figure out what is going on here???

@runningnak3d

well, i think i figured out why there are more than one.
If you take a look at the files you extract from the kdz, you will see some numbers following each partition. Those numbers are not random, they are chosen to show the first lba of that partition.
The issue you see, is that multiple partitions have the same exact starting lba.
How can this be? There can't be multiple partitions in the same location... I believe LG is splitting the emmc into multiple Dynamic drives, then partitioning them with each PrimaryGPT.
I'm at a loss here...

I have an idea of what to do. But, for now, gotta sleep...

Related

messed up partitions on internal storage

After researching and trying to figure out more info my semi brick sgs4g... I'ts looking like I screwed up the partitions on the internal storage. For one I can get into cwm but not too many things work.. and usually I get "E:can't mount data" .. or "can't mount cache" type errors. And in Odin most tars/md5's get about 90 percent and fail.. usually on Cache. So I found a posting on repairing those partitions.. just wanted to post this just in case some smarty out there knows I'm way off and wasting my time.. I'd really appreciate any info. thanks
Hi,
This is a notorious error that can occur after lagfix conversions and other file system partitioning tools. However, I can actually fix this error and have many times now on i9000 and the original Vibrant using a full JTAG dump write from a known good backup I obtained from good working phones. Please contact me if you are interested in this and I can get you more details. In nearly all cases this is not fixable by standard ODIN flashing and repartitioning with a PIT file. I was happy to find it is however fixable by re-writing each addressable block of the NAND chip with a good backup. This dis-proves many theories of "dead internal SD-card failure" which have been thrown around for almost a year now on the i9000 as well.

memory problem

I have my nook rooted through my memory card. When I check how much internal storage I have on it through the nook it shows only 900 mb. It shows the same when I have it hooked to my computer. I know its supposed to have 5 gigs. I havent downloaded anything so I dont know where all the 4 + gigs went. Can anyone help? Thanks.
Can anyone please help?
thegameksk said:
Can anyone please help?
Click to expand...
Click to collapse
Barnes & Noble repartitioned the newest Nook Colors. If you had done even a hint of research before starting yet another thread you would know that.....which is why no one answered you last night when you asked this question....C'mon man this isn't customer service, do a search before you post.
How bout I did research and everything that i've seen has said that 5 gigs should show not 900 mb. The nook has 8 gigs. 3 are used for the os/repair and 5 for downloading things.
Nope, you are wrong.
New models made in May or refurb units as of May are partitioned for 1 GB of space.
http://forum.xda-developers.com/showpost.php?p=13772065&postcount=4
http://forum.xda-developers.com/showthread.php?t=1083506
http://forum.xda-developers.com/showthread.php?t=1080445
http://forum.xda-developers.com/showthread.php?t=1077321
Thats bs. When I bought it I was told there were 5 gigs for storage of files from my computer. Lokks like im sending this back. Thanks. Sorry bout the tude before.
No worries...I didn't mean to jump on you either. Just gets frustrating seeing new posts with the same old questions. Makes it tough to stay on top of the most current stuff and gets a little frustrating.
YeA i had searched but everything that came back said 5 gigs. Based on my reading of the threads that were posted theres no way to reparation the nook?
thegameksk said:
YeA i had searched but everything that came back said 5 gigs. Based on my reading of the threads that were posted theres no way to reparation the nook?
Click to expand...
Click to collapse
It's being worked on by many, but as of yet has not been solved. Conventional methods have come up empty. I'm quite sure we're getting closer to a solution though.
I was doing some research and came across this:
Here's how to convert a new NC (or one where you don't care about anything in /data and /media that won't be automatically restored by B&N) with only a 1GB /media space, back to one with with 5GB media space:
Boot a rooted Android system in the external SD card slot:
Access the rooted OS command line prompt, using either ConnectBot or ADB.
Fire up "busybox fdisk /dev/block/mmcblk0"
Delete partition #8 (the /media partition).
Note the size of partition #7 (the cache partition), and delete it as well.
Delete partition #6 (the /data partition).
Recreate partition #6 (the /data partition), to the size you want (say 1GB).
Recreate partition #7 (the /cache partition), to the size noted in step #5.
Recreate partition #8 (the /media partition), to occupy the remainder of the space.
Remove the SDcard and reboot.
When the NC boots its native system, it will recreate (just like a factory reset), the contents of the resized partitions. Yes, you will have to reregister. Of course, the same process, but with a different number in step #7, can give you more app space.
This is easily scriptable as well, and I fully expect such scripts.
Do you think this could work? I dont know enough about modding to try it. lol

HELP partitioning dev/block/mmcblk0

SO I half bricked my nook by deleting off partitions from the emmc, and now it only boots from SD card... without the SD card it won't turn on at all
I know my issue is partitioning the mmcblk0 as it used to be but I can't access it from adb shell, it does not find the parted command or gives me no permission
I have tried bootable CLW and have tried to reflash stock firmware but nothing does the trick
any one have any tips? or have run into this problem?
If you don't have parted, use fdisk. Take a look at the manual repartitioning post: http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110. Basically you'll want to do something similar, except you'll create all the partitions instead of just p6,p7,p8.
jll544 said:
If you don't have parted, use fdisk. Take a look at the manual repartitioning post: http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110. Basically you'll want to do something similar, except you'll create all the partitions instead of just p6,p7,p8.
Click to expand...
Click to collapse
thanks for the link, I been very busy this week with final projects and final exams approaching so this thing isn't my number one priority but nevertheless I would love to fix it asap...
I manage to recreate all the partitions, however the number of cylinders, heads, and sectors is different then it should be in my disk, when I use fdisk expert mode to change these things and do the w to write changes to disk the changes are not there once I do the p command, as if I never wrote the changes to disk... and still my nook will not boot off emmc.
Anny suggestions?

Super Unique problem (I deleted all partitions)

I kinda super screwed this NC I am working on. I literally deleted all partitions on blk0 (I know... don't ask how). I have rebuilt them all based off of:
http://forum.xda-developers.com/showthread.php?t=920347 (not including 9,10; just merged them into 8)
and dd'd boot and system images. Still will not boot. I know they contain device specific data but could anyone PLEASE post dd images of op2 and op3? I think that is all else I need.
I have tried every recover fix zip I have found on these forums. If anyone can think of anything else I can try please let me know. Thanks
talitore
You can reconstruct the partitions, but if you messed with the underlying geometry of the eMMC it will need to be reformatted. See this link for how to do it for SD. The same idea applies to eMMC. If you previously backed up your eMMC image, you can dd it over the entire mmc and should recover your geometry in the process.
Good luck. FWIW you are very unlikely to have done any permanent damage. You should be able to get a system back up and running.
Be sure partition one is FAT and the emmc is formatted correctly if you want u-boot/kernel to load...
GL
talitore said:
I kinda super screwed this NC I am working on. I literally deleted all partitions on blk0 (I know... don't ask how). I have rebuilt them all based off of:
http://forum.xda-developers.com/showthread.php?t=920347 (not including 9,10; just merged them into 8)
and dd'd boot and system images. Still will not boot. I know they contain device specific data but could anyone PLEASE post dd images of op2 and op3? I think that is all else I need.
I have tried every recover fix zip I have found on these forums. If anyone can think of anything else I can try please let me know. Thanks
talitore
Click to expand...
Click to collapse
My understanding is that if you collapsed the partitions that this is nearly impossible to recover in a functional state. You might get data retreival but to get it to be non buggy and working will be difficulties suggest that you back up or restore as much information ad possible and reformat/repartition.
fattire said:
You can reconstruct the partitions, but if you messed with the underlying geometry of the eMMC it will need to be reformatted. See this link for how to do it for SD. The same idea applies to eMMC. If you previously backed up your eMMC image, you can dd it over the entire mmc and should recover your geometry in the process.
Good luck. FWIW you are very unlikely to have done any permanent damage. You should be able to get a system back up and running.
Be sure partition one is FAT and the emmc is formatted correctly if you want u-boot/kernel to load...
GL
Click to expand...
Click to collapse
I've gotten all the partitions rebuilt and formatted. It's just that the 0p2 and 0p3 partitions are empty and I need the DD image to fill them again. For now I am going to try an undelete on the partitions to see if I can recover them until someone dumps the dd images or has another idea.
Thanks for the suggestions.

i need a bit of help in partitioning.

sorry if in the wrong section but i need a bit of help in partitioning a hard drive.
see attachment
i have shrunk a partition and i want to put it back but has somehow been separated from it's host (C: drive) and the efi drive is now in the way so now i cant merge the D: partition back to the C: partition because there no longer neighbors. how can i move the EFI partition over or the D: partition so that i can merge them back together?
xdarkmario said:
sorry if in the wrong section but i need a bit of help in partitioning a hard drive.
see attachment
i have shrunk a partition and i want to put it back but has somehow been separated from it's host (C: drive) and the efi drive is now in the way so now i cant merge the D: partition back to the C: partition because there no longer neighbors. how can i move the EFI partition over or the D: partition so that i can merge them back together?
Click to expand...
Click to collapse
I do not believe you can merge partitions while the system is running. If i remember correctly, you have to reformat the entire hard drive in order to do that. Taking away from one partition is an operation which usually has no way of undoing without losing data.
You need a couple of utils.
MiniTool Partition Wizard (freeware) http://partitionwizard.com
Acronis True Image 2014 (trialware) http://acronis.com/homecomputing/trueimage
Make a bootable USB from each of the provided tools. The TrueImage boot USB will work w/o limitation (trialware only affects the Windows app). You only need the boot images; once that's done, you can uninstall the tools.
Am assuming that D: is empty. Boot to USB and use TrueImg to back up the ESP (EFI system partition). If C: has user data, back it up as well (onto a separate storage device). Use PartWiz to nuke the D: and ESP partitions, recreate a 200MB partition at the end of the drive, and expand C: to fill the rest. Use TrueImg to restore the ESP to the 200MB partition.
This kind of thing can also be done from any Linux liveCD worth mentioning; they all include parted and usually a graphical front-end to it (either gparted or qtparted, sometimes something else too). Parted is capable of moving partitions and of resizing them.

Categories

Resources