Hallo,
i want to backup my NAND (and sd-ext partition) directly to my windows hdd (not to /sdcard/backup). I can do it with 'adb shell dd if=/dev/mtd/mtd0 > boot.img' already but that includes unallocated space as well. Not sure if this is even compatible to CWM.
How is CWM doing it? Going over loop device or something? How can i create compatible CWM img files via adb that only hold allocated data?
First download the leak using my torrent in attachments. You also need s-off and an eng bootloader
1. Extract to wherever you want.
2. Put radio.img, boot.img (rename boot_signed.img to boot.img) and system.img from the extracted zip on to internal or external depending what is the first mountpoint in recovery
3. Reboot to recovery
4a. Use superwipe script or wipe manually
4b. wait for reboot mount sdcard and all partitions in mounts and storage
5. Run these from recovery with your phone plugged in to computer
Code:
adb shell
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/system.img of=/dev/block/mmcblk0p29
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p22
reboot
Note flashing the radio is optional but not necessary to run the rom just allows better service and all that that normally comes with an updated radio
6. Flash superuser package http://androidsu.com/superuser/
7. Boot up and enjoy
This method won't change you're hboot or effect s-off or bootloader status
8. ??????
9. PROFIT!!!!!111!!!1
so this is the method for people without s=off? if so, YAY!
(i dont feel like s=off'ing just yet)
ziggy46 said:
so this is the method for people without s=off? if so, YAY!
(i dont feel like s=off'ing just yet)
Click to expand...
Click to collapse
well then you can't flash the boot.img this way but yes. you would have to fastboot flash boot boot.img just like you normally would
sportsstar89 said:
well then you can't flash the boot.img this way but yes. you would have to fastboot flash boot boot.img just like you normally would
Click to expand...
Click to collapse
do you need an external sd card
EclipzeRemix said:
do you need an external sd card
Click to expand...
Click to collapse
Not if you're using a recovery that mounts the internal
This is only for tmo though right
sportsstar89 said:
Not if you're using a recovery that mounts the internal
Click to expand...
Click to collapse
ok cool
Quick question:
Would fastboot flash boot boot.img, fastboot flash radio radio.img, and fastboot flash system system.img all achieve the same or does it have to be done by dd?
rbaruch said:
This is only for tmo though right
Click to expand...
Click to collapse
unless you have S-OFF and Super CID
Keylogger_0 said:
Quick question:
Would fastboot flash boot boot.img, fastboot flash radio radio.img, and fastboot flash system system.img all achieve the same or does it have to be done by dd?
Click to expand...
Click to collapse
Not as efficient and clean trust me just do it this way
sportsstar89 said:
Not as efficient and clean trust me just do it this way
Click to expand...
Click to collapse
i'm more comfortable doing it over fastboot compared to dd, because i know for a fact that if you mess up dd commands, it will permanently brick the phone. I remember reading where one guy forgot to put a number after the mmcblk0p and it broke the phone
Keylogger_0 said:
i'm more comfortable doing it over fastboot compared to dd, because i know for a fact that if you mess up dd commands, it will permanently brick the phone. I remember reading where one guy forgot to put a number after the mmcblk0p and it broke the phone
Click to expand...
Click to collapse
if thats the way you prefer go for it but im not responsible either way if you brick it
sportsstar89 said:
if thats the way you prefer go for it but im not responsible either way if you brick it
Click to expand...
Click to collapse
I'll just place all of the blame on you xD
Keylogger_0 said:
I'll just place all of the blame on you xD
Click to expand...
Click to collapse
ha it's a common theme when n00bs try to do something then there like my phone won't turn on your broke it lol
i keep on getting
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root>if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
C:\Root>if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root> if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
help
EclipzeRemix said:
i keep on getting
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root>if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
C:\Root>if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root> if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
help
Click to expand...
Click to collapse
you didn't adb shell it's asking windows if in knows a linux command
Omg downloaded in less than a minute with the torrent!
i lost root after flash wtf...
Jetta2_MTL said:
i lost root after flash wtf...
Click to expand...
Click to collapse
Well it's a stock rom so that is to be expected and obviously you did not read the complete tutorial where it tells you to flash su
C:\Root>adb shell
~ # dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd: can't open '/sdcard/radio.img': No such file or directory
~ # dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd: can't open '/sdcard/radio.img': No such file or directory
~ # dd if=/sdcard/system.img of=/dev/block/mmcblk0p29
dd if=/sdcard/system.img of=/dev/block/mmcblk0p29
dd: can't open '/sdcard/system.img': No such file or directory
~ #
-_- help, and i know i put all three files in there and mounted sdcard
hi guys,
I've been a fool and balls up a note 10.1 (n8010).
I've got a 2nd device and was wondering if I could simply do a
Code:
dd if=/dev/block/mmcblk0 of=/extSdCard/image.img
to get a complete image of ALL partitions on the device, then on the broken one do the restore
Code:
dd if=/extSdCard of=/dev/block/mmcblk0
?
Would this keep all partition table information?
I'm assuming it'll crate an exact clone of the 2nd device?
I've already done this for the efs partition as I over wrote it by mistake....
any thoughts?
thanks.
for google...
Yes I managed to fix my device.
From the working one, I opened a adb shell from CWM recovery and ran ls -l /dev/block/platform/{name}/by-name
this gave me a list of partitions and their names.
I then then did a dd (disk dump) of the partitions to a external sd card (had to mount the sd in recovery first). This gave me 7 .img files.
I then moved the sd to the broken device, booted to TRWP recovery and used the terminal to dd them the img files back into their respective partitions.
Long story short, she be working fine now
I recently flashed the Cyanogen monthly from 11/02 (was running Carbon before). It seems to work fine, but there are some oddities I's like to resolve regarding recovery...
When I turn on the Nook from a powered off state, it boots into CWM v5.5.0.4 (I can select "reboot system" and go to Cyanoboot, and then CM)
Once in CM, if I reboot to recovery, it reboots into CWM v6.0.2.5
In Cyanoboot, if I choose "Internal eMMC Recovery", it boots into CWM v6.0.2.5
In Cyanoboot, if I choose "Internal eMMC Alternate", it boots into CWM v6.0.3.7
I'm not sure how I ended up in this state... But I'd like to have it boot into cyanoboot, and then CM, when I power it up. Also, I'd like to get rid of the multiple version of CWM, and just run the latest. Do I need to revert back to stock, then go through the rooting and flashing process? Or is there a way to fix this without starting over?
Thanks!
Did you boot from power-off state with a SD card in the slot? If so, try booting without the SD card to see if the NT still boots into CWM v5.5.0.4; if it does not then CWM v5.5.0.4 is on the card and you can bypass it by renaming a file name MLO in the first partition on the card (thereby making the card non-bootable so that the NT would boot straight onto emmc when you power up).
CWM v6.0.3.7 is likely located in the /bootdata partition on emmc. You can find it by opening a terminal emulator app, then type:
Code:
su
cd /bootdata
ls
and look for a file with name having .img extension.
To get rid of it, use the rm command:
Code:
rm <filename>
Thankyou sir, that did the trick!
Hello everyone, i was S-off, unlocked and rooted few days ago. now my device is hard bricked as i was installing CM12 which was installed successfully after booting to android it was requiring encryption password, to eliminate encryption i head to different thread and followed by formatting one of data partition. after rebooting device went to dead qhusb or QDL mode. tried every trick using linux PblClear/ Brickdetech.sh/ revive.sh nothing is working.
Last hope before sending it to Jtag is pulling mmcblk0 of working device and writing it to ext.sd card. Booting with same written ext Sd card .
If somebody wants to help me or others with same situation trying trial and error approach could help here.
Guide for helpers;
1- Working Droid Inc4g
2- Rooted
3- Terminal installed or Debugging enable
4- Commands
* To View partition Tables
adb shell su -c ls -al /dev/block/
* After Running this you can see this partition mmcblk0 in starting and make sure that the partition is available.
* Backup your Partition
* Pulling in Internal device SDCARD
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/sdcard0/fulldump.img
or
* Pulling in Internal device External SDCARD
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/sdcard1/fulldump.img
(Chances are mmcblk0 is in GB external Sdcard approch is more reliable with few GBs free space)
5- Connect your device to PC and find fulldump.img
6- Zip/winrar archive
7- Upload to popular cloud (Mega/Google Drive)
8- Share the link
For those with similar brick and if they can get mmcblk0.img(fulldump.img) mentioned above then;
Use win32Diskimager and write full mmcblk0(fulldump.img) to External SD card of 8/16 GB.
Place the ext Sdcard in device and boot to bootloader by holding Power + Vol Down.
try your luck, if booted from dead state try to restore fresh firmware or previous good known backup if you have one.