yashsingh1/xdaforums huggingface dataset:
[P3300, MDA Compact III ROM Development] Leigh:
Does anyone kow if this is floating about anywhere, plus are the imate ultimates out? Or does anyone have ther hands on one to extract the sideshow application on them which is sopost to have the likes of a media center remote ideshow gadget which would be very handy, thanks
[P3300, MDA Compact III ROM Development] Leigh:
so no answers orany other questions?
[P3300, MDA Compact III ROM Development] lyger:
http://xdaforums.com/showthread.php?t=397751
[G Pad 10.1 General] fatbas202:
If anyone wants to use my work to create a flashable zip to make it easier for novices, please do so. My problem is solved and I don't have the time to create the zip. Please post any questions and I'll gladly answer them! I'm so stoked that we have a usable downgrade method now!
[G Pad 10.1 General] grandamle91:
Thank You, Worked Great
[G Pad 10.1 General] dopekid313:
Thanks for making this I was gonna do it but was to lazy lol and thanks for linking my thread and giving cred instead of just linking straight to the kdz thank you
[G Pad 10.1 General] fatbas202:
Glad to be of help!

Of course! If you hadn't obtained the firmware then we'd all still be looking for a solution. It pisses me off to no end when people try to take credit for other people's work. We all just need to realize and acknowledge that we are simply standing on the shoulders of those who did the work necessary for each of us to do our work.
[G Pad 10.1 General] grandamle91:
I just noticed since we formatted the userdata it screws up TWRP. It won't mount Data and it says the settings are corrupted
[G Pad 10.1 General] fatbas202:
Is this after you've rebooted into Candy5 and the partition is reformatted as ext4 (or you've done so manually)? TWRP may not be able to mount an ext2 partition.

EDIT: I just tested this. Following my instructions and flashing to Candy5, TWRP sees mmcblk0p33 (userdata) as the full size and mounts it at /emmc.

For clarification, after you run the parted commands, it will mess with the partition table and TWRP will most likely not be able to see it to remount it - at least not until after a reboot. This is why you need an external SD card from which to install ROMs.
[G Pad 10.1 General] xudox:
/data not mounted

Edit: nevermind. The partition 33 was still ext2. I had to run make_ext4fs /dev/block/mmcblk0p33 and now I am able to mount /data. Thanks.

Thanks for taking the time to help us.

I followed the steps and till 33 I am good. But once I am in Candy5, I am not able to adb shell (adb not recognizing device eventhough usb debugging is on). I rebooted to recovery and adb works there. But my /data partition is not enabled in TWRP. I am not able to check it either under Mount in TWRP.

mount | grep userdata

is empty

df

does not show data
[G Pad 10.1 General] gridironbear:
I tried this and my tablet bootlooped. I was able to get into fastboot and restore. I would GREATLY appreciate it if someone who has the time, would kindly donate their valuable time to into making an exe zip or something.
[G Pad 10.1 General] fatbas202:
At what point did it bootloop? What was the last step that you took before rebooting?
[G Pad 10.1 General] drumm3rb0y:
Zip

I would really appreciate a zip file as I have never been savvy with adb and for whatever reason it doesn't want to work on Windows 10.
[G Pad 10.1 General] fatbas202:
A zip file for what part? The only part that requires ADB directly is to fix the internal storage. You absolutely have to flash the KDZ and then root before you can do anything. If you are on 5.x then you have no possible way to root, much less flash a zip file.

If you tell me what exactly you are having issues with I will try to help.
[G Pad 10.1 General] drumm3rb0y:
The adb part is the part im having issue with. Everything else is flashed already. I was wondering if you could make a zip for the adb part so I can just flash it through twrp.
[G Pad 10.1 General] shahidmianoor:
thanks for the great help. it did work perfectly to regain the lost space.

what about white lines ? is there any solution for that problem ?

I have tried flashing back stock recovery extracted from kdz, dd' but didn't help.

Now i am thinking of flashing back the aboot.bin extracted from original kdz or i can dump ".img" from another working device. (i have 4 similar devices)

what is your opinion i m not a developer and i need your advise. should i go ahead and which partition should i dd ? aboot or abootb or boot ?

regards
[G Pad 10.1 General] fatbas202:
I have no solid evidence of this, but I suspect that the white lines are caused by a display driver issue where when the bootloader hands over control of the display to the kernel it doesn't get reinitialized properly. I have no ideas as to how to get rid of that at the moment but if I stumble across something I'll be sure to post here.

