Database Info

Question about rooting and flashing recovery image..

Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.

mobilehavoc said:
Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.
Click to expand...
Click to collapse
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.

chuckhriczko said:
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.
Click to expand...
Click to collapse
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.

mobilehavoc said:
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.
Click to expand...
Click to collapse
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.

chuckhriczko said:
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.
Click to expand...
Click to collapse
What he said...but yes, at the steps you quoted, mobilehavoc, you are capable of root access (you don't actually have it until you run that "su" command ). That allows you to read and modify otherwise locked away files and tweak to your hearts content!

Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated

Grinder16 said:
Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated
Click to expand...
Click to collapse
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?

thecodemonk said:
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?
Click to expand...
Click to collapse
Dont see that folder - I guess that is not good. Any ideas?

Grinder16 said:
Dont see that folder - I guess that is not good. Any ideas?
Click to expand...
Click to collapse
You must do a backup BEFORE you can do a restore..

To clarify for everyone, here's a breakdown of the steps:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
This copies the asroot2 program to the /data/local folder on your phone.
adb shell
This logs you into the phone. From here on out, you are no longer executing Windows commands from a DOS shell - you are actually executing Linux commands on the phone.
chmod 0755 /data/local/asroot2
This changes the permissions on the asroot2 program so that it can be executed.
/data/local/asroot2 /system/bin/sh
This actually runs the root exploit and creates a file called /system/bin/sh that we will later turn into su.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
This unmounts the /system partition and remounts it as writeable.
cd /system/bin
This puts you into the /system/bin folder.
cat sh > su
This creates the su program.
chmod 4755 su
This changes the persmissions on the su file to allow it to be executed.

theresthatguy said:
You must do a backup BEFORE you can do a restore..
Click to expand...
Click to collapse
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find

Grinder16 said:
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find
Click to expand...
Click to collapse
Boot to the recovery image then select "nandroid backup"

jonnythan said:
Boot to the recovery image then select "nandroid backup"
Click to expand...
Click to collapse
Can you provide those steps? Sorry but complete newbie here

"I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error"
Go there but select Backup instead of Restore.
Turn the phone off, hold the Home key, and turn it on. When you get to the screen with the green text select nandroid backup.

Does anyone have the proper file to get QuickBoot working?

I know you had to push a reboot file to get it working on some Hero ROMs. What about the EVO version?

The Hero way works.
FIRST, install Quickboot from the market. Run it and enable it in the superuser permissions screen.
Download the reboot.txt file I attached and rename it to "reboot" (take off the ".txt"). Move it to where ever your "android-sdk-windows/tools" folder is.
Connect your phone to your computer (make sure it is "charge only") and boot into recovery...
Code:
adb shell
reboot recovery
Start your "Windows-recovery.bat" (if using windows) and let it do it's thing in the CMD prompt. Keep that prompt open.
In a CMD prompt OTHER THAN the one opened by recovery.bat type...
Code:
adb shell
mount /dev/block/mtdblock4 /system
exit
This will keep your system mounted but get you out of shell. Now type...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
Once you're back up, run Quickboot and choose either reboot or recovery (both will now work). It takes about 5 seconds to start rebooting but it does work.

What does this do? does it make recovery stick?

watzone69 said:
The Hero way works.
Download the reboot.txt file I attached and rename it to "reboot".
Once you're in recovery...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
EDIT: It takes about 5 seconds to start rebooting but it does work.
Click to expand...
Click to collapse
Woo! Thanks!
Edit: Didn't seem to work for me. Damn.
joeavery2 said:
What does this do? does it make recovery stick?
Click to expand...
Click to collapse
No, this just lets you use the QuickBoot app from the Market to reboot your phone.

TheBiles said:
Didn't seem to work for me. Damn.
Click to expand...
Click to collapse
Code:
adb shell
cd /system/bin/
ls
See if the reboot file actually got pushed to the directory. If so, try this:
Code:
chmod 755 /system/bin/reboot
The only other thing I can think of is that I installed Quickboot BEFORE doing all of this. Did you get the SU permission screen when you tried to run it?

Any luck??
Did I mention that the Quickboot "recovery" button works also? Much easier than opening a shell and typing it in.
Of course you still have to run the recovery.bat to get the custom recovery but at least it's one less step.

Still no dice. I also already had QuickBoot installed and granted it root permission prior to pushing the reboot file.

any update to this?
thanks

joey3002 said:
any update to this?
thanks
Click to expand...
Click to collapse
It doesn't work for you?

I updated my earlier post to give more instructions for getting into recovery and pushing the "reboot" file. I hope it helps!

I have a ROM ready to go that changes a couple icons and quickboot works with no probelm. Wifi tether is the only thing I don't have working. I can post it if you would like. I also removed sprint apps and some widgets

I made an update zip that got Quickboot working for me. This is using watzone69's reboot file.
Run from Toast's recovery. http://forum.xda-developers.com/showthread.php?t=690762

watzone69 said:
It doesn't work for you?
Click to expand...
Click to collapse
yes i got it working last night by reading this thread from top to bottom.. then repeated.. thanks

How make run sound boot animation on CM6

Hello guys im trying for awhile to make a run some boot animation sound over the stock CM6 blue android that is comming as stock but i never get succes can somebody help me with this please

juancaperez2000 said:
Hello guys im trying for awhile to make a run some boot animation sound over the stock CM6 blue android that is comming as stock but i never get succes can somebody help me with this please
Click to expand...
Click to collapse
The solution is not for the faint of heart and will have to be reapplied with each nightly.
Add this to init.local.rc
Code:
###Bootsound - Safe to Delete: Start ###
service bootsound /system/bin/bootsound
user media
group audio
disabled
oneshot
on property:init.svc.bootanim=running # to correct timing
start bootsound
on property:dev.bootcomplete=1
stop bootsound
### Bootsound - Safe to Delete: End ###
Then make a new file called "bootsound" and push it to /system/bin
i.e. "adb push c:\path\to\bootsound /system/bin/bootsound"
Code:
#!/system/bin/sh
bprop=/system/build.prop
grepprop() { x=`grep "^$1=" $bprop | head -n 1`; echo $x | cut -d = -f 2; }
play=`grepprop "ro.config.play.bootsound"`
if [ "$play" = "1" ]; then
stagefright -a -o /data/local/android_audio.mp3
fi
exit 0
Issue the following commands:
Code:
adb remount
adb shell chmod 777 /system/bin/bootsound
adb shell chown root:shell /system/bin/bootsound
adb shell echo ro.config.play.bootsound=1 | cat >> /system/build.prop
Now put your startup sound, whatever MP3 it is, in /data/local with name android_audio.mp3 and it will be played at startup. You test it with an adb reboot. I flash nightlies on a regular basis so I stopped doing this as it's a PITA to constantly have to push changes each night. I like to flash + go.
'tuna

Wow...only question is would this work for for stable 6? And can I do it thru term emu

cubanjinx said:
Wow...only question is would this work for for stable 6? And can I do it thru term emu
Click to expand...
Click to collapse
As long as you have a way to edit the init file + create/edit the new bootsound file then yes it can be done via term emu. Should work with any/all versions of cm6. Obviously you'd omit the "adb shell" portion of the shell commands.
'tuna

spiicytuna said:
The solution is not for the faint of heart and will have to be reapplied with each nightly.
......
'tuna
Click to expand...
Click to collapse
Wow. One of the best answers I have ever seen around here.

spiicytuna said:
The solution is not for the faint of heart and will have to be reapplied with each nightly.
---------
Now put your startup sound, whatever MP3 it is, in /data/local with name android_audio.mp3 and it will be played at startup. You test it with an adb reboot. I flash nightlies on a regular basis so I stopped doing this as it's a PITA to constantly have to push changes each night. I like to flash + go.
'tuna
Click to expand...
Click to collapse
Wow. Not kidding with the "not for the faint of heart" part. I think I will live with no sound. Unless, I knew how the hell to use that code. Meh....

Will donate
Tuna or anyone else willing to walk me through this for a donation? Haha... I set up a whole mp3 for the boot to come to this road block. Also, for anyone reading, how can I change just the lock screen wallpaper on froyo. (Using plain black background right now and it makes the lockscreen a little too boring) Thanks.

has this been confirmed working on CM6 final? read some comments over at the cyanogenmod forum that this script was droid x phones, not the evo?
i'm going to give it a try tonight or tomorrow night, some questions
1)where is the init.local.rc file?
2)what kind of file should the bootsound file be? .txt file? no extension? ??
3) the code you put after saying to make the bootsound, does that mean that code is to be entered into adb or as the content of the bootsound file?
spiicytuna said:
The solution is not for the faint of heart and will have to be reapplied with each nightly.
'tuna
Click to expand...
Click to collapse
EDIT: tried it. edited the init.local.rc file using Notepad++. made the bootsound file using Notepad++ and in it put the code you have up there. no file extension. pushed it to the right directory, followed the adb commands. got an error in the last one (echo) saying it couldn't find the path (it's there though?).
put the android_audio.mp3 in /data/local....rebooted and no sound. no errors either, but no sound.
EDIT 2: thanks for your work spiciituna. apparently there was some mistake on my part. i ran a script that your code in it and now the boot sound works.
http://forum.cyanogenmod.com/topic/7433-bootanimations-audio/

