Gear S2 Firmwares R720 and R732 - Samsung Gear S2

I got these 2 firmware for the gear.
R720XXU2EQH1
R732XXU2EQH1
https://drive.google.com/open?id=0B0M3TYEwiP9wSGhPZEdneTJvRjg
https://drive.google.com/open?id=0B0M3TYEwiP9weHNlUXNjaGxxdHc
I hope I have contributed

:good:
This sounds great. Thank you very much.
Need time for downloading... my Internet is very slow at the moment...
Please, maybe my mistake.... but I can see only AP file...
Maybe the other 2 parts are missing?
BL and CSC?
Code:
BL_R732XXU2EQH1_usr.tar
CSC_OXA_R732OXA2EQH1_usr.tar
Best Regards

The name of the zip is bad. but I assure you are all 3 files
CSC_OXA_R720OXA2EQH1_usr.tar
BL_R720XXU2EQH1_usr.tar
AP_R720XXU2EQH1_usr.tar
and
AP_R732XXU2EQH1_usr.tar
BL_R732XXU2EQH1_usr.tar
CSC_OXA_R732OXA2EQH1_usr.tar
adfree said:
:good:
This sounds great. Thank you very much.
Need time for downloading... my Internet is very slow at the moment...
Please, maybe my mistake.... but I can see only AP file...
Maybe the other 2 parts are missing?
BL and CSC?
Code:
BL_R732XXU2EQH1_usr.tar
CSC_OXA_R732OXA2EQH1_usr.tar
Best Regards
Click to expand...
Click to collapse

Thank you very much.
I have successfully downloaded both RAR files and after decompress I can see all 3 parts...
AP, BL and CSC. :good:
My fault.
Best Regards

Does this firmware support Samsung Pay?

Does this firmware support Samsung Pay?
Click to expand...
Click to collapse
Samsung Pay (Tizen Version) is inside EQH1 Firmware...
You can check by simple unpack/extract with Tool:
Code:
7zip
Check rootfs.img... you will find:
Code:
com.samsung.samsung-pay-app.tpk
But this is not what you want nor need... Samsung enable and DISABLE this app by selected CSC/Sales Code and few other Knox related Security crap...
Look at this Video... 1 way could be this... to force Spay...
https://forum.xda-developers.com/showpost.php?p=73982855&postcount=213
WARNING! This could create dangerous sideeffects...
I have only Retail Mode app from Gear S3...
This creates on my SM-R732 harder problems... CSA related...
Other attempt is CSC change...
BUT... Spay is security chain....
Maybe also handset part... like Spay Plugin or CSC of handset is mandatory...
Only as info...
Best Regards

I'm not able to flash this new firmware into my Gear S2. The beginning of the whole process always goes right, but at the end it always writes an error. And the result is always the same, which can be seen in the picture below.

@pRo_lama
You managed your problem?
If not:
1.
You have SM-R720 or SM-R720XXX...
Check in Download Mode if you see SM-R720 or SM-R720X
Other checkpoints... look at Rear Case... Back Cover... back side for:
Live Demo Unit... Not For Sale
2.
The beginning of the whole process always goes right, but at the end it always writes an error.
Click to expand...
Click to collapse
Copy & Paste Odin output... Example:
Code:
<ID:0/001> 192.168.49.1
<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/001> Odin engine v(ID:1.0000)..
<ID:0/001> File analysis..
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation..
<ID:0/001> Set PIT file..
<ID:0/001> DO NOT TURN OFF TARGET!!
<ID:0/001> Get PIT for mapping..
<ID:0/001> Get PIT Transmission
<ID:0/001> Firmware update start..
<ID:0/001> SingleDownload.
<ID:0/001> sboot.bin
<ID:0/001> NAND Write Start!!
<ID:0/001> param.bin
<ID:0/001> zImage
<ID:0/001> zImage-recovery
<ID:0/001> modules.img
<ID:0/001> rootfs.img
<ID:0/001> system-data.img
<ID:0/001> user.img
<ID:0/001> ramdisk-recovery.img
<ID:0/001> csc.img
<ID:0/001> ramdisk.img
<ID:0/001> RQT_CLOSE !!
<ID:0/001> RES OK !!
<ID:0/001> Remain Port .... 0
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)
3.
Follow if I see some feedback from you...
Best Regards