While I'm not an Android developer, I've been a Linux admin for 10+ years and have a lot of experience with Android devices. I'd be really hesitant to go flashing things ad hoc. While Download Mode may save you if you flash the wrong thing, I'm not entirely sure what the limitations that you may run in to with a locked bootloader are.

After having this device for months on 5.x and FINALLY being able to downgrade and run custom ROMs with root, not seeing a boot animation is a pittance to pay. But I'll keep looking.
[G Pad 10.1 General] zmali1:
i have same problem entered in TWRP but when ADB sheel thorough DP tools it didn't connect to my device. i m also using windows 10
[G Pad 10.1 General] iphone5sf:
Do I need to Re-mount Data ? I press format data button at TWRP and mount data. It looks work great.

After all process, it shows 16Gb total at storage, 11.04GB available. it works perfectly.

I need the stock V41010d, so I reflash the stock rom rooted at [ROM][STOCK](V410 ONLY)KOT49I.V4101d | 4.4.2 | Rooted + Busybox

Now, my Gpad is at stock V41010d, but I have a question about the boot screen, is it still with white lines and white screen? Any method to fix it?
[G Pad 10.1 General] nmnm4alll:
Hello,

Thanks for the great work. unfortunately I am facing some difficulty, starting from step# 16 "Things get tricky here", how to run"adb shell in TWRP?

also can I use minimal_adb_fastboot_v1.1.3_setup.exe as mentioned in the link in the OP http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ ?

also I noticed the path have been used includes 'parted' folder, but the folder I have after unzipping the parted zip called 'sdparted-recovery-all-files', do I rename the folder to 'parted' instead?

please help and excuse my broken English.
[G Pad 10.1 General] summonholmes:
I'm also having trouble with the adb shell step. When my device is powered on normally, adb commands work. However, in TWRP mode my computer can't recognize the tablet, mount properly, and copy over parted. All the steps have been identical to this point. Any ideas?
[G Pad 10.1 General] fatbas202:
You shouldn't need to remount or format data. The parted command nukes the filesystem and creates a new one formatted as ext2. At this point the running kernel has the old partition table loaded and won't know that the partition has been extended. Simply flash Candy5 and reboot at this point and it will reformat the userdata partition.

See above for the white lines during the boot animation. Known issue, no fix in sight, doesn't really matter.

You only need the sdparted-recover-all-files.zip from that site. "parted" is not a folder, but the binary (without a file extension) inside of that zip file. Copy that file to /sbin and you are in business.

I'd recommend installing the SDK and pulling the drivers from that. Alternatively, you can try the drivers here: https://github.com/koush/UniversalAdbDriver.

Technically, when I ran the "parted" commands I was actually booted in to rooted 4.4.2 from the KDZ; I wasn't actually in TWRP. It's just not a very recommended way of going about it. I explained how to run all of this from TWRP, but there's no technical reason that you *can't* run this from Android. You just *shouldn't* because you can't cleanly unmount the filesystem and it theoretically could cause filesystem corruption. I just figured that I don't care about that partition getting corrupted since it's getting wiped out.
[G Pad 10.1 General] fatbas202:
Bizarre. Ok, at this point I'm going to recommend that you flash the KDZ again. It will repartition your internal storage and we can go from there. I cannot think of any reason that parted shouldn't be able to find your internal mmc.
[G Pad 10.1 General] Kennypete:
It took a few tries (It was a learning process for me, as I have next to no experience flashing) but I finally got it to work. THANK YOU very much. You rescued my tablet.
[G Pad 10.1 General] fatbas202:
Excellent! Thank you for posting your results here.
[G Pad 10.1 General] jeffary:
Brightness adjustment does not work for me. Screen is about medium brightness, I can't make it dimmer or brighter, slider makes no difference. Live display if off.

Does anyone else have this issue?
[G Pad 10.1 General] swaqas:
I'll try to reflash kdz on the weekend. As i said CM13 works flawlessly and gets things done for me. So, Im not super worried about that issue. Its just annoying that I cant do certain things. I will update you once flashed

Thanks for being so awesome.
[G Pad 10.1 General] fatbas202:
Which ROM, dude?
[G Pad 10.1 General] jeffary:
Sorry forgot to say which ROM.

I'm on the Candy 5 ROM, but I had the same issue on CM 12.1 and 13.

