Database Users

For All sdcard issues

09/01/2012:
this tutorial may work for those who are having encryption issues on ics or jb roms (the error is related to mmcblk0p2(data))
well, after some months of work, here´s an tutorial about how to fix the mostly common sdcard issues.
1º Of all :***Be sure of what you´re doing,or else you can corrupt the partition table of you sdcard/brick your phone,and I´ll not be responsible of it***
2º-Do Not send me PMs, post here so everyone that have the same problem can now how to fix it.
3º-If you are an starter, you can post here your questions,but be sure that you haven´t found answers on Google or other threads.
and 4º-Read ALL topic before start and try one solution than the other,they´re in order of difficulty and risk of get an "permanent" brick.
0 - Always backup your EFS folder, maybe its not related to this thread but it´s also very important to remember.
I -If you have a folder called "voodoo" in your sdcard, you may have voodoo enabled on your ROM, so be sure of disabling it before trying a new rom or a stock rom.
if you´re on another rom already and having problems in mounting partitions, try to flash you last rom or a kernel that supports voodoo and it´s compatible with your new rom.
II-If you´re getting problems in mounting DBDATA,Download a full rom that contains DBDATA to flash with odin(or only flash dbdata,but you´ll have to do a full wipe later). To see if it haves dbdata.rfs by opening your .tar file in 7zip or others.
III-If you´re getting Can´t mount data (dev/block/mmcblkl0p2) File exists, try to flash an kernel with voodoo suport,if it still the same, format data in the menu of your recovery.
IV-If you´re getting can´t mount sdcard (/dev/block/mmcblk0p1)File exists, try to access it via ADB and send pull file command to recover your files(must have root),if you could do that, so try to format it via recovery.If not work,Download gparted, burn it on cd (it´s an CD with a tool of linux) and go to ADB shell to run this command:
su
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
now
reboot your PC in gparted and format mmcblk0p1(it´s the first partition) in FAT32.
Done
V-If you´re getting cant mount sdcard (/dev/block/mmcblk0p1) with (invalid argument) You can try the fix IV and see if it works,if not, proceed to VI.
VI-If you´re getting cant mount data(dev/block/mmcblk0p2) or can´t mount sdcard (/dev/block/mmcblk0p1) with (invalid argument) or (no such file or directory) you may have to do this:
***search on google for 'fdisk' commands first***
You MUST*¹ remake your partition table manually,so the phone have the /data partition back to boot.
*¹
In some cases you can use gparted to do this, without doing it manually,
you shoud only mount mmcblk0 before.
you can run this command line on adb shell to mount it:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
You Will have to format it and it MUST have the partitions as said below.
YOU SDCARD MUST HAVE THE FOLLOWING PARTITION TO BOOT ON AND RECOGNIZE INTERNAL SDCARD:
/dev/block/mmcblk0p1
AND
/dev/block/mmcblk0p2
Start:
Open ADB,comnect your phone and proceed.
run adb shell
su
fdisk /dev/block/mmcblk0
p (you should see your partition table,POST HERE BEFORE CONTINUING)
YOU ARE NOW ABOUT TO REMAKE YOUR PARTITIONS:
partition 1 will correspond to mmcblk0p1(SDcard) and partition 2 will correspond to mmcblk0p2 (DATA)
**DO ONLY AS I SAY HERE, UNLESS YOU MAY GOT I/O ERROR ON YOUR SDCARD AND ITS ALL OVER. I say because it happened to me and i had to dissolder the internal sdcard an use only the external.**
**********IF YOU DONT HAVE ANY IDEA OF LINUX COMANDS: DO NOT PROCEED !!!!!!!!!*************
tap on adb:
n (will create a new partition)
1 (partition number)
press enter on keyboard so it selects the first block
get a calculator and estimate the size of the partition 1.IT MUST HAVE around 2GB left.
write the block number you got in calculator(BE SURE OF WHAT YOU TAPE HERE)
t
b (partition 1 is done and formatted as fat 32)
Now again:
n
2
enter on keyboard
enter again so it select the last block
(DO NOT TYPE COMMAND "T" FOR PARTITION 2, IT BY DEFAULT SET TO LINUX EXT FORMAT)
p (you will see you new partition table)
****IT MUST HAVE 2 partitions, partition 1 is in fat 32 format and partition 2 is in linux format(AND MUST HAVE AROUND 2GB)****
w (IT WILL WRITE YOU NEW PARTITION TABLE ON YOU SDCARD,SO BE SURE IT's ALL CORRECT)
Done,
now tap:
q
fdisk /dev/block/mmcblk0
p (you should see your new partition table, if ok reboot your phone, flash an stock rom for vibrant (I sugest an T959UVJFD ROM only to correctly format your partitions),root it,backup it,and enjoy,You can put a custom rom if you want so.)
If You have an error That does not appear here and you think it may me related to you sdcard just ask. In one or two days I or others developers may post here a possible solution.
Thanks For Google and some XDA users who indirectly helped me doing this.
You can try Paragon Hard Disk Manager in place of gparted
but remember: mmcblk0p1 is FAT32 and mmcblk0p2 in EXT2 (in truth it´s not EXT2, its in rfs, but the stock rom T959UVJFD is the only that I have absolute sure that will do the conversion).
Sorry for my bad english, it´s not my native language.

Great post doiiido!
Hay doiiido, you have been thanked and this post has been added to the [REF][KERNEL] ✰ The Official Vibrant Kernel ßible Thread ✰ → 07/05/12.
Great post!

News
Original pos by: ferhanmm
link to it:
http://forum.xda-developers.com/showthread.php?t=1665123
[FIX] Data wipe error or Can't mount /dev/block/mmcblk0p1
Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (http://www.goo-inside.me/gapps/gapps...317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get/...mtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/show....php?t=1447303
Samsung Vibrant

News
Original post by:
draikz
Link to original post:
http://forum.xda-developers.com/showthread.php?t=848737
** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly **
Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
I DO REALIZE THAT MOST OF THESE LINKS ARE BROKEN, PLEASE SCAN THE THREAD TO FIND UPDATED LINK. I'M NOT VERY ACTIVE ANYMORE, SORRY!
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO JUSTANOTHERCROWD):
Quote:
Originally Posted by justanothercrowd
JFD ODIN Images from Samsung (PDA)
www.justanotherdev.slackdev.com/T959UVJFD.tar
MD5:632730f6b637f53e5b10e5cbc8b966a7
512 PIT File (PIT Extract first!)
www.justanotherdev.slackdev.com/s1_odin_20100512.rar
MD5:b5628c8e183fdd8f4c703321ca40e33a
ODIN
www.justanotherdev.slackdev.com/Odin3.rar
ALL 3 Files plues the root update.zip
http://tinyurl.com/2bc5b6r
thx to KopyKatKiller
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.
Hope you enjoy, this is my first guide, please don't flame. Any comments or suggestion is suggest, or if you have your own method I'll also post it
POST YOUR RESULTS!
-Steven
The only forums this guide should be posted on is XDA, DZ, and PHANDROID under the username DRAIKZ and EXPLOSIVE. If it helped you, feel free to donate a coke or two!

Completely Ruined my Partitions - Need Glow Restore IMG

Hello everyone,
Yesterday evening I bought a Nook Touch with Glow, went home, backed it up, or so I thought (my backup in retrospect is only 75mb and when I restore it, it does try to boot but says "Install Failed"), then proceeded to install android with Glownooter. Most of the programs I tried to launch closed after a few seconds (though I followed the instructions and installed both .zip parts), so I was going to restore and try again.
Following the restore instructions, I blew out the entire Nook partition table in preparation and now I feel I am screwed without external help. I tried everything last night for three hours...
Could anyone upload a stock .img file for me please? I really want to use the device and don't think it would be right for me to return it to the store for an exchange because of a mistake I made. Currently my SD card has nooter on it, but last night I had CWM open with the factory.zip someone posted and tried installing that zip to no avail... I even tried the n2T-Recovery_0.2.
Thank you.

trimalchioinwestegg said:
Hello everyone,
Yesterday evening I bought a Nook Touch with Glow, went home, backed it up, or so I thought (my backup in retrospect is only 75mb and when I restore it, it does try to boot but says "Install Failed"), then proceeded to install android with Glownooter. Most of the programs I tried to launch closed after a few seconds (though I followed the instructions and installed both .zip parts), so I was going to restore and try again.
Following the restore instructions, I blew out the entire Nook partition table in preparation and now I feel I am screwed without external help. I tried everything last night for three hours...
Could anyone upload a stock .img file for me please? I really want to use the device and don't think it would be right for me to return it to the store for an exchange because of a mistake I made. Currently my SD card has nooter on it, but last night I had CWM open with the factory.zip someone posted and tried installing that zip to no avail... I even tried the n2T-Recovery_0.2.
Thank you.
Click to expand...
Click to collapse
The partition table of the NSTG is the same as the NST.
I am in the same situation, and so far I have not had a huge success reviving mine but perhaps this thread could assist you in the right direction. Remember to save /rom information before trying anything
http://forum.xda-developers.com/showthread.php?t=1805936
good luck!

srgarfi said:
The partition table of the NSTG is the same as the NST.
I am in the same situation, and so far I have not had a huge success reviving mine but perhaps this thread could assist you in the right direction. Remember to save /rom information before trying anything
http://forum.xda-developers.com/showthread.php?t=1805936
good luck!
Click to expand...
Click to collapse
I know - I read that thread front to back last night and made no progress either.
Am I correct to assume that a backup image from someone would restore all partitions and completely solve our problem?
If so, if someone would upload an image in virgin state it would solve problems for everyone. I'm completely surprised that such an image is so elusive.

Anybody's full backup image will wipe out all your personalized data in /rom and /factory/rombackup.zip.
Generally, AFAIK, all these Nooters can screw up your Nook but not re-partition it or format it.
Make an effort to get to get your /rom back.

Renate NST said:
Anybody's full backup image will wipe out all your personalized data in /rom and /factory/rombackup.zip.
Generally, AFAIK, all these Nooters can screw up your Nook but not re-partition it or format it.
Make an effort to get to get your /rom back.
Click to expand...
Click to collapse
Is /rom an item unique to each device, or are you worried about me losing books/login information in "personalized data"? I had done nothing with my device except get past initial startup when I rooted it, so I have no personal items (books or otherwise) invested. I'm sorry if this is a silly question, but I don't understand.
Edit: Also, I used the magic (something) application to delete all partitions from the nook prior to the restore because it would not let me restore until then. If I had known my backup was invalid I would never have done that.

Attached is an image of what my restore contains. It does try to boot, but then says "Install Failed."
Note there is a romrestore.zip.

trimalchioinwestegg said:
I know - I read that thread front to back last night and made no progress either.
Am I correct to assume that a backup image from someone would restore all partitions and completely solve our problem?
If so, if someone would upload an image in virgin state it would solve problems for everyone. I'm completely surprised that such an image is so elusive.
Click to expand...
Click to collapse
Yes, that's the idea.
But as Renate mentions, that would overwrite you /rom partition with invalid data from another device (mac address, serial, and things like that).
But in the same situation I managed to salvage my /rom partition, so if I ever install such an image from someone elses' NSTG i coudl overwrite /rom with the data from my own device.
It could be also possible to generate such an image of an NSTG and then carefully unpack, delete the most sensitive files from /rom and repack the image to share. That way no sensitive infromation would be shared/compromised.
If you happen to stumble on such an image, please let me know.
BTW, those /boot files you have, could you pack them in a zip file and send it to me or post it here in the forums? I formatted my /boot partition and I could make good use of yours (no sensitive/personal information contained in there)

srgarfi said:
Yes, that's the idea.
But as Renate mentions, that would overwrite you /rom partition with invalid data from another device (mac address, serial, and things like that).
But in the same situation I managed to salvage my /rom partition, so if I ever install such an image from someone elses' NSTG i coudl overwrite /rom with the data from my own device.
It could be also possible to generate such an image of an NSTG and then carefully unpack, delete the most sensitive files from /rom and repack the image to share. That way no sensitive infromation would be shared/compromised.
If you happen to stumble on such an image, please let me know.
BTW, those /boot files you have, could you pack them in a zip file and send it to me or post it here in the forums? I formatted my /boot partition and I could make good use of yours (no sensitive/personal information contained in there)
Click to expand...
Click to collapse
I'm throwing in the towel because my /rom partition is gone and I understand all of that now. Tonight I will exchange for another (against my conscience) and make a proper backup before I do anything going forward.
In my research I found this:
search.4shared.com/postDownload/2YsbIxQJ/nook_glow_partition_files__023.html
It is all of the files except rom, and you will find the boot files in the 0 directory.
Good luck, and thanks for the help everyone.

Did you check both the p1 (/boot) and p3 (/factory) partitions to see if you had rombackup.zip?
Of course check p2 (/rom) for devconf.
Try repartitioning your Nook. You'll need CWR on an SD card with ADB or Noogie and Linux tools.
The script nookpart.sh is in my signature.

trimalchioinwestegg said:
I'm throwing in the towel because my /rom partition is gone and I understand all of that now. Tonight I will exchange for another (against my conscience) and make a proper backup before I do anything going forward.
In my research I found this:
search.4shared.com/postDownload/2YsbIxQJ/nook_glow_partition_files__023.html
It is all of the files except rom, and you will find the boot files in the 0 directory.
Good luck, and thanks for the help everyone.
Click to expand...
Click to collapse
Are you sure you can't recreate the partition table and mount /rom to get access to your files?
It is explained in the thread I mentioned. If so, then it would be fairly easy to recover your device.
Be careful when returning the NSTG to B&N, some of the operations performed are not covered in the warranty and they could want to charge you....
Anyway, thanks for that pointer! I'll see if I can use it to revive my NSTG

srgarfi said:
Are you sure you can't recreate the partition table and mount /rom to get access to your files?
It is explained in the thread I mentioned. If so, then it would be fairly easy to recover your device.
Be careful when returning the NSTG to B&N, some of the operations performed are not covered in the warranty and they could want to charge you....
Anyway, thanks for that pointer! I'll see if I can use it to revive my NSTG
Click to expand...
Click to collapse
Good thing I bought it at Staples.

Renate NST said:
Did you check both the p1 (/boot) and p3 (/factory) partitions to see if you had rombackup.zip?
Of course check p2 (/rom) for devconf.
Try repartitioning your Nook. You'll need CWR on an SD card with ADB or Noogie and Linux tools.
The script nookpart.sh is in my signature.
Click to expand...
Click to collapse
I fired up CWR but saw no USB activity on the computer (for ADB). Could you please tell me how to get ADB running? I did download your script and was interested in trying, but only got USB Disk mode on Noogie (which I couldn't get ADB to work with).
Thank you!

ADB on CWR can be a bit tricky.
It seems like the daemon dies sometimes on disconnecting and stuff.
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/ADB
Boot it up on CWR first, then connect the USB cable.
In Windows it should show both Removable storage and ADB on the taskbar.
Code:
adb usb
adb shell
Make sure that you have the CWR with USB ADB and not Wifi ADB.

trimalchioinwestegg said:
I fired up CWR but saw no USB activity on the computer (for ADB). Could you please tell me how to get ADB running? I did download your script and was interested in trying, but only got USB Disk mode on Noogie (which I couldn't get ADB to work with).
Thank you!
Click to expand...
Click to collapse
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
And search for a file named "ADB + Fastboot + Drivers.zip" in the forum.
With all that you can get ADB running in a Windows machine in no time.

Renate NST said:
ADB on CWR can be a bit tricky.
It seems like the daemon dies sometimes on disconnecting and stuff.
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/ADB
Boot it up on CWR first, then connect the USB cable.
In Windows it should show both Removable storage and ADB on the taskbar.
Code:
adb usb
adb shell
Make sure that you have the CWR with USB ADB and not Wifi ADB.
Click to expand...
Click to collapse
Forgive me, but where would I find CWR with USB ADB? I currently have CWM-based Recovery v5.0.2.7 from the Glownooter thread. The 2gb image.
At the bottom of the black screen I have some errors, though:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Nothing reacts when I plug in USB.

srgarfi said:
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
And search for a file named "ADB + Fastboot + Drivers.zip" in the forum.
With all that you can get ADB running in a Windows machine in no time.
Click to expand...
Click to collapse
I did successfully install ADB and the Android SDK earlier, but it is not running on my Nook under CWM and I do not know how to get it on there. The guide says "The Nook must specifically have an adbd daemon running on either WiFi or USB. The stock Nook has no adbd."
Do you know how?

trimalchioinwestegg said:
I did successfully install ADB and the Android SDK earlier, but it is not running on my Nook under CWM and I do not know how to get it on there. The guide says "The Nook must specifically have an adbd daemon running on either WiFi or USB. The stock Nook has no adbd."
Do you know how?
Click to expand...
Click to collapse
You should have adb.exe somewhere. From a command window in windows (start menu, execute cmd.exe), go to the path where adb.exe resides and type "adb devices": this will tell if your nook is hooked and accessible.

srgarfi said:
You should have adb.exe somewhere. From a command window in windows (start menu, execute cmd.exe), go to the path where adb.exe resides and type "adb devices": this will tell if your nook is hooked and accessible.
Click to expand...
Click to collapse
I do.
C:\Users\XXXX\AppData\Local\Android\android-sdk\platform-tools>adb usb
error: device not found
C:\Users\XXXX\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
I don't believe ADB is running on the nook, which is currently booted into CWM.
I do see the showing USB Mass Storage Device in device manager, but I cannot access the device as I can in noogie.

You may have the CWR running WiFi ADB (which doesn't make sense to me because you can't select AP).
If you have USB ADB running on CWR you should see on the USB in the taskbar two things, Mass Storage and ADB.

Renate NST said:
You may have the CWR running WiFi ADB (which doesn't make sense to me because you can't select AP).
If you have USB ADB running on CWR you should see on the USB in the taskbar two things, Mass Storage and ADB.
Click to expand...
Click to collapse
How can I make CWR use USB?

Flashing Now Fails

I've been flashing N7 with no issues as recently as over the weekend. Today I tried to flash a new ROM and it failed. Tried a second, different ROM, same result. Do not know what I did. Any thoughts?

Error log would help greatly.

How do I get/generate the log? Haven't had to do it before.
Thanks,
Paul

The logs= errors displayed on the screen provided by the interface you use to flash the rom (recovery, computer...)

Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...

do I need to create a partition? Never get more details despite the tease.
Thanks,

First -
Try and download a different (NEWER) TWRP. Re-flash TWRP. Try again
or
Have you tried completely wiping the device? And pushing a ROM from ADB or using a USB OTG and Memory stick?
I had issues with my nexus becoming VERY unstable. Leading to issues.
I completely, and I mean completely, wiped. To the point that all that device basically had was a recovery, and a bootloader.
I proceeded to flash again, BOOM all fixed up.

Is there a new TWRP?
I did a factory restore after wiping everything thing, if that is what you mean?
It was working as expected last week, don't know what I did to screw it up

Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.

ibsk8 said:
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Did this, and it said it copied but I am unable to locate it. It says 0\media\data But that folder structure doesn't exist, at least according to file expert

Will a complete wipe/restore create a partition?

pmgreen said:
Will a complete wipe/restore create a partition?
Click to expand...
Click to collapse
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
pmgreen said:
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
Click to expand...
Click to collapse
Focus your efforts here; it certainly looks like a first-order problem.

bftb0 said:
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
Focus your efforts here; it certainly looks like a first-order problem.
Click to expand...
Click to collapse
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why

pmgreen said:
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
Click to expand...
Click to collapse
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?

bftb0 said:
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
Click to expand...
Click to collapse
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash

pmgreen said:
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
Click to expand...
Click to collapse
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ su
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed

bftb0 said:
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ such
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
Click to expand...
Click to collapse
Thanks bftb, you are correct it's a can't open zip. No error than fail and it can't open the zip. It says updating partition but nothing changes
The file names are from the developers, once of which I recently successfully flashed. Tried coping the log to the SD card, but unable to find /data/media/0. Do I need to recreate a partition?

(FYI there was an auto-correct typo in my prior post - "su" not "such". Derp)
pmgreen said:
Do I need to recreate a partition?
Click to expand...
Click to collapse
No. (There is no way to do that with the tools we have anyway)
Unless what you mean by "recreate" is rebuild/reinitialize a filesystem in a partition - that's a possibility.
You need to try and figure out why you can't read files.
As a workaround, you can put files on a USB key (FAT formatted, not NTFS) and using TWRP access them by putting the USB key on the other end of a OTG cable.
Your posts are a bit vague - I can't even tell if you have tried other ROM files, whether you checked them to see if they are the correct size/checksum, etc.

pmgreen said:
Tried coping the log to the SD card, but ...
Click to expand...
Click to collapse
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.

bftb0 said:
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
Click to expand...
Click to collapse
I am not familiar using ADB pull. Tried using a root file manager to access the log but don't see.
Greatly appreciate your help, let me know what other info I should paste.
Thanks,

[Q] replacing factory.zip image for 8 failed boots

is there a reasonably easy way to replace the factory.zip? (partition 3?)
I have what must be an older color, that if I do the 8 failed boots, it reverts all the way back to software 1.0.0
I find that it wont auto update to 1.4.3.
I have to first apply a 1.2 update, before it will take the stock B&N 1.4.3
(or manually thru cwm apply a 1.3 for example)
its not a deal breaker, but I'd prefer a solution that isnt boot into linux/dd the partition
this is a unit I muck around with, testing various roms, and getting it back to stock just involves a few extra steps.
thanks!

The easiest way to get it back to stock is just to flash it directly back with CWM. Go to my NC Tips thread linked in my signature and follow item A15. I have a CWM flashable 1.4.3 there.
However if you want to change the factory zip in partition 3, I can walk you through how to do that. It basically means mounting p3 in a rooted operating system like CM and copying the new zip there.
Sent from my BN NookHD+ using XDA Premium HD app

"However if you want to change the factory zip in partition 3, I can walk you through how to do that. It basically means mounting p3 in a rooted operating system like CM and copying the new zip there."
I'd like to try that if you are willing. Thanks!
I think im pretty experienced.
I have done cm7 / cm10 / on colors/NT many times, have run all the possible scripts you might think of more than once to fix various issues on many colors
one thing Ive noticed on this one after resetting data to the new partition scheme,
that just sort of nags at me, (besides not having a restore to the way I like it from the 8 failed boots)
after Im at 1.4.3 and think Im done, if I do a factory reset from within the stock rom
going to the "factory" screen (and before skipping oobe) seems to flipflop between thinking its got sw 1.0.0 and 1.4.3 , however, the running version in both cases is 1.4.3.
thanks again
----- edit -----
addl info:
I have a CM7 loaded / with the NookColorUMS am able to mount the partition, but have no idea how to maneuver to it, or the format of the zip I'd be dropping in it. (I assume its just a factory rom renamed) On the tablet, cant seem to find the partition after its mounted in either file manager program I've tried, and I've forgotten any real linux/Unix skills I used to have... and it would appear its not usable on the Windows side.

The zip to use is the one I referenced above in item A15. Just rename it factory.zip.
And since you have the UMS utility, mount p3 in the first section. Then plug in your USB cable to Windows and it should show up as a drive. Look at it with Windows Explorer. You can tell if you are there by seeing the factory.zip. Backup that one to your PC in case something goes wrong. Then copy the new factory.zip on the drive replacing the old one. Be careful with the other files there, especially the rombackup.zip. That is critical and needs to stay there. (In fact back that up to your PC too).
That's it, you're done. Next 8 failed boot you should be on 1.4.3.
Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier.
Sent from my BN NookHD+ using XDA Premium HD app

" And since you have the ums utility, mount p3 in the first section. Then plug in your USB cable to Windows and it should show up as a drive. Look at it with Windows Explorer."
Yeah, this is where the plan goes south,
anything mounted in UMS doesn't seem to be translated properly for Windows. I get a "you must format the disk" but no additional usable mapped drives.
the internal partitions in the version of cm7 UMS I have are all down below, in the 2nd section
do I have to mount the "big" extended partition first? then in the second tab of UMS the factory p3? (ill try it in a few)

No, don't do that. I'll give you alternate instructions.
Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory
The go to /factory with your root file manager.
Proceed as earlier instructed.
Did you see my edit above?
Edit: and the reason your drives are not showing properly in Windows is you must activate UMS in CM7. Pull up your notification area and tell it to allow access after you plug in the cable
Sent from my BN NookHD+ using XDA Premium HD app

the su/terminal thing is just what I need I think. will report back in 5
re:
"Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier."
Oh, I have no trouble getting em back to stock, and "close" to perfect, but I could sell this unit and 6 months from now I wanna be able to tell the user just do this ( 8 factory failed) , and its good to go, and Im not supporting a rebuild to stock 1.0, then 1.2, or a cwm flash.
Edit2:
re: " Edit: and the reason your drives are not showing properly in Windows is you must activate UMS in CM7. Pull up your notification area and tell it to allow access after you plug in the cable "
Yea, Im doing that. Does one have to disable debugging or something too?
Its not a big deal at all, just didn't have it committed to memory and hasn't been necessary to this point to access the protected partitions.

mikeataol said:
the su/terminal thing is just what I need I think. will report back in 5
re:
"Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier."
Oh, I have no trouble getting em back to stock, and "close" to perfect, but I could sell this unit and 6 months from now I wanna be able to tell the user just do this ( 8 factory failed) , and its good to go, and Im not supporting a rebuild to stock 1.0, then 1.2, or a cwm flash.
Click to expand...
Click to collapse
if you sell or give away your unit, be sure to erase and deregister with stock so it is removed as your device on the B&N servers. Otherwise the new user will not be able to register it. And you know stock recovery must be installed before the 8 failed boot works, right?
Also see my edit above about how to fix ums..... Yes you must disable debugging.
Sent from my BN NookHD+ using XDA Premium HD app

"Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory"
Hi, I did the whole process twice , just to be sure before coming back... 2nd time was with a newly downloaded copy of the signed A15 zip
Are you sure the factory recovery wants the signed zip file and not the stock?
after 8 failed boots it does a data reset, then tried the factory image reinstall but the factory image reinstall part fails about 1/3rd of the way through
---
had to wing it on the mounting / copy a little as just running terminal put me in a read only file system
but im 100% positive I Installed the signed1.4.3. into factory (backed up the 1.0.0 factory.zip first)
just noting , I DID use the repartition scripts on this prior, setting it to the "new" 5gb data / 1gb media
but it seems to me that the stock recovery isnt liking the signed zip file

mikeataol said:
"Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory"
Hi, I did the whole process twice , just to be sure before coming back... 2nd time was with a newly downloaded copy of the signed A15 zip
Are you sure the factory recovery wants the signed zip file and not the stock?
after 8 failed boots it does a data reset, then tried the factory image reinstall but the factory image reinstall part fails about 1/3rd of the way through
---
had to wing it on the mounting / copy a little as just running terminal put me in a read only file system
but im 100% positive I Installed the signed1.4.3. into factory (backed up the 1.0.0 factory.zip first)
just noting , I DID use the repartition scripts on this prior, setting it to the "new" 5gb data / 1gb media
but it seems to me that the stock recovery isnt liking the signed zip file
Click to expand...
Click to collapse
That is possible since I modified it. Go get a clean one from B&N. Go their support page and look for update. There will be a link to a big file that ends in .npk. Download that and rename to factory.zip.
Sent from my BN NookHD+ using XDA Premium HD app

It seems the 1.4.3 update zip from B&N isn't suitable as a factory.zip
neither the signed or unsigned works
I've grabbed 2 factory zips from other units
1.2.0 and 1.3.0 and copied them into factory, and they both work as expected on the 8 failed boots
I didn't get the complete result that I wanted , but good enough.
Thanks again for your help leapinlar, It's appreciated.

Could you put a custom rom as a factory.zip? Just a thought. It'd be cool to rollback to a stable rom like cm7 if something in a cm10/11 nightly goes wrong.

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

EDIT: If you are coming here for the first time, this guide should still work, but @PorygonZRocks has created a flashable zip that should deal with a lot of these issues automatically. You can check out his post here:
https://forum.xda-developers.com/showpost.php?p=75787067&postcount=699
This method will indirectly allow you to root the LG Gpad v410 after it has been upgraded to Lollipop 5.1.1. Yes. Rooting LG v410 Lollipop. It's through a downgrade, but it works.
It took a while to get working, but here's how I did it. The process is straightforward, but the details matter greatly. You will brick your device if you mess up. Please read everything *first* before you do anything. Be sure you understand the process. I'll try to explain what's going on along the way.
An external SD card is extremely helpful for this process. You *could* adb push everything, but that will tedious.
First, you need some files.
The 4.4.2 KDZ which is a TEST OS, but it can be rooted and it downgrades to a Bump'able bootlaoder:
http://forum.xda-developers.com/g-pad-10/general/kdz-lg-g-pad-7-0-v410-t3224867
The LG 2014 Flash Tool:
http://www.mediafire.com/download/fwrcd3pdj0svjtb/LG_Flash_Tool_2014.zip
Android LG Drivers:
https://www.androidfilehost.com/?fid=24052804347802528
Parted for Android. You can probably find it other places, but I found this file:https://dl.dropboxusercontent.com/u/84115590/LG%20G2%2016GB%20Solution/sdparted-recovery-all-files.zip
EDIT: There seems to be a lot of confusion here. My bad. All you need is the file named "parted" from this zip file - nothing else. Just put that one file in the root of your external SD card.
https://dl.dropboxusercontent.com/u/84115590/LG G2 16GB Solution/sdparted-recovery-all-files.zip linked from here: http://www.**********.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/
EDIT2: The dropbox link is down. I've attached the file directly.
The Candy5 ROM (This will potentially save you some manual steps. Somewhat optional, but highly recommended):
http://forum.xda-developers.com/g-pad-10/development/rom-candy5-g-pad-v410-lollipop-5-1-1-v2-t3111987
Flashify APK:
http://www.apkmirror.com/apk/christian-gollner/flashify/flashify-1-9-1-android-apk-download/
TWRP for the v410:
http://forum.xda-developers.com/g-pad-10/development/recovery-twrp2-8-5-0lgv400-410-t3049568
LG One Click Root:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
(You may use Purple Drake or whatever else you want. They all use the same root script as this does and the GUI is helpful for novices.)
Android SDK (specifically adb.exe. After installing go to SDK Manager and ensure that Android SDK Platform Tools is checked):
http://developer.android.com/sdk/index.html
For clarification below, when I have commands in "quotes" they are Windows commands. When they are in `backticks` they are commands that you run inside of ADB which actually run on your device....as root. Root can screw things up. Please be extra cautious. If you blame me for messing up your device I will laugh at you. But that's not gonna happen, right? Good. Let's go.
Now that you have everything, put it all into a folder where you can access it easily.
Install the LG Drivers.
Install Android SDK (or otherwise get adb.exe).
Extract all of the archives.
Move the KDZ to the LG Flash Tool 2014 folder.
Put the tablet into Download Mode by powering it off, holding VolUp, and plugging in the USB cable. Press VolUP when instructed. You must be in Download mode before continuing.
Run LGFlashTool2014.exe. Select the KDZ file. Click "CSE Flash". Click "Start". Select "English" and click OK. Do not change anything else.
WAIT for the flash to continue. If you really want to brick your device, here's a good opportunity.
The device will reboot into Android 4.4.2. You will only have 4GB of internal storage at this point. DON'T PANIC! We are fixing it.
Enable USB debugging.
Connect the device.
Install and run LG One Click Root. Wait for the device to be rooted before proceeding.
Copy the Flashify apk, TWRP image, and Candy5 ROM to your external SD card.
Install Flashify and flash TWRP to the recovery partition.
Use the Flashify menu to reboot in to recovery.
DON'T PANIC! You will get white vertical lines on the boot screen from now on. They only show up during boot animations. A small price to pay. This may be fixed at a later date. for the time being! Thanks to marcsoup's first post ever, we have a fix! Details below. PLEASE click this link and thank him!
Things get tricky here. Copy parted to your external SD card and then run "adb shell" from Windows to get a shell in TWRP.
In TWRP, unmount /data by tapping Mount > uncheck Data.
`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.
`chmod +x /sbin/parted` Make it executable.
`parted /dev/block/mmcblk0` Run parted against the internal mmc
`p` Prints the partition table.
`rm 34` Deletes partition 34 labeled "grow". This is the root of our problem. The KDZ apparently only creates a 4GB partition, I assume so the test build has maximum compatibility with all sized devices.
`rm 33` Deletes partition 33 "userdata"
`p` Print to verify
`mkpartfs` Create a partition and put a filesystem on it. If we only expand the partition it won't help us because the filesystem is still only 4 GB.
a) name: userdata
b) type: ext2 (the tool only supports ext2. This is ok for now.)
c) start: 3439MB (the end of part 32. IT MAY BE DIFFERENT FOR YOU!) Be sure you do not omit the MB part otherwise the offset will overwrite another critical partition.
d) end: 15.8GB (where "grow" ended above. IT MAY BE DIFFERENT FOR YOU!) Be sure you do not omit the GB part otherwise the offset will overwrite another critical partition.
`p` Verify. For me it did not name the partition properly. Gotta fix that.
(if necessary) `name 33 userdata` This is critical for mount to find it in /dev/block/platform/msm.sdcc.1/by-name/ on some/all ROMS.
`p`. Verify one last time. Compare it to my partition table in the attachments. If you want to brick, delete some random partitions here.
Flash Candy5 with TWRP. It's only 239 MB, so it will flash quickly. I do this because Candy5 will reformat mmcblk0p33 from ext2 to ext4 for you. It does this as part of it's system boot, apparently. If you install a different ROM that does not do this, you can reformat it by running `make_ext4fs /dev/block/mmcblk0p33`. If your ROM does not have make_ext4, it likely has some differnt method to make an EXT4 filesystem. `/system/bin/mke2fs -t ext4 /dev/block/mmcblk0p33` may work better. Just flash Candy5 and be done with it.
Tap Wipe > Swipe to Factory Reset.
Tap Reboot > System.
WAIT!!! It will take a minute for the ROM to start the first time. You will have white lines and and possibly a white screen. WAIT. It's moving the DEX files to cache, formatting a partition, creating default folders on the internal storage, and several other things. WAIT! When the screen goes dim or turns off then it's ready.
Cycle the display or turn it on. You should be at the Candy5 lock screen.
USB debugging is on by default. Run "adb shell".
`mount | grep userdata` Make sure mmcblk0p33 is mounted.
`df` Make sure /data is 11.3 GB (or whatever size it is on non-16GB devices).
HELL YEAH, you downgraded, rooted, and fixed the partition problem. Enjoy your tablet!
Thanks to dopekid313 for finding the KDZ.
Thanks to timmytim for Candy5.
Thanks to the creators of the root script, flashify, TWRP, and XDA for being so awesome.
Thanks to marcsoup for fixing a fix to the white lines.
Thanks to navin56 for the partition dumps. PLEASE thank his post!
White lines fix.
What we are going to do is flash the aboot partition with the stock image provided by navin56. I've removed the extra files from the dump, so simply download aboot.img.7z below. Unzip it using 7zip.
These commands are to be run in TWRP. Reboot to TWRP recovery and connect with "adb shell". All of the following commands will be run in ADB under TWRP. If you cannot figure out how to get here, please post in the thread and someone will help you. Onward:
If you do everything correctly then you don't have to reflash your ROM and you won't lose data. This process can be done any time after flashing the KDZ, even before you follow the steps above to resize the userdata partition. It's a completely separate process.
Unzip aboot.img.7z so you have the file named aboot.img. You should also make sure that aboot.img's MD5 sum is e97431a14d1cee3e9edba513be8e2b52. Do not flash the 7z file. Please.
Copy aboot.img to your external SD card. It should live at /sdcard/aboot.img
Boot to TWRP and run "adb shell"
`ls -al /dev/block/platform/msm_sdcc.1/by-name/` Let's make sure we are flashing the right partition. On my device "aboot" is /dev/block/mmcblk0p6. You should verify this on your device or you WILL brick your tablet.
`dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot-fukt.img` Let's back up our current aboot partition before we go flashing things just in case there are unintended consequences later. Be sure you have the same partition that "aboot" referred to in the 4th step or you have just backed up the wrong partition.
`dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p6` Be sure the file exists, is the correct aboot.img, and you are flashing the right partition. You have been warned!!
Reboot TWRP and enjoy your boot animations again.
If I missed anything, please let me know. As far as I know this is the very first tutorial that details what is necessary to accomplish this. Please hit the Thanks button on every thread that you visit to download files!
FAQ:
Q: Why do I only have 11.3 GB of space when my device is 16GB?
A: The entire internal SD card (eMMC) is 16 GB. Gotta have someplace to install the bootloader, recovery, android, the modem OS, the secondary bootloader, the cache, the resource and power manager, and all of the other partitions necessary for the table to operate. Please look at the second screenshot in the OP. All of those 33 partitions take up room on the internal card. Fortunately ALL of those partitions ONLY take up about 4.4 GB. Hence the 'userdata' partition is ~11.3 GB.

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!

Thank You, Worked Great

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

grandamle91 said:
Thank You, Worked Great
Click to expand...
Click to collapse
Glad to be of help!
dopekid313 said:
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
Click to expand...
Click to collapse
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.

I just noticed since we formatted the userdata it screws up TWRP. It won't mount Data and it says the settings are corrupted

grandamle91 said:
I just noticed since we formatted the userdata it screws up TWRP. It won't mount Data and it says the settings are corrupted
Click to expand...
Click to collapse
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.

/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.
Code:
mount | grep userdata
is empty
Code:
df
does not show data

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.

gridironbear said:
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.
Click to expand...
Click to collapse
At what point did it bootloop? What was the last step that you took before rebooting?

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.

drumm3rb0y said:
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.
Click to expand...
Click to collapse
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.

fatbas202 said:
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.
Click to expand...
Click to collapse
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.

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

shahidmianoor said:
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
Click to expand...
Click to collapse
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.

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

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?

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.

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?

iphone5sf said:
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?
Click to expand...
Click to collapse
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.
nmnm4alll said:
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.
Click to expand...
Click to collapse
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.
zmali1 said:
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
Click to expand...
Click to collapse
summonholmes said:
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?
Click to expand...
Click to collapse
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.