Database Develop

app2sd doesn't work on cm5.0.6

I flashed the cm5.0.6 rom and definitely setup ext2 partition for my new 16G sdcard, but the app2sd always gray out, how can i fix it to make app2sd work?

Think it only works with ext4.

Thanks for the tip.
but when i try to ugrade ext2 to ext3 or ext3 to ext4 by using recovery 1.7, it always show some error info such like run "fs repair"
could u pls give more details for solving this issue?
much appreciated!

Create it from the computer instead. Did you run fs repair? The exact error codes are important to post, it can also help you search and see if anyone else had the same problem.

sounds like your partitioning may not have worked or your sdcard is not legit? have you confirmed it is 16gb?

evilkorn said:
Create it from the computer instead. Did you run fs repair? The exact error codes are important to post, it can also help you search and see if anyone else had the same problem.
Click to expand...
Click to collapse
How to run fs repair command? I connected via adb, there is no fs command

behelit said:
sounds like your partitioning may not have worked or your sdcard is not legit? have you confirmed it is 16gb?
Click to expand...
Click to collapse
I confirmed it's 16g. what does it mean not legit?

Not legit = fake
adb shell fs repair

return back : fs not found

Reformat and start from scratch.
You'll need both fat32 and ext4 partitions.

Hi, can app2sd work with a kingston 16gb class2? Thanks in advance
prettyboy85712 said:
Reformat and start from scratch.
You'll need both fat32 and ext4 partitions.
Click to expand...
Click to collapse

Need help rebuilding emmc

Ok fellas, my nook color has been out of commission for over 2 months. I can boot from sd but not from internal emmc.
Sam has been helpin me but it has been difficult due to him being in a different part of the world. From what i've been told my emmc is corrupt and my partitions need to be rebuilt or formatted.
I have tried the different fixes here and still i am stuck on the N screen.
I am trying to return my NC to stock form.
I will let Sam chime in also. I know there are a lot of talents on this forum and pretty sure this can be fixed.
Thanks everyone..
Sent from my SGH-T959 using XDA App

Hi,
As Wendell said, I've tried helping him with his corrupt emmc.
The problem is:
The emmc semms to be corrupt, or at least some sectors of it. Wendell cannot return it, because it boots to CWR. That's the strange part, though the disk seems totally corrupt, it still seems to be able to boot. I guess some sectors and still working. But I don't know of any way to find out which..
This is what I know so far:
The internal emmc generally returns I/O error when trying to use fdisk or parted.
But, somehow, depending on the bs and count, I can dd /dev/zero to it.
Even after having dd zeros to it, it still seems to boot to internal CWR. So, the dd isn't working. Still don't know why, or how to remedy to it.
If someone could give us a clue or two here, it would be very much appreciated. I must admit I'm really no HDD expert..
Thanks!!
Sam

http://nookdevs.com/Flash_back_to_clean_stock_ROM
Have you guys tried this? Or has an internal EMMC rom been flashed?

Any idea how the partition became corrupt? Did you dual-boot?

Partition became corrupt after flashing a couple of the very first OC kernels. Not sure if thats what caused it but wouldn't boot past N screen. Since then i have been trying to fix it by doing the several fixes to no avail and possibly damaging the emmc even more.
Sent from my SGH-T959 using XDA App

fprice02 said:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Have you guys tried this? Or has an internal EMMC rom been flashed?
Click to expand...
Click to collapse
Please correct if I'm wrong but i think i need the stock recovery for this method. Unfortunately, the stock was replaced with CWR and now i cannot even get rid of CWR off the internal. If I could do it again, I would not place CWR on internal but rather run it off sd. I installed CWR via rom manager because the sd method was not yet available.

Try option number 3 in the thread I made in the general forum. the clockworkmod recover + stuck at " " screen. Flashing cwm via rom manager can cause corrupted /boot partition
Sent from my Vortex using Tapatalk

Woot , thanks for your response.
I have tried those methods to no avail. I can currently boot into CWR via 'home+N' but here is the crazy part, I cannot use the zip that sam made to remove CWR from emmc or even try to update to 3.0.1.0 via the CWR zip. My CWR on the emmc will not budge at all.
Sam, has even tried to erase my emmc totally from being able to boot to CWR just so I can get it looked at by B&N but CWR will not budge.

Excuse my ignorance, but will linux run off the sd card on the nook?
What about using something like GParted? Perhaps the USB bootable image on the sd card might work?