I flashed older FW and then the smartwatches booted. I have SM-R720. What is the difference between R720 and R720X ?

in my case. I use them for live demo. and I had no problems.

What is the difference between R720 and R720X ?
Click to expand...
Click to collapse
The X...
X means Live Demo Unit... NOT FOR SALE
Demo Devices for Store...
If you are sure you have SM-R720...
Then check Odin Output as I told...
Or if your solution work and you are lucky. Then you can use official way with over the Air... depend on your CSC if you reach EQH1...
Btw... Which Version you flashed successfully? Maybe helpfull for other users too...
Best Regards

I'd love to upload a log, but I do not have it, because I try it last week and I immediately flashed R720XXU2AOJ3 (http://www.mediafire.com/download/zhultaz1dz3brlc/R720XXU2AOJ3_Gear_s2_sport.rar)
Right now I have R720XXU2EQC1.

EQC1 is, because Samsung "branded" device with CSC... Sales Code...
Not every country can download over the Air...
But EQH1 could run on more CSC...
If maybe for next attempts... here is BOKK for SM-R720:
https://forum.xda-developers.com/showpost.php?p=73948041&postcount=178
And here are few Links and my overview for SM-R732:
https://forum.xda-developers.com/showpost.php?p=72225177&postcount=137
Only as info.
Best Regards

i have a somewhat similar problem with a gear s2 classic...
i can get into download mode, i cant get into wireless download, recovery, or factory command, also cant boot... sits at gear s2 logo for a minute or 2... then goes to a snowy screen like post 7
also, 2 of the solder pads are borken but ive managed to be able to still connect in a very delicate manner..
everytime i try to flash in odin, it gets past the set download mode and such and then gets stuck right at writing param.bin... and sits there FOREVER.... doing nothing..
i know its connected properly as it shows up in device manager properly, and in odin,..
but it seems like the nand is messed up permanently

2 of the solder pads are borken but ive managed to be able to still connect in a very delicate manner..
Click to expand...
Click to collapse
:good:
Thanx for this info.
This gives me hope, as I have killed 1 pad...
Checklist for you.
1.
I saw 1 device on Ebay...
Anyway.
Check Download Mode screen for Model name/Product Name...
You see?
SM-R732 or SM-R732X
2.
Same screen shows more infos... like Reactivation Lock on...
RL is on or off?
Perfect and easier for me... if you can post Picture... to see all infos from Screen. :good:
3.
If you need Combination Firmware... then you can PM me.
Best Regards

so here is all the info from the bootloader screen
SM-R732
K: Official, P: Official
R/L: OFF, S/D:1, W/V:0, R/P:B2
i should have attached a pic too for reference

@tnap1979
Output on Screen looks good...
No Reactivation Lock :good:
Also the other infos with official offical looks good...
Screen is from normal Bootloader sboot.bin not from Combination Firmware... otherwise it looks different.
1.
Your Odin Version?
I have used successfully 3.12.3 for instance from here:
https://forum.xda-developers.com/showthread.php?t=2711451
2.
Suggestion... try BOKK Version... click through links here to find it:
https://forum.xda-developers.com/showpost.php?p=72225177&postcount=137
3.
Try package by package... for instance:
Code:
CSC_R732OXA2BOKK_usr.tar.md5
Select only 1 file in Odin...
Check if success...
Then next round if success... proceed with:
Code:
AP_R732XXU2BOKK_usr.tar.md5
Last round BL...
Best Regards

Hi all,
Just update a Gear S2 in France.
Got release R732XXU2EQJ2.
I'm unable to find info about this one .... Any inputs ?
Thx

Code:
R732XXU2EQJ2
Thanx for info.
I can not find changelog... like this:
http://doc.samsungmobile.com/SM-R732/CHC/doc.html
No idea what is inside the 23 MB FOTA package...
Seems for now only for XEF Sales Code... aka France.
Also US XAR is still on BQH1...
Best Regards

