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.

root help!

i know i think i might be at the wrong forum but i thought i might get help over here....i have unlock the boot loader fine, then i installed the super boot and flash the recovery image amran 1.6.2 fine, i backup my nan and now i like to flash it with cyanogen rom 5.0.4.1 do i need to update the radio or put the add on for this before i do continue...please help!!!! thanks
i have radio:4.03.00.21.2
do i?? or just flash it directly and how about addon???

xghostyxjokerx said:
i know i think i might be at the wrong forum but i thought i might get help over here....i have unlock the boot loader fine, then i installed the super boot and flash the recovery image amran 1.6.2 fine, i backup my nan and now i like to flash it with cyanogen rom 5.0.4.1 do i need to update the radio or put the add on for this before i do continue...please help!!!! thanks
i have radio:4.03.00.21.2
do i?? or just flash it directly and how about addon???
Click to expand...
Click to collapse
you do not need a new radio. I am still using stock radio! and maybe try this rom http://forum.xda-developers.com/showthread.php?t=639637 its a supermodified, sexy, feature-rich cyanogen rom

theres alot of deferent ones which is suggested for the most out of it???

if i decide to flash the desire rom do i need to update the radio then??? isnt it always is good to keep up with the radio??? if so how do i do the update i have it ere38 i beleive???

xghostyxjokerx said:
if i decide to flash the desire rom do i need to update the radio then??? isnt it always is good to keep up with the radio??? if so how do i do the update i have it ere38 i beleive???
Click to expand...
Click to collapse
Hi xghost. You dont have to update radio to flash desire roms.
You can update it if you want to but remember, flashing the radio is the "only" way to brick your phone. Not a high chance but higher then most other things you can do.
-Roger

okay thanks...so since it is my first time using the root for nexus one...im going to flash it with 5.0.4.1 do i flash it then flash the ere38 add on that is on the page or???

[Q] Upgrading from Cyanogen 4.15 to 6

Hey guys, I'm planning to update from Cyangoen 4.15 to 6. However, my radio version is not the proper version and every time I try to install it using the Cyanogen 1.7 recovery image, I get an E:/ error although I have tried two different memory cards. Why is this happening? Perhaps I should try another radio version? Is it possible to continue upgrading without updating the radio?

What phone? Phone info? Radio you're trying to flash? Need more info.
Sent from my Chromatic Magic using XDA App

yeah...must have slipped me sorry
It's the G1 (HTC Dream). It runs on Cyangoenmod 4.2.15 right now with a radio version that starts with a 1 (I don't know the exact version, the phone is not with me).
I'm trying to flash the 2.22.19.26I radio version by going to "flash zip" option. It goes about half way and tells me that it's having a reading error on E:/
I know I need to install DangerSPL which needs a radio version right? So how can I install when I keep generating this E:/ error?

Don't need danger. Firerat made a mtd script that does the same thing without the threat of bricking your phone. If u have a spl that's compatible with the 2.22.23.02 radio that works fine but don't think it's necessary.
Sent from my Chromatic Magic using XDA App

So I can just go ahead and install CM 6, or do I need to apply this script? If I need the script, can I please get a link with instructions on how to do this?

cm6
Not sure how it works as i have a mt3g and no need for it. But yes you apply the script via his instructions and then you will have enough room in your internal memory to hold the rom. Which is the prob with the g1 stock partitioning. Hence the need for the patch or danger. Here it is. http://forum.xda-developers.com/showthread.php?t=717874. Good luck

It's really not hard to update. I would suggest using the DangerSPL if your board is compatable. It's worth it. Fireat's patch is buggy and can cause issues. So to upgrade, do this:
1. Check to see if you have a PVT board. Boot your phone holding the Camera button to enter the bootloader. The first line will say "Dream XXX 32B ENG S-OFF". If it says PVT where the XXX is, then you can safely flash the DangerSPL.
2. Upgrade your Recovery Image, I suggest ClockworkMod 2.5.0.1 (download ROM Manager from the market to install)
3. Update your radio to version 2.22.23.02 - Instructions [HERE]
4. Flash DangerSPL - Carefully read instructions [HERE]
5. Wipe Data/Cache, Flash CyanogenMod 6.0 RC2
6. Flash Google Apps v3
All done.
Alternately, just follow [THIS] guide, just ignore the first step "Gain Root".

tehseano said:
It's really not hard to update. I would suggest using the DangerSPL if your board is compatable. It's worth it. Fireat's patch is buggy and can cause issues.
...
Click to expand...
Click to collapse
Are you sure? The issues you might get in flashing DangerSPL in a wrong way will be much heavier!
I would suggest using the engineering SPL 1.33.2003 and go with the MTD-patch, it' much more flexible and more save. Only my 2 cents.
Sent from my Htcclay's Superfly G1 using XDA App

