Related
Hello everyone,
first off, I'm new to all this. Here's my situation,
I was trying to install a new ROM on my G1 and I found instructions on how to gain root access to my phone. I felt like I had followed the instructions but I can't seem to get the ROM installed on my phone. I downloaded Recovery Flasher and installed it. I chose "Backup recovery image" and then "Flash Cyanogen Recovery 1.4" and it all seemed fine, but then when I rebooted my phone and tried to install the new ROM it wouldn't let me. But I think I know what the problem was, I missed the step where I had to rename the folder of the ROM to "update." I went back to factory settings and tried to re-do the steps but this time, Recovery Flasher gives me the options to:
Download Recovery Image
Restore Backup Image
this confuses me because it's not the same as it was the first time I tried it. Does this mean my phone is already rooted? I tried to uninstall and install it again and same 2 options come up.
I know i was doing it right at first because I got all the correct screens that I saw on the instructions, but now I don't. I've been searching here and all over google to see if I can find an answer but I couldn't so I decided to make a thread to see if someone can help.
Thanks!
AFAIK the one-click method doesn't survive a full reboot, because when you reboot the OS it overflashes the recovery partition again with the original (unless you've flashed a new ROM)
Now your problem seems to be the "folder" bit. You do not unzip the ROM, you put, eg, "update-cm-4.0.4-signed.zip" on your SD card as-is. You also no longer need to rename it to use from this recovery partition.
I see,
well, when I tried it with update-cm-4.0.4 (that's what I was trying to install) it said that the file could not be found, and then I read that I'm supposed to change the file name to "update" and when I did that, it found it right away but it gave me the error "No Signature" (something along those lines) even though according to the place where I download it from, it is signed.
Should I just try to boot into recovery mode again and try it out again? I remember the very first time I tried it loaded the screen with a bunch of options, but now it just has 3, Boot Into Home, Wipe, and Apply SDcard zip, I might be wrong on the exact wording of those options but that's all I get...
and recommendations? Thanks for your response
nevermind, I got it to work! Thanks
Ok, let me start off by saying my phone is currently not bricked. I can get into recovery(H+P) or fastboot(C+P) just fine. My problem lies with the last step of rooting when I flash the new ROM. I am currently trying to flash v4.2.15.1 which is apparently the latest Cyanogen Mod.
Now I've tried two different methods and both won't boot after the ROM is flashed.
The first method is "method B" seen over at the AndroidAndMe website. This method works fine and I can get back into the phone all the way to the point of flashing the SPL and then the ROM. It installs fine, but after reboot it gets stuck on the G1 startup screen.
The second method is the wiki guide for updating from original OS to Cyanogen. This one is a bit different using the Android 1.6 base image. The installation on this method goes smooth up untill the last reboot after flashing the ROM just as the other method. The difference here is instead of it hanging at the G1 startup screen, it get's just past that to a blank backlit screen. No images, no android logo, no sound, no nothing.
Like I said before, I can still access recovery and fastboot which seams to be my only way out. I have repeated this process multiple times on both methods with the exact same results. Fastboot keeps bringing me back to the Android 1.0 firmware(RC29) which is atleast giving me access to a phone while I try to figure this out.
Suggestions? Ideas? I really need to get this phone working again.
I am always on AIM "DeathstarsOG" if that is more convienient for those offering up some help.
What steps did you take to flash the rom?
Did you read the steps outlined in his wiki? The most important step is to flash DRC83_base_defanged.zip first, then his rom over the top.
dbl post sorry.
evilkorn said:
What steps did you take to flash the rom?
Did you read the steps outlined in his wiki? The most important step is to flash DRC83_base_defanged.zip first, then his rom over the top.
Click to expand...
Click to collapse
I followed the steps on both writeups exactly how they were written. As far as the wiki one, I already had a few of the files needed from trying the Androidandme method. Also, my phone is basically already downgraded to the RC29 so thats another step i can skip. All needed files are already on my SD card and were installed in the following fashion:
DREAIMG.nbh
cm-recover-1.4.img
DRC83_base_defanged.zip
update-cm-4.2.15.1-signed.zip
ota-radio-2_22_19_26I.zip
My SD card is already formatted to FAT32
I set up the telnet to get access to recovery mode, wipe phone, then install DRC83, then the cm-4.2.15.1 and lastly the radio. I do a Home+Back reset after installing the radio and it goes past the G1 Startup screen, to a black lit screen of nothingness.
If you're looking at the wiki guide named: "Full Update Guide - G1/Dream Firmware to CyanogenMod" you'll see I basically am supposed to be seeing a update screen that loos like a open box with an arrow pointed down toward a phone after I do this reboot. Well, that doesn't happen. It just goes to that black screen.
Now I'm not a whiz when it comes to stuff like this however I can figure things out fairly sufficiently for the most part. But this has got me stumped. It sounds like I may have a corrupted version of Cyanogen as everything else I have been able to install and actually run on the phone(besides the DRC83). Or maybe I need to flash the radio before the DRC83? I haven't even gotten to the SPL, and after all this I may not want to.
I've done this process over and over atleast 8 times and I feel like I basically know every step by heart, but I still don't want to just guess at what it could be and risk a brick. So that's why I'm here. What do you guys think could be the issue?
Do not wipe the phone after istalling RC29. nbh file rewrites everything, and I mean it... everything.
Here's your order:
DREAIMG.nbh
Boot, sign-in, obtain root (telnet, connect to local host, you know the shpill).
Flash recovery (use ra 1.6.2, it's more updated then cm 1.4)
Wipe
Flash DRC83 defanged.zip
Flash ota radio, follow directions on the screen, you will need to reboot at least once
Flash 1.6 rom (cyan's is a good one to start at least)
Fix permissions.
Wipe
Reboot
Do not set-up linux swap or apps2sd at this time, it will complicate the process more then needs to at this point, you can do it all later.
Good luck.
borodin1 said:
Do not wipe the phone after istalling RC29. nbh file rewrites everything, and I mean it... everything.
Here's your order:
DREAIMG.nbh
Boot, sign-in, obtain root (telnet, connect to local host, you know the shpill).
Flash recovery (use ra 1.6.2, it's more updated then cm 1.4)
Wipe
Flash DRC83 defanged.zip
Flash ota radio, follow directions on the screen, you will need to reboot at least once
Flash 1.6 rom (cyan's is a good one to start at least)
Fix permissions.
Wipe
Reboot
Do not set-up linux swap or apps2sd at this time, it will complicate the process more then needs to at this point, you can do it all later.
Good luck.
Click to expand...
Click to collapse
You my friend are a genius!
Maybe the write-ups for rooting should be re-written to follow this as it worked flawlessly.
I started all the way back from step one at the default G1 1.6 Firmware.
Downgraded to the RC29.
DL'd telnet from the market.
Installed the new RA-recovery
Wiped.
Flashed DRC83.
Flashed Radio.(promted me to reboot)
Flashed the ROM.
Fixed Permissions.
Wiped again.
Then reboot.
Process went flawless, no hicups or anything. Thank you very much sir!
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
JohnPublic said:
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
Click to expand...
Click to collapse
try amon ra recovery, full wipe including dalvik and flash one of the roms you listed above, like cm6.1 stable (from cyanogenmod.com) with the gapps (from jaybob413's rom thread in hero development). once it starts the boot, give it time, it may take a long time (10 min.) Hope it works.
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Now don't I feel silly! I re-downloaded CM6.1 and put it on the card and it seems to be firing up. I'm on the CM logo bootscreen right now. I have no idea how three separate zips all got corrupted en route to my card, but I suppose that must be what happened. Thanks for the help!
JohnPublic said:
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Click to expand...
Click to collapse
have you tried re-downloading the roms? it sounds like something is missing in them, which shouldn't be. if you are downloading from your phone, try a download from a computer and see what happens. where are you dl'ing the roms from? verification failure makes no sense..... also, did you recently update rom manager from market to 3.0.0.7? there was something listed in the changelog about verification failure fixed when using other recovery, i think....
EDIT: saw your last post, maybe your browser was acting up? delete the bad ones, get new ones, flash away
Hi,
I just wanted to update manually to Gingerbread.
But I am truly confused with all the version jibber jabber...
My Android version is 2.2.1, Build Number FRG83D and Kernel is 2.6.32.9-g6624e39 [email protected] #1.
My phone is from german Vodafone Company. Maybe it is because of the language? But I do not care about it, use only English anyhow.
Can I update?
Obviously I can not with the just released file, cause I get a "cannot verify".
Or do I have to wait for another file and why?
Thanks!
Do you have Vodafone or Stock Google Android installed? This update works not on the vodafone version.....
You're not even on the latest version of Froyo, of course you won't be able to use the Gingerbread update.
Update to FRG83G with the last link in this post: http://forum.xda-developers.com/showpost.php?p=11618364&postcount=947
Direct link to FRG83G (from D) http://android.clients.google.com/p...igned-passion-FRG83G-from-FRG83D.2854b06b.zip
How do I switch to the lates stock version that I can update Gingerbread to?
I thought I updated manually to the latest version before...
I really hate this part of Android
edit: oh thanks to the above, guess I'll try that
Brownbay said:
Update to FRG83G with the last link in this post: http://forum.xda-developers.com/showpost.php?p=11618364&postcount=947
Direct link to FRG83G (from D) http://android.clients.google.com/p...igned-passion-FRG83G-from-FRG83D.2854b06b.zip
Click to expand...
Click to collapse
This fails to verify too
Can anyone lead me to a way to get to vanilla Android so I wont be bothered with this **** again?
DarsVaeda said:
Can anyone lead me to a way to get to vanilla Android so I wont be bothered with this **** again?
Click to expand...
Click to collapse
it seems to me that you are not on the stock android ROM, but you are on a special vodaphone version of the ROM. if this is true, i highly suggest that you get rid of that ROM. that means you should root your phone, gain superuser acces, and install ROM manager.
ROM manager will now let you easily flash a variety of ROMs, just like an official OTA update, and including the stock ROM. so from ROM manager you could switch to stock if you wish, which would let you upgrade to gingerbread. or you can switch to cyanogen, or any other ROM you see in the list.
by far its the best thing to do.
Okay this are the steps I figured so far, if I follow them will I be able to update to Gingerbread?
Any step I forgot?
- Root with this method http://forum.xda-developers.com/showthread.php?t=959672 (yeah I'm on ubuntu)
- then I "download the FRG83 system image from http://developer.htc.com and use fastboot to flash over the system and boot images"
- then I run the update the Gingerbread update
DarsVaeda said:
Okay this are the steps I figured so far, if I follow them will I be able to update to Gingerbread?
Any step I forgot?
- Root with this method http://forum.xda-developers.com/showthread.php?t=959672 (yeah I'm on ubuntu)
- then I "download the FRG83 system image from http://developer.htc.com and use fastboot to flash over the system and boot images"
- then I run the update the Gingerbread update
Click to expand...
Click to collapse
That is what I had to do to get mine working...
So you may help me out cause i'm stuck again.
I have rooted via SuperOneClick now, cause the linux one did not work, blame it on eclipse...anyway.
I installed RomManager as suggested above, but there is no FRG83 to choose from.
So i downloaded the FRG83 from HTC and choose that with RomManager. But it does not install, just backups then reboots and nothing changed.
I also tried to do it manually but if i go to fastboot i can not do anything.
There are only Bootloader, Reboot, Reboot Bootloader and Power Down.
I named the downloaded zip (http://dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip), root.zip and placed it in the root of the sd-card.
What am i missing?
DarsVaeda said:
So you may help me out cause i'm stuck again.
I have rooted via SuperOneClick now, cause the linux one did not work, blame it on eclipse...anyway.
I installed RomManager as suggested above, but there is no FRG83 to choose from.
So i downloaded the FRG83 from HTC and choose that with RomManager. But it does not install, just backups then reboots and nothing changed.
I also tried to do it manually but if i go to fastboot i can not do anything.
There are only Bootloader, Reboot, Reboot Bootloader and Power Down.
I named the downloaded zip (http://dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip), root.zip and placed it in the root of the sd-card.
What am i missing?
Click to expand...
Click to collapse
I downgraded to stock from my laptop.
You go into fastboot on the device and then on your computer run commands like:
Code:
fastboot flash boot boot.img
and
Code:
fastboot flash system system.img
.
Fastboot in this case is used to restore the stock images from your computer to the device.
You then need to re-apply all the updates.
Just flash the full stock Gingerbread ROM from the dev section. Easy peasy.
http://forum.xda-developers.com/showthread.php?t=968396
Hi all,
I have exactly the same problem as DarsVaeda, and also the same specs:
Nexus One (Vodafone NL)
Android version 2.2.1
Build Number FRG83D
Kernel version 2.6.32.9-g6624e39 [email protected] #1
HBOOT-0.35.0017
RADIO 5.12.00.08
I've been trying to find a solution for the problem but trying to update to FRG83G gives me the same error message:
Finding update package…
Opening update package…
Verifying update package…
E:failed to verify whole-file signature
E:signature verification failed
installation aborted
if someone has a solution, please post it here
I believe Vodafone tweak their ROMs, so you can't install the update. You will need to revert your phone to complete stock, or root and flash files through a custom recovery, our unlock the bootloader and fastboot flash...
Sent from my Nexus One using XDA App
Yep he's right.
I am on gingerbread now.
I rooted with super one click.
Then installed rom manager.
Flash a custom recovery (ie. at the bottom).
Downloaded stock FRG83G from HTC.
Booted into the recovery and installed the rom.
Afterwards I could update to gingerbread.
No downsides yet.
You can also flash the stock gingerbread rom now. Saves you one step.
It's linked here in the forum.
Sent from my Nexus One using XDA App
So there is no way around it? if I want Gingerbread on my Nexus I have to root it or wait for Vodafone.
I'm unsure about rooting, never done it before and I'm a noob in this field, but I really, really want the update
If you don't mind, DarsVaeda, and in the light of your success with that method, could you maybe post an even more detailed step by step instructions of how you did it?
Sure.
First of all I lost all data that was not saved remotely. Like SMS or application data from applications that do not remotely store data. Keep that in mind! But it's worth it.
I backup SMS to my google account anyway and delete them after some time from my phone, so I was fine with that.
As far as I know now you do not void your warranty if you root with "SuperOneClick". The root will also be gone after you flashed the rom. On my phone there is only a program called "superuser" left, but it's not usable since the phone is not rooted anymore.
Step by step:
before get all of this:
- get and install the USB Android drivers on your WindowsOS explained here (and download): http://developer.android.com/sdk/win-usb.html
- install "RomManager" from the market on your phone
- get "SuperOneClick" here: http://forum.xda-developers.com/showthread.php?t=803682
- get the Gingerbread Stock ROM: http://forum.xda-developers.com/showthread.php?t=968396
- rename the stock rom to "root.zip" and place it on the SD-Card, top level
1. on your phone goto Settings -> Applications -> Development -> check "USB debugging"
2. connect phone with USB to your Windows machine (drivers above should be installed and Windows should recognize the phone)
3. fire up SuperOneClick and click "root", wait until it tells you it wants to run a test
3a. if it fails to root the first time, just hit root again (I had to do it, after second try it worked)
4. restart the phone after it is rooted
5. back in Android start RomManager
6. in RomManager flash a custom recovery, I took the one at the bottom (something with alternative recovery, second last entry)
6a. it might want you to install additional software, allow it
6b. it will ask you for rights, allow them
7. after the flash is finished boot into the recovery (second entry from top of rommanager)
8. in the custom recovery navigate to the point where you can apply an update with a zip file (in the one i took it was the second entry I guess)
9. after you choose the entry you can choose the zip, choose the "root.zip" and apply
10. now the installation should start with verifying and then actually applying the rom
11. restart the phone
11a. if you are now stuck in the start animation (the one with that floating x-thing) and it does not go on you have to reset all you data (factory reset)
11b. power off the phone and start it with pressing the power button and volume down
11c. a screen appears, navigate to "recovery" and hit the power button (you have to wait till it loads something, then you can press that)
11d. in the new screen there should be an option called factory reset, if not it is like "wipe all data" -> that's when you loose all your data (I had to do it)
11e. reboot the phone
12. Gingerbread should boot now
Feel free to ask any questions if you have. Hopefully I can help.
I did not use the stock rom directly, guess that saves you one step.
If it does not work, but I guess so you have to do the same as above but install this rom first:
http://dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
After you installed it boot the phone and check if the version is correct: Settings -> about phone.
If so get the Gingerbread update (http://android.clients.google.com/p...signed-passion-GRI40-from-FRG83G.81304b2d.zip) and place it on the SD-card as "update.zip".
Boot to the recovery, same steps as the factory reset. There will be an option "apply update.zip". Use that and after it you will also have Gingerbread.
Wow! thank you so much for the step by step guide, I really appreciate it now I feel more confident to attempt the feat of updating.
You don't need to root to update.
Follow the wiki guide to unroot/restore using the passimg method for FRG33, then install the updates to FRG83, 83D, 83G, then finally Gingerbread...
Sent from my Nexus One using XDA App
I have difficulty installing the cyanogenMod 5.0.7 ROM for the G1. I tried installing it thrice over 3-4 days and still cant get over it. I initially had Jesus Freak 1.4.2, from which, I tried installing DangerSPL, although to no avail, from then on, the phone seemed bricked. Hence, I renamed the CyanogenMod ZIP file as update.zip, and retried installing it by pressing home+power. Although I got the error that the script file couldn't be found.
Therefore, I freshly installed the official Android 1.0 release from here: code.google.com/p/android-roms/wiki/Unbrick and again began the process of rooting, and installing the CyanogenMod ROM. Although, I rooted the phone by watching the videos (youtube.com/watch?v=xOo2V9qCauc) and (youtube.com/watch?v=ua8ljJAnTpc) .
Following which, I think, I installed the radio updates.
I then installed Amon Recovery from following the steps: (bit.ly/eMyBlL) and then the DangerSPL (bit.ly/f2xkvp)
It again seemed the phone was bricked since, it didn't went past the G1 logo. But still I went into recovery via home+power, after I reattempted as earlier, by renaming the .zip file (from computer) to update.zip. and then inserted it into the SD card slot. But it still gave out the same error:
Code:
E:Can't find update script
Installation aborted
Bear in mind that, the recovery utility is not the one where there is a HTC logo on the background, but rather, the one with the exclamation mark within the triangle logo. So there is no choice to flash ZIP files which are not named update.zip
I'm thinking I will again start from scratch, and got back to the official release of Android 1.0, and keep upgrading till the last official one which is, 1.6. Therefore in the meantime, do throw away advice on how to properly root and install CyanogenMod 5.0.7 on the T-Mobile G1 with a different network.