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 ...
Related
after flashing DREAMIMG.nbh, do i have to use the recovery image provided in the instructions at section two, step 1?
or can i use any recovery image? such as cyanogen's?
I would use JF's Recovery while you're getting everything set up. Flashing the radio, rom and SPL. The after you've got compfortable use cyanogen's. The only reason I say this is because Cyabogen's has some issues with flashing Haykuro's SPL, and possibly others. You might be fine with Cyanogens from the offset, but I'd play it safe with JF (although I might be worrying about nothing).
themadbogart said:
after flashing DREAMIMG.nbh, do i have to use the recovery image provided in the instructions at section two, step 1?
or can i use any recovery image? such as cyanogen's?
Click to expand...
Click to collapse
themadbogart<funny name> I would do what AdrianK said... get it all setup first following the root directions that you are using... once you feel comfortable doing that read how to do the new radio... and then move to Cyanogen's new recovery image... but READ up on how to 1st... and if you don't need the new Haykuro SPL then don't use it... Most of all the Hero based ROMS require it... due to the size of the ROM... plain and simple it has bricked many a phone and you can find info on the "bricked" phones as well... Good luck to you and if you get stuck don't continue alone come back and read... read.... read... read!
peace
fair enough. i just wanted to know that i wasn't stuck using the supplied recovery image.
themadbogart said:
fair enough. i just wanted to know that i wasn't stuck using the supplied recovery image.
Click to expand...
Click to collapse
There are some people running into trouble with installing his recovery. I was unable to go to cyans directly from stock but the upgrade from jf's recovery went fine.
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
I have been trying to flash the CM7 Rom to my G1 and continue to get the same error messages... I tried uploading a pic but the app wouldn't let me, so I will try and get the pic posted asap
Sent from my LG-P999 using XDA App
what is your radio/spl?
also have you flashed many other roms before?
Please using following combination for Radio and SPL. Also note, flash radio first and then SPL otherwise G1 will not boot. Also make sure you have Clockworkmod recovery for CM7. This recovery helps for smooth flashing for CM7.
update_2.22.28.25_S - Radio
hboot0013d-signed - SPL
kudlinux said:
Please using following combination for Radio and SPL. Also note, flash radio first and then SPL otherwise G1 will not boot. Also make sure you have Clockworkmod recovery for CM7. This recovery helps for smooth flashing for CM7.
update_2.22.28.25_S - Radio
hboot0013d-signed - SPL
Click to expand...
Click to collapse
OK, this might be sorta a strange question, but this looks to be the best place to ask it.
Will the Dream be bootable if you flash only the Radio and SPL, leaving untouched the stock Android 1.6?
While I am a Linux geek, I am new to android and prefer to take things one step at a time. That explains why I have a Rooted dream with Amon RA with the stock 1.6 backed up with nandroid.
TheLexx said:
OK, this might be sorta a strange question, but this looks to be the best place to ask it.
Will the Dream be bootable if you flash only the Radio and SPL, leaving untouched the stock Android 1.6?
While I am a Linux geek, I am new to android and prefer to take things one step at a time. That explains why I have a Rooted dream with Amon RA with the stock 1.6 backed up with nandroid.
Click to expand...
Click to collapse
never tried, theoretically it should be as if you did a factory reset and you would just use your recovery to replace anything lost. but if you want to be safe maybe someone who has will chime in.
besides the point go ahead and flash a new rom, even if you stick with 1.6 firmware the developers have come out with much superior roms over the stock android. if you want only 1.6 try super d or super csdi
ok so i decided to test this out, updating a g1 to the 2708+ radio/spl and not flashing a new rom -------- stuck on g1 boot screen, hit call+menu+power then hit home to reboot to recovery, reflashed rom and gapps, rebooted, now everything is good as can be, so to answer your question --- yes it appears you need to flash a rom after you update your radio/spl
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
I wanted to flash cm5 for a variety of reasons (moving from cm4, so I have some experience on the matter)
The thing is< I don't want to flash a custom spl, don't want to brick my phone, it's my only one, but have found the firerat partition method and was wondering how to proceed with the matter.
I know how to recover from a soft brick, and have nandroid backups made with cm recovery 1.4.
Anyone have any expertise on the subject?
Make a nandroid, wipe clean, flash new ROM and gapps
What's your current radio/bootloader?
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Make a nandroid, wipe clean, flash new ROM and gapps
What's your current radio/bootloader?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have no idea what my radio version is, but I have a stock bootloader, and I'm currently unwilling to flash that because the risks are so high, but I've tried just flashing the update, and it soft bricked my phone; the really bad thing it did was partition /system in a way that nandriod didn't work, and I had to flash rc29 and repeat the procedure to even get cm4 working. My signature probably has most of the info that you'll need to see what hardware/software configuration I have. Thanks for being an such an active help demkantor!
edit: no signature with that info anymore, and it had already changed, so to rephrase: I just had stock.
Can't see SIG on app, but the risks are minimal on flashing firmware so long as you know what you're doing
I used to buy and sell g1s and have fully upgraded close to 100 of them, never damaged one
Just use fastboot when possible, check md5sums, always flash radio then bootloader, just be sure you follow proper steps and all is safe
If you want any newer ROMs you will be forced to update and it literally takes less then ten minuets to go from pure stock to fully updated phone running gingerbread or whatever. And most of the froyo and gingerbread ROMs run better than older ones especially with the ram hack
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Can't see SIG on app, but the risks are minimal on flashing firmware so long as you know what you're doing
I used to buy and sell g1s and have fully upgraded close to 100 of them, never damaged one
Just use fastboot when possible, check md5sums, always flash radio then bootloader, just be sure you follow proper steps and all is safe
If you want any newer ROMs you will be forced to update and it literally takes less then ten minuets to go from pure stock to fully updated phone running gingerbread or whatever. And most of the froyo and gingerbread ROMs run better than older ones especially with the ram hack
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have heard a lot about fastboot, what is it and how do I enter it?
Its mode within bootloader that allows for communication between phone and PC, kinda like adb
Some of the bootloaders for the dream have limited fastboot commands available so you'll have to read dream specific threads to see which have what
Here is some help to set up and use it though
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
I know that many people have flashed it with a great deal of ease, however, I have no replacement, no local jtag as a possibility, and no interest in buying a new one. If you could give me detailed instructions along with working, easy to use, links to anything required, then that would be really great. If you have a way that I could preserve the data for my apps, then that would be even better!:fingers-crossed::victory:
What would you like help with, flashing cm5 or changing radio/SPL
Also write down all info on bootloader screen and let me know current recovery and ROM youre on
Sent from my Nexus 4 using XDA Premium 4 mobile app
I want reliable help with both.
The information that I could gather from the bootloader is:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I (P.S. the last character is an "eye", not a one or an L)
SEP 2 2008
_____________________
I flashed update-cm-4.2.15.1-signed.zip to get my current ROM, even though I have some custom mods, so it can't technically be considered more than based off of cyanogenmod.
I am running the cyanogen+JF recovery as my current recovery. I have heard of a partition re-sizer made by firerat, but have no indication of its reliability. if you have a fail-safe way of flashing cm5, of even cm6, then that would be great!:fingers-crossed::victory:
ok so here are your steps
boot to recovery and make a backup
now flash Danger SPL from recovery
now boot back to bootloader and see that you have .26i radio and .2005 SPL (not needed step but good to see this)
The preferred thing to do is flash the .13d spl with a compatible radio but we can save this until later
For now we will go through these next steps:
boot to recovery and flash THIS SUPER WIPE SCRIPT (always a good idea between flashes)
and I'm OCD when it comes to wiping clean so also wipe all in recovery
Now flash CM5 ROM
and the flash GAPPS in recovery
when all is done reboot ---- profit
also consider using THIS RECOVERY just my preferred one for the dream
Let me know if you need further help
The links to cm5 and gapps seem to be dead, but I'll find them elsewhere. And, are you sure that there is no possibility of a hard brick while doing this? If I killed this phone, then I would be out of luck for at least 6 months.
does superwipe wipe recovery and hboot as well?
These forums are almost as good as live support!
Superwipe wipes and formats system/data/cache/boot not recovery or hboot
If you can't find cm5 or gapps let me know and I'll upload them
Flashing bootloaders through recovery is dangerous so always check md5sum and once you have the .2005 hboot you will be able to use fastboot for all your firmware flashing needs
Having said that I have flashed that .zip literally over 100 times with never a brick (used to sell rooted phones on eBay) but choice is yours
Sent from my Nexus 4 using XDA Premium 4 mobile app
So you're saying both that it is dangerous and that you recommend doing it? P.S. Please excuse the immaturity of this, it's just that this is really exciting, as my first android is about to get a really major update.
Will the superwipe wipe the ex2 partition on my sd? Or will I have to make a copy?
DREAMWAVE_devteam said:
Will the superwipe wipe the ex2 partition on my sd? Or will I have to make a copy?
Click to expand...
Click to collapse
I would do the upgrade, it is safe so long as you follow proper instructions
download all files
check md5sums
make sure you meet all requirements (ie radio matches new spl - you're good here)
place all needed files on root of sd
yes it wipes ext partition, you can always extract contents of any mod/rom/whatever
if you're not sure - look through an updater-script if its flashable (this is) and see what it does
you will see it runs SuperWipe.sh - in here you see it wipes boot/cache/data/system/sd-ext (not fat32 partition) and .adroid_secure
I use this same superwipe each time i flash a new rom to my g1, its good (always make nandroid in recovery first)
and yeah, first time you do anything new like this it's scary/exciting but knowing that thousands upon thousands have successfully done this
you'll be just fine
best of luck!
Is it possible to do it without erasing the ext partition? Maybe just wiping with the recovery wipe data? It will mean that I will have to find my sd adapter if I have to copy the ext partition.
Maybe you misunderstand, it won't remove the partition altogether it will just remove contents which is a good idea when moving to a new ROM, the backup you made will backup contents of ext partition and can be restored at a later point if needed
Sent from my Nexus 4 using Tapatalk 2
I've seen a lot of tutorials on how to do this say that I need to flash hardspl. is this correct?