Database Develop

Installing ROOT Help

ok i got this far
8. Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
and on the last command i get a error "cannot create /system/recovery.img"
am i rooted already ????? or what needs to be done please help...
files i have on sd card are recovery.img and update.zip

read the threads and follow them step by step....STEP by STEP....

Verify that you command prompt has a "#" in front and not a "$"
# = root
$ = user.
make sure you type in mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system exactly like that. and be sure that it does not return any errors.
again type these in EXACTLY as shown.
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
if you still have the problem, please respond.

i am following everything step by step and cant get it i just get cannot create recovery.img read only file system

if its not working then you arent following the steps correctly.

cat recovery.img > /system/recovery.img
i get this after ## is that a good thing???

if you are using the crappy built-in windows telnet client.. it will appear like this:
Code:
# # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# # cd sdcard
# # flash_image recovery recovery.img
# # cat recovery.img > /system/recovery.img
# #
i recommend you use putty. Putty Homepage
this provides a cleaner telnet interface.
but yes.. that means it worked!
EDIT:
Now to explain just a bit what just happened:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system :: this mounts /dev/block/mtdblock3 in /system (lots of fun stuff available here, but i recommend you leave that to developers
flash_image recovery recovery.img :: this flashes the recovery image with JesusFreke's custom recovery image.
You should now proceed to downloading a modded RC30 (also available on this forum) and place it in the root of your SD card. Rename it to update.zip and turn off your phone.
Press (and hold) the Home and Power(red) keys until you see the recovery screen. Now slide out the keyboard and press ALT+S.
After it's complete press ALT+W, and reboot.
WARNING: this will wipe out all previous custom settings and restore you to factory defaults!

Ok, so I've decided I want to root my G1 too, and I'm having a similar problem. I broke my first G1, huge crack on the screen, but still functional. I have a replacement in hand, but want to test rooting on the old one so I don't risk the new one till I know I get it right. I had OEM RC30 installed and flashed down to OEM RC29. No problems there. Then I restarted, following instructions to the letter. Typed in "telnetd" :enter: No problems there. Downloaded Telnet app from the market and connected to local host on port 23. No problems. I even had the ## prompt. After typing in the commands listed in the tutorial with no problems, I installed HardSPL and update.zip into the sdcard and did all that. Then I upgraded to JF RC30. Now when I open the Terminal Emulator program, I get the $ prompt. What did I miss? Should I flash back down to RC29 and try again? I think I will just in case I'm an idiot, which is entirely possible.

polaris0352 said:
Ok, so I've decided I want to root my G1 too, and I'm having a similar problem. I broke my first G1, huge crack on the screen, but still functional. I have a replacement in hand, but want to test rooting on the old one so I don't risk the new one till I know I get it right. I had OEM RC30 installed and flashed down to OEM RC29. No problems there. Then I restarted, following instructions to the letter. Typed in "telnetd" :enter: No problems there. Downloaded Telnet app from the market and connected to local host on port 23. No problems. I even had the ## prompt. After typing in the commands listed in the tutorial with no problems, I installed HardSPL and update.zip into the sdcard and did all that. Then I upgraded to JF RC30. Now when I open the Terminal Emulator program, I get the $ prompt. What did I miss? Should I flash back down to RC29 and try again? I think I will just in case I'm an idiot, which is entirely possible.
Click to expand...
Click to collapse
type su in the terminal emulator. you'll get the # prompt.

Right... I'm just stupid. So I'm running 1.41 on my old G1 now. Nicely done, it feels just like the ota version (no hiccups or bugs so far) and I have multi touch. You're awesome jf!

or do it through pc like intended.. and remount

am having this problem but it says
recovery.img: no such file or directory
##
i am using rc8 uk model please help

For those still having trouble rooting there is an app that can root your G1 with "1 click", that's not what I used to root my phone but I hear it works I bet if you look for it you'll find it

Add root to ROM

Hello,
I have created a ROM, but it does not have root access - how do I add root access to this ROM?
Thanks,
Isaac

From what I remember you need to go to Terminal, and type in:
Code:
telnetd
After that...
# Download an Android "Telnet" application from the Market and connect to localhost.
# If you connect successfully, you will have a root prompt "#".
# Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
That's only for RC29 though, and in RC29 it executed anything you typed in, so you are supposed to type it into the home screen. More info here:
http://forum.xda-developers.com/showthread.php?t=442480
Hopefully it will work on the ROM you worked on as well.
Good luck!
Big fan of your app, btw.

i want a SiriusXM player, and got mad you didn't have one,

isaacwaller said:
Hello,
I have created a ROM, but it does not have root access - how do I add root access to this ROM?
Thanks,
Isaac
Click to expand...
Click to collapse
Boot into the recovery console (power + home) and then drop into the shell (alt+x).
Then do this:
Code:
# mount system
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot

Thanks! That worked perfectly!

Urgent Help required Rooting

Hi Guys,
I am having a problem with rooting my G1, For the last hour I have been stuck at the point where I have downgraded the phone to the RC7 successfully and am trying to press enter twice and type the telnetd.
At this point I'm not sure if it should give me a sign that it has worked but I then goto telnet command prompt which is showing some questions marks them the # sign but when I type in the commands from the instructions the following happens: Typed exactly as it appears on my screen
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# #cd sdcard
# #flash_image recovery recovery.img
No such file or directory
# #flash_image recovery/sdcard/recovery.img
usage: flash_image partition file.img
# #cat recovery.img > /system/recovery.img
recovery.img: No such file or directory

Try reading this: http://forum.xda-developers.com/showthread.php?t=442480
Its sounds like you havent put the recovery image in your sdcard.
read the instructions again.

I placed the recovery image and the zip file in the sd card, but i was thinking of sacking this method and trying the root.apk method.

rename cm-recovery-1.4.img to recovery.img on your sd card
-OR-
flash_image recovery cm-recovery-1.4.img

The file is called recovery.img

Ok I rebooted the phone pressed enter<reboot>enter again and the phone rebooted, so now I have root what next, do I need to do anything else before putting on a rom, what rom should I put on?>?????

http://androidcommunity.com/forums/f12/rooting-your-g1-made-easy-11825/
faster and less complicated

gtrplr71 said:
http://androidcommunity.com/forums/f12/rooting-your-g1-made-easy-11825/
faster and less complicated
Click to expand...
Click to collapse
Thanks worked

no problem

Problems getting into recovery image on rooted Nexus

Hey guys,
I rooted my Nexus one but I have a small problem getting into the recovery image.
In the modaco instructions you have this red text
Check if there's no /system/etc/install-recovery.sh script if you keep booting back in the stock recovery (exclamation mark with a little Android).
This is exactly what is happening to me and all I would like to know is....
How can I make this exclamation android disapear?
The file /system/etc/install-recovery.sh is there... but can I delete it or modify it somehow?

Why not use fastboot and flash the recovery?

I actually tried to do that but I have the same problem when trying to boot up in recovery.

Actually finally managed to get into the recovery image just now after using fastboot to flash the image once again.
However after rebooting the phone I still have the same problem. So basicly, this works if I just flash it, power off phone and run the custom recovery image. After that I get the little android with the exclamation mark.
Just to show what I do when flashing the reccovery image.
Superboot aquired
Code:
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
I get success on this and my root access seems to work. (I am only running Market enabler to make it work)
Code:
Copy recovery-RA-nexus-v1.7.0.1.img to a location where fastboot can find it. ( Put this in my home folder under superboot\recovery-RA-nexus-v1.7.0.1.img
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your [B]MAC[/B]
./fastboot devices (to make sure that fastboot "sees" your phone)
./fastboot flash ./recovery recovery-RA-nexus-v1.7.0.1.img
So, I continue... Any idea why I am still getting the little Android? I have

also
hjaltih said:
Hey guys,
I rooted my Nexus one but I have a small problem getting into the recovery image.
In the modaco instructions you have this red text
Check if there's no /system/etc/install-recovery.sh script if you keep booting back in the stock recovery (exclamation mark with a little Android).
This is exactly what is happening to me and all I would like to know is....
How can I make this exclamation android disapear?
The file /system/etc/install-recovery.sh is there... but can I delete it or modify it somehow?
Click to expand...
Click to collapse
same problem with me i can not do it!

Well look no further becouse I have found the solution to our problems.
Superboot again and start with
Code:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Then you type
Code:
rm /system/etc/install-recovery.sh
Now follow instructions to install the Recovery image
After this you will hopefully not have any problems

help
sorry to bring this back... but, i need some help here...
when i enter $ su... i get "permission denied"

You need to have root access, google it or look in the development section for guides.

Cannot remove /system/etc/install-recovery.sh
Nexus One FRF91, unlocked and rooted.
SDK and USB driver installed, Windows XP.
Using ConnectBot I can see /system/etc/install-recovery.sh is present
I recovery boot into RA-nexus-v1.7.0.1
fastboot and adb both see the device.
adb remount returns remount failed: Invalid argument
If I go into adbshell and try mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system I get failed: Invalid argument
Have I missed something?
Any help would be most appreciated!

I can work around it with adb shell, still puzzling why adb remount will not work though...

[APP] DropBear Server II // ssh/scp (root only)

I wanted to enable SCP and SSH using DropBear II ... for some reason DropBear Server II doesn't install scp & ssh binaries, you can get them from github and symlink it into system. Here's what I did...
DropBear archive (1M): https://www.dropbox.com/s/h2guipuvdltiden/dropbearii.zip
Feel free to mirror that if you want.
These directions allow you to ssh into the system as root, be very careful. I recommend not leaving the service running if you are not using it.
I take no responsibility if you brick your unit while mucking around as root.
Back Up
Download dropbearii.zip and unzip on your local file system.
From your local filesystem install the APK and push scp & ssh to tmp.
Code:
adb install DropBearServer2.1.apk
adb push scp /data/local/tmp/scp
adb push ssh /data/local/tmp/ssh
From the OUYA GUI install the DropBearServerII service... Select Make -> Software -> DropBearServer II -> Install
Shell into your OUYA and make /system writable.
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
Move scp & ssh into DropBear II directory
Code:
mv /data/local/tmp/scp /data/data/me.shkschneider.dropbearserver2/app_data/
mv /data/local/tmp/ssh /data/data/me.shkschneider.dropbearserver2/app_data/
Change the permissions
Code:
chmod 6555 /data/data/me.shkschneider.dropbearserver2/app_data/scp
chmod 6555 /data/data/me.shkschneider.dropbearserver2/app_data/ssh
Create the symlinks
Code:
cd /system/bin/
ln -s /data/data/me.shkschneider.dropbearserver2/app_data/scp ./scp
ln -s /data/data/me.shkschneider.dropbearserver2/app_data/ssh ./ssh
Change /system back to read-only (optional) and exit.
Code:
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
exit
exit
Reboot the OUYA (optional)
Code:
adb reboot
Notes/testing
Windows users can use Putty to ssh & scp get them here.
To ssh into the system:
Code:
ssh [email protected]_ADDRESS
To scp a file to the sdcard:
Code:
scp ./some_file [email protected]_ADDRESS:/sdcard/
To get to settings push the U circle button one time.
If you turn on "Start on boot" in the settings menu and reboot, the service will be turned off. Though it will be left on in the standard standby mode.
I recommend using pubkey rather than password. Basically generate a public key and push it into /sdcard/ then install it from the DropBear II app.
Unix Hosts can do:
Code:
ssh-keygen -t rsa
Windows using PuttySSH follow these directions, I haven't tested them though.
If you don't want to be bothered with pubkey, please change the default password it is set to 42.
If you already know about pubkey, you can cat them into: /data/data/me.shkschneider.dropbearserver2/app_data/authorized_keys
Unchecking "Allow Password" doesn't work properly.
Why would I want to do this? I didn't really like the Wireless ADB disappearing after the OTA upgrade, this may be less annoying if the next OTA doesn't nuke it.

I'm getting an error that busybox is not installed when trying to start the service. Is there anything special you had to do with busybox to get this to run? I installed it via the apk.
Edit: Nevermind. I didn't realize the busybox apk was an installer and I didn't find the icon when I looked. Just checked again and found the busybox installer icon and did a smart install. Dropbear ssh is running now.

I ran it manually with
Code:
dropbear -E -s -P /data/dropbear/dropbear.pid -r /data/dropbear/dropbear_rsa_host_key -d /data/dropbear/dropbear_dss_host_key
and it looks ok when idling but when connection it gives me
Aiee, segfault! You should probably report this as a bug to the developer
Click to expand...
Click to collapse
This could be CM10.1 environment issues (libc). The built-in SSHd doesn't work properly as well. Some binaries give strange errors when executed with SSHd (like sqlite3).

I can't install the DropBearServer II from the Make option, comes up with "operation failed". Tried to make the system rw to see if that might have been the problem but still no luck. Anyone else had that problem?

andlid said:
I can't install the DropBearServer II from the Make option, comes up with "operation failed". Tried to make the system rw to see if that might have been the problem but still no luck. Anyone else had that problem?
Click to expand...
Click to collapse
I installed it via adb.
For others I was able to install using IncognitoMan's -=StockPlus=- ROM -- http://forum.xda-developers.com/showthread.php?t=2347214
You may need busybox installed, I'm not 100% sure, I haven't tried without busybox.

SSH command line on android
The link is broken

Could someone please reupload this? would be awesome
Thank you so much

BIade said:
Could someone please reupload this? would be awesome
Thank you so much
Click to expand...
Click to collapse
bump - upload again please

You can also get static binaries from dropbear or ssh server apks in playstore by simply unpacking the apk.