Dear All
I am pulling the modem partition from my galaxy tab with the below command
adb shell dd if=/dev/block/mmcblk0p7 of=/data/log/modem.bin
but i am getting the error cannot open for read: permission denied, could anybody help me how i can change the permission or what should i do in this case? i am pretty sure the partition is correct..
Related
I would really appreciate if someone with 16G Nexus 4 can make a primary partition table dump.
It is only 17KB in size and has no personal information and is same on all 16G devices.
Device has to be rooted and root for adb should be enabled in dev options or it can be booted into cwm
Code:
adb shell
su (skip this test if booted into cwm)
dd if=/dev/block/mmcblk0 of=/sdcard/pgpt.img bs=512 count=34
exit
exit (skip this step if booted into cwm)
adb pull /sdcard/pgpt.img
Please post pgpt.img or send a PM to me.
Thanks!
http://d-h.st/bR1
Good luck with getting the full 16GB on the LOG to N4 conversion
Sent from my Nexus 4 using xda premium
android88 said:
http://d-h.st/bR1
Good luck with getting the full 16GB on the LOG to N4 conversion
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks! Yep, you nailed it, I'm converted (my phone, to be precise)
Can I ask another favor to make a dump of more partitions? I want to make sure they do not differ from 8G version.
Code:
...
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/sdcard/sbl1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl2 of=/sdcard/sbl2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl3 of=/sdcard/sbl3.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/sdcard/tz.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/sdcard/rpm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/DDR of=/sdcard/DDR.img
...
adb pull /sdcard/sbl1.img
adb pull /sdcard/sbl2.img
adb pull /sdcard/sbl3.img
adb pull /sdcard/tz.img
adb pull /sdcard/rpm.img
adb pull /sdcard/aboot.img
adb pull /sdcard/misc.img
adb pull /sdcard/persist.img
adb pull /sdcard/DDR.img
I just downgraded my Verizon G2 from 12b to 11a with this guide: (because of the push email issue)
http://forum.xda-developers.com/showthread.php?t=2448960
What I didn't realize was it would erase the data partition and now all my pictures are gone (idiot, I know)
Recovery software wont work because the G2 is only listed as a MTP device and they software doesn't see it.
I tried using this guide here, http://forum.xda-developers.com/showthread.php?t=1994705, which has instructions for the Galaxy Nexus which has the same MTP only issue. It basically dumps the partition as a .raw file to the computer through adb and then you can recover from that. I'm having a problem with this command "/system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p12" mmcblk0p12 is the block on the galaxy nexus where the userdata was stored. I thought I had found the G2's block at "/dev/block/platform/msmsdcc.1/by-name/userdata" but the command doesn't work
Does anyone have any idea what the block path really is or an alternative to recover my lost stuff? Thanks.
Also tried to flash TWRP and then mount from there so software will see it but mounting does nothing
indigoataxia said:
I just downgraded my Verizon G2 from 12b to 11a with this guide: (because of the push email issue)
http://forum.xda-developers.com/showthread.php?t=2448960
What I didn't realize was it would erase the data partition and now all my pictures are gone (idiot, I know)
Recovery software wont work because the G2 is only listed as a MTP device and they software doesn't see it.
I tried using this guide here, http://forum.xda-developers.com/showthread.php?t=1994705, which has instructions for the Galaxy Nexus which has the same MTP only issue. It basically dumps the partition as a .raw file to the computer through adb and then you can recover from that. I'm having a problem with this command "/system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p12" mmcblk0p12 is the block on the galaxy nexus where the userdata was stored. I thought I had found the G2's block at "/dev/block/platform/msmsdcc.1/by-name/userdata" but the command doesn't work
Does anyone have any idea what the block path really is or an alternative to recover my lost stuff? Thanks.
Click to expand...
Click to collapse
Hi there,
You should identify which partition is your data partition (link in step 1 of the guide). I did it, it shows me mmcblk0p35 (i have D802). But I had another problem.
I have rooted stock rom (D80210f-EUR-XX) with stock recovery. After modyfying /system/build.prop i got bootloop. the only thing I could do was to enter stock recovery and "Reset to defaults", so I did, but I lost all my data, messages, settings etc.
I tried to recover data partition using the same guide, but i'm stuck at step 6. It shows me speed of 0 B/s and creates file of 0B nomatter how long I wait.
Can anybody help please?
indigoataxia said:
I just downgraded my Verizon G2 from 12b to 11a with this guide: (because of the push email issue)
http://forum.xda-developers.com/showthread.php?t=2448960
What I didn't realize was it would erase the data partition and now all my pictures are gone (idiot, I know)
Recovery software wont work because the G2 is only listed as a MTP device and they software doesn't see it.
I tried using this guide here, http://forum.xda-developers.com/showthread.php?t=1994705, which has instructions for the Galaxy Nexus which has the same MTP only issue. It basically dumps the partition as a .raw file to the computer through adb and then you can recover from that. I'm having a problem with this command "/system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p12" mmcblk0p12 is the block on the galaxy nexus where the userdata was stored. I thought I had found the G2's block at "/dev/block/platform/msmsdcc.1/by-name/userdata" but the command doesn't work
Does anyone have any idea what the block path really is or an alternative to recover my lost stuff? Thanks.
Click to expand...
Click to collapse
I'have your same issue (LG G2 D802)
I tried with:
/system/xbin/busybox ncat -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p35
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p35
/system/xbin/busybox ncat -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0p35
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0p35
but nothing happen!
did you solve? if yes, how???
tetractius said:
did you solve? if yes, how???
Click to expand...
Click to collapse
No, never was able to recover.
Sorry for reviving a dead thread.
Has anyone been able to successfully recover their deep formatted drive? Like the guide mentioned does? I'm currently trying, but no success..
Q&A for [ROOT][CWM] Root Nexus 4 & Install Official ClockworkMod Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][CWM] Root Nexus 4 & Install Official ClockworkMod Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Booting with insecure boot image has broken all my sensors in my Nexus 4 / Android 5
I have been using a boot insecure image made for Nexus 4 / Android 4.2 downloaded from here :
http://forum.xda-developers.com/nexus-4/development/boot-img-obsolete-please-lock-t1990170
to boot my phone to have root access through adb by doing:
$ fastboot boot bootinsecure.img
But after upgrading to Android 5 the process of booting with this image was ruining all my sensors and my wifi.
My wifi was fixed by deleting the content in /data/misc/wifi but leaving wpa_supplicant.conf to keep my saved wifis.
But I cannot fix the sensors. I tried this fix for Nexus 5 but it didn't work:
http://forum.xda-developers.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915
If I delete the user data the problem is solved but I don't want to remove all my data.
There is something in that boot image that brakes my sensors by changing something in the userdata partition
For testing purposes, I deleted the user data. Booted again and the problem was fixed. I saved a image of the userdata partition by doing as root:
$ adb pull /dev/block/mmcblk0 mmcblk0.img
and mounting the userdata partition in my linux as root to keep al the original permissions
# sudo mount -o loop,offset=1627389952,defaults,ro,noload mmcblk0.img mnt/userdata
I booted from my boot insecure image and reboot normally and all the sensors where ruined as expected
So I created another image and I mounted the userdata in another folder
and then I compared all the files that where changed using rsync after and before the boot with the insecure image.
I found a few extra files in the "after" image so I deleted them but the problem was not fixed.
I think that maybe the problem is related to folder/files permissions, attributes or extended attributes (like SElinux) that were changed and cannot be detected when comparing using rsync
Any ideas what might have been and what to do to fix it?
SOLVED:
Solution:
Apparently the problem was not in the userdata partition was in the persist partition. I solved by cloning a working persist partition from another Nexus 4.
I realized that something was wrong in the probably extended attributes in the file /persist/sensors/sns.reg since a
$ adb logcat
was giving this error:
W/sensors.qcom( 282): type=1400 audit(0.0:5): avc: denied { getattr } for path="/persist/sensors/sns.reg" dev="mmcblk0p20" ino=15 scontext=u:r:sensors:s0 tcontext=ubject_r:unlabeled:s0 tclass=file
So I fixed in this way:
First I downloaded a modified busybox dd from:
http://d-h.st/cFA
Don't use the default one it will ruin your partition:
I downloaded recovery-clockwork-touch-6.0.4.7-mako.img from:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-mako.img
1) Then I booted from a recovery image like ClockWorkMod. With the phone in the bootloader:
$ fastboot boot recovery-clockwork-touch-6.0.4.7-mako.img
2) Created a ramdisk in the phone
$ adb shell mkdir /dev/ramdisk
$ adb shell mount -o size=1536M -t tmpfs tmpfs /dev/ramdisk
3) Copied dd to the phone
$ adb push dd /
$ adb shell chmod 755 /dd
4) Extract persist from the working phone
$ adb shell /dd if=/dev/block/mmcblk0 of=/dev/ramdisk/persist.img bs=4096 skip=34816 count=4096
5) Pull file to our PC
$ adb pull /dev/ramdisk/persist.img
6) Reboot working phone
$ adb reboot-bootloader
With our not working Nexus 4
Repeat steps 1 to 3
7) Push your persist image to the phone
$ adb push persist.img /dev/ramdisk/
8) Overwrite image
$ adb shell /dd if=/dev/ramdisk/persist.img of=/dev/block/mmcblk0 bs=4096 seek=34816 conv=notrunc
9) Wipe cache and dalvik cache
10) Reboot
Should be fixed if that was the problem
My phone has not been able to receive calls because the default APN settings from LOS are just wrong. I updated the file (/system/product/etc/apns-conf.xml) in recovery, but after a reboot, the file is back to what it was before I changed it.
I am using LOS recovery if that helps. How do I change that one file to have it persist across reboots?
Thanks
Problem solved!
Had to mount the "/" partition to be writable using the command:
Bash:
adb shell su -c 'mount -o remount,rw /'
Then after making changes, I first pushed the file to internal storage:
Bash:
adb push ./apns-conf.xml /sdcard/Documents/apns-conf.xml
Then finally I copied it to the proper location:
Bash:
adb shell su -c 'cp sdcard/Documents/file.xml /system/product/etc/apns-conf.xml'
Hope that helps someone
Hi all,
I tried to identify partitions on the device (userdata, vendor, system, etc.)
Device: Oneplus2 (unrooted).
After
Code:
adb shell
ls -l /dev/block/by-name
It returns
Code:
/dev/block/by-name: Permission denied
I also tried
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
The same result followed.
So
1. How to solve this "permission denied" problem?
2. Would it nevertheless be possible identify partitions on an unrooted device?
Thanks in advance.
Cheers,
Wen