Database Info

error routing please help

Hi, i am currently experiencing problems with my g1 (uk rc8/now rc7) I follow all the instructions and I now have rc7 on my g1, however I am stuck at this point:
Instructions:
5. After your phone starts up, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
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
I type telnetd>press enter, nothing happens. I thought that was fair enough, so went to market and downloaded telnet, and clicked connect for localhost 23. I get a message saying:
'error while connecting to server: localhost/127.0.0.1:23 -connection refused'
followed by:
'error while receiving from server: null'
What am I doing wrong?

I'm having this same problem with rc33 and my system is modded already I'm trying to end some apps with task manager and It says something like unable to connect to host ..... blah blah I went to telnet and I get the same error you get.

@tucka20: Try typing the telnetd command in soon after a fresh reboot. If you do it after the system has been booted up for a long time it may not work.
@Lamar720: already rooted don't need to work through telnet. Just open Terminal Emulator and do your work there.

jashsu said:
@tucka20: Try typing the telnetd command in soon after a fresh reboot. If you do it after the system has been booted up for a long time it may not work.
@Lamar720: already rooted don't need to work through telnet. Just open Terminal Emulator and do your work there.
Click to expand...
Click to collapse
I don't understand how but, I tried it again after I went to T.E. and typed in
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and Task manager is now terminating apps ..... Thanks

Lamar720 said:
I don't understand how but, I tried it again after I went to T.E. and typed in
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and Task manager is not terminating apps ..... Thanks
Click to expand...
Click to collapse
Wait are you on official RC33 or modified/rooted RC33? If it's the latter then yeah you cannot perform those operations. Need root access.

Task manager is now terminating apps ..... Thanks
jf 1.41 rc33 lite it works telnet doesnt but the task manager does.

Sorry I had a mistype in the first post I meant now not not . lol thanks again

problem

i have a problem, for some reason i cant go to recovery mode. i have JFv 1.42_RC33... what can i do

What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?

Iceucold said:
Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
That made even less sense.

forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?

kydcleric said:
forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?
Click to expand...
Click to collapse
i dont know im new to this stuff but what happens is that the g1 boot screen pops up when i press home+power then it just restarts and shows the g1 boot screen again then it goes to the normal home screen

Iceucold said:
What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
i dont know what u mean

Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery

Iceucold said:
Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery
Click to expand...
Click to collapse
nothing happens i put that in there and it just shows a money sign under it.. and when i just put reboot it says
reboot: operation not permitted

You are holding down home first right? I.e. press home and hold it down and then press power(I continue to hold home down all the way up until I see recovery mode starting)

Can you check if the recovery image (/system/recovery.img) is intact?
if you're using the haykuro builds, it is known that reboot won't work from terminal emulator. but you should be able to reboot recovery through adb shell.
I remember I read somewhere that certain bootloaders have a different key sequence for recovery mode, but i've never seem any of them.

ooooo crap i just checked it and there is no recovery.img in there ok what do i do??

someone plz help me out

probably best to dl the one from the Rooting Hacking & Flashing... post. They have a link to the file there. Just dl it and, as su, copy it to the folder they say.

what post???

Cosine said:
what post???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=442480

yea but thats only to get to root and i already did that... and i just tried it and it dosent work

