Related
Hi everyone,
First of all, please forgive me of my noobishness as this is my first post on the XDA forums.
My Galaxy S4 (SCH-I545) was working fine today. It was also rooted. As some of you may know, you are not able to recieve software updates if your phone is rooted, so I decided to try unrooting it and flash the unrooted stock firmware.
I booted into download mode and started Odin with the stock firmware in the PDA section. No other settings were changed. I attempted to flash the phone, and it failed with "sw rev check failed".
I tried restarting the phone. It came to the screen "Firmware Update Encountered an Issue".
Later, I was reading about the PIT file. I downloaded the PIT file for the SCH-I545 and flashed it. It failed on the phone with "Secure Check Fail: PIT". It failed on Odin with "Re -Partitioning Failed".
I restarted the phone again. It now displays "Samsung Custom" with a little unlocked padlock under it. I left it there for 20 minutes, it stayed on the same screen.
I tried booting into the stock recovery with success. I immediately selected "Wipe Data/Factory Reset". After this, I restarted the phone.
When the phone came back up, I booted into download mode and tried flashing again. This process failed with the same error "sw rev check failed". It again went to "Firmware Update Encountered an Issue". I repeated flashing the PIT, which failed again, but I was then able to boot into recovery once more.
At this point, I have wiped the data. The phone is sitting on my desk right now, completely wiped and able to boot into recovery, I just need to get this fixed ASAP because it is my only means of contact.
Can anyone help me as far as not being able to flash the phone? I apologize if I am confusing you, I just want to be as descriptive as possible to get the best help.
Thank you everyone for your time.
Squerl101 said:
Hi everyone,
First of all, please forgive me of my noobishness as this is my first post on the XDA forums.
My Galaxy S4 (SCH-I545) was working fine today. It was also rooted. As some of you may know, you are not able to recieve software updates if your phone is rooted, so I decided to try unrooting it and flash the unrooted stock firmware.
I booted into download mode and started Odin with the stock firmware in the PDA section. No other settings were changed. I attempted to flash the phone, and it failed with "sw rev check failed".
I tried restarting the phone. It came to the screen "Firmware Update Encountered an Issue".
Later, I was reading about the PIT file. I downloaded the PIT file for the SCH-I545 and flashed it. It failed on the phone with "Secure Check Fail: PIT". It failed on Odin with "Re -Partitioning Failed".
I restarted the phone again. It now displays "Samsung Custom" with a little unlocked padlock under it. I left it there for 20 minutes, it stayed on the same screen.
I tried booting into the stock recovery with success. I immediately selected "Wipe Data/Factory Reset". After this, I restarted the phone.
When the phone came back up, I booted into download mode and tried flashing again. This process failed with the same error "sw rev check failed". It again went to "Firmware Update Encountered an Issue". I repeated flashing the PIT, which failed again, but I was then able to boot into recovery once more.
At this point, I have wiped the data. The phone is sitting on my desk right now, completely wiped and able to boot into recovery, I just need to get this fixed ASAP because it is my only means of contact.
Can anyone help me as far as not being able to flash the phone? I apologize if I am confusing you, I just want to be as descriptive as possible to get the best help.
Thank you everyone for your time.
Click to expand...
Click to collapse
wut? Take 2 minutes to search for the Odin file of the build you were on, boot into odin mode and on 3.09 odin version load it to the ap section.
You CAN take OTA on rooted software.
sorry if I sound rude but you shouldn't root your phone if you can't even Google a solution to the possible problems that can occur.
gnubian said:
wut? Take 2 minutes to search for the Odin file of the build you were on, boot into odin mode and on 3.09 odin version load it to the ap section.
You CAN take OTA on rooted software.
sorry if I sound rude but you shouldn't root your phone if you can't even Google a solution to the possible problems that can occur.
Click to expand...
Click to collapse
Did you even read the whole post?
I CANNOT FLASH THE PHONE WHATSOEVER. It fails with "sw rev check failed" EVERY TIME.
As far as your saying of being able to take OTA on rooted firmware, it really isn't applicable to me right now considering my phone does not have an operating system on it.
Maybe someone that actually has useful information can help me?
Squerl101 said:
Did you even read the whole post?
I CANNOT FLASH THE PHONE WHATSOEVER. It fails with "sw rev check failed" EVERY TIME.
As far as your saying of being able to take OTA on rooted firmware, it really isn't applicable to me right now considering my phone does not have an operating system on it.
Maybe someone that actually has useful information can help me?
Click to expand...
Click to collapse
You haven't indicated what base is your phone originally and what stock image you were trying to flash.. Also...try to understand the frustration so many of us have with people that are jumping into something without researching as best as they could.
safestrap enabled, Hyperdrive driven
decaturbob said:
You haven't indicated what base is your phone originally and what stock image you were trying to flash.. Also...try to understand the frustration so many of us have with people that are jumping into something without researching as best as they could.
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
That's your problem. You can't revert to an older build. You have to flash the build you were originally on.
Sent from my NCC 1701 using Tapatalk 4
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
There's a guide telling you to flash down from mj7??
I don't think so..
Sent from my SCH-I545 using XDA Premium 4 mobile app
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
Can't flash backwards...bootloader changes from 1 version to the next makes impossible
safestrap enabled, Hyperdrive driven
I will see how this comes out when i get home from work. I will have to look for mj7. I'm sure it's out there floating around on the internet somewhere.
I will post after i try to flash mj7 with the outcome.
Please stand by
Squerl101 said:
I will see how this comes out when i get home from work. I will have to look for mj7. I'm sure it's out there floating around on the internet somewhere.
I will post after i try to flash mj7 with the outcome.
Please stand by
Click to expand...
Click to collapse
There is full wipe and no wipe version of mj7 stock image here somewhere
safestrap enabled, Hyperdrive driven
decaturbob said:
There is full wipe and no wipe version of mj7 stock image here somewhere
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Just to be clear, is MJ7 the firmware the one before MK2? I just want to be sure that I am flashing the right firmware.
Squerl101 said:
Just to be clear, is MJ7 the firmware the one before MK2? I just want to be sure that I am flashing the right firmware.
Click to expand...
Click to collapse
Correct.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
Correct.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Found it here http://forum.xda-developers.com/showthread.php?t=2507253 , will be flashing within the next 30 minutes...
Squerl101 said:
Found it here http://forum.xda-developers.com/showthread.php?t=2507253 , will be flashing within the next 30 minutes...
Click to expand...
Click to collapse
Just go to MK2.
No Wipe MK2 -> http://forum.xda-developers.com/showthread.php?t=2578209
Saferoot -> http://forum.xda-developers.com/showthread.php?t=2565758
GS4 Tether Unlock -> http://forum.xda-developers.com/showthread.php?t=2512981
tech_head said:
Just go to MK2.
No Wipe MK2 -> http://forum.xda-developers.com/showthread.php?t=2578209
Saferoot -> http://forum.xda-developers.com/showthread.php?t=2565758
GS4 Tether Unlock -> http://forum.xda-developers.com/showthread.php?t=2512981
Click to expand...
Click to collapse
I would, but I have been downloading MJ7 for about an hour (slow internet ) so it's probably not worth starting over. Hopefully everything works out!
Cool, the problem no longer exists. It took about 5 minutes to flash, and after that, it started working perfectly again. Thank you everyone for your help!
Sent from my SCH-I545 using Tapatalk
Have you tried using Kies to fix your phone?
Sent from my SCH-I545 using Tapatalk
Soft bricked my phone because my boot loader was locked. I got it to where it says i need to update the firmware in kies. How do I fix this?
I tried to flash the a stock rom via odin but it kept saying it fails...
moonylol said:
Soft bricked my phone because my boot loader was locked. I got it to where it says i need to update the firmware in kies. How do I fix this?
Click to expand...
Click to collapse
Flash a factory stock ROM image. You will need to know what build you're on to know what factory image to flash.
moonylol said:
I tried to flash the a stock rom via odin but it kept saying it fails...
Click to expand...
Click to collapse
Well, that's interesting.
Consider telling us what build you started with, what ROM you were trying to flash, and what the failure was. There's way too many things you could have done wrong for anyone to guess what failed.
In need of help returning to stock . Tried using odin 3 to load i605vramc3 but stopped by fail message in top left of odin screen. on phone downloading screen binary is samsung official but system status is custom. any help is appreciated.
coltblue said:
In need of help returning to stock . Tried using odin 3 to load i605vramc3 but stopped by fail message in top left of odin screen. on phone downloading screen binary is samsung official but system status is custom. any help is appreciated.
Click to expand...
Click to collapse
You need to post the output of Odin or tell us where it failed.. without more information it's kind of hard to tell you what is going on.
If no more information I would just tell to try again
lacoursiere18 said:
You need to post the output of Odin or tell us where it failed.. without more information it's kind of hard to tell you what is going on.
If no more information I would just tell to try again
Click to expand...
Click to collapse
after attempt 4 of odin. fail message on first square. complete ( write) operation failed.<osm> all threads completed.(succeed 0 / failed 1 ).
those are the only readings that is see from odin. not sure aware of more output readings.
coltblue said:
those are the only readings that is see from odin. not sure aware of more output readings.
Click to expand...
Click to collapse
coltblue said:
after attempt 4 of odin. fail message on first square. complete ( write) operation failed.<osm> all threads completed.(succeed 0 / failed 1 ).
Click to expand...
Click to collapse
Are you positive you are in Download Mode? Also make sure you do not have Kies installed. Also might want to try to reinstall Samsung drivers after uninstalling them. After that reboot your computer and let them install
lacoursiere18 said:
Are you positive you are in Download Mode? Also make sure you do not have Kies installed. Also might want to try to reinstall Samsung drivers after uninstalling them. After that reboot your computer and let them install
Click to expand...
Click to collapse
yes it was in downloading mode. tried deleting kies and usb drivers then download of new usb drivers after pc restart. now getting usb device not recognized.
after new usb drivers and trying odin again i received the fail message . cant open the serial (com) port
coltblue said:
after new usb drivers and trying odin again i received the fail message . cant open the serial (com) port
Click to expand...
Click to collapse
Sounds like a usb error. Try another
i got the usb error solved by deleting kies and installing seperate usb drivers. found 2 different .tar files to use in the pda section but cant locate a proper .pit file. the ones that i havve searched for lead to broken or bogus links.
coltblue said:
i got the usb error solved by deleting kies and installing seperate usb drivers. found 2 different .tar files to use in the pda section but cant locate a proper .pit file. the ones that i havve searched for lead to broken or bogus links.
Click to expand...
Click to collapse
Pit....
https://www.dropbox.com/s/ka9a0x6juscjwfc/sch-i605-16gb.pit
Thanks for the link. Still no luck though.Problem originated from a missing su binary from a superuser app that didnt update. tried to flash the original rom to correct the problem but it didnt work out. probably time to just get a new note. thanks for the help.
coltblue said:
Thanks for the link. Still no luck though.Problem originated from a missing su binary from a superuser app that didnt update. tried to flash the original rom to correct the problem but it didnt work out. probably time to just get a new note. thanks for the help.
Click to expand...
Click to collapse
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
mattnmag said:
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
Click to expand...
Click to collapse
i have tried i605vrufnd7 , and KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_ , but not the other 2. i coouldnt find a working link for the others. i shall try them and report back thank you.
success ! odin finally accepted stock 4.1.1 but showed a warning triangle saying not official software on the phone screen. ran 4.4.2 through odin and it worked first try. phone restarted , booted up and loaded 4.4.2 . never lost any settings contacts or data! the big thing i did different was using odin on my desktop with a new usb cable and using the usb 3.0 port. Thanks for all the help !
coltblue said:
success !....
Click to expand...
Click to collapse
Glad to hear that you got it restored. It sounds like you were initially running factory 4.4.2 Kit Kat when you had tried to root it to start with.
If you're re on stock 4.4.2 VRUFND7 , then unfortunately - - you can not root the device or unlock the bootloader because there's no rooting method or bootloader unlock method that works right now. You also won't be able to use Odin to downgrade to any of the other Android builds because of lock downs implemented with the 4.4.2 Kit Kat software. The good news is that your phone should run fine on stock 4.4.2 and you can use it again.
Keep your eyes open for new rooting methods.... you never know, someone might figure out how to root it yet.
mattnmag said:
Glad to hear that you got it restored. It sounds like you were initially running factory 4.4.2 Kit Kat when you had tried to root it to start with.
If you're re on stock 4.4.2 VRUFND7 , then unfortunately - - you can not root the device or unlock the bootloader because there's no rooting method or bootloader unlock method that works right now. You also won't be able to use Odin to downgrade to any of the other Android builds because of lock downs implemented with the 4.4.2 Kit Kat software. The good news is that your phone should run fine on stock 4.4.2 and you can use it again.
Keep your eyes open for new rooting methods.... you never know, someone might figure out how to root it yet.
Click to expand...
Click to collapse
stock is ok for now. just didnt like it to be a paperweight. ill watch for new rooting methods in the future too. Thanks.
Thanks!!!
mattnmag said:
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
Click to expand...
Click to collapse
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Phsyclone79 said:
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Click to expand...
Click to collapse
These guys are really helpful!
Phsyclone79 said:
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Click to expand...
Click to collapse
Cool. Glad you got it fixed. :thumbup:
So i am an idiot and bricked my s9+ international model with different firmware. It now has green screen with triangle and point in it. Can anyone help me fix this or am i sol?
xp500 said:
So i am an idiot and bricked my s9+ international model with different firmware. It now has green screen with triangle and point in it. Can anyone help me fix this or am i sol?
Click to expand...
Click to collapse
What did you do?
Sent from my SM-G965U1 using Tapatalk
so i updated the filmware to the wrong one. it says sw re check fail(bootloader) device 2 binary 1. i got 965f/ds how do i find what country it is made from ?
xp500 said:
so i updated the filmware to the wrong one. it says sw re check fail(bootloader) device 2 binary 1. i got 965f/ds how do i find what country it is made from ?
Click to expand...
Click to collapse
What firmware did you update to? Can you boot into download mode at all?
yes i can but i got stuck in a boot loop now. i have 965f/ds tiwan.
xp500 said:
yes i can but i got stuck in a boot loop now. i have 965f/ds tiwan.
Click to expand...
Click to collapse
when i tired to flash that filmware it says sw rev. check fail (bootloader) device 2: binary 1:
xp500 said:
when i tired to flash that filmware it says sw rev. check fail (bootloader) device 2: binary 1:
Click to expand...
Click to collapse
That means you're trying to load an older bootloader than what the phone already has. Find a newer Odin image for the F firmware. Samfirm is a good place to look.
I got it up and running but only have 32gb storage. Its 128gb phone
xp500 said:
I got it up and running but only have 32gb storage. Its 128gb phone
Click to expand...
Click to collapse
At least you've got it running. Not sure what's up with the storage, though.
Re
CrazyApe18 said:
At least you've got it running. Not sure what's up with the storage, though.
Click to expand...
Click to collapse
Yes ill factory restore tonight with samsung software and see if that fixes it.
CrazyApe18 said:
That means you're trying to load an older bootloader than what the phone already has. Find a newer Odin image for the F firmware. Samfirm is a good place to look.
Click to expand...
Click to collapse
Agreed ! You should look for samfirm or frija tool . Those would help you get latest firmware for your phone. Download it , flash it with odin and everything should be fine including your 128 GB memory. Just remember that its possible that as you would be on latest firmware, you might not be able to downgrade in future.
I have s6 edge latest official firmware but I have a problem that didn't faced me with earlier versions that is when i turn the screen on it flashes on then off instantaneously and the touch keeps responsive while the screen is completely off and to get it to work i have to turn it off and on several times until it works fine, so i decided to downgrade the firmware from version G925FXXU6ERD3 to version G925FXXS5ERB6 and my device origin is THR, when i tried to flash the older firmware using odin it stopped and i realized that to perform a downgrade i have to get pit file.
when i searched for the file i found a lot of different files with different sizes and i don't know what should work with me.
so please can anyone help me to get pit file?
my s6 edge is G925F with 64GB storage.
thanks a lot.
Hossam Diab said:
I have s6 edge latest official firmware but I have a problem that didn't faced me with earlier versions that is when i turn the screen on it flashes on then off instantaneously and the touch keeps responsive while the screen is completely off and to get it to work i have to turn it off and on several times until it works fine, so i decided to downgrade the firmware from version G925FXXU6ERD3 to version G925FXXS5ERB6 and my device origin is THR, when i tried to flash the older firmware using odin it stopped and i realized that to perform a downgrade i have to get pit file.
when i searched for the file i found a lot of different files with different sizes and i don't know what should work with me.
so please can anyone help me to get pit file?
my s6 edge is G925F with 64GB storage.
thanks a lot.
Click to expand...
Click to collapse
A pit file won't help you downgrade. It will repartition the phone. When you flashed the S4ERB6 firmware in odin at which point did it fail? If it failed at sboot.bin then you won't be able to downgrade even with a pit file. After you upgrade the BL locks to that revision.
So first tell me at which point odin failed at?
callumbr1 said:
A pit file won't help you downgrade. It will repartition the phone. When you flashed the S4ERB6 firmware in odin at which point did it fail? If it failed at sboot.bin then you won't be able to downgrade even with a pit file. After you upgrade the BL locks to that revision.
So first tell me at which point odin failed at?
Click to expand...
Click to collapse
It did fail at sboot.bin
that means i will never be able to perform a downgrade?
Hossam Diab said:
It did fail at sboot.bin
that means i will never be able to perform a downgrade?
Click to expand...
Click to collapse
Yes most likely
callumbr1 said:
Yes most likely
Click to expand...
Click to collapse
do you have any ideas how to fix my screen problem ?
Hossam Diab said:
do you have any ideas how to fix my screen problem ?
Click to expand...
Click to collapse
Honestly it sounds like a hardware issue, try a custom rom or a different stock Rom and see if same happens. If it does it's probably hardware issue
Do you have AOD installed?? If yes turn it off as it could be what's making the screen go off