Hi all,
Last week I bought a Samsung Galaxy S7 Edge through ebay. Everything has been great until it came time to plug in my recently purchased Gear VR which is coming up with a network error. After some searching for solutions, it appears that my phone isn't set to a specific country (so I guess it doesn't know what software to install). I have installed "Phone INFO" which shows as per the attached screenshot.
My question is what could have caused this? If I was to reinstall firmware or attempt to add a CSC could it cause issues? Is it likely the previous owner was just a tinkerer? Am worried If I add a CSC my phone may become blocked or something but If I don't I can't use my Gear VR
Any help or advice greatfully received.
what software version is on your phone ?
It looks like someone may have have upgraded your phone to nougat beta or a custom ropm. Nougat beta does not have a csc associated with it. You need to flash one after installing.nougat beta.
I suggest you ddownload one for your provider from samfirmware or contact the sellor and try to find out what was done to the phone.
ozmo said:
Hi all,
Last week I bought a Samsung Galaxy S7 Edge through ebay. Everything has been great until it came time to plug in my recently purchased Gear VR which is coming up with a network error. After some searching for solutions, it appears that my phone isn't set to a specific country (so I guess it doesn't know what software to install). I have installed "Phone INFO" which shows as per the attached screenshot.
My question is what could have caused this? If I was to reinstall firmware or attempt to add a CSC could it cause issues? Is it likely the previous owner was just a tinkerer? Am worried If I add a CSC my phone may become blocked or something but If I don't I can't use my Gear VR
Any help or advice greatfully received.
Click to expand...
Click to collapse
The previous owner has probably installed a custom rom and that's why the csc is missing. If you don't have root, then I would recommend for you download the stock firmware and flash it with Odin and that should fix your problem.
Cosmic Blue said:
what software version is on your phone ?
It looks like someone may have have upgraded your phone to nougat beta or a custom ropm. Nougat beta does not have a csc associated with it. You need to flash one after installing.nougat beta.
I suggest you ddownload one for your provider from samfirmware or contact the sellor and try to find out what was done to the phone.
Click to expand...
Click to collapse
Please see attached for the software info, does this looks like the beta? Thanks for the replies both, I'll look into this Odin and see what it's all about. I haven't done anything with firmwares for years, not since messing about with Nitdroid on my old Nokia N9, hopefully can still get to grips with it all!
ozmo said:
Please see attached for the software info, does this looks like the beta? Thanks for the replies both, I'll look into this Odin and see what it's all about. I haven't done anything with firmwares for years, not since messing about with Nitdroid on my old Nokia N9, hopefully can still get to grips with it all!
Click to expand...
Click to collapse
Nope. not nougat
You can download full rom and flash through odin. Make sure you flash all 4 files (bl,ap,modem and CSC).
Here's what I thought happened.
Previous owner root phone(cause knox 0x1)
and probably update the firmware by flashing rom though odin or use custom rom. But he/she didn't know how to flash the full firmware though odin properly(or just don't want to. idk) because of the old modem(baseband APEQ) but new rom file(build APG3) and also missing CSC.
These probably mean he/she flashes only AP files(rom) in odin and ignore the other 2 files(modem and CSC) and might also bl file(bootloader).
Sent from my SM-G935F using Tapatalk
NonXtreme said:
Nope. not nougat
You can download full rom and flash through odin. Make sure you flash all 4 files (bl,ap,modem and CSC).
Here's what I thought happened.
Previous owner root phone(cause knox 0x1)
and probably update the firmware by flashing rom though odin or use custom rom. But he/she didn't know how to flash the full firmware though odin properly(or just don't want to. idk) because of the old modem(baseband APEQ) but new rom file(build APG3) and also missing CSC.
These probably mean he/she flashes only AP files(rom) in odin and ignore the other 2 files(modem and CSC) and might also bl file(bootloader).
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Yeah that sounds very plausible, just can't imagine why they would root it and update firmware but not do it properly, every guide I've read directs you to use the appropriate CSC for your country. Well I've got Odin running as we speak, so fingers crossed I can get this working and that I'll be testing out the VR as soon as possible! Does put me off buying second hand in future, but I guess on the plus side at least I don't have a warranty to worry about and can have some fun with different firmware.
some small 3 rd party providers or regional area have csc which are not commonly available, so when you upgrade you would not want to touch the csc.
The sim you are using may not recognize the csc the previous sim card was using that is why it is giving you there error message.
Could be that, guess we'll never know.
As mentioned above I have flashed with the latest firmware and updated the CSC, fortunately it's all working now so thanks for all the support. My refurbishment check now shows as attached.
Related
I became so disgusted with Samsung while waiting for the 2.3.3 upgrade, I gave up a phone company in town upgraded my phone to 2.3.3 for me and it works great. I am happy about that, however KIES now says my phone is not able to be updated... I bought the phone from Vodafone Australia and the firmware looks like it is from Korea?? CSC:JVK (KOR).
Does anyone know how to fix this?? Must I change the firmware again?? The problem is that I have never seen a firmware that is Australia based.. Is it possible to change some setting to trick the phone into thinking that the firmware is from Australia and therefore allowing the updates to occur??
It can't hurt to ask...
Thank you for any replies...
You will have to reflash your phone if you want to get it back to an Australian firmware.
The KOR one is the generic Samsung (Korean company) firmware.
You can check out this web site http://fus.nanzen.se/ to see if your service provider has released a 2.3.3 firmware as yet.
If they have, you can use the CheckFusDownloader application from that site to download the firmware, and you will need to follow the instructions available in this forum to flash the firmware to your phone.
You can change CSC without reflashing (sometimes).
You just type a code into your phone on the dial-pad, utilising your IMEI code, (i think you type *#06# to find out IMEI).
Be aware, one you select a new option (If you have multi CSC on your phone) your phone will reboot and wipe itself with the new CSC. So i say this once and only once DO NOT DO THIS UNLESS YOU ARE FULLY BACKED UP, and/or also don't mind starting from fresh again.
For Galaxy S it is *#272*IMEI CODE#.
Also, my phone is updated to latest firmware and KIES does not recognise it. This is good, because Kies is bad. I'd advise to backup your stuff manually, it's not hard.
If you are using Galaxy S I9000, i strongly suggest getting to know how the program ODIN works. There are plenty of guides on here, and unless you're a total dweeb or seriously unlucky it's a very easy process and hard to balls up.
But, as always, make sure you know what you're doing.
You should be able to get JVT now over KIES.
Flake x
---------- Post added at 12:10 PM ---------- Previous post was at 11:50 AM ----------
Also, to my knowledge, it doesn't matter if you're on the wrong CSC.
The only problem you may encounter is that Market may have a different selection apps, and some may be undownloadable, other downloadable.
Basically, if keywords like 'flashing' and 'Odin' put the fear into you. It's ok, it doesn't matter. My phone ran on KOR CSC for 6 months without any problems, albeit i'm in UK.
Hope this is of some help.
EDIT:
AND i just found this post.
http://forum.xda-developers.com/showthread.php?t=787163
The automatic method will also work if the CSC for australia is not installed on your phone.
again, hope this helps
Flake x
Hey all,
I bought my GNote off of Amazon (I live in the States), and it's been running great. I've been waiting for the most recent update to push to my phone, but it hasn't rolled out yet. So I've been doing a lot of searching to try to figure out where my phone actually came from. Pulling CSC using *#1234# gives me N7000UUBKK2. I can't find reference to that anywhere. When I run Kies or dial *#272*IMEI#, I get the following three options, which I've been able to identify.
VNO (selected) = Venezuela
TDR = DOMINICAN REP.
TTT = Trinidad & Tobago
Anyway, I bring this up because I can't seem to find this in Dr.Ketan's huge list of Stock roms (or any roms from those countries at all, though I am running 2.3.6). Does anyone know more about my rom, or when I can expect to get the newest update that enables the 1-handed keyboard?
@projectrally --- this is something I have not come across from anywhere myself...
Maybe, you be able to find out if you do research through samfirmware.com
you know the one i am talking about ?
There was a UBKK8 firmware floating around the DEV subforum a couple days ago... (http://forum.xda-developers.com/showthread.php?t=1478060)
I think "UB" is Brazil, and being that mine started with the same firmware, I'd say that you purchased the "samsung galaxy note gt-n7000 unlocked cellphone -- US Warranty (blue)" that's actually sold by amazon directly (not a 3rd party.)
I'm curious why would you want to keep the UB firmware? There are much more recent firmware versions for other regions, and they'll all work on your phone. I'm currently running a XXLA4 firmware with no problems.
If there is an issue where I need to send this back, I can easily put a UBKK1 firmware back on the phone.
Take care
Gary
garyd9 said:
I think "UB" is Brazil, and being that mine started with the same firmware, I'd say that you purchased the "samsung galaxy note gt-n7000 unlocked cellphone -- US Warranty (blue)" that's actually sold by amazon directly (not a 3rd party.)
I'm curious why would you want to keep the UB firmware? There are much more recent firmware versions for other regions, and they'll all work on your phone. I'm currently running a XXLA4 firmware with no problems.
Click to expand...
Click to collapse
I purchased from Amazon through a 3rd party seller called Worldwide Imports.
I don't really want to keep the UB firmware, but I've got a mac and really zero friends with PCs that I can use to reflash this thing. Even at work we've got all Macs. I tried installing a wineskinned version of Odin, but it couldn't find my phone via USB, so that didn't work. I've read a lot about heimdall and most of it's bad. I'm new to Android, and I'd rather go with a tried and true method (i.e. Odin on Windows) for my first crack at flashing a new rom.
Eventually I'll track down somebody with a windows machine to do this update, but it might take me a while. In the meantime, I'm sort of stuck with what I've got, so I was just wondering what info there is out there on the build.
I have the same build. I bought mine from expansys last week. I plan on keeping the rom as is and wait for the ICS upgrade. Really enjoying the phone. Everyone notices it.
Sent from my GT-N7000 using xda premium
garyd9 said:
I'm curious why would you want to keep the UB firmware? There are much more recent firmware versions for other regions, and they'll all work on your phone. I'm currently running a XXLA4 firmware with no problems.
Click to expand...
Click to collapse
Gary,
I've got a problem. Maybe you can help. I borrowed a friend's windows laptop and I've upgraded to XXLA4 using the following method...
- Root before reflash using zergrush
- downloaded and extracted zip file for XXLA4 to tar.md5 file
- flashed using mobile odin pro.
The result is that I get a successful update, but I get the "null" problem when typing. People have said that I need to update the CSC file by manually pointing the Cache file at the new CSC file, but I don't have a new CSC file to point to. When I unzipped the XXLA4 file that I downloaded, it was a single .tar.md5 file, which is the file I used to flash. If I put that same file in the Cache field of mobile odin (and don't change any other values) and then flash again, I still get the null error.
So Dr. Ketan says to use the CSC file, but I don't have a CSC file. If I extract the .tar.md5 file again, I get the following five files:
cache.img
factoryfs.img
hidden.img
modem.bin
zImage
Is one of those the file I should be using in mobile odin in the Cache field? Should I clear the cache first?
For now, I just went back and used PC Odin and flashed the KL1 version of XXLA4 without root. I'll keep searching and see what I can sort out. This would be easier if I didn't have to borrow a Windows machine to do this...
projectrally said:
For now, I just went back and used PC Odin and flashed the KL1 version of XXLA4 without root. I'll keep searching and see what I can sort out. This would be easier if I didn't have to borrow a Windows machine to do this...
Click to expand...
Click to collapse
So were you able to get la4 working?
planoman said:
So were you able to get la4 working?
Click to expand...
Click to collapse
Yes, but without root.
NVM Got it
Hi,
i got a Samsung Galaxy Note 3 with Android 4.3 currently installed.
I would like to update it to 4.4.2 but i have several questions before i want to take the risk of updating the device.
As a german user i downloaded this firmware file from sammobile.com:
N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5
This should be the german unbranded 4.4.2 firmware file for the Note 3 N9005.
After reading a few tutorials i saw some people who have problems while flashing this Firmware, because of that i hope you can help me here.
First question:
In Odin i can select the "Phone Bootloader Update", some people are saying i have to select this or the device or it won't work properly after the flash.
Do i have to select this and what happens when i do it?
Second question:
A lot of people also have problems while flashing this firmware because of a missing .pit file (-> http://forum.xda-developers.com/showthread.php?t=2664461)
So do I have to select an .pit file or not?
I really, really hope you can help me with that because Google couldn't help me at all so far.
Geicher said:
I would like to update it to 4.4.2
Click to expand...
Click to collapse
I am actually trying to do the very same thing
The thing is: if you didn't already get an update OTA / via kies (since samsung rolled out kitkat in germany a few days ago) chances are, you are not having a german phone, like myself.
so please enter *#1234# into the dialer app and post the results
also, it would be nice to know your country/product code: if you happen to have the box the phone came in, check the label where your imei and gsm frequencies are mentioned.
There, you'll find a string like "SM-N9005ZKEROM" which (in my case) means a black note 3 from romania
or hook it up with kies and tell the last three characters between the brackets in your firmware version
to your first question: uncheck it. AFAIK, if it is set, the firmware will flash a new bootloader onto your device, and in most cases you don't want that, it could mess your phone up badly. correct me if i'm wrong.
Back to the rom, which also addresses you 2nd question:
The actual problem with simply flashing the DBT rom is that the EU devices happen to be partitioned differently from the german ones, so odin will fail if you have a device with an uncompatible CSC/Product code (e.g. an east-european device), which in turn may or may not trigger knox and/or void your warranty.
i currently try to get more information on that topic.
nevertheless, pocketpc.ch provides a tutorial which mentions flashing DBT firmware along with a custom pit file, which may or may not void your warranty, but doesn't seem to trigger knox (pm me for a link or google it yourself: "Flashen der DBT-FW auf EU-Geräte")
Thank you very much for your detailed answer, as far as i know i will receive the device tomorrow. (Amazon DE order)
I will post the details as soon as i have access to them!
I understand that if i put a custom rom on even another stock firmware for another region other than what my phone came with i won't get OTA updates.
That i understand. I was wondering though how does it know that its not the firmware that came with the phone.
For example if i put BTU on my carrier branded S5 it won't update but how does it know thats not what it came with. What is not changing when it gets flashed.
Is it based on IMEI or is there another parameter that does not get changed when flashing another firmware.
Thanks for your help guys i like to really understand whats going on.
anyone any thoughts
drich290195 said:
I understand that if i put a custom rom on even another stock firmware for another region other than what my phone came with i won't get OTA updates.
That i understand. I was wondering though how does it know that its not the firmware that came with the phone.
For example if i put BTU on my carrier branded S5 it won't update but how does it know thats not what it came with. What is not changing when it gets flashed.
Is it based on IMEI or is there another parameter that does not get changed when flashing another firmware.
Thanks for your help guys i like to really understand whats going on.
Click to expand...
Click to collapse
I don't know how it works exactly, but here is one of possible ways:
Samsung stores the device's S/N and the initial CSC in its database.
(You can check that by using Kies 3 software > Tools > Firmware Upgrade and Initialization, enter your S/N and Kies 3 will show your initial CSC).
That way, when you perform an OTA update, Samsung will know if your current CSC is the same as your initial CSC or not.
Hey guys,
The OTA update for android 7 has come up in my s7 edge duos. I have tried downloading it twice........it gets to 100% and says there an error and that it's the wrong version.
Not sure what to do.........any ideas
Download and flash the rom through odin.
Did you ever flash a different rom? Which brand is respectively CSC has your phone?
Never flashed another rom........bought the phone off amazon.com............it's zn international version, but looks like the supplier got them from UAE.
r374rd said:
Never flashed another rom........bought the phone off amazon.com............it's zn international version, but looks like the supplier got them from UAE.
Click to expand...
Click to collapse
the supplier may have gotten from UAE but the csc may not be from there.
you can try downloading the Rom from samfirmware and flashing that way.
Thanx for the reply guys, how can I find out the CSC on the phone? Also if I flash with odin, Will that erase all the data on the phone? And will it trip the knox?
Why is it that the update doesn't work? How come the software on my phone doesn't match the update it's downloading? Is it something the supplier/seller has done to the phone? Like modify the software?
Thanx guys
Install Phone INFO ★Samsung★ and you get all necessary information.
If you flash with Odin Know won't be triggered. You can keep your data with the three following requirements:
- The firmware you flash must have the CSC included you use at the moment.
- You need to use HOME_CSC file instead of CSC file.
- You may not tick re-partition.
Keep in mind to only flash firmwares designed for the Exynos variant.
Sellers on Amazon sometimes get phones from a different market and flash then a firmware fitting your market. This is rather a replacement than a modification (since the whole system is still official) and Knox is not triggered. However, one effect is that OTA may not work or gives "phantom" update notices. There's no restriction aside of that and you can just use Odin to remain updated.
You can post screens from all pages of the app I mentioned and we can see what's going on.
Hey Andiling, really appreciate your help pal. Here are some pictures you requested. Thank you