Database Develop

This can't be happening... [SOLVED]

So today i finally get the gusto mod my phone Android Dev 1. After downloading all the files and following the instructions here i can't get past the black g1 screen (#8). note i can also get the the rgb screen. thats it, but with so many different posts with similar issues, my brain is pounding. At this point if i can get beack to factory, ill live. what i'll hate is the fact that bricked my phone. i'll most likely get screamed on for not searching, but i think i may be searched out. any help would be appreciated.
thanks.
docfu.

first of all dont freak out lol. Download the dreaming.nbh or w/e file from the rooting instructions and place it at the root of the sdcard. Then get into the rgb screen (Camera + Power) and flash it. That should get you back to factory settings. If not, download the update.zip for w/e region you are in place it on your sd card. Enter recovery (Home + Power) and flash the update.

ok...so i tried the DREAMING file and it kept turning up no image found, alternatively i'm not sure what you mean by w/e region update. i ihavent come across that in my searches.

ok dreaming file did infact work. i feel better knowing that the phone isnt bricked. however after running the update when it prompts for action, i hit the trackball and i'm right back at the rgb screen..AGGGHHHH! sorry. i've been at this since 3pm this afternoon.

Chill. Don't freak. You can't just jump in and do something as soon as your read it. Read the whole thing and if you don't have the patients for this work on that before you work on this. bbreath.

I must say start by saying thanks guys. i stepped back, and actually took my [email protected]@ to bed. Rest does wonders. That said. I've accomplished the factory reset. so i back to a stock g1, and boy does it suck. As stated my phone WAS a dev 1. i've already started the upgrade process, my question at this point is where do you recommend i go from here. back to dev 1 or try one of the other roms. i've already installed the spl, and right now im stuck at the telnetd part of the root process. and this too may have me screaming by the end of the day...
any thoughts would be appreciated.

After the recovery image is installed you need to update the radio if you want to install a cupcake 1.5 ROM. You can get it here, rename 'update.zip', place on the SD card and boot in to recovery and flash. Then flash a ROM of your choice. You should be able to do that on RC 30, but I'm not sure if you need to install a rooted image first, so I'd wait for someone else's input before trying that.

I played it extra safe and used the rc29. as far as i know the proper radio is installed. i'll wait around before i do something stupid. thanks for the input tho. i'm trying to learn everything.

ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.

Future reference ^-^
In case you encounter this problem in the future, cause it can happen with flashing new roms if you skip a step:
You're only bricked if you are stuck at the G1 boot screen but can't get into recovery or fastboot, adb or anything. In cases where you can still get to other phone options to start over, rest assured your phone does still work, just need to step back and figure it out, which you did in this case with a little help ^-^ First few times doing anything to my phone, I went into panic mode a couple of times thinking I bricked until I read around and found out otherwise.
Just in case you didn't know these things, if you did, well, hope it was a nice read? ^-^

doctorfugazi said:
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Click to expand...
Click to collapse
Well... if you actually purchased a dev phone it should not be sim locked.
Technically... after the rooting process, we all have dev phones with the exception of the sim lock.
So... what SPL are you using?
What ROM are you trying to install? Some roms you should consider partitioning your sdcard.
What radio do you have?
First thing is first.
Get the 1.4 recovery if you haven't done so already. 1.4 Recovery
Because this allows you to select any .zip file without having to rename it to update.zip. This saves on confusion so you don't try flashing a spl (like danger spl )before a radio (could brick your phone).
Second
You need the 1.5 radio to use cupcake. 2.22.19.26I
Third
Consider an spl. You have 4 choices. HARDSPL (Recommended), Eng SPL (what the dev phone defaults with.. skateboarding androids), the standard spl (nondev) and Danger SPL (risk bricking but worth it because you have more memory for your ROMs and can try HERO builds).
Fouth
Find your rom. NOTE: Read each post carefully! If it says you need a specific spl then get it! Otherwise it won't work. Some require the Danger SPL. If you chose a JF rom then you should be alright and don't even need to partition your card and it will work just like the OTA release. Some (such as Cyanogens 3.9.7) are experiemental and are not recommended for noobs.
Fifth (and probably the most important)
ALWAYS BACKUP WITH NANDROID!!!
In the event that you think that you've bricked your phone. I would say that there is a 90% chance that you didn't. As long as you have a nandroid backup and can get to the bootloader then you still have a phone. Just make sure the fastboot.exe file is in your sytem32 directory of your computer. Open CMD and cd to your fastboot backups saved on your computer. Simply
fastboot flash boot boot.img <enter>,
fastboot flash system system.img <enter>,
fastboot flash userdata data.img <enter>
fastboot reboot <enter>
and you should be back to where you were immediately after the point you backed up. Think of it as a system restore for Windows. It couldn't hurt to have a few backups stored.
If you have any questions or problems include information for us to read in a single post and edit as necessary.
Example:
AT&T
Cyanogen 3.9.7 Rom
Recovery 1.4
HARD SPL
Radio 2.22.19.26l
8GB class 4 sd card (7gb fat32/900mb ext3/100mb swap)
Theme version if any.
That way we know what we are working with.
Happy flashing.