Tizen 3.0 now rolling out to the Gear S3 with Value Pack update.
It looks like Gear S2 does not get this update.

Related

[Help] I soft bricked my phone, i am desperate.

I am so lost as to what to do next, i really need guidance.
I am offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work ASAP.
So i was attempting to root my phone [GALAXY S6 - SM-G920F]
Got the file from: https://autoroot.chainfire.eu/ which should've matched my Phone.
First attempt failed, got back into my phone everything is fine. Tried the same thing again, failed this time i get this message:
An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." The logs for the times it has failed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Tried connecting with Kies and Smart switch, none can find the device just keeps buffering and for smart switch it just say it's not supported. I am able to get into downloading mode, but that's it.
Got newest Kies, odin 3 v.10.7.exe however on my first go i noticed i had odin3 v.10.6 but now i got the latest i believe. After reading around i decided to try to fix it back to normal, so i downloaded my countries [sweden] firmware this one: http://www.sammobile.com/firmwares/confirm/57869/G920FXXU3COI9_G920FVDS3COI6_VDS/
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004>
<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!!
And now i am here, i am truely nervous that i wont be able to get it to work.
Please Xda your my only hope. All i wanted was to free up space on my phone.. That's it.. :crying:
Ps. Worth mentioning, sometimes my usb is not recongnized and it flickers on and off (connectiong) but seems
to be fine most of the times and during the odin trials.
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
I just begain with youtubing easy way to root and i just said download odin, get the right firmware plug in an click odin.
That has failed and it's bricked, however i have tried to get my countries firmware, it didint work and produced my last log that i posted.
I am downloading another one there is two for Sweden however the other one says Sweden tre which is an operator over here and not one that i use so i doubt that will work?
i will attempt to download it but it takes 3h due to the limited speed at sammmobile.
So summarize, the sweden firmware from sammobile failed ;_;
What i do is, put phone in download mode, open odin, get the AP [Sweden from sammomobile] it finds it and press start, quickly after it says failed and i am back to square one.
I was reading the link you gave me about the pit files, it appears the error could be related to me having the wrong firmware?
I am seriously offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work.
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
blud7 said:
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
Click to expand...
Click to collapse
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
If you were on 5.1.1, then get 5.1.1
You can try the file you dl before. Just uninstall Kies before using Odin.
WaDoDem said:
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
Click to expand...
Click to collapse
You dont need to download another rom dude...the problem is your usb dont get recognized and after a while it will disconnect...it happened to me aswell...searched on youtube did an easy fix and then i flashed stock rom with odin and joined marshmallow beta...
Tldr: search on youtube a fix for usb not recognized...i dont have a link sorry you have to search it by yourself its an easy fix..
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
anthonyrv03 said:
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
Click to expand...
Click to collapse
You're fine with either.
@WaDoDem
First of all, calm down. Believe me it's harder than you think to brick S6 in a not fixable way
If Odin doesn't flash official roms or you just cant suffer a slow a** download speed from SamMobile :
1. Press and hold all of 4 buttons on your device. (Volume up + Volume Down + Home + Power) your device will reboot.
2. As soon as device reboots release volume up and hold other 3 three. (Power + Home + Volume Down). Your device should boot into downloading mode.
3. Download this :
https://dl.twrp.me/zeroflte/twrp-2.8.7.2-zeroflte.img.tar.html
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes, hold Power+Home + Volume Up. Now your device will boot into TWRP recovery.
5. Wait for drivers to be installed. Your pc should show phone's internal storage as connected device. If not, go to TWRP Mount section and enable MTP mode. (Or if it's enabled, disable and re enable it )
6. Download this rom :
http://forum.xda-developers.com/gal...rom-2013266107-arrow-rom-v1-0-0-fast-t3212318
And this kernel:
http://forum.xda-developers.com/gal...nified-development/kernel-vindicator-t3156281
Then put them on your phone.
7. Wipe system,data,cache and dalvik cache from twrp.
8. Install Arrow Rom first and then flash Vindicator Kernel.
9.Reboot, first boot can take up to 15 minutes
10.Continue celebrating new year [emoji14]
Sent from my SM-G920I using Tapatalk
sometimes if odin not working i restart my computer and put my mobile in downloadmode again and than i try again,most of the time it worked.....
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes said:
Odin cant find the tar file.
I got odin 3V3.10.7 in options auto reboot and f. reset time are all bocked in is that right?
On files to download i am able to do, ap,cp,csc,bl neither of those help to find the recovery image that i am supposed to start?
Click to expand...
Click to collapse
Damientju said:
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
Click to expand...
Click to collapse
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
WaDoDem said:
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
Click to expand...
Click to collapse
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Damientju said:
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Click to expand...
Click to collapse
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
WaDoDem said:
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
Click to expand...
Click to collapse
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
[email protected] said:
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
Click to expand...
Click to collapse
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<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!!
yes
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
WaDoDem said:
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<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!!
Click to expand...
Click to collapse
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
sd_N said:
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
Click to expand...
Click to collapse
I just downloaded and tried the pit that above user posted.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
It's a Galaxy s6 32GB.

