S7 EDGE SM_935A ODIN SHA256 is invalid (fail) - Samsung Galaxy S7 Edge Questions and Answers

hello please i need help , i flashed firmwares with odin before but now is giving me SHA 256 is invalid Id never had this error before.
cant get it to work by the way im trying to flash the 935U firmware

chuchobeer said:
hello please i need help , i flashed firmwares with odin before but now is giving me SHA 256 is invalid Id never had this error before.
cant get it to work by the way im trying to flash the 935U firmware
Click to expand...
Click to collapse
I'm getting the same. So far I have tried Odin versions 3.11.1, 3.12.3 and 3.12.5
Not sure what else to do.

Related

[Q] Note 4 SM-N910F 5.01 firmware upgrade fail Ext4 to small

Hello,
I have a note 4 SM-N910F and I'm from Belgium.
I have upgraded succesfully my note to 5.01 with a Netherlands firmware N910FXXU1BOC3_N910FTPD1BOC1_TPD. However in this firmware the APN for ZiGGO was hardcoded and I couldn't remove it.
In the mean time a new 5.01 for Belgium has become available N910FXXU1BOC5_N910FPRO1BOC1_PRO. But when I try to flash my note with Odin 3.09 I always end up with an error being hidden.img to big and an EXT4 size fail error. Then I need to flash back to the previous firmware to make it work again.
I redownloaded the firmware to make sure (MD5 was correct) and tried to erase the Note before flashing but with the same flashing error.
Any suggestions ?
Thank you
Bump
toxictoy said:
Hello,
I have a note 4 SM-N910F and I'm from Belgium.
I have upgraded succesfully my note to 5.01 with a Netherlands firmware N910FXXU1BOC3_N910FTPD1BOC1_TPD. However in this firmware the APN for ZiGGO was hardcoded and I couldn't remove it.
In the mean time a new 5.01 for Belgium has become available N910FXXU1BOC5_N910FPRO1BOC1_PRO. But when I try to flash my note with Odin 3.09 I always end up with an error being hidden.img to big and an EXT4 size fail error. Then I need to flash back to the previous firmware to make it work again.
I redownloaded the firmware to make sure (MD5 was correct) and tried to erase the Note before flashing but with the same flashing error.
Any suggestions ?
Thank you
Click to expand...
Click to collapse
toxictoy said:
Hello,
I have a note 4 SM-N910F and I'm from Belgium.
I have upgraded succesfully my note to 5.01 with a Netherlands firmware N910FXXU1BOC3_N910FTPD1BOC1_TPD. However in this firmware the APN for ZiGGO was hardcoded and I couldn't remove it.
In the mean time a new 5.01 for Belgium has become available N910FXXU1BOC5_N910FPRO1BOC1_PRO. But when I try to flash my note with Odin 3.09 I always end up with an error being hidden.img to big and an EXT4 size fail error. Then I need to flash back to the previous firmware to make it work again.
I redownloaded the firmware to make sure (MD5 was correct) and tried to erase the Note before flashing but with the same flashing error.
Any suggestions ?
Thank you
Click to expand...
Click to collapse
Make sure you are using the latest ODIN version, which is 3.10.6 and run ODIN as administrator.
I'm using latest Odin in administrator mode but with same result (hidden file failed size too big ext4 error). I see in the forum lot's of people face the same problem and they solve it by integrating it with a new PIT file in Odin. However I can't find the correct PIT file for this one..
Cheers
toxictoy said:
I'm using latest Odin in administrator mode but with same result (hidden file failed size too big ext4 error). I see in the forum lot's of people face the same problem and they solve it by integrating it with a new PIT file in Odin. However I can't find the correct PIT file for this one..
Cheers
Click to expand...
Click to collapse
Flash stock rom and when finish then flash custom recovery twrp and phone booted normally.
@toxictoy
Did you find how solve your problem?
Because I have the same problem like you. The only different that my note4 have region code BTU.
I was able to find online a PIT file for the note 4. I used this to flash the new rom and this worked perfectly.
Could you give me a link to this PIT file ?

Pit file

