Hi,
I followed this guide for rooting and JF'ing my G1: http://www.androidandme.com/2009/05...r-rooting-your-android-g1-to-install-cupcake/
Everything worked fine but I cannot for the life of me get the radio to update.
It's stuck on Baseband: 62.33.20.08H_1.22.12.29
I downloaded the HTC radio update, renamed it to update.zip and followed to install procedure (home+power, alt-s).
I have tried wiping the phone beforehand etc. as well, but doesn't seem to make a difference.
It does not show any errors or anything, and seems to complete successfully, but the baseband never gets updated.
Is there something else I can try?
Thanks
If I were you, my next step would be to reflash jf.
Also, did you install the new radio update before jf 1.5? I heard that was the right way to do it.
I've tried reflashing to 1.0, reflashing radio back to original, then updating radio, updating OS - radio version still stuck on the same :/
is the official radio update signed with testkeys or "official" key?
i got my update package from haykuro's site and it worked fine.
you could also try reflashing the recovery image as suggested in the steps to get root, then update the radio image again. also remember to press home+back and wait till the phone reboots itself.
What's the radio package you're using? (Link/filename)
If it's not http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip, then it's the wrong one.
>>If it's not http://sapphire-port-dream.googlecod..._22_19_26I.zip, then it's the wrong one.
This is the radio package I'm using.
>>you could also try reflashing the recovery image as suggested in the steps >>to get root, then update the radio image again. also remember to press >>home+back and wait till the phone reboots itself.
Have reflashed back to original firmware (removing root and hardspl), then tried RC7->RC8 upgrade (radio is not updated) and then OTA update to Android 1.5.. again the radio isn't updated.
I have also tried keeping the phone rooted, and manually updating to stock android 1.5.. again radio isn't updated..
I'm all out of ideas?!
It's starting to sound like you've got a bad EEPROM to me. Does it go through all the normal steps? It should unpack the update, prompt you for a reboot, show a pic of a chip with an arrow pointing to it, and finally reboot again. No errors reported?
Hi,
Thanks for your response.
You're right - it goes through the entire procedure 'successfully,' i.e. it reports no errors and prompts for reboot, then does another reboot cycle after the 'unpacking' logo.
Just for everyones benefit:
Got the handset replaced - must have been a bad EEPROM as mikedmayer suggested.
I'm glad you were able to do that. What did you tell T-mobile? I can just imagine the blank look on the cust-serv's face when you try to tell them you think it's got a bad EEPROM because when you try to flash the radio it wouldn't take. Either that or them asking you why you're trying to flash your own radio.
Related
I've got an ADP1, and I'm trying to upgrade to JF's v1.5 image. I started from JFv1.43 and radio 1.22.14.11, which seems to work fine.
From there, I flashed the new radio image, wiped, and flashed the JFv1.5 image. I copied image files onto the SD card root as "update.zip" using the USB cable into a booted Android environment and then flashed them using Alt+S on the (JFv1.43) recovery screen.
Here are the files I've got:
aeecdb49b74a0d4bb67f9d8af70c1889 ota-radio-2_22_19_26I.zip
8d78b985316ec77f81c71cab0eeb9f27 JFv1.50_ADP1.5.zip
On the first boot after flashing JFv1.5, I get three bars, can go through the sign in wizard, and can surf the web. In the phone info screen, it shows the correct baseband version. On second and subsequent boots, I get absolutely no signal (zero bars with an X) and in the phone info screen it shows the baseband version as "unknown".
Reflashing the radio image has no effect with either the 2.22 or the 1.22..11 radio. Reflashing the JFv1.5 image makes it work again for a while, but breaks again with the next reboot. This isn't specific to the JF image either - Hv1.5r3 gives me the same behavior.
Further tests:
- JFv1.43 with radio 2.22 works fine.
- The HTC ADP1.5 release breaks the same way. In this test, web connectivity broke before the first reboot; I had gotten the same result in one of my JFv1.5 tests too, so the reboot may not be the key thing.
Any ideas what I might be doing wrong?
MD5sum
I can confirm that the MD5 sum of the JFv1.5 image is correct. I just installed the two images, like you, and it works fine. (After entering my PIN, it cost 10 seconds before I have bars)
Did you check the MD5 sum of the images after you uploaded them with the android/recovery shell? I don't know if the recovery will detect a corrupt image, but I always check it just in case. I downloaded the image over 3G.
I have a T-mobile G1.
tomvleeuwen said:
Did you check the MD5 sum of the images after you uploaded them with the android/recovery shell?
Click to expand...
Click to collapse
In trying to test this, it magically works now.
I hate it when that happens - if a computer decides to magically work by itself, that means it can decide to magically break again by itself whenever it wants to.
Specifically, I applied the JFv1.5 update over JFv1.43 without wiping this time and I'm now unable to replicate the unknown baseband issue by rebooting.
Edit: Apparently by "works" I mean "google maps and the market both don't work at all". But that's a new problem. Whee...
In playing with the JFv1.43 to Xv1.5 (no wipe) upgrade path, I ran into a couple more issues. That path would consistently result in no working market, and I could only get Google Maps to work on Hv1.5r3.
But I've come up with a new strategy that largely seems to work:
Wipe
Install JFv1.42_R33
Wipe
Boot, Login to Google
Install JFv1.5
When I do this, I get signal and the market works. Google Maps shows a broken icon with the class name and won't launch, but I've basically got a working v1.5 phone.
Apparently all of this stuff just works for everyone else, but I figure I might as well document the fact that it took me two days to install a point-release update on my telephone in case anyone else is equally incompetent.
Edit: Apparently I hadn't installed the new radio. Doing that last doesn't seem to have broken anything.
I managed to solve the Google Maps thing.
I deleted these files:
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.maps.xml
/data/data/com.google.android.apps.maps
/system/app/Maps.apk
Then I copied the stuff under /system over from H1.5r3.
I'm relieved - finally Android acted exactly the way I expected it to.
Update 1.5 + radio
Hey, I am also having a problem with updating my g1 when I update to the 1.5v and new radio. When I updated to the 1.5v phone was not allowing me to make calls. I updated the radio and then it started acting crazy. No gps, internet, when a phone call come in it automatically went to speaker phone and none of the buttons would work. I couldn't bring up the dial pad or get to the menu. I had to go back to the old radio and old 1.43adp1.1h build. Has anyone gotten this to work and is there a certain order to update and when to wipe. Also, do I need to have a certain build in before updating and could the copies of the radio and build I got be bad. They came in on my jf updater and downloaded ota.
Current Setup :
HardSPL (latest, 3.56 I believe)
Radio: 1.65.29.22 (from Niki or Neon, almost positive it was Niki)
Solace v3.1
Decided I wanted to go back to newest radio, attempted to flash to it; hit a snag at about 78%. Progress didn't update for a while, then to 100%. Update app said there was a flash error, and it did not complete correctly. Device restarted, stuck at bootloader. Re-attempted the flash, same result.
Next, I tried flashing AT&T's latest ROM. Stalled at about 76%, message about having a communication error, walked through the apps troubleshooting steps; it tried (and failed) again.
Tried the latest HTC direct ROM, same result.
Tried to flash the latest HTC via MicroSD card, got 20(ish) percent through, the Radio line then went red and said "RSA Failure". Then that whole process died on me as well.
The only way I can get my device back up to run MTTY to remove the RUU flag. When issuing the "task 8" command to format, it instead reboots the phone. The phone will come up normally after that.
Since I got it back up, I have tried flashing once again, and am getting the same result. Am I just stuck here now?
It's not that I don't like this ROM, I'm just wanting to update the radio. Any ideas what else I might be able to try?
Try using the search function next time before you create a new thread.
If you would tryed you could find this post
Yes, thank you...except that I started my thread saying that the proposed solution was exactly what CAUSED the problem to begin with. I tried to flash to the 1.70.x radio, which is where I got the flash write error.
Anyone else?
Now that you can get it up normally, have you tried going to a stock HTC ROM first, then the new ROM, then the radio? Or HTC, radio, new ROM? I'd probably do it the second way. You said you tried flashing stock before getting it up again, and that you tried flashing after getting it back up, but you didn't state what you've tried flashing after getting it back up.
Since I've gotten it back up, I've tried both OEM and radio only. Both have the same result.
Really at a loss now as to what to try next.
Did you try the 3.29Hard2 SPL? I haven't encountered your issue and wish I could be mroe help here. My only thoughts would be to try a different SPL, or perhaps looking into the ForceUSB issue. Best of luck.
Hi,
Alright, im totally new to this; I'm trying to run Android on my HD2...
So, All guides I found kind of talked about the same things:
1, Flash phone with HSPL3
2. Flash phone with Radio 2.15.50.40
3. Flash magldr v.1.13
4. Download a NAND ROM -- I was first trying with Cope's Cyanogen Rom, kept getting stuck on GO GO GO! (in magldr) after a while I actually got it to work, but couldn't get data to work, the first time I restarted the phone it got stuck again....
Then I flashed official tmobile wm, got rid of magldr, and started all over, but this time I tried flashing MDJ's Cyanogen Rom, however after resolving several previous issues i got stuck on GO GO GO! again...
also, I have tried with both magldr v 1.11 and 1.13
-------------------
Is there something wrong with the previous steps I took? Any suggestions?
There is another thing that was always wrong with my phone which might be causing this problem; ever since I got it it would sometimes get stuck on the first purple "stay together" screen and not want to move... Even after I restart the screen would persist, and the only solution was to let it 'chill' for a while before attempting to turn on again...[It got stuck even when I flashed the wm to get rid of mangldr]
So any suggestions on how could I get Android running ???
Thanks
Never mind....
It seems to have fixed itself!!! THIS IS GREAT!!! Skyfire, one bus away!!!!
Thanks to all for this awsome forum and for the great roms!!!!
xzpx said:
Hi,
Alright, im totally new to this; I'm trying to run Android on my HD2...
So, All guides I found kind of talked about the same things:
1, Flash phone with HSPL3
2. Flash phone with Radio 2.15.50.40
3. Flash magldr v.1.13
4. Download a NAND ROM -- I was first trying with Cope's Cyanogen Rom, kept getting stuck on GO GO GO! (in magldr) after a while I actually got it to work, but couldn't get data to work, the first time I restarted the phone it got stuck again....
Then I flashed official tmobile wm, got rid of magldr, and started all over, but this time I tried flashing MDJ's Cyanogen Rom, however after resolving several previous issues i got stuck on GO GO GO! again...
also, I have tried with both magldr v 1.11 and 1.13
-------------------
Is there something wrong with the previous steps I took? Any suggestions?
There is another thing that was always wrong with my phone which might be causing this problem; ever since I got it it would sometimes get stuck on the first purple "stay together" screen and not want to move... Even after I restart the screen would persist, and the only solution was to let it 'chill' for a while before attempting to turn on again...[It got stuck even when I flashed the wm to get rid of mangldr]
So any suggestions on how could I get Android running ???
Thanks
Click to expand...
Click to collapse
Hi, Can you please tell me how do you fix your data to work? On my HD2 everthing iworks fine except data using phone connection ( Data works fine on wifi). Please let me know how to fix this or send me a link for your android ROM. I am using Flash phone with HSPL2.08
2. Flash magldr v.1.13. Anroid version 2.2. I dont know the radio version i am using.
Thanks in advance. Mathew
I recently rooted and started applying roms to my nexus s. Everything was going fine until my network data stopped working.
Have tried to unroot and return to stock but cant seem to get it right. whenever I try to use clockwork recovery any update zip i apply fails. Im currently on:
version - 2.3.1
baseband - 19020AUCKF1
kernal - 2.6.35.7-g7f1638a [email protected](hash sybol that isent on my mac keyboard)1
build - GRH7
I am based in the UK and think nthat my radio could be wrong?
When I factory reset in 2.3.1 i get the official update to 4.4 which dowloads, verifies then on installation stops and wont complete.
I am confussed with all the terminoligy and find the info on here overwelming to follow correctly.
on another forum i got the response that if i dont understand the process then I shouldent be doing this. Fact is I thought I did know what I was doing until it went wrong.
Could somebody be good enough to help me through this so I can restore my nexus s to working order please?
Read this thread: http://forum.xda-developers.com/showthread.php?t=1116884
Check your phone model, behind the battery. You probably have a gt-i9020 since you are in the UK.
Probably you need to flash the correct radio. What's a good choice? If you do have 9020, anything in the list with kb3 in it.
Kb3 has no limit to how fast it can upload data, which can be a benefit depending on how you use your phone. Most people would choose kl1 which is the most recent.
Download and flash in cwm recovery. Reboot.
Let me know if that works for you.
pnut1982ad said:
I recently rooted and started applying roms to my nexus s. Everything was going fine until my network data stopped working.
Have tried to unroot and return to stock but cant seem to get it right. whenever I try to use clockwork recovery any update zip i apply fails. Im currently on:
version - 2.3.1
baseband - 19020AUCKF1
kernal - 2.6.35.7-g7f1638a [email protected](hash sybol that isent on my mac keyboard)1
build - GRH7
I am based in the UK and think nthat my radio could be wrong?
When I factory reset in 2.3.1 i get the official update to 4.4 which dowloads, verifies then on installation stops and wont complete.
I am confussed with all the terminoligy and find the info on here overwelming to follow correctly.
on another forum i got the response that if i dont understand the process then I shouldent be doing this. Fact is I thought I did know what I was doing until it went wrong.
Could somebody be good enough to help me through this so I can restore my nexus s to working order please?
Click to expand...
Click to collapse
can you make calls? if you can, check your apn settings, settings>Data and networks>More>APN and delete everything, and retype the correct values for your carrier. if calls doesn't work, follow the post above. ^
I've tried just about everything to flash a new version of the radio firmware on my 9020a. I've used the Radio Flashing Guide and tried every version available for the 9020a. Each time, the flash reports that it was successful, but no matter which one I choose, baseband still shows I'm running i9020aucke1 when I boot it back up.
I've also flashed the stock ICS OTA update 4.04 for the 9020a, thinking "well, THAT has to do it." but still I'm stuck on cke1.
Are there permissions that may be wrong? Is there anything else I can do? I want to flash a new radio because e1 is terrible for me. It won't switch between "3g" to "H" and just spins it's wheels and I get no data. Sometimes I get ZERO signal. If I reboot or switch Airplane Mode on & off, data comes back and works for a while, but then reverts back to working like crap.
Thanks a lot.
Update
I was trying to flash via Clockworkmod. I used ADB FASTBOOT and the radio is now on J1.
So, if Clockworkmod isn't working, use ADB FASTBOOT.
metalgeek said:
I've tried just about everything to flash a new version of the radio firmware on my 9020a. I've used the Radio Flashing Guide and tried every version available for the 9020a. Each time, the flash reports that it was successful, but no matter which one I choose, baseband still shows I'm running i9020aucke1 when I boot it back up.
I've also flashed the stock ICS OTA update 4.04 for the 9020a, thinking "well, THAT has to do it." but still I'm stuck on cke1.
Are there permissions that may be wrong? Is there anything else I can do? I want to flash a new radio because e1 is terrible for me. It won't switch between "3g" to "H" and just spins it's wheels and I get no data. Sometimes I get ZERO signal. If I reboot or switch Airplane Mode on & off, data comes back and works for a while, but then reverts back to working like crap.
Thanks a lot.
Click to expand...
Click to collapse
What recovery and what version are you using?