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
Related
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 ...
Greetings, all. I'm just moving into the Android scene from some dark and lonely years using WinMo/iOS. Since I'm cheap, I bought a used G1 that was already rooted, figuring I could figure it out (did my time jailbreaking iOS and modding WinMo). Well, apparently I'm a worse noob than I'd thought....
Here's what I'm finding:
Firmware Version: 2.1-update 1
Baseband Version: 62.505.20.17U_2.22.19.261
Kernel Version: 2.6.29.6-wg ctso#h0meb0x #2
Mod Version: OpenEclair-v1.2.1 BACONWEAVE
Build number: openeclair_dream_sapphire_us-eng 2.1-update1 ERE27 eng
From the Recovery Mode: CyanogenMod v1.4 + JF
I've tried searching XDA, but honestly, it confused me even more. From what I've found, I should be on at least CyanogenMod v4 to be running Eclair (2.1)? And the guy I bought it from must have been running an older ROM, as WiFi doesn't work and Android Marketplace don't show up.
If anyone could give me a few pointers on where to start, I'd greatly appreciate it. I feel pretty confident that I'll pick up Android pretty quick, just a big change from iOS/WinMo. Again, sorry for this probably being a repeat article, but the search tool has been more confusing that helpful to me here (unlike most forums).
The easiest thing for you to do is to flash a new rom onto you phone I'm using the new super e rom and have had no problem with it, you will have to do a seperate zip download for the marketplace with this rom, which is found on page 86 of this roms post, if your wanting to wifi the apk can be found in the rom bible in the development section as well, power on your g1 holding the power and home button go to the home section and WIPE EVERYTHING not doing so will cause problems, then install the rom reboot then power off and back into the same mode, and flash the gapps zip this will get you up to date
Sent from my HTC Dream using XDA App
So just to make sure I completely understand, I'm not going to need to touch the SPL or Radio or anything like that, right? Just wipe, then run the ROM for the saved .zip file?
Thanks for the quick response!
If ur not sure what spl or radio u have its best to get the most up to date ones, theunlockr.com has the easiest way to get the most up to date and walks you through step by step just click the how to tab, but when it comes to roms this site is by far the best
Sent from my HTC Dream using XDA App
If your going to replace everything then partition the sdard ext upgrade the exts install in order with reboots between, radio, spl, then rom, (if you beed more detail just ask I'm not sure how new you are to this) then once u install the gapps u will be asked to sign into google, if you haven't done this before then you will not have your contacts so be sure to write them down or something before wiping (sorry forgot about this earlier
Sent from my HTC Dream using XDA App
Haha, I was just watching their videos. Thanks for the help, I think my plan will be to wipe my phone then go their route. Does super E work with their system, by the way? I'm still trying to figure out the difference between "Danger SPL" (required for super e) and their method...
Also, since I can already get to root, can I just save a .zip'd ROM to my SD card, wipe the phone, and then install it? Or if I need to go through their steps, do I need to un-root my phone, and then do their "One-Click Root" method?
Thanks again, you're the best!
I would not recommend danger spl due to the risk of bricking your device just stick with the hard spl they provide it runs just fine on the super e
Sent from my HTC Dream using XDA App
You don't need the whole root method just use they're how to load a custom rom it gives you the latest spl and radio but yes save all three straight onto the sdcard after partitioning it
Sent from my HTC Dream using XDA App
In the future yes you can just wipe and flash but this ensures ur up to date with everything else, I'm calling it a night, post a update so we can see how it worked for you
Sent from my HTC Dream using XDA App
I'm having a TON of issues with the current radio. I flashed the updated radio during the whole 911 patch fiasco and ever since the phone will just randomly not be able to send/receive text messages or phone calls. I've read that some of the newer radios (6.xx) and the older radios are compatible.
Current Specs:
Rom: CM 6.1.0 with patched kernel
Radio: 3.22.26.17
Model: HTC Dream 32B
You should update to the ezterry's newest radio and spl.
They also come with an extra 14MB RAM!
http://forum.xda-developers.com/showthread.php?t=831139
seems cool, but I was hoping for something simpler... Ah well if it gives me back the use of my phone...
It will, trust me if you need a guide, on how to flash it, go to the g1 development forum, its either on the first or second page
Sent from my COS-DS using XDA App
maximo360 said:
It will, trust me if you need a guide, on how to flash it, go to the g1 development forum, its either on the first or second page
Sent from my COS-DS using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1098899
ldrifta said:
brick://forum.xda-developers.com/showthread.php?t=1098899
Click to expand...
Click to collapse
Absolutely under no circumstances *EVER* flash via recovery a 2.22.* radio when you have a 3.22.* radio it *WILL* brick your phone
on a similar note:
Absolutely under no circumstances *EVER* flash via recovery a 3.22.* radio when you have a 2.22.* radio it *WILL* brick your phone
And on that note another few reasons why we recommend using fastboot
If you have a 1.22.* radio and install Danger SPL or 1.33.0013/0013d SPLs via recovery you will also brick your phone.
http://forum.xda-developers.com/showthread.php?t=831139 is safe for ALL dream users, always use that fastboot method for installing 1.33.0013d or ask ldrifta to pay for your replacement phone.. anyway those other instructions are for downgrading a t-mobile dream.. while 60% of the time it may work.. downgrading to out of region firmwares causes headaches when an NBH fails to apply the first time.. since you can't simply re-flash and move on.
(anyway the rooting guide for the e911 dreams already expects the users to install fastboot/adb so it ought to be easy to fastboot the radio+SPL.. the only real problem with my thread is some people feel overwhelmed with the full operation guide of the new phone the Radio/SPL transforms the phone into)
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
ive downgraded to rc7 to have a bit of a faff, tried to root but it looks like my keyboard has gone wonky and for somereason telnetd just does not do what it should. i thought i could upgrade it back to 1.6 and use the rooting app id used before but i cant find a way to get the ota updates without a sim.
does anyone have a list of the signed ota updates i would need to install to get back to 1.6?
found this:
https://code.google.com/p/official-android-firmware/downloads/list
on another forum, ive gone through as far as getting myself to a rooted 1.5 (though 1.6 is just a few more easy steps)
is it safe to start installing the recovery/danger spl and all that other stuff now?
this is what i intend to follow
https://sites.google.com/site/jonathanexe/test
AAAGH
might just sling this back in the drawer, im now on rooted android 1.5 but every guide tells me to go back to rc29 (which i can do but would prefer not to as telnetd doesnt work (i think i have a sticky button). is anyone (even reading this forum) willing to tell me the safest way to put cyanogenmod on this handset so i can go "oo thats pretty" and sling it in the drawer again?
Haha
If you're having issues with downgrade process but you are rooted with 1.5 then just flash a new recovery via a terminal. Being you're rooted you should have busy box and superuser, so now you just need a terminal and flash image binary
Once you have those installed to your phone find amonra recovery, and the proper hboot and radio put those on the root of SD card. Then radio and SPL stay as zips, the recovery should be an img and named recovery.img
Open terminal on phone and type
su
flash_image recovery sdcard/recovery.img
Now boot into new recovery and flash radio first, then danger SPL, then ROM of choice
Sent from my Nexus 7 using xda premium
Got up to installing DangerSPL and its apparent why the telnetd>home>start terminal didnt work for me. My home button has gone crackers and seems to press home and a plethora of other keys at the same time. Consequently when i try to install danger it both actions the update process it and aborts it instantly.
Gonna have to take the thing appart tonight and see whats causing it. As i say im not massively fussed, when its done it will probably be 5 mins of... oooo look, right, back in the box.
thanks for confirmation tho
I believe there may be a touch recovery for this phone that would make you home button issue irrelevant
Sent from my Nexus One using xda app-developers app
Got it sorted and cm6 installed, was that the last cm (that ran at a decent pace) for the g1/dream? Btw was a hardware issue, i took the phone appart and cleaned the keyboard connector to get the home key to work propperly. As expected, once done it was met with me going "meh"
Sent from my LG-P920 using xda app-developers app
Cm6 runs horrible on the dream, I would suggest 5 over it
But if you really want to see what this old phone is capable of install the latest radio and SPL, just search out ezterry's thread on the 2708+ update
Then run a spin off of cm6 like froyobylaszlo or darianx's ICS themed version of the same, also some great froyo asop built ROMs
Ezgingerbread is great as is andisa's mod of it, also feel free try some of the other great GB ROMs
They key is the latest radio and SPL to give you the extra ram, then this phone has much more to offer!
Happy flashing
Sent from my Nexus 7 using xda premium
Cm6s os seems speedy but apps are hit n miss. Tried to install cut the rope, took 2 tries to get it to the point of installation but after install it never appeared in the apps drawer. Only smaller apps seem to install, shame, the little one loves cut the rope and it would have kept little fingers off my o3d
Sent from my LG-P920 using xda app-developers app