Database Develop

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.

simplest way to switch from JF 1.5 to current Cyan?

I bought a g1 off of craigslist and it already had root. JF 1.4 ....
Around the time cupcake was released I updated it to jf 1.51
Now since there will be no more JF updates I wish to switch to Cyan builds.
I'm unsure of the proper way of doing this?
Should I go back stock .. unroot and then go thru the steps to load cyan?
Or is there a better way? A wipe?
I'm asking to be clear because internet access is strictly from my g1.
Although I can download all the files I need, I do not have constant access.
I'd appreciate any tips or pointing me to the proper thread.

Check the threads in Dream >Dream Android Development look for Cyanogen's thread on his release of 4.1.999, follow the instructions and you will be fine. I'd also suggest at least flashing Cyanogen's v1.4 Recovery Image over JF's, easier to flash any .zip on sdcard. So, new recovery image (use search option in forums, or look in the same thread i mentioned for cyanogen recovery image 1.4) then update to cyanogen's latest rom build

So simply flash a new recovery, then follow the cyan steps?
Cool, easy as pie.
I certainly appreciate it.
Thank you

Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder

B-man007 said:
Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder
Click to expand...
Click to collapse
that is why there is a full update made for it.

haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol

B-man007 said:
haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol
Click to expand...
Click to collapse
sleep is for the weak. also it is really hard to flash two things while in recovery it causes hemorrhoids and anal fissures.

haha trust me...someone somewhere will make something incredibly easy look like rocketscience

B-man007 said:
haha trust me...someone somewhere will make something incredibly easy look like rocketscience
Click to expand...
Click to collapse
you mean rocketsurgery

david1171 said:
you mean rocketsurgery
Click to expand...
Click to collapse
*sigh*
yes its true.

B-man007 said:
*sigh*
yes its true.
Click to expand...
Click to collapse
lmao me went to smart person learning place

I'd like to chime in here as well since I'm having such a hard time searching for info on the conversion from jf1.51 to the latest build of CM. The amount of posts are staggering!
So, I vaguely remember setting up apps2sd following the guide at the bottom of this page - http://yokohead.com/2009/06/how-to-root-android-g1-with-cupcake-and-appstosd/
Will CM automatically detect this partition?
Also, will I lose the google experience? I'm still confused as to where we are on that.
Thanks for your time! If anyone knows an updated post on this process, please point me to it.
TJ

Well the sticky by fingerlickin at the top of this section is a good place to start....
all you have to do is find the singleflash update in the dev section, backup and clear everything off your ext3, and wipe+flash the single update. you can restore the ext backup then.
also you should upgrade to cyan 1.4 recovery
to do so
su
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
you wont lose the google experience

Thanks B-Man007,
After a couple attempts, all is working well. I'm thoroughly impressed with the snappiness of this build. Although it's only my second time updating a ROM, I'm going to blame the amount of posts for my hesitation and confusion. It was easy to just go in and do it.
I actually updated to the latest Amon-Ra(sp?) recovery. At first my Rom was running real slow and the recovery allowed me to update my ext2 to ext3. Loving it now!

The amount of posts does make it quite confusing i agree, especially with the high amount of conflicting posts
Ya ext3 is a must, but you could have upgraded from cyans too haha
cyan usually has the fastest builds out there though at times it can get very slow.

Another noob here. A few months ago I rooted and flashed to xrom 1.5. When I do a reboot, my recovery screen tells me its "CyanogenMod v1.4 + JF".
Since xRom is experiencing some problems w/ updates, I figured I might try the latest build of Cyanogen. I re-booted, went to recovery mode. Wiped. Then flashed the latest Cyan and even found the 1.6 ota on another site. Flashed both zips, then did a re-boot and it hangs now.
I tried it over and over a few times, wiping then flashing again. Wiping, then re-booting, then flashing the rom, etc. Over and over with the same results.
Then as a test, I tried flashing back to xRom... perfectly fine.
As another test, I tried wiping and flashing to another rom, the rooted stock option (the HTC rom version)... and got the same results as when I tried Cyan... just hangs.
Wiped and flashed again back to xRom... works fine.
So at this point, I'm thinking I need a more updated recovery rom? Any other possible problems? Yes, I did a search all over and this was the best thread that matched my problem.
If it helps... I have a T-mo G1, firmware 1.5, JACxROMv1.5, kernel version 2.6.29.6-jac-ski root. And I know many will slap their foreheads when I say this: But the SD is NOT partioned at all (kept trying and trying with zero success, so I eventually gave up).

