flash stock ROM without loosing application data. - Samsung Galaxy S7 Questions and Answers

Hey All,
My phone is stuck on Samsung logo. I am reading mixed opinions. Is it possible to flash stock ROM without loosing application data. How can i do this?

I had a similar problem on Monday. I restored my system filed through abd then flashed the AP file from the stock ROM through Odin. I did a wipe prior to this.

Normal flashing procedure with ODIN but use HOME_CSC instead of CSC
Don't ask how to flash with ODIN, the instructions are everywhere

*Detection* said:
Normal flashing procedure with ODIN but use HOME_CSC instead of CSC
Don't ask how to flash with ODIN, the instructions are everywhere
Click to expand...
Click to collapse
Thank you. Will all app data remain intact If i flash with HOME_CSC instead of CSC?

xdanewbie1 said:
Thank you. Will all app data remain intact If i flash with HOME_CSC instead of CSC?
Click to expand...
Click to collapse
As that was your original concern, that is what I posted for lol
Yes
CSC = Factory reset after flash
HOME_CSC = No reset and data remains safe

*Detection* said:
As that was your original concern, that is what I posted for lol
Yes
CSC = Factory reset after flash
HOME_CSC = No reset and data remains safe
Click to expand...
Click to collapse
Thank you
With a phone that only boot-loops. How do I find my PDA and CSC? The model number is SM-G930FZKABTU

xdanewbie1 said:
Thank you
With a phone that only boot-loops. How do I find my PDA and CSC? The model number is SM-G930FZKABTU
Click to expand...
Click to collapse
Google.

xdanewbie1 said:
Thank you
With a phone that only boot-loops. How do I find my PDA and CSC? The model number is SM-G930FZKABTU
Click to expand...
Click to collapse
Flash the latest BTU firmware for the G930F from sammobile or updato.com or samfirm tool on XDA (fastest)

*Detection* said:
Flash the latest BTU firmware for the G930F from sammobile or updato.com or samfirm tool on XDA (fastest)
Click to expand...
Click to collapse
Hello again,
There are 21 versions
I am confirming this to be absolutely sure so that i don't end up potentially loosing my important app data. The latest firmware for G930 is G930FXXU2ERD5.
Is this what i should download?
NAME MODEL VERSION DATE REGION / CARRIER PDA
GALAXY S7 SM-G930F 6.0.1 April 15, 16 United Kingdom (BTU) G930FXXU1APD3
GALAXY S7 SM-G930F 7.0 April 05, 17 United Kingdom (BTU) G930FXXU1DQC4
GALAXY S7 SM-G930F 7.0 January 09, 18 United Kingdom (BTU) G930FXXS1DQLC
GALAXY S7 SM-G930F 6.0.1 November 24, 16 United Kingdom (BTU) G930FXXU1BPJG
GALAXY S7 SM-G930F 7.0 February 06, 17 United Kingdom (BTU) G930FXXU1DQB3
GALAXY S7 SM-G930F 7.0 August 08, 17 United Kingdom (BTU) G930FXXU1DQG1
GALAXY S7 SM-G930F 7.0 September 10, 17 United Kingdom (BTU) G930FXXS1DQHF
GALAXY S7 SM-G930F 6.0.1 July 11, 16 United Kingdom (BTU) G930FXXS1APG3
GALAXY S7 SM-G930F 7.0 April 02, 18 United Kingdom (BTU) G930FXXS2DRC3
GALAXY S7 SM-G930F 6.0.1 June 07, 16 United Kingdom (BTU) G930FXXU1APEQ
GALAXY S7 SM-G930F 7.0 January 16, 17 United Kingdom (BTU) G930FXXU1DPLT
GALAXY S7 SM-G930F 7.0 May 10, 17 United Kingdom (BTU) G930FXXU1DQD7
GALAXY S7 SM-G930F 7.0 December 20, 16 United Kingdom (BTU) G930FXXU1BPLB
GALAXY S7 SM-G930F 6.0.1 November 01, 16 United Kingdom (BTU) G930FXXU1BPJE
GALAXY S7 SM-G930F 6.0.1 September 05, 16 United Kingdom (BTU) G930FXXU1BPHJ
GALAXY S7 SM-G930F 6.0.1 December 13, 16 United Kingdom (BTU) G930FXXU1BPL2
GALAXY S7 SM-G930F 7.0 February 09, 18 United Kingdom (BTU) G930FXXS2DRAA
GALAXY S7 SM-G930F 7.0 November 12, 17 United Kingdom (BTU) G930FXXU1DQJ3
GALAXY S7 SM-G930F 7.0 March 13, 18 United Kingdom (BTU) G930FXXU2DRB6
GALAXY S7 SM-G930F 7.0 July 26, 17 United Kingdom (BTU) G930FXXS1DQGK
GALAXY S7 SM-G930F 8.0.0 May 02, 18 United Kingdom (BTU) G930FXXU2ERD5

I would personally recommend staying on the same Android version if you're concerned about data loss just to reduce the amount of variables at play and to be as safe as possible. So if you're nougat then flash G930FXXS1DQGK, but if you're already Oreo then flash G930FXXU2ERD5.
But ultimately flashing an upgrade with home_csc should still work.

*Detection* said:
Flash the latest BTU firmware for the G930F from sammobile or updato.com or samfirm tool on XDA (fastest)
Click to expand...
Click to collapse
This did not work
Help!
Used
GALAXY S7 SM-G930F 8.0.0 May 02, 18 United Kingdom (BTU) G930FXXU2ERD5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:1/004> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:1/004> File analysis..
<ID:0/003> skip file list for home binary
<ID:1/004> skip file list for home binary
<ID:0/003> sboot.bin.lz4
<ID:1/004> sboot.bin.lz4
<ID:0/003> param.bin.lz4
<ID:1/004> param.bin.lz4
<ID:0/003> cm.bin.lz4
<ID:1/004> cm.bin.lz4
<ID:0/003> boot.img.lz4
<ID:1/004> boot.img.lz4
<ID:0/003> recovery.img.lz4
<ID:1/004> recovery.img.lz4
<ID:0/003> system.img.lz4
<ID:1/004> system.img.lz4
<ID:0/003> modem.bin.lz4
<ID:1/004> modem.bin.lz4
<ID:0/003> modem_debug.bin.lz4
<ID:1/004> modem_debug.bin.lz4
<ID:0/003> cache.img.lz4
<ID:1/004> cache.img.lz4
<ID:0/003> hidden.img.lz4
<ID:1/004> hidden.img.lz4
<ID:0/003> Home Binary Download
<ID:1/004> Home Binary Download
<ID:0/003> SetupConnection..
<ID:1/004> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> SingleDownload.
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 1 / failed 1)

