Database Develop

[Q] Problems booting into recovery

I am pretty sure I have followed the directions for installing CWD correctly but I cannot boot into recovery from "Power Off" state. This is a cut-and-paste of my ADB session. Everything looks OK right?
Thanks for any help.
Code:
# dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
2560+0 records in
2560+0 records out
10485760 bytes transferred in 1.391 secs (7538289 bytes/sec)
# dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
1238+1 records in
1238+1 records out
5070963 bytes transferred in 0.509 secs (9962599 bytes/sec)
# rm /data/recovery.img
rm /data/recovery.img
# reboot
reboot

You did power+volume down+3D til vibrate then release power and hold volume down+3d til recovery right?
Sent from my LG-P925 using Tapatalk

CallMeAria said:
You did power+volume down+3D til vibrate then release power and hold volume down+3d til recovery right?
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
I did the power+downvolume+3D multiple times. And then it finally worked AFTER I unplugged my phone from my laptop(it was low on battery and I didn't want to have it power off in the middle of flashing).
Thanks for your help!

Cant flash ClockworkMod Recovery
When i type the dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash over the clockworkmod, into my command promt it says 'cannot open for read: No such file or directory' and i dont know what im doing wrong.
I mean everything else seemed to workout fine. i downloaded the recovery image it said to save it but it was already saved to my computer after i downloaded it so i dont know if this could be the problem.
Then i used the adb push recovery.img/data command to push the recovery image to my phone, i think this might be where i messed up. After i put in the command a long list of text pops up on the command prompt. It starts out showing 'Android Debug Bridge version 1.0.26' then is followed by a long list of adb commands. Idk know if this is what its supposed to show.
Next i did the adb shell, su, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 command and that worked fine it said 2560+0 records out, 2560+0 records in 10485760 bites transfered in 0.413 secs and i actually found that file on my sdcard. So i think i did that right.
Next i tried to use the command 'dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096' and like i said earlier it just says 'cannot open for read: No such file or directory'
Lastly i tried the rm /data/recovery.img command and it said rm failed for /data/recovery.img, No such file or directory in the command prompt.
Im sorry i am new at this but i thought i followed the directions perfectly and any help anyone could give me would be greatly appreciated.

powers.jereme said:
When i type the dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash over the clockworkmod, into my command promt it says 'cannot open for read: No such file or directory' and i dont know what im doing wrong.
I mean everything else seemed to workout fine. i downloaded the recovery image it said to save it but it was already saved to my computer after i downloaded it so i dont know if this could be the problem.
Then i used the adb push recovery.img/data command to push the recovery image to my phone, i think this might be where i messed up. After i put in the command a long list of text pops up on the command prompt. It starts out showing 'Android Debug Bridge version 1.0.26' then is followed by a long list of adb commands. Idk know if this is what its supposed to show.
Next i did the adb shell, su, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 command and that worked fine it said 2560+0 records out, 2560+0 records in 10485760 bites transfered in 0.413 secs and i actually found that file on my sdcard. So i think i did that right.
Next i tried to use the command 'dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096' and like i said earlier it just says 'cannot open for read: No such file or directory'
Lastly i tried the rm /data/recovery.img command and it said rm failed for /data/recovery.img, No such file or directory in the command prompt.
Im sorry i am new at this but i thought i followed the directions perfectly and any help anyone could give me would be greatly appreciated.
Click to expand...
Click to collapse
I did this the exact same way and got the directory not found or no such directory. I have the recover.img file but when I type in dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash it just doesn't work. What am I doing wrong or where do I need to put the recovery.img after downloading?

Rabidaries said:
I did this the exact same way and got the directory not found or no such directory. I have the recover.img file but when I type in dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash it just doesn't work. What am I doing wrong or where do I need to put the recovery.img after downloading?
Click to expand...
Click to collapse
Recovery.img needs to be in
/sdcard
Sent from my LG-P925 using XDA App

Rabidaries said:
I did this the exact same way and got the directory not found or no such directory. I have the recover.img file but when I type in dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash it just doesn't work. What am I doing wrong or where do I need to put the recovery.img after downloading?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1363132
Go there and follow those directions they are the easiest way to install cwm. Good luck

I'm getting an error message that says cannot open for read: No such file or directory. I've already download the recovery.img and followed the steps from here http://forum.xda-developers.com/showthread.php?t=1363132

Previously broken GB root prohibits ICS404root script

The ICS404root script package has a fatal bug if a broken su already exists. Here's what happened on my D4.
I had root working fine on the GB version that shipped when I got the phone
I updated my stock (but rooted) D4 to 6.13.219 using normal OTA update and like an idiot, I forgot to use a root-keeper.
Confirmed root was broken as expected
Updated to ICS with "D4 6.16.217.zip". (I did no wipes other than the cache partition).
Everything worked fine and ICS is up and running
I ran the ICS404root.zip script package and get the following:
Code:
ICS404root # sh linux_runme_root_script.sh
Pushing files from root package to device...
4393 KB/s (586212 bytes in 0.130s)
4554 KB/s (1862336 bytes in 0.399s)
15 KB/s (660 bytes in 0.042s)
473 KB/s (22364 bytes in 0.046s)
Removing local copies.
Setting permissions.
Rebooting device...
Waiting for device to boot...
Attempting to place su binary on /system...
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: write: The file 'su' already exists
debugfs: debugfs: debugfs: debugfs: Cleaning up...
Rooting completed, must reboot.
Rebooting device...
Rooted.
So I have an old broken root on my phone, and this breaks the root script. I tried reinstalling superuser, but could only "uninstall updates" rather than uninstalling. (Uninstalling updates and re-installing them did not work.) I tried installing busybox but got root denied messages.
I *really* don't want to wipe my /system to fix this. Can the script be modified to deal with pre-existing su binaries?
UPDATE: (partially solved)
I ran debugfs in interactive mode and did a
Code:
debugfs: cd xbin
debugfs: rm su
debugfs: cd ..
debugfs: cd bin
debugfs: rm su
Then I completed the root hack manually and rebooted. I then updated Superuser and ran Titanium since I saw somewhere in a thread the TB will correct permissions on the su binary if they were funky. Sure enough it changed su from 4755 to 6755. After a reboot, everything was fine!
So... Root is attainable on ICS in the presence of a broken GB root, but the script should still be updated to deal with this.

ryanmcdonald said:
UPDATE: (partially solved)
I ran debugfs in interactive mode and did a
Code:
debugfs: cd xbin
debugfs: rm su
debugfs: cd ..
debugfs: cd bin
debugfs: rm su
Then I completed the root hack manually and rebooted. I then updated Superuser and ran Titanium since I saw somewhere in a thread the TB will correct permissions on the su binary if they were funky. Sure enough it changed su from 4755 to 6755. After a reboot, everything was fine!
So... Root is attainable on ICS in the presence of a broken GB root, but the script should still be updated to deal with this.
Click to expand...
Click to collapse
looks like i have the same issue except i got there a different way. i did use rootkeeper (though didn't do temp unroot before allowing OTA update to run), so i lost root when going to ics. not a big deal though, as the ics404root util worked fine to re-root.
well, i was having some odd issues like no sound when getting an sms, among others, so decided to do factory reset (without unrooting first). su is gone from the app drawer, but apparently it's still there as i get the same "debugfs: debugfs: write: The file 'su' already exists". i had to add a pause to the end of the batch file to be able to see that message, since it quits whether it worked or not, and you never see it.
i'm not familiar with what you mentioned about running debugfs in interactive. i tried using adb shell to poke around to see if i could find su and mv it to a .bak or something, but my linux command line skills are apparently too rusty. i found su in /system, but since /system is mounted as read only, i can't do anything. i eventually figured out how to get into interactive mode (forgot i had to specify the full path to debugfs since it's not in the default search path), but it tells me fs not open. i try to open, but i don't know what to give it for things like block size, etc:
Code:
[email protected]_maserati:/ $ /data/local/12m/debugfs
/data/local/12m/debugfs
debugfs 1.42 (29-Nov-2011)
debugfs: cd xbin
cd xbin
cd: Filesystem not open
debugfs: open_filesys
open_filesys
open_filesys: Usage: open [-s superblock] [-b blocksize] [-c] [-w] <device>
when looking around in adb shell, i could only find an su in /system/xbin - if i could come up with a way to delete this via adb, i think i could just run the regular root script and be done. any ideas?

still broken. i found a command that let me remount /system as rw, then i used rm su and verified it was gone w/ ls. re-ran ics404root batch file. no errors this time, but still no root on the phone. it seems to be putting su in there, but apparently it's corrupt. the way i check for root is to simply start titanium. right away it says it couldn't get root privileges.
Code:
C:\temp\droid4\ICS404root>adb shell
[email protected]_maserati:/ $ su
su
[email protected]_maserati:/ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /syste
m
2 /dev/block/mtdblock3 /system <
[email protected]_maserati:/ # cd /system/xbin
cd /system/xbin
[email protected]_maserati:/system/xbin # ls s*
ls s*
script
scriptreplay
sed
sendmail
seq
setarch
setconsole
setfont
setkeycodes
setlogcons
setsid
setuidgid
sh
sha1sum
sha256sum
sha512sum
showkey
slattach
sleep
smemcap
softlimit
sort
split
start-stop-daemon
stat
strings
stty
su
su.bak
sulogin
sum
sv
svlogd
swapoff
swapon
switch_root
sync
sysctl
syslogd
[email protected]_maserati:/system/xbin # rm su
rm su
[email protected]_maserati:/system/xbin # ls s*
ls s*
script
scriptreplay
sed
sendmail
seq
setarch
setconsole
setfont
setkeycodes
setlogcons
setsid
setuidgid
sh
sha1sum
sha256sum
sha512sum
showkey
slattach
sleep
smemcap
softlimit
sort
split
start-stop-daemon
stat
strings
stty
su.bak
sulogin
sum
sv
svlogd
swapoff
swapon
switch_root
sync
sysctl
syslogd
[email protected]_maserati:/system/xbin # rm su.bak
rm su.bak
[email protected]_maserati:/system/xbin # ls s*
ls s*
script
scriptreplay
sed
sendmail
seq
setarch
setconsole
setfont
setkeycodes
setlogcons
setsid
setuidgid
sh
sha1sum
sha256sum
sha512sum
showkey
slattach
sleep
smemcap
softlimit
sort
split
start-stop-daemon
stat
strings
stty
sulogin
sum
sv
svlogd
swapoff
swapon
switch_root
sync
sysctl
syslogd
[email protected]_maserati:/system/xbin # exit
exit
[email protected]_maserati:/ $ exit
exit
i have modified the batch file. i turned echo on and rem'd out the delete statements so i could see what was going on and so i wouldn't have to unzip it every time i tried it. (why does it delete the local stuff anyway?) i also added a pause at the end.
Code:
C:\temp\droid4\ICS404root>echo Connect your phone via USB to your PC and be sure
Connect your phone via USB to your PC and be sure
C:\temp\droid4\ICS404root>echo it ISN'T set to mount as a mass storage device.
it ISN'T set to mount as a mass storage device.
C:\temp\droid4\ICS404root>echo (ENTER to continue or push Ctrl-C to exit)
(ENTER to continue or push Ctrl-C to exit)
C:\temp\droid4\ICS404root>pause
Press any key to continue . . .
C:\temp\droid4\ICS404root>echo "Pushing files from root package to device..."
"Pushing files from root package to device..."
C:\temp\droid4\ICS404root>adb push busybox /data/local/12m/
2434 KB/s (586212 bytes in 0.235s)
C:\temp\droid4\ICS404root>adb push debugfs /data/local/12m/
2774 KB/s (1862336 bytes in 0.655s)
C:\temp\droid4\ICS404root>adb push rooter /data/local/12m/
71 KB/s (660 bytes in 0.009s)
C:\temp\droid4\ICS404root>adb push su /data/local/12m/
1818 KB/s (22364 bytes in 0.012s)
C:\temp\droid4\ICS404root>echo "Removing local copies."
"Removing local copies."
C:\temp\droid4\ICS404root>rem del busybox
C:\temp\droid4\ICS404root>rem del debugfs
C:\temp\droid4\ICS404root>rem del rooter
C:\temp\droid4\ICS404root>rem del su
C:\temp\droid4\ICS404root>echo "Setting permissions."
"Setting permissions."
C:\temp\droid4\ICS404root>adb shell chmod 755 /data/local/12m/busybox
C:\temp\droid4\ICS404root>adb shell chmod 755 /data/local/12m/debugfs
C:\temp\droid4\ICS404root>adb shell chmod 755 /data/local/12m/rooter
C:\temp\droid4\ICS404root>adb shell chmod 755 /data/local/12m/su
C:\temp\droid4\ICS404root>adb shell mv /data/local/12m/batch /data/local/12m/bat
ch.bak
C:\temp\droid4\ICS404root>adb shell ln -s /dev/block/mmcblk1p20 /data/local/12m/
batch
C:\temp\droid4\ICS404root>echo "Rebooting device..."
"Rebooting device..."
C:\temp\droid4\ICS404root>adb reboot
C:\temp\droid4\ICS404root>echo "Waiting for device to boot..."
"Waiting for device to boot..."
C:\temp\droid4\ICS404root>adb wait-for-device shell /data/local/12m/rooter
Attempting to place su binary on /system...
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: Allocated inode: 4359
debugfs: debugfs: debugfs: debugfs: Cleaning up...
Rooting completed, must reboot.
C:\temp\droid4\ICS404root>adb shell rm /data/local/12m/rooter
C:\temp\droid4\ICS404root>echo "Rebooting device..."
"Rebooting device..."
C:\temp\droid4\ICS404root>adb reboot
C:\temp\droid4\ICS404root>echo "Rooted."
"Rooted."
C:\temp\droid4\ICS404root>rem del AdbWinUsbApi.dll
C:\temp\droid4\ICS404root>rem del AdbWinApi.dll
C:\temp\droid4\ICS404root>rem del adb.exe
C:\temp\droid4\ICS404root>rem del linux_runme_root_script.sh
C:\temp\droid4\ICS404root>del
The syntax of the command is incorrect.
C:\temp\droid4\ICS404root>pause
Press any key to continue . . .
C:\temp\droid4\ICS404root>
i'm kinda stuck at this point, but at least my phone isn't bricked. but considering all the issues i've had w/ ICS (the separate notification and ringtone volumes which cannot be linked being the TOP of my sh*t list, right after the crappy dialer, the lousy SMS client (seriously, gray on black? i cant read that!) and the list goes on and on...) i'd honestly rather go back to stock rooted GB. chrome was the only other reason i wanted ics and it seemed to be pretty poorly implemented to me, so i have no more interest in ICS.
i almost wonder if it's worth intentionally bricking it and bringing it back to vzw for exchange, and hopefully the new one won't have ics yet.

ok, i am rooted again! i had to use the Droid 4 Utility ICS Only to do it. the links to the LITE version are broken, so i had to download the entire 600mb package, but it worked to root my phone. now to start reinstalling stuff w/ titanium!

Bricked over mistake, please help.

i have a Japanese HTC One or HTL22. I tried to sim unlock it as shown in this URL.
Code:
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
Upon writing this codes in cmd, i made a mistake: instead of /mmcblk0p19 I input /mmcblk0p1.
There was a message saying
Code:
/dev/block/mmcblk0p1: write error: No space left on device
257+0 records in
257+0 records out
131072 bytes transferred in ...
So i think the misc.img is transferred into the device (though it said no space left). And now the device wont boot.
Please help. Thanks.

I cant delete this thread. Please go to and reply in any of the following pages:
for HTC One
for Android

"No Space left on device" while trying to zero out .Laf file on adb

So I tried following This Guide, and I am unable to use the command
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
because adb gives me the error "No space left on device"
Any ideas on how to fix this?
C:\WINDOWS\system32>adb shell su
[email protected]:/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd: /dev/block/platform/msm_sdcc.1/by-name/laf: No space left on device
45057+0 records in
45056+0 records out
23068672 bytes transferred in 9.738 secs (2368933 bytes/sec)
Click to expand...
Click to collapse

Update: While I have no idea on what happened, apparently the bootloader is factory unlocked and I could just flash TWRP anyway.

One-click root ..amonet-mustang

Hi ..
I have a script for device amonet-mustang
I want when I run a file flash-B.sh
to do everything automatically
When I run my script it doesn't work .. say Permission denied
link file
https://www.mediafire.com/file/iioog...lash-B.sh/file
Quote:
#!/bin/bash
args=("[email protected]")
function goto
{
label=$1
cmd=$(sed -n "/$label:/{:a;n;p;ba};" $0 | grep -v ':$')
eval "$cmd"
exit
}
echo[*] OPEN Done ...
adb wait-for-device
adb devices
adb push arm/mtk-su /data/local/tmp
adb shell chmod 777 /data/local/tmp/mtk-su
echo[*] File Push Done...
adb shell "/data/local/tmp/mtk-su -c echo 0 \> /sys/block/mmcblk0boot0/force_ro"
adb shell "/data/local/tmp/mtk-su -c dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8"
echo[*] block Done...
adb reboot
echo[*] Reboot DONE .
./bootrom-step.sh
echo[*] bootrom-step DONE .
./fastboot-step.sh
echo[*] You are now in Recovery ..plz Format your Amazon ...
sleep
exit
Click to expand...
Click to collapse
say
dd: /dev/block/mmcblk0boot0: Operation not permitted
1+0 records in
0+0 records out
0 bytes transferred in 0.001 secs (0 bytes/sec)
Click to expand...
Click to collapse

PRInCEI7 said:
Hi ..
I have a script for device amonet-mustang
I want when I run a file flash-B.sh
to do everything automatically
When I run my script it doesn't work .. say Permission denied
link file
https://www.mediafire.com/file/iioog...lash-B.sh/file
Quote:
say
Click to expand...
Click to collapse
Link is dead