I know you are all trying to help. But please keep in mind that there aren't any obvious answers here. The emmc is corrupt. You can't flash anything to it.. and as I already stated, parted won't work either, it returns I/o error.
The only strange thing is that the nook still boots.. I can't understand that as the emmc lacks any partition table.
We need someone with hdd repairing experience. None of the answers found on existant threads will help Wendell..
Thank you.
Sam
Sent from my Desire HD using XDA App

samuelhalff said:
The only strange thing is that the nook still boots.. I can't understand that as the emmc lacks any partition table.
Click to expand...
Click to collapse
The boot may be from real hardware/non-eemc rom.
I know you said it's a emmc error - but have you tried to flash back to stock using CWM off of the SD with thecubed's MonsterRoot pack?

Yes
Sent from my SGH-T959 using XDA App

I'm sure you have tried this... but just in case...
Can you fdisk the partitions... then dd image img files to it?
I don't know if you will have any way of saving mmcblk0p2 and 3 to save your device specific information.

I believe sam has already tried
Sent from my SGH-T959 using XDA App

Here is what i would try.
First thing, get a cwm sd card setup that is bootable and has a decent amount of space so you can backup your emmc. The cwm sd card will allow us to adb in, but not worry about having any emmc partitions mounted (booting to a full android image would want at least the mmcblk0p2 partition mounted).
Make sure you have adb setup and working, so you can adb in once you've booted into cwm from the sd card. Make sure you know how to use adb pull and adb push to get files onto and off of the device easily.
Boot from the card, adb shell into the device. make sure when you are doing dd commands you are pulling from and writing to image files in a directory on the sd card, not on the emmc. you probably shouldn't even have any emmc partitions mounted at all.
Note: dd and bzip2 are both on the cwm 3.0.10 ramdisk, dunno about the earlier versions
I'd make a backup image of your emmc just in case things go from bad to worse:
Code:
dd if=/dev/mmcblk0 | bzip2 -9 > backup.img.bz2
This will take a while.
Now you'll need a MBR from someone with a stock partition table (i'm dual booting so mine probably won't work, otherwise i'd make one for you). Any volunteers?
Code:
dd if=/dev/mmcblk0 of=mbr.img bs=512 count=1
Once you have this file, just dump the image onto your emmc.
Code:
dd if=mbr.img of=/dev/mmcblk0
once you have a working partition table, you should be on your way to using the standard recovery techniques peppered throughout the forums.
btw, this won't fix any corruption in the extended partition table, that would take a little more effort (i'd have to read up on where/how that info is saved). Also obviously if it's a hardware problem rather than just corrupted data you have more problems than this will fix.
p.s. cwm loading witch a corrupt partiton table isn't that weird imho. the bootloader has barely over 400 bytes to load up the boot file and hand things off, it's probably not taking a close look at the partition map when it does this.

I know am probably being a stupid noob...have you tried the 8 failed boots?
Sent from my NookColor using Tapatalk

wendellc said:
Woot , thanks for your response.
I have tried those methods to no avail. I can currently boot into CWR via 'home+N' but here is the crazy part, I cannot use the zip that sam made to remove CWR from emmc or even try to update to 3.0.1.0 via the CWR zip. My CWR on the emmc will not budge at all.
Sam, has even tried to erase my emmc totally from being able to boot to CWR just so I can get it looked at by B&N but CWR will not budge.
Click to expand...
Click to collapse
Again..probably being a noob...are the file permissions set as ro? Mayhaps you need to change permissions?
Sent from my NookColor using Tapatalk

Lol.
Thanks for all your input.
DD and fdisk return i/o error. DD only works if I use i.e 1M as BS.
It seems there isn't any partition table on the emmc.
I guess some sectors are dead. The idea would be to identify which ones and erase them.
Although simply being able to remove the bootloader would allow Wendell to bring it back to the shop..
Maybe someone has a clue as to how to delete completely the first X sectors of emmc..?
Thanks.
Sent from my Desire HD using XDA App

samuelhalff said:
Lol.
Thanks for all your input.
DD and fdisk return i/o error. DD only works if I use i.e 1M as BS.
It seems there isn't any partition table on the emmc.
I guess some sectors are dead. The idea would be to identify which ones and erase them.
Although simply being able to remove the bootloader would allow Wendell to bring it back to the shop..
Maybe someone has a clue as to how to delete completely the first X sectors of emmc..?
Thanks.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Did you read my post? It is exactly telling you how to replace the first sector of the emmc. you can source it from /dev/zero with a bs=512 and a count=1 if you really wanna wipe the bootloader, but better would be just getting it working yeah? all our nooks have the same partition map (unless we are dual booting) and that map is stored on the first sector. My instruction tell how to pull the first sector with dd, and how to push it back on. notice i'm accessing the mmc directly? not the partitions? so unless his hardware is bad (or the extended partition is corrupt too) then my instructions will work. He just needs a copy of the first sector of a working nook. I'd put mine up but i'm not sure it would work, i have two extra partitions from stock. It probably wouldn't matter, but i'm not 100% sure on that, so i'd rather it be someone else that makes the image from a nook with a stock partition map (the contents of the partitions can be whatever, as long as they are all in the same place as stock).

