yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] kagero:
thx

many thx for ur great work and also for the detailed step-by-step instructions from James Nylen for i am thefirst user in austria and nobody knows nothing about the phone ^^

tx alot :):):):)
[G1 Android Development] amir1jk:
ok so i download the file, and renamed it and all i did the alt-s thingy, but then when it says file cannot be loccated. i tried a billons of tiems. im running on rc29, i rooted.

another question. i accendently presses alt-w, and restored my phone i think? do i keep root
[G1 Android Development] zackmpls:
I screwed up while installing a theme, and am now stuck on the G1 boot screen. Would pushing the v1.3 update.zip onto my card in recovery and running the update fix this? If so, I don't know how to push/pull files on the sdcard during recovery. Could someone help me out here? Thanks!
[G1 Android Development] zackmpls:
Never mind. I figured out how to push/pull files in recovery. Applying the RC30 update didn't work. I'm still stuck at the G1 startup screen. Anyone have any ideas? I'm going to start a new thread about this (can't figure out how to delete posts here- sorry for the double posts).
[G1 Android Development] mlevin:
On another forum someone mentioned that after rooting and installing the JF version of RC30, they had Gtalk but not the other IM apps (specifically, they mentioned AIM). Is this right? Are there things missing? If I do a NAND-Backup first, and then restore after rooting, won't I get all the apps back?
[G1 Android Development] tr.slate:
Hey guys, I have successfully rooted and re-bootloadered my G1 thanks to your instructions and hard work. Cant thank enough.
[G1 Android Development] sprime01:
modified rc30 help

when ever i try to install the jesus freak modified rc30 i always gt stuck at this step:

Then “cat /data/local/recovery.img > recovery.img”

the phone would say that the os is read only (when it says that i go to droidsans and make the os read/writeable) after that it always say that the file doesnt exist

also since all my attempts to install my recovery mode doesnt load for the phone anymore it just makes light lines come acroos the screen, is there an automated (.exe) installer somewhere, i don't really want to go back to the regular rc30 without root access for rc29 is too buggy
[G1 Android Development] LucidREM:
seems like you may have missed this step or something:

"adb push recovery_testkeys.img /data/local/recovery.img"

i always like to do "LS" to make sure the file exists before i move to the next step .. just a thought

does using droidsans work? legitimate access to modify the system? that's not a part of the walkthrough
[G1 Android Development] sprime01:
re

the step u mention works when i put it it's the next step the one i posted earlier that doesnt work, and when i use droidsans it does allow me to write on the file but it then says that the file is missing
[G1 Android Development] LucidREM:
no clue dude .. i have an abbreviate set of instructions on my signature .. not sure if that would help you at all
[G1 Android Development] danguyf:
I think I need a period or two in there; I have no clue what you just said.

DroidSans Tweaks doesn't write to recovery.img, so mounting /system/ as rw through it isn't telling you anything.

If it says that the file is missing then THE FILE IS MISSING. Do an "ls /data/local/" to see if it's there; if not then adb push the file.
[G1 Android Development] BennyFlex:
Hi, I'm running rc8, do I need to be root to push the moded recovery image to /data/local ?

I'm using a unit I perchased recently and would like to obtain root access, as I am not root I cannot view the contents of /data/, will I still be able to push to it from adb?

Thanks.
[G1 Android Development] hablam1961:
Question

Hi Guys, If after you downgrade to RC29 from RC33 to gain root access and at the point where you are suppose to see test keys so that you can update to the modified RC30 and you don't . Is it just a matter of the test key being the wrong place, wrong name, corrupt..etc..or is there something wrong..? when I try to start the process over (home & red) the screen stops at the boot screen (red,green, blue & white), it never continues on to the dreamimg.nbh. The phone is on RC29 but doesn't have root access & works fine...Any suggestions..Thanks
[G1 Android Development] McLin:
Can anybody sign an image for me for T-Mobile Germany? I need to Downgrade from RC33 to RC29 and want change the Firmware to US Model.
[G1 Android Development] eviltiger:
Austian Image !!! not rooted !!!

Hi Guys!

i did it!

With this perfect threat http://http://xdaforums.com/showthread.php?t=485364 i was able to root my austrian G1 and do the JFv1.43 thing.

Now, a few days after rooting my G1, its runnin on linux! ;) Wheehaaa! Thx to all the guys which made me able to do my thing!

with best regards

