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?
Related
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...
Venue Rooting Android 2.2 & 2.3.3 In Under 2 Min, Backup ROM, Udating to Gingerbread
DISCLAIMER
Do this at your own risk. Always have a backup. If you Break your phone, don't blame me. There is a chance that your Andriod device will be made into a paper weight. This post is my adventures of my phone and if you follow do so at your own risk.
Requirements:
Dell Venue:
My dell was oem unlocked, so it should be region 00
Oem Ver: GTOUB1A130730
Baseband Ver: GTOUB1A130730-AWS
Quick Root instructions:
1: Enable Debug USB
2: Download SuperOneClickv1.5.4-ShortFuse to your desktop
3: Download Fastboot with ADB to your c:\ Drive
3: Open SuperOneClick as Administrator under the dir Win32
4: Click "Shell Root" in the GUI of SuperOneClick, then wait untill a popup says "Reboot to remove Superuser" Click "OK"
5: Go to the Fastboot with ADB Dir using Windows Command Prompt.
6: Type: adb shell (You should see # insted of $)
You should have temp root until you reboot the device.
Permanent root instructions: (Optional)
(Get the system mtd path)
Type: cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00600000 00020000 "recovery"
mtd2: 00600000 00020000 "recovery_bak"
mtd3: 00040000 00020000 "LogFilter"
mtd4: 00300000 00020000 "oem_log"
mtd5: 10400000 00020000 "system"
mtd6: 22600000 00020000 "userdata"
mtd7: 06600000 00020000 "cache"
(do the following as root, #)
1: Type: mount -t rfs -o remount,rw /dev/block/mtd5 /system
2: Type: cd /system/xbin
3: Type: cat /system/bin/su > su
4: Type: chmod 4755 su
5: Type: exit
6: Type: adb install Superuser.apk (Only do this if missing from device)
7: Test, Reboot, GoTo ADB Win dir
Type: adb shell (you should see $) Type: Su (Push Yes When your Android App SuperUser asks you to accept)
Backup Android ROM:
Type: cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00600000 00020000 "recovery"
mtd2: 00600000 00020000 "recovery_bak"
mtd3: 00040000 00020000 "LogFilter"
mtd4: 00300000 00020000 "oem_log"
mtd5: 10400000 00020000 "system"
mtd6: 22600000 00020000 "userdata"
mtd7: 06600000 00020000 "cache"
(do the following as root, #)
Type: cat /dev/mtd/mtd0 > /sdcard/boot.img
Type: cat /dev/mtd/mtd1 > /sdcard/recovery.img
Type: cat /dev/mtd/mtd2 > /sdcard/recovery_bak.img
Type: cat /dev/mtd/mtd3 > /sdcard/LogFilter.img
Type: cat /dev/mtd/mtd4 > /sdcard/oem_log.img
Type: cat /dev/mtd/mtd5 > /sdcard/system.img
Type: cat /dev/mtd/mtd6 > /sdcard/userdata.img
Type: cat /dev/mtd/mtd7 > /sdcard/cache.img
Type: exit
Type: adb pull /sdcard/boot.img
Type: adb pull /sdcard/recovery.img
Type: adb pull /sdcard/recovery_bak.img
Type: adb pull /sdcard/LogFilter.img
Type: adb pull /sdcard/oem_log.img
Type: adb pull /sdcard/system.img
Type: adb pull /sdcard/userdata.img
Type: adb pull /sdcard/cache.img
Udating to Android 2.3.3 Gingerbread:
Be warned, remember to backup your phone before these next septs.
1. Goto the dell venue wiki (http://forum.xda-developers.com/wiki/Dell_Venue) and download these 2 files from Version 408
a. Thunder_408_20707_14.pkg
b. recovery.img (make sure its the version 408)
2. Download Thunder_408_20707_14.pkg and rename it update.pkg
3. type: adb push update.pkg /sdcard/update.pkg
4. Reboot and go into fastboot recovery, conect the usb and you should see yellow fastboot recovery mode 2
5. type: fastboot flash recovery recovery.img (remember this is version 408)
6. Reboot and enter recovery mode, there you should see an option (update using update.pkg), select it with the camera button
You should see another screen in blue saying doing emergency update..................
Your phone will reboot and another update screen will appear saying Updating..... and a Android logo animation
Your phone should reboot one last time this time slowly be patient and you should see Android 2.3.3 Gingerbread welcome screen.
Rooting Android 2.3.3 Gingerbread:
1. Download Superuser.zip and rename it to update.zip (http://mirror2.streakdroid.com/manii/Tools/Superuser.zip)
2. Download ClockWorkMod rename it to recovery.img (http://mirror2.streakdroid.com/manii/misc/ClockWorkMod/V-5.5.0.4.img)
3. Type: adb push update.zip /sdcard/update.zip
4. Remember to remove update.pkg from /sdcard/update.pkg
5. Reboot to Fastboot_Mode 2 again
6. Type: fastboot flash recovery recovery.img (remember this is ClockWorkMod)
7. Reboot into recovery mode and select "update.pkg" option again to go into Rom Manager
8. Once in Rom Manager select (update.zip) option
You should see Rom Manager saying "update completed you have root now".
9. Reboot and test with adb shell with the command su.
10. Upon reboot Rom Manager will be remove and 408 recovery.img will be on your system.
DO NOT INSTALL "Rom Mamager" AGAIN ON 2.33, BACKUP DOES NOT WORK AND FILLS YOUR /CACHE/RECOVERY/ WITH LOG FILES
thx share,but this not work on 2.3 rom
Thank You
Best easy way....use gingerbreak.apk...frm ur cell only u cn root ur phn
Sent from my Dell Venue using xda premium
1. Goto the dell venue wiki (http://forum.xda-developers.com/wiki/Dell_Venue) and download these 2 files from Version 408
a. Thunder_408_20707_14.pkg
b. recovery.img (make sure its the version 408)
2. Download Thunder_408_20707_14.pkg and rename it update.pkg
3. type: adb push update.pkg /sdcard/update.pkg
4. Reboot and go into fastboot recovery, conect the usb and you should see yellow fastboot recovery mode 2
5. type: fastboot flash recovery recovery.img (remember this is version 408)
6. Reboot and enter recovery mode, there you should see an option (update using update.pkg), select it with the camera button
You should see another screen in blue saying doing emergency update..................
Your phone will reboot and another update screen will appear saying Updating..... and a Android logo animation
Your phone should reboot one last time this time slowly be patient and you should see Android 2.3.3 Gingerbread welcome screen.
3. type: adb push update.pkg /sdcard/update.pkg where i type ?? have tool ?? i used windows 7
thank
masirvan said:
1. Goto the dell venue wiki (http://forum.xda-developers.com/wiki/Dell_Venue) and download these 2 files from Version 408
a. Thunder_408_20707_14.pkg
b. recovery.img (make sure its the version 408)
2. Download Thunder_408_20707_14.pkg and rename it update.pkg
3. type: adb push update.pkg /sdcard/update.pkg
4. Reboot and go into fastboot recovery, conect the usb and you should see yellow fastboot recovery mode 2
5. type: fastboot flash recovery recovery.img (remember this is version 408)
6. Reboot and enter recovery mode, there you should see an option (update using update.pkg), select it with the camera button
You should see another screen in blue saying doing emergency update..................
Your phone will reboot and another update screen will appear saying Updating..... and a Android logo animation
Your phone should reboot one last time this time slowly be patient and you should see Android 2.3.3 Gingerbread welcome screen.
3. type: adb push update.pkg /sdcard/update.pkg where i type ?? have tool ?? i used windows 7
thank
Click to expand...
Click to collapse
Follow this thread:
Link
Its for downgrade , but you can upgrade in similar manner
I have one big problem after update to 2.3.3(408):
I can't run USSD codes on my device. This is very annoying - I can't chcek value of my account, put money into account and many others...
checking of IMEI is working...
Re: Venue Rooting Android 2.2 & 2.3.3 In Under 2 Min, Backup ROM, Udating to Gingerbr
Tomaszu87 said:
I have one big problem after update to 2.3.3(408):
I can't run USSD codes on my device. This is very annoying - I can't chcek value id my account, put money into account and many others...
checking of IMEI is working...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1558331
Flash this file using CWM or TWRP
USSD codes will work
Sent from my Dell Venue using xda app-developers app
terminal17 said:
Flash this file using CWM or TWRP
Click to expand...
Click to collapse
Thanks for your reply!
One more question: Where can I get CWM in proper version - all of the links on forum are dead or are for the devices, not fot PC...
Re: Venue Rooting Android 2.2 & 2.3.3 In Under 2 Min, Backup ROM, Udating to Gingerbr
I don't know for pc...but they are available only for fones in this forum...chk for dell venue CWM Or TWRP
Sent from my Dell Venue using xda app-developers app
terminal17 said:
I don't know for pc...but they are available only for fones in this forum...chk for dell venue CWM Or TWRP
Click to expand...
Click to collapse
Everything well done!
My earlier questions born of my low level of knowledge on android.
Read a lot of posts, users answers and everything becomes easier...
Thanks XDA!
Hi, I have unlocked the bootloader and had used CWM (recoveryNeo.img). Too bad it is a one-time boot. I was thinking is there a recovery partition.
Code:
# cat /proc/mtd/
dev: size erasesize name
mtd0: 19000000 00020000 "system"
mtd1: 00600000 00020000 "appslog"
mtd2: 06580000 00020000 "cache"
mtd3: 1a400000 00020000 "userdata"
So is there a way to install CWM other than to the system partition? Or I would need to do a fastboot every time I need it?
Mine is a Neo V, but doesn't matter
Use flashtool. Flash kernel boot.img with build-in CWM. Try NightElf kernel.
Try to install this CWM install.RAR
Hey!
Try NightElf's kernel it haves built in cwm
Just put boot.img (boot.img = kernel you downlaoded) into fastboot folder and hold shift and rightclick and "open... here" on command prompt type "fastboot flash boot boot.img" and you have permanent cwm
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.
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.