Beanvee7 said:
I would personally recommend staying on the same Android version if you're concerned about data loss just to reduce the amount of variables at play and to be as safe as possible. So if you're nougat then flash G930FXXS1DQGK, but if you're already Oreo then flash G930FXXU2ERD5.
But ultimately flashing an upgrade with home_csc should still work.
Click to expand...
Click to collapse
Is there a way to find out what version I have when phone does not boot up?

Booting to recovery and download mode is still possible? One or both of those should contain the current version information

You have to use Odin 3.13 not
3.12 I believe
Sent from my SM-G930F using XDA-Developers Legacy app

xdanewbie1 said:
This did not work
Help!
Used
GALAXY S7 SM-G930F 8.0.0 May 02, 18 United Kingdom (BTU) G930FXXU2ERD5
Click to expand...
Click to collapse
People need to read a few threads before mucking about flashing blindly..
ODIN 3.13.1 for Oreo

Beanvee7 said:
Booting to recovery and download mode is still possible? One or both of those should contain the current version information
Click to expand...
Click to collapse
Yes it is possible to boot into both. I found G930FXXU2ERD5 in recovery mode

*Detection* said:
People need to read a few threads before mucking about flashing blindly..
ODIN 3.13.1 for Oreo
Click to expand...
Click to collapse
Help!
Still boots to samsung logo

xdanewbie1 said:
Help!
Still boots to samsung logo
Click to expand...
Click to collapse
Not sure why you don't just restore a nandroid backup in full or in part? (wipe cache, dalvik, system then restore system, wipe caches again before rebooting system...?)
My guess is that you probably were not on oreo/8.0 unless you somehow took ota while rooted... I use the Canadian variant but it's pretty much is the same process every android device whether using odin or fastboot to flash
recovery being used is twrp 3.1.1.0? deselected enable digest verification in twrp settings? have you done a backup before today, if so did you swipe right to write to system? I'm more a supersu girl so if not flashing supersu zip to root after touching system and/or kernal you will be stuck at samsung screen of frustration indefinitely due to dm-verity verification fail which can be fixed by flashing system partition of nandroid before booting (if previously boot was working), flashing supersu to update stock kernel, or flashing a different kernel which i'm not totally ok recommending to you at this point in time given that I still don't understand how you don't know if you were on oreo, nougat, kitkat, jellybean, MM, or gingerbread >.<
your best bet if you absolutely have no idea what you are doing is to backup data/complete nandroid while waiting for full firmware download from samsung to finish, might as well go with oreo but may have bugs so might want to wait a bit still and take March or April release date, wait a few hrs so do backups then mount to usb and transfer to pc (not mac right? using samsung usb if possible in 2.0 port) then read up on guides, all in ones, get rooting things needed bc you'll need to re-root. heck reformat your microsd too that sometimes helps (if bored when waiting for firmware to complete downloading - data easily corrupts and I have no idea what led up to this event or has been happening since soooo yeah, might be worth a try)
when download is done using whichever odinis applicable to match firmware you are flashing, turn off antivirus, run odin as admin, connect phone using usb after putting into download mode (btw just to verify dev option - usb debug and oem unlock were selected before starting all of this right? assuming yes sinice rooted already w/ recovery but heads up, will need to do this again after), put extracted ap file in ap, don't reboot only f reset time checked in options in odin, when that's done, reboot phone back to download mode flash recovery/twrp, then go from there and eventually restore data using something like titanium backup if you had that already going, if not... this is why we do backups in recovery before playing with things (esp if unsure what you have or where you are going and how to get there) or regularly so if things go wrong, you have semi-recent image to restore to so loss is minimal.
good luck!
ps. i use whatever firmware matches my carrier (or used to match carrier if unlocked) but here we can use almost any so go with ones w/ least amt of bloat.
pps when set up take a nandroid and save it somewhere like onedrive also you can install custom rom but always like to have clean starting place when i've screwed up and been stuck in similar place before
at least you can get to recovery, hopefully you have backup to can restore from easily!

How long have you left it on the samsung logo? An upgrade to oreo + all the wipes and tinkering you did it might just need to wait. ROMs can sit there for 20+ minutes in some cases.

crazy_dr0id said:
Not sure why you don't just restore a nandroid backup in full or in part? (wipe cache, dalvik, system then restore system, wipe caches again before rebooting system...?)
My guess is that you probably were not on oreo/8.0 unless you somehow took ota while rooted... I use the Canadian variant but it's pretty much is the same process every android device whether using odin or fastboot to flash
recovery being used is twrp 3.1.1.0? deselected enable digest verification in twrp settings? have you done a backup before today, if so did you swipe right to write to system? I'm more a supersu girl so if not flashing supersu zip to root after touching system and/or kernal you will be stuck at samsung screen of frustration indefinitely due to dm-verity verification fail which can be fixed by flashing system partition of nandroid before booting (if previously boot was working), flashing supersu to update stock kernel, or flashing a different kernel which i'm not totally ok recommending to you at this point in time given that I still don't understand how you don't know if you were on oreo, nougat, kitkat, jellybean, MM, or gingerbread >.<
your best bet if you absolutely have no idea what you are doing is to backup data/complete nandroid while waiting for full firmware download from samsung to finish, might as well go with oreo but may have bugs so might want to wait a bit still and take March or April release date, wait a few hrs so do backups then mount to usb and transfer to pc (not mac right? using samsung usb if possible in 2.0 port) then read up on guides, all in ones, get rooting things needed bc you'll need to re-root. heck reformat your microsd too that sometimes helps (if bored when waiting for firmware to complete downloading - data easily corrupts and I have no idea what led up to this event or has been happening since soooo yeah, might be worth a try)
when download is done using whichever odinis applicable to match firmware you are flashing, turn off antivirus, run odin as admin, connect phone using usb after putting into download mode (btw just to verify dev option - usb debug and oem unlock were selected before starting all of this right? assuming yes sinice rooted already w/ recovery but heads up, will need to do this again after), put extracted ap file in ap, don't reboot only f reset time checked in options in odin, when that's done, reboot phone back to download mode flash recovery/twrp, then go from there and eventually restore data using something like titanium backup if you had that already going, if not... this is why we do backups in recovery before playing with things (esp if unsure what you have or where you are going and how to get there) or regularly so if things go wrong, you have semi-recent image to restore to so loss is minimal.
good luck!
ps. i use whatever firmware matches my carrier (or used to match carrier if unlocked) but here we can use almost any so go with ones w/ least amt of bloat.
pps when set up take a nandroid and save it somewhere like onedrive also you can install custom rom but always like to have clean starting place when i've screwed up and been stuck in similar place before
at least you can get to recovery, hopefully you have backup to can restore from easily!
Click to expand...
Click to collapse
Thank you for the elaborate response. I will read up on nandroid backup. I have never made a backup of the phone