AndDiSa said:
Are you sure? The issues you might get in flashing DangerSPL in a wrong way will be much heavier!
I would suggest using the engineering SPL 1.33.2003 and go with the MTD-patch, it' much more flexible and more save. Only my 2 cents.
Sent from my Htcclay's Superfly G1 using XDA App
Click to expand...
Click to collapse
As long as you have a PVT board, flash the correct recovery first, then flash the spl, you are perfectly safe.

I'm going to try updating via DangerSPL because my cousin is getting crappy coverage as is, so perhaps updating the radio version will help him
However, is seems to update the radio that I originally wanted needs 2.22.19.26I. However, I keep getting the "No Signature (5 files). Verification failed. Installation aborted."
How can I fix this?

I actually decided to use the script. However, the volume is very low at the fullest. Anyway to fix this?

Does cm6 have the cyanogen settings option in the settings? If so does it have the dsp settings? Its a sound equalizer of some kind. It might help but I don't mess with it or know anything about it. The volume hack in the market or any that I know of don't work on froyo
Sent from my Chromatic Magic using XDA App

Actually I'm running CM 5.0.7. Any specific solution for that? If this app does it, may I have the name or a link to download it?

Sorry but louder volume hack in market says it doesn't work on 2.1 and up. But that's what its called. If I see anything ill keep u informed
Sent from my Chromatic Magic using XDA App

Can I have the name anyway...just to try it out and please keep me updated

One in market is called louder volume hack. Made by meltus.
Sent from my Chromatic Magic using XDA App

Also, the headset doesn't seem to be working. The phone will charge and such but when I plug in the headset adapter, it won't work and will continue playing from the speakers which is still very low at it's highest. What could be the possible solution for this?

Does this happen on other roms? Wondering if it's an actual hardware prob. G1 has had a low volume from day one but not sure your issue is just that.
Sent from my Chromatic Magic using XDA App

The thing is, it's not my phone and my cousin is very needy of this phone for work so I can't keep experimenting with it by swapping roms so I really don't know.
I know that before I applied the script and installed CM 5.0.7 sound was working and I could play music through the headset but after I installed CM 5.0.7, it stopped. Could it be my fault, or is just the G1 crapping out on us?

Not really sure but I would try a no wipe upgrade to cm 5.0.8 and see if that works. I know that Rom is stable. Unless u have to wipe I can't remember.
Sent from my Chromatic Magic using XDA App

[Q] Softbricked

Ok so I found this usefull tut on the wiki from cyanogenmod, and I followed it. Everything went great until I had to flash dangerSPL. So I've put the 2.22.19.26i Radio on it, flashed it, and then I flashed the DangerSPL. I was going absolutly crazy when it was stuck at the t-mobile G1 screen... I Can acces the Recovery AND the bootloader (Amon Ra 1.7). Ive tried Whipe -> Whipe data/factory reset. But I'm still stuck on the G1 screen after that. Is there a step that I'm missing or can I call it my own personal brick?

You did install your ROM after flashing the SPL?
Sent from my Htcclay's Superfly G1 BTX using XDA App

AndDiSa said:
You did install your ROM after flashing the SPL?
Sent from my Htcclay's Superfly G1 BTX using XDA App
Click to expand...
Click to collapse
No, So I have to flash SPL and then directly flash ROM?

Excuse me the question, but do you know, what you are doing? Do you expect, too, that a computer, where you repartitioned the harddisk is booting the former OS without any problems?
Sent from my Htcclay's Superfly G1 BTX using XDA App

AndDiSa said:
Excuse me the question, but do you know, what you are doing? Do you expect, too, that a computer, where you repartitioned the harddisk is booting the former OS without any problems?
Sent from my Htcclay's Superfly G1 BTX using XDA App
Click to expand...
Click to collapse
Ooh, that explains a lot XD So DangerSPL is there to repartition the memory.

Ok so did the whole process again, after doing the SPL, I flashes cyanogen mod 6.0 and google apps. Now I've rebooted and it is stuck (Or does it just takes ages) on the blue Cyanogen(mod) cirkel with the rotating thingie

You sound like a real newb.
You should install spl 1.33.2003, which uses stock partition layouts and is fully compatible with the DREAM RADIOS (and thus won't brick). To alter partitioning, use the CORRECT tools, specifically, the partition table can be handed to the kernel on the command line. http://forum.xda-developers.com/showthread.php?t=717874

Unfortunately DangerSPL is "misused" to repartition the memory of the phone. Nowadays there is no need to do so (links to alternatives can be found in my signature), but everybody is suggesting it, so everybody is using it.
About the boot time: It will take long to boot, for sure several minutes. If you see the bootimage at least the kernel was loaded without problems, i.e. first step is working. If you want to see what's going on during the boot-phase, you can try to logcat using adb (-> it's a remote debugging tool).

I sound noob because I am at this stuff. Got my phone in yesterday...
And so if I install spl 1.33.2003, I will be able to get Cyanogen 6.0 on the phone. The tutorial said dangerSPL expanded one pertition and that that was necessary. Is this also so with spl 1.33.2003?

