Related
Dear folks,
I have a dutch Galaxy S6 (firm: XXU1AOCV, Netherlands) which i updated today manually with ODIN to XXU1AOE3 (France)
I flashed with stock settings in ODIN and my question is:
1. How can i flash a rom in ODIN so the phone will flash device to factory reset? Since i flash with ODIN, my apps still remain. Do i have to check another box in ODIN?
2. Is it ok to flash another firmware from different country on device from native country?
Many thanks in advance!
I would like to know exactly the same...
I yesterday flashed france newest firmware, its ok i believe.
After the flash i immediately made factory reset...
So far so good, i did a flash via ODIN and a factory reset afterwards. Only language and keyboard dictionary is set in other language.
I hope within a month our device will be upgraded to 5.1.1 and our device will be flying!!
Thanks
So, having smart switch installed on your pc doesn't cause any problems when flashing via odin? Samsung KIES did cause some problems when flashing via odin.
And how's performance? Is the latest french firmware really that much better than our latest Dutch version?
greets
my samsung s4 is i9505, its in settings>about and beneath the battery. i rooted my phone a week ago and installed cyanogenmod rom 12 and then kushan rom v7. now i want go back stock 4.4.2, but in download mode my phone model is different then before. its SPH-L720. thats a verizon model. is this possible ??
further i cant install stock firmware(by stock firmware i mean stock firmware of i9505) in pc odin and the error msg is "complete write operation failed" however i can install stock firmware in mobile odin pro but during flashing modem # 2 remains same with msg "memory protection enabled, skipping" and hence with end result my phone has no wifi, LTE and 3g connectivity. i cant flash boatloader and modem. the baseband is of verzion phone installled. current phone info;
AP: I9505XXUGNF1 CP: L720VPUFNAE CSC: I9505OXAGNF1
i have tried different odin versions, different cables including original cable, different PC's with diff. OS & different ports on each PC. custom rom and recovery are still flashable and then wifi, lte and 3g works. triangle away 3.26 dosent reset the counter. kindly help me !!!
i want to remove this thread, if mods or admins can remove it. thanks
Hi guys,
I'm posting searching for some assistance. I have a Galaxy S6 SM-G920i that I've been trying to flash a stock rom using Odin with no success.
I've tried flashing 5.02 versions, but read here that it won't work since it has an older bootloader.
Tried flashing 5.11 versions, but get stuck in boot screen/samsung logo.
Tried 6.01 versons, but get a DRK error after flashing.
Aldo tried with different versions of Odin, to no avail.
What else can I do to get my phone to work? I've tried ZTA and ZTO rom versions, but there seem to be no difference.
Also, I didn't make a backup of any folder, unfortunately. Read about many people that managed to get their phone working again, can anyone shed some light?
Thank you very much.
Edit: some more details:
- Odin v3.09 apparently gets stuck at "NAND Write Start!!" everytime. I'm trying with v10.6 and 12.3.
- Already tried changing the USB port, but I don't have another PC to try it.
- Tried flashing these roms already:
5.02
G920IDVU1AOD1_G920IZTO1AOD1_G920IDVU1AOD1_HOME.tar
G920IDVU1AOD1_G920IZTO1AOD1_G920IDVU1AOD1_HOME.tar
5.11
G920IDVU3DOJ6_G920IZTO3DOJ6_G920IDVU3DOJ6_HOME.tar
G920IDVU3DOJ6_G920IZTA3DOJ6_G920IDVU3DOJ6_HOME.tar
6.01
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar
G920IDVS3EPK2_G920IZTO3EPIF_G920IDVU3EPIF_HOME.tar
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar
G920IDVS3EPG4_G920IZTO3EPFC_G920IDVU3EPG3_HOME.tar
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920I
Region: INU
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
Once it finished, you'll have DRK problem again.
To fix that, download and extract this;
https://download.chainfire.eu/736/CF-Root/CF-Auto-Root/CF-Auto-Root-zeroflte-zerofltedv-smg920i.zip
Open the "Odin3-v3.10.6" file in extracted zip folder, then press AP and select "CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5"
Once you've set the file to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
Thanks for the help, I'm going to follow those steps!
But one question: why should the region be INU? Shouldn't it be ZTO or ZTA (I live in Brazil, it's a brazilian model)?
Thanks, it worked!
The phone is running again, but there is still a problem: when I try to use 3G/4G it doesn't work, and if I try to make a call, it says it's "not registered to network".
I tried the same chip on another phone and it was working, so it's not a faulty chip. How can I fix this?
luckysquall said:
Thanks, it worked!
The phone is running again, but there is still a problem: when I try to use 3G/4G it doesn't work, and if I try to make a call, it says it's "not registered to network".
I tried the same chip on another phone and it was working, so it's not a faulty chip. How can I fix this?
Click to expand...
Click to collapse
Is your IMEI still intact?
No, it's not the same number as the back of the phone. It shows 3500000000006. How do I return it to it's original value?
luckysquall said:
No, it's not the same number as the back of the phone. It shows 3500000000006. How do I return it to it's original value?
Click to expand...
Click to collapse
I think the IMEI was written with a box (like Z3X) and it needs a patched modem firmware. You flashed stock modem while flashing the stock ROM, thats why the "IMEI" can't read by modem.
So, you need a box (like Z3X) to patch the modem again.
I see... so there's no way to change the IMEI without a box?
luckysquall said:
I see... so there's no way to change the IMEI without a box?
Click to expand...
Click to collapse
Yes, there's no way to change the IMEI without a box.
ahh the ole efs corruption. Seems to be common on this phone, and is essentially the worst thing that can go wrong from flashing :/
Hi guys,
it's been a few weeks that I'm struggling to understand why I'm not getting software updates.
My phone is stock, never rooted nor flashed. It's been with this software since when I bought it.
My CSC is VDI and I was noticing that potentially the modem version on my phone (CP) is wrong.
Here's my details:
AP: G930FXXU1DQEI
CSC: G930FVFG1DQE3
CP: G930FXXU1BPJJ
Model: SM-G930F
I was trying to figure out why I'm not getting updates and from what I can see here: http://fota-cloud-dn.ospserver.net/firmware/VDI/SM-G930F/version.xml I should have a different CP version in order to get the update (G930FXXU1DQD7) which also seems in line with what this firmware page has: https://samsung-firmware.org/download/Galaxy__S7__/n494/VDI/G930FXXU1DQEI/G930FVFG1DQE3/
Now, a couple of questions.
- Any idea of the why? Could it be just a mistake in the production of the device?
- Is my hypothesis correct that I'm not receiving updates because of this?
- Would it be safe to only flash the CP part with ODIN and let the device receive the OTA normally?
Looking forward to hearing your thoughts!
I've not heard of a modem stopping updates, but it's not an area I'm fully familiar with.
Flashing modems with Odin is probably the most harmless flash you can do as long as it's for the same android version (e.g. don't flash a nougat modem on a marshmallow device)
You could also try flashing the latest home_csc, and bootloader (BL) if you really wanted to. Both of those are pretty trivial to flash too. If you do flash csc just make sure it's home_csc, and regular csc wipes your data.
Beanvee7 said:
I've not heard of a modem stopping updates, but it's not an area I'm fully familiar with.
Flashing modems with Odin is probably the most harmless flash you can do as long as it's for the same android version (e.g. don't flash a nougat modem on a marshmallow device)
You could also try flashing the latest home_csc, and bootloader (BL) if you really wanted to. Both of those are pretty trivial to flash too. If you do flash csc just make sure it's home_csc, and regular csc wipes your data.
Click to expand...
Click to collapse
Hi, thanks for your reply.
I ended up flashing CP only for the firmware I was at and I straight away got the update notification and the subsequent security patches up to December 2017 ( was stuck at may ). I'm at the latest firmware for my CSC now.
I bought the S22 ultra Korean version with KT branding. I really don't like their bloatware.
I downloaded the non-branded Korean firmware (KOO) and also the non-branded US firmware (XAA).
I tried to flash both using Odin but no luck. It continuously shows the "Secure check failed: PIT" error.
What am I missing?
My first priority is to flash the US non-branded firmware. Both of the models are Snapdragon. So, is it possible to do so?(2nd question)
Original Baseband: S908NKSU1AVCH
Downloaded Korean Baseband: S908NKSU1AVCK_S908NOKR1AVCK_KOO
Downloaded USA Baseband: S908U1UEU1AVC8_S908U1OYM1AVC8_XAA
Odin: 3.14.1
update: Finally successfully flashed Korean non-branded firmware. But CSC didn't change. It is still KT branded one. What did I miss?
You have to look for chimeratool or Samkey to change csc.
did you flash the CSC file ? or just the AP
gav83collins said:
did you flash the CSC file ? or just the AP
Click to expand...
Click to collapse
I used all the four files (BL, AP, CP, and CSC). I didn't use HOME_CSC, used CSC instead.
yeah i was just checking, i dont know then did you try chimeratool or Samkey
gav83collins said:
yeah i was just checking, i dont know then did you try chimeratool or Samkey
Click to expand...
Click to collapse
Sorry, I didn't try Samkey or chimeratool. Is it possible to change CSC by flashing the ROM via odin?
well usually, you can choose to just flash the csc on its own, i dont know why its not working without insulting you with questions like "is usb debugging" enabled lol
gav83collins said:
well usually, you can choose to just flash the csc on its own, i dont know why its not working without insulting you with questions like "is usb debugging" enabled lol
Click to expand...
Click to collapse
Haha, there is nothing to get insulted about. We, humans, are prone to make silly mistakes. I didn't make this mistake this time maybe.
Checklist:
1. USB debugging enabled
2. Samsung driver reinstalled
3. Downloaded Odin's latest version
4. OEM lock disabled
5. Bootloader lock enabled/disabled (tried both).
I was able to flash the firmware once but didn't change CSC. But don't know why.
Then I tried to flash the firmware again but didn't work. It fails to write. Tried more than 20 times with different configurations but no luck.
have you tried the patched versions of odin ? check my thread "here" for links
Thank you for the patched app. If I used patched Odin, will it trigger Knox?
And can I flash US non-branded firmware to Korean branded phones?
Both are single sim snapdragon phones.
i would assume so, but you know what presumption did......... if its a stock rom i dont think it will trigger knox, aslong as its an unmodified official release firmware you should be ok
ive been out of the game for a while due to the pleasure of her majesty, so wait to see what other people say that have been more current than me
I have tried using patched Odin. But it's stuck at Setup Connection.
the only other thing im thinking is maybe there is an error in the download, back in the day they used to come with md5 checksums, they dont seem to now, how confident are you the download isnt corrupted ? have you tried to extract it to see that it unpacks properly
gav83collins said:
the only other thing im thinking is maybe there is an error in the download, back in the day they used to come with md5 checksums, they dont seem to now, how confident are you the download isnt corrupted ? have you tried to extract it to see that it unpacks properly
Click to expand...
Click to collapse
Finally, I was able to flash using Odin. The problem was I tried to flash the US version first which returns with PIT error. But then I tried to flash Korean ROM without restarting the phone. Which caused the problem. But if I flash with a fresh start inside download mode, it works fine.
But the pit error problems are still there for the US ROM. Is there any way to flash US ROM on Korean model?
Thanks a lot for all the replies.
nazmulnsu said:
Finally, I was able to flash using Odin. The problem was I tried to flash the US version first which returns with PIT error. But then I tried to flash Korean ROM without restarting the phone. Which caused the problem. But if I flash with a fresh start inside download mode, it works fine.
But the pit error problems are still there for the US ROM. Is there any way to flash US ROM on Korean model?
Thanks a lot for all the replies.
Click to expand...
Click to collapse
ive only ever owned australian and uk devices, so i couldnt tell you with any certainty, but one would assume if its the same chipset / processor the region of the rom shouldnt make any difference
Yes, I assumed that too. But seems like Samsung added some extra layer of security for different pit files. I tried many ways to flash US firmware. But, it always says "Secure check fail: pit".
Hope someone can crack that. Thanks a lot for your kind replies.
However, I was able to flash KOO ROM a few times but it didn't change the CSC. My phone still remained KT branded.
I tried to cleared cache and did factory reset before booting and after flashing, but no luck.