eviltiger
[G1 Android Development] baomobile:
Hello

My G1 had root already,and next step i do recovery mod partition to be able to go next step for HSPL,but when i go to su and get

C:\g1\tools>adb push recovery.img /data/local/recovery.img

1380 KB/s (0 bytes in 1767424.001s)

C:\g1\tools>adb shell

$ su

su

su: permission denied

what was i missing for?

Thanks for your help
[G1 Android Development] baomobile:
I spend 3 days and 3 night already,but still stuck on getting su permission.Can you clearlly step by steps please?I did connect with Putty successfull,but when type su it sayd not found

.

((((then carry out option 5 on page, to copy 'su' to enable root from adb and terminal)))))

i'm really get lost

Thanks
[G1 Android Development] aac2384:
I know this a dumb question

but do you do the codes in the terminal on your computer or on the terminal of your phone? thanks
[G1 Android Development] jacsonmoore3:
man i tried this 10 times i im still on rc29..it just dont make nosense..can u make it easier..damn what the hell im doing wrong..it dont read when i push power+home..i think rooting ur phone is not good if u dont know what the hell u doing..LIKE ME..LMAO
[G1 Android Development] DroidRC1:
k ive rooted my phone and im on jf1.5 but i dont have the recover.img with test keys..so i need to update my recover.img to 1.3..so ive downloaded it i tried flashing it with fastboot and on my computer i get error device not found..so i read this thread and i think i read that u can just place the recovery.img on your sdcard and go to recovery mode and pass alt+S to update or so that wrong wha do i have to do if im already rooted with a hardspl and jf1.5 plz help i like to do a back-up so i can get jf1.5.1..thanx
[G1 Android Development] Denkai:
looking at how the file is set up, I doubt it is signed, there for renaming it update and loading it through recovery is not an option. try using terminal and copy the file "recovery_testkeys.img " to /data/local/ and reboot. I'll try writing a terminal script, tell me how it works.

Copy "recovery_testkeys.img" to SD card root and unmount cell phone.

In Terminal you should get a $, type:

$ su <enter>

After a Permission request (say always) a # should appear

#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#cp -f recovery_testkeys.img /data/local/recovery.img
# cd /system
# cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
#reboot

your system should restart after this, while it is shutting off, press and hold home until your phone boots into the new recovery menu, if you goto bootloader (RGB screen) then something is a miss. yank your battery out and reboot without holding any buttons down at that point to get back into the system.
[G1 Android Development] DroidRC1:
i tried this and when i get to #cp -f recovery_testkeis.img /data/local/recovery.img and press enter..i get cp: cannot stat 'recovery_testkeys.img' : No such file or directory...but i place the recovery_testkeys.img in the root on my sdcard
[G1 Android Development] mattaviles5:
Nothing will flash anymore.

Everytime i put my G1 into recovery mode to do a update.zip i get the error

E:Can't open /cache/recovery/command

and then when i try applying the update with alt+s i get the message

E:No signature (28 files)

E:Verification failed

I've never gotten these messages previously...anybody have advice or know what the problem is?

Thanks
[G1 Android Development] Denkai:
I fixed the script, I did a typo. either case, I suggest moving onto Cyanogens 1.2 recovery menu, much nicer.
[G1 Android Development] corp769:
Are you fully rooted? Most likely you messed something up, i have helped many people out already with this problem. Retrace your steps and make sure everything is flashed correctly and set up.
[G1 Android Development] Amon_RA:
I'm a bit confused...

How exactly is the recovery image using the test keys? I've unpacked recovery_testkeys.img and I don't find test-keys back?

If I would make my own recovery image, how do I tell it to use the test keys? Is it just a matter of signing the recovery.img file?
[G1 Android Development] uries62:
Stuck at SPL

Would a fix like this help someone stuck at rainbow SPL screen? I did an OTA update to 1.6 and restart afterward went straight to SPL. I can't get out of it with normal restart. I have reflashed the phone successfully to RC29 with DREAIMG.nbh, and can access the recovery mode, to conduct updates (Though the CRC1 update fails when it attempts to apply a patch to recovery). When I restart or finish an update though, I get the the TMobile G1 screen followed directly by the SPL screen. No matter what I do, or what update I have applied, I cannot get past this screen.
[G1 Android Development] bigmerchant:
what i am confused about is in any of the direction when it says reboot, etc.. and hit ALT-S or ALT+L, what are they talking about? hit it on my computer in Windows or is it like in a virtual device under the SDK Manager?
[G1 Android Development] brandnew2009:
Yes I can.. ms account
[G1 Android Development] ballaholyk84:
I get this error through cmd on my Vista machine when typing in the fist command "*failed to start daemon* error: cannot connect to daemon"