Hi,
Thanks. Yes, I read your post. dd, for some reason, only works if I set bs to at least 1M. I don't have the NC, but maybe Wendell could confirm that.
Wendell: go to "adb shell" and type [dd if=/dev/zero of="/dev/block/mmcblk0" bs=512 count=1] without the [].
Please confirm that this returns an I/O error.
But for some reason, using 1M or greater as bs works, but the bootloader still isn't erased.. it still boots to CWR..
I'm pretty sure all the I/O error i've had mean that there's a hardware failure.. But that's my opinion, nothing more..
Thanks.

[Linux][RFS]How do I rebuild the /efs/ block device?

I've been playing around and I screwed up my EFS partition. It will not mount to the folder. I have backups of my EFS files on my computer including the nvdata.bin.
I can upload the nvdata just fine and the phone will connect to the network upon reboot. The problem is that the block device which contains EFS data has been destroyed. This means every time I flash a new ROM i have to reupload my nvdata because the block that saves it is not mounted.
How do I rebuild/reformat this block of memory to avoid having to upload my nvdata.bin every time I flash?

See, that's the problem with being one of the top devs, nobody can answer the few questions you have...
Sent from my SGH-I897 using XDA App

Im guessing sdparted wouldnt work?
http://forum.xda-developers.com/showthread.php?t=566669
Sent from my SAMSUNG-SGH-I897 using XDA App

bulletproof1013 said:
Im guessing sdparted wouldnt work?
http://forum.xda-developers.com/showthread.php?t=566669
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
That is for HTC phones.. They use different processors. It would likely cause my phone to freak out because of invalid architecture.

That's a classic, I'm sure there are some adequate fat.format methods but I always used the laziest one: restoring a dump of the partition itself.
I send you a link on twitter.

Thanks SuperCurio. I didn't want to scare people away before I got an answer... but here's what happened.. I used UnBrickable mod to upload BADA bootloaders to my Captivate. It treated my non-Bada formatted partition table as a invalid MoviNAND and tried to reformat it... It never suceeded in boot or whatever it was trying to do because the GPIOs in my phone are different and I could see errors coming across UART output.
When all was said and done, I used UnBrickable mod to restore my device but I did not have a block level backup of the EFS, only files. The EFS would not mount.
The solution was to get an EFS block from another similar device, put it on the SDCard, then type in a terminal:
Code:
su
dd if=/sdcard/efsbackup.bak of=/dev/block/stl3
Finally, I mounted my /EFS/ rewritable and copied my /efs/ backup to the folder.
You can reverse the "if" and "of" to make a backup of the efs before hand.
Everything was working properly until i went and booted NexusS bootloaders and unlocked... lol. I can always restore again.
Thanks Supercurio. I'll post a blank EFS partition soon.

So if we have the block backup...then if we mess up partitions. We just move those blocks back to original place.?
Sent from my SAMSUNG-SGH-I897 using XDA App

bulletproof1013 said:
So if we have the block backup...then if we mess up partitions. We just move those blocks back to original place.?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes. Make a backup of your EFS partition and you can use odin to flash it.

AdamOutler said:
Thanks SuperCurio. <SNIP> I'll post a blank EFS partition soon.
Click to expand...
Click to collapse
Did you ever get to posting a link of a blank efs partition...?
Peace
Devvie
~~~ [email protected] ~~~
Cuisvis hominis est errare, nullius nisi insipientis in errore persevare
——
All spelling mistakes are my own and may only be distributed under the GNU General Public License! – (© 95-1 by Coredump; 2-013 by DevNullius)

Help eMMC Partitions will not save

