I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.
STEyeAndroid said:
I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.
Click to expand...
Click to collapse
You need a gingerbread radio for a gingerbread rom.. so MR2 or MR2.5
Sent from my ThunderBolt using XDA Premium App
i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff
poloboogie said:
i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff
Click to expand...
Click to collapse
when you say everything is the same, do you mean it still has the previous radio version number?
I'd suggest that you both:
1) Wipe data/dalvik/cache and flash back to a froyo ROM where you do have a signal
2) Upgrade from froyo to the MR2/2.5 radio
3) Re-wipe data/dalvik/cache (or even do it twice for good luck ) and re-flash BAMF 3.0
If its worth doing, its worth overdoing, especially when you're messing with radios and the like. Best of luck!
That's the same problem I first had with gingeritis before flashing the correct radio.. if you are still experiencing the problems after the radio flash i would suggest confirming the radio did install by checking the version number..
if it is all correct do as MattBeyers said and wipe and reflash
Thanks, that seemed to work. I still got a couple of force closes but much less than before. Also I can see my radio now! If I wanted to restore my old my Backup (Stock Froyo - MR1), do I restore my backup then flash MR1? If so, does anyone have a link the MR1 image? TIA!
I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App
MattBeyers said:
I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App
Click to expand...
Click to collapse
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.
I tried mr2 and mr2.5 but could only get 3g. Went back to CM7.
Sent from my ThunderBolt using XDA Premium App
Mr_Joshua said:
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.
Click to expand...
Click to collapse
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )
Make sure u have a gb radio mr2 or mr2.5
MattBeyers said:
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )
Click to expand...
Click to collapse
This makes sense from a logical reason. Perhaps a ROM developer on this site can confirm this.
I'm a total noob but thanks to XDA, and literally hours and hours of reading I was able to flash the original ics leak from DG, the latest 4.0.4 leak, install CWM touch, and successfully root my AT&T skyrocket. Thank you all! However, I am one of the few that have had better data and voice with the ucalc4 radio despite reports to the contrary. I decided to try flashing LeeC's CWM flashable ucalc4 radio after doing a backup. After flashing the zip and rebooting, i was unable to get a signal. The baseband was also listed as "unknown". I tried putting the phone in and out of airplane mode, reinserting the sim and rebooting but to no avail. Finally, I gave up and restored my backup and upon reboot, lo and behold.....under baseband it says ucalc4!!! 4-5 bars of service instead of 1. Signal Strength -85dBm 14asu (not sure what this means and didnt record settings prior to modem flash) and hspap instead of hspa under phone status!! (No LTE in my area). I'm completely dumfounded now. How did the ucalc4 modem stick, after restoring from backup.??? I would think the default ucle2 modem would have been restored (not complaining though). Sorry for being such a noob and look forward to responses such as..."Post in the right section noob" or "for cryin' out loud, do a search!!"
The radio is not backed up or restored in CWM.
Ril mismatch was your experience.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Ends said:
Ril mismatch was your experience.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. So in order to reconcile this for future reference, I would need to flash a radio with no ril, such as the ones posted in the Embryo rom thread?
pinoyscorpion951 said:
Thanks for the response. So in order to reconcile this for future reference, I would need to flash a radio with no ril, such as the ones posted in the Embryo rom thread?
Click to expand...
Click to collapse
If you're going to flash radios from different basebands. IIRC you just remove the system folder from the zip
I've looked at multiple forums, not just galaxy 3, and I can't find an answer to this problem. I keep getting the "symlinks: some symlinks fail - status 7" error when I try to flash certain roms. First of all, I'm rooted and unlocked. I have flashed CM10 and Synergy before (couple weeks ago,) but now I can't install any of the synergy nightlies or JB roms. I've tried to install from internal and external sd, and failed on both. I've flashed CWM touch and non touch 6.0.1.2 as well as twrp with the same error message. I've flashed the cwm recoveries through Rom Manager and Odin with no change. I loaded the latest Modem through Odin to see if that would fix the problem somehow, and that didn't work either. (Wasn't expecting it too.) Has anyone run into this issue and come out with a fix? I think I've done some pretty in depth research on this, but maybe I've missed something. I don't want to create a brick if someone has a fix. Thanks for the help.
I just bought a S3 last night. I immediately went through all of the steps for root,unlock,and tried to load a custom rom. After about 5 hours worth of research and trial and error I gave up and am probably going to return it for something different. No one has answers for this issue, but it seems a decent amount of people are getting this. I believe it has something to do with the phones memory / storage. Be sure to share anything that might fix this issue.
Hi, I am new to xda and i'm also quite new to the flashing process. I have a captivate i896 and successfully flashed a rom on to my phone. However after doing so the phone is unable to connect to my mobile carrier. I have also tried to install a modem from the stickied thread how ever it gives me an error::
cwm 3.0.zip error
i'm going to try to flash the helly bean rom in hopes of getting that fixed.
also in the about phone section it says baseband is unknown... ive googled that and it said my IMEI is corrupted or something or other.
So I'm looking to update my ROM. I was currently on Eaglesblood for about a year. Wanted to switch to Miui.
I downloaded the new ROM, put on my SD card and once I reboot in clockwork to flash the ROM it gives me this error.
States installing update...
assert failed: getprop("ro.product.device") ==......
E:error in /sdcard/miui_P990_3.5.24_......zip
Status 7
installation aborted.
Any help would be greatly appreciated.
Thanks
This phone is a P999 not a P990 and judging by the error you tried to install a P990 (O2X) ROM
Sent from my LG-P999
Lol i noticed that too. There are some good roms in the dev section. Take a look
http://forum.xda-developers.com/showthread.php?t=1696956
Here's a link for a Miui rom I myself have been thinking about flashing whenever it is i get tired of cm7 (although unlikely lol). Its even been integrated for 21y baseband in case you're one of the unlucky ones such as myself who use that baseband
-custom sig.
Very cool. Thanks for the help.
When I first flashed the phone I changed the ROMs quite often but after 6 months and a newborn a rarely touched it as the phone worked great.
Once again thanks for the quick help looking to get Miui back on it and see the if the bluetooth issue to a media device has been worked out.
Bluetooth on 21y baseband works with media. It does not work with call audio.
-custom sig.