Maybe I missed a step?
[G1 Android Development] neoobs:
Remember you need to have debug on and the debug drivers installed. So far I haven't heard of debug drivers for Windows 64bit.
[G1 Android Development] humble:
Thanks for the instructions this will be very helpful.:D Maybe you should open an

Instruction thread so that these threads don't become polluted

EDIT: you must have 32bit for the drivers to works so you can use the adb shell

, I used VM to
[G1 Android Development] ballaholyk84:
Sweet haha. Now I have gotten that far and now when i "su" I get "su: permission denied"
[G1 Android Development] alansj:
Ok, well I used essentially that method, but instead of just pasting back into the file in a hex editor I used mkbootimg. This does the initramfs size update for you and just plain seems a bit more kosher.

You want to do something like:

mkbootimg --cmdline no_console_suspend=1 --kernel kernel.gz --ramdisk newramdisk.cpio.gz -o newboot.img

...where kernel.gz was manually extracted from an existing good boot.img (the kernel starts after 2k and ends with a bunch of padding 0's, followed by the gzip magic number 1f 8b showing the start of the gzipped ramdisk)

Ok, that's what I did. I had the cpio flags wrong at first (details here), but once you have the directory ready to go, you can cd into that dir and do something like this:

find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz

Then wrap it all up with mkbootimg (as shown above). I've tested this and it works.
[G1 Android Development] humble:
go here http://www.helloandroid.com/ this will help
[G1 Android Development] ballaholyk84:
Thanks to you and JesusFreke for the help I have now modded it. Here is the final result:
[G1 Android Development] JesusFreke:
Sure, feel free :)
[G1 Android Development] JesusFreke:
Looks like you got it :)
[G1 Android Development] JesusFreke:
Great info there, thanks!
[G1 Android Development] RyeBrye:
my seal of approval

After my thorough review, I give your images my "seal of approval"

Thanks for your work.
[G1 Android Development] humble:
I second that!
[G1 Android Development] ballaholyk84:
Ok guys problem. I am trying to install RC29 and it wont install it because its runningon test keys. Is there a way to basically reverse what you had posted and I had did to the phone?
[G1 Android Development] SGTDavePwnage:
Great work on the Modded recovery and boot images people :)

Has anyone had any joy creating one for the UK RC7?

Im not sure if T-mobile in the UK have started the update process to give us the equivalent of rc30 yet but i cant imagine it will take them long.

I've already renamed otacerts.zip & cacerts.bks and Updater.apk	& Updater.odex to deny any update they bring out, but it would be nice to get the phone up and running a modded recovery/boot image for when the time comes (hopefully leading to a modded version of whatever locked down firmware they lump the UK owners with).

Any help would be GREATLY appreciated by the UK owners
[G1 Android Development] neoobs:
I have an issue with trying to load a new Update... it won't let me mount the SD card... Anyone else have issues? I have mounted it before and updated.

I am beginning to hate that screen.
[G1 Android Development] quedijo:
It can't mount the SD card, in other words it can't access.

It's an issue that has to do with the SD cards that came with the G1.

One option is to wait a minute before you Alt+S.

Other is to format the SD card through the phone through your computer.

Now try again.
[G1 Android Development] neoobs:
I know that... But this isn't the stock one... this one worked perfectly before (I updated manually to RC29) but now it seems to not want to update. I believe there was a change to the recovery image which might be the issue. JesusFreke can you help?
[G1 Android Development] stephen.n.nikki:
I am having an issue can anyone help? I have gotten to the last step and am getting the following output/error.

flash_image recovery recovery.img

Can't find recovery partition

Can someone tell me what to do next and why I'm getting this error?
[G1 Android Development] JesusFreke:
Huh.. weird. type in

cat /proc/mtd

on your phone. The output should look something like this:

dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"

Is yours any different than that?
[G1 Android Development] stephen.n.nikki:
Yep, mines different.

I get

# cat /proc/mtd

cat /proc/mtd

dev: size erasesize name

mtd0: 04000000 00020000 "system"

mtd1: 04000000 00020000 "userdata"