rest assured i was in panic mode yesterday. but honestly the only thing i could really do was just step back for a while, meaning get some rest tackle it with a clean head. its frustrating for sure. this one guy tho who posted in the brick think tank thread...just cuz he couldnt figure things out in an hour he got pissed and started screaming waste of time this that and the other. total BI$CH! I was like whoa. I was at that point too. but Im not tryna be that guy.
Now, if could just figure out if i have to start from scratch, i just might be able to get my phone working again in time fro me to go to work tmrw morning.

So... what SPL are you using?
the hard SPL found here
What ROM are you trying to install?
Well i was trying to follow suggestion on something simple, like one of the early jesusfreke's. if i can step it up sure why not. but i'll pass on the partitioned sdcard setup for now.
actually I'll run with JesusFreke JFv1.51 US CRB43
What radio do you have?
radio number listed in my previous post.
Hey thanks by the way for taking the time out of your day to respond to this. i know u guys get your fair share of spazmiesters, so i appreciate it totally.

after doing research it seems that all the current roms require partitioning. or is that optional just for running apps to sd?

partitioning is optional of apps2sd for preformance. some like myself have three partitions, the third being for a linux swap

Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)

doctorfugazi said:
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
Click to expand...
Click to collapse
Okay... you have the recommended recovery and spl.
So all you need to do is get your rom and radio and store the zip files to the root of your sdcard. You don't need to rename them.
Just boot in recovery (power+home) and scroll down to:
[Alt+A] apply any zip from sd
And then you should see the zip files.
Upgrade your radio first.
Then your rom.
Another note... make sure you have a data plan once you've installed your rom. Depending on your rom version, you may not be able to sign in without one. If you can't sign in, you can't use your phone which is why most would recommend a custom rom or an adp rom.
Now... if I'm not mistaken... you do NOT have to partition your sdcard to install a rom (unless it's a HERO rom).
You may want to consider doing so however.
The advantages are that you can have virtually unlimited storage for apps and it's much easier to restore them after a wipe because they are still on your sdcard. Some apps will recognize the partitioned sdcard and automatically do all the apps2sd work for you by default. It is also recommended that you use at least a 2gb class4 card at MINIMUM. Any slower then a class 4 may result in system crashes and errors. Any less then a 2gb card is almost not worth all the effort since you'll likely be using at least a quarter of it for the apps2sd. I would suggest buying at least a 8gb class 6 card for less then $50 online. It's both fast and plenty of storage. With apps to sd, if you do need to wipe you still have all of your apps installed. A great advantage of having apps2sd.
Also... try different roms! There are DOZENS out there! Some have the htc music installed, some have myfaves, some have special cameras, etc. Don't be afraid to experiment. As long as you have a backup and can get to the bootloader (skateboarding androids) and a pc, you can't go wrong! If fact... with the 1.4 recovery you can store several different roms on your sdcard, backup your current rom, wipe, flash a new rom to try it, wipe, flash a different rom to try that one, etc. If you decide that you didn't like any of those... just restore back to your previous backup. Simple as that. No pc needed. However having a pc is handy to get logcat information if it's not booting for some reason.
Speaking of roms not booting... while your experimenting with various roms... you MUST have patience. Sometimes (based on my personal experience with about 10+ different roms) they can take up to 15 minutes to boot up. You can literally be staring at the ANDROID or HTC logo this entire time. Unless you are using ddms.bat or adb shell logcat, you will be clueless of whats going on. DO NOT do anything unless you get the infamous "boot loop". This will be obvious. It will stick at the ANDROID or HTC screen for a while and then blink and go back to the logo. If you see it blink and go back to the logo then try pressing power + talk + menu to restart it and then immediately press the home button to bo back to recovery. Wipe... try again. This time it should work. If it doesn't then restore your backup while you research on that partitcular rom. You may have skipped a step or not have the proper requirements (partitioned card, spl, etc).
With all of that said... good luck and you'll be posting help to other users like yourself before you know it.