Boot loop - verity verification failed

I have tried to installed marshmallow via Odin on my galaxy s6 SM-920F. It's not the first time I'm flashing a device but this time reactivation lock was on and Odin would not finish. Restarting the phone is not possible as its stuck in a bootloop and shows blinking "Galaxy S6" every time and recovery mode says verity verification failed. Didn't not know reactivation would do so much damage as I thought it would just ask a password in case a thief tries to flash the phone.
I searched everywhere but could not find a solution and hope to get some expert advice here. Please help
Get the phone into Download mode and flash the ROM again?
Flashing again won't help because of reactivation lock and there is no way I know I can disable that without entering the phone itself.
Eek. Tried flashing the original firmware you were running prior to trying to upgrade and doing a factory reset?
Might let you log back in and disable the lock.
Sent from my SM-G920I using Tapatalk
Already tried reset or reinstalling current version. The lock won't let it happen. Upon restart the phone is stuck in a loop.
heetesh22 said:
Flashing again won't help because of reactivation lock and there is no way I know I can disable that without entering the phone itself.
Click to expand...
Click to collapse
Reactivation Lock prevents only custom (not Signatured by Samsung) images to flash. So, you should able to flash stock ROM.
Did you try SmartSwitch?
heetesh22 said:
I have tried to installed marshmallow via Odin on my galaxy s6 SM-920F. It's not the first time I'm flashing a device but this time reactivation lock was on and Odin would not finish. Restarting the phone is not possible as its stuck in a bootloop and shows blinking "Galaxy S6" every time and recovery mode says verity verification failed. Didn't not know reactivation would do so much damage as I thought it would just ask a password in case a thief tries to flash the phone.
I searched everywhere but could not find a solution and hope to get some expert advice here. Please help
Click to expand...
Click to collapse
Download the stock firmware from sammobile.com
Unzip the file then open the tar archive with 7-zip or winrar. Extract the system.img and boot.img from it.
Download and unzip this software:
https://www.dropbox.com/s/bsreazoonsw4gwv/tar-Tool_Odin3-v3.07_by_mkh.mourad.zip?dl=0
Copy/paste the system.img and boot.img into the software directory and run the batch file. It will spit out a system.tar.md5 and boot.tar.md5 file
Flash the system.tar.md5 as AP with Odin then flash the boot.tar.md5 as AP with Odin
I recommend Odin 3.10.6:
https://www.dropbox.com/s/1dlmxtc0ic7u7ew/Odin3_v3.10.6.zip?dl=0
IMEIRescue said:
Download the stock firmware from sammobile.com
Unzip the file then open the tar archive with 7-zip or winrar. Extract the system.img and boot.img from it.
Download and unzip this software:
https://www.dropbox.com/s/bsreazoonsw4gwv/tar-Tool_Odin3-v3.07_by_mkh.mourad.zip?dl=0
Copy/paste the system.img and boot.img into the software directory and run the batch file. It will spit out a system.tar.md5 and boot.tar.md5 file
Flash the system.tar.md5 as AP with Odin then flash the boot.tar.md5 as AP with Odin
I recommend Odin 3.10.6:
https://www.dropbox.com/s/1dlmxtc0ic7u7ew/Odin3_v3.10.6.zip?dl=0
Click to expand...
Click to collapse
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
heetesh22 said:
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
Click to expand...
Click to collapse
Try Samsung Smart Switch. It might help.
Bang in your serial number and it goes automatically.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Try Samsung Smart Switch. It might help.
Bang in your serial number and it goes automatically.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
what should be done exactly using smart switch? and in what mode should the phone be connected as I tried and it doesnt detect the phone.
heetesh22 said:
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
Click to expand...
Click to collapse
No it will not remove the reactivation lock. If the phone is yours then once you get it to boot you should know the account login information to bypass the Samsung or Google lock.
I would just download the most current firmware for the phones original country/carrier.
heetesh22 said:
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
Click to expand...
Click to collapse
Im not sure I understood how to extract system.img and boot.img from the tar file. I have G920FXXU3COI9.tar.md5. How do I do that?
heetesh22 said:
Im not sure I understood how to extract system.img and boot.img from the tar file. I have G920FXXU3COI9.tar.md5. How do I do that?
Click to expand...
Click to collapse
Open the tar archive with 7-zip or winrar then select the files you want an extract them
IMEIRescue said:
Download the stock firmware from sammobile.com
Unzip the file then open the tar archive with 7-zip or winrar. Extract the system.img and boot.img from it.
Download and unzip this software:
https://www.dropbox.com/s/bsreazoonsw4gwv/tar-Tool_Odin3-v3.07_by_mkh.mourad.zip?dl=0
Copy/paste the system.img and boot.img into the software directory and run the batch file. It will spit out a system.tar.md5 and boot.tar.md5 file
Flash the system.tar.md5 as AP with Odin then flash the boot.tar.md5 as AP with Odin
I recommend Odin 3.10.6:
https://www.dropbox.com/s/1dlmxtc0ic7u7ew/Odin3_v3.10.6.zip?dl=0
Click to expand...
Click to collapse
I did that and when flashing the system.tar, its gets stuck on NAND Write Start. Help IMEIRescue
heetesh22 said:
I did that and when flashing the system.tar, its gets stuck on NAND Write Start. Help IMEIRescue
Click to expand...
Click to collapse
Download this teamviewer module and give me the ID and password
http://download.teamviewer.com/download/TeamViewerQS_en.exe
IMEIRescue said:
Download this teamviewer module and give me the ID and password
http://download.teamviewer.com/download/TeamViewerQS_en.exe
Click to expand...
Click to collapse
Whatsl access does it give you?
heetesh22 said:
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
Click to expand...
Click to collapse
IMEI Rescure, I get this error with your method
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
heetesh22 said:
IMEI Rescure, I get this error with your method
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Update 1: I have been able to flash the phone with system and boot file. Now when starting the phone, it just displays the Samsung Galaxy S6 logo and stays like that. What to do next?
heetesh22 said:
Whatsl access does it give you?
Click to expand...
Click to collapse
It's a remote desktop program. I'll remote in and see if I can have any better luck.
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
heetesh22 said:
Update 1: I have been able to flash the phone with system and boot file. Now when starting the phone, it just displays the Samsung Galaxy S6 logo and stays like that. What to do next?
Click to expand...
Click to collapse
Hmm try this
Power off then hold volume up + home + power to get into recovery mode then do a factory reset > wipe cache > flash system.tar > flash boot.tar
IMEIRescue said:
It's a remote desktop program. I'll remote in and see if I can have any better luck.
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Hmm try this
Power off then hold volume up + home + power to get into recovery mode then do a factory reset > wipe cache > flash system.tar > flash boot.tar
Click to expand...
Click to collapse
For the time being, I can't enter recovery mode but only download mode. Any idea why?
When I charge the phone, only a grey battery logo with lightning appears but no indication that it is charging(green blinking dot at the bottom). Do you think the battery has been depleted completely?
And now it does not power on with the power button to show the samsung logo as it showed some time back, but I can still enter download mode. It's so confusing now. Wondering if a software issue is causing it not to charge as some hours back, it was fine.

