Problems with builds! (Splash screen hangs) - G1 General

Hey everyone,
I am writing this because a day of research and playing about with my phone has resulted in nothing.
I recently rooted my G1 european (UK) phone and ended up with the JesusFreke build absolutely no problems...
Today I updated to the latest radio and SPL (again, no problems) and went to put on the Virtudude Roger's mod first and it froze on the splash screen, so I reverted back to original Android, rooted again and went back to JesusFreke's build.
This time I tried Cyanogen mod, which also freezes on the splash screen.
I have tried going to both these builds straight from Android 1.0 or from the JesusFreke build with no success - it just freezes on the splash screen every time.
Anyone have any advice? Maybe theres something I'm doing wrong on the way?! I use recovery mode to format and load the flash images on
So much thanks in advance!

After rooting the phone and then putting it on JesusFreke's build, you were trying to update the radio and SPL with the 2.22.19.26I radio and the 1.33.2005 SPL (Haykuro's "special" SPL - http://forum.xda-developers.com/showthread.php?t=517593)?
You do risk bricking your G1 with this SPL, but if you follow the directions in the thread exactly, you should be fine (do this at your own risk).
Also, make sure to do a wipe (Alt+W) in recovery before you try to apply (Alt+S) the build update.zip.

Nickizzle said:
Hey everyone,
I am writing this because a day of research and playing about with my phone has resulted in nothing.
I recently rooted my G1 european (UK) phone and ended up with the JesusFreke build absolutely no problems...
Today I updated to the latest radio and SPL (again, no problems) and went to put on the Virtudude Roger's mod first and it froze on the splash screen, so I reverted back to original Android, rooted again and went back to JesusFreke's build.
This time I tried Cyanogen mod, which also freezes on the splash screen.
I have tried going to both these builds straight from Android 1.0 or from the JesusFreke build with no success - it just freezes on the splash screen every time.
Anyone have any advice? Maybe theres something I'm doing wrong on the way?! I use recovery mode to format and load the flash images on
So much thanks in advance!
Click to expand...
Click to collapse
What SPL do you have? Are you wiping before you update?

Thanks for the great advice, I was actually following the instructions you provided and have 1.33.2005 SPL.
I just had no idea why it wasn't working, but I have now sorted it...
I put on the recovery utility from JFv1.43, format/flashed the image for Virtudude, restarted and then just left the house for a couple of hours whilst it was on the splash screen....just came back and it had booted in fine.
Now it boots fine every time (does take a few minutes to boot but worth it!)
So, all sorted now - again, so much thanks for the help - I honestly thought it was because I had an EU model or something like that; unfortunately, searching the forums for "EU" or "UK" doesn't bring up much because of the minimum character limit!!

Related

ONLY - Technical Support - ONLY

