Database Info

Unable to update Radio

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.

strange ns4g issues

I used odin when the 4.0.4 official leak was posted here. I since uses the one click software restore back to 2.3.4. At first it gave an issue with the radio. On my phone while restoring it said "radio fail" but the phone seems to be working.
Now I manually updated the unrooted Sprint official 4.0. And my phone since the very first thing I said, has been randomly rebooting, I tried a different battery and it does the same thing. It's also real laggy. Any advice? Are there stock 2.3.4(7) files I can odin? I want it completely factory. Or suggest the problem? Thank you.

Bumping

[Q] Would Samsung fix my bricked phone?

I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy

If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?

If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham

Yeah, you can still fix it. No need it to bring to samsung

Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?

random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.

cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!

Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!

random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!

[Q] Stuck at Bootloader after reboot on CM10.2

This has happened to me several times and I am seeing that other people are running into this problem with no fix found.
Everytime I try to install CM10.2 onto my xt926 I can never get past the unlocked bootloader warning screen after a reboot. I can still access CWM which is the recovery I'm using. I have tried clearing cache, data, factory reset, fixing permissions, reflashing the rom. The only way to get a working phone again is to flash stock 4.1.2 using RSD.
Then I remembered seeing an article a while ago saying that their were two versions of an OTA update for Razr HDs because for some reason their were slight differences between some phones, hardware wise.
Could this be the reason for these random phones not accepting CM10.2 installs?
Also if anyone has any ideas to get past this. I read someone had luck toggling bluetooth on and off for some reason but it didn't help me. I'm at a loss here and would love to play with Android 4.3 but I guess its just not in the cards...

ive got the same problem to i finally decided to get rid of safestrap and unlock my phone. now im stuck on stock rom because no roms will work after a reboot. theres two diferent stock 4.1.2 firmware files. one says mr4 the other one says mr2 anyone know the diference?

Not sure. I just use the RazrHD Utility 1.21 for that, its a lot easier. Also I have heard that 10.1 may work for us, just not 10.2 for whatever reason

[Q] Reboots 30 into loading ROM

From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly

talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.

When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita

Recovery: Custom TWRP 2.6.3.0 w/selinux support

And what errors did it give you when trying to install Gummy?
Sent from my Evita

The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF

I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita

You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.

jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.

timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".

xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.