I cant unroot my Galaxy S7 Verizon (SM-G930V)

I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Parteeajp said:
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Click to expand...
Click to collapse
Hi mate
Just flash a stock rom with odin on top of it
http://www.sammobile.com/firmwares/database/SM-G930V/
back up everything important before you do it ..just in case
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Hi
Yes you need to flash it with Odin
did you downloaded from sammobile?
if not try i from there , follow their instructions :
Extract (unzip) the firmware file
Download Odin v3.11.1
Extract Odin ZIP file
Open Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Usually sammobile has only one tar file ( unzip it just once) , back up you photos and files before just in case
Check this thread is not for your phone but the basics apply to all samsung phones
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Can you post a pic of the back of the phone showing the model number as SM-G930V and FCC ID. Then take a pic of the bootloader screen and show what what model number it has, if flash successfully it should be showing as SM-G930T. If proven true then it may seem that as the S7 is a Universal Hardware phone (QCOMM that is).
Please Help
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Benaiah1287 said:
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Click to expand...
Click to collapse
nitropowrd said:
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Click to expand...
Click to collapse
You need to use the prince comsey's modified odin that bypasses SHA verification.
Saga's End
aromerblz said:
You need to use the prince comsey's modified odin that bypasses SHA verification.
Click to expand...
Click to collapse
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
nitropowrd said:
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
Click to expand...
Click to collapse
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
nitropowrd said:
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
Click to expand...
Click to collapse
thanks a lot. I had 2 S7s. One I was able to flash with G930UUEU2APEH, but the other one couldn't...but I could with the one you posted ( SM-G930U_1_20160921124641_vvcrzx3ej5_fac)
Help please <ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<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> persist.img.ext4
<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> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
I am having the same problem. How do I know the version before trying and failing until I get one that works?
Couldn't the boot loader 'version' be changed/hacked within the (down graded) boot loader so the version check would pass?