Hey Doc, if I'm not mistaken (other guys correct me if I'm wrong), if all, and I mean ALL you have is a boot loader (AKA SPL. ie// skating androids or colored bars) you need to reflash dreaimg.nbh to get a system back.
This ALSO flashes your SPL and RADIO back to default so reflash your radio and SPL afterward. (IN THAT ORDER I HOPE)

Binary100100 is a gentleman and a scholar
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.

innerspace said:
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
Click to expand...
Click to collapse
Thank you! I do what I can.

Unable to flash Anything else

i have done quite a few searches on this and yet have found nothing so i hope i dont get reamed for posting this.
if someone has a link for this answer id be very thankful.
if not then PLEASE SOMEONE EXPLAIN!!!!!!!
at the moment i am running drizzy hero rom. to do the update i did use the one touch root. on a second phone i did it manually. on both i added the hard spl and am running the RA v 1.2.1 recovery. I liked this ROM and wanted to see what bugs it had. after a few days i wanted to switch and try a different ROM I have dl most of the ROMs available and already have them on my sdcard once i did this no ROM would load except for Drizzy(new Vision v2.8). after trying a few things and accomplishing nothing i decided to redo EVERYTHING. unrooted my phone rooted again applied recovery made sure radio was to date and spl. and still nothing i cant even run the original jf1.5 that i was using before deciding to port. this issue is occuring on both phones. 1st phone was again done with one step root and the 2nd phone was done completly manually. I REALLY REALLY REALLY want to try these other roms SO PLEASE SOMEONE HELP. if you need more information on what i did with these phones ill gladly tell you step by step on what i did.
sorry for that.
I was using my G1 and also had a friends. On my g1 i used the one step root. I used the Instructions from The Unlocker.com. It uses flashrec.apk and also Amon Ra's recovery image. After that i went over to the How to Load a Custom ROM. same site. It asks you to check the Radio and the Spl. The radio is 2.22.19.26I and the spl used was the HARDSPL 1.33.2005.
Once i finished that i went and formated the sdcard to Fat32+Ext2+LinuxSwap also converted Ext2 to Ext3.Then I did-Move Dalvik Cache to SD. last 3 steps to speed up hero. after all of that I loaded 4 ROMS CyanogenMod ROM, jACXHeroSkiv Hero ROM v1.8, Drizzy’s NewVision TouchFlo ROM, and JF v1.5 Cupcake ROM. I have only flashed Drizzy's until last night.
I was unable to flash any other one and when i flashed back to drizzy I had problems loading it back but eventually loaded fully the issue was running the startup wizard it kept crashing. after a reboot it was ok.

Give us step by step on what you did and USE PARAGRAPHS
that whole thing looked like mumbo jumbo to me
put new lines where they belong to help separate out the steps you took

FIXED! thanks!

hobbitton said:
FIXED! thanks!
Click to expand...
Click to collapse
did you do a data wipe? you need to wipe going from hero to cupcake/donut

When I first did all of that I did. Am I supposed to data wipe everytime I switch the Rom?

hobbitton said:
When I first did all of that I did. Am I supposed to data wipe everytime I switch the Rom?
Click to expand...
Click to collapse
when your using hero rom's, yes.
if your upgrading cupcake roms (ie cyan 4.0.4 to 4.1.9.2 ), no
If its not working, WIPE
you cant go from hero to cupcake without wiping and not expect a lot of problems. they cause too many issues.
hero roms use the data partition differently

also remember to wipe /system/sd/ to clear all of that out. pull your /system/sd/ to your computer first though

thanks you guys it helped alot

help!!!! i searched for hours and cant fix it

my phone is stuck in a reload state i put jac xreroskiv rom or what ever its called and its stuck it starts up but keep saying hero over and over any ideas. help please thanks in advance i had already installed hero and such was just trying this new rom. i tried other roms too but no dice. even the original hero rom i originally put on here.

You should probably make a post for help in the rom's forum that you're having problems with.
Also, it would help if you told them which G1 device you had, what radio/spl and stuff like that.
But with really no info from your post the only things I can think of is that you need to do wipe or reformat your sd card.

Most likely you just have to repart your ext partition. But more info would help.

i have radio-2.22.19.261 hboot-1.33.2005 dream32b i was able to restore it but now i cant install the rom . i tried again and got the same problem so i probably got the wrong radio for the rom i want which is this one http://forum.xda-developers.com/showthread.php?t=534479\

You have the right radio. Really there is only one radio. There's the 26I that we use and the old radio that is not used anymore. Do not flash the hero radio or you will brick your phone. Did you repartion your sd card so it's fresh?

yeah i used the home and end button and did the partition using the boot loader thingy. i ended the loop but now its like i bough the phone new with root make sense?

mad82109 said:
yeah i used the home and end button and did the partition using the boot loader thingy. i ended the loop but now its like i bough the phone new with root make sense?
Click to expand...
Click to collapse
Not the least amount of sense to me, but if your phone is working ,then good. You had a bootloop which is usually solved by wiping your ext3 and phone.

maybe i have the wrong build? i had some ra build cant remember what it was called i reflashed to cyanogen 1.4 gonna try it when i get home

mad82109 said:
maybe i have the wrong build? i had some ra build cant remember what it was called i reflashed to cyanogen 1.4 gonna try it when i get home
Click to expand...
Click to collapse
all you had to do was wipe ext3, you should do this when changing any hero build unless otherwise noted. be sure you are wiping the intern. memory as well ALT+W in ReCon. also, repair ext filesystems and flash again, hero roms take a while to boot so make sure you are patient.

okay ill try when i get off work. i have 1.33.2005
2.22.19.26I my build is cyanogen + jf 1.4 can i install the rom i discussed earlier using the method u talked about? it was slow when i installed it earlier anyway of making it faster kept loading.

i fixed it dont know how lol but i did. i think i just had the wrong build. close thread plz. thanks for all the help people.

mad82109 said:
i fixed it dont know how lol but i did. i think i just had the wrong build. close thread plz. thanks for all the help people.
Click to expand...
Click to collapse
I kept seeing you say you were trying to flash the cyanogen build 1.4. That is not a rom but the recovery. But glad its working now. Put [SOLVED] on your thread title.

G1 - Failed CyanogenMod help appreciated

I will start off with the issue is i probably messed up something and more importantly I am probably over my head.
Basically my G1 will not get past the tmobile screen. I have let it sit up to 35 mins in between flashing on this screen.
Before i touched it today, I had a working version of CyanogenMod, and before that the 1.5 of JF. The version of CyanogenMod i had I don't remember, but it did have all the standard google features including work email, but was not able to be updated via the CyanogenMod Updater app if that helps.
What i did.
I went out to CyanogenMod and downloaded update-cm-4.2.3-signed.zip and renamed it to update.zip and placed on the root of my SD card. I deleted the previous version that was there that flashed sucessfully last time.
I then restarted the phone holding Home and Red - did a wipe and applied the image. Nada - did it again. I have attempted to do so 4x's now. I can get into the that mode just fine.
Booting with camera yields the following
DREA100 PVT 32b
HSPL10.95.3000
CPLD-4
RADIO-1.22.12.29
OCT 20 2008
Any help gents? I appreciate it.
White G1 - 4 Gig SD Card - T-Mobile Service -
Thanks!

do u have a nandroid back up? if not once this is resolved u should grab the latest recovery 1.4 i believe that can do back ups and restores with out much work. have u tried flashing a different rom back onto your phone again to try and get that to work?

Thanks for the reply and I will look into the backup.
I did take my SD card out and dump it all to my pc. I started looking around and it appears I made a backup of the original CyanogenMod i did in september. I then took my sd card - wiped it, and put that one on it.
So now im back working again, which i can live with, but I wonder what I did wrong with the last one or why it wont work.

If your cyan was pre-4.1.99, You have to flash the ADP recovery image as the instructions state
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs

B-man007 said:
If your cyan was pre-4.1.99, You have to flash the ADP recovery image as the instructions state
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
Click to expand...
Click to collapse
Thus where I failed. Thanks for pointing that out, I ran through this pretty fast assuming it was like the previous install. Again Thanks! I will take sometime and go through it slowly tonight.

Knowledg said:
Thus where I failed. Thanks for pointing that out, I ran through this pretty fast assuming it was like the previous install. Again Thanks! I will take sometime and go through it slowly tonight.
Click to expand...
Click to collapse
Frankly, before you go through upgrading to a more recent ROM, and since you have a working rooted phone at the moment, I'd take the time to upgrade to the latest Radio (you're on the old 1.22.12.29 according to your post), newest SPL (Haykuro's "Danger" SPL), and recovery partition.
First update to a new Recovery... I recommend Amon_RA's latest 1.3.2. It simplifies backing up and flashing immensely. He's built Backup and Restore Tool into the Recovery, so you can essentially make an image of your phone and ext partition and restore within minutes if you screw something up (short of bricking your phone of course).
Next, I would upgrade your Radio and SPL (in that order). Follow the link in my sig for directions. Remember though... RADIO, THEN SPL. If you do SPL then Radio, you'll brick.

Need help with installing rom coming from root

I just rooted my g1 and i'm having problems trying to install cms rom.
some info;
DREA100 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO-2.22.19.26I
Oct 20 2008
I installed cm's recover 1.4 img and have access to the recovery screen no problem.
Tired installing AP1.6 but can't confirm it got installed.
I did this..
wipe
flashed signed-dream_devphone_userdebug-ota-14721
wipe
flashed cm 4.2.7.1
goes to the T-mobile screen, then it loads up cm's boot screen then after where it should take me to the setup screen, it turns gray/black and stays there.
please give me some imput on what i'm doing wrong.
Thanks!

You wipe, then you flash the ota update. Reboot and it will go back into recovery by itself. from there you install cm, without wiping. Reboot and you are good.

Ok i've done just that.
wiped
flashed ota, it goes back to recovery image
i flash cm 4.2.7.1
reboot and it does the same thing.
t-mo logo loads up. then cm's android bootscreen loads up.
then it goes gray/black and stays there.
i know im doing something wrong but not sure what... should i install a older cm rom first? since i'm coming from a fresh rooted g1? i was coming from rc29

RegulatorG1 said:
Ok i've done just that.
wiped
flashed ota, it goes back to recovery image
i flash cm 4.2.7.1
reboot and it does the same thing.
t-mo logo loads up. then cm's android bootscreen loads up.
then it goes gray/black and stays there.
i know im doing something wrong but not sure what... should i install a older cm rom first? since i'm coming from a fresh rooted g1? i was coming from rc29
Click to expand...
Click to collapse
it shouldn't make a difference. how much time did you wait? It could take up to 15 minutes for the first initial boot.

i've waited about 10mins. but even if it goes to the gray/black screen i should wait for it longer?
gonna redo this again and wait for a longer time. 20mins max and see where it goes from there.

Upgrade to amon_ra recovery 1.5
Then do this
Wipe
install ADP 1.6
flash cm rom right after flashing ADP without reboot
now reboot and it will go back to recovery mode
now reboot once again and wait my friend

I'm still waiting for about 20mins to see if it reboots good.
If not then i'll be doing the new amon_ra recovery 1.5 way.
should i install a older cm rom if coming from bare root?
or it doesn't matter if i'm flashing 1.6?

you might want to consider upgrading your spl while you're at it. Just a thought. I don't think it's necessary for running Cyanogen, but it'd be nice to have in case you ever want to run a hero rom to upgrade to the danger spl

where can i get the spl? I dont wanna install the danger one since I wont be installing hero on it. I just wanna run cm roms.

no luck still. but have another dumb question for you folks.
the spl i have is this. .. HSPL10.95.3000
is this ok to run cm or should i upgrade it? i know that there is a spl that is used to run hero roms but i'm not gonna be doing that so I thought that maybe there might be another spl out there that is a upgrade from the one i have?
gonna go search the forums for this btw. I dont wanna be a pain about this.

RegulatorG1 said:
no luck still. but have another dumb question for you folks.
the spl i have is this. .. HSPL10.95.3000
is this ok to run cm or should i upgrade it? i know that there is a spl that is used to run hero roms but i'm not gonna be doing that so I thought that maybe there might be another spl out there that is a upgrade from the one i have?
gonna go search the forums for this btw. I dont wanna be a pain about this.
Click to expand...
Click to collapse
I was wondering if it was your spl that could be preventing the rom to boot up. If you don't want to flash the danger spl, you can flash another one, like the HardSPL. I'm sure if you look in one of the sticky's or locked threads at the top of the forums in development you will probably be able to find a download link. It's worth a shot. Since you already have the latest radio, there is no reason to worry about upgrading the radio.

i was checking the forums and i have the hard spl.
or at least this says is the hard one. goes something like this..
hardspl =VER: HSPL10.95.3000
then
Engineering SPL=VER: HBOOT-0.95.3000
and last
G1 Original SPL=VER: HBOOT-0.95.0000
still no luck with installing cm's rom.. gonna look some more.
thanks for all the help guys! please if you think of something else let me know.

ok can't figure this crap out. gonna go bald lol
did a restore on my recovery and i'm back to this.
Model number: Android Dev Phone 1
Firmware version: 1.6
Baseband version: 62.50s.20.1H_2.22.19.26I
Kerner version: 2.6.29-00479-g3c7df37
[email protected] #19
Build number: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
It does show the 1.6ADP
but what the hell lmao. I can't install cm though.
Not gonna touch the g1 right now till hopefully some of you can tell me how or what to do to upgrade my rom to hopefully cm4.2.7.1.
Again i'm really sorry for being soo needy.

oh crap. I think i lost root access again >_< crap
what's the best way to check to see if i still have root?
turned off phone and tried going into recovery but now it just shows the triangle ! and the phone pic. guess root is gone???

The newer Spl rearranges how mem is allocated so more is given to system partition on phone which allows larger roms to be installed(heros).Any SpL is fine for cyanogen/enom/dwang roms.

RegulatorG1 said:
oh crap. I think i lost root access again >_< crap
what's the best way to check to see if i still have root?
turned off phone and tried going into recovery but now it just shows the triangle ! and the phone pic. guess root is gone???
Click to expand...
Click to collapse
The triangle means root is no longer with you,young one.

ok, gonna root it again. i can get it to rc29 no problem but that's where the entire thing went wrong. will post later. wish me luck

ok rooted my g1 once again. gonna install the 1.4 recovery image now.
ok installed 1.4 recovery, now performing a backup for this point.
I think I have a old cm rom around somewhere.. .. its a 3.9.5cm should i update radio first then install this or visa versa?
+ok, installed 1.4 and flashed new radio. now gonna do what your saying and see where it goes. performing backups at each point >< lol
-ok i went to recovery and flashed the new radio and it's still formating cache... its been like 5mins already. should i reboot or wait longer?
i'm still needing to install the 1.6ADP and the rom still.

Don't reboot between the 2 zip files.
Boot to recovery
do a wipe
wipe it again for good measure
install from zip signed dev dream zip
install from zip Cyanogenmod 4.2.7.1
reboot
It will tell you it is writing radio then actually reboot
It will reboot to recovery mode
where it will tell you its writing cache...
wait till it offers reboot option again
Reboot
you shoul dget the G1 screen, than the cyanogen screen...
yes it might take a while on the second screen...I have never had it hang more than about 8 minutes.
Then you should be operational.
I do have a reoccuring issue with poor response after the initial boot to the desktop.
I usually just wait for it to stop all the background shuffling and then it smooths out.
YMMV

ok this is where i am so far...
have root
have hardspl
have recovery 1.4
have Radio Update 2.2.19.26I
now i'm gonna perform backup and do what you just said. hopefully since i did everything brand new there will be no issues.