Hello, please I need help on this
Model: SM-G955 - MX Telcel
Update: I cannot reproduce the issue of the Kernel rev. I tried in another computer and the result continue SW Rev. CHECK FAIL (BOOTLOADER) DEVICE: 4 BINARY: 3
Having this issue:
Odin 3.13
<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/015> Odin engine v(ID:3.1301)..
<ID:0/015> File analysis..
<ID:0/015> Total Binary size: 5529 M
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> NAND Write Start!!
<ID:0/015> SingleDownload.
<ID:0/015> boot.img
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Steps to Reporduce
I was following this thread [GUIDE] How To Install TWRP & Root Galaxy S8 After Oreo Update breaking the device, and get a loop device with the legend of the OEM. After that, I follow this thread [ROM] [8.0] [OFFICIAL] [CRGB] [ODIN FLASHABLE] For Galaxy S8+ [G955F/FD] [08.09.2018]. Everything was ok, I received an OTA didn't remember the version and continue configuring until I install the Magisk.apk and restart the device, the device stays on OEM boot loop again, trying to reflash S8+ Official Oreo CRGB Firmware 07.09.2018 this version, comes the error SW rev. check to fail device 4 binary 3 related that I am trying to use an older version.
So I find 2 newer versions: SM-G955F_1_20180904043214_2afttpa4az_fac // SM-G955F_1_20180904010814_39o648ohci_fac. Try and now the error is the Kernel rev.
Hope you can help me with some guideline here.
Thank you!
hackerjj22 said:
Hello, please I need help on this
Model: SM-G955 - MX Telcel
Update: I cannot reproduce the issue of the Kernel rev. I tried in another computer and the result continue SW Rev. CHECK FAIL (BOOTLOADER) DEVICE: 4 BINARY: 3
Having this issue:
Odin 3.13
<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/015> Odin engine v(ID:3.1301)..
<ID:0/015> File analysis..
<ID:0/015> Total Binary size: 5529 M
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> NAND Write Start!!
<ID:0/015> SingleDownload.
<ID:0/015> boot.img
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Steps to Reporduce
I was following this thread [GUIDE] How To Install TWRP & Root Galaxy S8 After Oreo Update breaking the device, and get a loop device with the legend of the OEM. After that, I follow this thread [ROM] [8.0] [OFFICIAL] [CRGB] [ODIN FLASHABLE] For Galaxy S8+ [G955F/FD] [08.09.2018]. Everything was ok, I received an OTA didn't remember the version and continue configuring until I install the Magisk.apk and restart the device, the device stays on OEM boot loop again, trying to reflash S8+ Official Oreo CRGB Firmware 07.09.2018 this version, comes the error SW rev. check to fail device 4 binary 3 related that I am trying to use an older version.
So I find 2 newer versions: SM-G955F_1_20180904043214_2afttpa4az_fac // SM-G955F_1_20180904010814_39o648ohci_fac. Try and now the error is the Kernel rev.
Hope you can help me with some guideline here.
Thank you!
Click to expand...
Click to collapse
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
spawnlives said:
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
Click to expand...
Click to collapse
Thank you Spawnlives, you are right, I reflash this one: BL_G955FXXU4CRI5_CL14315050_QB19732162_REV00_user_low_ship.tar from Device 4, and everything is ok.
thanks so much my brother your tips working
:angel:
spawnlives said:
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
Click to expand...
Click to collapse
Hi, but what if Lineage OS is Android 10 (currently running) and Samsung / Sammobile doesnt offer a ROM with corresponding bootloader version? I want to go back to stock but it doens't work, right? Thanks!
spawnlives said:
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
Click to expand...
Click to collapse
Anyway to flash older firmware once the device has been updated?
Used to be absolutely fine on older devices, could rollback and flash any firmware you wanted.
ben.marks said:
Anyway to flash older firmware once the device has been updated?
Used to be absolutely fine on older devices, could rollback and flash any firmware you wanted.
Click to expand...
Click to collapse
No anti rollback prevents this thus this error
spawnlives said:
As you have already guessed you are trying to flash older firmware than what is on your phone. Device 4 = current bootloader version on phone.Binary 3 = bootloader your trying to flash.
Have a look through this and use samfirm to download latest firmware then flash with odin. Or download latest from sammobile and flash.
When looking at firmware names the 5th number from the right is the bootloader version number.You will need version 4 bootloader firmware.
https://www.xda-developers.com/download-stock-odin-firmware-samfirm/
Click to expand...
Click to collapse
you seem to know things brother how about a little help
so my running bootloader is G9550FXXSBDUA3 what binaries are used in case i want to load a combination file
p.s: i cant boot the device only runs download mode and bootmenu
Nima_shah said:
you seem to know things brother how about a little help
so my running bootloader is G9550FXXSBDUA3 what binaries are used in case i want to load a combination file
p.s: i cant boot the device only runs download mode and bootmenu
Click to expand...
Click to collapse
Bootloader version numbers,
A - bootloader version 10
B - bootloader version 11
C - bootloader version 12
And so on
You can check bootloader version in download mode.
Nima_shah said:
you seem to know things brother how about a little help
so my running bootloader is G9550FXXSBDUA3 what binaries are used in case i want to load a combination file
p.s: i cant boot the device only runs download mode and bootmenu
Click to expand...
Click to collapse
your best bet is to go to sammobile.com/firmwares and download the latest FW for your device and flash it with Odin. I bet itll boot right up barring any hardware issues
Related
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.
Hey,
today i tried to install a custom rom on my S6 (www youtube com/watch?v=ZFrvoNGoUn8) I did all steps in this Video, but with the first step there comes an error in Odin and on my phone
(started with: bl_old.tar.md5) :
In Odin it says:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sboot.bin
NAND Write Start!!
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
On my phone in download mode: Secure Check Fail: (BOOTLOADER)
What can i do? Its a s6 from vodafone. But i think it hasn't a branding. Only some apps from vodafone..
bl are bootloader are you sure you have used correct bootloader for ur model nimber ? in this video phone used are SM-G925F
if you have another model find corect bl file for ur phone and test agains
spawk said:
bl are bootloader are you sure you have used correct bootloader for ur model nimber ? in this video phone used are SM-G925F
if you have another model find corect bl file for ur phone and test agains
Click to expand...
Click to collapse
do you have any idea where i can find the correct one? :/
on XDA here an example for I920 http://forum.xda-developers.com/galaxy-s6/development/g920i-bootloader-modem-updated-10-10-t3221796
and i have juste taped Galaxy S6 bootloader on google and i have found this
https://www.androidfilehost.com/?w=files&flid=29573
all S6 and S6 edge BL are on androidfilehost thank to Edgarf28
and some another here
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
I have the SM-G920F with Android 6.0.1 and Basebandversion: G920FXXS3DPC2
In the video, he flashed first a bootloader, than twrp and than a bootloader again. Where can i find these 2 Bootloader except for my device?
I know how to use twrp and had root on old phons, but i dont have any idea, which bootloader is the rigt one :/
You don't need to flash the old bootloader anymore to flash TWRP.
Just flash this via Odin, and TWRP will be installed on your device;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
forumber2 said:
You don't need to flash the old bootloader anymore to flash TWRP.
Just flash this via Odin, and TWRP will be installed on your device;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
Click to expand...
Click to collapse
where to flash in odin? As AP?
m0tion said:
where to flash in odin? As AP?
Click to expand...
Click to collapse
Yes
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?
when( only official released binaries are allowed to be flashed ) come out ,i try to downloading and install the SM-950F Firmware,but the error always come out,the phone come out SW REV.CHECK FAIL(BOOTLOADR) DEVICE:11 ,BINARY: 1
and this is computer run out
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6042 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
any solution ?
by the way all lock is off
HansomeC said:
when( only official released binaries are allowed to be flashed ) come out ,i try to downloading and install the SM-950F Firmware,but the error always come out,the phone come out SW REV.CHECK FAIL(BOOTLOADR) DEVICE:11 ,BINARY: 1
and this is computer run out
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6042 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
any solution ?
by the way all lock is off
Click to expand...
Click to collapse
You are trying to flash a firmware that has an older binary version than what is already on the device. You can't do that, you have to flash a firmware that has the exact same binary as what is already on the device or you need to flash a firmware that has a newer binary.
In other words, you can not downgrade, you can only flash what you already have installed on the device or you can only flash an upgraded firmware, you can not go backwards.
If you are trying to downgrade your device in order to root the device, that is not going to work.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You are trying to flash a firmware that has an older binary version than what is already on the device. You can't do that, you have to flash a firmware that has the exact same binary as what is already on the device or you need to flash a firmware that has a newer binary.
In other words, you can not downgrade, you can only flash what you already have installed on the device or you can only flash an upgraded firmware, you can not go backwards.
If you are trying to downgrade your device in order to root the device, that is not going to work.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
ok understand,thank you solve my problem
HansomeC said:
ok understand,thank you solve my problem
Click to expand...
Click to collapse
Are you saying that you solved the problem or are you saying that you understand but still need help solving the problem?
Find the newest firmware available for your device, one that has a binary that is higher than what was on the device when the problem started.
Sent from my SM-S767VL using Tapatalk
I need some troubleshoot tinkering
I have received a Note 10.1 (GT-N8020) from a friend who would appreciate if I could salvage pictures and documents that was on this tablet, and let us not debate his backup options.
Problem with the tablet is it wont boot properly.
It just hangs on the Samsung animation.
As first troubleshoot step my thought was to boot into Recovery and wipe cache and dalvik, just to get it booting. But I simply cannot boot into Recovery. I can only get to ODIN mode.
After several attempts giving up on Recovery, my plan was to flash a new Recovery onto tablet by using ODIN mode, however all attempts both with several different version of ODIN and different version of TWRP fails to be flashed.
Code:
<ID:0/009> 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/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 6 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So here I am, feeling stuck.
Either I am thinking there is a defect with the NAND chip, why the tablet must have failed in first place, however I can also find some articles claiming some of Samsung's tablets does not have a Recovery mode/partition, is this true for this model?
I have not reflashed entire tablet, since I need access to whatever data there must be on the tablet.
I also found description on sammobile explaining how to re-install ROM while preserving apps and data, but they keep mentioning ROMs based on 5 files (AP, BL, CP, CSC, HOME_CSC), while I can only find ROMs based on single files (AP)
Link to article (see step 2)
https://www.sammobile.com/samsung/galaxy-note-101/firmware/GT-N8020/CNX/download/N8020XXUDOH1/55623/
Anyone know where I can download such ROM based on 5 files (Samsung official ROM)
Suggestions for any other methods I can try to get the data out of tablet?
Try Philz Recovery instead of TWRP .
Not sure if ADB will work for you .
JJEgan said:
Try Philz Recovery instead of TWRP .
Not sure if ADB will work for you .
Click to expand...
Click to collapse
Philz Recovery tried to flash and fails too
Recover data try ADB .
JJEgan said:
Recover data try ADB .
Click to expand...
Click to collapse
IIRC would that not require USB debugging enabled (which I cannot since it will not boot) and the Android in a running state?
Thanks to the SamFirm tool I managed to find some ROMs configured with CSC_HOME. On first shot it failed to flash these ROMs too. But I will try some more tinkering
I guess your eMMC is locked.
So the only possible solution would be to desolder it and read the data directly out of it.
Whereas the OP gives a link to an "article" at sammobile, that page has since changed and no longer gives any useful instruction for re-flashing while preserving apps and data. However, I believe that the original "step 2" of that page referred to was : "2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data."
Probably a bit late for the original poster from 2020 .
Could try flashing with No CSC .
JJEgan said:
Probably a bit late for the original poster from 2020 .
Could try flashing with No CSC .
Click to expand...
Click to collapse
Sure, there's a good chance that the original tablet has since become e-waste, however, there is also some chance that it's sitting in his friend's drawer in the slim hope of a resolution.
However, my clarification about "step 2" is for the benefit of other readers of this thread, since the OP will already know this information.
My own GT-N8020 tablet has the exact same problem. I was able to overcome the flashing difficulty by using the Prince Comsy patched version of Odin 3.12.3 (which disregards spurious USB communications errors that tend to occur).
However, re-flashing without the CSC portion of the firmware doesn't resolve the problem. I can't include the CSC portion as this will clear the data that I need to recover, and I haven't yet been able to find a HOME_CSC alternative.
Joe.