Problems after rooting

Hello, I just bought S7 (second-hand) last week and wondering to root it out.
My question is, is there any laggy or issue or something that feels 'downgraded' after the root? Because I've seen many people complain about after their phones being rooted.
Thanks in advance!
isssaputra said:
Hello, I just bought S7 (second-hand) last week and wondering to root it out.
My question is, is there any laggy or issue or something that feels 'downgraded' after the root? Because I've seen many people complain about after their phones being rooted.
Thanks in advance!
Click to expand...
Click to collapse
If you trip Knox you won't be able to use Secure folder, Samsung Pay or Samsung Health and that's it.
You won't get any other problems.
Hi!
Yesterday I rooted my S7 (SM-G930F) with CF-Auto Root (from desktop.firmware.mobi)
Unfortunately, I didn't notice that the Kernel was 7.0, while my S7 was already on 8.0.
Now I have a lot of apps (including camera, youtube, lightning launcher, opera, ...) that either crash directly after starting or freeze shortly after they are opened.
Do you know if/how it is possible to get a working system again?
Thank you in advance (and forgive my bad english),
Andi
If you download 8.0 firmware files (either use samfirmtool, or go to sammobile.com or updato.com) and flash using Odin, use AP, BL, CP and HOME_CSC instead of normal CSC (HOME_CSC keeps data, normal CSC wipes data), it should set your kernel and everything back to 8.0 without causing any data loss.
Flash guide here https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
However I'm pretty sure doing this will reset your root, your best bet is to flash TWRP and root using Magisk as its the more modern and updated root method.
Hi @Beanvee7,
thanks for your info!
In the meantime, I have installed TWRP, and downloaded the firmware from sammobile, but failed with magisk (since it is one of the apps that keep on crashing right after startup).
So, I'll have to install it the old fashioned way with odin tomorrow.
But I have one more question left: Is there an advantage of using CSC vs. HOME_CSC? Since I have backups of all my data, and rooting wiped data anyways (the system was encrypted), a wipe does not inflict any (addiditional) damage.
Thanks,
Andi
CSC is probably preferred because it means a clean wipe, so you won't be carrying across any potentially broken apps/system files.
If you have backups then I'd recommend CSC.
Hi!
I am still stuck: No matter what type of installation I choose, it fails:
Odin reports success, but doesn't install the new firmware (neither 7.0 nor 8.0, from updato or sammobile).
<ID:0/006> modem_debug.bin
<ID:0/006> cache.img.lz4
<ID:0/006> hidden.img.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> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<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/004> Added!!
<ID:0/004> Removed!!
Click to expand...
Click to collapse
The "Now Writing.. Please wait about 2 minutes"-part only takes one second or so.
Installing via TWRP reports "Invalid zip file format".
ROM Toolbox Pro also reports "Invalid ZIP file"
Magisk still crashes upon startup.
Do you have any ideas left?