EDIT: I was able to fix my issue by installing a brightness control app from the play store. Now the stock brightness slider works. For some reason I was stuck at 50% the entire time, the app must have re-enabled the toggle or something. Weird. :confused::good:
[G Pad 10.1 General] fatbas202:
Glad you got it figured out. I didn't see an issue on mine last night (Candy 5) and I've been racking my brain trying to figure out what advice to give you. This is very bizarre. Thanks for sharing your tip though.
[G Pad 10.1 General] mnsiw:
Thank you very much fatbas202 and other contributors for this wonderful post.

I was on stock 5.0.2, LG Flashing Tool shown some server error while flashing 4.4.2 test ROM but it flashed, after flashing my internal storage was 8GB, tried to root with PurpleDark Lite but failed, finally used LG OneClick Root 1.3, and followed other steps, now on Candy with everything fixed and working :)
[G Pad 10.1 General] fatbas202:
Hell yeah! Glad it worked for you.
[G Pad 10.1 General] swaqas:
I was about flash kdz again and wondering after what step should I remount Data? You know how it says to uncheck data at 17th step. Thanks,

Sorry for my ignorance :(
[G Pad 10.1 General] nolimitzz:
thanks for the efforts on this tutorial. worked for me, however, two notes:

- after re-partitioning to get 16gb back, i had to manually format because otherwise flashing Candy wont do it.

- lg flash tool will say error connecting to server or something but will continue flash, happy i didnt brick my device as i disconnected it and it it only stayed in lg firmware download mode.

now to the question,

anyone is able to use IR blaster on Candy 5? any solution for this?

thanks
[G Pad 10.1 General] fatbas202:
No worries!

So you unmount userdata (Data) so that you can cleanly change the partition size and reformat it. However, when you create the partition in step 25, it creates it as ext2 (due to a limitation with the tools that I found to do the more important parts). It needs to be ext4, so you need to reformat it manually or flash Candy5 and let it do it for you.

So to answer your question, after step 29. You can remount data in TWRP after you've successfully reformatted the userdata partition to ext4.

Hope that helps.
[G Pad 10.1 General] fatbas202:
Thanks for posting your results. It's kind of bizarre that Candy did not format the partition for you, but at least there's a good workaround.

As far as the IR blaster goes, I do not know if that will work on a non-LG ROM. I've not seen reports of anyone getting it to work, but I haven't specifically been looking. If you do find something, please PM me and I'll post it in the OP.

Thanks
[G Pad 10.1 General] faheyd:
Well, the first time I did this tut, I thought I'd take a short cut or two. That was NOT the right way. Second time around, I followed the tut exactly, and everything worked out. I have the correct userdata size and no white lines after doing the aboot thing. What an adventure, I don't know how you guys figure all this stuff out, but my hats off to you. It would be nice if the other developers would learn how to do the partitioning thing for older devices. We know they have the memory onboard, just need to delete/resize a few partitions. THANK YOU !
[G Pad 10.1 General] fatbas202:
Thanks for posting your success and failure. Sorry it didn't work out the first time, but I'm really glad that you have everything working.

For what it's worth, this exact method (well, 16-28) can be used on any rooted device to modify partition sizes and whatnot. It's just not necessarily safe to do unless you know exactly what you are doing.

As far as figuring it out... story time:

Basically dopekid313 posted a KDZ that he got for our device through some unknown (to me, anyway) channel. I flashed it and it seemed to work. But the GUI said that I had 8GB of storage, not the 16 I expected to see. So I created an 8GB file and it wouldn't write after 4GB. So I looked at the partition table to discover that it was really only 4GB and the GUI was lying. Fukme. But it IS a test build that successfully downgraded the bootloader (I knew this because 4.x won't boot from a 5.x bootloader) and this definitely booted. So how the hell can I resize that partition? Did some web searches to find a copy of the parted binary that was compiled for this CPU architecture and tried to resize the userdata partition. It worked! Then I spent a few hours flashing and reflashing the test KDZ to make sure this was a repeatable process and documented the steps necessary to do so.

It also doesn't hurt that I've been a Linux admin for nearly a decade, so I'm pretty familiar with how most of this stuff works.

Lastly, marcsoup figured out that flashing all of navin56's stock partition dump images fixed the white line issue. All that I did was flash them one at a time until I figured out the minimum amount of stuff that needed to be flashed.

I know it seems kind of complicated, but it's largely mixing knowledge, courage, and testing. Lots of things don't work but you never read about them. But most importantly, this is absolutely a group effort. None of us could create anything on our own as awesome as all of us together can create.

Anyhow, sorry to ramble on; just wanted to post some insight.