OK to start I have CM7.1 on my eMMC works fine for many months. I want to install MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer ROM and it does not seem to work. Using CWM 3.2.0.1 flashing looks successful but when I reboot CM&.1 is still on the eMMC.
Tried doing a reset to default using EVRY technich suggested on these forums. No Go.
Using ADB I thought I would manually delete and push the system files over. I mount the system partition /dev/block/mmcblk0p5 and removed the existing files then pushed the new system files. But once I unmount and remount it reverts to the old files. The changes don't write dispite seeing the differences with an ls -al in ADB before the umount.
So I thought I would check the partitions and using fdisk via ADB. Deleted partitions 5, 6,7,8 and rebuilt them but when I write I get.
The partition table has been altered!
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Click to expand...
Click to collapse
I also used the 1 - 5 - 6 - 7 - 8 fix and format zips with no joy.
I can boot to MIUI via SD but I want to put this on the eMMC.
Any ideas on how to fix this?

Yes, the first thing you do is upgrade that CWM. It is too old. You can get a new bootable CWM on my tips thread linked in my signature. Then I would reflash my repair zips as instructed in my partition repair thread. (Sounds like your partition 2 is ok, skip that). Don't forget to reboot between the repair and reformat. Then flash your rom with the new CWM.
Edit: oh, you changed the version in your original post to 3.2.0.1. That version is ok.

leapinlar said:
Yes, the first thing you do is upgrade that CWM. It is too old. You can get a new bootable CWM on my tips thread linked in my signature. Then I would reflash my repair zips as instructed in my partition repair thread. (Sounds like your partition 2 is ok, skip that). Don't forget to reboot between the repair and reformat. Then flash your rom with the new CWM.
Click to expand...
Click to collapse
Thanks for trying to help.
OK created a bbotable SD using the CWM-based Recovery v5.5.0.4 (CWM-5.5.0.4-bootable_SD.zip from your tips page)
Used that to apply NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Rebooted into CWM-based Recovery v5.5.0.4
Applied NookColor-emmc-format-partitions-5-6-7-8.zip
The applied MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer.zip
Rebooted the eMMC and still running CM7
I then retried the repartitioning and the following message was listed when I checked the log:
The partition table has been altered!
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Click to expand...
Click to collapse
Which matches the results I was seeing from adb.

rodneyshupe said:
Thanks for trying to help.
OK created a bbotable SD using the CWM-based Recovery v5.5.0.4 (CWM-5.5.0.4-bootable_SD.zip from your tips page)
Used that to apply NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Rebooted into CWM-based Recovery v5.5.0.4
Applied NookColor-emmc-format-partitions-5-6-7-8.zip
The applied MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer.zip
Rebooted the eMMC and still running CM7
I then retried the repartitioning and the following message was listed when I checked the log:
Which matches the results I was seeing from adb.
Click to expand...
Click to collapse
When you boot to your SD version of your ROM, can you save anything to the emmc media partition? I am wondering if somehow your emmc chip became read only. I have had that happen to my SD cards before, so it may be possible that it happens to your embedded chip. They act like they have been written to, but when you come back, nothing has changed.

leapinlar said:
When you boot to your SD version, can you save anything to the emmc media partition? I am wondering if somehow your emmc chip became read only. I have had that happen to my SD cards before, so it may be possible that it happens to your embedded chip.
Click to expand...
Click to collapse
OK Booted the SD with MIUI on it and was able to (or what seemed to be) save a file to the eMMC
BUT when I rebooted it was gone. It is like the write does not take on reboot.
I can even edit the file and it seems fine but the file is gone once I reboot.
It is like the changes are cached but not committed.
So I thought I would try creating the file and even edited the file from USB after booting the MIUI SD. Then when I stopped and restarted USB connection and then the file was gone.
So Somehow the eMMC is readonly.
So how do I fix that?

rodneyshupe said:
OK Booted the SD with MIUI on it and was able to (or what seemed to be) save a file to the eMMC
BUT when I rebooted it was gone. It is like the write does not take on reboot.
I can even edit the file and it seems fine but the file is gone once I reboot.
It is like the changes are cached but not committed.
So I thought I would try creating the file and even edited the file from USB after booting the MIUI SD. Then when I stopped and restarted USB connection and then the file was gone.
So Somehow the eMMC is readonly.
So how do I fix that?
Click to expand...
Click to collapse
That is exactly what happened to my SD. Looked like everything took, but take card out and put back in and changes did not last. This happened on my phone SD. No amount of trying different PCs, different device readers, formatting programs, partition managers, nothing would work. I could read and copy things from it, but never got it to accept anything. I just bought a new one. I know that won't work on your embedded chip.
You are lucky at least you can use your SD to run things. I have found there is no significant difference between running on SD and emmc.
Maybe someone else has some info how to fix it. I searched the web for a long time looking for solutions and found nothing. One other user here on XDA has reported the same symptoms on his SD, but I never heard of anybody that this happened to their embedded chip. Sorry.