mtd2: 04000000 00020000 "cache"

I aint about to brick my phone am i?
[G1 Android Development] JesusFreke:
Hrm.. You've definitely got something screwy going on..

I would suggest that you update (or re-update) to the official RC29 update, and then try the cat /proc/mtd thing again and see if you get the other 3 partitions.
[G1 Android Development] stephen.n.nikki:
I have the official rc29. Do I have to have debugging enabled? Could that be the reason? What about the steps I've done so far? Will they have adverse affects on my phone?
[G1 Android Development] JesusFreke:
Also, try

ls /dev/mtd

how many devices do you get? There should be mtd0-mtd5
[G1 Android Development] stephen.n.nikki:
I get,

# ls /dev/mtd

ls /dev/mtd

mtd2ro

mtd2

mtd1ro

mtd1

mtd0ro

mtd0
[G1 Android Development] JesusFreke:
I don't think debugging would make a difference. But it might. *shrug*

I honestly don't have a clue why you wouldn't have the recovery or boot partitions listed. I'm at a bit of a loss..

The steps that I listed, before flashing the recovery image, shouldn't hurt your phone. The only semi-permanent (i.e. permanent between boots) change is that the replaced recovery.img. But you can change that back easily enough.
[G1 Android Development] stephen.n.nikki:
Ok, so maybe rebooting my phone will help huh?
[G1 Android Development] JesusFreke:
I dunno.. it's possible that it won't boot back up. Not likely I don't think, but possible.
[G1 Android Development] stephen.n.nikki:
uhhh, any steps to ensure that it will boot back up?
[G1 Android Development] JesusFreke:
I hate to say this.. but nothing that I can think of.. There's something screwy going on with your phone, and I'm 99% sure it doesn't have anything to do with what you did so far to install the recovery image. If the missing partitions are a pre-existing problem, it is probably safe to reboot (since you would most likely have already rebooted with the problem in place).

I don't really even know how your phone could have gotten in that kind of state though.

Anyone else have any ideas?
[G1 Android Development] stephen.n.nikki:
Right, what I mean is are the files changes that I just made going to be the reason why my phone won't boot if it won't. And if so, can I reverse what I did to be sure that it wasn't these changes.

btw, I didn't make any other changes for it to get like this.....
[G1 Android Development] JesusFreke:
I can't see any way that the changes you made would have caused that. The only thing I could thing of is if you had some typo or something. But even then, I don't see how it could have caused that.

The only reason I say it might not boot is because if something happened to your recovery and boot partitions, your phone wouldn't be able to boot. But most likely the partitions are actually physically there on the flash, they just aren't showing up for some reason. If that's the case, the phone should boot fine.
[G1 Android Development] stephen.n.nikki:
well then here comes a reboot, we will see.
[G1 Android Development] stephen.n.nikki:
woo reboot went fine.....
[G1 Android Development] stephen.n.nikki:
Hey, I did cat proc/mtd and everything showed up....
[G1 Android Development] JesusFreke:
Great! You should be able to pick up where you left off.

That was certainly strange. At least it turned out ok :)
[G1 Android Development] stephen.n.nikki:
Ok, now I am getting an error after picking up where I left off and trying to boot into recovery mode. I get

android system recovery utility E:can't open /cache/recovery/command
[G1 Android Development] JesusFreke:
That's normal. You can ignore that error.
[G1 Android Development] stephen.n.nikki:
great so I got it! Thanks alot JesusFreke, you been such a great help.
[G1 Android Development] im.l0ltn:
Worked perfectly on the first try. You're the man ! :)
[G1 Android Development] UnkzDomain:
When I try this on my phone with RC29, when I type "su" in the adb shell, it says "su: permission denied." I'm getting the prompt for the RC30 update, but I keep denying it, so any help would be appreciated
[G1 Android Development] JesusFreke:
See here for how to create the su command
[G1 Android Development] momentarylapseofreason:
Ugh.... my phone is trying to update...

I am at a complete loss even after reading all 7 pages. Actually, think I am more lost than when I began.

Even though I don't need root access (wouldn't know what to do with it), I want the option to learn what can be done.

Can someone please give a *dumbed* down version of this? From what I gather, I need to get the SDK? Never used it before...so a step by step on that as well?

I generally hate people like myself..but need to hurry before my phone updates and is lost forever.

