Tablet ICOO D50 Lite (A13)
OS: Android 4.0.4 ICS
How do I know which section is the boot, which is the recovery, emmc and other nand*
The system has /dev/block/nand[a-i] (9pcs)
nandh - cache
nande - data
nandd - system
and sdcard - /dev/block/vold/93:64 (?)
How do I know the rest of the mount point?
mount does not show the boot and recovery.
xorkrus said:
Tablet ICOO D50 Lite (A13)
OS: Android 4.0.4 ICS
How do I know which section is the boot, which is the recovery, emmc and other nand*
The system has /dev/block/nand[a-i] (9pcs)
nandh - cache
nande - data
nandd - system
and sdcard - /dev/block/vold/93:64 (?)
How do I know the rest of the mount point?
mount does not show the boot and recovery.
Click to expand...
Click to collapse
Using terminal emulator or ADB shell type:
mount
This will list the mount points. If your rooted you can also type (Run as root in ADB shell or terminal emulator):
cat /proc/dev
This will also provide mount information and other similar information.
Sent from my SCH-I535 using xda premium
shimp208 said:
Using terminal emulator or ADB shell type:
mount
This will list the mount points. If your rooted you can also type (Run as root in ADB shell or terminal emulator):
cat /proc/dev
This will also provide mount information and other similar information.
Click to expand...
Click to collapse
View attachment mounts.txt
Not found any information about boot or recovery in mounts (and /proc/dev - not found)
xorkrus said:
View attachment 1395857
Not found any information about boot or recovery in mounts (and /proc/dev - not found)
Click to expand...
Click to collapse
Try running the following command from ADB shell
Code:
# cat /proc/mtd
This should return an output similar to but not exactly identical to
Code:
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 00140000 00020000 "misc"
mtd3: 00060000 00020000 "splash"
mtd4: 0ba00000 00020000 "system"
mtd5: 03f00000 00020000 "cache"
mtd6: 0a0a0000 00020000 "userdata"
mtd7: 01400000 00020000 "userdata2"
mtd8: 01400000 00020000 "cust"
From here you should be able to tell which ones is boot, recovery, etc.
shimp208 said:
Try running the following command from ADB shell
Code:
# cat /proc/mtd
This should return an output similar to but not exactly identical to
From here you should be able to tell which ones is boot, recovery, etc.
Click to expand...
Click to collapse
Code:
adb shell cat /proc/mtd
/proc/mtd: No such file or directory
and other *mtd* devices in /dev or /proc - not found.
xorkrus said:
Code:
adb shell cat /proc/mtd
/proc/mtd: No such file or directory
and other *mtd* devices in /dev or /proc - not found.
Click to expand...
Click to collapse
Seems your disk device got an internal FTL and does not uses MTD. Look for the device node (e.g. /dev/nand, /dev/block/nand, compare device node id with the partitions) and run [busybox] fdisk on it to print out the partition sizes. Now you can by the sizes guess which is the boot partition. Use dd if=/dev/block/nandx of=testboot.img and see if you'll get a valid boot image. Now you know for sure.
kuisma said:
Seems your disk device got an internal FTL and does not uses MTD. Look for the device node (e.g. /dev/nand, /dev/block/nand, compare device node id with the partitions) and run [busybox] fdisk on it to print out the partition sizes. Now you can by the sizes guess which is the boot partition. Use dd if=/dev/block/nandx of=testboot.img and see if you'll get a valid boot image. Now you know for sure.
Click to expand...
Click to collapse
View attachment fdisk.txt
I need not only the boot-partition. I would like to know, for example, nanda - /, nandb - / system, nandc - boot, nandd - recovery, etc...
On the output of commands fdisk, i was not able to correlate the sections.
Only nandi - /mnt/sdcard and nande - system partition.
xorkrus said:
View attachment 1409237
I need not only the boot-partition. I would like to know, for example, nanda - /, nandb - / system, nandc - boot, nandd - recovery, etc...
On the output of commands fdisk, i was not able to correlate the sections.
Only nandi - /mnt/sdcard and nande - system partition.
Click to expand...
Click to collapse
You already know system, cache and data. Also, root and boot lives in the same partition.
Related
Can we add a new section for the LG Optimus One P500?
Thank You
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
I agree!
Bye
Franco
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
Yes, please create a forum for the LG Optimus P500.
giacor
came on men
create this section for LG Optimus one with Google!
thanks
Yes!!! You know you want it!
Thanks!
yes please, can you add this section?
yes please, can you add this section?
Add it.
Thanks!
Please, Add it
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
Yes I think it would be useful
Proud owner of a LG P500 Optimus One since 2 days, great device, please open a section for it! It deserves that!
I'm seeking a rom dump from the P500 to aid in porting froyo to the LG VS740. I'll also try to make a custom recovery for you as I have done ones for the lg ally and htc incredible as a thank you for dumping the files.
It should be able to be rooted with universal androot or else use the rageagainstthecage-arm5.bin method.
Once rooted from adb shell or terminal app type:
Code:
su
cat proc/mtd
note the mtd partition # of boot & recovery.
then in the dd parts use the mtd number of your boot and recovery partitons
for example if boot is mtd3 on P500 do dd if=/dev/mtd/mtd3 of=/sdcard/boot-dump.img bs=4096
then type
Code:
cd /system
tar zcvf /sdcard/system-dump.tar.gz *
dd if=/dev/mtd/mtd1 of=/sdcard/boot-dump.img bs=4096
dd if=/dev/mtd/mtd0 of=/sdcard/recovery-dump.img bs=4096
Please someone upload these 3 files from p500:
system-dump.tar.gz
boot-dump.img
recovery-dump.img
Thanks again.
Also, in case anyone is worried there is no personal user data in /system thats all in the /data partition.
I agree we need a Optimus One P500 forum.
IMHO it's one of the most interesting middle class Android phones: better screen resolution than HTC Wildfire or Samsung Galaxy 3. An alternative to HTC Aria/Gratia
I have rooted my P500 and i have found this :
cat proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
but when i tried to TAR files the system told me
tar: not found
I have WIN XP Pro and maybe TAR is for linux or i'm wrong in something ...
if you could help me we can make it.
bye and sorry for my english.
Get busybox for phone and do it on phone with terminal eumulator. Optionally do adb pull of your entire system folder and zip it up if all else fails. Need boot and recovery too.
I'd like a section for Optimus One ...
Have someone installed Flash Lite for default browser?
Ok I just downloaded a dump thanks fughy. I am looking at pics and don't see a navigational pad. Can someone confirm it has one or it not & what it uses other than touch screen for navigation as thats needed for recovery. Please list all hardware buttons/keys also please.
I have a custom amon ra recovery that needs to be tested. Please PM if interested. Md5 is below to check against after download.
MD5sum b15d0d4a6588b28b58ee16cf9470ab5f recovery-thunderg_test.img
drellisdee said:
Ok I just downloaded a dump thanks fughy. I am looking at pics and don't see a navigational pad. Can someone confirm it has one or it not & what it uses other than touch screen for navigation as thats needed for recovery. Please list all hardware buttons/keys also please.
I have a custom amon ra recovery that needs to be tested. Please PM if interested. Md5 is below to check against after download.
MD5sum b15d0d4a6588b28b58ee16cf9470ab5f recovery-thunderg_test.img
Click to expand...
Click to collapse
The P500 has no touchpad or something else for navigation. The only keys are:
- Power button on top
- Volume Up/Down on right side
- Menu, Home, Back, Search on front
I would love to create my own custom rom for this device but I'm quite new to this. Is there somewhere a good tutorial on how to create a custom rom based on an original rom?
This LG Optimus is the number ONE
As promised here is a beta amon ra style recovery for opt1 thunderg.
Its untested as I don't have one to test it on.
Key mapping is up/down = vol-up and vol-down
select = power
backup = search
If the keys aren't right use the key code debugger under "other" menu and give me the key code outputs.
Fastboot IF enabled on optimus one can be accessed by "adb reboot bootloader".
The best way to test this if you have fastboot is to do
Code:
fastboot boot recovery-thunderg_test1.img
if done this way it will boot from ram and will be lost upon reboot. IE. its temporary if it needs some changes instead of actually flashing it.
If you need help setting up fastboot/adb drivers reference my post here for the Lg Ally
http://androidforums.com/ally-all-things-root/146564-ally-recovery-img-here-custom-roms.html
It should either be 618e or 618f for adb.
If you don't have fastboot on device this will flash it:
Do this from a su (root) adb shell (preferred) or terminal on phone after you have copied recovery-thunderg_test1.img & flash_image to root of your sdcard. Flash_image is attached to the post linked above.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-thunderg_test1.img
Also if you have a file named install-recovery.sh in system/etc you will need to rename it to install-recovery.sh.bak prior to flashing a recovery.
Download at:
http://www.mediafire.com/file/atz2309jc5d5zqc/recovery-thunderg_test1.img
MD5 = 954c6249e400c0b779b8f47cdb79d87c
This is a simple little guide that'll show you how to back up the phone without the famous nandroid. So as we can use it to get fastboot to work and restore the phone back without nandroid.
adb shell //enter the device native shell
$ su //enter the secure shell (make sure your screen is unlocked when you run this command, then click allow when the window pops up on the phone's screen)
# cat /proc/mtd //show device partitions
Here's an example output. Note: not all phones are like this, some have different partitions. This just happens to be the structure of the my old LS670.
cat /proc/mtd
dev: size erasesize name
mtd0: 00700000 00020000 "boot"
mtd1: 07c20000 00020000 "cache"
mtd2: 00700000 00020000 "recovery"
mtd3: 00140000 00020000 "splash"
mtd4: 00700000 00020000 "FOTA_STO"
mtd5: 09e80000 00020000 "system"
mtd6: 0a4e0000 00020000 "userdata"
mtd7: 00080000 00020000 "misc"
mtd8: 00180000 00020000 "persist"
Then we will back them up to the SD card
# cat /dev/mtd/mtd0 > /sdcard/boot.img
# cat /dev/mtd/mtd1 > /sdcard/cache.img
# cat /dev/mtd/mtd2 > /sdcard/recovery.img
# cat /dev/mtd/mtd3 > /sdcard/splash.img
# cat /dev/mtd/mtd4 > /sdcard/FOTA_STO.img
# cat /dev/mtd/mtd5 > /sdcard/system.img
# cat /dev/mtd/mtd6 > /sdcard/userdata.img
# cat /dev/mtd/mtd7 > /sdcard/misc.img
# cat /dev/mtd/mtd8 > /sdcard/persist.img
Similiarly for the others..
To restore your phone to it's previous state, you'll need fastboot which should come with the SDK.
# exit //exit the secure shell
$ exit //exit the device native shell
fastboot flash boot /sdcard/boot.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash cache /sdcard/cache.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash recovery /sdcard/recovery.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash splash /sdcard/splash.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash FOTA_STO /sdcard/FOTA_STO.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash system /sdcard/system.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash userdata /sdcard/userdata.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash userdata /sdcard/misc.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash persist /sdcard/persist.img //wait for 'sending...OKAY / writing...OKAY'
fastboot reboot //reboot the device
After that, you can zip all of the img files and upload it for us.
This will be really appreciated.
Update me if you need any help
Please Dell Venue Users, help us restore our bricked devices
Thank you
Clarification...
Let me make sure I understand this correctly...
All I need to do to create an update.zip to restore the phone is:
Take these 9 image files from the phone, zip them, name the zipped folder "update.zip"?
Will doing this potentially fix all the "bricked" dell vunes?
If so... Can that "update.zip" folder be flashed from fastboot?
This HOWTO is only useful for people who have NOT yet installed a stock recovery or who have lost the custom recovery after KDZ or LGMDP flash.
Why I posted it? Since I have had enough of complaints about screwed phones via ROM Manager, also there is some broken rf.sh script I have heard of.
Step 1:
- Download (see attachment) the flash_image.zip
- unzip it
- and put the flash_image binary on the root of your SD card (via USB cable).
Step 2:
- Dowload a recovery of your choice (CWM or AmonRA) from this thread.
- Unzip it on your local box and find the recovery.img file.
- Put the recovery.img to the root of your SD Card (via USB cable)
Step 3a - via terminal emulator
- Run terminal emulator on your phone (download one from market if you do not have it yet, duh!)
- type these command exactly: $ denotes a normal user, # denotes root. This character should NOT be typed into terminal emulator!
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
or
Step 3b:
- Install Android SDK (EXE installer recommended for Windows users.)
- run command prompt (cmd.exe) on your Windows box, or run the following from shell on your Linux box:
Code:
> adb shell
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# exit
$ exit
> adb reboot recovery
Step 4:
Now you should find yourself in your shiny new custom recovery. Do whatever you need there.
Q: Is not there an easier way? This seems like a lot of typing? It sucks - I have heard about ROM Manager!
A: ROM Manager's way of flashing recovery is broken by design. Do NOT use it unless you are comfortable with rescuing your phone via ADB/fastboot like many people before.
Q: I already have custom recovery. Do I need to do this if I want to switch from CWM to AmonRA or vice versa?
A: No. This thread has recovery ZIPs when can be flashed from recovery itself.
Q: HELP!!! I screwed and now my phone is stuck in fastboot mode! What should I do?!?!
A: You are officially lame, very lame person. Now go here to fix it.
Q: But my phone is not rooted (no su binary) - the above does not work! I tried to root it via z4root, GingerBreak, SuperOneClick but everything failed! What should I do? Am I stuck with stock ROM?
A: No! See the LGMDP method below.
Nice guide
This way newbies won't be confused where to search.
BTW, a little mistake: in the adb codes it's flash_image recovery /sdcard/recovery.img
Alternative method: Flashing custom recovery via LGMDP.exe
Tried to root it via z4root, GingerBreak, SuperOneClick but everything failed? No problem! Flash the recovery via LGMDP.
Step 1:
Download P500-CWM-3.1.0.0.zip (CWM 3.1.0.0 included, if you want something else, replace recovery.img with whatever you want) and unzip it.
Step 2:
- Browse to the folder where you unpacked the ZIP and run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job. It will backup your IMEI and MACs to .NV2 file, reboot your phone, flash recovery and restore the NV2 backup. Do NOT interrupt it or disconnect your phone until it says "Download complete"! Do NOT delete the NV2 backup!
Step 3:
Done! Now when you press Home + Volume Down + Power, you should find yourself in your shiny new custom recovery. Now you can flash a rooted ROM via flash zip menu.
Q: I am a moron and have interrupted the process. Now I get a black screen with some weird fastboot text, what to do? HELP!!!!
A: Yes, you are a moron. See [HOWTO] Revive a bricked P500 on fastboot mode (the SHORT way) thread.
Q: Can I just quickly root my stock ROM after flashing recovery? I do not want a custom ROM.
A: Yes. Download su-2.3.6.3-efgh-signed.zip and flash it from recovery. Reboot, download Busybox Installer from the market, run and install busybox on your phone.
--- reserved ---
Thx doktor, it helps some of my friend who lost their recovery while upgrading to official GB...
+1
Nice one man, really useful and funny text.
Yo,added this to the N00B repo.
"Q: Can I just quickly root my stock ROM after flashing recovery? I do not want a custom ROM.
A: Yes. Download su-2.3.6.3-efgh-signed.zip and flash it from recovery. Reboot, download Busybox Installer from the market, run and install busybox on your phone."
In reference to the above words, cud i use this as a method to root my stock GB 2.3.3??? cos nothing else seems to root it and installing sdk and adb and all tat, seems too complex!
Of course.
nice guide TS
but this guide also can use for thunderg recovery right ???
and i not quite understanding ur step 3a
which is this :
type these command exactly: $ denotes a normal user, # denotes root. This character should NOT be typed into terminal emulator!
Click to expand...
Click to collapse
but in my mind just type EXACTLY what the below quote write
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Click to expand...
Click to collapse
but you say the things in 1st post make me confuse
so just follow and type the word exactly ???
No comment, everything I wanted to say has been censored
get what you meaning already
When I type
flash_image recovery /sdcard/recovery.img
I take the error message
mtd: not writing bad block at 0x00440000
error writing recovery : No space left on device
But I have at least 60MB on my phone's memory...
edit:
OK,that error bricked my phone again...
evripidis said:
error writing recovery : No space left on device
But I have at least 60MB on my phone's memory...
Click to expand...
Click to collapse
Has nothing to do with the space for /recovery on a separate partition.
evripidis said:
edit:
OK,that error bricked my phone again...
Click to expand...
Click to collapse
Congrats.
doktornotor said:
Has nothing to do with the space for /recovery on a separate partition.
Click to expand...
Click to collapse
KDZ is always saving me always!
How can I fix that about /recovery?
Because I don't understand, I don't have a partition for recovery?
If is that, why after KDZ update, original recovery works properly?
I am worried about bad block that error message said...
evripidis said:
I am worried about bad block that error message said...
Click to expand...
Click to collapse
Yeah, am I worried too, should not report any bad sectors (at least not on this phone).
Code:
> adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
I get this
Code:
>adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
In google I found this http://android.modaco.com/content-p...kmod-recovery-for-zte-blade-oled-tft/page/20/
He gets the error at the same point.
And this http://androidforums.com/647576-post25.html
I did everything as I was meant to, but when I get to the point to insert the text, both on pc or on phone I get an error message...What's wrong?
celtic-paolino said:
I did everything as I was meant to, but when I get to the point to insert the text, both on pc or on phone I get an error message...What's wrong?
Click to expand...
Click to collapse
Eh... Insert what text? Where? What error message?
When I have to write the codes in the terminal emulator or in cmd.exe, I get these messages:
TE: su: permission denied
and the rest doesn't obviously work
CMD: doesn't work at all even if I installed the program you said...
Hi folks,
im noob, so sorry if my questions are poor for you...
I try to understand android boot sequence on my JB (under CM10). I found some docs and there should be specific partitions (boot, recovery, system, cache, data).
My understanding of the boot sequence is now:
A) normal boot:
1) Power ON ->
2) bootloader ->
3) boot-partition where i flashed the kernel aka boot.img ->
4a) system-partition with the OS (libs, UI, etc) where i unpacked over CWM my customROM.zip ->
4b) data-partition, where i unpacked google-apps.zip and installed all the apps ->
4c) cache-partition with user data
B) recovery boot (adb reboot recovery):
1) Power ON ->
2) bootloader ->
3) recovery-partition with CWM where i may unpack all the .zip stuff to proper partitions, or restore from sdcard, etc.
Is this correct? I wonder, because i didn't installed CWM into recovery-partition. It cames from install of CM10 (fastboot -i 0xfce flash boot boot.img), so it must be in boot-partition and not in recovery?
So, next confusion: i looked up to /proc/mtd and i don't see neither boot nor recovery partition here:
# cat /proc/mtd
dev: size erasesize name
mtd0: 19000000 00040000 "system"
mtd1: 00600000 00040000 "appslog"
mtd2: 06580000 00040000 "cache"
mtd3: 1a400000 00040000 "userdata"
Click to expand...
Click to collapse
I did a backup with CWM and loocked the data. There aren't boot, and recovery backups:
# ls -lha /sdcard/clockworkmod/backup/2012-10-04.18.49.55/
d---rwxr-x 2 system sdcard_r 4.0K Oct 4 18:56 .
d---rwxr-x 3 system sdcard_r 4.0K Oct 4 18:49 ..
----rwxr-x 1 system sdcard_r 1.6K Oct 4 18:54 .android_secure.vfat.dup
----rwxr-x 1 system sdcard_r 54.6M Oct 4 18:55 cache.yaffs2.img
----rwxr-x 1 system sdcard_r 360.2M Oct 4 18:53 data.yaffs2.img
----rwxr-x 1 system sdcard_r 212 Oct 4 18:56 nandroid.md5
----rwxr-x 1 system sdcard_r 214.6M Oct 4 18:51 system.yaffs2.img
#
Click to expand...
Click to collapse
So, i think i didn't understand the boot sequence and partition schema corectly. May you give me a eye opener, what is here wrong?
TIA!
w7
wolke7 said:
So, next confusion: i looked up to /proc/mtd and i don't see neither boot nor recovery partition here:
[...]
Click to expand...
Click to collapse
The partitions in /proc/mtd only contains the NAND partitions the bootloader chooses to expose to the kernel. The bootloader may know about others as well, but don't include them in the ATAGs partition list booting the linux kernel. Partitions of a NAND flash is not defined in a partition table in the device itself as for a block device (e.g. MMC).
kuisma said:
The partitions in /proc/mtd only contains the NAND partitions the bootloader chooses to expose for the kernel. The bootloader may know about others as well, but don't include them in the ATAGs partition list booting the linux kernel. Partitions of a NAND flash is not defined in a partition table in the device itself as for a block device (e.g. MMC).
Click to expand...
Click to collapse
OK I see... but...how to backup my boot and recovery partition if those aren't accessible from OS? CWM takes only system, data and cache partition...
Thanks
w7
I have a specific situation I'm hoping
someone can shed some light on. I'm making a nanddump of the userdata
partition on a nexus one with the below commands using two Cygwin
terminals. But, when I do this, the nanddump seems to go on forever. I
ended up stopping it at over 8 GB written. I believe the entire
internal storage is only something like 512 MB. The form of the below
commands seemed to work for creating nanddumps of the other phone
partitions. But, it's the userdata partition I'm really looking to get
so as to potentially recover some important deleted files. Also, note
that I have removed the external sd card so that there's no
possibility I'm copying from that.
Cygwin Terminal 1
---------------------------
adb forward tcp:5555 tcp:5555
adb shell
su
# nanddump [options] /dev/mtd/mtd5 | nc -l -p 5555
-------------------------------
Cygwin terminal 2
-----------------------------
nc 127.0.0.1 5555 > /nexus/mtd5_userdata.img
------------------------------
This approach is similar to this, but with nanddump instead of dd:
http://forum.xda-developers.com/showthread.php?t=1994705
In case it's of use, the proc/mtd file shows the following
mtd0: 000e0000 00020000 "misc"
mtd1: 00400000 00020000 "recovery"
mtd2: 00380000 00020000 "boot"
mtd3: 09100000 00020000 "system"
mtd4: 05f00000 00020000 "cache"
mtd5: 0c440000 00020000 "userdata"
Also, the df command in adb shell, brings up the following:
Filesystem Size Used Free Blksize
/dev 192M 32K 192M 4096
/mnt/asec 192M 0K 192M 4096
/mnt/obb 192M 0K 192M 4096
/system 145M 131M 13M 4096
/data 196M 80M 116M 4096
/cache 95M 1M 93M 4096
Although I have likely already lost the files I'm seeking, I hope someone can help, so I can get this flash image and be able to start
using the phone again. Thank you.