I hope you are all having a great weekend!
[G Pad 10.1 General] instructor2:
Hello [MENTION=1772416]fatbas202[/MENTION], luckily i have a twrp backup of candy5 with all the processes completed described in op. All the user will have to do is install twrp and restore twrp backup. If you like, i can upload it to some host and provide you link so you can add it in op.
[G Pad 10.1 General] fatbas202:
Thank you! Unfortunately I don't think that it will actually complete the task that we require of it. TWRP basically takes a tar (like a zip) backup of all of the files on each of the selected partitions. I think there may be a way to tell it to do a sector-based backup (like dd would create) and dump the raw data to an img file. However, both of those solutions are inadequate.

Let's say that, for argument's sake, you have a full disk image of your device - all 33 partitions ready to go. Then you copy that image file over and dump it on to another system that has the 4GB userdata partition. It would successfully write all of the data, however the partition table would remain unchanged so you'd only be able to see the first 4GB of the 33rd partition.

The long and short of it is that TWRP doesn't modify partition tables (by design) so it won't solve our 4GB problem for us.

Thank you instructor2 for your work in capturing that image and willingness to help out. I sincerely appreciate it. It's just unfortunate that it won't help very much. Sorry dude.
[G Pad 10.1 General] instructor2:
this is what i was thinking lately.. thanks
[G Pad 10.1 General] faheyd:
When I adb shell into the tablet, and install a 'parted' app into /sbin/, I get this:

/sbin # df -m

df -m

Filesystem 1M-blocks Used Available Use% Mounted on

tmpfs 484 0 484 0% /dev

tmpfs 484 0 484 0% /tmp

/dev/block/mmcblk0p8 504 8 496 2% /cache

/dev/block/mmcblk1p1 30421 14081 16339 46% /external_sd

/dev/block/mmcblk0p12

5606 755 4851 13% /data

/dev/block/mmcblk0p12

5606 755 4851 13% /sdcard

/sbin #./parted /dev/block/mmcblk0

./parted /dev/block/mmcblk0

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) p

p

p

Error: /dev/block/mmcblk0: unrecognized disk label

(parted)

Why is the blk0 an unrecognized disk label? I just want to print out the existing partition labels to see what's there.
[G Pad 10.1 General] fatbas202:
This is interesting. I'm not sure why you're getting those results. Are you in TWRP or booted into a full ROM?
[G Pad 10.1 General] faheyd:
Oh my, that post was for the Sero Pro forum. XDA went down today while I was posting that. It must have done something weird. Please disregard. Thank you.
[G Pad 10.1 General] lamp216:
can u help me i bring back to life my gpad with ur guide but when i try to remove the white lines nothing happens, on the shell everything is good, but nothing change, the only think different than happen to me is that when i flash Candy5 it say unable to mount data, well after trying to flash Candy5 i reboot system and my gpad boot with the kdz test att but this time i have the 11.6 gb of internal memory, my problem are the white lines, and i cant mount data in twrp :/

EDIT: i now can mount data partition i just format thougth twrp, but keep with the white lines problems
[G Pad 10.1 General] faheyd:
The first time I did it, I too had the white lines, as I didn't follow the instructions exactly. Do each line of the instructions and you should be OK. Do it EXACTLY.
[G Pad 10.1 General] draexo:
I got stuck and then unstuck myself.

I got stuck at step 29. make_ext4fs /dev/block/mmcblk0p33 would not work and Candy 5 would not flash. I then formatted data with TWRP and in doing so it changed it to ext4! I then did the white line fix and I am now back on stock rooted kitkat, which is where I wanted to be! 11.05GB available now.

Thanks for the tutorial and all your help.
[G Pad 10.1 General] faheyd:
And my first unsuccessful time doing this, step 29 was where I messed up, I tried to manually format the partitions, even though it looked successful, it did not work. I had to go back and start over and flash candy5 to get the partitions right.
[G Pad 10.1 General] jamesyun:
help

ok so im a beginner in rooting and programing.

I got all the way up to this step`cp /sdcard/parted /sbin/` This copies the parted binary to /sbin so it can be executed in the path. I had trouble running `/sdcard/parted`, but YMMV.

but when i enter that code, it tells me that cp is not recognized as a command.

i've installed busybox btw. that might affect it

Any help would be appreciated
[G Pad 10.1 General] fatbas202:
Are you running this via ADB in TWRP or in a Terminal Emulator in a booted ROM? We need more details in order to help...
[G Pad 10.1 General] jamesyun:
I'm using the adb via command prompt on my laptop. I got into the adb and saw the long thread of possible commands. Meanwhile, my lg g pad was plugged into the usb and on the TWRP screen.

