It is a wise idea to backup the /pds partition of your Atrix. It is /dev/block/mmcblk0p3. It holds very important information unique to the phone, like the wifi and bluetooth mac addresses. We still don't fully understand it, but it can resolve issues with the touchscreen not taking input properly. This has happened to a number of people, and now that everyone can have the unlock, I am sure people will do things that will cause the same problem.
Steps:
1. Pick your favorite method: adb, ssh, terminal emulator, etc
2. Become root if not already, REQUIRED
3. dd if=/dev/block/mmcblk0p3 of=/tmp/pds.img
4. Pick your favorite method to get the file off the phone: scp, sd card, etc
The file should be about 2mb. Keep it in a safe place.
edgan said:
It is a wise idea to backup the /pds partition of your Atrix. It is /dev/block/mmcblk0p3. It holds very important information unique to the phone. We still don't fully understand it, but it can resolve issues with the touchscreen not taking input properly. This has happened to a number of people, and now that everyone can have the unlock, I am sure people will do things that will cause the same problem.
Steps:
1. Pick your favorite method: adb, ssh, terminal emulator, etc
2. Become root if not already, REQUIRED
3. dd if=/dev/block/mmcblk0p3 of=/tmp/pds.img
4. Pick your favorite method to get the file off the phone: scp, sd card, etc
The file should be about 2mb. Keep it in a safe place.
Click to expand...
Click to collapse
Everyone can't have the Unlock... Bell is denied for now.
This is sweet though. Thanks for the tip.
Can Root Explorer be used to do this?
no pds is mounted but root exp sees an empty partition, btw would be possible to know which files exactly are in the directory?
me and others messed up this partition using tenfar's recovery, now we have problem with temp throttling, i guess (cpu reaches only 50% of max freq)
Once you go through steps 1 to 3, you can go to /tmp in root explorer and copy pds.img file to sdcard or wherever you want to copy the pds file
Uhhh, is this still possible to back up after unlocking and flashing the 2.3.4 build?
Sent from my MB860 using XDA App
neer2005 said:
Uhhh, is this still possible to back up after unlocking and I flashing the 2.3.4 build?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I don't see any reason why you wouldn't be able to.
Screwed up my PDS on my old Atrix. Made sure to immediately back mine up when I got a new one too lol
Backed up the pds file to my ext-sd card using adb shell and got a 2.00mb file. Is this right?
Thanks for the info!
yes
now share it
Thanks I just make a backup image... but how do you restore it?
dd if=/tmp/pds.img of=/dev/block/mmcblk0p3
edgan said:
It is a wise idea to backup the /pds partition of your Atrix. It is /dev/block/mmcblk0p3. It holds very important information unique to the phone. We still don't fully understand it, but it can resolve issues with the touchscreen not taking input properly. This has happened to a number of people, and now that everyone can have the unlock, I am sure people will do things that will cause the same problem.
Steps:
1. Pick your favorite method: adb, ssh, terminal emulator, etc
2. Become root if not already, REQUIRED
3. dd if=/dev/block/mmcblk0p3 of=/tmp/pds.img
4. Pick your favorite method to get the file off the phone: scp, sd card, etc
The file should be about 2mb. Keep it in a safe place.
Click to expand...
Click to collapse
i cant seem to find the file once i created it!
ok, seems simple enough, but stupid question... can someone explain the commands "dd=" and "of=".
I was able to see the file @ dev/block with winscp but how do I convert it to a .img file, etc.
Thanks for your help.
samcripp said:
i cant seem to find the file once i created it!
Click to expand...
Click to collapse
It's in /tmp.
I suggest people use this command:
*MicroSD Installed*
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
*No MicroSD Installed*
dd if=/dev/block/mmcblk0p3 of=/sdcard/pds.img
These commands will create the pds.img file in the root directory of your MicroSD or your Internal SD card respectively.
What is pdf partition?
I believe and if I am wrong I am sure someone will correct me but
dd = I'm not sure
if = input file
of = output file
dd essentially takes a disk and copies it.
Sent from my MB860 using Tapatalk
Not to sound newbish, but I am, I keep getting Cannot Open for Read: Permission Denied
Could someone assist? Thanks.
Realized:
SU is what I needed to type, methinks...will try.
Worked:
Yeah, once I put SU and got that done, it worked out.
_Dennis_ said:
I believe and if I am wrong I am sure someone will correct me but
dd = I'm not sure
if = input file
of = output file
dd essentially takes a disk and copies it.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
From Wikipedia: "dd is a common Unix program whose primary purpose is the low-level copying and conversion of raw data............. dd can also be used to copy regions of raw device files, e.g. backing up the boot sector of a hard disk, or to read fixed amounts of data from special files like /dev/zero or /dev/random.[4]"
So, I am a n00b on using adb (etc..) so I will explain the way I did it using adb.
1. Make sure you have adb.exe installed on your computer and connect the phone to the computer. (I got my adb.exe from the Gladroot script. Here is a link: http://goo.gl/jHiJc)
2. Open a command window
3. Browse to the directory where the adb.exe is and type the following (press enter after each line):
adb shell
su
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
Now, if you DON'T have a SDcard in your phone, take out the "-ext" from that last line.
The file (pds.img) should now be in either the internal sdcard or on your physical sdcard, as nexxusty described.
I hope that helps some as it took me a while to learn this.
Sorry if this is too noob for some, but I started from zero knowledge of this
garekinokami said:
Not to sound newbish, but I am, I keep getting Cannot Open for Read: Permission Denied
Could someone assist? Thanks.
Click to expand...
Click to collapse
Only thing I can think of is if you didn't give ADB superuser permission. You have to physically click allow on the phone after you type "su". Could that be it?
wirednix said:
Only thing I can think of is if you didn't give ADB superuser permission. You have to physically click allow on the phone after you type "su". Could that be it?
Click to expand...
Click to collapse
Lol Yes. 10 Char.
Aye I know what it IS....not what dd MEANS lol. Thank you for the guide.....I completed this in terminal emulator.
Related
I bought my own nook color on saturday, there doesn't appear to be a factory image that can be restored. My new nook color came with version 1.01 preinstalled. Before turning it on the first time I put in nookie froyo and did a dd of all 8 of the stock partitions. Below is the zipped up .img files of mmcblk0p1/mmcblk0p5 (boot/system) from a stock untouched 1.01 nook color. I am also including the factory.zip. This should be enough to restore a bricked nook color with a corrupted boot or system partition. Many people have been able to restore to stock by just using the boot.img because after 8 failed boots it will do a factory reset.
To make this work you must have ADB working first. You may be able to get this to work on ADB Wireless, but I don't recommend it. For instructions on getting adb to work with the nook color go here:
http://nookdevs.com/NookColor_USB_ADB
To use these files unzip them to the sdcard portion of a nookie froyo sdcard, or just about any other rom that runs from the sdcard and run the following commands in an adb shell:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Boot
System
factory.zip
Thanks, you're a life saver!
samuelhalff said:
Thanks, you're a life saver!
Click to expand...
Click to collapse
Did it fix you samuelhalff?
Yes. But I only used boot.img. Then restored to stock with 8 failed boots. Dd'ing system will also work.
If it dosen't boot, do a factory reset with power+n.
Sent from my HTC Desire using XDA App
So if I put the factory.zip on /dev/mmcblk0p3 and replace the current one, when we do the 8 bad boot trigger we would get 1.0.1 flashed instead of 1.0.0 right?
Yes. And I would also do a power+n reset at the end, to avoid any problems.
Sent from my HTC Desire using XDA App
shad0wf0x,
I am having the same problem with my NC not booting after a failed attempt at
re-rooting. I will tell you in advance that I am VERY tech-phobic and don't comprehend all this command-line stuff well at all.
Given your original post above, could you please explain in layman's terms EXACTLY what steps to take to restore my NC to like-new? And hopefully it can be done with just simply putting some files on a micro SD and that's it. Please let me know from start to finish how I do this. Appreciate your help in advance.
vigeh4
P.S. I know I had no business doing this, but I screwed my unit up anyway. I already tried the 8-step interrupt thing before re-rooting but with no success.
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
shad0wf0x said:
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
Sorry, I am WAY confused about how to do this. This adb crap is over my head.
Maybe I just have a $250 paperweight at this point. If I mail you my NC, would you reset to "factory" for a small fee?
Thanks.
OMFG, thank you very much for these files and instructions.
I really thought I bricked it to the point of no return. I initially screwed it up when I installed Clockwork and wouldn't boot past "N", then after tinkering around some more, it wouldn't even turn on ... lol.
@vigeh
First you need to unzip those files you just downloaded. Second, you need to copy the "boot.img" and "system.img" (not the *.zip) to the "/SDCARD" folder on your SDCARD. I had to use WIFI FILE Explorer in Nookie Froyo cuz I messed up my nook so bad, i couldn't copy these files by turning on the USB Storage through the regular method. It took me days to figure this out cuz i'm kinda slow.
I hope you installed the Android-SDK on your computer already. If so, then go to the folder named "\platform-tools" on your PC - this is where ADB.EXE is located. Connect your nook and type "ADB DEVICES" just to make sure your nook is connected to the computer. It'll show up and tell you it is or not. If it is connected then do the following:
1. Type "ADB SHELL" then you'll see a "#" symbol after you hit enter.
2. Type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1" just the way it is written by the original poster (minus the "" marks)
at this point, it usually wont say anything. Just wait a few minutes and something will pop up. In my case, it says:
"477033984 bytes <454.9MB> copied, 138.757660 seconds, 3.3MB/s"
"#"
3. Type the second command next to the "#" sign "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
wait another few minutes til the next confirmation pops up.
4. turn off nook, remove SD card
5. Hold the N button and the Power button at the same time and it'll ask you to reset the nook to factory settings.
I hope this helps you ....
well im a tard... i did this without reading that YOU CANNOT HAVE GOOGLE APPS!!!! so anyway Im trying to get back to a stock image, but i cant figure out how to copy 700 med +/- of images to 134 meg f free space. someone un-tard me plz . thanks
I have ClockworkMod Recovery installed, and if I put the factory.zip you provided on my sd card and use the option 'install zip from sdcard' will that in fact install factory settings on the nook?
I tried to do the 8 failed boots, but cannot get it to work with this installed.
shad0wf0x said:
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
How do you get to your "working adb?" I'm probably even more ignorant on this SDK stuff that vigeh4. I have SDK installed though.
How to get adb working is found here:
http://nookdevs.com/NookColor_USB_ADB
gconol said:
@vigeh
First you need to unzip those files you just downloaded. Second, you need to copy the "boot.img" and "system.img" (not the *.zip) to the "/SDCARD" folder on your SDCARD. I had to use WIFI FILE Explorer in Nookie Froyo cuz I messed up my nook so bad, i couldn't copy these files by turning on the USB Storage through the regular method. It took me days to figure this out cuz i'm kinda slow.
I hope you installed the Android-SDK on your computer already. If so, then go to the folder named "\platform-tools" on your PC - this is where ADB.EXE is located. Connect your nook and type "ADB DEVICES" just to make sure your nook is connected to the computer. It'll show up and tell you it is or not. If it is connected then do the following:
1. Type "ADB SHELL" then you'll see a "#" symbol after you hit enter.
2. Type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1" just the way it is written by the original poster (minus the "" marks)
at this point, it usually wont say anything. Just wait a few minutes and something will pop up. In my case, it says:
"477033984 bytes <454.9MB> copied, 138.757660 seconds, 3.3MB/s"
"#"
3. Type the second command next to the "#" sign "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
wait another few minutes til the next confirmation pops up.
4. turn off nook, remove SD card
5. Hold the N button and the Power button at the same time and it'll ask you to reset the nook to factory settings.
I hope this helps you ....
Click to expand...
Click to collapse
Thanks to Shadowf0x for getting ABD to work
I have a question though, if I dont have the file "SDCARD" in my SD card then can I just make a new file and name it SDCARD, and put both of the .img's into it?
Sir a teema said:
I have ClockworkMod Recovery installed, and if I put the factory.zip you provided on my sd card and use the option 'install zip from sdcard' will that in fact install factory settings on the nook?
I tried to do the 8 failed boots, but cannot get it to work with this installed.
Click to expand...
Click to collapse
I'm not sure if that will work, I guess it's worth a try, however if you replace the existing factory.zip and do a factory reset you will restore back to 1.01 instead of 1.0 if you don't already have a nc that has 1.01 on it. I saw another thread about trying to use the factory.zip with cwm, but I didn't see anyone coming back and say it worked. How to flash back to stock is found here:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
mmaner said:
well im a tard... i did this without reading that YOU CANNOT HAVE GOOGLE APPS!!!! so anyway Im trying to get back to a stock image, but i cant figure out how to copy 700 med +/- of images to 134 meg f free space. someone un-tard me plz . thanks
Click to expand...
Click to collapse
The nookie froyo sdcard partition for me was 900+m, and I've heard that all you need to do for this to work is to flash the boot.img.
Ign3nt said:
Thanks to Shadowf0x for getting ABD to work
I have a question though, if I dont have the file "SDCARD" in my SD card then can I just make a new file and name it SDCARD, and put both of the .img's into it?
Click to expand...
Click to collapse
You could try to mount the media partition in nookie froyo and put them there.
The partition is /dev/block/mmcblk0p8 and type is vfat.
shad0wf0x said:
The nookie froyo sdcard partition for me was 900+m, and I've heard that all you need to do for this to work is to flash the boot.img.
Click to expand...
Click to collapse
Ill try it tonight. thanks
I saw a thread on the international S2 forum regarding the importance of backing up the /efs folder on the phone so you don't lose the phones imei. I was wondering if this is still a necessity on our phone as well? And if so is there a different process to do it than what they used? They used terminal commands to back it up using terminal Emulator or ADB.
This is the thread:
http://forum.xda-developers.com/showthread.php?t=1068193
Its very important..ask me..i lost my IMEI and dint have a back up of the efs folder..had to go to the store and get a new phone under warranty.
Please make a backup of it.
After 2 months, someone just had EFS corruption last week - so yes, now I think it's a good idea to back it up.
IMO it would be a good idea to image the partition too...
Entropy512 said:
IMO it would be a good idea to image the partition too...
Click to expand...
Click to collapse
Can you verify the partition? Is 0p3 the right one, or is it 0p1? I coundn't find a definitive answer by searching.
For some reason I thought it was p3, but I was wrong. It's p1:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
To back it up, get ADB working, and run the following using ADB while the phone is in CWM recovery and /sdcard is mounted (It often is not when you first enter CWM, mount it in the Mounts and Storage menu if it is not) (If you do this when the phone is running, you may back it up as it is getting written to, which could result in a bogus backup)
Code:
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/efs_backup.img
Thanks for the verification entropy!
Sent from my SAMSUNG-SGH-I777 using XDA App
Entropy512 said:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
Click to expand...
Click to collapse
I don't know much about linux commands. Is this how you verified the partition?
Also, am I correct in assuming that if the partition is backed up, it would not be necessary to back up the efs directory using a file explorer? Or is there a reason to have both?
You can also run the command from entropy in terminal emulator on your phone. Do su first to get root and enter the dd command to do your backup.
Sent from my SGH-I777
creepyncrawly said:
I don't know much about linux commands. Is this how you verified the partition?
Also, am I correct in assuming that if the partition is backed up, it would not be necessary to back up the efs directory using a file explorer? Or is there a reason to have both?
Click to expand...
Click to collapse
I verified it by executing the following command and looking at the output:
Code:
mount
It may be easier to restore a folder backup - not sure. A partition backup is the best way to guarantee you got EVERYTHING in that partition, byte-for-byte.
That's crazy. Cause I don't understand how you learn stuff like that but thanks(aka I'm gonna go do this since I mess with my phone alot.) I followed amk28's troubles. What's the difference between efs backup pro and this mehod? They both backup images
Entropy512 said:
For some reason I thought it was p3, but I was wrong. It's p1:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
To back it up, get ADB working, and run the following using ADB while the phone is in CWM recovery and /sdcard is mounted (It often is not when you first enter CWM, mount it in the Mounts and Storage menu if it is not) (If you do this when the phone is running, you may back it up as it is getting written to, which could result in a bogus backup)
Code:
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/efs_backup.img
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I777 using XDA App
Here is a complete guide for anyone interested in rooting the HTC Droid DNA. The insecure boot image, TWRP recovery, CWM recovery and SuperSU files used in this guide are not my own developments, and their developers have been credited in the end of this post.
I am only writing this as a newbie-friendly guide for everyone, and am providing my own SuperSU, su and busybox installer zip file that includes everything you need for full root.
Unlock the bootloader of your device by visiting the HTC bootloader unlock page. Warning: This will wipe your data.
UPDATE: Thanks to Verizon, the official bootloader unlocking method mentioned above no longer works. Please refer to this method for unlocking the bootloader.
Download ClockworkMod or TWRP recovery for the device and rename it to recovery.img (or keep the existing name and change recovery.img in the command below to that name).
Download the SuperSU and busybox package and put it on your SD card.
Put your phone into bootloader mode and connect it to your PC via USB.
On your computer, make sure you are in the folder where you downloaded the recovery file and use this command to flash the recovery:
Code:
fastboot flash recovery recovery.img
Finally, reboot your device into recovery, flash the SuperSU and busybox package and reboot your device.
You should now have root access.
Credits:
jcase for unlocking the bootloader after Verizon decided to lock it.
dsb9938 for sharing the CWM port and correcting me regarding my previously posted and now removed second method involving his insecure boot image
Dees_Troy for TWRP recovery.
utkanos for CWM port.
Chainfire for developing SuperSU
I have tried to credit everyone involved but if I have missed out on anyone, please do let me know.
thanks for the guide!
just one question though. when you say "Download the SuperSU and busybox package and put it on your SD card.", what do you mean exactly by SD card? doesn't the DNA not have a SD card? sorry if this is a dumb question. i've never rooted a phone before :/
hotmonkas said:
thanks for the guide!
just one question though. when you say "Download the SuperSU and busybox package and put it on your SD card.", what do you mean exactly by SD card? doesn't the DNA not have a SD card? sorry if this is a dumb question. i've never rooted a phone before :/
Click to expand...
Click to collapse
Internal storage would be another name for the SD card.
touretts69 said:
Internal storage would be another name for the SD card.
Click to expand...
Click to collapse
ah okay, thank you
which device do u use on the htc page?
nyjw said:
which device do u use on the htc page?
Click to expand...
Click to collapse
"Other devices", or similar.
Sent from my ADR6425LVW using xda premium
Awesomeness.
The fact that this phone is rooted a week before its even out... simply awesome. I love XDA!
So excited for this phone.
HQRaja said:
Code:
adb shell mount -o remount,rw /system
[LIST=1]
[*] adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
[*]Reboot your device.
[/LIST]
Click to expand...
Click to collapse
This will not work. You cannot write to /system except in recovery.
This is why I did not publish my initial root method. Using a package and flashing in recovery is the only way to get files on /system without some really gnarly stuff.
D
.
dsb9938 said:
This will not work. You cannot write to /system except in recovery.
This is why I did not publish my initial root method. Using a package and flashing in recovery is the only way to get files on /system without some really gnarly stuff.
D
.
Click to expand...
Click to collapse
Thanks for your response. =)
Based on my understanding (and my experience with Nexus devices), once you boot using an insecure boot image, you have full root access in ADB since it is running adbd as root on the device. You can then successfully write to the /system partition and the changes persist after reboot. While I can confirm that the above will work on any Nexus device as well as any similar device with an unlocked bootloader and fastboot access, I am not 100% sure if that's how it works on HTC devices that have the S-ON flag. Are you referring to S-ON devices in particular here?
HQRaja said:
Thanks for your response. =)
Based on my understanding (and my experience with Nexus devices), once you boot using an insecure boot image, you have full root access in ADB since it is running adbd as root on the device. You can then successfully write to the /system partition and the changes persist after reboot. While I can confirm that the above will work on any Nexus device as well as any similar device with an unlocked bootloader and fastboot access, I am not 100% sure if that's how it works on HTC devices that have the S-ON flag. Are you referring to S-ON devices in particular here?
Click to expand...
Click to collapse
Normally it does work that way. And I was very disappointed that it did not on this phone, as I made the kernel just for that reason.
I think there was an error in the coding where it tells unlock which partitions to remove write protection from. That, or they just wanna make our lives hard for some reason.
Either way, you cannot write to /system while the phone is booted normally without S-Off. Even as root.
D
.
dsb9938 said:
Normally it does work that way. And I was very disappointed that it did not on this phone, as I made the kernel just for that reason.
I think there was an error in the coding where it tells unlock which partitions to remove write protection from. That, or they just wanna make our lives hard for some reason.
Either way, you cannot write to /system while the phone is booted normally without S-Off. Even as root.
D
.
Click to expand...
Click to collapse
Ah I see. Thanks for pointing that out. I'll remove the second method from my guide, since including that would be pointless if that's the case as you can now confirm.
So does this method work? Or not???Im confused with the last few posts. Thanks
suzook said:
So does this method work? Or not???Im confused with the last few posts. Thanks
Click to expand...
Click to collapse
Edited post is fine. He removed the part I was talking about.
D
.
What I want to know most if anyone knows..will the DNA through verizon be unlockable....I'm actually using the RAZR Maxx hd through verizon and Motorola has restricted unlocking the bootloader because of verizon
Sent from my DROID RAZR HD using xda app-developers app
Irish65 said:
What I want to know most if anyone knows..will the DNA through verizon be unlockable....I'm actually using the RAZR Maxx hd through verizon and Motorola has restricted unlocking the bootloader because of verizon
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
You can't do any of this stuff without unlocking.
As of right now, it is working.
D
.
How do you do the command in the folder were u downloaded to like the instructions say?
idle0095 said:
How do you do the command in the folder were u downloaded to like the instructions say?
Click to expand...
Click to collapse
Please be more specific.
D
.
idle0095 said:
How do you do the command in the folder were u downloaded to like the instructions say?
Click to expand...
Click to collapse
In command prompt, use the "cd" command. The easiest way to do this is to make a folder at the root of your hard drive (C:\) and place all files you need to flash in here e.g. "C:\android\" Then in command prompt, type in "cd .." and press enter until it displays "C:\". Then type (if you use the same name as the example) "cd android" and it will enter the folder "C:\android\" where you placed the files. Now you can continue with the rest of the guide.
CastleBravo said:
In command prompt, use the "cd" command. The easiest way to do this is to make a folder at the root of your hard drive (C:\) and place all files you need to flash in here e.g. "C:\android\" Then in command prompt, type in "cd .." and press enter until it displays "C:\". Then type (if you use the same name as the example) "cd android" and it will enter the folder "C:\android\" where you placed the files. Now you can continue with the rest of the guide.
Click to expand...
Click to collapse
Or if on Windows, simply: Do the following in folder where files are located.
Shift+Right-Click > Open Command Window Here
I've never had an HTC device before but does using the HTC bootloader unlock is that making it s-off? Also I don't see the DROID dna on the list
Sent from my SCH-I535 using xda premium
I've tried using twrp and cwm to backup my system image but i havent been able to, with twrp i had system.ext4.win when i backed up only the system. Is their a tool or do i need to do it with adb ?
Thanks!
could you specify your phone/tablet model?
fantamedo said:
could you specify your phone/tablet model?
Click to expand...
Click to collapse
Galaxy s3
First make a full nandroid backup in CWMR, then on your phone navigate to mint/sdcard/clockworkmod then copy the folder of the backup you made (It should be the date of the backup by default) and transfer it to your computer. Once you transfer it to your computer open the backup folder and inside should be the system.img file.
You can also type these commands in terminal emulator to get your system.img:
Code:
su
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/system.img bs=4096
Then just transfer the system.img from your sdcard to your computer. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
It didn't work with cwmr but I haven't tried out the terminal command
Sent from my SCH-I535 using xda premium
CovXX said:
It didn't work with cwmr but I haven't tried out the terminal command
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Like I said try out the terminal command I suggested and let me know how it goes .
Sent from my SCH-I535 using xda premium
shimp208 said:
First make a full nandroid backup in CWMR, then on your phone navigate to mint/sdcard/clockworkmod then copy the folder of the backup you made (It should be the date of the backup by default) and transfer it to your computer. Once you transfer it to your computer open the backup folder and inside should be the system.img file.
You can also type these commands in terminal emulator to get your system.img:
Code:
su
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/system.img bs=4096
Then just transfer the system.img from your sdcard to your computer. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
thanks man, just the command i was looking for, and it works like a charm.. :good:
So how about for a Razr M XT907 ? I ran the term command, but the img size was wayyy too small.
Find out what your system partition is and change command accordingly
Sent from my Nexus 4 using xda premium
livinginkaos said:
So how about for a Razr M XT907 ? I ran the term command, but the img size was wayyy too small.
Click to expand...
Click to collapse
You can find out your which partition your /system partition is by running the following commands either from terminal or adb shell as the root user:
Code:
ls -l /dev/block/platform/{your_platform_name_here}/by-name
For example on my Nexus 10 the platform name is "dw_mmc.0" so the command would look like:
Code:
ls -l /dev/block/platform/dw_mmc.0/by-name
To figure out your platform name first cd into the platform directory then list the contents of the platform directory to figure out what your platform name is:
Code:
cd /dev/block/platform/
ls
After you have then figured out what your platform name is you can run the command:
Code:
ls -l /dev/block/platform/{your_platform_name_here}/by-name
Once you have figured out your system partition you can dump it to your phones storage by running a command similar to:
Code:
cat /dev/block/block_of_system_partition > /mnt/sdcard/system.img
Let me know if you still have questions .
Awesome guys ! Thanks a bunch.
OK, so I have gotten the img. I've done it both ways with the dd and the cat. The image size comes up close to 1.5Gb. I know this is too large. The fastboot img file is normally in the 800-900 Mb range. Am I missing something here?
livinginkaos said:
OK, so I have gotten the img. I've done it both ways with the dd and the cat. The image size comes up close to 1.5Gb. I know this is too large. The fastboot img file is normally in the 800-900 Mb range. Am I missing something here?
Click to expand...
Click to collapse
Have you installed any additional system apps or placed any other files in the system folder? Because if you have modified the /system folder contents the file size will be greater then the normal 800-900 MB file range you listed since that file size if for an unmodified completely stock /system image.
Actually not really. I had done an erase data, roll back fxz, root, update and cache/dalvik wipe. Was trying to get a somewhat clean system.img
shimp208 said:
You can find out your which partition your /system partition is by running the following commands either from terminal or adb shell as the root user:
Code:
ls -l /dev/block/platform/{your_platform_name_here}/by-name
For example on my Nexus 10 the platform name is "dw_mmc.0" so the command would look like:
Code:
ls -l /dev/block/platform/dw_mmc.0/by-name
To figure out your platform name first cd into the platform directory then list the contents of the platform directory to figure out what your platform name is:
Code:
cd /dev/block/platform/
ls
After you have then figured out what your platform name is you can run the command:
Code:
ls -l /dev/block/platform/{your_platform_name_here}/by-name
Once you have figured out your system partition you can dump it to your phones storage by running a command similar to:
Code:
cat /dev/block/block_of_system_partition > /mnt/sdcard/system.img
Let me know if you still have questions .
Click to expand...
Click to collapse
When we come to Android 5.0 ages, we have new problems:
Method1 Using the dd we really can get the system.img, but in my 8994 device with busybox 1.23.1, it will 2.5GB fixed size, same as the system partition size.
so what I can found it works is , use sparsecoverter in this forum http://forum.xda-developers.com/showthread.php?t=2749797, we can remove the sparse bytes and make it a 1.4GB around and fastboot back to devices, that works fine, NOTE, that is not from dd nandroid backup. not from who only have TWRP and CWM backups;.
Method2 Using TWRP/CWM system.ext4.win/data.ext4.win, we can use
tar -xvf /storage/sdcard1/twrp/backup/abcd/2015-03-29-09-00-00/system.ext4.win
tar -xvf /storage/sdcard1/twrp/backup/abcd/2015-03-29-09-00-00/data.ext4.win
to gotten a folder, I run this on my target device under adb root and adb shell, but it will have many errors, tar remote link .... function not implement, so I think we need a cygwin according this post, but next step since Android 4.0 should be make_ext4fs, which will need a special build to avoid Permission Denied. which I still not success to finish it.
so, if Android successful tar -xvf and make_ext4fs story, please share here, thank you very much!
any news to help me forward?
hello guys. help me to get boot.img on my LG Magna (H502F) device. thanks before
You can try this
You could use the guidelines in this thread
http://forum.xda-developers.com/showthread.php?t=2450045
In my phone I couldn't list by name but if you use the cat commands in terminal Emulator with a rooted phone you can know the partition distribution in mmcblk0.
Hope this helps.
Here is described how to pull the files with the details remember first accessing to root privileges
vampirefo said:
Do you have a complete tutorial on how to do this? plus commands to restore? This would be great for us Linux users, I have two of these phones coming in from china and have zero desire to use windows to back up and restore a android device.
I think I got it figured out, wont know for sure until I get my phones to test.
Anyway basically I just
cat /proc/dumchar_info
this gives me partition info, from there I dd partition contents to sdcard, example below is to pull your recovery.img from the info you posted.
to pull eg backup
dd if=/dev/block/mmcblk0 of=/sdcard/recovery.img bs=4096 count=2560 skip=10112
to restore
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0 bs=4096 seek=10112
Click to expand...
Click to collapse
If=the directory you are going to read, of=the directory you are going to write, I recommend using your internal memory to avoid any problems, I did this using terminal Emulator and fx file manager with the root plug in to copy those files to the external_SD card
Where bs= blocks size, 4096 is fine, count= the number of blocks to copy and skip is the number of blocks that are omitted blocks copy