Hi all,
Thank for reading this post.
After I have flashed my branded carrier Vodafone NL -> to the PHN firmware - everything went well. I could boot up set up my account, then when I started to set up my KNOX account, the problems began to appear.
First I could not sign in my KNOX account ... then perform a reinstall of KNOX but ran into an error message telling me "was not able to install because KNOX detected a custom binary" (Phone not rooted). So when I look into ODIN splash screen of the telephone KNOX warranty was ok 0 0x0000). However the letter "b" down below was turned from "0" into "1", this would mean that the binary was changed at some point (well yes, I just flashed to another stock rom).
Anyway, since I need KNOX for work, I had to flashed the Phone back to the Vodafone NL rom. By doing that I was able to get everything up and running again including KNOX. However, when I checked the information I saw that my CSC information was wiped away.
So my question is: I have the Vodafone NL Firmware, when I extract the 5 files, I see a CSC and HOME_CSC file. Is it safe to flash these files via ODIN? Or which files do I need to have in order to get back my CSC information?
In advance thanks for your help.
Cheers!
[UPDATE]
Problem solved - via SmartSwitch - Flashing Original F/W
Related
Hi all,
New here. Just bought myself a Galaxy S3 (first smartphone). It's a bit tricky to get use too but is fun.
I basically purchased the phone as an import, so it came with French(?) software, though I wanted to change to Australian Firmware. I downloaded the latest Australian Firmware from;
sammobile.com/firmware/?page=3&model=GT-I9300&pcode=XSA&os=1&type=1#firmware
along with the "Additional Files" which came with Odin 3.04
I booted the phone into Developer Mode then loaded Odin, left "Auto Reboot" & "F.Reset Timer" checked & other boxes unchecked/unchanged.
The phone detected (0:[COM9]) highlighted in light blue.
I then loaded the downloaded Firmware into 'PDA' section (.tar.md5), then clicked 'START'
The phone and Odin did its thing then 'Green PASS' appeared and phone reset.
I input all the details into the phone and details from *#1234# are as follows;
~~~BEFORE UPDATE~~~ (French stock ?)
AP: I9300XXALEF
CP: I9300XXLEF
CSC: I9300XEFALE1
~~~AFTER UPDATE~~~ (Australian Sotck ?)
AP: I9300XXBLH3
CP: I9300XXLH1
CSC: I9300XSABLH2
Afterwards I went into system settings and did a factory reset. After phone loaded up again, re-did all the details, but, when I went to update (there was a system update available), it failed to update. I loaded Kies and it said "your device does not support software upgrading via Kies". After this, I remembered the PDF Flashguide from sammobile said to Factory Reset using *2767*3855#, which I then did, re-did all the info again. Attempted the update and it seemed to work (unknown if anything was actually installed as it was quite fast). Now Kies says "This is the latest Firmware"...did it work?
If this is all good, what went wrong during this process? (so I know for future reference)
Is there anything I can check to make sure everything else is all good ? I basically want Australian Stock Firmware and don't really want any issues downloading updates via Australian networks.
Another thing, I read a couple times where people are saying UK firmware is 'better'?...something to do with faster updates ??
Sorry for the long post, kinda new and wanted to be clear as possible (noob video told me to ).
Kind Regards,
OZ Thread .
http://forum.xda-developers.com/showthread.php?t=1683668
Hey,
Thanks for the link. I've copied and paste my question to that Aus thread so this one can be locked/deleted if mods wish.
Thanks again
Regards,
SO i debranded my N3, it was UKcarrier branded and flashed BTU rom no issues. Knox stayed at 0x0
Only thing ive noticed so far is when i plug into KIES it says "Your devise's current firmware version is not supported to update firmware via KIES.
I assume this is because even tho i flashed the BTU rom, my CSC stays as VOD untill i change it?
Example, when i boot to recovery it still shows the message about applying VOD CSC.
I guess OTA will be no issue still, but KIES doesnt like the different CSC mismatch.
I'm gona assume the only way to truely debrand/change csc is gonna be with root once it is eventually able?
I remember on my s3 i did it by dialing *#272*IMEINUMBERHER# or somethign along those lines but as far as i know that stopped working on newer phones/FW's?
Hi there
Did you just flash a btu rom over existing Vodafone branded rom to debrand it.
John
Also interested - did you just flash the stock rom from sammobile?
Did you do a factory reset? It generally resets the CSC.
I rooted my phone two weeks ago with towelroot and disabled Knox with supersu.Note: my device status said official I'm still running stock firmware. Have to send my phone back for warranty problem so I unrooted with supersu and reset my phone. So now when I look at my device status it says custom (never flashed any roms or nothing) so I factory reset and notice unlock padlock and custom on my reboot startup screen. I also put phone in Odin mode the binary still said Samsung official but now the other say custom. And Knox says 0×0. I was told to use Odin so I installed odin3v3.09, drivers, stock firmware on the PC tried to flash it but got a Auth: Fail in the left lower box.
My replacement phone will be here today and will send the old back Monday to give me a couple more days to figure this out. What did I do wrong?
PLEASE HELP!
UPDATE
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Try going to the sammobile website (cant post link because I'm a new member). It should be there
Sent from my SM-G900F using XDA Premium 4 mobile app
tmadekush said:
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Click to expand...
Click to collapse
Your warranty should be honoured because it still shows Knox 0x0. But it would be prudent to resolve the custom message as you are trying to do. It's showing custom because you disabled Knox. Flashing a full stock firmware should restore Knox and resolve the custom message.
Odin flashes can fail for many reasons e.g. trying to flash non-Odin versions of firmware, bad signatures, poor quality USB cables, wrong firmware version e.g. one meant for a different phone, et cetera.
Back up your files, then do a full system reset from the settings menu. Then put your phone into download mode and use Odin to flash a full stock firmware. Ideally use the latest firmware version for carrier that the phone originally came from (i.e. it should match the baseband). Google will find many firmware repositories e.g. sammobile, samsung-updates and this site.
.
I have a Note 3 SM-N9005. There was a polish release of 4.4.2 firmware, which I'm fairly certain was this, which I installed in January using this guide on XDA.
Today I discovered that my carrier (Telstra, Australia) had released an official 4.4.2 firmware N9005XXUENE3, and thought I would flash it. The flash failed and I got the message "Firmware upgrade encountered an issue" in recovery. In a panic, I tried to return to the polish firmware. Having lost what I'd originally flashed, I tried N9005XXUENA6 from sammobile first. This got me to the setup screen, but the phone would crash on the first or second page of setup with "Unfortunately Samsung Setup Wizard has stopped". I then downloaded the N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX from the first link. This has the same result.
After each flash I did a factory reset and wiped the cache (not dalvik, because I'm not rooted). The stock firmware comes just in the form of a .tar.md5 as did the N9005XXUENA6 from sammobile, but the final polish firmware and the original I had installed had separate parts for bl, ap, cp, csc.
Is this what it means to be soft-bricked?
What was the mistake that I made to result in a soft brick?
What can I do to have a functional phone again, either with stock firmware or anything at all?
Given that my knox is still 0x0, is it likely my warranty is void anyway, and can I repair this somehow?
Go to SAMMOBILE and download the latest Polish or Slovakian rom using the europpean pit. My N9005 is polish too, and yesterday I had the same problem, thinking that since I am bulgarian , the bulgarian rom should work.
So install the Polish or Slovakian (see down) and it should work...
+ this pit: http://forum.xda-developers.com/attachment.php?attachmentid=2427062&d=1385931899
SM-N9005
Poland (T-mobile)
2014 October
4.4.2
N9005XXUGNI4
N9005TPLGNI1
or
SM-N9005
Slovakia
2014 October
4.4.2
N9005XXUGNI4
N9005TMSGNI1
Alexander_Q said:
I have a Note 3 SM-N9005. There was a polish release of 4.4.2 firmware, which I'm fairly certain was this, which I installed in January using this guide on XDA.
Today I discovered that my carrier (Telstra, Australia) had released an official 4.4.2 firmware N9005XXUENE3, and thought I would flash it. The flash failed and I got the message "Firmware upgrade encountered an issue" in recovery. In a panic, I tried to return to the polish firmware. Having lost what I'd originally flashed, I tried N9005XXUENA6 from sammobile first. This got me to the setup screen, but the phone would crash on the first or second page of setup with "Unfortunately Samsung Setup Wizard has stopped". I then downloaded the N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX from the first link. This has the same result.
After each flash I did a factory reset and wiped the cache (not dalvik, because I'm not rooted). The stock firmware comes just in the form of a .tar.md5 as did the N9005XXUENA6 from sammobile, but the final polish firmware and the original I had installed had separate parts for bl, ap, cp, csc.
Is this what it means to be soft-bricked?
What was the mistake that I made to result in a soft brick?
What can I do to have a functional phone again, either with stock firmware or anything at all?
Given that my knox is still 0x0, is it likely my warranty is void anyway, and can I repair this somehow?
Click to expand...
Click to collapse
My note 3 is not actually polish. I used the polish firmware because it was the first to offer 4.4.2. Does this suggestion still apply?
Alexander_Q said:
My note 3 is not actually polish. I used the polish firmware because it was the first to offer 4.4.2. Does this suggestion still apply?
Click to expand...
Click to collapse
I'm not sure... do you know your original configuration, before this 4 file polish rom?
Still you need to try and flash, one thing is sure, you can't flash an older one. So if your phone is not locked to any operator than any latest stock rom from your region should work. If you're not sure which region is your phone originally from, then there's a problem....
So go to sammobile, type n9005 in the firmware tab, and try the ones at top,October...November, from your region. And use the pit file too.
The latest for my region and carrier is N9005XXUENE3, which is what got me into trouble in the first place in my OP. What should I try next?
Update: Got past setup and into homescreen. Usually crashes after about 10 minutes, but sometimes I can get up to a few hours. Doesn't detect the SIM card, and camera doesn't work. Any clue what might be going on?
Alexander_Q said:
Update: Got past setup and into homescreen. Usually crashes after about 10 minutes, but sometimes I can get up to a few hours. Doesn't detect the SIM card, and camera doesn't work. Any clue what might be going on?
Click to expand...
Click to collapse
http://www.sammobile.com/forum/showthread.php?t=20032
do this above
load your rom in the AP
load the pit File
use odin 3.0.9
good luck
I did the same and it worked
Any suggestions as to how to get my UK vodafone contract I9505 back to its correct CSC ??
Back in the mists of time (JB or KK) I flashed a ROM which flipped my CSC from VOD to Switzerland (AUT). Now I've tried applying I9505XXUHOB8_I9505VFRHOC1_VOD.ZIP to get back to Vodafone UK's CSC and the bloody phone thinks it's Spanish (ATL) !!
This is driving me bananas! I've tried reflashing, clearing the cache and doing factory reset before and afterwards, I've tried reflashing it twice with a factory reset from android and that hasn't worked either. There's so much crap out there on what should fix the problem but I can't find anything that actually works.
Phone is currently "offical" status and has knox 0x0 and I'd like to keep it that way, but I really want to get the CSC situation resolved so I can take a stab at getting the vodafone wallet/NFC support working. I need to stay away from rooting it as I use the phone for banking
Please help!
WARNING: The following procedure will result in the S4 being factory reset. Backup all data beforehand.
Dial *#272*IMEI#. A screen will appear with the list of available CSC codes. Select one and reboot. The other option is to use CSC Changer from the Play Store.
Strephon Alkhalikoi said:
WARNING: The following procedure will result in the S4 being factory reset. Backup all data beforehand.
Dial *#272*IMEI#. A screen will appear with the list of available CSC codes. Select one and reboot. The other option is to use CSC Changer from the Play Store.
Click to expand...
Click to collapse
*#272 doesn't work any more.
In the end I went down the root/csc change app path.
Downgraded to I9505XXUGNJ5_I9505VFRGNK1_VOD 4.4.2, then used towelroot & Mr Wolf's instructions to get root for NJ5. Now I was able to use (I think) csc selector to flip the CSC over to VOD. Finally I reflashed and factory reset I9505XXUHOB8_I9505VFRHOC1_VOD again and am now on lollipop with the correct CSC
And most surprisingly I'm still knox 0x0 !! It was showing custom status whilst it was rooted, but is now back to official.
Last step was to bung geohot a tenner for writing towelroot and making this possible