Cosine said:
yea but thats only to get to root and i already did that... and i just tried it and it dosent work
Click to expand...
Click to collapse
The suggestion was to try restoring the recovery image as outlined in that thread: (though you shouldn't need to do the "telnetd" part)
Instructions:
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
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
Now you have root!
Click to expand...
Click to collapse

so should i just try
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
in the terminal emulator

[GUIDE] Safer way to unroot and revert to stock myTouch 3G 1.2

This method we will use nandroid's recovery option in ClockworkMod
Requirements:
Rooted myTouch 3G 1.2 with USB Debugging
ClockworkMod Recovery Installed (can be install from ROM Manager)
Universal Androot apk saved to your AndroidSDK tools folder
(I will be doing this in adb)
Create the recovery folders
Code:
mkdir /sdcard/clockworkmod
mkdir /sdcard/clockworkmod/backup
mkdir /sdcard/clockworkmod/backup/Stock
Mount the SD card so you can access it on your computer.
Now extract SAPPIMG_Sapphire_T-Mobile_US_2.10.531.4_release_signed.zip (from shipped-roms) [FYI: I had to use 7zip for this] into clockworkmod/backup/Stock.
Now we are down with that unmount it and return to adb.
Once your phone has remounted the SD card do:
Code:
cd /sdcard/clockworkmod/backup/stock
md5sum * > nandroid.md5
cd ../../../
cat /system/bin/flash_image > flash_image
(If you do not have flash_image post here in this thread and I will pm you a link to it)
Reboot the phone and boot into recovery mode (hold home when powering on)
Once in there
**DO A FULL WIPE**
then restore the "Stock" backup from the restore menu,
It should get past boot and system then fail on /data THIS IS NORMAL
It is not safe to reboot your phone
Set up your phone and all that good stuff, then re-enable adb debugging.
in a command prompt cd to your androidsdk/tools folder and run
Code:
adb install UniversialAndroot.apk
and reroot your phone (bare with me)
once that is done do
Code:
adb shell
su
be sure to click allow on the Superuser Permission pop up that shows up on the phone
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd ..
cat /sdcard/flash_image > flash_image
chmod 0700 flash_image
./flash_image recovery /sdcard/clockworkmod/backup/Stock/recovery.img
rm flash_image
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
exit
unroot your phone via universal androot and uninstall it via the applications menu
reboot and done!
I have done this a couple times and every time it worked like a charm.

Hey there, I get to inputting the md5 command, but I get cannot create nandroid.md5: permission denied
What am I doing wrong?

Using a SAPPIMG.zip is not at all unsafe and is faster and easier.

Well, I have been trying to use the sappimg.zip from unlockr's guide and on the t-mobile dev forums, but yet all of them end up giving me a Main version is older! error.
I cant seem to find the solution.

I've had the same problem. I have made the gold card a million times (worked rooting the phone) and now it tells me the older error. Thought it would be easier reverting back, guess that's not true.
Anyways, can I get the flash_image file?

getting past the "older version" error
what i did to get past the "older version" error, was this:
step1: re-use gold card and the 1.5 version sappimg.zip from unlockr.com
step2: reboot using the original sappimg for t-mobile (i wont link from the post but i found it on XDA aka use search)
this will reload EVERYTHING as stock MT3g1.2 including original splash, and recovery images.

if you want to revert it to stock, try this: http://forum.xda-developers.com/showthread.php?t=641174, it may help

The safer way is to NOT BOTHER.
The update schedule is to run from today through the 25th inclusive. That's 11 days. The average length of time that any particular user will have to wait is therefore 5.5 days. Chances are that the update will be posted by tonight or tomorrow (latest), and 10 minutes later, it will be fixed so that it doesn't rob you of root (keep your options open!).
So... you save about 5 days of waiting (average) and end up with your options wide open. OR, you can commit to the average and end up locked out, possibly forever.

I like the way you think...
Sent from my T-Mobile myTouch 3G using XDA App

Need eng spl
bartcrusades said:
well, i have been trying to use the sappimg.zip from unlockr's guide and on the t-mobile dev forums, but yet all of them end up giving me a main version is older! Error.
I cant seem to find the solution.
Click to expand...
Click to collapse
just got through doing the same thing tried goldcard method and still got main version older....then i got it right...flash eng spl i beleive it was 0010 then do the sappimg.zip it works and when you finish the update your 0013 spl is back...then used universal androot installed superuser then installed rom manager and made backup of stock then put my phone back the way it was hopefully when the update comes out and i do think it will be a long time before it does i can restore backup of stock unroot with universal androot and uninstall superuser. At least thats the plan. If you want to do this look for kennys posts in the sappimg thread his directions are what i used.

That is the correct way to do it. Eng spl then tmo stock image. When done its back to completely stock.
Sent from my T-Mobile myTouch 3G using XDA App

hey i do not have flash_image can u post up a link? thanks.

[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

[Q] Nexus S (rooted) does not save clockworkmod recovery after reboot

Hi,
I have followed all of these steps theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/[/url] up to VI. Stop the Phone from Uninstalling the Custom Recovery Image. After I shutdown the phone I hold the volume up and press the power to go into fastboot however when I press recovery, the clockworkmod does not save and just boots the stock recovery. Once I type in adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh I get mount: Operation not permitted.
I hope someone can help me. Thanks to whoever is reading this.

shuandroid said:
Hi,
I have followed all of these steps theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/[/url] up to VI. Stop the Phone from Uninstalling the Custom Recovery Image. After I shutdown the phone I hold the volume up and press the power to go into fastboot however when I press recovery, the clockworkmod does not save and just boots the stock recovery. Once I type in adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh I get mount: Operation not permitted.
I hope someone can help me. Thanks to whoever is reading this.
Click to expand...
Click to collapse
I have the same issue and my work around was to install Jrummy's ROM Manager and Flash recovery and reboot from within the APP itself.
Hope this helps.

adding the line, prior to the mount command:
su
for superuser access did the trick for me when I was getting this problem