Guys,
I really need the pit file to flash the lollipop firmware.... I get error in odin.
Someone plssss
liobeir said:
Guys,
I really need the pit file to flash the lollipop firmware.... I get error in odin.
Someone plssss
Click to expand...
Click to collapse
Pit files are really "last resort" situation. What error are you getting?
What version of odin are you using?
What model of the note4 do you have?
What happened in the first place that got you here?
Have you tried to search for a fix?
What have you tried?
More info is needed mate.
Im also on the hunt for a PIT file. I had to use one on my 9505 a few times after a brutal softbrick/almost hardbrick to recover it.
N910F
andrewwright said:
Pit files are really "last resort" situation. What error are you getting?
What version of odin are you using?
What model of the note4 do you have?
What happened in the first place that got you here?
Have you tried to search for a fix?
What have you tried?
More info is needed mate.
Click to expand...
Click to collapse
Well I was trying to flash twrp trough the twrp app. But it failed. And when I wanted to reboot in recovery.. All my phone could do was boot in download mode. So I looked for the latest lollipop firmware from Samfirmware and got an error in odin. Something about the size is too big. 85098<125876 and odin said something about exfat hidden (I'm not really sure anymore). I got my phone back to work by flashing a random pit file I found on my pc. Definitely not a note 4 pit and it failed but for some reason it rebooted back to my 4.4.4 rom as it was before I bricked it. Strange. Cause odin was almost at the end of its flash so I assume some things were flashed...
Odin version 1.83 I guess but I tried it also with 3.04 and same error
I have nite 4 sm-N910F
Searched for a pit file but as I said it was fixed by a failed flash of 4.4.4 original firmware trough odin with a totally different pit file. For some reason it booted up again. So now my phone is back... If I put it manually in download mode... Will I have the same error? Cause yeah it's not bricked... See?
Sent from my SM-N910F using XDA Free mobile app
What that app did was wipe you're recovery... All you would of had to do was flash a twrp/cmw/PHILZ recovery.
liobeir said:
Guys,
I really need the pit file to flash the lollipop firmware.... I get error in odin.
Someone plssss
Click to expand...
Click to collapse
No you really need to read the Forum Rules...moved out of the Development sections.............

Can't restore G930P Firmware

Ok so here's my issue
For a very long time since the G930U firmware was available to install, I've been using that. Well I decided to want to get my phone unlocked for GSM using those services but it needs Stock Firmware.
So I tried to restore to the latest G930P firmware and ODIN is giving a Volume size error for the system.img.ex4. I've tried now a couple different firmwares and no luck. Any idea?
The latest Firmware is PH7 I don't recommend it. PG1 on down are good to go. Extract zip stock firmware to a folder and add it in to Odin all the slots accordingly. BL AP CP CSC the last slot CSC is HOME_CSC not CSC_SPT and start flashing. It always works for me.
I ended up figuring it out. I had to find the stock G930P .PIT mapping's and re-partition because G930U ended up changing the sizes.
Oh good to know. Thank for sharing
Why do you not recommend PH7 update? I've heard it helps with battery life.
Could you share the pit file you used. I tried the same thing with a pit file i found online how ever since the pit i am able to flash bootloader but unable to flash system.ext4. Odin gives me a "failed (auth)" and neyjer the 930u version or the f2 or any of the other stock roms wont flash.... Help please
Don't you just love it when people "figure it out" and then don't share how? lol
Here... Since nobody gave you this. This may not be your problem.
https://drive.google.com/file/d/0BzyeAt2hy6XeenhWM2dNSU40TDA/view?usp=sharing

[Firmware] G930TUVS4BQL2 (12/21/2017)

G930TUVS4BQL2_CL12142063_QB16000831_REV02_user_low_ship_MULTI_CERT_meta.tar.rar
Thanks. I will try it on my boot looped SM-G930T tonight.
First off, Thank you to muniz_ri for the zip.
I have a 930A (S7) running ATT firmware and having some issues every now and then running the ATT firmware on TMobile (my phone suddenly is not recognized by TMo and 4G data stops working. I have to switch the SIM card with another TMo user and switch back to my SIM and it starts working...).
I tried to load the previous version yesterday of the TMo firmware posted by muniz_ri (G930TUVS4BQJ2) and Odin (Prince) failed with a Write failure- some file was larger than could be written (ext4 fail). It then stuck at boot.
I was able to recover by flashing the ATT firmware back again.
Question- How do I get this latest TMo firmware onto the phone? Do I need to repartition or something?
Thanks for your time.
webzo said:
First off, Thank you to muniz_ri for the zip.
I have a 930A (S7) running ATT firmware and having some issues every now and then running the ATT firmware on TMobile (my phone suddenly is not recognized by TMo and 4G data stops working. I have to switch the SIM card with another TMo user and switch back to my SIM and it starts working...).
I tried to load the previous version yesterday of the TMo firmware posted by muniz_ri (G930TUVS4BQJ2) and Odin (Prince) failed with a Write failure- some file was larger than could be written (ext4 fail). It then stuck at boot.
I was able to recover by flashing the ATT firmware back again.
Question- How do I get this latest TMo firmware onto the phone? Do I need to repartition or something?
Thanks for your time.
Click to expand...
Click to collapse
I figured I would try flashing the new software you have provided above, and maybe have better luck. But no, still same deal. I captured the log messages this time-
Odin stated-
system.img.ext4
FAIL! (ext4)
Complete (write) operation failed
On the phone, I see this-
Volume size is too big 1228800 < 1254400
ODIN: Invalid ext image
[18] eMMC write fail system
So, something is too big to be written into the existing partition, I guess.
It sounds like, reading through some posts, I need to use a PIT file and re-partition or something
Any ideas on how to approach this?
By the way, yesterday, I was able to get out of the boot loop by using Odin Prince Comsey to flash to G930AUCS4BQE1 (ATT firmware from june-2017)
Today, Prince comsey wouldn't work. It ended up at-
FAIL! Model dismatch fail
After some digging around, it seemed like Odin Prince Comsey is not to be used for Stock ROMs... tried with Odin 3.12.3 and that never got past "SetupConnection". Tried again with Odin 3.12.10 and that worked.
Anyway, back to the problem at hand.... I am at G930AUCS4BQE1 (ATT from June) and need to get to G930TUVS4BQL2 (TMo, December) or G930UUEU4BQJ5 (latest 930U).
Any pointers are greatly appreciated..
Thanks.
I believe flashing the csc file rather than the home_csc automatically reformats the partitions for the rom you are flashing. If it does not, you are correct that you need the pit file which is used to reformat partitions accordingly. The pit file for TMobile can be found around this forum.

ODIN : Flash read failure + No pit binary

Hello guys,
My note 4 was having some reboot problems and when I try to boot in recovery mode I was getting error that it couldn't boot in normal mode.
I read somewhere that I should be doing a clean flash for the PIT file and the stock Rom, I started with the PIT file and it went perfectly with Odin.
But later when I tried flashing the ROM, it fails with the following errors:
- ODIN: flash read failure
- ERROR: There is no pit binary
I'm sure I have used the exact pit file for my model, I've tried flashing the Rom and the pit file at the same time but always the same error, now even retrying to flash the PIT file fails.
I'm wondering if there is any way I can fix this problem.
Thank you
binpax said:
Hello guys,
My note 4 was having some reboot problems and when I try to boot in recovery mode I was getting error that it couldn't boot in normal mode.
I read somewhere that I should be doing a clean flash for the PIT file and the stock Rom, I started with the PIT file and it went perfectly with Odin.
But later when I tried flashing the ROM, it fails with the following errors:
- ODIN: flash read failure
- ERROR: There is no pit binary
I'm sure I have used the exact pit file for my model, I've tried flashing the Rom and the pit file at the same time but always the same error, now even retrying to flash the PIT file fails.
I'm wondering if there is any way I can fix this problem.
Thank you
Click to expand...
Click to collapse
I bet 100$ (which you'll pay) that nobody can find in your message the hidden sentence about the model of your note 4.
If, by the grace of the literate and smart people here, someone can 100% say that your phone is a 910F or similar model with a Snapdragon CPU, then...
Maybe your phone has a health problem plague called eMMC failure.
Or so it looks like.
You want my paypal account ? :silly:
Did you try newer versions of Odin?
And try also the PC app of Samsung - SmartSwitch - it can flash the original firmware based on the SN of your phone (located under the battery).
Read some more about these steps and try.
Tho, it looks like a dead emmc.
w41ru5 said:
I bet 100$ (which you'll pay) that nobody can find in your message the hidden sentence about the model of your note 4.
If, by the grace of the literate and smart people here, someone can 100% say that your phone is a 910F or similar model with a Snapdragon CPU, then...
Maybe your phone has a health problem plague called eMMC failure.
Or so it looks like.
You want my paypal account ? :silly:
Did you try newer versions of Odin?
And try also the PC app of Samsung - SmartSwitch - it can flash the original firmware based on the SN of your phone (located under the battery).
Read some more about these steps and try.
Tho, it looks like a dead emmc.
Click to expand...
Click to collapse
Sorry man, I forgot to mention my phone model, which is N910F.
The eMMC failure error only showed once on the recovery mode.
I've tried different versions of Odin, 3.13, 3.10 and 3.09, same error.
I also tried with SmartSwitch but for some reason they say that my model is not supported.
binpax said:
Sorry man, I forgot to mention my phone model, which is N910F.
The eMMC failure error only showed once on the recovery mode.
I've tried different versions of Odin, 3.13, 3.10 and 3.09, same error.
I also tried with SmartSwitch but for some reason they say that my model is not supported.
Click to expand...
Click to collapse
Interesting, I have an 910C (Exynos) and the SmartSwitch worked for me - I've had a soft brick too.
Oh, well... don't have too many hopes for the emmc issue. As far as it's known this means death.
Sorry for your loss.
try maybe
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448
SAMSUNG SM-N915FY ODIN: Flash read failure ERROR: There is no pit binary
raul6 said:
try maybe
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448
Click to expand...
Click to collapse
Good day! I just want to ask. I want to flash the firmware of my samsung SM-N915FY. But when I flash the firmware that I downloaded, this is the prompt message:
ODIN: Flash read failure
ERROR: There is no pit binary
Can someone help me with this
#19
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .
Mã Lạc said:
#19
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. ......
Click to expand...
Click to collapse
This here is the forum for Note 4.
That has no OEM unlock option.

Categories

Resources