Let me know if im doing something wrong.

Thanks for replying
[G Pad 10.1 General] fatbas202:
Thanks for the update.

What happens when you type `ls /sbin`?

Remember not to run these commands with the backticks. You are running what's inside of them.

Don't worry, we'll get you squared away. I'm limited on time that I can help at the moment, so please be patient with me as we work through this.
[G Pad 10.1 General] fatbas202:
Thank you for posting your results!
[G Pad 10.1 General] cogency:
Woops?

Hi [MENTION=1772416]fatbas202[/MENTION] - thanks so much for all of your help and guide on this topic. Everything went very smoothly until this morning when I attempted to fix the aboot partition before drinking my morning cup of coffee. For some reason I renamed the 7z file (removed the extension) and flashed that partition instead of unzipping it like a normal human would (like I said, hadn't yet had my morning brew). Anyways, as one might expect the tablet now won't boot to anything. Can't get an ADB to recognize, but when I plug it into my computer I see a partition with folders "image" and "verinfo".

Can you point me the way to get this mess cleaned up or did I kill it completely?

Again, thanks for all of your time and guide on this subject - it was very easy to follow and well written - don't let my dumb mistake be a barometer on its success!
[G Pad 10.1 General] cogency:
Just want to keep you posted on what I have tried. I tried to dd the aboot partition from a linux box because the partitions are showing up on that. However, after pushing the correct aboot - still no dice.

Followed these instruction roughly, substituting our aboot: http://androidforums.com/threads/gu...oad-mode-no-recovery-mode-no-fastboot.893311/
[G Pad 10.1 General] fatbas202:
Oh, wow. Sorry to hear about this. I kind of didn't expect the link that you sent to show all of the partitions, but if it does, then that's awesome. So you definitely flashed to /dev/sdX6 (it's the 6th partition on the v410)? Can you provide the output of `gdisk -l /dev/sdX` (of course replacing X for whatever it comes up as on your system)? And you did do a backup of your aboot partition to something like /sdcard/aboot-fukt.img right? :) One other idea is that if you accidentally dd'ed the zip then it's possible that you copied it to the wrong partition too. Maybe try checking out this link and copying all of those images to the corresponding partitions: http://xdaforums.com/showpost.php?p=56126957&postcount=38.

I'll think on this more and get back to you if I have any other ideas.
[G Pad 10.1 General] cogency:
Here's the output:

I did make a backup before as well - maybe I should try to restore that one? Could be interesting to try and restore the several partitions from the dropbox link as well. I'll attempt that first.

Thanks again!

---------- Post added at 10:53 AM ---------- Previous post was at 10:33 AM ----------

Here's what I tried this morning with no success:

root@ubuntu:/home/ubuntu/Downloads# dd if=/home/ubuntu/Downloads/aboot.img of=/dev/sdb6
4096+0 records in
4096+0 records out
2097152 bytes (2.1 MB) copied, 0.365142 s, 5.7 MB/s
root@ubuntu:/home/ubuntu/Downloads# dd if=/home/ubuntu/Downloads/abootb.img of=/dev/sdb22
4096+0 records in
4096+0 records out
2097152 bytes (2.1 MB) copied, 0.310071 s, 6.8 MB/s
root@ubuntu:/home/ubuntu/Downloads# dd if=/home/ubuntu/Downloads/encrypt.img of=/dev/sdb24
1024+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 0.184446 s, 2.8 MB/s
root@ubuntu:/home/ubuntu/Downloads# dd if=/home/ubuntu/Downloads/boot.img of=/dev/sdb13
49152+0 records in
49152+0 records out
25165824 bytes (25 MB) copied, 3.0535 s, 8.2 MB/s
root@ubuntu:/home/ubuntu/Downloads# dd if=/home/ubuntu/Downloads/recovery.img of=/dev/sdb14
49152+0 records in
49152+0 records out
25165824 bytes (25 MB) copied, 2.99223 s, 8.4 MB/s

---------- Post added at 11:25 AM ---------- Previous post was at 10:53 AM ----------

No luck with restoring the original aboot.img backup either.
[G Pad 10.1 General] fatbas202:
Crap. That really sucks. I'm kind of at a loss as to what to suggest... Maybe let the battery run all of the way down to make 100% sure that it fully power cycles (it may not be fully powering off before rebooting)? Can you get in to recovery or download mode with button combinations? I really don't have any other ideas off of the top of my head. I'll dig through some forums as I get time to see if we can come up with a solution.