[Tutorial] LG Gpad v410 5.1 to 4.4 downgrade, root, & internal storage fix.

[fatbas202]

It doesn't seem like it worked. I can get into TWRP and see my sdcard but not the internal storage. See attached pics.

Thanks!

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.

 

[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.

 

[fatbas202]

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.

Excellent! Thank you for posting your results here.

 

[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?

 

[swaqas]

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.

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.

 

[fatbas202]

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?

Which ROM, dude?

 

[jeffary]

Which ROM, dude?

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. :good:

 

[fatbas202]

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. :good:

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.

 

[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

Sent from my LG-v410 using Tapatalk

 

[fatbas202]

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

Sent from my LG-v410 using Tapatalk

Hell yeah! Glad it worked for you.

 

[swaqas]

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.

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

 

[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

 

[fatbas202]

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

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.

 

[fatbas202]

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

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

 

[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 !

 

[fatbas202]

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 !

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!

 

[instructor2]

Hello @fatbas202, 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.

 

[fatbas202]

Hello @fatbas202, 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.

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.

 

[instructor2]

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.

this is what i was thinking lately.. thanks

 

[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.