Disclaimer: As in every case your choice to flash any memory on your phone is YOUR decision and you run the risk of making a expensive Paperweight. Research Flashing and read post about new Rom's or Builds to learn from others mistakes.. There are a lot of risk takers here on XDA that will be glad to bite the bullet to help the community with rom stability and issues. But ultimately you CHOOSE to flash your phone Not us.
I created this thread for new users unfamiliar with Flashing and modding their phone to get technical Support for any technical Issue that comes up regarding the phone. However Please Avoid Posting things such as "I am bricked how do I fix" or "Help my phone doesn't Start up" Because they will not allow the more experienced users to Help you.
Suggestions:
1. List the following in the reply
- What Model Is your Phone (Should Be HTC Dream AKA Tmobile G1)
- What SPL are you using (Boot Holding Power + Camera then first line)
- What Recovery Image are you using(Stock, Jesus Freakes 1.42, 1.43 or HK)
- What Rom is Currently Loaded (Booted up go to Settings-> About Phone)
- What Radio do you have currently (Settings -> About Phone)
2. What are you Trying to do (Ultimate Goal)
3. What steps has you taken (In Detail please)
4. Once you problem has been resolved please Edit your Original Post indicating that it was resolved.
Thanks In advance for Keeping this thread Neat.
Some Reading Material for you:
APN Info Thread
General Questions Thread
G1 Wiki Thread
G1 Tips and Tricks Thread
jf recovery 1.43
doesnt seem like i need it because ive flashed beta 3 using 1.42 but i want it cause it has to have some capability that 1.42 doesnt right? Only problem is I have no idea how to flash it. I tried renaming the 1 in "haykuros hero rom" post to update.zip and it still said 1.42 when i went back 2 recovery. I dont use fastboot or adb or anything because I am a capital "N" noob and nothing seems to ever say how to do any of this stuff using a mac so.... that being said...can you help?
1. tmobile g1
2. haykuros latest spl
3. 1.42
4. ion
5. latest radio
goal: 1.43 recovery
steps taken: saw a lot of people ask the same question. searched. went back to the rooting thread attempted to enter the commands by pressing alt+x in the recovery console the way they were listed and placed the recovery.img file i unzipped from the hero thread on my sdcard. no luck.
build..?
I did my first fastboot recovery, even though I didn't need to. Pretty decent operation. Just wanted to get the feel of it. I think I'll be using nandroid and fastboot a whole lot in the near future
Goal: To either build myself, or at least play a part in the building of one sweetest ROM's. I guess i'll start small, with a theme.
(it's been a 12 pack of Mountain Dew and B movies kinda night.)
CC CEO said:
doesnt seem like i need it because ive flashed beta 3 using 1.42 but i want it cause it has to have some capability that 1.42 doesnt right? Only problem is I have no idea how to flash it. I tried renaming the 1 in "haykuros hero rom" post to update.zip and it still said 1.42 when i went back 2 recovery. I dont use fastboot or adb or anything because I am a capital "N" noob and nothing seems to ever say how to do any of this stuff using a mac so.... that being said...can you help?
1. tmobile g1
2. haykuros latest spl
3. 1.42
4. ion
5. latest radio
goal: 1.43 recovery
steps taken: saw a lot of people ask the same question. searched. went back to the rooting thread attempted to enter the commands by pressing alt+x in the recovery console the way they were listed and placed the recovery.img file i unzipped from the hero thread on my sdcard. no luck.
Click to expand...
Click to collapse
Installing JF Recovery 1.43 is just like any flash update for a rom...
You find and download the recovery file. Rename it to update.zip (Keep in mind that windows by default hides the.zip part so if you rename it to update.zip windows actually sees it as update.zip.zip.. This is a common problem.
Then Boot to SPL by powering off your phone and powering up with Home + Power Key.
Once loaded then hit Alt + L (If you don't have a modded Recovery already) and then If you have to wipe(which I usually do) Alt-W then you need to load the new firmware with Alt + S.
If all goes well it will load the new recover image and will reboot back into Recovery mode in which you just Home + Back to Exit and reboot.
I don't wanna step on anyones toes but I believe to load the new image after wipe it'll be alt + s....
Hero beta's
I've triend to install both Beta 2 & Beta 3 of the Hero build, but evertime it got to the setup screen it would force close. What can I do to get past this problem?
mvanwyk83 said:
I've triend to install both Beta 2 & Beta 3 of the Hero build, but evertime it got to the setup screen it would force close. What can I do to get past this problem?
Click to expand...
Click to collapse
With the beta 3 update update on your sdcard boot into recovery and wipe then flash then wipe again then reboot.
If you have a2sd already Use the adb recount Command and then adb shell to delete the system/sd/ folder.
Just a quick question:
I'm currently running
the Android 1.5r2 based Cyanogen build v3.3.1
1.43 recovery img
Hardspl
The latest radio update (the one with the I as the last character)
I would like to update to Haykuro's new bootloader to get more space and to be ready for the upcoming haykuro build, but I'm a bit scared by all the reports of phones getting bricked.
So my question is, if I install it using the update.zip on sd-card method, is there any chance of a brick?
Let me point out that I don't have a microsd card reader available, so I wont be able to flash the build I'm currently using right after updating the SPL. So far it's not entirely clear to me whether this can be a problem.
tia
Curunir said:
Just a quick question:
I'm currently running
the Android 1.5r2 based Cyanogen build v3.3.1
1.43 recovery img
Hardspl
The latest radio update (the one with the I as the last character)
I would like to update to Haykuro's new bootloader to get more space and to be ready for the upcoming haykuro build, but I'm a bit scared by all the reports of phones getting bricked.
So my question is, if I install it using the update.zip on sd-card method, is there any chance of a brick?
Let me point out that I don't have a microsd card reader available, so I wont be able to flash the build I'm currently using right after updating the SPL. So far it's not entirely clear to me whether this can be a problem. Tia
Click to expand...
Click to collapse
Before you consider flashing the new spl. Make sure you have a pvt revision board. Power + camera when turning on your phone. It will be at the top. If it says dvt don't flash.
You also need the 26I radio firmware.
If you do not have a memory card reader or a second memory card ten do not flash the new spl. Once you flash the spl, your phone will not boot until you flash a new Rom onto it
I believe this is correct. Anyone with experience care to confirm?
Actually now that I am rested and thinking straight.. Don't you load a recovery image by loading the recovery.img file on your sd card and booting to Bootloader?
Man I was sick and tired last night =)
Go to My Hero Thread and in the first post is the JF 1.43 Zip file you can use to Flash to JF 1.43 in update.zip format.
ubernicholi said:
With the beta 3 update update on your sdcard boot into recovery and wipe then flash then wipe again then reboot.
If you have a2sd already Use the adb recount Command and then adb shell to delete the system/sd/ folder.
Click to expand...
Click to collapse
Now is that process the same for Beta 4??
,
mvanwyk83 said:
Now is that process the same for Beta 4??
Click to expand...
Click to collapse
Should be. Can anyone confirm?
I put some music on beta 4. The album cover is in my pics but doesnt show where it should when playing music, do i need to somehow manually put it there?
Am I asking this in the right place even? thanks
1.
Tmobile G1
SPL: DREA100 PVT 32B
Firmware version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.627-00392-g8312baf [email protected]
Build Number: dream_devphone-userdebug 1.5 CRB21147201 test-keys
2. Upgrade to the Dudes Build (http://forum.xda-developers.com/showthread.php?t=507151) and backing up all my data and apps
3. Tried to update (by naming his build update.zip and updating) and also tried backing up data using the commands in his post (listed above)
cronin4392 said:
1.
Tmobile G1
SPL: DREA100 PVT 32B
Firmware version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.627-00392-g8312baf [email protected]
Build Number: dream_devphone-userdebug 1.5 CRB21147201 test-keys
2. Upgrade to the Dudes Build (http://forum.xda-developers.com/showthread.php?t=507151) and backing up all my data and apps
3. Tried to update (by naming his build update.zip and updating) and also tried backing up data using the commands in his post (listed above)
Click to expand...
Click to collapse
What errors did you get or what problems are you having?
stuck on android screen
hey guys, this morning i got the OTA cupcake update, and my phones been running fine all day, however, i just restarted it and its stuck on the android logo screen, it shows the shine going through the logo like it is loading but after a few seconds it stops, then does it again, is my phone shot? please, any help will be greatly appreciated
rschuman90 said:
hey guys, this morning i got the OTA cupcake update, and my phones been running fine all day, however, i just restarted it and its stuck on the android logo screen, it shows the shine going through the logo like it is loading but after a few seconds it stops, then does it again, is my phone shot? please, any help will be greatly appreciated
Click to expand...
Click to collapse
Wipe your phone. Press and hold home+power. Continue to hold it till youe see a caution triangle. Press alt+l and then alt+w when its done select reboot from the top of the list. Good luck
Quick Question
I am running the newest of everything, currently on Hero BUild 4
What actions should be taken to downgrade to the older SPL. I am getting extremely bad battery with this and can't handle it.
Mast3rmatt said:
Quick Question
I am running the newest of everything, currently on Hero BUild 4
What actions should be taken to downgrade to the older SPL. I am getting extremely bad battery with this and can't handle it.
Click to expand...
Click to collapse
From what I know, its a bad idea to downgrade your spl. Check you screen brightness and your screen time out if you are running an overclock program, try setting it to 384 max 128 min. Double check to make sure your screen actually times out. See if your wifi is running, as well as your gps. If you use twidroid change the rate from 5 minutes to 1 hour
i have to wipe my entire phone and loose everything now!!?

G1 Wont boot after SPL Update

So, I have just made a couple of changes to my phone. My mistake is that I did it all at the same time. So I dont know what fu***ed it up !
1. I formated the ext2 partition to ext3
2. I added a linux Swap partition (104Mb)
3. I loaded the CN 1.4 Recovery image
3. I installed the SPL 1.33.2005
I have been using JF 1.51 and I was having some issues after a recent corruption so I thought I will try JacHero 1.7 since I was planning on a clean install anyway. So the new SPL was for the Jachero rom.
Anyway, why i think the issue happened while flashing the SPL its because after I flashed the CN Recovery screen came up and it said "Formatting Cache" and it stayed on that screen for like 15 min. and I thought ok, it must be done and the Recovery menu was active so I just scrolled to reboot after which I was never able to boot past T-Mobile G1 screen.
I did eventually update to JacHero 1.7 after a wipe but still didnt seem to work. Still stuck at boot screen.
Any ideas ?
Any help is appreciated !!
Thanks.
If its the spl I know that one if I rem was the tricky one that couldnt be downgraded or so.
http://forum.xda-developers.com/showthread.php?t=517593 is the only thread on top of my head I can link you to. Hopefully it helps.
Sometimes the only way the danger spl will take is if you rename it to update.zip and click on apply sdcard update zip. Try doing that and see, also try a non hero rom and see if it boots, if it does and a hero won't chances are it was the spl
ITS WORKING !!
So I kept on messing around, I went into the SPL settings pressed lots of keys (not much clue wut i was doing) and I tried a couple of restarts and after messing around with everything.......somehow it booted into the new Hero rom (Dont ask me how !) but it was completely screwed up. Meaning, This HTC screen is the only thing I can see. If i turn off the screen and turn it back on, I will see the unlock screen of Hero (which looked really cool) but as soon as I unlock im back to this wierd HTC black screen where nothing happens!!.
Soooo I went back into the recovery mode and tried the nandroid restore option (AGAIN) only this time it went through and completed the recovery ! (It wouldnt do that the last 3 times i tried) and now I back to my JF 1.51
Not really sure if I still want to try Hero anymore
and thanks alot guys for your quick responses......I REALLY Appreciate it.
Thanks again for your help !
It's up to you, cyanogen just came out with donut in his expermental line of roms so now we are gonna be passed cupcake roms soon

Stuck after flashing

Hey guys, I usually try to avoid asking for help because I can usually find several topics to guide me on how to do thigns, but today I find myself completely stuck. So here's my story:
A couple of days ago I was running cyanogen's 4.2.4 rom. I had ended up with some bugs like not syncing with gmail and it was giving me 3-4 hours of battery life while idle and everything turned off. The previous rom had none of these problems. Anyway, I heard about Dwang's and decided to try out v1.11 of his rom and loved it. However last night when I tried to flash to version 1.13 it froze on my rogers screen. My last nandroid backup was the one made on the cyanogen rom. I spent all day fiddling around trying to do everything to get anything stable to run and now tonight I ended up overwriting the nandroid backup and now it can't boot anything up other than the fastboot and 1.4 loader. I've tried wipes loading older roms, newer one (both dwang and cyanogen)
I don't wanna touch anything else for tonight in fear of bricking my phone but I'm hoping someone can help. It's not bricked, but I feel at this rate and how frustrated I am I have a feeling that might happen and I want to avoid it.
I know there are some other topics that may be similar because I've done a search but I'm not exactly 100% that the solution given to them might be used for my problem as well.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA210000)
CPLD-4
RADIO:2.22.19.261
Ok well, I seemed to have made things a bit worse somehow. Now when I hold camera+ home it brings up a triangle with an exclamation mark and a phone logo. BUT I'm still able to fastboot.
Did you boot on the ADP 1.6 ROM?
Yes I did as it was one of the steps on cyanogens wiki. I even tried to flash it without flashing cyanogen's rom and what it does is just show the android screen, then when it finishes loading it goes black for a split second and then goes back to the android screen. I managed to load older nandroid backups of cyanogen again but whenever I try to flash the 1.6 and then either dwangs or cyanogens it doesn't work. I also cannot do fix_permission at the recovery screen. it tells me something about e2fsck.
Here some of the things I've tried today on the phone without any success:
Another thread had a similar problem and one of the tips was to fastboot and do
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.3.2G.img
so I tried that and now I am equipped with the ra recovery and when I try to flash the rom it still doesn't work. I also let it hang for about 20 minutes before trying something else.
I've also flashed it to 1.6 htc stock and it works but it doesn't let me have the proper recovery screen and whne I try to update with a renamed rom file it says installation aborted.
So now I feel stuck :-(

Radio update problem...

Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition
That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer
You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!
Turn your phone off, hold the camera button down, and power on your phone.
What do you see?
each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.
speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer
speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer

Stuck at splash after rooting us tmo mt3g

Okay I'm lost, weary of trying things as I'm not 100% clear on alot of this stuff.
Here's what I did, I recently had tmo replace my original mt3g, sadly the replacement gave the version is older or whatever message. I've gone through the steps and now I'm stuck at the boot up splash screen. I'll post what i've done so far, hopefully someone can identify whats gone wrong and steer me
Ok I followed the instructions here:
h~p://theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/
h~p://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
h~p://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
That worked, the phone was rooted and booting.
I then installed the the AMON_RA recovery img and I've tried both flavors
recovery-RA-sapphire-v1.7.0H.img
recovery-RA-sapphire-v1.7.0G.img
I forget at this point, but I think the G didn't work for me, but i have H working.
From there I began following the instructions on cynogen mod to install...
h~p://forum.cyanogenmod.com/topic/394-cyanogenmod-5-for-dreammagic-mean-lean-pastry-machine-v508-06192010/
h~p://forum.cyanogenmod.com/topic/278-installation-support-line-cyanogenmod-5-for-dreammagic/
h~p://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_HTC_Magic_%2832B%29
I booted the the recovery, wiped everything, installed the cm base, then gapps and powered down and powered on, stuck at splash...
I've tried a few variances and just to make sure, i went back to recovery and installed the Rom-RAv1.1.0H-signed-update.zip again to make sure it was working. It booted right up.
Ok so here is my phones info from the vol down + power hboot menu
sapphire pvt 32b eng s-off h
hboot-1.33.2005(sapp30000)
radio-3.22.20.17
apr 20 2009,15:30:43
I'm not sure of what else to include, my minds melted at this point.
It was so easy to root my old mt3g, this new model just makes me feel like an idiot.
*edit* Here is the info from my phones settings>about with the Rom-RAv1.1.0H-signed-update.zip loaded
Model: Ion
Firmware 1.5
Baseband 62.525.20.18h_3.22.20.17
kernel 2.6.27-cb85e129
[email protected] #3
Build #
cr843
Hmm
Did you root your phone using the MyTouch Rooting guide? Or the MyTouch 1.2 (has 3.5 mm headphone jack) guide? From what it sounds like you got the updated model of the MT3G.
If you used the Rooting guide for the old model and you have the new one, you will have issues. Heres the link:
h~p://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
If I'm right, you should have no issue re-rooting your phone.
Good luck, hope this helps.
<grin> that's another aspect of my mind melting yesterday, making sure i wasn't following instructions for the wrong version of the phone.
I have the original base model, no 3.5mm.
Tmo sent me the replacement phone about a month ago.
So that said, I think I followed the original versions instructions.
Flashing back to the old version
Rom-RAv1.1.0H-signed-update.zip
the phones worked fine all night and I got it doing the things i rooted for in the first place, sharing my cells inet to my laptop etc. so I can live with this until the weekend I suppose but still want to figure out why i couldn't get cynogen mod 5 running.
Okay i have an idea what might be going on, just my guess at this point.
I think i have mix matched mt3g-a and mt3g-b files.
Here's my thinking...
recovery-RA-sapphire-v1.7.0H.img - works
recovery-RA-sapphire-v1.7.0G.img - doesn't work, sits at splash screen
Rom-RAv1.1.0H-signed-update.zip - works, but shows up in settings>about Model = ION. I think Ion is the mt3g-a flavor...
I tried today to use flashrec, the first backup of my recovery failed. tried again it reported success. closed app opened and it gave me the option to flash the cyno recovery or restor mine, i flashed the CM and when i rebooted to the recovery it would just sit there at the splash screen. i could still boot normally and into the fastboot menu... I then went and downloaded the CM 5.08 install from a mirror.
I also tried the the newest cm v6 rc2, and update-cm-4.2.15.1-signed.zip
All stuck at splash on boot.
Fixed and working, I think it was my radio. I had a mirror post over ta the CM forums, and I was pointed to the correct radio and after flashing the radio and the g version of the recovery it came up, then flashed CM and Gapps and it worked...
I was also told to update my spl, but havn't done that part yet.
*edit* username is globeadue there, post should come up with a username search

Categories

Resources