NOTE: I originally posted this to r/AndroidQuestions on Reddit and was advised to post here so please forgive if there are formatting errors as I copied and pasted instead of re-writing everything.
Im trying to upgrade my VZW Samsung Galaxy S7 from 7.0 to 8.0. I used to be heavily into modding my Android phone on my old HTC M8 Google Edition, but when I changed jobs a few years back my company gave us iPhones instead. Last year I got my first new Android device, a Verizon Samsung Galaxy S7 (SM-G930V). I recently was told by a friend that Oreo was available for my phone, which is currently on 7.0 (BUILD NRD90M.G930VVRU4BQF2).
Googling about showed me to an app Updato. Under the FW tab is shows "Update Available!". One the "Easy Mode" page I selected "Update Now", then "CHECK FOR UPDATE" but is says "Your system is up to date".
I checked the "ADVANCED SEARCH" tab, which indicated I need to use a computer and ODIN or KIES to complete the upgrade. After dusting off my old Win10 Laptop I installed KIES 3.
In Kies I selected "Firmware Upgrade and Initialization", input my model number "SM-G930V" & my SN from the settings page but received an error 'SM-G930V' does not support initializing.
So I installed Odin 3.12 and from the Updato website the FW "SM-G930V_1_20180528104327_6hlcc33j7u_fac.zip".
I unzipped the FW, and used the Youtube Guide https://youtu.be/aJa7ak5s3ts on what steps to do.
- Rebooted phone using "home+volumeDOWN+power" then volumeUP at the prompt.
- Connected the phone to my laptop, Odon Lit up blue under ID:COM
- Placed the following files into ODIN:
- BL: BL_G930VVRU4CRE5_CL13527029_QB18290739_REV02_user_low_ship_MULTI_CERT.tar.md5
- AP: AP_G930VVRU4CRE5_CL13527029_QB18290739_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
- CP: CP_G930VVRU4CRE5_CP9774707_CL13527029_QB18290739_REV02_user_low_ship_MULTI_CERT.tar.md5
- CSC: HOME_CSC_VZW_G930VVZW4CRE5_CL13527029_QB18290739_REV02_user_low_ship_MULTI_CERT.tar.md5
I then selected "Start"
After everything ran, Odin lit up green with "PASS!" but my phone still shows version 7.0, and im out of ideas. Could anyone please help me out on what im doing wrong or what I can do to try going forward? Here is the log output from Odin:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/006> 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..
<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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> emmc_appsboot.mbn.lz4
<ID:0/006> lksecapp.mbn.lz4
<ID:0/006> xbl.elf.lz4
<ID:0/006> tz.mbn.lz4
<ID:0/006> hyp.mbn.lz4
<ID:0/006> devcfg.mbn.lz4
<ID:0/006> pmic.elf.lz4
<ID:0/006> rpm.mbn.lz4
<ID:0/006> cmnlib.mbn.lz4
<ID:0/006> keymaster.mbn.lz4
<ID:0/006> apdp.mbn.lz4
<ID:0/006> msadp.mbn.lz4
<ID:0/006> cmnlib64.mbn.lz4
<ID:0/006> sec.dat.lz4
<ID:0/006> NON-HLOS.bin.lz4
<ID:0/006> boot.img.lz4
<ID:0/006> recovery.img.lz4
<ID:0/006> system.img.ext4.lz4
<ID:0/006> persist.img.ext4.lz4
<ID:0/006> modem.bin.lz4
<ID:0/006> adspso.bin.lz4
<ID:0/006> cache.img.ext4.lz4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
Thank You,
Jess
UPDATE: I was pointed to Samsung Smart Switch, which apparently is the successor to Samsung Kies. After installing Smart Switch it notified me an upgrade was available for my phone. I ran the upgrade and finally we have Android 8.0!
UPDATE: I was pointed to the Verizon Wireless Software Upgrade Assistant https://www.verizonwireless.com/support/samsung-update-upgrade-assistant/
I ran the program, and it stated "RG2 is ready to install". I allowed the software to run, during which my phone rebooted to the "download" screen. After another reboot the application stated my phone was upgraded, but I still show 7.0 and when I connected my phone again it gave the same "RG2 is ready to install". Just to be safe I let it run again, but no change.
I would really appreciate any assistance or input anyone could provide.
Thank You,
Jess
UPDATE2: I was pointed to Samsung Smart Switch, which apparently is the successor to Samsung Kies. After installing Smart Switch it notified me an upgrade was available for my phone. I ran the upgrade and finally we have Android 8.0! Some of my apps aren't happy with 8.0 so im going to master reset but, finally ive gotten it upgraded!
Thanks!
Jess
Related
Hello,
I tried to do a CF-Auto root and as it was going through the process my phone fell and unhooked the USB cable. Now, the phone is stuck on "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Does anyone know how to get out of this screen or is my phone completely dead?
PLEASE HELP:crying:
titans20 said:
Hello,
I tried to do a CF-Auto root and as it was going through the process my phone fell and unhooked the USB cable. Now, the phone is stuck on "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Does anyone know how to get out of this screen or is my phone completely dead?
PLEASE HELP:crying:
Click to expand...
Click to collapse
Okay, so I just kept trying to get back into the download mode and it eventually worked. However, I am still stuck....Odin failed because "There is no PIT partition"....does anyone know how to fix this?
THANKS!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
titans20 said:
Okay, so I just kept trying to get back into the download mode and it eventually worked. However, I am still stuck....Odin failed because "There is no PIT partition"....does anyone know how to fix this?
THANKS!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I was able to fix the problem. If anyone gets this problem, you need to make sure you are using the stock USB cable. If you use any other brand, it will not work. Hope this helps!
im also having the same issue.
im stuck with cache.img.. anyone can help please..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> recovery.img
<ID:0/017> NAND Write Start!!
<ID:0/017> cache.img.ext4
Make sure connection on com4 when USB conn.
Sent from my SPH-L720 using xda app-developers app
adhuto said:
im also having the same issue.
im stuck with cache.img.. anyone can help please..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> recovery.img
<ID:0/017> NAND Write Start!!
<ID:0/017> cache.img.ext4
Click to expand...
Click to collapse
Check over here. Also make sure you run CF-Autoroot 'As adminstrator'. Also it doen't matter what COM port as long as it shows up.
Either I was being a brickhead or the phone decided to change species (into an expensive brick of course).
Ok, I have a S4 originally from ATT which has been unlocked (which is used for Tmobile). One day I was messing with it and suddenly it powered off on me and from that point on I was never able to get past the ATT logo screen. The phone has been bricked.
After consulting Google. I've found Odin.... ONLY to see this error.
"<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)"
Ok someone please help.
What you flashed before for have a NAND WRITE error?
I'm so hopeless
Joku1981 said:
What you flashed before for have a NAND WRITE error?
Click to expand...
Click to collapse
Nothing? (I'm sorry, no clue what you are saying)
Rarwkitty said:
Nothing? (I'm sorry, no clue what you are saying)
Click to expand...
Click to collapse
Try flash with Odin 3.09, other USB port or other pc :highfive:
Hello,
I have a GT-I9505 which was under 4.3
I did the update OTA 4.4.2 and redemarage bootloop
impossible to get to recovery I left a red message at the top: moviNAND Checksum Confirmation Fail
I try to flash via odin with the latest firmware 4.4.2 XEF and here the result:
Enter CS for MD5 ..
Check MD5 .. Do not unplug the cable ..
Please wait ..
I9505XXUFNC4_I9505OXXFNC3_I9505XXUFNC4_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully ..
Leave CS ..
Added!
Odin v.3 engine (ID: 5) ..
File analysis ..
SetupConnection ..
Initialzation ..
Get PIT for mapping ..
There is no PIT partition.
All threads completed. (succeed 0 / failed 1)
Do you have any ideas?
Download and unzip this file: HERE and flash it like in the pic attached (+ the stock firmware u downloaded). Reboot manually then.
OTA update samsung missed
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC4_I9505OXXFNC3_I9505XXUFNC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the result
chtiti said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC4_I9505OXXFNC3_I9505XXUFNC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the result
Click to expand...
Click to collapse
if you use single tar file do not check re-partition option
open odin use default auto-reboot and F.reset time only
OTA update samsung missed
Hello,
same result.
Run as administrator (Right click on the icon)
Use Odin 3.07
If that doesn't work then download a 4.3 file and flash that onto the device.
OTA update samsung missed
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
OTA update samsung missed
Do you think the JTAG can solve my problem?
Did you try basic stuff like:
A different usb cable
A different usb port
A different pc?
You are not running Odin on a virtual machine are you?
Did you try redownloading the firmware? Did you try other firmwares?
OTA update samsung missed
I tried everything! Nothing works!
Did you try flashing a custom recovery and then try to flash a custom rom from there?
OTA update samsung missed
re,
How do I flash a custom rom without access to recovery?
OTA update samsung missed
The S4 has gone on a JTAG date.
Told you please uncheck re-partition option...you use single file
Sent from my GT-I9500
chtiti said:
re,
How do I flash a custom rom without access to recovery?
Click to expand...
Click to collapse
Can't you reflash the recovery?
I currntly have a samsung galaxy s5 sm-g900i. And want to root it. I have followed the guides on these forums using odin and the appropriate md5 file. I have installed kies After rebooting my phone into download mode, connect to odin 3.07 and attempting to start it and get the following error.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltedv-smg900i.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
This all started when I tried to flash Clockwork recovery on my stock G900F. I used Odin to successfully load the recovery, but as soon as it booted it would get stuck at "Set warranty bit: recovery" and restart itself into the ROM. So then I tried TWRP and Philz Touch and got the same thing. Then I tried to flash CF-Auto Root to see if I could use root permissions to restart into recovery via the CWM app, but that too gave me the same error. I tried both with and without Auto-Reboot on to see if maybe the stock ROM was overwriting the recovery but that didn't fix it either. This entire time USB debugging was enabled so that's not it.
Since the point of me doing this was to install CM 14.1 anyways, I decided to try flashing a stock ROM. I tried a whole bunch of different rips and none of them worked. The ones that were compressed into .tar would give the following error in Odin:
Code:
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The one that was broken into four separate files gives this error:
Code:
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
For both types of rips I had both Auto-Boot and F. Reset Time on. I did once attempt to use the .pit file provided with the latter rip and attempt to re-format, but that didn't do anything except prevent my stock ROM from booting (it's now stuck at the Samsung logo). I can still boot into download mode.
What are my options from here? I'm a little disheartened that my stock phone was unable to load any of the recovery tools that I tried, but maybe I'm missing something.
I tried using the firmware linked in this thread. I tried flashing with both T-flash and repartition as well as just T-flash and it doesn't work.
I get about halfway through the download before it fails. This is the output from Odin:
Code:
<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..
<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/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> T Flash...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> userdata.img.ext4
<ID:0/004> FAIL! (Erase)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can still boot into download mode and successfully flash any recovery I try, but I also still can't boot into recovery. Any help is greatly appreciated.
Turns out this was as simple as not having the version of the phone I thought I had.
Amazon told me it was a G900F when I bought it. The box says G900F. The sticker beneath the battery says G900F. The phone itself says G9006V.
When I searched to see if this has happened to anyone else, I saw more than a few confused and frustrated people learning this same thing the hard way as I did.
The lesson here is to trust what you see in download mode and disregard everything else. It's a bit slimy, but that's the world we live in.