Hello pros,
I have a S5 (G900F), bought in Germany that has a provider branding from O2 (VIA) I want to get rid off.
After searching and reading many many many threads I wasn't able to find as "safe" solution. There are some threads, where people were able to flash a stock firmware, but it was BTU. Some managed to flash the DBT, but with errors during procedure, workarounds etc.
Since the key to flash from VIA firmware to another seems always to be the correct PIT file and the PIT files also seem to come from this forum I hope to get some professional help to solve my problem. I've already read enough contradictory statements from people who think they might know something, but I'm looking not for assumption.
Here is data from my S5:
AP: G900FXXU1ANG2
CP: G900FXXU1ANG2
CSC: G900FVIA1ANG1
So I have Android 4.4.2 and would like to flash a 5.0 DBT and to keep the KNOX of course.
1. First I wondering why it not working to flash the DBT fw on a VIA S5 with the "original" DBT PIT? If the VIA phones have a different partition layout the PIT for DBT should solve this or not?
2. The most promising solution seems to be use the DBT (it's not state from which to which version the update was done) with special pit version for s5 (also not clear which one was used). When flashing with Odin at the end always a failure message will be displayed. Then disconnect and reconnect the phone and to flash only the PIT after a restart to wipe all. But as mentioned earlier that doesn't sound like a "safe or proven" solution.
Here is the link-> (German) handy-faq.de/forum/galaxy_s5_original_roms_firmware_kies/306126-samsung_galaxy_s5_branding_entfernen_sm_g900f-18.html#post2926313
3. Suppose I use the solution as described in 2. and flash the first 5.0 version (...BNL9) and then perform a update using the build in updated function on my S5 (no Odin, Kies, etc. ) to the second 5.0 version (...BOB7) will the update clean up the possible mess I've done using the procedure above? Or would it be better to use the Kies software on PC to update from 5.0 to 5.0?
I really appreciate competent help on this (and probably many other in the same situation) and no abuse of this thread for other topics .
As step by step guide with a link to PIT file and tool version info (Odin 3.09 etc.) is very welcome.
Cheers!
Flashing the DBT over an o2 branded device is ok. The upcoming error in the end, related to a to small cache.img ext4 partition comes up because of the comparsion by odin of the is and the has to be partition size.
At this stage the DBT rom at the S5 is not installed, it's like a download only. If you now flash the right *.pit as a next step this will adjust the partition size. The installation afterwards will be work and all is on a clean state. Have done this yesterday here in Germany using before o2 branded S5.
Sent from my SM-G900F using XDA Free mobile app
Thank you for the quick reply Endur.
Is there a guide I can follow for the whole procedure (what you did on you phone)? And where can I get the "right" PIT file?
I had some experience flashing a Galaxy S1, so I know this might be tricky and would like to avoid any possible heart attacks during the procedure .
Thanks in advance.
Flash bob7 DBT using Odin (I have used 3.10).
After that you will get the failed message because of wrong partition size.
Unplug USB cable.
Plug USB cable.
Flash *.pit (European for G900F 16GB)
You will get a note now about adjusted partions. The installation of bob7 DBT will start now (you see the green Android spinning). You may wipe cache and data as last step.
Sent from my SM-G900F using XDA Free mobile app
Alright, with mental support of Endur and some courage I just de-branded my phone by updating it from VIA (O2) 4.4.2 (G900FXXU1ANG2) to no branding (DBT) 5.0 (G900FXXU1BOB7). I've used Odin 3.10 and Samsung USB Driver for Mobile Phones 1.5.51.0.
The flashing procedure is basically as described in many other posts, so I don't want to create a copy of a copy. Please take a look for yourself.
Instead I will only add the steps required for O2/VIA de-branding with my experience.
As Endur mentioned the first step with Odin doesn't flash but "copy" the firmware to the phone. Due to different partition layout Odin will show an error. Remove the USB cable and replug it while Odin is still running. Remove the check from "AP" (former PDA) in Odin, select correct PIT, check "Re-Partition" in Odin and press "Start". Now comes the excitement moment. My phone got stack showing Android, powered by Google etc. I had to remove the battery, boot into recovery an wipe data and cache. So it seems to be a must instead of may.
I've used the SM-G900F_pit_16GB.zip (for German / DBT version) from forum.xda-developers.com/showthread.php?t=2737448
Good luck!
Yes, wipe data and cache is a good idea while updating from Android 4.2 up to 5.
There is a lot different for data, Dalvik was changed to ART and much, much more.
I had updated from BTU BNL9 to DBT BOB7 only. The DBT requires the greater partition size for hidden.img while BTU can be flashed without any partition change to a formerly German o2 branded device.
Sent from my SM-G900F using XDA Free mobile app
Related
Hello guys.
I just have one very weird problem with my phone.
Previously, i've been using the asian singapore firmware dxjf4. Today, I decided to flash over to JG5, but didn't like it. So i flashed back to my asian firmware.
What happened is, during the point of flashing, my phone says
E:Error in /cache/recovery/sec_csc.zip
(status 7)
Installation aborted.
Then installation of firmware terminated. Therefore, my phone is still bricked, and I don't know how to revert it back to the asian firmware.
When i flashed the european jg5 firmware, i had to add in the .pit 512, the csc, the pda, and the modem. But for the asian firmware, i only need the pda. So did i flash incorrectly? please help!
Do i need to do a factory data reset before i flash?
Or is there a special way to flash from jg5 to dxjf4?
I wouldn't want another firmware as a solution, because the singapore firmware has specific features and i got certain carrier benefits from the 2 year contract phone line that could enable those specific features.
Thanks.
FOR PEOPLE WHO WANT TO HELP ME, PLEASE LOOK AT POST 4. I HAVE SOLVED THIS PROBLEM, BUT MY NEXT PROBLEM IS ON POST 4.
Clear cache and clear settings, Flash again with Asian and use pit 512 and select repartition option.
If no good stay with jm5 til SingTel releases a new rom with csc file.
Sent from my Apple Newton 2100
List of method tried
Hi ickyboo, i've tried your method before. I even went to the extent of doing a factory data reset on adb recovery. But they all don't help.
For the list of methods i've tried:
flashing dxjf4 with 512 .pt
flashing dxjf4 with 513 .pit
flashing dxjf4 with 512 .pit with repartition
flashing dxjf4 with 513 .pit with repartition (but failed)
flashing dxjf4 with csc and modem of jg5 with repartition
flashing dxjf4 with csc, pda, and modem (but failed)
flashing dxjf4 without any pit
wiping cache and data in adb recovery then flash dxjf4 without any pit
...None have worked and they either show up as
E:Error in /cache/recovery/sec_csc.zip
(status 7)
Installation aborted.
or (failed) if stated above the list of methods.
Please help me thanks.
I realised where i what went wrong, but the problem is i don't know how to solve it, unless i have the file.
Every firmware comes with the csc and modem. Unfortunately, those provided as samsung firmwares are not full. The csc and modem of dxjf4 isn't there. Without that, i cannot flash over to dxjf4.
To prove it to you, i did a simple test. I used the pda of dxjf4, and the modem and csc of dxjg4 (another asian firmware). It successfully flashed over to the asian firmware. However, the dxjg4 is lacking the apps that i need. So i decided to flash back to dxjf4. And of course, that successfully happened but now..... the applications that i want on dxjf4 are gone. So it is easily concluded that the modem and csc aren't changed and are still using the dxjg4 version's.
Now if anyone could post up links on dxjf4's full firmware (pda, modem, csc) it would be much appreciated. (The singtel (a carrier of singapore) version i mean)
Thanks.
I wish I can help you but like you my Telco Optus (singtel) also only released a new Rom recently and without csc or modem file. Why do you need csc anyways? Are you after apps on stock Rom like "my account"? I'm happy with jm5. There's no reason for me to flash stock unless I want warranty
Sent from my Apple Newton 2100
Ask around for the stock apk's for singtel, I'm sure someone has em. Better yet wait for official froyo from singtel
Sent from my Apple Newton 2100
Ok, I may be able to help you now, I found the CSC files you are looking for here : http://forum.xda-developers.com/showthread.php?t=763369
Just get the CSC file and flash with your asian rom. Other then that I can't help you anymore as I can't think of another way except sending it into samsung
solved!
hey ickyboo,
i found the solution and i'm happy with it. My friend managed to get for me the stock apps from singtel, plus i used the full fledge dxjg4 firmware. I'm really happy with the firmware and it is nice and snappy.
Thank you ickyboo, and xda of course.
Hi,
can you share with us the stock apps from SingTel?
Thanks.
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
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
lolozaur said:
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
Click to expand...
Click to collapse
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
willcor said:
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
Click to expand...
Click to collapse
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
lolozaur said:
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
Click to expand...
Click to collapse
hi ,
i personally , don't think it will make any difference or matters,
if you flash the one or the other ..but hey ..who knows ..?
Only reason ,i flashed BOB4 as it was the first Lollipop available and BOC3 was a later date ( March 2015 )
good luck
I have the similar issue. KK and BOB4 roms work and install perfectly. however I am having the same issues while installing BOC3 rom be it Stock or Custom.
So I finally managed to solve the issue. Seems that the image I was downloading from Sammobile was not that good.
I was trying to install N910FXXU1BOC3_N910FVFG1BOC2_CNX - Romania Vodafone. I was unable to install it no matter what I tried.
I was able to install N910FXXU1BOC3_N910FTPD1BOC1_TPD - Netherlands unknown, without any issues.
Something that i noticed is that when loading the tar with issues in Odin, total binary size was shown as 0 mb, while on the Netherlands tar file it was showing 3.3gb.
Also the tar sizes where a bit strange : RO CNX 3.6gb - NL TDP 3.4gb. So I would imagine that extra 200mb might be an issue for the partition size (suspecting bloatware maybe?).
Long story short, the tar file I was trying was the issue and downloading a different CSC file solved this for me.
Also, I tried an advice from the forum, where you extract the recovery.img and convert to tar and first flash that tar before the ROM, but that did not work in this case.
Thank you for the replies and support.
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
I installed the BOB4 like said willcor and do an antutu and, I know that it are subjective information, but I was exhausted of see the Meizu above our fairy note 4 (including with the last 4.4.4), but now, I will sleep much more well than yesterday...
Beko68 said:
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
If you're talking about knox (hehe of course, what else) knox still 0x0 after installation...
Doing this kept my knox counter at 0x0, but I did not root or install any custom recovery.
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
BNerd89 said:
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
Click to expand...
Click to collapse
Yes, I wiped from the recovery before and after the BOC3 upgrade and I must say that I like how BOC3 feels.
Battery life feels about the same for me - 50% when I get home (9-5), considering i have BT on all day as i have a smartwatch paired, exchange account, 3 gmails, skype push and a few others.
Love the new Smart Lock features with Trusted Places an On Body Detection.
One thing I noticed, manual check for updates on Security Policy Updates does not give any results, not sure if that is working correctly.
I tried rooting my galaxy j7 with Odin and the feedback I get Is binary size too large
Kindly help me out
#19
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .
Hello everyone, I'd like to start off by saying I am a complete newcomer to all this so please explain literally all of the terminology/jargon you intend to use and correct me when I use it wrong.
I have a Chinese version of the Samsung Galaxy Note 4 SM-N9109W and up until yesterday it was running out of the box on android 4.4.4. I care not for any of the data on the phone nor the warranty as there was none to begin with when it was gifted to me.
I attempted to "root" it as I didn't want any of the Chinese apps/restrictions on it but have failed miserably and now my phone is stuck in a bootloop.
I was following this guide if it helps: http://forum.xda-developers.com/note-4/general/root-note-4-sm-n910c-t2977948 and downloaded the appropriate Snapdragon version (SM-N9109W).
I cannot enter recovery mode by holding down *power+vol up+home* as it just keeps on rebooting. I can, however, get into the downloader by holding down *power+vol down+home*.
I have tried for the entirety of today to find a specific guide for the Chinese note 4 on xda, youtube and google but to no avail - nothing that I can find is identical to my situation and I am hesitant to do anything further to it by following a similar guide in case I make it worse.
I have repeatedly seen suggestions to "flash" stock rom and as I can get into the downloader I believe this would be a great starting point, but once again I am afraid to do anything without a specific guide for the N9109W.
A few people have referred to SamMobile to download stock rom, but a search for SM-N9109W lists 8 files for 4.4.4 and I believe I have no way of working out my PDA or CSC, yet again I don't know what these even are and they might not be relevant?
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience,
Ryan
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
ithehappy said:
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
Click to expand...
Click to collapse
Thank you ithehappy for the reply,
When I search for the stock firmware on SamMobile, I type in my exact model number (SM-N9109W). This search returns with a list of multiple different versions for my phone, of which 8 are 4.4.4 (my initial version).
Does it matter which version I download and install?
To my knowledge, I have no way of finding my CSC or PDA unless you know of a database I can use to search the information that is physically on my phone? Once again, does it matter that I know what these are or can I simply download, for example, version 5.1.1 and flash that on instead of my original 4.4.4? Or, will this just cause further possibly unfixable problems?
Thank you for your help
Anyone?
No, you can download any one you want.
Thank you for the help, ithehappy. I now have a working phone!
For future readers, I downloaded the latest version of 4.4.4 that SamMobile had (2015-03-27) for my model (SM-N9109W):
PDA: N9109WKEU1ANL3
CSC: N9109WCTC1ANL3
It failed the first time I tried flashing with Odin 3.10.7, but whilst I was hastily taking screenshots of my problem to post here I accidentally started the transfer again and it successfully installed that time.
I followed the instructions on SamMobile for the installation.
This version of the firmware I installed does not have any google services (thank China for that), so keep that in mind.
Thank you
Hi,
I have an S7 edge olympic edition straight from the games in Brasil.
It hasn't received any updates since September whereas ZTO Brasil has released multiple updates since then, as well as my provider (Proximus - Belgium).
The CSC code is G935FYTO1BPIF (notice the Y instead of the standard Z).
I'd like to flash the latest 6.0.1 firmware for Belgium - Proximus, but am afraid to brick my phone.
Can anyone tell me which steps I should follow? I found on this forum for example to not use the repartition option in Odin. But in another tutorial they indicated to activate it. Do I need to change some files or not (CSC_Home),...?
Also the multi csc firmware stuff only adds to my confusion.
Bumping the thread. I'm not flashing anything on my phone until I have a decent answer from you guys
jvdv360 said:
Bumping the thread. I'm not flashing anything on my phone until I have a decent answer from you guys
Click to expand...
Click to collapse
1)You can flash stock firmware for you specific device and country using sammobile.com as a free member registration* Remember to download latest stock firmware for your specific model number and country, you can find your model number printed below on back panel of your phone*
2)Go there in firmware section and enter your device model no and country..( Save it to pc and extract it on your pc in particular firmware folder, you will now find tar.md5 file in that folder)..Now download latest versions of odin and Samsung usb drivers for your device( Extract those files as you did with firmware, install latest usb drivers on pc)
3)From your phone's setting>about device>software info>press build version for 7-8 times continuesly to enable developers option
4)You can find developers option below setting>about device..From developers option select oem unlocking and usb debugging enabled
5)Now connect your phone to pc in download mode( Press volume down+home+power button simultaneously, you are now in download mode..press volume up button to continue)
6) Run odin as device administrator on your pc from odin extracted folder, let pc to install device drivers and your device will be highlighted in odin..
7)Add previously extracted tar.md5 file of stock firmware in AP tab of odin, give it some time to be ready..In odin options let auto reset and reboot options checked..*Dont check repatriation option*
8) Now click start button in odin, flashing process have been started..Sit back and relax untill firmware is being flashed..After that your device will be automatically rebooted and you will have latest stock firmware on your device..
*DO IT ON YOUR OWN RISK NOR I NEITHER ANYONE FROM XDA FORUM WILL BE RESPONSIBLE FOR ANY DAMAGE OR BRICK OF YOUR DEVICE*
You can use SamFirm for free and high-speed download of Nougat (Model: SM-G935F, Region: PRO). Since you do want to change CSC for best experience in Belgium you can just use the set you downloaded and flash with Odin (a factory reset will be performed, use the standard CSC not the HOME one). There's no need to flash as admin or set OEM unlock. Keep in mind all olympic specific goodies won't be available afterwards anymore.
Just to put things clear: it doesn't matter which firmware I download as long as it's for an SM-G935F with exynos processor.
I do not use CSC_Home but the normal csc file and afterwards I have a standard s7 edge, correct?
And the chances of bricking it are quite low using Samfirm?
andiling said:
You can use SamFirm for free and high-speed download of Nougat (Model: SM-G935F, Region: PRO). Since you do want to change CSC for best experience in Belgium you can just use the set you downloaded and flash with Odin (a factory reset will be performed, use the standard CSC not the HOME one). There's no need to flash as admin or set OEM unlock. Keep in mind all olympic specific goodies won't be available afterwards anymore.
Click to expand...
Click to collapse
Yes, as long as you use a firmware for the Exynos S7 edge and flash it with Odin chances are towards zero to brick something.
The HOME_CSC is only relevant if you flash something with same CSC as already installed as you do not have to perform the mandatory reset then. This is, however, not your case.
Where you get the firmware is up to you, there's fw.updato.com where you can download from Google Drive (you need to use a trick if Google thinks there's too much traffic), there's sammobile.com (fast download costs money) or SamFirm (still works despite being deprecated). However, all three options are basically maintained by the same team.
Thx for the answer.
As samfirm is deprecated and there seems to be a problem with the fw.updato.com I'll go for the sammobile option.
Leaves me with the question: which options to use when flashing via odin?
I suppose droidhacker's guide is the one to follow: In odin options let auto reset and reboot options checked..*Dont check repatriation option* And with repatriation I guess repartition is meant Can you confirm this?
EDIT: if you're saying 'same CSC', that means from the same carrier? Does this mean in theory that I can flash any other Brasil (ZTO) firmware - which would then be a default s7 edge firmware, but without having to reset my phone? The CSC codes that sammobile mentions are each time different per fw version
Code:
Date Country Version PDA CSC
2016-12-29 Brazil 6.0.1 G935FXXU1BPLB G935FXTO1BPK3
2016-12-21 Brazil 6.0.1 G935FXXU1BPLB G935FZTO1BPL4
2016-12-07 Brazil 6.0.1 G935FXXU1BPK3 G935FXTO1BPK3
2016-11-28 Brazil 6.0.1 G935FXXU1BPK3 G935FZTO1BPK3
2016-11-03 Brazil 6.0.1 G935FXXS1BPJC G935FXTO1BPIF
2016-11-03 Brazil 6.0.1 G935FXXU1BPIF G935FYTO1BPIF
andiling said:
Yes, as long as you use a firmware for the Exynos S7 edge and flash it with Odin chances are towards zero to brick something.
The HOME_CSC is only relevant if you flash something with same CSC as already installed as you do not have to perform the mandatory reset then. This is, however, not your case.
Where you get the firmware is up to you, there's fw.updato.com where you can download from Google Drive (you need to use a trick if Google thinks there's too much traffic), there's sammobile.com (fast download costs money) or SamFirm (still works despite being deprecated). However, all three options are basically maintained by the same team.
Click to expand...
Click to collapse
You click BL, AP, CP and CSC and select the appropriate file (for AP ist may be that it seems Odin hangs but just be patient as this is the biggest file to be read). If device drivers are not installed you need to install them, too. Put the phone in download mode (Switch off, then Vol down+Home+Power together and confirm with Vol-Up). Connect your device and click "Start".
I do not adjust any other settings (Options Auto Reboot and F. Reset Time is ticked by standard, Pit tab is not used). The Re-Partition does not matter in case you plan a reset or need to do so it just should NOT be ticked if you want to keep your settings (along with matching HOME_CSC). This is based on Odin 3.12.5 from odindownloader.com.
andiling said:
You click BL, AP, CP and CSC and select the appropriate file (for AP ist may be that it seems Odin hangs but just be patient as this is the biggest file to be read). If device drivers are not installed you need to install them, too. Put the phone in download mode (Switch off, then Vol down+Home+Power together and confirm with Vol-Up). Connect your device and click "Start".
I do not adjust any other settings (Options Auto Reboot and F. Reset Time is ticked by standard, Pit tab is not used). The Re-Partition does not matter in case you plan a reset or need to do so it just should NOT be ticked if you want to keep your settings (along with matching HOME_CSC). This is based on Odin 3.12.5 from odindownloader.com.
Click to expand...
Click to collapse
Thank you for the clear answers and the help provided. I'll give it a try tonight.
It's basically fairly easy... if any questions just post here. (-:
I'm on UAE firmware can I flash just another county's CSC? I'm in India. Or do I need to flash the whole firmware? Is there a way to flash CSC without a factory reset?
*have been asking all these for a long time in different threads and not getting a reply please help me out *