Related
I downloaded stock XXJVT yesterday.There are 2 different csc files.Which one should i use to flash?Help.
The bigger multi csc one, you can then change your csc to your country after the flash
Sent using TCP/IP
Thanks mate.I just want to know whats the use of the smaller csc file?
Not sure, might have a single csc only, changing the csc will perform a reset so make sure you backup apn's, sms etc before
Sent using TCP/IP
Well I think its the small one we have to use not the big one, I know this from the person who first posted jvt here at xda. Can anyone else confirm it as I have flashed jvt 7 times now with the small file and its always fine.
Sent from my GT-I9000 using xda premium
After many months of discussions, I was wondering if anybody had ever flashed an XT860 radio on an XT862. I know people were using the XT883 to get Tmo/ATT access on their XT862, but has anybody ever tried using the XT860 radio? Some have said it's different radio hardware. I'm not 100% sure, and would like to hear from experience.
Also, if anybody needs it, the SBF for the Bell XT860 has been released so you can easily pull the radio file from there.
Please let mek now!
Bump, Anyone?
Sent from my XT894 running ICS
Curious about this myself. I've heard the same question asked in a couple other Droid 3 threads but it doesn't look like anyone's tried it yet.
--posted from my phone
Dunno, but with ATT having the Note (one sexy beast) why would you want a D3 on ATT?
cappysw10 said:
Dunno, but with ATT having the Note (one sexy beast) why would you want a D3 on ATT?
Click to expand...
Click to collapse
I'm interested more for the overall engineering process for motorola. Do the different model numbers actually have different hardware on the inside? Or is it all software based?
Also, the note doesn't have a physical keyboard
danifunker said:
After many months of discussions, I was wondering if anybody had ever flashed an XT860 radio on an XT862. I know people were using the XT883 to get Tmo/ATT access on their XT862, but has anybody ever tried using the XT860 radio? Some have said it's different radio hardware. I'm not 100% sure, and would like to hear from experience.
Also, if anybody needs it, the SBF for the Bell XT860 has been released so you can easily pull the radio file from there.
Please let mek now!
Click to expand...
Click to collapse
I know this is an old thread but since some time has passed and more people have had time to play with using the xt883 radio on the xt862 I'm wondering if anyone has gotten around to trying the xt860 radio? I have an xt861 I'd like to put the xt883 radio on and don't really have the experience needed to try out the xt860 radio without some idea it would work but it seems to me that if this worked it would be a better solution than using the xt883 radio and having to deal with the few bugs that has then just using the xt860 radio which to my understanding is a straight gsm radio to start with. If there were a way to use the xt883 radio and maintain cdma and gsm then I could see the point but since we lose cdma anyways why not just go with the xt860 anyways? If someone wanted to provide the files and walk me through it I'd be willing to try it either on the xt861 I have or on an old xt862 if you'd rather after I get the 861 up and running on the 883 radio. Maybe I'm barking up the wrong tree and this has already been tried and didn't work but I haven't seen anyone state that to be the case when I went searching. Anyone have anythoughts on this?
Sent from my XT862 using xda app-developers app
You can always go back to original radio so there is no risk for you, maybe the latest baseband (newer than Verizon's one) from sbf.droi-developers.org the ACG OR ACG-nTelos will work fine, who knows maybe is US gsm-unlocked, just extract and flash the radio.img, no modified build.prop is neccesary
For the moment I don't have a D3 at my disposal to try the 860 radio but you can try to mount the system.img from the xt860 sbf zip file(mount -o loop) and copy the build.prop if after flashing you have unknown baseband version.
Regards
Sent from my XT894 using xda app-developers app
Don't flash the 860 radio on an 861/862/883 or vice versa. If you want GSM use the 883 radio, if it will let you.
lucize said:
You can always go back to original radio so there is no risk for you, maybe the latest baseband (newer than Verizon's one) from sbf.droi-developers.org the ACG OR ACG-nTelos will work fine, who knows maybe is US gsm-unlocked, just extract and flash the radio.img, no modified build.prop is neccesary
For the moment I don't have a D3 at my disposal to try the 860 radio but you can try to mount the system.img from the xt860 sbf zip file(mount -o loop) and copy the build.prop if after flashing you have unknown baseband version.
Regards
Sent from my XT894 using xda app-developers app
Click to expand...
Click to collapse
The baseband on the xt861 I have is n_03.18.37P . This is different than the xt862 I'm using now and appears to be newer would this cause a problem with using the xt883 radio? If so is there a way to change the baseband on the xt861 to the same as the one on my xt862? Would using the one click unbrick found on this forum change the baseband?
Sent from my XT862 using xda app-developers app
every1nosme said:
The baseband on the xt861 I have is n_03.18.37P . This is different than the xt862 I'm using now and appears to be newer would this cause a problem with using the xt883 radio? If so is there a way to change the baseband on the xt861 to the same as the one on my xt862? Would using the one click unbrick found on this forum change the baseband?
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
It's easy to change it, you only have to write de radio partition with the radio.img file, the user data can remain intact. the ACG version number I remember that it's ending with 37 and the verizon's one is ending with 32
you have to put the phone in fastboot mode and use the moto-fastboot.exe /flash radio radio.img
all the radio.img versions can be found in the zip files from the http://sbf.droid-developers.org/ site, it takes around 5 minutes to do it, but as I said maybe you need a modified buid.prop from xt860, because for xt863 if is not modded you will have unknown version number for the baseband and no radio signal.
When I did this I didn't need to change the build prop. It work just fine for me. It worked while I was in Afghanistan and works on ATT and T-Mobile here stateside.
MrObvious said:
Don't flash the 860 radio on an 861/862/883 or vice versa. If you want GSM use the 883 radio, if it will let you.
Click to expand...
Click to collapse
I appreciate the advice and I have used the 883 radio sp successfully several times but what I want to know is why can't we just use the 860 radio? Is there a hardware difference or will it just not work ith the 862 firmware? If the firmware is the problem could we just puut the entire 860 firmware on an 862/861/883 and essentially make it an 860? Have you tried this and it didn't work?
Sent from my XT862 using xda app-developers app
---------- Post added at 07:12 AM ---------- Previous post was at 07:06 AM ----------
Gilly Monster said:
When I did this I didn't need to change the build prop. It work just fine for me. It worked while I was in Afghanistan and works on ATT and T-Mobile here stateside.
Click to expand...
Click to collapse
I think I read somewhere that with a foreign sim in the phone it will work on at&t and tmo and it would work in afghanistan anyways so I guess my question is were you using a sim from a carrier in afghanistan when you returned here?
Sent from my XT862 using xda app-developers app
I imported a GN when it first came out. I am in the US. I use it as a mini tab no SIM.
If I try to update the firmware over wifi it says "no sim" or something. No upgrade.
So I try in Kies and it says something like Kies doesn't support firmware updates for this device or something similar.
So how can i update this? I don't know why they won't let me do it but it is irritating to say the least.
I am not good with odin and rooting and flashing leaks or custom ROMS, I just want a stock normal update? Anyway to do this?
check your csc if there is a update for your gnote.
dial *#06# for emei, write down
then dial *#272*emeinumberhere* and check which csc is selected. Can you post that here?
dont post your emei here btw, just csc code
Sent from my GT-N7000 using Tapatalk 2
can use u also check your firmware version in settings then about phone?
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
can use u also check your firmware version in settings then about phone?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
It is very old, what ever it was when it came out (I think gingerbread), it is not ICS and that is what I wanted to upgrade to.
Samsung service center should update your your device
Sent from my GT-N7000 using xda premium
danteoo7 said:
Samsung service center should update your your device
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
A US service center will update a device I am not supposed to have(import)? Something tells me no. They will just tell me to get the authorized device (crap slow ATT version) for my region.
So I guess there is no way to do it at all? I guess that is what we get for importing, they refuse to let you make any updates. Damn Samsung!
DaveC1964 said:
A US service center will update a device I am not supposed to have(import)? Something tells me no. They will just tell me to get the authorized device (crap slow ATT version) for my region.
So I guess there is no way to do it at all? I guess that is what we get for importing, they refuse to let you make any updates. Damn Samsung!
Click to expand...
Click to collapse
As above poster said, check your csc. Then you can download a corresponding or different csc, such as American and install any official rom such as ics via pc odin.
Sent from my GT-N7000 using xda premium
Easiest way to do it is still via ODIN - Check out Dr. K's thread, there's a complete walk through..
baz77 said:
check your csc if there is a update for your gnote.
dial *#06# for emei, write down
then dial *#272*emeinumberhere* and check which csc is selected. Can you post that here?
dont post your emei here btw, just csc code
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
It doesn't give me the CSC. I got the other but it does nothing when I type in all of that plus my imei. Yes I checked the number a few times to make sure I didn't get it wrong.
sorry made error code should be *#272*imei# my bad. Be careful changing it on ics kernel due to brickbug as it triggers factory reset/wipe.
pc odin is good alternative, then you can update to whatever you want as Jim said. It might be wise before to root so you can backup efs partition thought. http://forum.xda-developers.com/showthread.php?t=1606012 Rooting can be done via dr Ketans thread also.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
sorry made error code should be *#272*imei# my bad. Be careful changing it on ics kernel due to brickbug as it triggers factory reset/wipe.
pc odin is good alternative, then you can update to whatever you want as Jim said. It might be wise before to root so you can backup efs partition thought. http://forum.xda-developers.com/showthread.php?t=1606012 Rooting can be done via dr Ketans thread also.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ok thanks, What do you mean"changing it on ics kernal? Changing what on ics kernal? You mean changing imei number? or do you mean typing in that code? I am not sure what you mean.
DaveC1964 said:
Ok thanks, What do you mean"changing it on ics kernal? Changing what on ics kernal? You mean changing imei number? or do you mean typing in that code? I am not sure what you mean.
Click to expand...
Click to collapse
Entering that code on your dialler will show you a list of csc codes installed on your device. If you change from the one currently applied it will perform a full wipe of device, on ics that's dangerous. So if you want to change csc, need to flash gb rom first then change csc before upgrading back to ics.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Entering that code on your dialler will show you a list of csc codes installed on your device. If you change from the one currently applied it will perform a full wipe of device, on ics that's dangerous. So if you want to change csc, need to flash gb rom first then change csc before upgrading back to ics.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I am already on GB so I guess I don't need to worry yet. If I go to ics will I then have brickbug? Is there a way to avoid this bug?
baz77 said:
sorry made error code should be *#272*imei# my bad. Be careful changing it on ics kernel due to brickbug as it triggers factory reset/wipe.
pc odin is good alternative, then you can update to whatever you want as Jim said. It might be wise before to root so you can backup efs partition thought. http://forum.xda-developers.com/showthread.php?t=1606012 Rooting can be done via dr Ketans thread also.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
OK if I do this it gives me a "sales code KOR" then install or cancel. The build number is gingerbread.xxkj4
I am on GB, should I change this? I really don't have much set up on this yet to worry about wipe, as long as it doesn't brick.
So that's a Korean csc I believe, it's worth checking your settings in about phone, post what firmware version your on and model of device.
Sent from my GT-N7000 using xda premium
Every rom has a default csc it defaults to if the previous selected csc is not in that rom. You can change it. But beware, be sure you are on safe kernel cause changing csc triggers a wipe, so you will lose data when doing that.
Also if not done already do efs backup, see dr ketans thread on that.
Sent from my GT-N7000 using Tapatalk 2
SpyderTracks said:
So that's a Korean csc I believe, it's worth checking your settings in about phone, post what firmware version your on and model of device.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
model GT-N7000, What indicates firmware version, I see three entries at the bottom which look like they could be it? Is the build number I listed above it?
DaveC1964 said:
model GT-N7000, What indicates firmware version, I see three entries at the bottom which look like they could be it? Is the build number I listed above it?
Click to expand...
Click to collapse
It says android version, just post that.
Sent from my GT-N7000 using xda premium
just post all, dont post your emei (long string of numbers) thought.
Sent from my GT-N7000 using Tapatalk 2
SpyderTracks said:
It says android version, just post that.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
android version is 2.3.5
baseband is n7000xxkj4
So I flashed the newest firmware but it must of been for the European version cause I can't get lte.. Even when I go into the radio menu it still defaults to hspa. Anyone know which firmware is compatible? Thanks!
Sent from my C6606 using Tapatalk now Free
Bump
Sent from my C6606 using Tapatalk now Free
I used this solution with the C6603 firmware and the 4G option is sticking.
http://forum.xda-developers.com/showthread.php?p=45919439
I get LTE when it is sporatically available as they roll it out here.
Sent from my C6606 using xda app-developers app
seniorstew said:
So I flashed the newest firmware but it must of been for the European version cause I can't get lte.. Even when I go into the radio menu it still defaults to hspa. Anyone know which firmware is compatible? Thanks!
Sent from my C6606 using Tapatalk now Free
Click to expand...
Click to collapse
If you flashed the c6602 version, you won't have LTE. Try the 6603 version. I always like to use the unbranded one from Germany. If you did flash the 6603 version, download the 6606 firmware and only flash the baseband. then type *#*#4636#*#* in the dialer and in the radio settings make sure it is set to LTE/CDMA/GSM preferred.
Hey Guys,
I have no idea what the issue is with this. I'm running CM 10.2.
Baseband: 9x15A-ACEFWMAZQ-30110057-39
I have tried flashing the baseband from 10.3.1.A.2.67 (9x15A-ACEFWMAZQ-30110068-44) and 10.3.1.A.2.74 (9x15A-ACEFWMAZQ-30110068-47) via FlashTool, and always says successful, but when I go to Settings > About Phone, the Baseband Version always reports 9x15A-ACEFWMAZQ-30110057-39.
Any ideas?
Nothing wrong,only the about phone is incorrect but the baseband has been changed,cause flashing baseband doesn't change the system files related.
Sent from my C6603 using xda premium
gm007 said:
Nothing wrong,only the about phone is incorrect but the baseband has been changed,cause flashing baseband doesn't change the system files related.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Ah right, too easy. Know which files need editing?
maybe changing build.prop
from: ro.build.fingerprint=Sony/C6603_1270-6697/C6603:4.2.2/10.3.A.0.423/WP5_rg:user/release-keys
to: ro.build.fingerprint=Sony/C6603_1270-6697/C6603:4.2.2/10.3.1.A.2.74/WP5_rg:user/release-keys
Or decompile the System-UI.apk and change it.
Sorry i don't know.
Sent from my C6603 using xda premium
Juzman said:
Ah right, too easy. Know which files need editing?
maybe changing build.prop
from: ro.build.fingerprint=Sony/C6603_1270-6697/C6603:4.2.2/10.3.A.0.423/WP5_rg:user/release-keys
to: ro.build.fingerprint=Sony/C6603_1270-6697/C6603:4.2.2/10.3.1.A.2.74/WP5_rg:user/release-keys
Or decompile the System-UI.apk and change it.
Click to expand...
Click to collapse
Not likely. Unfortunately CM for Odin and Yuga specifically is somewhat behind other phones and most of the nightlies only contain generic CM/AOSP updates. I think the ROM libs etc. are still based on 423. A thorough Odin/Yuga update would be welcome.
My own CM builds for Odin does show 44, the official nightlies don't, for interest.
The baseband needs to have updated RIL files in /system/lib to reflect the radio being used.
In any case, I'm not sure why you are bothered by the fact that CM displays 39 in lieu of 44 or later. There is no tangible difference, and it is just text...
You need to update etc/firmware folder i can upload flashable zip but dont know if it will works on Cm..
Its still useless no matter what it displays in about phone..basseband is still changed
That zip
http://www.myupload.dk/showfile/1P2e-xkAh.zip
Odoslané z C6603 cez Tapatalk 2
NetSkill said:
You need to update etc/firmware folder i can upload flashable zip but dont know if it will works on Cm..
Its still useless no matter what it displays in about phone..basseband is still changed
That zip
http://www.myupload.dk/showfile/1P2e-xkAh.zip
Odoslané z C6603 cez Tapatalk 2
Click to expand...
Click to collapse
On Xperia 2011 line-up, you could change baseband after flashing proper BB libs in recovery. First flash baseband in flashtool, then flash proper libs in recovery.
This should be the same on the Z, if it can be done right. I can look into it?
Sent from my C6603 using xda app-developers app