Due to repeated radio connection freezes I tried using an old radio version from stock Froyo plus corresponding baseband files. So far so good, I do have call connection.
I used this guide: http://forum.xda-developers.com/showthread.php?t=1459470
I failed trying to create my first update.zip with the baseband files. I got some strange error 7 or so... used root explorer to copy/past files and changed permissions.
Question:
Permissions have to be 644 right?
How about the owner? Do I have to change it and to which owner?
/edit: I added the files I used, maybe someone else wants to try as well.
measel said:
Due to repeated radio connection freezes I tried using an old radio version from stock Froyo plus corresponding baseband files. So far so good, I do have call connection.
I used this guide: http://forum.xda-developers.com/showthread.php?t=1459470
I failed trying to create my first update.zip with the baseband files. I got some strange error 7 or so... used root explorer to copy/past files and changed permissions.
Question:
Permissions have to be 644 right?
How about the owner? Do I have to change it and to which owner?
Click to expand...
Click to collapse
What exactly does 'old radio version from stock Froyo plus corresponding baseband files' mean? What files did you replace?
The 'Central europe Hong Kong, Taiwan, ... 4.5.1-85' setting in baseband switcher should exactly match the stock German Froyo baseband files (I've compared MD5 sums).
I didn't know the baseband is the same.
Well I extracted CG45.smg from official DACH froyo: JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF.sbf
and flashed it.
And because I read I had to use suiting baseband files I got them from an old Nandroid backup and placed them on the bp_nvm_default folder.
Sorry if that is a bad idea but I really want to fix the connection bug and since switching basebands or builds didn't help at all I thought that might be a chance.
I confess: My knowledge is VERY limited.
/edit: Reason for this action was that my buddy has the same phone with stock eclair and his baseband is totally different from CM7. That's when I thought: Uhm maybe it helps to swap the radio drivers.
BTW: Log has got quite a view RIL warnings.
Questions go in the Q&A section
not only a question, info too! but well...
well, my test is over. yesterday I had the radio bug again. so that wasn't the solution.
Related
Hi all actually i'm running DFT NAND ROM and i'm just wondering how can i modify the system files as they are read only (for istance i'd like to edit build.prop or gps.conf).
Sorry for the noob question
Thanks all
NO GPS
I'm not able to get GPS to Work no matter what Nand Rom I Use, I edited my GPS.conf with the us.pool.ntp.org still not locking on SATs
thesniffer said:
Hi all actually i'm running DFT NAND ROM and i'm just wondering how can i modify the system files as they are read only (for istance i'd like to edit build.prop or gps.conf).
Sorry for the noob question
Thanks all
Click to expand...
Click to collapse
You need to get root explorer. Google it for the apk. Then set your permissions to read/write in the app. Then you can easily modify those files.
Ok - other question, is there a way to modify or replace the file
/proc/calibration
I can replace the same file in two other locations (/system/etc and /etc) but not the one mentioned above. I tried with root explorer and adb - no success.
If not, i'll live with the generic mac-address
EDIT: i also tried a modified batch from mdj (I updated my kernel today with this one).
I apologies in advance if this is not the correct place to post this.
I recently purchased a rooted and unlocked SGS2. Coming from a Jailbroken iPhone4, this is my first Android. For more than a month everything worked great with my Fido sim. However, all of a sudden I lost data connectivity. After reading forums and researching on Google I reinstalled/flashed the firmware, modem and so on. But the problem still persists. In fact now my sim is not even recognised.
Did a clean wipe and re-rooted using Odin3 v1.85
PDA: CF-Root-SGS2_XX_OXA_KG6-v4.1-CWM4
Phone: MODEM_I9100XXKG6_REV_02_CL1044543.tar
Then performed a sim unlock using an app from Market.
Under 'About phone' the 'Baseband version' still say 'Unknown'
I don't know what else to do. Please help... Thank you
Hi mate, would u tell me if u can c the imei no. of ur device!
dial *#06#
U should be able to read the proper number
Sent from my GT-I9100 using Tapatalk
drreality said:
Hi mate, would u tell me if u can c the imei no. of ur device!
dial *#06#
U should be able to read the proper number
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I don't. All it says is "IMEI" with an Okay button...
vish4488 said:
I don't. All it says is "IMEI" with an Okay button...
Click to expand...
Click to collapse
Sounds like your efs files got messed up, I don't think there is a way to fix it if you don't have a backup copy of your efs folder. Maybe Samsung can repair it for you.
jhernand1102 said:
Sounds like your efs files got messed up, I don't think there is a way to fix it if you don't have a backup copy of your efs folder. Maybe Samsung can repair it for you.
Click to expand...
Click to collapse
Oh man! I guess I will call them tomorrow and see what they recommend.
jhernand1102 said:
Sounds like your efs files got messed up, I don't think there is a way to fix it if you don't have a backup copy of your efs folder. Maybe Samsung can repair it for you.
Click to expand...
Click to collapse
how can we make a backup of the EFS files?
One the backup your EFS post in the dev section .
Two nitralitys app .
http://www.appbrain.com/app/nitralit...sanity.toolbox
Three other methods as posted .
jje
Samsung pretty much said that they cannot help
Then flash a stock rom see if that pulls it back .Do nothing else stock rom reboot and check IMEI .
That fails search exact same problem EFS i believe someone recently recovered one .
jje
JJEgan said:
Then flash a stock rom see if that pulls it back .Do nothing else stock rom reboot and check IMEI .
That fails search exact same problem EFS i believe someone recently recovered one .
jje
Click to expand...
Click to collapse
I flashed generic samsung rom from here.
However, the phone is now stuck in a boot loop
_____
Got it out of the loop by flashing these (below), but I am back to square one. I will try to find the EFS file from online...
PDA: CODE_I9100XXKG6_CL425236_REV02_user_low_ship.tar.md5
Phone: MODEM_I9100XXKG6_REV_02_CL1044543.tar.md5
CSC: GT-I9100-CSC-MULTI-OXAKG6.tar.md5
efs is unique for each phone, as it contain the imei in those files
Sent from my GT-I9100 using XDA App
DummyPLUG said:
efs is unique for each phone, as it contain the imei in those files
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Someone suggested "deleted the nv_data.bin and the nv_data.md5 in efs folder with Root Explorer, and renamed the .nv_data.bak into nv_data.bin, then restart."
Using Root Explorer I can access the efs folder. Where I can see all the files and my IMEI. But I cant make any changes as its read only. I have tried multiple code using terminal but I still can't access it.
vish4488 said:
Someone suggested "deleted the nv_data.bin and the nv_data.md5 in efs folder with Root Explorer, and renamed the .nv_data.bak into nv_data.bin, then restart."
Using Root Explorer I can access the efs folder. Where I can see all the files and my IMEI. But I cant make any changes as its read only. I have tried multiple code using terminal but I still can't access it.
Click to expand...
Click to collapse
Didn't work
I am in the same situation, is there any fix?
I fixed my problem by shutting down the phone, removing the sim card, booted, then the IMEI command returned a number.
I did a full backup of my efs folder. (nothing to do in solving the issue, but it was the time or never to do it).
Restarted, putting the sim back in, and voila.
iam in the same sitatuion .. :/
I've backuped my actual system /2.3.5 with CF Root Kernel 4.2 and restored the Original Firmware Backup i made at first day i've got the I9100
Then i try to copy out the /efs Folder, backup on my computer, restore the image from today and replace the /efs Folder from the stock rom... hope it works :/
// i think it works, but have to test - after restoring my backup i made 30 minutes before (with the baseband and imei problem (i backuped with this problem)) withhout chaning anything in the /efs folder it works, too.
I think some data after rebooting will be lost.. dont know.. have to wait and test :/
same problem here. tried to update to the new modem and this happened.
---------- Post added at 08:18 AM ---------- Previous post was at 08:14 AM ----------
I wish i had known i needed to backup something before updating to the EG31 modem for the epic 4g touch.
Is there a fix to this? Cant use my phone until this is fixed...
download KTool or HC-kTool from new Android market, make sure your phone has root permissions or super user, you know after you root you get it anyway, it has efs file that should have a backup for your imie, also get Root explrer and Rom Manaer they have access to efs file, you should watch Mobiletech reviews on YouTube, he also provides his own tool that he says will fix your imie.
Ten chars...
the1cyrus said:
same problem here. tried to update to the new modem and this happened.
---------- Post added at 08:18 AM ---------- Previous post was at 08:14 AM ----------
I wish i had known i needed to backup something before updating to the EG31 modem for the epic 4g touch.
Is there a fix to this? Cant use my phone until this is fixed...
Click to expand...
Click to collapse
E4GT is in a different forum, try there - it has a completely different method of managing modem firmware since it's a CDMA phone.
Carrier is just showing numbers on a AOSP rom I installed. I understand this is completely stripped but I was wondering how to setup the carrier name properly instead. I read that spn-conf.xml in /system/etc/ is what I should edit but there was no file so I created one and pushed it to the device with adb rebooted the device but no luck. Anyone know how to set this up? Thanks
maybe you lost the imei?
No phone works fine.. I know there is suppose to be a file that will read the numbers then display the carrier name. Before it use to be spn-conf.xml and you would setup the file as follows;
<spnOverride
numeric="302320" spn="Mobilicity"/>
</spnOverrides>
then push it to /system/etc and it would overwrite the file however in the new 2.3.5 this file is not present and was wondering if anyone with knowledge knows this. I would post in development but that is for projects and not for troubleshooting or chatting.
Thanks
Did you find a fix for this? I just installed CyanogenMOD 7.1 and am seeing these numbers as well (using Mobilicity on my Vibrant).
Ok.... I've seen a lot of users in many forums that want change the radio...
See HERE!!!! For european with Argentinian radio!!!
http://forum.xda-developers.com/showpost.php?p=27649093&postcount=25
I've changed the radio on droid pro... (american)
But I didn't remember how!!
Edit...
Yes I know....! With rsdlite... Ok rsdlite can rewrite the radio. Sbf_flash no...
The American users know this thing, but for European it is a good news, because they can flash an american/argentinian sbf without changing radio.... Naturally with sbf_flash...
Flashing american on european with rsdlite will brick your phone, without changing the radio...
European on American with rsdlite will brick your phone, without changing your radio...
But if you'll use sbf flash, your phone will be glad!
You must see only if you have a locked kernel... (argentinian 2.3.6 I'm sure... for american 2.3.4, I don't know...)
Attention!!!
Argentinian gsm is 800/2100
European gsm is 900/1200
So we can understand the european's issues with argentinian rom....
I'm always sure that we must search the radio in the sbf! Not files...
I've done some steps here, only for trying...
1) Put your phone in bootloader mode
2) Start with Linux Knoppix live cd
3) Open terminal emulator from your folder where you have your sbf (i've used 2.26.20 verizon SBF..))
4) put also sbf_flash in the same folder ( you can find here:http://blog.opticaldelusion.org/search/label/sbf_flash )
chmod +x sbf_flash
then
sudo ./sbf_flash -r --bpsw 2260.sbf
Connect your phone...
Reboot and now you'll have a new radio!
See HERE!!!! For european with Argentinian radio!!!
http://forum.xda-developers.com/showpost.php?p=27649093&postcount=25
Sent from My Motosola....
Ok... Only for testing... I've saved on my dropbox folder a euril.zip, extract lib_moto.ril and replace with yours in system/lib (rename before yours)... Before set your pin sim card... with a new one!
Set permission to rw-r-r... Reboot...
Try...
If you have any issue set airplane mode on, reboot and replace it with yours renamed, reboot again...
Sent from My Motosola....
dettofatto,
Replacing the files did not help.
USSD does not work.
It may have something else to fix?
motostigr said:
dettofatto,
Replacing the files did not help.
USSD does not work.
It may have something else to fix?
Click to expand...
Click to collapse
No.. I'm thinking...
For Your issue on gsm, try to install this file with clockwordmod, make backup before...
http://www.grupoandroid.com/topic/45732-3g-hack-para-xt610/page__pid__667515#entry667515
All Credits to: http://www.grupoandroid.com/topic/45732-3g-hack-para-xt610/page__pid__667515#entry667515
Just tried the hack. Unfortunately I don't notice any progress.
In fact the extracted files are missing after reboot (no bp_nvm_default folder). I searched for them earlier in order to use basebandswitcher but never found them.
Maybe the whole telephony module really is emulated in java (see /system/etc/init.goldfish.sh)? But what would it mean for us?
I also tried 3 other ways yesterday without success:
- tried to flash bp.img from Blur_Version.4.7.3XT610.Verizon.en.US.zip --> status 7 error in CWM
- flash a zip containing radio.img of a european Pro+ update --> installs too fast without any noticable difference. Looks like he is ignoring the radio
- flashed JackpotCalvin's ICS rom which also includes bootmenu with a 2nd boot config only containing init.mapphone_umts.rc --> I may have done something wrong during the process but coulnd't see any difference
@any user of the US-verizon model: can you choose between more than "USA Band" when you do the following?
- dial *#*#4636#*#*
- go to "Phone Information"
- press menu softkey
- select radio band
@anyone with original european froyo: what choices do you have?
Ive seen different models (including Pro+) which always let me choose between 5-6 different basebands.
hlat said:
Just tried the hack. Unfortunately I don't notice any progress.
In fact the extracted files are missing after reboot (no bp_nvm_default folder). I searched for them earlier in order to use basebandswitcher but never found them.
Maybe the whole telephony module really is emulated in java (see /system/etc/init.goldfish.sh)? But what would it mean for us?
I also tried 3 other ways yesterday without success:
- tried to flash bp.img from Blur_Version.4.7.3XT610.Verizon.en.US.zip --> status 7 error in CWM
- flash a zip containing radio.img of a european Pro+ update --> installs too fast without any noticable difference. Looks like he is ignoring the radio
- flashed JackpotCalvin's ICS rom which also includes bootmenu with a 2nd boot config only containing init.mapphone_umts.rc --> I may have done something wrong during the process but coulnd't see any difference
@any user of the US-verizon model: can you choose between more than "USA Band" when you do the following?
- dial *#*#4636#*#*
- go to "Phone Information"
- press menu softkey
- select radio band
Ive seen different models (including Pro+) which always let me choose between 5-6 different basebands.
Click to expand...
Click to collapse
In all pro we can choose only usa band (also in european froyo...)
Try to move manually the folder bp_nvm
Or Try this...
Install a nandroid backup of original american 2.3.3 (very original!!)
then try to recive the update from verizon and install it
Will I need to pull battery for 3 hours if I do the verizon update?
Boh....!!!! But I've seen your pm! Did you phone restart?
In my experience my phone restart in about 3 ours... coming from froyo...
But coming from 2.3.6?
Sent from My Motosola....
I don't know if this will help you or not, but I have the VZW 4.7.3 SBF file now. I just got it from a friend who pulled it from Motorola's server.
I have not tested it yet and have no need to as my Pro is already on 4.7.3 and rooted and is an engineering model anyway.
I will upload it somewhere to post publicly tonight or tomorrow when I get the chance.
cellzealot said:
I don't know if this will help you or not, but I have the VZW 4.7.3 SBF file now. I just got it from a friend who pulled it from Motorola's server.
I have not tested it yet and have no need to as my Pro is already on 4.7.3 and rooted and is an engineering model anyway.
I will upload it somewhere to post publicly tonight or tomorrow when I get the chance.
Click to expand...
Click to collapse
do you have any files bp-nvm or similar?
we are searching the radio file...
Thank you!
dettofatto said:
For Your issue on gsm, try to install this file with clockwordmod, make backup before...
http://www.grupoandroid.com/topic/45732-3g-hack-para-xt610/page__pid__667515#entry667515
All Credits to: http://www.grupoandroid.com/topic/45732-3g-hack-para-xt610/page__pid__667515#entry667515
Click to expand...
Click to collapse
I may have good news everyone!
After I have some issues with the 3g hack (files not showing up after reboot), I unzipped them manually. Then I changed permissions to rw-r--r-- and installed Defy+ baseband switcher to changed baseband to European (900/2100).
Since I've been mainly in areas with good signal quality the last week, I'm not a 100% sure if it really improved anything. But it feels like it!
Can someone please try this workaround for verification? The needed files are attached.
Thanks!
the right steps are?
1) Extract your I and II zips file in our pc
2) copy folder bp_nvm_default (II zip) from our pc to our phone under system/etc/motorola
3) set permissions
4) copy basebandswitcher (I Zip) from your II zip to /system/app, set permission to rw-r-r
5) Reboot
6) Open the new app
7) Or use my rom....! ;-)
it is right?
Thats right! Thank you for completing
Sent from my XT610 using XDA
dettofatto said:
the right steps are?
copy folder bp_nvm_default under system/etc/motorola
set permissions
install apk
it is right?
Click to expand...
Click to collapse
Hi
where can I find folder bp_nvm_default so that I can try..?
Thanks
sorry found. a question: are the files installed by CWN ..?
In the hlat's files...
you must open these zips files and add manually in your phone...
with root explorer..
dettofatto said:
In the hlat's files...
you must open these zips files and add manually in your phone...
with root explorer..
Click to expand...
Click to collapse
ok
then:
unzip 3ghack and copy the folder bp_nvm_default under system / etc / motorola.
After I install the file basebandswitcherV4.0.apk.
files that are present in the meta-inf folder what do I do..?
billamele said:
ok
then:
unzip 3ghack and copy the folder bp_nvm_default under system / etc / motorola.
After I install the file basebandswitcherV4.0.apk.
files that are present in the meta-inf folder what do I do..?
Click to expand...
Click to collapse
Nothing.....
Try also this zip file: http://dl.dropbox.com/u/33827639/Droid Pro/Ril & Init/noncancellatmp.zip
install this file 2 times in the same session with clockwordmod....
i think that your radio will change...
Make your backup first!! And use new bootmenu!!
New steps for extracting radio....
See the first post...
Hi,
Would someone be kind enough to send me his stock 4.3 build.prop for Nexus4 because I have modified it without backup (hey I know that's not smart... ) and I cannot use the OTA for JWR66Y because build.prop file does not pass the binary verification.
Thanks !
Flav106 said:
Hi,
Would someone be kind enough to send me his stock 4.3 build.prop for Nexus4 because I have modified it without backup (hey I know that's not smart... ) and I cannot use the OTA for JWR66Y because build.prop file does not pass the binary verification.
Thanks !
Click to expand...
Click to collapse
Just to remind, remember to delete the TXT extension when you put it back in because if i dont add an extention I cant upload it. I extracted it from Cataclysm, don't worry, it doesnt matter. Its still a JWR based build.prop.
KiD3991 said:
Just to remind, remember to delete the TXT extension when you put it back in because if i dont add an extention I cant upload it. I extracted it from Cataclysm, don't worry, it doesnt matter. Its still a JWR based build.prop.
Click to expand...
Click to collapse
Make sure it doesn't have any names of custom roms or anything like that.
Sent from my Nexus 4 using Tapatalk 4
Thanks a lot !
But I can see your are already in JWR66Y. I am not sure this will work for the OTA...
I think it would be better to have a JWR66V version don't you think ?
AFAIK, it doesnt have and even if it does it doesnt affect the ROM.
Because any names in the build.prop is just stated in the About in the phone. I trolled my classmates for having Beta android 4.4
Well, it worked for the build.prop verification, but i have some errors ...
It passed the patching of system files but I have an error set_perm : some changes failed.Installation aborted.
The phone rebooted properly.
So now I don't know what version i'm in with the modified build.prop !
Do you know how to check my version other than checking the build.prop file ?
Finally I'v been able to update with this fix :
http://forum.xda-developers.com/showpost.php?p=44940220&postcount=556
Status 7 error was due to my root.
Thanks.
KiD3991 said:
Just to remind, remember to delete the TXT extension when you put it back in because if i dont add an extention I cant upload it. I extracted it from Cataclysm, don't worry, it doesnt matter. Its still a JWR based build.prop.
Click to expand...
Click to collapse
Yeah this didn't work for me. I verified that the build.prop matches what you linked, but I'm still getting the build.prop error. So had any of you also flashed different radios or the LTE enabler zip that floats around the All LTE Discussion board? I just don't understand why I'm still getting that error if it worked for you.
Pokley said:
Yeah this didn't work for me. I verified that the build.prop matches what you linked, but I'm still getting the build.prop error. So had any of you also flashed different radios or the LTE enabler zip that floats around the All LTE Discussion board? I just don't understand why I'm still getting that error if it worked for you.
Click to expand...
Click to collapse
I'm not using any LTE. My radio is the pure 4.3 radio.
It could be that the build.prop you used is edited by computer. (one that might effect)