You cannot flash the 1.33.2003 and use CM6 directly. To use CM6 with 1.33.2003 you need to "patch" your kernels using Firerat's mtd-custom partition layout. It consist of 2 zip files which are used to modify your recovery and your boot images (down in my signature is a link to the thread where it is explained in detail). The advantage of doing so: no risk to brick your phone and the partition layout can be defined almost as you want.
Another hint I would like to give you and others starting to root and to flash new ROMs: before rooting and flashing, try to read as much as possible here in the forum. Especially the "sticky" postings which give you some introductions. It will help you to get an understanding of what you are doing and how it is working. Bricking a phone is more easy as you might think ...

[Q] google g1 keeps rebooting at g1 screen

Hi my g1 keeps rebooting at the g1 screen only on the ezgingerbread rom it boots but 3g/edge doesnt work there. ive tried alot of roms and its always the same. I have used the search function.
Dream 32B
hboot 1.33.2005
radio 2.22.28.25
Does anybody know how to fix this?
Thanks

its probably your radio /spl are not supported in the roms you are choosing to flash, make sure you meet all requirements in the op of any rom you choose
Sent from my HTC Vision using xda premium

The reason for your problems might be your unusual SPL / radio combo. EzGingerbread has auto-kernel included, so it's booting up fine, but probably the interface to the radio is not working fine. The other ROMs probably are installing a wrong kernel and so it boot-loops.
I suggest you to eiher install the 1.33.0013d spl or the 2.22.19.26 radio. Look at Terry's thread for more info! (A link is in my signature)
Sent from my Nexus 7 using xda app-developers app

Thank you i got it working i am now running :
hboot 1.33.0013d
radio 2.22.28.25
i couldnt find a image of 2.22.19.25 but its working thank you

I lied sorry not all roms work still the same issiue does anyone know where to get a radio image of 2.22.19.25 ?

anddisa mistyped, but he is right in your first issue, you now have the most up to date radio/spl combo more info here
http://forum.xda-developers.com/showthread.php?p=26639740
some roms won't work with this unless you use the proper kernel. you don't need to change your radio but more info is needed. what roms are you trying to flash? have you ever used cmtd? what is your recovery? are you wiping between flashes? superwipe? fastboot -w?
Sent from my HTC Vision using xda premium

I have been using clockworkmod 2.5.0.7 i dont know what cmtd is but i've been using oshaka superwipe and just normal wiping with clockworkmod (factory reset and then cache). I wanted to flash lmc froyo and super e 1.0.3. and froyo cream sandwich. Froyo cream sandwich works but i dont like the theme. I have no ext partitions i had a 8gb class 6 sd card with ext4 but it just wouldt work on this phone using a 2gb sd card now.

I suggest using amonra recovery, it works better on the g1. super e will not work as is, you need a kernel to flash over it. I suggest the biffmodtest kernel found in ezterrys thread I linked. make sure to read the op of a thread and make sure you meet the requirements. cmtd is custom partition mapping. if you don't use it don't worry about it.
Sent from my HTC Vision using xda premium

sthij said:
Thank you i got it working i am now running :
hboot 1.33.0013d
radio 2.22.28.25
i couldnt find a image of 2.22.19.25 but its working thank you
Click to expand...
Click to collapse
This combo is best, but 1.33.2005 / 2.22.19.26(!) would be fine, too, even with less memory available.
Sent from my Nexus 7 using xda app-developers app

I tried flashing the amon ra recovery via fastboot but theres a signature failure (FAILED remote signature verify fail) and i will test the biffmodtest kernel if i can get my recovery working. super e is working perfectly with the biffmod kernel i am not gonna mess with my phone any further since i am not having it long anymore. Thank you very much for all your help

now that you have the .13d spl write fastboot commands wont work (read the full op of ezterry's post)
i dont want to sound rude but all of your questions could have easily been answered by searching and reading. im afraid you are going to brick your phone if you dont do the appropriate reading to understand the process. it is very easy to brick a phone when flashing firmware, people make the same mistakes frequently; dont check md5sums, flash incompatible spl/radio, etc.
if you read the post you will see you would need to flash the orange.nbh through bootloader to regain an spl with fully working fastboot commands.
just be careful and make sure you understand what you are about to do so you dont end up with a paper weight

sthij said:
I tried flashing the amon ra recovery via fastboot but theres a signature failure (FAILED remote signature verify fail) and i will test the biffmodtest kernel if i can get my recovery working.
Click to expand...
Click to collapse
You cannot fastboot flash recovery with the 1.33.0013d SPL. If you want to change it, you either need to use recovery, or you need to go the long way: flashing the orange-rom, flashing the recovery, flashing the 1.33.0013d SPL (the details are described in Terry's 2708-thread).
Sent from my Nexus 7 using xda app-developers app