can somebody tell my why when i use te solution from here
http://forum.xda-developers.com/showthread.php?p=15851843
after i put a command $ adb shell cat /dev/msm_rotator
i get an error: permission denied also when i use push command..
please help
Hello everyone,
Can someone help me get some files from HTC one S s4 (US T-mobile) please?
Because my phone was broken, even cannot power on, cannot use adb as well. I need to collect a partition file from the phone.
Because once I saw some articles to solve this kind of trouble and want to have a try, but in lack of this partition file.
I just need those who have the same phone as mine can provide the file to me.
--------
adb shell su -c 'dd if=/dev/block/mmcblk0 of=/cache/partition0.bin bs=512 count=1'
adb shell su -c 'dd if=/dev/block/mmcblk0 of=/cache/partition0.bin bs=512 count=9'
--------
Can someone use these two command and send me two partition files please?
The final file is called "partition0.bin"
Each command can create one.
Thank you so much.:victory:
Q&A for [TUT] Fix Mount System in Kitkat After Root
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 [TUT] Fix Mount System in Kitkat After Root. 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!
boot.img
Please give me M2 ,D2303, 4.4.2 , 18.3.C.0.37 boot.img
aunggyi2014 said:
Please give me M2 ,D2303, 4.4.2 , 18.3.C.0.37 boot.img
Click to expand...
Click to collapse
heres a .40 one if it helps https://drive.google.com/file/d/0B8tBozpqUuU1R0RnV3VoVXJEUWs/view
d2306 unable to update from OTA
Hi,
I've tried this method and I couldn't update my d2306 with D2306_18.0.C.1.17_PT-BR.ftf (JB) using the Update Center app (I'm really sorry for my ignorance, but this is how we update from OTA, right?). It only said that the update failed and didn't gave any log or reason why.
So I've tried to flash everything, but the kernel, again using the flashtool, as seen in androidclub. But then I got stuck in bootloop.
I've already tried to flash CWM and root from within it, and then, as my phone had come with KK already, I've flashed only the kernel. But then I can't go into custom recovery anymore, and I got the system not writable problem.
For OTA errors check this file :
/cache/recovery/fota/report
Sony ric service for KK 4.4.2 is located at /sys/kernel/security/sony_ric
Assume you have root access on your KitKat, and busybox installed.
Get ready (or compile for yourself) copymodulecrc and ric_disabler_mod.ko written by @cubeundcube from here.
Look at install_tool.sh script, there is everything you need...)
e.g., connect your device via usb......and execute from shell :
Code:
adb push files/copymodulecrc /data/local/tmp/
adb push files/ric_disabler_mod.ko /data/local/tmp/
adb shell "su -c 'chmod 0755 /data/local/tmp/copymodulecrc'"
adb shell "su -c 'chmod 0644 /data/local/tmp/ric_disabler_mod.ko'"
adb shell "/data/local/tmp/copymodulecrc /system/lib/modules/scsi_wait_scan.ko /data/local/tmp/ric_disabler_mod.ko"
adb shell "su -c 'insmod /data/local/tmp/ric_disabler_mod.ko'"
adb shell "su -c 'dd if=/data/local/tmp/ric_disabler_mod.ko of=/system/xbin/ric_disabler_mod.ko'"
adb shell "su -c 'chown root.root /system/xbin/ric_disabler_mod.ko'"
adb shell "su -c 'chmod 0644 /system/xbin/ric_disabler_mod.ko'"
Create a file 00stop_ric, with the following content:
Code:
#!/system/bin/sh
insmod /system/xbin/ric_disabler_mod.ko
Save it, copy to the /system/etc/init.d/ and set access permissions :
Code:
adb push 00stop_ric /system/etc/init.d/00stop_ric
adb shell "su -c 'chown root.root /system/etc/init.d/00stop_ric'"
adb shell "su -c 'chmod 0755 /system/etc/init.d/00stop_ric'"
Put this line at the end of the file init.qcom.post_boot.sh (located in the /system/etc/)
Code:
/system/xbin/busybox run-parts /system/etc/init.d
Test mount:
Code:
adb shell "su -c 'mount -o remount,rw /system'"
p.s
For all written above I used koush/Superuser for root access.
Please help
After rooting, my phone is showing internal storage fill. How can i fix it.
Hi Guys,
My phone's screen has broken and I can't see anything, although the touch still works. I have been able to connect it to the PC to take my music and photos off the internal storage, and my contacts are backed up to Google, but my texts are not and I'd like to recover them.
I've read that they normally reside in /data/data/com.android.providers.telephony/databases/mmssms.db and I should be able to pull this via ADB.
When the phone is booted to the OS it is not detected by ADB at all with 'error: device not found'. I thought USB debugging was on, but obviously not. I can boot to recovery (custom CWM) and now adb will connect to the device. However, when I try to pull the sms db I get 'No such file or directory'
Code:
[email protected] ~ $ sudo adb start-server
[sudo] password for james:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected] ~ $ adb shell
error: device not found
[email protected] ~ $ adb devices
List of devices attached
[email protected] ~ $ adb devices
List of devices attached
CB5122TH5B device
[email protected] ~ $ adb shell
~ # mkdir /mnt/sdcard/tmp
~ # cat /data/data/com.android.providers.telephony/databases/mmssms.db > /mnt/sdcard/tmp/mmssms.db
cat: can't open '/data/data/com.android.providers.telephony/databases/mmssms.db': No such file or directory
~ # su cat /data/data/com.android.providers.telephony/databases/mmssms.db > /mnt/sdcard/tmp/mmssms.db
cat: can't open '/data/data/com.android.providers.telephony/databases/mmssms.db': No such file or directory
/sbin/sh: su: not found
~ # exit
[email protected] ~ $ adb pull su /data/data/com.android.providers.telephony/databases/mmssms.db
remote object 'su' does not exist
~ # ls /data
~ #
It would appear the directory /data is empty but I bet that's because I don't have permissions to view the contents. I'm guessing this is also why su is not found.
Can anyone help me to get over this hurdle? Please bear in mind I'm not familiar with ADB and not great in a Linux shell either; the above commands took a bit of reading to find, but I do understand what they're trying to do.
My phone is a Sony Xperia T LT30p and is rooted running Xperiment 3.5 and Clockworkmod recovery 6.0.4.6 and I'm running ABD on Linux.
Any help would be appreciated! Cheers :good:
Code:
adb shell ls
Is OK and lists files. adb devices sees the phone no problem too.
Yet:
Code:
adb logcat -s (any input)
freezes at 'beginning of main'.
For example:
Code:
>adb logcat -s dirtysanta
- waiting for device -
--------- beginning of system
--------- beginning of main
(no more output. tried for hours)
What can I try next? This doesn't really seem like a v20 problem but the xdadevs forum needs me to post here afaik.
edit: I think it was Mcafee, bundled by default and preventing run-as com. After a OTA update I managed to get a temp root prompt.
Is there someone I can pay to help me with this?