I am still having no luck. :-( Can anyone enlighten me?
Sent from my PC36100 using XDA App

austinjay said:
I am still having no luck. :-( Can anyone enlighten me?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I was finally about to get it to work.
Here is the post with the flashable zip
http://forum.xda-developers.com/showthread.php?t=844414

juancaperez2000 said:
Hello guys im trying for awhile to make a run some boot animation sound over the stock CM6 blue android that is comming as stock but i never get succes can somebody help me with this please
Click to expand...
Click to collapse
if it's FroYo, then the directory has been moved to /system/customize/resource/. You reboot to clockworkmod -> mount system (partitions menu) -> reboot recovery (advanced menu) -> open cmd prompt in windows, cd to sdk\tools\ and run: "adb remount" -> then have the .wav file in the tools folder and run "adb push ATT_bootup.wav /system/customize/resource/" if it's an AT&T phone. Verizon phones use VZW_bootup.wav I am pretty sure & I'm not sure about the other ones.

[Q] adb shell "exec '/system/bin/sh' failed: No such file or directory (2)"

Hey,
Ok so a little backstory before my problem: So I was in the middle of putting a new ROM on my captivate. I had one before but i wanted to change so I put the rom in update.zip and installed it will clockworkmod recovery. It installed fine I think but then when I tried to boot it gets stuck on the boot screen. So i tried to boot in recovery mode. I geld down both the volume buttons and the power button until it reboots twice, then I let go of the power button. but it still gets stuck on the boot screen and does not go into recovery mode. So i plugged it into my computer and using
Code:
adb devices
it shows up under recovery mode. So far so good. I can use the
Code:
adb reboot
and
Code:
adb push
commands fine. but when i try to use
Code:
adb shell
it says
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
So i can not reflash the recovery image. I read that I just needed to mount the /system file. But i do not know how to do this. the "mount" command does not work with adb. I would appreciate anything to help me to either reflash the rom or restore to factory or anything where i can work off of. thanks

I have exactly the same problem.
Did you get to a solution to this?
Good luck, dude.

Is there a solution to this without using a Motorola Factory cable? I don't have the resources to make one and I don't have money to buy one.

I'm not sure putting the rom into "update.zip" was the right choice.
adb shell could fail because the partition is not mounted, the sh binary is not installed, or not at the correct location
If you can still get the captivate into download mode, you could use odin/heimdall to flash a working ROM.

First of all...thanks to everyone that has EVER posted in the XDA forums! I've spent days reading them and I came across one that had a suggested solution for my problem. So let's start...
1) Bricked
2) ADB is finally working again...so..not a problem any longer
(Don't ask me how I got it to work again....I have no idea. System was wiped while using TWRP from a bootloop)
3) Now...with system wiped I have no '/system/bin/sh'
4)adb shell will not work because of this. adb root does not work because of production model. adb remount is not permitted.
Now....I came across a thread that suggest using r2.6.2.kindlefire.boot.insecure.img and zergRush. I have the zergRush file, but I need the r2.6.2.kindlefire.boot.insecure.img to push with adb.
Does anyone know where I can get the r2.6.2 at? Filesonic is disabled and Multiupload will not return page.
Link I came across: addictivetips /mobile/gain-root-adb-access-with-insecure-boot-image-for-kindle-fire/