leapinlar said:
That is exactly what happened to my SD. Looked like everything took, but take card out and put back in and changes did not last. This happened on my phone SD. No amount of trying different PCs, different device readers, formatting programs, partition managers, nothing would work. I could read and copy things from it, but never got it to accept anything. I just bought a new one. I know that won't work on your embedded chip.
You are lucky at least you can use your SD to run things. I have found there is no significant difference between running on SD and emmc.
Maybe someone else has some info how to fix it. I searched the web for a long time looking for solutions and found nothing. One other user here on XDA has reported the same symptoms on his SD, but I never heard anybody that this happened to for their embedded chip. Sorry.
Click to expand...
Click to collapse
Thanks for trying to help. It is appreciated.
In the case of your SD did you try burning an image over top?
I was thinking if I had a complete image of the eMMC I might be able to use dd via ADB to overwrite the whole thing. Back up the files from partition 2 first and then write them back once it was finished.
Thoughts?
Problem is where could I get a "good" image of the entire eMMC?

rodneyshupe said:
Thanks for trying to help. It is appreciated.
In the case of your SD did you try burning an image over top?
I was thinking if I had a complete image of the eMMC I might be able to use dd via ADB to overwrite the whole thing. Back up the files from partition 2 first and then write them back once it was finished.
Thoughts?
Problem is where could I get a "good" image of the entire eMMC?
Click to expand...
Click to collapse
For my SD I tried everything. Images, formatting, partitioning, etc. Nothing could be written to the device.
You can make your own images of emmc by dding in reverse and write emmc partitions to your SD via adb. But if it is truly read only like my SD was, you will be able to write nothing back no matter what tool you use.

Yea I was hopping I could get an image of the entire working eMMC that included the partition tables and see if that worked in case the problem is related to a setting in the partition table.

Repartition + FUSE in the next build of CM10

Hello,
I think it would be interesting in the next buid of CM10 implement FUSE.
For those not familiar with FUSE, this makes the EMMC (Internal) and DATA partitions are one.
FUSE is the standard in new android devices like the Galaxy S3.
With this gain in space, since both would have 6.7 GB of user data (photos for example) and for applications.
This would require using a repartitioning and as it should be, we could give more space to the partition and Partition System Cache.
I made a build with FUSE on, and doing great. It should be a standard in CM10 for P990.
A greeting and I apologize for the translation.

no thanks, i really like having my system and sd card separated...

60nine said:
no thanks, i really like having my system and sd card separated...
Click to expand...
Click to collapse
Sorry, SDCARD is the defaul name for internal.
FUSE = (Internal EMMC + DATA)
Without FUSE:
Partition 8 = DATA [1,5GB]
Partition 9 = EMMC [5,3 GB]
With FUSE only have:
Partition 8 = USERDATA [6,8 GB]
The user can see 6,8 GB in Internal SD

Sounds good but will it work,
If you want the CM team to pick it up you will have to talk with them directly.
Good luck
Sent from my LG-P990 using xda app-developers app

Tamps said:
Sounds good but will it work,
If you want the CM team to pick it up you will have to talk with them directly.
Good luck
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Only change two files, and they here in the p990 repo.
Other solution is clone a p990, change two files and create a p990-fuse repo.

why would i fuse those two partitions? they are fine like they are now.
if i want to format the internal storage without affecting apps data i can while i'm using the actual partitions set, i cannot with the new mixed one.
this fuse leads what advantages?

pidocchio said:
why would i fuse those two partitions? they are fine like they are now.
if i want to format the internal storage without affecting apps data i can while i'm using the actual partitions set, i cannot with the new mixed one.
this fuse leads what advantages?
Click to expand...
Click to collapse
- You can format only DATA, and can format only EMMC too with FUSE with CWM.
- When you use a file manager, you see the same that without FUSE but you have 6,7GB.
- You can install 6,7 GB of APP.
- FUSE is ANDROID standard. All new Android devices use FUSE.

sounds great. make a flashable zip, we'll start using it

Sure
I'd give it a try i have a device i can use for testing

Ok,
I'll upload a zip with NVFlash and partitions.
Anyone can upload misc and lgdrm partitions?
Open Terminal
su
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard0/misc.img
dd if=/dev/block/mmcblk0p6 of=/storage/sdcard0/lgdrm.img
After doing this, in the internal memory of the device, there should be two new files: lgdrm.img and misc.img.
Screenshot:
http://imageshack.us/photo/my-images/90/screenshot2012110410465.png/
http://imageshack.us/photo/my-images/12/screenshot2012110410462.png/

