Does anyone know what the latest ril matcher is for the new G2 radio .03? I saw one by rmk and one by blah, but everything I saw they were for the .30 radio.
Any help would greatly appreciated!
Thanks
Right here, flash it in recovery. Enjoy!
http://www.multiupload.com/4VGRZ3A3AO
Sent from my HTC Vision using XDA App
But you don't need to match your RIL, if you are using the radio that came with the ROM, right?
For example if you are running Virtuous Sense 2.0.0 which is based on the latest Stock ROM 2.42.405.2 and flashed the Radio 26.10.04.03_M, which came with that Stock ROM, the RIL should already be the right one and any RIL-matching would probably just do more potential damage than any good, correct?
Tronar
PaganAng3l said:
Right here, flash it in recovery. Enjoy!
http://www.multiupload.com/4VGRZ3A3AO
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Awesome! Thank you so much...........I appreciate it
Tronar said:
But you don't need to match your RIL, if you are using the radio that came with the ROM, right?
For example if you are running Virtuous Sense 2.0.0 which is based on the latest Stock ROM 2.42.405.2 and flashed the Radio 26.10.04.03_M, which came with that Stock ROM, the RIL should already be the right one and any RIL-matching would probably just do more potential damage than any good, correct?
Tronar
Click to expand...
Click to collapse
Yes, I would imagine you're already using the 0098 ril that is for the 04.03 radio, but attempting to match again shouldn't hurt anything. But if you're happy with your performance and battery life I wouldn't mess with it, honestly the only reason I flashed the newest radio/ril was because I was at a club and had no service on my old radio. Hard to chat up this girl I was meeting with no service
Sent from my HTC Vision using XDA App
PaganAng3l said:
Yes, I would imagine you're already using the 0098 ril that is for the 04.03 radio, but attempting to match again shouldn't hurt anything. But if you're happy with your performance and battery life I wouldn't mess with it, honestly the only reason I flashed the newest radio/ril was because I was at a club and had no service on my old radio. Hard to chat up this girl I was meeting with no service
Click to expand...
Click to collapse
Do you know a quick and easy way to check, which RIL my phone is currently using? I can access my phone through ADB, Android Terminal or a tool like Root-Explorer or Astro. So anything fast and simple like displaying the properties of a specific file would be great.
Thanks in advance,
Tronar
Tronar said:
Do you know a quick and easy way to check, which RIL my phone is currently using? I can access my phone through ADB, Android Terminal or a tool like Root-Explorer or Astro. So anything fast and simple like displaying the properties of a specific file would be great.
Thanks in advance,
Tronar
Click to expand...
Click to collapse
I know it's stored in your /system/lib directory (might be wrong there, someone correct me if I am) but I'm not quite sure what they're called... ro.ril is ringing a bell. Honestly since rmk and pfak made these automatchers I haven't pushed a ril file since my og G1. The easiest way is to flash the automatcher, the worst that would happen is it inserts the data that was there to begin with making no changes, but conversely it could correct rils you thought were matched but weren't actually
Sent from my HTC Vision using XDA App
Well, I am still a fan of the idea "if it ain't broke, don't try to fix it". So I would prefer to not flash anything, if everything is already matched.
So I want to find out first, which version of the RIL I am running, before I am taking any actions. Anybody else any idea how to check the current RIL version?
Tronar
Tronar said:
Do you know a quick and easy way to check, which RIL my phone is currently using? I can access my phone through ADB, Android Terminal or a tool like Root-Explorer or Astro. So anything fast and simple like displaying the properties of a specific file would be great.
Thanks in advance,
Tronar
Click to expand...
Click to collapse
Code:
su
getprop "gsm.version.ril-impl"
Maybe this could help you.
Tronar said:
Well, I am still a fan of the idea "if it ain't broke, don't try to fix it". So I would prefer to not flash anything, if everything is already matched.
So I want to find out first, which version of the RIL I am running, before I am taking any actions. Anybody else any idea how to check the current RIL version?
Tronar
Click to expand...
Click to collapse
farsanx said:
Code:
su
getprop "gsm.version.ril-impl"
Maybe this could help you.
Click to expand...
Click to collapse
Or from terminal type ls -l /system/lib/*ril.so and check the date of the files
hey were can i get an ril patcher for the 4.19 that do not blow up my apns when it flashes on unity 2.39
Dont match the rils,its fine without them,dont think there is one that will not break your apns
Related
my data just turns off randomly and it never seems that a rom has fixed it. thank you in advance.
You would probably get better response and feedback by posting your question in the Q and A section of this forum...sorry I don't have or have seen a data loss issue. Perhaps coverage is poor.
Sent from my ADR6300 using XDA App
Awesome post, no info on what you are running.
shoman24v said:
Awesome post, no info on what you are running.
Click to expand...
Click to collapse
it does it on every ROM. its the same issue that you have to turn the airlplane mode off and on to get it to work again but i can't find another thread with that info. i have incdoes desire .5, 2.15.00.07.28 radio, s-off
blaine91787 said:
it does it on every ROM. its the same issue that you have to turn the airlplane mode off and on to get it to work again but i can't find another thread with that info. i have incdoes desire .5, 2.15.00.07.28 radio, s-off
Click to expand...
Click to collapse
ok, then i'd say it's the rom. Leaked sense did it for me, official was fine.
Thread moved to Q&A.
blaine91787 said:
it does it on every ROM. its the same issue that you have to turn the airlplane mode off and on to get it to work again but i can't find another thread with that info. i have incdoes desire .5, 2.15.00.07.28 radio, s-off
Click to expand...
Click to collapse
This happened to me when flashing the leak on a buddy's device. I had to reinsert the pst settings because they were all wiped to crazy ****. Enter your EPST by going to the keypad and dialing ##pst ->send. The NAM settings should be as follows:
MDN - you phone#
MIN1 - your phone # without area code
Min2 - area code
MSID - your phone number
Hope this helps.
I have this problem too but the thing I cannot find is a working froyo EPST on CM.
staticx57 said:
I have this problem too but the thing I cannot find is a working froyo EPST on CM.
Click to expand...
Click to collapse
You know I don't speak spanish, in english please....
You're saying you can't access your epst settings, or you can't change them?
Had this problem once using skyraider, I blamed it on a bad download/ flashing. Once I downloaded again and flashed it.again never experienced it since..this was over a month ago I experienced it.
Sent from my ADR6300 using XDA App
Sweeny Russ said:
You know I don't speak spanish, in english please....
You're saying you can't access your epst settings, or you can't change them?
Click to expand...
Click to collapse
I am saying I cannot access my EPST settings. And I am also saying I am using CyanogenMod.
Beautifully working VU2.39. Then decided to add new lock ring. Totally messed up phone.
Restored with ROM Manager to prior situation, but have totally lost phone radio (and therefore phone, 3g etc.) Have tried restoring many times, tried airplane mode, wiped cache...all with no solution.
Shows no service, no CDMA or other option exists in settings, phone info shows:
Signal Strength =0
Mobile Network Type unknown
Service state= out of service
What did I do here??? How to fix???
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
lair12 said:
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
Click to expand...
Click to collapse
2.3.4 is definitely rootable. And I don't think a ring would change that much. Have you tried flashing a New radio?
Sent from my Incredible 2 HD using XDA App
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
lair12 said:
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
Click to expand...
Click to collapse
Try flashing this Radio. It's the last one on the list.
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
lair12 said:
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
Click to expand...
Click to collapse
Well...... Was the lockring made for your specific ROM and phone? If not, that may be why.
Have you tried any other ROMs to make sure it's not just something interfering in the ROM itself?
To root 2.3.4, you have to downgrade the hboot v.98 to v.97 following these steps found here.
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
lair12 said:
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
Click to expand...
Click to collapse
Post edited so the link for 2.3.4 root should work. But, yeah, that's for Thunderbolt, not the DINC2. Try flashing another ROM or full wipe/reflash of VU 2.39. Don't apply any mods until you find out if it works, and see if someone can port the lockring to the DINC2.
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
lair12 said:
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
Click to expand...
Click to collapse
What about the .722 radio?? Earlier you said you had the .622 radio which is an older one. If that doesn't work, boot into hboot and factory reset (I think this works). Then you'll probably have to re-root. Otherwise, you can get a new phone, and root via the downgrade.
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
lair12 said:
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
Click to expand...
Click to collapse
Sorry to hear that.... Let us know how the rooting goes.
Sent from my Incredible 2 HD using XDA App
Sir, i flashed my nexus with AOSP rom(4.0.3),everything works well for several hours.but yesterday my phone shows error no service,i tries several sim card but facing same issue.so i tried imei no and guess what it shows nothing.... i checked baseband shows unknown. so i flashed stock rom via cwm (restore),but unfortunately facing same problem. so i flashed few baseband images also but not workrd either. plz help me how should i get my imei number back..... i have no backup file of my EFS folder.
First off, don't call me sir
I've been seeing alot of the same issue and no one seems to have a solid lead on the real problem.
And yes, it has happened to me.
My opinion is that flashing *some* roms is causing the bootloader to become corrupted...as this is exactly the issue I had experienced.
A fubar'd bootloader will screw everything up.
The solution for me was to odin back to stock.
Since you did not state if your gnex is gsm or cdma I am not going to attempt to post directions or even file names for you (you can easily search for odin and get them here in this forum). The directions are completely different depending on the gsm/cdma thing.
Be careful and make sure you have the right version of odin and the correct files to flash. It's actually pretty simple, but it's always the simple things that are easiest to get wrong.
g'luck
mangesh hotkar said:
Sir, i flashed my nexus with AOSP rom(4.0.3),everything works well for several hours.but yesterday my phone shows error no service,i tries several sim card but facing same issue.so i tried imei no and guess what it shows nothing.... i checked baseband shows unknown. so i flashed stock rom via cwm (restore),but unfortunately facing same problem. so i flashed few baseband images also but not workrd either. plz help me how should i get my imei number back..... i have no backup file of my EFS folder.
Click to expand...
Click to collapse
For me the solution was to just flash a suitable radio
Sent from my Galaxy Nexus using Tapatalk 2
There is no 4.0.3 for the nexus the last time i remember..
Mach3.2 said:
There is no 4.0.3 for the nexus the last time i remember..
Click to expand...
Click to collapse
? ... 4.0.3 has been out for GN.
zephiK said:
? ... 4.0.3 has been out for GN.
Click to expand...
Click to collapse
There's no 4.0.3 images for the gnex, at least official ones.
http://www.randomphantasmagoria.com/firmware/galaxy-nexus/i9250/
I had this issue as well. I couldn't get the gnex (GSM) to show up in Odin to even start flashing anything so the only thing I could do was send it in to Samsung.
Sent from my Sensation using Tapatalk 2
sorry my mistake its 4.0.4, i have GSM phone.is ODIN solve my problem to get back my baseband.....
buenso80 said:
For me the solution was to just flash a suitable radio
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i tried ur way but its not working and i have the same problem
haziqshaikh97 said:
i tried ur way but its not working and i have the same problem
Click to expand...
Click to collapse
Any update? have anyone make a warranty reclamation? my phone with cyanogen 9 have the same problem, factory image restoration and radio install don´t work for me.
radiazo said:
Any update? have anyone make a warranty reclamation? my phone with cyanogen 9 have the same problem, factory image restoration and radio install don´t work for me.
Click to expand...
Click to collapse
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
PaullieVicious said:
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
Click to expand...
Click to collapse
Hi, I went back to stock by odin but had no success! no gsm signal... baseband unknown :crying::crying::crying:
[email protected]:/data/radio/log # cat nv.log
cat nv.log
Sat Jul 28 12:29:43 2012: /data/radio/nv_data.bin does not exist.
Sat Jul 28 12:29:43 2012: /data/radio/nv_data.bin does not exist.
[email protected]:/data/radio/log # cd /data/radio
cd /data/radio
[email protected]:/data/radio # ls
ls
log
nv_data.bin
nv_data.bin.md5
[email protected]:/data/radio #
is problem hardware pba (modem)
http://forum.xda-developers.com/showthread.php?t=1626593&page=5
any updates? I'm having the same problem, only had my GNEX for a week.
Try copying these files from /factory to /data/radio:
nv_data.bin
nv_data.bin.md5
And set the permissions to 700.
efrant said:
Try copying these files from /factory to /data/radio:
nv_data.bin
nv_data.bin.md5
And set the permissions to 700.
Click to expand...
Click to collapse
Then reboot of course.
Sent from my Galaxy Nexus using Tapatalk 2
PaullieVicious said:
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
Click to expand...
Click to collapse
I use fastboot, and don´t have luck. EFS partition contents exist, but i don´t have imei or baseband detected. I install google jellybean
Same happened to my GNex after flashing miui 2.11.16.
Common sense suggests that the rom, which doesn't include a radio, shouldn't be the reason for the unknown imei and unknown baseband fault.
This has also happened to others of whom most, including me, indicated flashing the updated recovery either twrp 2.3.2.1 or cwm 6.0.1.5/6 which were rolled out for android 4.2 compatibility.
I went back to stock 4.1.2 everything... GNex Tool and ODIN methods, but the problem remained: still UNKNOWN IMEI and UNKNOWN Baseband.
Common symptom to this fault is the phone/os thinks that Flight Mode is ON. Closer inspection in hidden menu phone information (*#*#4636#*#*) clearly shows the radio alternating On/Off continuously... all suggested tricks to set band to gsm manual or auto failed.
I have also tried the OMAP_Flash tool recently leaked from smsng team... it works as described (fix boot partition) but it wouldn't fix this problem.
Those suggesting it's a hardware fault are simply "just saying" but there's no actual prove or method to such a conclusion.
I'm leaning more to believe the cause to be a bug in the updated custom recoveries for android 4.2.
Hope this helps anyone trying to find a fix.... if you find a fix, please PM me
... and for now, i'm using my good old galaxy s i9000 <= will give it to anyone successfully helps us to fix the GNex
Do you have signal? are you in the same rituation described in this post? http://forum.xda-developers.com/showthread.php?t=1797931
I'm in the same situation, only flashing 4.0.4 firmware Imei and baseband are shown, but no signal...
I really don't know if it's just a solvable software problem or it's an hardware one!
Thanks for any news!!!!
xanadux said:
Do you have signal? are you in the same rituation described in this post? http://forum.xda-developers.com/showthread.php?t=1797931
I'm in the same situation, only flashing 4.0.4 firmware Imei and baseband are shown, but no signal...
I really don't know if it's just a solvable software problem or it's an hardware one!
Thanks for any news!!!!
Click to expand...
Click to collapse
similar problem, but unlike dhuberto, not able to get imei back with any version of a stock image using any method.
My radio keeps going FLIGHT MODE on then off then on continuously... I have tried several apps to force gsm off (turn off radio) to no avail.
I personally still think it is not a hardware issue. Maybe it's me just hoping!
I have reasons to slightly believe that it was caused by a bad custom recovery code while doing fix permissions.
I am still researching and I will update once there's some news, good or bad.
A couple of days back I rooted my wildfire and installed CM7. Everything worked like a charm except for a GPS.
I managed to find the Radio.img version ending in 19.25 which is needed to make GPS work and flashed it over fastboot after installing the Android SDK on my linux machine.
It works and locks to the gps. I'm now going to test it out extensively in the wild and go on a hike. (I'll come back later with the results).
Now my question is: Why would I want to update it to 20.10? Any benefits?
(By the way, bluetooth works as well).
In case it is suggested to upgrade my radio... how would I have to do it?
Would I have to reflash with fastboot or should I first download "Test GPS", clear and upgrade the AGPS data and then reflash radio 20.10?
Thank you!
some radios have network advantages over others IE a radio that gives me great network connection may not give you the same result
heavy_metal_man said:
some radios have network advantages over others IE a radio that gives me great network connection may not give you the same result
Click to expand...
Click to collapse
Thank you. It seems that everything works perfectly with the current radio. I see thus no reason to change it and won't change it unless otherwise advised.
RonaldSmith said:
Thank you. It seems that everything works perfectly with the current radio. I see thus no reason to change it and won't change it unless otherwise advised.
Click to expand...
Click to collapse
Just stick with what works for you pal besides, you can always just go back again
Sent from my HTC Sensation using xda premium
Since it appears the One also can potentially lose its IMEI upon flashing an AOSP rom like a few other devices, I have a couple of questions...
#1 - will "adb reboot nvbackup" and nvrestore work on the One, or was that a Samsung only thing for the S3?
#2 - I was about to ask about backing up EFS via recovery, but it appears, at least with TWRP, that's not an option yet
#3 - is there any other way to backup the IMEI before flashing an AOSP rom? I've had no issues with CM, but after NOT backing up my IMEI when I had a GS3 and going through the massive headache to get that working again, I'd prefer to have a backup before trying any others
TIA!
jntdroid said:
Since it appears the One also can potentially lose its IMEI upon flashing an AOSP rom like a few other devices, I have a couple of questions...
#1 - will "adb reboot nvbackup" and nvrestore work on the One, or was that a Samsung only thing for the S3?
#2 - I was about to ask about backing up EFS via recovery, but it appears, at least with TWRP, that's not an option yet
#3 - is there any other way to backup the IMEI before flashing an AOSP rom? I've had no issues with CM, but after NOT backing up my IMEI when I had a GS3 and going through the massive headache to get that working again, I'd prefer to have a backup before trying any others
TIA!
Click to expand...
Click to collapse
yuuup.... I jumped the gun and installed GPE without even considering this... now no VZ signal even after the restore. am I totally screwed without a backup?
Wait what's going on? I've flashed a few aosp ROMs already and back to sense and haven't lost anything g yet as far as I can see
Sent from my One using Tapatalk now Free
crazyg0od33 said:
Wait what's going on? I've flashed a few aosp ROMs already and back to sense and haven't lost anything g yet as far as I can see
Sent from my One using Tapatalk now Free
Click to expand...
Click to collapse
Same here - well only CM so far. But others are reporting what sounds like IMEI loss after flashing AOSP. Doesn't sound as widespread as it was with the S3 - but if there's even a remote chance, I don't want to mess with it! Just hoping to get more info... hopefully it's not as big of a concern.
jntdroid said:
Same here - well only CM so far. But others are reporting what sounds like IMEI loss after flashing AOSP. Doesn't sound as widespread as it was with the S3 - but if there's even a remote chance, I don't want to mess with it! Just hoping to get more info... hopefully it's not as big of a concern.
Click to expand...
Click to collapse
what happens with an IMEI loss? we lose cell service?
BaBnkr said:
yuuup.... I jumped the gun and installed GPE without even considering this... now no VZ signal even after the restore. am I totally screwed without a backup?
Click to expand...
Click to collapse
If you are S-OFF, flash the RUU posted, and that will fix you up.
Yikes. I've flashed GPE (didn't enjoy so much), bonestock (LOVE) and am now on CM (like so far) and haven't had any issue. Hopefully I don't!
Sent from my HTC One.
Has anybody figured this out yet and is it still an issue??
Sent from my HTC6500LVW using xda app-developers app
andybones said:
If you are S-OFF, flash the RUU posted, and that will fix you up.
Click to expand...
Click to collapse
Yuup. That worked .
Sent from my stock (but rooted) VZW HTC One now Free
andybones said:
If you are S-OFF, flash the RUU posted, and that will fix you up.
Click to expand...
Click to collapse
Where is the RUU posted at?