[Q] Please help, I was trying to change the fonts and screwed my phone.

I need some help please, my phone wont boot and is stuck at the M logo. I am using dexters ROM with its patch. I wanted to change the android font from the standard droidsans to the Ubuntu font. I downloaded the ttf's from the ubuntu website and started looking on how to go about it.
So after searching the internet, I saw most people were doing it using adb push to replace the fonts in the /system folder. First problem that I encountered was adb not working, but after updating my $PATH to add platform tools it started working. After that when I tried the push command it said the /system was read only. I followed these instructons to make the /system folder read/write.
adb shell
$ su
# mount
# # mount -o remount,rw -t yaffs2 /dev/block/mtdblock7 /system
After this I did:
mv /system/fonts/DroidSans.ttf /system/fonts/DroidSans_org.ttf
# exit
$ exit
I tried to adb push the fonts but they permission was denied. I them removed the original fonts and thats when the screen went black. I did adb reboot and now the phone wont go past the M logo. Went into normal recovery using the camera, media and power keys. Did a factory reset. Still stuck. I have no idea wtf I did, I just usually follow instructions and everything is fine dunno what happened this time. I dont know how to go back into open recovery and flash the rom again. Any help would be appretiated. Thanks!

You should be able to get into openrecovery by pressing and holding the volume up key while powering on.

Thank you! It worked now to get around to fixing this Thanks again