ProgMaq said:
Ok,
I'll upload a zip with NVFlash and partitions.
Anyone can upload misc and lgdrm partitions?
Open Terminal
su
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard0/misc.img
dd if=/dev/block/mmcblk0p6 of=/storage/sdcard0/lgdrm.img
After doing this, in the internal memory of the device, there should be two new files: lgdrm.img and misc.img.
Screenshot:
http://imageshack.us/photo/my-images/90/screenshot2012110410465.png/
http://imageshack.us/photo/my-images/12/screenshot2012110410462.png/
Click to expand...
Click to collapse
misc.img: http://www.mediafire.com/?ik7gq8ddxxx0ujz
lgdrm.img: http://www.mediafire.com/?mf6oe0mio7xh9g9
I hope they are useful

Very thanks Chuck Bartowski
But your lgdrm.img is empty when mount.
This occurs when you have used nVFlash, not a problem, but I would like the original partition lgdrm compare with mine.
Anyone can upload original misc and lgdrm.
Thanks.

What about usb storage(internal storage) mounting after FUSING ?
Will it work as before ?
Sent from my Galaxy Nexus using xda premium

ProgMaq said:
Very thanks Chuck Bartowski
But your lgdrm.img is empty when mount.
This occurs when you have used nVFlash, not a problem, but I would like the original partition lgdrm compare with mine.
Anyone can upload original misc and lgdrm.
Thanks.
Click to expand...
Click to collapse
Ok, sorry, I didn't know.
I have reflash 10b with NVflash ( stock partition ), ROOT and Recovery, and I have flash cm10.
misc.img: http://www.mediafire.com/?1n0pmdbembdeorr
lgdrm.img: http://www.mediafire.com/?dan8jpucxjdw4ok

Chuck Bartowski said:
Ok, sorry, I didn't know.
I have reflash 10b with NVflash ( stock partition ), ROOT and Recovery, and I have flash cm10.
misc.img: http://www.mediafire.com/?1n0pmdbembdeorr
lgdrm.img: http://www.mediafire.com/?dan8jpucxjdw4ok
Click to expand...
Click to collapse
Thanks again, but even installing the stock version, the misc partition lgdrm and do not return to be the same (missing files)
What about usb storage(internal storage) mounting after FUSING ?
Will it work as before ?
Click to expand...
Click to collapse
Working same
Good news, I have uploaded the file. Zip
http://forum.xda-developers.com/showthread.php?p=33671985

Take a look at this link
teamw.in/DataMedia
So i think we might loose usb mounting on pc
Sent from my LG-P990 using xda app-developers app

ProgMaq said:
Sorry, SDCARD is the defaul name for internal.
FUSE = (Internal EMMC + DATA)
Without FUSE:
Partition 8 = DATA [1,5GB]
Partition 9 = EMMC [5,3 GB]
With FUSE only have:
Partition 8 = USERDATA [6,8 GB]
The user can see 6,8 GB in Internal SD
Click to expand...
Click to collapse
and still - i like it as it is
i still have 2 partitions with 6,8 GB total - but i can keep things more organized with 2 partitions than with one...
for me it's just like having 2+ PC harddrives - one only for the system, and other disks for the other files...

how do I flsh this to files with nvflash?

instead of fuse of internal memory(1.5gb) n internal sd(5.5gb).....
can i have fuse of internal sd(5.5gb) n external sd(i have 16gb) so that i can get...
external sd---21.5gb....
imo 1.5gb is enough for app data but 5.5gb is not enough for sd data files(nova 3 almost 2gb)
i hav mounted my externalsd as internalsd so that sd data files are saved in ext but 16gb not enough(game addict)...
hope u can help..thanks

ullekh99 said:
instead of fuse of internal memory(1.5gb) n internal sd(5.5gb).....
can i have fuse of internal sd(5.5gb) n external sd(i have 16gb) so that i can get...
external sd---21.5gb....
imo 1.5gb is enough for app data but 5.5gb is not enough for sd data files(nova 3 almost 2gb)
i hav mounted my externalsd as internalsd so that sd data files are saved in ext but 16gb not enough(game addict)...
hope u can help..thanks
Click to expand...
Click to collapse
I like it ,interesting thought
But what will hapn when sd ejected and phone restarted
Sent from my LG-P990 using xda app-developers app