Phone Won't Boot

I also posted this over at HowardForums:
Long story short, I was trying to root my phone and flash it with the latest CM using this guide: http://forum.xda-developers.com/showpost.php?p=4848777&postcount=506 Basically, somewhere along the line I f***ed up, and now when I try to turn it on it gets to the Rogers screen and hangs there. I've tried everything I could find to fix it and nothing has worked. I've tried basically everything I could in recovery, and when I go to fastboot, it's a wierd screen that has sort of a rainbow-ish background and for the first line that says what SPL it is, it doesn't say anything.
Just woundering if anyone knows how to fix this or if it's even at all fixable? And if not, is it possible for me to take it in to Rogers and have them replace it or is that not possible? I bought the phone in early July of this year, so I'm not sure if it's under warranty or anything.
Thanks in advance.

Well atleast you haven't bricked the thing. When you boot in to recovery, is it the stock recovery or Cyanogen's recovery image?

I think it's Cyanogen's. It's the one that says something like CM 1.4 + JF at the bottom.

Ah, in that case you're fine I'm not too familiar with the flashing process for cyanogen ROMs, so I can't really help you out there, but if you choose to use other ROMs you will only need to flash one file.
To get your (newly-rooted) phone working again, you could
download http://forum.xda-developers.com/showthread.php?t=567023 ROM
put it on the root of your sdcard (do not unzip it)
boot in to recovery
wipe
choose flash any zip
follow the promts to flash the ROM
If you don't have a card reader to mount the sdcard, boot in to recovery, then the console and type 'ums_enable' and it will mount on your computer. Then use 'ums_disable' when you're done.

Ok I'll try flashing another ROM and see if it works. Any suggestions for a good non-CM ROM xD?
I think I may have screwed it up since CM now needs you to flash the 1.6 Android, then CM or something. Maybe I did that part wrong. Anyways, I'll try another ROM and post back whether it works or not.

Thanks for the help. I tried flashing a AOSP T-Mobile 1.6 ROM I found and it worked. Now I'm woundering if anyone has any suggestions on other ROMs to try out?

DiSTroy3d said:
Thanks for the help. I tried flashing a AOSP T-Mobile 1.6 ROM I found and it worked. Now I'm woundering if anyone has any suggestions on other ROMs to try out?
Click to expand...
Click to collapse
Dwang's ROM sounds good, might want to give that a try. I meant to link to it in my last post, but I guess I forgot :-S

DiSTroy3d said:
Thanks for the help. I tried flashing a AOSP T-Mobile 1.6 ROM I found and it worked. Now I'm woundering if anyone has any suggestions on other ROMs to try out?
Click to expand...
Click to collapse
You can try Dwangs. Also, if you decide to install cyanogen's rom, follow his instructions on his wiki, but remove the radio.img inside the ADP recovery just to be safe and resign.

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.

Only CM works on G1 and MT3G

Alright well first off I've looked all over XDA for an answer if theres is one out there a Mod can remove this post. I'm not new to this at all I have been flashing roms since the Dream was released, just the other day i was thinking about trying out a new from King's new Legend coming from CM 4.2.15.1 as usual i wiped everything reformatted my SD partitions and installed the Legend rom, now for some reason i cannot get past the G1 screen on that or any other rom there is out EXCEPT CM 4.2.15 I attempted the same thing on my 32B MT and get the same problem it will not go past the MT green screen has anyone had this issue or would anyone be able to tell me whats going on I've tried everything i could think of and nothing works. Thanks for any help people!

theres a lot of other roms that require a different SPL than CM does. make sure you have the correct one installed. also, make sure to wipe before flashing.

I have kept that in mind and yes I have wiped before every flash I once again just now tried the CanNNoN202 rom correct SPL and all also running the latest radio still no go on either the MT3G or G1

wut does it say in bootloader screen ?