I rooted my phone using this guide. I wanted CM7 on here, so I flashed the MR2.5 radio. My phone came with MR1. It flashed properly, but now I have no signal and it shows me as having no baseband.
What did I screw up? From my knowledge of radios from my DInc, I can't flash 2.5 again or it'll brick (can't flash the same radio twice in a row).
Would I be able to flash MR2, then MR2.5 again? Basically, wtf do I do, and why did this happen?
you flashed the wrong cm7...there are two versions...one for the mr1 radio and another for the mr2 radios
I didn't even flash CM7. I said I flashed the MR2.5 radio.
When this happened to me I made a backup of my ROM, flashed the file found here, http://forum.xda-developers.com/showthread.php?t=1082114, loaded my backup, and tried again with a different download of the MR2 radio. My theory on why the no baseband thing happened to me was a bad download... I've since started checking MD5 sums every time I flash anything through HBOOT which I should have been doing all along.
I'll try that. It shows me as no baseband, no phone number, no anything. Crap.
if you didn't flash a rom then its normal. You can't flash a 2.0+radio with an mr1 rom and have signal. Nothing is wrong just flash an mr2 rom.
Sent from my HTC ThunderBolt using XDA Premium App
Alright I'll try flashing CM7 then. I hope this works. This is a lot more involved than my Incredible, haha.
Edit: Yup, that's definitely it. I flashed my original MR1 ROM and radio and I'm fine.
Thanks guys!
If you have the MR1 rom, the MR2.5 radio will not work for it due to the new RIL.
And I have flashed radios twice in a row before and nothing has happened...but if you take my word for it it's on you
Yeah it was just something I heard when I was working with radios on my incredible. No clue how true it was, but it's not worth the risk.
I got everything sorted out, thanks guys!
pspkicks316 said:
Yeah it was just something I heard when I was working with radios on my incredible. No clue how true it was, but it's not worth the risk.
I got everything sorted out, thanks guys!
Click to expand...
Click to collapse
Bricks like that don't happen on the thunderbolt if you flash the radio twice in a row, but I still wouldn't recommend it
Related
Got the radio upgrade 3.3x and all works well with 2.x dcd rom, but upgrading to 3.0.1 has problems with phone calls. Both receiving or outgoing, the device resets 10 sec into the call. Also Voice Command 1.6 not working. sucks.
verizon xv6800
I'd be willing to bet millions you didn't follow directions when flashing.
Nope. Cooked a kitchen, tried the Verizon Rom....neither work with 3.0.1. works great with 2.x though.
Voice Command 1.6 now working OK as well under 2.3.2. I is happy. Still looking for good GPS software. I really liked Earthcomber, but doesn't work with this rom.
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
OK so I cry for help. Why the heck would I apply a Sprint update to a Verizon handset, granted both CDMA. I upgraded the radio at the same time as 2.2. The 2.2 DCD rom I'm using that WORKS WELL should be no different than the upgrade to 3.0.1. Unless I'm forgetting to stop customization with a soft reset.
You're not getting the point!!!
The only reason to flash sprint's official rom is so you can update the radio to its latest version. After this is done, it DOESN'T MATTER whatever rom you flash next, such as a Verizon rom. Use DCD's 3.0.1 rom it should be working. You would have known this if you read instructions. If you flashed the radio alone first, then your settings (ESN, MSID, etc) will be wiped. You will have to re-enter these either manually or call up Verizon to do it for you. This is probably why you can't make calls.
Exactly my point. I flashed the radio with the Oli 2.4 and updated the radio from stock verizon. Then flashed 2.3.2 and all is good with the new radio. So why doesn't it work with 3.0.1? I just found my way to the In and Out Burger via Odyssey Mobile locator.
Everyone keeps telling me that i didn't follow the destructions but they don't point to where they are.
Maybe wrong radio ver?
Crap. Mine says 3.24.00. I guess that's my problem. I'm an idiot.
Please point me to the proper radio D/L.
Thanks,
Sorry for asking what is probably a simple question, but I am having the same problems. I have SPL-2.40.Olipro atm, installed the verizon ROM upgrading to 3.0.1 from NexVision's Hybrid rom. My radio is upgraded to 3.25 or whatever it was supposed to do fine. On vibrate mode, when a phone call is incoming, I get stuck in an ever ending vibrating. I can text, and attempt to cal lsomeone but nothing can be heard and no one can hear me. I know i screwed up somehow- but what exact steps do I do to remedy this?
Thank you in advance
We have to do the Sprint radio update to 3.35 first, which is an upgrade from 3.27. Then go to ROM 3.0.1.
It's always interesting to me how people jump up to say "you're doing it wrong" but don't tell you how to do it right.
Here's how to do it right.
http://forum.ppcgeeks.com/showthread.php?t=17667
Gecko122, There is more to the Sprint file than just the radio... It includes the ROM as well.... My understanding is this:
1st - Run Olipro unlocker 2.4
2nd - Run Sprint Official upgrade , NO CUSTOMIZATIONS.
3rd - Load Custom ROM.....
That has worked for me.....
PS - the DCD 2.x.x series do NOT play well with the new radio, hence the 3.0.1 kitchen.... Driver differences....
do i have to flash back to a former version of dcd or anything? or can i start from a messed up 3.0.1?
hi Penn,
Well, exactly what have you done to your phone?
Bootloader version?
ROM version?
Radio Ver?
Then we can start from there and develope a plan to help ya.
Ignore that above - I re-read you original post....
Here's what you can do and correct me if I'm wrong Penn...
You have Oli-pro 2.4 bootloader loaded
You have DCD 3.0.1 ROM loaded
You have the 3.27 Radio loaded?
If the above is true, then we have options..... Let me know
gcincotta said:
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
Click to expand...
Click to collapse
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
Click to expand...
Click to collapse
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Gecko, the reason why I did not "tell" you how to do it the right way is because dcd's thread has 94 pages of information on how to do it the right way. I've even posted several times on different pages in that thread with explicit instructions on how to. While I am always very eager to welcome newcomers to this community, I also strongly encourage them to read, research and educate themselves before touching their device. It doesn't mean I'm not a nice guy and don't like to help, because if you search my posts you will see that I help a lot around here. If you had simply taken 20 minutes and even skimmed dcd's thread, you would have found the answer yourself in no time.
gcincotta said:
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Click to expand...
Click to collapse
Wow... I'm sorry, I had not been keeping up with the issues of others, so until you said that just now, I had no idea. You are right, I am really lucky, so thanks for bringing it to my attention.
No problem
I am rooted and using BAMF 1.63, and want to do a clean move to 2.0 Beta 5 without errors.
I've been told that I don't need to do the entire AutoRoot w/MR1 program, but that I should instead just flash using the MR1 rom. The link below is where the files are located here on XDA, but see 3 files listed.
I assume that what I need is the last one, the custom ruu with MR1 included...BUT, will I also need to download the exploits file that contains busybox, wpthis, psneuter, su, readme.txt, misc.img, and hbooteng.nb0?
http://forum.xda-developers.com/showthread.php?t=996616&highlight=prerooted+RUU
You shouldn't need to do the whole root process again, when I switched from 1.6.3 to 2.0, all I needed was the new GB radio. I haven't had any issues with it & I didn't do any of the MR1 stuff
So, that process then would be to:
place radio file on the SD root and reboot so it will flash.
Remove the radio file, and then boot into Recovery and install 2.0 Beta5 ReMix using CWM
That's it? Sounds too easy. lol
have you read jcase's notice about the leaked gb radio, you might want to give it a read before taking the plunge,
I just came back to froyo, bamf remix 1.6.3 style
ibsk8 said:
have you read jcase's notice about the leaked gb radio, you might want to give it a read before taking the plunge,
I just came back to froyo, bamf remix 1.6.3 style
Click to expand...
Click to collapse
I'm new to all this and monitor androidcentral more, only coming here for info on released files. When I tried BAMF 2.0 Beta4 recently I didn't do the radio file, and the phone was dead with no signal. I'd like to avoid that so flashing with a radio file is necessary. What or where is the concern with the leaked radio file? Instead of what not to do, are you able to offer a link to a good radio file compatible with the new BAMF Beta5? Thanks!
EisBlade said:
I'm new to all this and monitor androidcentral more, only coming here for info on released files. When I tried BAMF 2.0 Beta4 recently I didn't do the radio file, and the phone was dead with no signal. I'd like to avoid that so flashing with a radio file is necessary. What or where is the concern with the leaked radio file? Instead of what not to do, are you able to offer a link to a good radio file compatible with the new BAMF Beta5? Thanks!
Click to expand...
Click to collapse
A few people are getting bricked TBs from the GB radio they are thinking. Enough people are having this happen that the ROM devs are advising everybody that has gone to a GB ROM, to go back to a Froyo ROM until we get an updated GB radio.
leoingle said:
A few people are getting bricked TBs from the GB radio they are thinking. Enough people are having this happen that the ROM devs are advising everybody that has gone to a GB ROM, to go back to a Froyo ROM until we get an updated GB radio.
Click to expand...
Click to collapse
Well, I didn't get bricked, but I was without connection/service to anything after doing the latest radio file followed by BAMF 2.0 b5, until I restored to my last working backup. Not fun. I downloaded TeslaCoil to give it a try, but my TB has turned off on its own 3 times now in 3 days.
EisBlade said:
Well, I didn't get bricked, but I was without connection/service to anything after doing the latest radio file followed by BAMF 2.0 b5, until I restored to my last working backup. Not fun. I downloaded TeslaCoil to give it a try, but my TB has turned off on its own 3 times now in 3 days.
Click to expand...
Click to collapse
You didn't brick because you weren't running the GB radio. In order to run any GB ROM with signal and whatnot, you need the leaked ALPHA GB radio, which is supposedly causing some phones to brick. And just because you run the GB radio fine for a few days doesn't mean you are in the clear. This has been happening to people a couple days after running it.
still not sure why the whole brick thing vanished as fast as it came, nobody bother to ask the simple question "was your phone having alot of reboots befor,root no root stock ruu or custom rom". my original tbolt was rootet cause it would reboot all the time as stock, was running bamf 1.63,never had gb on it,well it started doing it again,so when the ota came out i put the phone back to stock s-on did the ota and 2 days later it had the reboot contious could not do anything, that tells me it was hardware and it was replaced no probs,htc and verizon have been aware of the problem
Sent from my ADR6400L using XDA Premium App
Hopefully this isn't too hard to solve. I have an HTC Evo, and offered to root my friends Thunderbolt. I rooted it fine, everything works flawlessly, and I even flashed a ROM without an issue.
Now, here is the thing I cannot figure out. Every ROM i have installed (BAMF, Synergy, etc) has no radio when it boots up. There are two processes that stop responding (A Sync process and a DM process). There is just simply no radio at all. I can connect to wifi, and I can browse the internet that way, but it refuses to show any connection to Verizon.
Any idea as to what is causing it? Again, I am usually on my Evo, so the Thunderbolt is a little bit different territory.
Keep in mind, all the ROM's flash and boot fine. Everything on the ROM works fine, with the exception of the radio.
Thanks for your help guys.
You have to install a new radio for the gingerbread Rom. In the dev section there is a Rom and kernel list. Find the mr2 radio there. Rename it to PG05img.zip, place on root of SD card, boot into hboot (phone off, hold vol down and power. It will flash the radio. Once it reboots delete or rename that radio file so it won't try and flash it again the next time you boot into hboot. And your done.
sent from my BAMF'n thunderbolt.
Do you see any notification of data on the phone? (1x, 3g, 4g)
Did you make sure to snap the back of the battery cover on tight as it has a connection for the antenna for the battery?
Are you trying to flash the MR1 radio on a ROM that requires either MR2 or MR2.5?
All of these could cause the issue you are having.
Have you tried to reflash one of the radios in hboot? Plus with not all the roms based on the new radios and some of them are this can cause you to lose data if the rom isn't compatable with the radio. Just make sure the roms you are installing are not based on the MR2 or MR2.5 radio while you have a MR1 radio and vice versa.
I hope this helps. If not you may want to just find the original rooted stock OTA ruu and reflash it in hboot. This will wipe all your data so if you have a way to back up apps and data like mybackup pro or titanium backup.
Here is the rom and radio listing thread
http://forum.xda-developers.com/showthread.php?t=1081930
Edit: Yeah almost forgot about the battery cover having the antenna on it like Beastclaw said
Ah. Downloaded the MR2 file, renamed it and flashed it and it worked perfectly.
Thanks so much, you all are the ****.
Going back to the Evo section now.
Again, thanks for all your help. *Waves*
In your opinion do I need to flash the radio.zip after cm7. If so wat does it do for my device? Do I get better service/ faster data speeds?
Thanks, tHe NoOb
Sent from my MB860 using Tapatalk
I think the radio that you have currently should work well enough.
I had the 1.97.00 radio and found that cwm was giving me a 1 bar issue. Same thing with aosp. And input so I installed the 1.77.30 radio via cwm. Wish I had a cwm version of the 1.97.00 radio just to try while im at work. Seems the 1.77.30 radio switches from H to 3g less in my area than the. 97 radio.
ok, it seems as if my service is pretty good compared to what yours was before you flashed it. ill keep it for now. thanks for the replies
Please help Radio flash
I want to flash the radio to my unlocked and cwm installed atrix 4g. I used to have 2.3.4, 4.5.91 ATT stock software, but went to cyanogenmod 7.
What radio do I need to flash in cwm? There is a radio.zip file on briefmobiles website, I just want to make sure I am downloading the correct one.
I want to flash because it is taking a while to get a gps lock in CM7, where in the stock rom it would happen almost instantly.
trekbikedude said:
I want to flash the radio to my unlocked and cwm installed atrix 4g. I used to have 2.3.4, 4.5.91 ATT stock software, but went to cyanogenmod 7.
What radio do I need to flash in cwm? There is a radio.zip file on briefmobiles website, I just want to make sure I am downloading the correct one.
I want to flash because it is taking a while to get a gps lock in CM7, where in the stock rom it would happen almost instantly.
Click to expand...
Click to collapse
Not 100% sure but gps lock on isnt slow because of radio but couz of CM7 i got stock radio and its also slower then on GB. also CM7 doesnt install radio if im not mistaken if u had GB radio u should still have it
what cm says
code.google.com/p/atrix-dev-team/wiki/FAQ CM7 is saying if you are having slow locks to reinstall the radio. I'm just wondering how I can accomplish this through cwm.
***Pre warning***
Turning your phone s-off gives you a chance of bricking your phone. I am not responsible if you try these steps and have problems. Also you will loose all your data as you will be wiping your phone multiple times. Make sure to backup all your data (I used Titanium backup) OK?! :good:
I had done a ton of research trying to fix the GPS on my HTC Jewel and never found a solution that worked. Issue was the GPS would not lock. I was originally running MeanRom, then JellyBam, and finally switched to CM10.1 nightly builds, all with no GPS. Last night though I finally fixed it and wanted to post this for anyone else having this problem.
Prior to last night here is how my phone was setup:
S-On
Hboot 1.19
Radio 1.12.11.0890
CM10.1 20130224
I saw that HTC released a new update, and started digging on how to update when on a custom ROM. I realized that I needed to go s-off which I had tried last year with LazyPanda, but it failed.
Last night I was able to go S-Off following directions from FacePalm: http://forum.xda-developers.com/showthread.php?t=2163013
It was a lot easier than DirtyRacoon and I'm running Win7x64 which DirtyRacoon says is not supported by them.
Once I was s-off I downloaded the latest Radio 1.12.11.1210 from: http://themikmik.com/showthread.php?13192-RADIOS-RECOVERY-FLASHABLE-Jewel-Radio-Collection
I confirmed that the radio upgraded successfully and rebooted. I was then prompted to activate my phone, and when I tried to activate it gave me the error that I was not authorized! With some help from the FacePalm IRC channel I was pointed to having to flash stock to be able to re-activate and then flash again back to your custom ROM.
I downloaded and flashed with Stock_Rooted_Deodexed_2.13.651.1 found here http://themikmik.com/showthread.php?14585-ROM-Kernel-2-13-651-1-Stock-Rooted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
Booted and re-activated, and confirmed GPS working! Then I re-flashed with CM10.1 20130228 and GPS was still working!
I hope this helps others as I have seen a lot of forums with people complaining about the HTC Jewel GPS and saying it's faulty hardware, unfixable, or their fixes are all in app software related.
Thanks!
One thing that I would like to add is if you go stock, do NOT turn off your GPS after you get a lock. I usually have GPS turned off to save battery, but it was the reason why the new ROMs couldn't get a signal.
So to recap
1. Go back to stock
2. Get any old signal even for just a second
3. Immediately flash your new ROM without turning off GPS
4. Enjoy
This indeed works.
I don't like Sense-Based ROMs, so the first thing I did after getting my Jewel was S-Off, and I'm running AOKP. The GPS was driving me crazy, and I couldn't figure out how to get it working.
I updated my radio, flashed a sense-based ROM, locked GPS, then reverted back to AOKP, and it works flawlessly!
This method works!
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
The way I fixed the problem before was to flash back to sense, clear maps data and flash back to CM10.1. Voilà
I use waze
xlxcrossing said:
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
Click to expand...
Click to collapse
The only reason you have to go back to stock is to re-activate your phone.
xlxcrossing said:
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
Click to expand...
Click to collapse
pbedard said:
I use waze
Click to expand...
Click to collapse
So do I, but before I did this waze just searched for GPS signal.