Samsung Gear S2 Classic is Stuck On Update Loop

I've flashed the R732XXU2AOJ3 firmware form this link https://forum.xda-developers.com/smartwatch/gear-s2/tutorial-downgrade-gear-s2-sport-t3334123 using Odin v3.13.1 and the USB method because the WiFi option in the bootloader was damaged. The watch started properly and I could connect to it with my phone and the damaged connection with the WiFi option in the bootloader was fixed as well.
The Samsung phone app suggested an update (I don't remember the version). After going through the update process the watch has restarted itself and performed the 0 to 100% update step. After reaching the 100% it just shuts down, every time I turn it on it goes again through the update process
{
"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"
}
and shuts down.
Using the normal bootloader factory reset doesn't work and the phone it stuck on the boot logo when using that. Now even if I flash the R732XXU2AOJ3, R732XXU2AOJ4 or the R732XXU2EQH1 firmware successfully using NetOdin3 I’m still stuck on the update process as shown here . I've tried flashing using the AP, BL and CSC files and also using AP, BL, CSC and PIT files, the watch was always updated with its official stock firmware.
Those are my set NetOdin3 options for the flash:
And this is the flash log:
Code:
<ID:0/001> 192.168.49.1
<ID:0/001> Odin engine v(ID:1.0000)..
<ID:0/001> File analysis..
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation..
<ID:0/001> Set PIT file..
<ID:0/001> DO NOT TURN OFF TARGET!!
<ID:0/001> Get PIT for mapping..
<ID:0/001> Get PIT Transmission
<ID:0/001> Firmware update start..
<ID:0/001> SingleDownload.
<ID:0/001> zImage-recovery
<ID:0/001> NAND Write Start!!
<ID:0/001> sboot.bin
<ID:0/001> param.bin
<ID:0/001> zImage
<ID:0/001> modules.img
<ID:0/001> user.img
<ID:0/001> system-data.img
<ID:0/001> ramdisk-recovery.img
<ID:0/001> ramdisk.img
<ID:0/001> rootfs.img
<ID:0/001> csc.img
<ID:0/001> RQT_CLOSE !!
<ID:0/001> RES OK !!
<ID:0/001> Remain Port .... 0
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)
Idea 1...
Flash Combination Firmware... to check if SM-R732 boot
Idea 2...
No idea why you started with Odin... so my first idea is... Live Demo Unit ?
SM-R732X
Idea 3.
Few threads about dead devices...
Still no idea why you flashed with Odin
Idea 4...
If you have enough time... I could help you to dump Log files from device...
Maybe this answer why fail...
Best Regards
Edit 1...
By mistake saw your tiny Pic... clicked weired around...
Those are my set NetOdin3 options for the flash
Click to expand...
Click to collapse
Re-partition
No idea if this is good idea...
So I really suggest you to flash Combination Firmware...
Hint... Be carefully not to use LDU Firmware... with 1 more X in Filename...
R732XX :good:
R732XXX :cyclops:
Best Regards
adfree said:
Idea 1...
Flash Combination Firmware... to check if SM-R732 boot
Idea 2...
No idea why you started with Odin... so my first idea is... Live Demo Unit ?
SM-R732X
Idea 3.
Few threads about dead devices...
Still no idea why you flashed with Odin
Idea 4...
If you have enough time... I could help you to dump Log files from device...
Maybe this answer why fail...
Best Regards
Edit 1...
By mistake saw your tiny Pic... clicked weired around...
Re-partition
No idea if this is good idea...
So I really suggest you to flash Combination Firmware...
Hint... Be carefully not to use LDU Firmware... with 1 more X in Filename...
R732XX :good:
R732XXX :cyclops:
Best Regards
Click to expand...
Click to collapse
Thank you for the response I thought the post will never get any attention. I flashed with Odin the first time because the device was stuck on the logo and I couldn’t rest it. After the first flash using the R732XXU2AOJ3 I could start the watch and use it normally. The problem occurred after I tried to install an official update though the Galaxy Wearable app. I don’t know if I can get any logs from the watch since the debugging is not enabled so a connection with sdb is not an option, I can ping the local IP addres of the watch with CMD .
Do you know any working free links to some Combination Firmware for the SM-R732? The model says SM-R732 so I don't think that it is a live demo unit. I have the R732XXU2AOJ3, R732XXU2AOJ4, R732XXU2AOJD, R732XXU2EQC1 and R732XXU2EQH1 and I thought that they all were Combination Firmware.
Update 1:
I've flashed this Combination Firmware COMBINATION-FTMA_R732XXU2AOJ2.tar.md5 successfully. The watch started with the problematic 0-100% update process on boot and shut down after reaching 100%.
Is there any difference between flashing with Odin and USB and flashing with NetOdin and Wi-Fi?
Is there any difference between flashing with Odin and USB and flashing with NetOdin and Wi-Fi?
Click to expand...
Click to collapse
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards
adfree said:
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards
Click to expand...
Click to collapse
Yes, I've found the FRC1 Firmware, I didn't know it was the "latest". If you want it I can upload it and give you a download link in a PM.
Best regards
adfree said:
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards
Click to expand...
Click to collapse
It is wired. When I flash with NetOdin then the flash succeeds but when I use ODIN + USB then it fails with:
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..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 908 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Re-Partition setting is not set and I understood that it is not supposed to be set. In both cases of NetOdin and Odin + USB I've used the COMBINATION-FTMA_R732XXU2AOJ2.tar.md5
Remove partition.pit from TAR... repack...
1 way is with 7Zip tool to create valid TAR file...
In case of 3 file crap... AP BL CSC bla bla crap...
partition is inside CSC file...
In normal working Gear no PIT file necessary...
Best Regards
adfree said:
Remove partition.pit from TAR... repack...
1 way is with 7Zip tool to create valid TAR file...
In case of 3 file crap... AP BL CSC bla bla crap...
partition is inside CSC file...
In normal working Gear no PIT file necessary...
Best Regards
Click to expand...
Click to collapse
I ended up removing all the files causing the fail message until I was left with no files at all .
A
Odin Version?
B
Try to flash only this param file...
Try both... Odin and netOdin...
Hope to enable Upload in Reboot menu... to use RDX Tool...
https://forum.xda-developers.com/showpost.php?p=72110199&postcount=45
Best Regards
Edit 1.
I mean menu like this:
Code:
[B]REBOOT MODE[/B]
Continue
[B]Upload[/B]
[B]Upload (wireless)[/B]
Download
Download (wireless)
Factory command
Recovery
PowerOff
adfree said:
A
Odin Version?
B
Try to flash only this param file...
Try both... Odin and netOdin...
Hope to enable Upload in Reboot menu... to use RDX Tool...
https://forum.xda-developers.com/showpost.php?p=72110199&postcount=45
Best Regards
Edit 1.
I mean menu like this:
Code:
[B]REBOOT MODE[/B]
Continue
[B]Upload[/B]
[B]Upload (wireless)[/B]
Download
Download (wireless)
Factory command
Recovery
PowerOff
Click to expand...
Click to collapse
A. Odin v3.13.1 and NetOdini v1.0
B. Odin shows fail and NetOdin shows success
The extended menu doesn't appear .
Best Regards
Maybe you are out of luck...
Look here:
https://forum.xda-developers.com/smartwatch/gear-s2/fail-to-hard-softreset-t3746359
https://forum.xda-developers.com/smartwatch/gear-s2/gear-s2-wont-perform-factory-reset-t3737448
It is not 100 % sure to me... if really eMMC damaged... (Hardware)... or some Security crap enabled... and write protect eMMC...
Sorry, I have no solution nor more ideas to try... :crying:
Best Regards

Categories

Resources