Related

[q] SGS4 i9505 signal error !!

I own a SGS4 GT-i9505 which I bought from UAE. I updated the os to 4.3 via OTA . It worked well for about 4 months then it started to show up some signal errors. Actually there is no signal at all. When i searched for updates it showed latest firmwares are alredy installed. Now I got rooted my phone and it didn't solved my issue. Now when I try to update my phone via OTA it shows your device is modified. But when I connect with kies 3 there is an official update available.
Now my question is 1. Can I update that available official update through kies to my rooted phone ?
2. How can I get rid of this no network error ?
3. Is it possible to downgrade my sgs4 from 4.3 to stock 4.2.2 ? If so is there is any problem with knox app in 4.3 ?
Please help now its giving pain..
screen shots are attached.
Thanx.
Yes you can!
HI Friend!
This will guide you to update your phone to the latest official firmware, May be it solves all the problems!
Things you need:
* Samsung Kies
*USB Cable
*device to update/downgrade to official firmware available
How to:
*Open kies
*Go to tools-->Firmware Upgrade and Installation
*Enter your device Model Number i.e. "GT-i9505"
*Now it will ask you Serial number
Go to Settings-->about device-->Status and find serial number and enter it
*Now connect your device and leave till it Updates.. it will automatically reboot and complete Update!
Now your phone will be Upto-date
Don't forget the Thanks button!
SadEff said:
HI Friend!
This will guide you to update your phone to the latest official firmware, May be it solves all the problems!
Things you need:
* Samsung Kies
*USB Cable
*device to update/downgrade to official firmware available
How to:
*Open kies
*Go to tools-->Firmware Upgrade and Installation
*Enter your device Model Number i.e. "GT-i9505"
*Now it will ask you Serial number
Go to Settings-->about device-->Status and find serial number and enter it
*Now connect your device and leave till it Updates.. it will automatically reboot and complete Update!
Now your phone will be Upto-date
Don't forget the Thanks button!
Click to expand...
Click to collapse
Thanks for the reply but here in my case please note that my phone is rooted one and kies itself gives a warning that installing firmwares to rooted devices may encounter any failure !!!
alison20064all said:
Thanks for the reply but here in my case please note that my phone is rooted one and kies itself gives a warning that installing firmwares to rooted devices may encounter any failure !!!
Click to expand...
Click to collapse
No problem just accept and continue...
Don't forget to backup every thing i.e, Contacts and internal sd card for safety I am not sure about it will format it all..
SadEff said:
HI Friend!
This will guide you to update your phone to the latest official firmware, May be it solves all the problems!
Things you need:
* Samsung Kies
*USB Cable
*device to update/downgrade to official firmware available
How to:
*Open kies
*Go to tools-->Firmware Upgrade and Installation
*Enter your device Model Number i.e. "GT-i9505"
*Now it will ask you Serial number
Go to Settings-->about device-->Status and find serial number and enter it
*Now connect your device and leave till it Updates.. it will automatically reboot and complete Update!
Now your phone will be Upto-date
Don't forget the Thanks button!
Click to expand...
Click to collapse
Some thing useful! :fingers-crossed:
No service state !!
SadEff said:
No problem just accept and continue...
Don't forget to backup every thing i.e, Contacts and internal sd card for safety I am not sure about it will format it all..
Click to expand...
Click to collapse
Hey friend,
Thanks for the reply. I have updated my GT-i9505 to android kitkat 4.4.2 but the problem still exist. i have done a hard reset and wiped out the cache after upgrading the firmware. then also the problem still exist. there is no signal at all. Please help me.
thanks in advance
Few questions mate. But first thing to do is get rid of the Imei number you put up in a ss. GET RID OF THAT NOW FOR YOURE SAKE!!!
next question is is it second hand? Possible Imei block if it's second hand.
Next question is have you flashed stock firmware with Odin? What happened? Have you tried to change you're modem?
Sent from my GT-I9300 using xda premium
andrewwright said:
Few questions mate. But first thing to do is get rid of the Imei number you put up in a ss. GET RID OF THAT NOW FOR YOURE SAKE!!!
next question is is it second hand? Possible Imei block if it's second hand.
Next question is have you flashed stock firmware with Odin? What happened? Have you tried to change you're modem?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
1. No i bought it from UAE. And there is no problem with the imie, when i check imie with *#06# it is same as the number in box.
2. Yeah i got rooted my device and it didn't solved my issue. Then i upgraded to 4.4.2 via kies, it removed my root and the status gone back to official.But it is sad that the signal error is same as before.
At this time my firmware details were as follows
Product Code: XST
PDA: I9505XXUFNBA
CSC: I9505OJVFNB2
MODEM: I9505XXUFNBA
Then finally i flashed the modem with odin. The current baseband version is I9505XXUBMF7 . The problem still exist.
please reply..
thanks in advance mate.
Do you get data still? What is uae? ALSO REMOVE YOURE SS OF YOURE IMEI NUMBER. check online with a google search for Imei block checkers. Input you're Imei number into that and see if it's blocked already. :thumbup:
Sent from my GT-I9300 using xda premium
Bricked s4 !! Help please !!
andrewwright said:
Do you get data still? What is uae? ALSO REMOVE YOURE SS OF YOURE IMEI NUMBER. check online with a google search for Imei block checkers. Input you're Imei number into that and see if it's blocked already. :thumbup:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Mate everything gone out of my hand !! I read that flashing the modem individually may resolve the problem from http://forum.xda-developers.com/showthread.php?t=2192025 and i tried it too., I flashed I9505_XXUBMF7_MODEM.tar with Odin3_v3.09 and it got installed in my device which had 4.4.2 kitkat and replaced the MODEM: I9505XXUFNBA without any mess. But the problem remained unsolved . So i tried to flash another modem I9505XXUAMDM_MODEM.tar but something went wrong and the odin download mode didn't finished properly and my phone got bricked :crying:
I tried to recover my device with stock firmware downloaded from http://www.sammobile.com/firmwares/3/?download=26474 but odin fails to flash it. mEssages shown in Odin is given below,
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNBA_I9505OJVFNB2_I9505XXUFNBA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Then i downloaded the pit File and tired to flash with it see below
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ODDIN MODE STATUS IN MY DEVICE IS
ODIN MODE
PRODUCT NAME : GT-I9505
CURRENT BINARY :CUSTOM
SYSTEM STATUS : OFFICIAL
KNOX KERNAL LOCK : 0x0
KNOX WARRENTY VOID : 0x1
USB-COFIG.LSB : 0x30
WRITE PROTECTION : ENABLE
eMMC BURST MODE : ENABLE
I think the failure is due to the write protection enabled in the divice. I s there is any way to unbrick my device ?
.
I have a feeling I have now totally screwed everything up and there is no-way back . Please help ...
BTW UAE stands for United Arab Emirates
UNSOLVED !!!
Someone please help me....!!
Wow you flashed a pit file on a failed Odin flash!! Pit file is a very very last resort thing to do. Had you tried everything and if so what did you try? Odin can be funny with phones at times so don't put of and go flashing pit files. Can you remove the pit you flashed. Does it go into download mode now??
Sent from my GT-I9300 using xda premium
andrewwright said:
Wow you flashed a pit file on a failed Odin flash!! Pit file is a very very last resort thing to do. Had you tried everything and if so what did you try? Odin can be funny with phones at times so don't put of and go flashing pit files. Can you remove the pit you flashed. Does it go into download mode now??
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes, i can get into the download mode.
I tried almost everything i can.I mean as i mentioned in the previous reply. I tried to recover the firmware via Kies recovery, but after downloading almost the recovery file kies says " device not recoganised...... bla blaa "
BTW, falshing pit file always failed in my device !!
eMMC BURST MODE :Enabled
How can i get this bug disabled ?
actually what is this eMMC MODE ?
LOSING HOPE !!! anyone have any idea ??:crying::crying::crying::crying:
Firmware from sammobile.com
And flash it with Odin!!!. Forget kies!!!
Stuck on boot after flash?? Factory reset.
Flash in Odin fail??? Service center fix.
Sent from my GT-I9300 using xda premium
andrewwright said:
firmware from sammobile.com
and flash it with odin!!!. Forget kies!!!
Stuck on boot after flash?? Factory reset.
Flash in odin fail??? Service center fix.
Sent from my gt-i9300 using xda premium
Click to expand...
Click to collapse
samsung totally sucks !! No quality at all> totally hate it..
at first go to download mode then flash with firmware and make sure your phone charged upto 70%.
Sent from my GT-S5282 using xda app-developers app
SOLVED
When i approached the samsung authorized service center they told me to change the mother board and that will only solve my problem. Since the GT-I9505 varient is not available in my country its hopeless. So i gave it to a local store. They just changed the antenna and the network IC. Finally my phone got life back.

