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
Related
I can enter the first two commands, mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system,flash_image recovery recovery.img and cd /sdcard but when i type in the last command i get this
cannot open /system/recovery.img no such file
Don't know what you're typing there.. missing some stuff.
Try this:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system
cat /sdcard/recovery.img > recovery.img
flash_image recovery recovery.img
Did you type SU before??
i did what the first reply did. what do you mean su?
i got it thanks
SU = root access.
Once you have rooted your phone and installed a custom image, you need to type "su" and press enter anytime you go to the command prompt to do something requiring root. Basically root is disabled by default so you don't break things - you need to specifically tell the phone you want root access to try and avoid breaking things by mistake.
Anyway, glad you got it working.
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
I ve noticed that many people have posted having problems with keyboard layouts after flashing a rom. I have a German G1 which was rooted to Cyanogens 4.2.14.1 before, and I never had problems keeping the phone in English but retaining the German keyboard (I ve gotten use to it).
But after flashing Super D just now (which is AWESOME), my keyboard has defaulted back to the U.S keyboard, which is really annoying.
Anyone know exactly why this problem didnt exist in Cyanogens rom and why it does exist with SuperD? Also, Im assuming this is something I have to live with, as I couldnt find an easy fix for it? I really just want the German keyboard back.
Any help would really be appreciated.
1.SuperD isnt Cyanogen
2.Most Likely in the scripts that have to do with the keyboard.
Hope that didnt sound rude but yeah =/ You would probably have to change something in the system/usr directory.
I had the same problem and solved it like so:
1.) DL and unzip the zip file I have attached
2.) copy the file to your SD card root folder
3.) open a Terminal Emulator app and type the following (press Enter after each line and allow if it ask for permission):
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/usr/keychars/
dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin
4.) Reboot your phone.
5.) Profit...
You will have to do this after every ROM flash, but it literally just takes a few seconds, so not worth mentioning.
kugelfish said:
I had the same problem and solved it like so:
1.) DL and unzip the zip file I have attached
2.) copy the file to your SD card root folder
3.) open a Terminal Emulator app and type the following (press Enter after each line and allow if it ask for permission):
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/usr/keychars/
dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin
4.) Reboot your phone.
5.) Profit...
You will have to do this after every ROM flash, but it literally just takes a few seconds, so not worth mentioning.
Click to expand...
Click to collapse
This is exactly what I tried, but after the "dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin" command in terminal, I get an error that says:
"cannot open for write: Read-only file system"
Not sure what Im doing wrong. I unzipped the file, put it on sd card, and entered in the commands.
I heard this method works for everyone, but for some reason I get this error when i try it.
Sadly, I'm not to familiar with linux or coding in general, but I would assume something went wrong when remounting. Your system folder seems to remain read-only...
Maybe someone more qualified can help with the right command line... ?
Edit
make sure there is a space between mtdblock3 and /system like so (shown red):
mount -o remount,rw /dev/block/mtdblock3SPACE/system
kugelfish said:
Sadly, I'm not to familiar with linux or coding in general, but I would assume something went wrong when remounting. Your system folder seems to remain read-only...
Maybe someone more qualified can help with the right command line... ?
Edit
make sure there is a space between mtdblock3 and /system like so (shown red):
mount -o remount,rw /dev/block/mtdblock3SPACE/system
Click to expand...
Click to collapse
Still no luck. I double checked, and its typed correctly. I tried swapping this command:
mount -o remount,rw /dev/block/mtdblock3 /system
for this one:
mount -o rw,remount /dev/block/mtdblock3 /system (found in another thread)
but it still didnt work. After I tried using the "mount -o rw,remount /dev/block/mtdblock3 /system" command that I found in the other thread, I didnt get the error, and thought this may have fixed the keyboard. But when I rebooted, the keyboard was still wrong.
Sorry dude, that's all I got. All I can say is, it works for me.
Maybe this'll help?
http://www.handy-faq.de/forum/htc_d...ogle_g1_qwertz_tastatur_wiederherstellen.html
try: mount -o rw,remount yaffs2 /system
bubonik said:
try: mount -o rw,remount yaffs2 /system
Click to expand...
Click to collapse
It worked!!! Thanks to everybody for all there help. It was this one command line that made all the difference!
So nice to have a keyboard again where all the keys actually display what they are supposed to. It was driving me crazy.
Thanks again guys
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...
I have...
Nexus one
FRF91, android 2.2
Radio: 4.06.00.12_7
Recovery: Recovery-RA-nexus-v1.7.0.1
I fallowed all the steps on unlockr.com to root my N1. I see the Superuser Permissions installed, but I still don't have root access. I attempted to delete the amazon mp3 app from my phone with the fallowing command:
adb remount
adb shell rm /system/app/*amaz*
and I'm replied with a Read-only error. Also, when I installed Titanium Backup, i was not able to gain root access after SU prompted me for permission (i allowed).
I have tried to re-root the device, but I'm told by superboot (updated FRF91 version) that the device has been rooted.
you gotta remount the /system to make big changes like that..
so you would go
mount -o remount,rw /dev/block/mtdblock3 /system
rm /system/app/amazon.apk
and should remove it from there.. you can also get terminal emu from market and use that with in terminal
ilostchild said:
you gotta remount the /system to make big changes like that..
so you would go
mount -o remount,rw /dev/block/mtdblock3 /system
rm /system/app/amazon.apk
and should remove it from there.. you can also get terminal emu from market and use that with in terminal
Click to expand...
Click to collapse
I just got the N1 yesterday, was on the MT3G before it. Another little step I need to remember.
Thank you, it worked perfectly.
np and welcome