I am attempting to install the *first* package and it's coming up "not signed 8 files"
[G1 Android Development] foltz61:
I know this is possible but, is it likely that Tmo could use the keys posted here and push an update to us. They would basically have to know who is jailbroken and who isn't. Correct? Otherwise, non jailbroken users would get an invalid update.
[G1 Android Development] Fared:
http://androidcommunity.com/forums/f28/i-have-rc30-and-root-6867/
[G1 Android Development] momentarylapseofreason:
THANK YOU THANK YOU THANK YOU!!!!

Got it done!!!
[G1 Android Development] bhang:
? bump

would this be possible at all, we would have to change our keys on board but then resign the update.zip with those test keys...

please ignore me if im just talking out of my a$$, I dont know much about code/scripting

Im doing some reading and installed the sdk, cause I doubt an easy way (root for dummies style) wont be seen for a bit... and I aint learning doing it that way... my quest continues

bhang
[G1 Android Development] ecpcorran:
If I understand this correctly please let me know.

If I replace the recovery image I will still get OTA updates, and even if I get RC30 I will be able to use this recovery image to replace the OS if I so choose in the future using full modified builds of the OS that use test-keys.

Also by replacing the image I screw myself out of manually updating my phone using the official patches (if they ever use the update.zip method as a supported update option in the future) unless I somehow revert to the previous recovery image.

I also assume that if I ever do go to a modified OS build, I won't be able to revert to an official one using even the original recovery image as only patches, not the full OS, have been found for download using the official certs.

Right?
[G1 Android Development] John5788:
I've successfully applied the modified RC30 update by flashing the recovery_testkeys.img file in and updating using the modified update.zip, thanks!

question: if I wanted to go back to unmodified system where I can receive OTA updates again, basically undo these changes and go back to stock, how would I accomplish this? just sign the next update.zip from google unmodified with the test keys and let the thing go normally?
[G1 Android Development] JesusFreke:
That's one way to do it, yes. Or you can grab the recovery image from one of the official updates and flash it, and then apply the official update.
[G1 Android Development] johnowa636:
Help

I try to run command:

"cat /data/local/recovery.img > recovery.img"

I get error:

"/data/local/recovery.img: No such file or directory" :(

like previous post i have the following:

dev: size erasesize name

mtd0: 00040000 00020000 "misc"

mtd1: 00500000 00020000 "recovery"

mtd2: 00280000 00020000 "boot"

mtd3: 04380000 00020000 "system"

mtd4: 04380000 00020000 "cache"

mtd5: 04ac0000 00020000 "userdata"

What am I doing wrong? Thanks for the help.
[G1 Android Development] JesusFreke:
I'm guessing you didn't do the first step

adb push recovery_testkeys.img /data/local/recovery.img

Alternately, you can copy recovery_testkeys.img to your sdcard, and then do

cat /sdcard/recovery_testkeys.img > /system/recovery.img

instead of

cat /data/local/recovery.img > recovery.img
[G1 Android Development] johnowa636:
yea user error. got it to work now. Thanks.
[G1 Android Development] BAD_BOY_KIEV:
It still sais READ ONLY FILE SYSTEM when i try co replace the img with the testkeys one....
[G1 Android Development] BAD_BOY_KIEV:
Plz need HELP!!!!

And also:can I SOMEHOW make do not to go to internet for update request?? It's eating my money on traffic (I'm in Europe)
[G1 Android Development] HagbardCelineII:
So I've installed this and thought everything went fine. But when I try to type telnetd, then go into the terminal and "connect to server", I get an error message about not being to connect to host 127.x.xx. (I can get the exact message if needed). This was working for me everytime before I updated. I was running RC19 before.

Have I done something wrong? Can you no longer get to root this way?

When I reboot into recovery mode, it does say that I'm using test keys. I also reinstalled the image from here and got the same problem.
[G1 Android Development] momentarylapseofreason:
If it's connecting to 127.0.0.1 (loopback), sounds like your WIFI is off
[G1 Android Development] JesusFreke:
The bug where you could just type "telnetd" to start a telnet server was fixed in RC30 (and the fix is included in my modified RC30). To get root, you can connect to the phone with "adb shell" through USB, or get the terminal emulator program from the market, and type "su".
[G1 Android Development] HagbardCelineII:
No, it's on. That's what I thought at first too.
[G1 Android Development] HagbardCelineII:
Whew. I was getting worried I screwed something up.

Lemme' try that and I'll be back.