[Q] Help!!! please p905 fail on installing stock rom

hi
last night I was trying to change my rigion stock rom
I download p905 firmware for UK
and odin 3.09
then I accidentally used old odin3.07 I had
I run the installation and got FAIL (size)
I was trying to reboot the device after half an hour and did it again
this time using odin3.09
Fail again
now my tab is stuck, I get a screen on strat up saying I need to run kies recovery mode
but that not helping because kies is asking for a recovering code .
I was trying to do it from on other pc same result.
I can get only into download mode !
what I did notice is "knox warranty void 0X1"
I am not sure what happened I never root it or install any rom ??
what can I do ??
I can't even shut it off.
pleas help
Press and hold power button until it shuts down
Serinety said:
Press and hold power button until it shuts down
Click to expand...
Click to collapse
hey thank you for replying.
well it wont turn off.
it just keep rebooting
in to the screen saying
"firmware faild" kind of massage
and please use kies to run emargency recovary.
i can go in yo download mode or reboot in to this screen
what is worng with it
why does odin dont install the ro, ?
i tryied from 2 diffrent pc 10 times
it will run the hole process untill 99% and the fail.?
koopg said:
what is worng with it
why does odin dont install the ro, ?
i tryied from 2 diffrent pc 10 times
it will run the hole process untill 99% and the fail.?
Click to expand...
Click to collapse
Not sure, but probably you uploaded a corrupted boot.img. Supposed your tablet is stuck in downolad mode, I'd try to upload only boot.img and see if then, after a restart, you are able to do a full flash. If this does not work I am afraid that, if nobody has other ideas, you should send your tablet to repair. Unfortunately you tripped your knox counter, so you will have to spend more than few words to explain to the assistance that you didn't try to root your tablet or to flash a custom rom. Moreover I'd not mention odin.
You can find two different boot.tar.md5 files for P905 here:
ht tps://www.dropbox.com/sh/rsm19e62ib4tn6o/AADQBWVe1HVBvO4z2WWyIvpQa?dl=0
Pay attention to the space I inserted in the address.
Use the one that comes from the original firmware you had or from the firmware that you tried to flash.
I don't think that the version of odin that you used matters. As far as I know, both versions are compatible with your tablet. pay only attention to use each version with its own ini file.
aviator1 said:
Not sure, but probably you uploaded a corrupted boot.img. Supposed your tablet is stuck in downolad mode, I'd try to upload only boot.img and see if then, after a restart, you are able to do a full flash. If this does not work I am afraid that, if nobody has other ideas, you should send your tablet to repair. Unfortunately you tripped your knox counter, so you will have to spend more than few words to explain to the assistance that you didn't try to root your tablet or to flash a custom rom. Moreover I'd not mention odin.
You can find two different boot.tar.md5 files for P905 here:
ht tps://www.dropbox.com/sh/rsm19e62ib4tn6o/AADQBWVe1HVBvO4z2WWyIvpQa?dl=0
Pay attention to the space I inserted in the address.
Use the one that comes from the original firmware you had or from the firmware that you tried to flash.
I don't think that the version of odin that you used matters. As far as I know, both versions are compatible with your tablet. pay only attention to use each version with its own ini file.
Click to expand...
Click to collapse
again thank you so much for trying to help !!
I feel so bad, lost, angry at my self for ever massing with my new expansive tablet ( all i wanted is my lte to function )
I forgot to mention I am a total Noob, I thought I can do it but apparently I don't understand nothing and I mass my tab
"but probably you uploaded a corrupted boot.img."
I download p905 firmware file from Samobile I actually tried several different region ending same result.
it wasn zip file contain 1 md5 file as I sew in tutorials i placed it in PDA select box, I got the com thing and hit start.
i download your files but not sure what should I do with it so I am stooping here and going to a local phone lab to get help
"Use the one that comes from the original firmware you had or from the firmware that you tried to flash."
not sure what you ment
p.s
"Unfortunately you tripped your knox counter, so you will have to spend more than few words to explain to the assistance that you didn't try to root your tablet or to flash a custom rom."
I don't think there is a custom rom for this tablet, at least not that I am a ware of.
I didn't tried to place a custom rom.
I love my tab It was perfect just LTE function was disabled.
I talked to samsung support LOL !!
i told them I used the odin LOL
they tried to help me but they guy there didn't understand much .
he gave me a number to call to there specialist but I stop there. ( I didn't want any body in my house hear a (Voice conversation) I mass my expansive tab )
koopg said:
again thank you so much for trying to help !!
I feel so bad, lost, angry at my self for ever massing with my new expansive tablet ( all i wanted is my lte to function )
I forgot to mention I am a total Noob, I thought I can do it but apparently I don't understand nothing and I mass my tab
"but probably you uploaded a corrupted boot.img."
I download p905 firmware file from Samobile I actually tried several different region ending same result.
it wasn zip file contain 1 md5 file as I sew in tutorials i placed it in PDA select box, I got the com thing and hit start.
i download your files but not sure what should I do with it so I am stooping here and going to a local phone lab to get help
"Use the one that comes from the original firmware you had or from the firmware that you tried to flash."
not sure what you ment
p.s
"Unfortunately you tripped your knox counter, so you will have to spend more than few words to explain to the assistance that you didn't try to root your tablet or to flash a custom rom."
I don't think there is a custom rom for this tablet, at least not that I am a ware of.
I didn't tried to place a custom rom.
I love my tab It was perfect just LTE function was disabled.
I talked to samsung support LOL !!
i told them I used the odin LOL
they tried to help me but they guy there didn't understand much .
he gave me a number to call to there specialist but I stop there. ( I didn't want any body in my house hear a (Voice conversation) I mass my expansive tab )
Click to expand...
Click to collapse
[update]
I install the bootloader
the device is alive again. however
I have tones of alerts and error.
I think that my knox is void and it cousing the proplem .
plus the stock rom rigeon I was trying to install sis not work.
So I will try again and see what happens.
any suggestion would be great
is there any way to reset knox ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thats the current state i am in
thats the rom I am coming from
thats the rom I installed
I think that's was my problem pda region wasn't match
maybe that's why my knox void?
the thing is 2 month ago I changed 10 region stock rom with no problem, in order to find lte stock rom
and coming to this united arab emirates was my last try.
so why it didn't it happened beck then ?
to recover i use the bootloader file giving by aviator1, "Boot_XXUANC3.tar"
and then I had alerts about security issues
now I switch to that boot loader "Boot_XXUANH3.tar.md5"
security issue gone
now I have other problem with samsung keyboard not working
BUT I HAVE 4G !!!!!!!!!!!!!!!!!!!!!!!!!!! (thats why I did this in the first place, so now I have a 4g with not working tab )
so if you look at the pictures I uploaded you can understand that I have a mixed rom now or something like that.
and by the odin log you can see it false on partition part in the installation process
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P905XXUANH3_P905DBTANI1_P905XXUANA7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> sbl1.mbn
<ID:0/014> NAND Write Start!!
<ID:0/014> aboot.mbn
<ID:0/014> rpm.mbn
<ID:0/014> tz.mbn
<ID:0/014> sdi.mbn
<ID:0/014> NON-HLOS.bin
<ID:0/014> boot.img
<ID:0/014> recovery.img
<ID:0/014> system.img.ext4
<ID:0/014> modem.bin
<ID:0/014> cache.img.ext4
<ID:0/014> hidden.img.ext4
<ID:0/014> FAIL! (Size)
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so what can I do now ??
by the way knox is still void
to fix keyboard ( the only problem I have now . none stop poping errors)
should I try install United emirates rom again ??
should I try to revert back to region rom I had ?
thanks
lol I talking my self out of this lol
but in order to help others I guess its fine.
so I role back to last known god region stock rom.
and all came back to life no errors what so ever NO 4G
it happened when trying the Germany firmware which is weird I had 2 month ago with no errors whats so ever.
they might changed the partion or I don't know what.
so I am trying to download Germany OLD firmware
if I can mange to install it I might upgrade from kies or something
I waiting for it to download so until its finish if any of you think I should not do it please tell me.
by the way
my knox karnel counter is 0x0
and my knox warranty void is 0x1
I'm quite a noob too, but I think that simply something went wrong during your firmware update and the boot.img was flashed incorrectly. Now I'm happy that you could solve your problem. I don't know if a region change can tip the knox counter, but I'm sure that a not original or recognized as not original boot.img can.
aviator1 said:
I'm quite a noob too, but I think that simply something went wrong during your firmware update and the boot.img was flashed incorrectly. Now I'm happy that you could solve your problem. I don't know if a region change can tip the knox counter, but I'm sure that a not original or recognized as not original boot.img can.
Click to expand...
Click to collapse
so that's wired as you can see my post from september 2014 I was changing 5-8 stock roms from different region and all went fine
"" http://forum.xda-developers.com/gal...samsung-galaxy-notepro-12-2-lte-p905-t2864328 ""
now I am stuck in United emirates or what ever the name is.
i tested
Germany, Germany(old firmware), hongkong, UK, and all failing and soft bricking my tab.
I can get back alive each time by rolling back to emirates.
could it be that in September when I install this rom it locket my tab ??
anybody please, my 4G is just around the corner...
OK thats is my last post at the matter
cut story short.
I was installing wrong stock rom I am not sure why it was wrong, mismatch csc, phone, PDA or what ever
after trying 5 different roms I nail it on Russia rom .
Now I have 4G / LTE enabled latest p905 firmware update (Emirates didn't get it)
downside knox warranty void 0x1.
aviator1 you saved me and show me the way, thank you.
so to get out of the emergency recovery boot I was stuck in
aviator1 supply me with 2 bootloader option files for P905
I flash them and tablet was bootable again but I had many problems, firmware wasn't matching
so then I was rolling back to last known good rom, and my tab was perfectly ok
beside loosing knox warranty.
most imported thing to get out of this story
1. be sure that the rom you are about to install is matching.
2. don't panic !!!!!!!!!!!!!!!!
Anyone knows if can I flash a P905 rom into a P905M device? I see no differences between them since both are LTE capable.

SM-N950U mismatch AP CP and CSC, Cant flash official firmware( Malware )

So i bought this refurbished note 8 (SM-950U) T-mobile varient.
at first everything ran fine until i signed in my google account, thats when the phone starting doing random stuff, like opening playstore and downloading apps without notifying.
well that was the least of my concern, when i tried to update my device, it gave an error "Processing failed" as it failed to register the device.
This is what is in my device right now.
AP: N950USQS4CRE1
CP: N950USQU5CRG7
CSC: N9500ZZH2CRD5
AP and CP seemed ok as both are from the same models, but that CSC file is from SM-N9500 model and as far as i know that is from chinese region and from dual sim models.
The next thing i tried was flashing it through odin with stock firmware that i downloaded from Sammobile.
The files i download are these "
Build date:Thu, 26 Jul 2018 04:01:45 +0000
Security Patch Level: 2018-07-01
Product code: TMB
PDA:N950USQU5CRG7
CSC :N950UOYN5CRG7 "
cant post the links here
i tried to match atleast the build number of my device to the files i downloaded.
After loading the file in odin, connected my phone (turned on debugging mode and removed all of my accounts),
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4857 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
so after researching the internet i found that there were reports of malware in samsung devices in certain regions, and i am certain that i have got one in my phone, so i am really scared to put my passwords or data in it technically rendering it useless.
i cant return the phone, so im stuck with this.
Dude, try flashing TWRP and delete everything, the entire OS and then try to reflash stock ROM with Odin or just flash a custom ROM with TWRP, hope it'll help!
DankMemz said:
Dude, try flashing TWRP and delete everything, the entire OS and then try to reflash stock ROM with Odin or just flash a custom ROM with TWRP, hope it'll help!
Click to expand...
Click to collapse
thanks for the input bro, there was problem with kies and drivers, tried on other computer with same odin version and firmware and everything worked like a charm.
abidhaidary said:
thanks for the input bro, there was problem with kies and drivers, tried on other computer with same odin version and firmware and everything worked like a charm.
Click to expand...
Click to collapse
Glad to help!
hello there,
i've bought a refurbished Galaxy Note 8 and encountered similar problem (missmatch between AP, CP, and CSC)
and my camera results is really really poor, at first i think there were hardware problem and i've tried to change it with the new galaxy note 8 camera and the results is still same.
is there any suggestion regarding this issue ?
did i need to flash my device to its stock firmware ? if it so, what is the correct firmware for my device ?
this is information that shown when i dialed *#1234#:
AP : N9500ZHU4DSD1
CP : N950USQU5DSC1
CSC : N9500ZZH4DSD1
thank you for your helps,
is there a fix were you guys able to flash original OS n950U rom? I also noticed my phone can't run 4g

OTA Update Not Available Galaxy S8 Active (AT&T SM-892A)

As far as I am aware the AT&T Galaxy S8 Active is supposed to be compatible with Android 9.0 (Pie). I just bought an unlocked version of this phone on Amazon and it is currently on Android 8.0 (Oreo). This is the baseband version: G892AUCS3BRG1. I have tried flashing the update file from this post, but I kept getting a PIT error. I also tried using Samsung's Smart Switch, but that also says that 8.0 is 'up to date'. I don't plan on getting an AT&T sim and the phone currently has no sim. Now that you know the information here is my question: How can I update to 9.0 without getting an AT&T sim? The best solution would be a working 9.0 Flash for my device. Thanks to anyone who figures anything out.
NeverEndingCycle said:
As far as I am aware the AT&T Galaxy S8 Active is supposed to be compatible with Android 9.0 (Pie). I just bought an unlocked version of this phone on Amazon and it is currently on Android 8.0 (Oreo). This is the baseband version: G892AUCS3BRG1. I have tried flashing the update file from this post, but I kept getting a PIT error. I also tried using Samsung's Smart Switch, but that also says that 8.0 is 'up to date'. I don't plan on getting an AT&T sim and the phone currently has no sim. Now that you know the information here is my question: How can I update to 9.0 without getting an AT&T sim? The best solution would be a working 9.0 Flash for my device. Thanks to anyone who figures anything out.
Click to expand...
Click to collapse
Flashing the 9.0 firmware from the link you posted above should work just fine.
Have you tried booting into stock recovery and factory resetting the device and wiping the cache partition, then boot into download mode and try flashing the device?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Flashing the 9.0 firmware from the link you posted above should work just fine.
Have you tried booting into stock recovery and factory resetting the device and wiping the cache partition, then boot into download mode and try flashing the device?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I haven't tried that yet. I will try that right now.
EDIT: Alright so I did what you said and nothing changed. I got the exact same error:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7763 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have any other ideas?
NeverEndingCycle said:
I haven't tried that yet. I will try that right now.
EDIT: Alright so I did what you said and nothing changed. I got the exact same error:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7763 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have any other ideas?
Click to expand...
Click to collapse
That isn't a PIT error, it just stopped when it got to the point of checking and flashing the PIT.
What is your exact model number and what model number is the new firmware for?
What version of Odin are you using? You need to use a version that was released around the same time that your device was first released on the market or a version that was released around the same time that android 9 was released.
Did you download your firmware as an all in one .tar file or is it separated into 4 or 5 individual .tar files containing BL, AP, CP, CSC and/or HomeCSC or CSC Home?
Try these simple troubleshooting steps for a failed Odin flash, the thread is from the S2 forum but the troubleshooting steps are the same, using Odin is using Odin, no matter what device you're using it on.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Sent from my SM-S767VL using Tapatalk
Droidriven said:
That isn't a PIT error, it just stopped when it got to the point of checking and flashing the PIT.
What is your exact model number and what model number is the new firmware for?
What version of Odin are you using? You need to use a version that was released around the same time that your device was first released on the market or a version that was released around the same time that android 9 was released.
EDIT: I am also unable to connect via ADB. It says that the device is unauthorized.
Did you download your firmware as an all in one .tar file or is it separated into 4 or 5 individual .tar files containing BL, AP, CP, CSC and/or HomeCSC or CSC Home?
Try these simple troubleshooting steps for a failed Odin flash, the thread is from the S2 forum but the troubleshooting steps are the same, using Odin is using Odin, no matter what device you're using it on.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Unfortunately the device is now bricked. I was watching a YT video and someone mentioned that enabling Nand Erase fixed the problem. My gullible ass tried it and now I can't even access recovery mode. I do have access to download mode, but I am unable to flash anything so I don't think that helps. I am going to try and factory reset from ADB now, but my hopes are not high.
EDIT: It seems that I also can't use ADB because the device is 'unauthorized'. So at this point I think I am going to try and get a replacement.

Choosing the right csc for the UK

For some context, I'm attempting to enable Wi-Fi calling on the UK MVNO iD Mobile. This phone was previously locked to Vodafone and is using a VOD CSC. I was able to at least confirm Wi-Fi calling works with a Vodafone SIM.
AP : G930FXXS7ESK7
CP : G930FXXS7ESK7
CSC : G930FVFG7ESK7
Phone info shows the CSC is VOD, the available codes all look like Vodfone CSCs for European regions.
G930FXXS7ESK7 seems to be a fairly common firmware across Europe, looking at sammobile
https://www.sammobile.com/samsung/galaxy-s7/firmware/#SM-G930F, but I don't immediately see a BTU (United Kingdom unbranded) or XEU (United Kingdom Ireland) CSC for it.
So what should I do, find a BTU CSC from a different 'recent' release and use that. Would that create a Hybrid mix of AP /CSC that doesn't exist. I was hoping to flash a HOME variant so as not to wipe data.
Thanks.
a.d.a.m. said:
For some context, I'm attempting to enable Wi-Fi calling on the UK MVNO iD Mobile. This phone was previously locked to Vodafone and is using a VOD CSC. I was able to at least confirm Wi-Fi calling works with a Vodafone SIM.
AP : G930FXXS7ESK7
CP : G930FXXS7ESK7
CSC : G930FVFG7ESK7
Phone info shows the CSC is VOD, the available codes all look like Vodfone CSCs for European regions.
G930FXXS7ESK7 seems to be a fairly common firmware across Europe, looking at sammobile
https://www.sammobile.com/samsung/galaxy-s7/firmware/#SM-G930F, but I don't immediately see a BTU (United Kingdom unbranded) or XEU (United Kingdom Ireland) CSC for it.
So what should I do, find a BTU CSC from a different 'recent' release and use that. Would that create a Hybrid mix of AP /CSC that doesn't exist. I was hoping to flash a HOME variant so as not to wipe data.
Thanks.
Click to expand...
Click to collapse
Use SamFirm tool to download the last version of BTU, then flash all via Odin for a clean install or just CSC for the region. Easy to use and very fast download.
1. Unzip
2. Rum application
3. Tick Auto
4. Model is typed exactly like this >> SM-G930F
5. Region BTU
6. Hit check update
7. Hit download when check finished
8. decrypt is auto matic, when finised you have your firmware zip file.
cooltt said:
Use SamFirm tool to download the last version of BTU, then flash all via Odin for a clean install or just CSC for the region. Easy to use and very fast download.
1. Unzip
2. Rum application
3. Tick Auto
4. Model is typed exactly like this >> SM-G930F
5. Region BTU
6. Hit check update
7. Hit download when check finished
8. decrypt is auto matic, when finised you have your firmware zip file.
Click to expand...
Click to collapse
it is essential to RUM the application. If you vodka or tequila it, itll just go berserk and run amok
all kidding aside, if all you need to change is the CSC, you can do that in Odin whilst leaving everything else exactly as it is. No need to reflash everything if all you need to change is the CSC. Also, use "CSC_HOME" vs "CSC" from within the zipped file. CSC will factory reset whereas CSC_HOME will not
Thanks for the information guys very helpful. The tool selected HOME_CSC_OXA_G930FOXA6ESGD_CL15877854_QB25123770_REV00_user_low_ship.tar.md5 which I've tried to flash with odin v3.14
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 49 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> cache.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode: SYSTEM REV. CHECK FAIL DEVICE:6 BINARY:5
Phone still starts. Any suggestions please.
a.d.a.m. said:
Thanks for the information guys very helpful. The tool selected HOME_CSC_OXA_G930FOXA6ESGD_CL15877854_QB25123770_REV00_user_low_ship.tar.md5 which I've tried to flash with odin v3.14
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 49 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> cache.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode: SYSTEM REV. CHECK FAIL DEVICE:6 BINARY:5
Phone still starts. Any suggestions please.
Click to expand...
Click to collapse
Ok so the error means you have bootloader 6 (or version 6 firmware) on your phone and you are trying to flash version 5, which is a lower version firmware. You cannot downgrade bootloaders only go up.
I've often encountered problems trying to change the region by flashing CSC from branded (in your case vodafone) to unbranded, it just doesn't like it.
Options.
1. Check you have the correct and latest (last) BTU unbranded and try it again, Or... flash the entire firmware and you phone will be as new but unbranded.
2. Download UK vodafone latest which is "VFG" (instead of "BTU" in SamFirmtool) and flash just the CSC-Home of that firmware (currently version 7).
3. Flash the whole latest VFG Vodafone UK firmware.
As i said flashing just the CSC is hit or miss in my experience.
Either way back up EVERYTHING you want to keep before.
cooltt said:
Ok so the error means you have bootloader 6 (or version 6 firmware) on your phone and you are trying to flash version 5, which is a lower version firmware. You cannot downgrade bootloaders only go up.
I've often encountered problems trying to change the region by flashing CSC from branded (in your case vodafone) to unbranded, it just doesn't like it.
Options.
1. Check you have the correct and latest (last) BTU unbranded and try it again, Or... flash the entire firmware and you phone will be as new but unbranded.
2. Download UK vodafone latest which is "VFG" (instead of "BTU" in SamFirmtool) and flash just the CSC-Home of that firmware (currently version 7).
3. Flash the whole latest VFG Vodafone UK firmware.
As i said flashing just the CSC is hit or miss in my experience.
Either way back up EVERYTHING you want to keep before.
Click to expand...
Click to collapse
Thanks for explaining the error code. It's annoying the operator variants for this phone seem to get regular releases, but the BTU release for example is much less, with the most recent from Aug. The Aug release has codes for VOD/BTU/XEU, but as you say it seems the versioning has moved on.
So, I'm thinking I might try and and hold out for a more recent BTU, hoping it's compatible. If that doesn't happen I might may have to bite the bullet and flash a complete stock firmware. Thanks for the help so far. Really appreciate it.
a.d.a.m. said:
Thanks for explaining the error code. It's annoying the operator variants for this phone seem to get regular releases, but the BTU release for example is much less, with the most recent from Aug. The Aug release has codes for VOD/BTU/XEU, but as you say it seems the versioning has moved on.
So, I'm thinking I might try and and hold out for a more recent BTU, hoping it's compatible. If that doesn't happen I might may have to bite the bullet and flash a complete stock firmware. Thanks for the help so far. Really appreciate it.
Click to expand...
Click to collapse
Hello buddy BTU won't receive anymore updates it's the generic firmware from Samsung. The S7 is no longer receiving updates from Samsung as they're now on S10 etc. In the same way they don't update S4, S5, S6. Any updates will come straight from branded networks who still sell the phones hence the Vodafone update.
cooltt said:
Hello buddy BTU won't receive anymore updates it's the generic firmware from Samsung. The S7 is no longer receiving updates from Samsung as they're now on S10 etc. In the same way they don't update S4, S5, S6. Any updates will come straight from branded networks who still sell the phones hence the Vodafone update.
Click to expand...
Click to collapse
I wondered about that. It seems the s7 dropped off the update roadmap, but then went back on. It's currently on the list for quarterly updates, if that includes BTU idk. It's been 3+ since Aug, i'll give it a bit longer.
https://security.samsungmobile.com/workScope.smsb
A new update dropped with a BTU firmware available, of which I've successfully flashed the csc file. However the phone has remained on the VOD csc. Is there anyway to switch it that doesn't involve some sort of factory reset?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello
I'm getting a little confused as to exactly what you want to achieve, if you have UK VOD installed then your phone will work in the UK and it doesn't have to have specifically the BTU firmware installed. People install BTU in the UK becasue they don't want all the branded rubbish on the phone.
The VOD firmware will show a list of available codes in the region where you are using the phone. This means if you happen to travel to a neighbouring country the phone will look in it's list to see if the correct code is there and use that on the network in that country. It changes automatically. The list in your screen shot are for countries in northen europe, Gemany (DBT) Netherlands (NEE) France (XEF) etc.
So to answer your question, yes there is a way to change csc code without factory reset and you can see the guide here
cooltt said:
Hello
I'm getting a little confused as to exactly what you want to achieve, if you have UK VOD installed then your phone will work in the UK and it doesn't have to have specifically the BTU firmware installed. People install BTU in the UK becasue they don't want all the branded rubbish on the phone.
The VOD firmware will show a list of available codes in the region where you are using the phone. This means if you happen to travel to a neighbouring country the phone will look in it's list to see if the correct code is there and use that on the network in that country. It changes automatically. The list in your screen shot are for countries in northen europe, Gemany (DBT) Netherlands (NEE) France (XEF) etc.
So to answer your question, yes there is a way to change csc code without factory reset and you can see the guide here
Click to expand...
Click to collapse
It was in the original post, but things moved on somewhat. I'm attempting to enable Wi-Fi calling on the UK MVNO iD Mobile. I know the firmware supports it as I've tested with a Voda sim, but with my iD sim the wifi calling option is missing - that's the goal here
Looks like I'd want the root option in that link. I'm not currently rooted, and would only want it temporarily, I'd need to see If i can do that without tripping KNOX, I'm not 100% but I think an app I'm using might require it. If you know of a guide for this it would be much appreciated.
Thanks
a.d.a.m. said:
It was in the original post, but things moved on somewhat. I'm attempting to enable Wi-Fi calling on the UK MVNO iD Mobile. I know the firmware supports it as I've tested with a Voda sim, but with my iD sim the wifi calling option is missing - that's the goal here
Looks like I'd want the root option in that link. I'm not currently rooted, and would only want it temporarily, I'd need to see If i can do that without tripping KNOX, I'm not 100% but I think an app I'm using might require it. If you know of a guide for this it would be much appreciated.
Thanks
Click to expand...
Click to collapse
Soooo.... back to my original answer. Its much easier to save everything you want to keep on your phone and flash a generic firmware for the region, in your case BTU. Generic firmware has all options enabled by default such as WiFi calling. I really see no benefit whatsoever for anyone to remain on branded firmware. When Google play updates it's app it also updates the security patch, did you know this?
With regards to rooting and maintaing knox it isn't possible. Rooting modifies system partition which immediately trips knox. Magisk will show knox at 0x0 but that is visual only for apps to run securely. Banking apps, Sammy pay etc will look for a different file hidden in efs to verify knox is intact, when they read it they will not run period. Knox fuse is a hardware component not a software component.

Categories

Resources