[q] helppppp! Gs4 verizon! Vruame7 - Verizon Samsung Galaxy S 4

I rooted on VRUAME7 I am now trying to do a reset/restore. When I did a factory reset in the system, it rebooted and is now stuck on a yellow exclamation mark and says:
I tryed to put CWM on my phone. I didnt do my research so I had no idea I couldnt with ME7.. I have followed multiple forum guides that have the same exact problems as mine. also all ME7 specific. At this point... ODIN is non responsive.. and I am at the mercy of all yall haha
Odin Failed and says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says:
Start [224,1440]
SW REV. CHECK FAIL: FOUND: 3, Binary: 1

Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk

spc_hicks09 said:
Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301259
I have followed this one.. downloaded the ME7 file...
It still is not working. This is not the only ME7 file I have downloaded and they have all not worked.
I have used multiple cables on the phone and multiple versions of odin.
They are all doing the same thing... I have been at this for HOURS.
I am seriously stumped....

spjohnson08 said:
http://forum.xda-developers.com/showthread.php?t=2301259
I have followed this one.. downloaded the ME7 file...
It still is not working. This is not the only ME7 file I have downloaded and they have all not worked.
I have used multiple cables on the phone and multiple versions of odin.
They are all doing the same thing... I have been at this for HOURS.
I am seriously stumped....
Click to expand...
Click to collapse
I would verify the md5 to.make sure your not getting corrupted downloads. Its pretty common, but ya like hicks said you cant go backwards in firmware which is what you tried to do the first time around. It has to be an me7 image or ml1.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

spc_hicks09 said:
Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
This is with the ME7 file...

hexitnow said:
I would verify the md5 to.make sure your not getting corrupted downloads. Its pretty common, but ya like hicks said you cant go backwards in firmware which is what you tried to do the first time around. It has to be an me7 image or ml1.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I am now trying to use the ml1 file on http://forum.xda-developers.com/showthread.php?t=2301259
I didnt know I could do that...
How do I verify the Hash?

spjohnson08 said:
I am now trying to use the ml1 file on http://forum.xda-developers.com/showthread.php?t=2301259
I didnt know I could do that...
How do I verify the Hash?
Click to expand...
Click to collapse
Google md5 checker or md5 verifier. Its a straight forward process. The correct md5 should be posted in the thread.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

Related

Samsung galaxy s3 international will not turn on.

So yeah, for some days ago i have installed a custom rom this one : Leaked Android 4.2.2 XXUFME3 ROM for Galaxy S III
it worked fine but i wanted to get back to stock rom.
So i downloaded a stock rom ( for nordic countries )
After this i re partioned my s3, i used a file for 16 gb cause its my model. after this the phone turned on and i saw samsung galaxy s3 logo blincking, nothing else heppend. But i knew i wasnt done and took the battery out and back, and entered download mode.
Now i chosed a rom with PDA button, i unchecked re partion and hited start button. Odin was stuck at "setup connection".
I have installed and reinstalled drivers, installed and uinstalled kies, i have tried this on all of my usb ports, i tried this on my other pc with installed drivers etc. Nothing WORKS!!!! i am a noob with Android and really need a help. i Have working to get it work 4 hours and nothing...
Btw i have no sd card in my s3.
It looks like i dont have any firmware on my phone now, but i can still enter download mod, but not recovery mod.
What can i do??
Reads as you may have bricked your phone as you have for some unknown reason repartitioned it ..
install stock rom via Odin and post the Odin results .
jje
JJEgan said:
Reads as you may have bricked your phone as you have for some unknown reason repartitioned it ..
install stock rom via Odin and post the Odin results .
jje
Click to expand...
Click to collapse
omg... now odin cant see my phone...., but it was always stuck at setup connection, or the odin have stoped working. I will reset my pc and post result.
kris222 said:
omg... now odin cant see my phone...., but it was always stuck at setup connection, or the odin have stoped working. I will reset my pc and post result.
Click to expand...
Click to collapse
no need to reset your pc. change the usb port and check it. there's no need for you to panic.
sriram231092 said:
no need to reset your pc. change the usb port and check it. there's no need for you to panic.
Click to expand...
Click to collapse
okey i have pluged it to another computer and now it comes up in odin. but it wont install . here
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9300_NEE_I9300XXALE8_I9300NEEALE3_I9300XXLE8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
and here it ends..... after like 20 min the message comes up and says that 0 complited 1 failed. so what now?
kris222 said:
okey i have pluged it to another computer and now it comes up in odin. but it wont install . here
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9300_NEE_I9300XXALE8_I9300NEEALE3_I9300XXLE8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
and here it ends..... after like 20 min the message comes up and says that 0 complited 1 failed. so what now?
Click to expand...
Click to collapse
did you do everything as mentioned in this site? http://androidromupdate.com/2012/06...ung-galaxy-s3-gt-i9300-stock-rom-i9300xxale8/
i did!
the only thing i did wrong was to re partition it......
now i dont know how to get it work...
Try flashing again but with the newest ROM from NEE, if flash successful, probably will boot loop again, enter to recovery mode and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=1646610 2nd post.
Good luck
Regards
[email protected]
You'll need to re-partition now! You probably screwed pit partition!
Try with another pit file and make sure its a legit one!
Sent from my GT-I9300 using xda premium
Ver3go said:
You'll need to re-partition now! You probably screwed pit partition!
Try with another pit file and make sure its a legit one!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hi i downloaded pit file for 16 gb model. After instlling it it said pass (green) on odin. After this i i tried to install the stock rom, but it failed....
Here is log of Odin :
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMD2_I9300OXXEMD1_I9300XXEMC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Help???
anyone??
kris222 said:
Hi i downloaded pit file for 16 gb model. After instlling it it said pass (green) on odin. After this i i tried to install the stock rom, but it failed....
Here is log of Odin :
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMD2_I9300OXXEMD1_I9300XXEMC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Help???
Click to expand...
Click to collapse
Do all in one thick re-partition! And put the pit. And choose pda with your rom
Sent from my GT-I9300 using xda premium
Pretty fun that non experienced people are flashing stuffs, rooting etc etc without reading two or three times before so they learn about what could happen if anything are done the wrong way..
In worst case, warranty is the only solution to fix this and re-program PIT layering of your phone. It may cost if there is any sign of modifications / flash counter above zero...
Sent from my GT-I9300 using xda app-developers app
Go to http://forum.xda-developers.com/showthread.php?t=1944196 post #6
Regards
[email protected]
So there is nothing i can do? just go to service....?
And because i have installed custom rom i have no waranty.... is it expensiv to fix?
btw i heard of a 3 part rom with mx.pit, would it help or would it make it wors?
?????
kris222 said:
So there is nothing i can do? just go to service....?
And because i have installed custom rom i have no waranty.... is it expensiv to fix?
btw i heard of a 3 part rom with mx.pit, would it help or would it make it wors?
Click to expand...
Click to collapse
Your phone is dead sure worst wont do
Sent from my GT-I9300 using xda premium
I think they will repair it for free
Sent from my washing machine using xda premium

[Q] Help unbrick my phone (soft brick)

Hi all last week I took my phone out of my pocket and it was turned off, I tried turning it back on and it just freezes on the Galaxy boot screen, my phone was running a stock ROM... Whats happened ????
I've tried flashing via odin
I've tried flashing via the MAC version
I've tried two or three different stock ROM's downloaded from Sammobile and Samsung updates
And all I get is FAIL, FAIL, FAIL......
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSW_I9100H3GLS5_I9100NELS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSW_I9100H3GLS5_I9100NELS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me
We got tons of threads like this, care to check them out?
BTW see that can't open COM port msg? That's kinda the key.
Sent from the little guy
gastonw said:
We got tons of threads like this, care to check them out?
BTW see that can't open COM port msg? That's kinda the key.
Sent from the little guy
Click to expand...
Click to collapse
Thats the first time thats come up, it normally says NAND then freezes then comes up fail................ ive read lots of posts and tried lots of things.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSW_I9100H3GLS5_I9100NELS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Alright, tell me what and how you are flashing.
Also what device you've got.
Sent from the little guy
gastonw said:
Alright, tell me what and how you are flashing.
Also what device you've got.
Sent from the little guy
Click to expand...
Click to collapse
GTi9100 UK three network
I've tried the latest ROM from sammobile & Samsung update also the ROM before the latest ?
Alright, I wanna know the how.
Killed kies and all?
Different usb ports, cables?
Sent from the little guy
gastonw said:
Alright, I wanna know the how.
Killed kies and all?
Different usb ports, cables?
Sent from the little guy
Click to expand...
Click to collapse
Ive uninstalled KIES (tried it before uninstall and same outcome, used different port, laptop, cable...
Alright, flash jb leak.
It's around here somewhere.
Edit: While you download that you could flash siyah v6.
Sent from the little guy
gastonw said:
Alright, flash jb leak.
It's around here somewhere.
Edit: While you download that you could flash siyah v6.
Sent from the little guy
Click to expand...
Click to collapse
whats jb leak ive tried Siyah
It's a samsung test firmware.
Google it & download it.
Are you sure you went over hopper's troubleshooting thread?
Sent from...this is not even my S2
gastonw said:
It's a samsung test firmware.
Google it & download it.
Are you sure you went over hopper's troubleshooting thread?
Sent from...this is not even my S2
Click to expand...
Click to collapse
Which post are you referring to
This one :
http://forum.xda-developers.com/showthread.php?p=43179020#post43179020
Sent from a galaxy far, far away
Cheers... is this the leaked ROM http://forum.xda-developers.com/showthread.php?t=1995767 just downloading it now to try it
Hopper8 said:
This one :
http://forum.xda-developers.com/showthread.php?p=43179020#post43179020
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Good god, where did you come from?
You're like a ninja.
Sent from...this is not even my S2
Red_Stafford said:
Cheers... is this the leaked ROM http://forum.xda-developers.com/showthread.php?t=1995767 just downloading it now to try it
Click to expand...
Click to collapse
Yep that'll do it. We usually download our firmware from Samfirmware around here, but that's the guy.
gastonw said:
Good god, where did you come from?
You're like a ninja.
Sent from...this is not even my S2
Click to expand...
Click to collapse
... I think I take that as a good thing?....
Sent from a galaxy far, far away
Just tried this
10.
Press "PDA" and select the "CODE_I9100XXLSJ.tar file".
Press "Phone" and select the MODEM_I9100XXLS6.tar file".
Press "CSC" and select the CSC_HOME_OXX_I9100OXXLS1.tar file".
and got this
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Try another odin version.
I still think this is a driver conflict.
Sent from the little guy
Hopper8 said:
Yep that'll do it. We usually download our firmware from Samfirmware around here, but that's the guy.
... I think I take that as a good thing?....
Sent from a galaxy far, far away
Click to expand...
Click to collapse
being a ninja is always a good thing
Sent from the little guy
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Thats what I get when I try and flash Siyah-s2-v6.0b5.tar
Is my nand corrupt do I need to re-partition using PIT file ?

Trying to root and bricked my phone.

I'm trying to brick my phone using ODIN 3.07 and file name, VRUDMI1_Root_de_la_vega_jfltevzw.tar.md5 but it kept failing at Fail (AUTH). I've since downloaded the factory image for VRUDMI1 (which is what my phone is) from the link found in this thread.
After rebooting the phone and again trying to flash it via Odin 3.07 I'm now getting this error message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point, what else can I do to recover the phone into working operation?
sage55 said:
I'm trying to brick my phone using ODIN 3.07 and file name, VRUDMI1_Root_de_la_vega_jfltevzw.tar.md5 but it kept failing at Fail (AUTH). I've since downloaded the factory image for VRUDMI1 (which is what my phone is) from the link found in this thread.
After rebooting the phone and again trying to flash it via Odin 3.07 I'm now getting this error message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point, what else can I do to recover the phone into working operation?
Click to expand...
Click to collapse
I would start by redownloading the file you're flashing to make sure your current one isn't corrupt. May even wanna try unistalling odin and reinstalling. And you're sure that you are flashing the same version you are already on?
sage55 said:
I'm trying to brick my phone using ODIN 3.07 and file name, VRUDMI1_Root_de_la_vega_jfltevzw.tar.md5 but it kept failing at Fail (AUTH). I've since downloaded the factory image for VRUDMI1 (which is what my phone is) from the link found in this thread.
After rebooting the phone and again trying to flash it via Odin 3.07 I'm now getting this error message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point, what else can I do to recover the phone into working operation?
Click to expand...
Click to collapse
This is a VERY frequently asked question. You're probably flashing the wrong software (i.e. older than what's on your phone). There's a bit more detail on the cause of the "FAIL!" displayed on your phone that could be used to verify the cause.
You're trying to flash a no-wipe image as well. Using a full wipe factory image may work better.
bjoostema said:
I would start by redownloading the file you're flashing to make sure your current one isn't corrupt. May even wanna try unistalling odin and reinstalling. And you're sure that you are flashing the same version you are already on?
Click to expand...
Click to collapse
Uninstall and re-install odin? What are you talking about? Odin was in a zip file that I simply had to extract then run. There was no install process nor would their be an uninstall process...
As for the files I've tried thus far and their MD5 as per Md5Checker:
File: rootdelavegajfltevzw.7z
MD5: BC497A23D75752D2C5AAD8D7D8E39B00
Note: Root for MI1 build.
File: SCH-I545_VZW_3_20131015092810_3pa3eg8qji.zip
MD5: 8335DA10191B0E2CE84A701B8E5249B4
Note: No-wipe factory restore for MI1 build.
File: SCH-I545_VZW_1_20130613171315_24s13crny1_fac.zip
MD5: 622956872FA0083188BEAB3A78A21B1C
Note: Factory restore for M7J build (I seen in another thread where this fixed previously bricked phones)
All three have failed, all at different points.
sage55 said:
Uninstall and re-install odin? What are you talking about? Odin was in a zip file that I simply had to extract then run. There was no install process nor would their be an uninstall process...
As for the files I've tried thus far and their MD5 as per Md5Checker:
File: rootdelavegajfltevzw.7z
MD5: BC497A23D75752D2C5AAD8D7D8E39B00
Note: Root for MI1 build.
File: SCH-I545_VZW_3_20131015092810_3pa3eg8qji.zip
MD5: 8335DA10191B0E2CE84A701B8E5249B4
Note: No-wipe factory restore for MI1 build.
File: SCH-I545_VZW_1_20130613171315_24s13crny1_fac.zip
MD5: 622956872FA0083188BEAB3A78A21B1C
Note: Factory restore for M7J build (I seen in another thread where this fixed previously bricked phones)
All three have failed, all at different points.
Click to expand...
Click to collapse
OK, you're doing the right things but it's failing. The next thing to try is to make sure you're using a known good OEM (Samsung) USB cable. Also, try a different port on your PC. Some people have had better success with using the ports on the back of their PCs.
When I run the Root image for MI1 the error in odin is above and the error on the phone in tiny red text is:
SECURE CHECK FAIL: CACHE
The MJ7 file seems to go the furthest but still fails:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone in super tiny text and red is:
START [224,1440]
SW REV. CHECK FAIL; FUSED; 5. BINARY; 3
For the No-Wipe MI1 file I Odin has this error:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and the phone shows the following error:
SW REV. CHECK FAIL; FUSED; 5. BINARY; 4
Just got the phone this afternoon and am using the white Samsung USB cord that came with the phone. I've tried using the USB ports on the back of my desktop computer (windows 8.1) as well as on my laptop (Windows 7).
sage55 said:
When I run the Root image for MI1 the error in odin is above and the error on the phone in tiny red text is:
SECURE CHECK FAIL: CACHE
START [224,1440]
SW REV. CHECK FAIL; FUSED; 5. BINARY; 3
Click to expand...
Click to collapse
That is not good news.
Each time VZ updates their software for these phones, they update a value in a fuse.
That started as 1 with MDK, went to 2 with ME7, 3 with MI1, and 4 with MJ7. At least that's what I think the revisions did to the qfuse.
So it's seeing that you're trying to flash a binary with revision 3 (BINARY:3) but it remembers a flash with revision 5.
Now, there's nothing out there that I know of for the i545 that's rev 5 - the next update after MJ7 will be rev 5. So, your phone is probably not going to be recoverable until VZ and Samsung release another software update for the I545. Something corrupted the fuse storing the update level.
You can verify this by flashing MJ7 - it'll probably say FUSED:5, BINARY: 4.
Sorry for the bad news.
k1mu said:
You can verify this by flashing MJ7 - it'll probably say FUSED:5, BINARY: 4.
Sorry for the bad news.
Click to expand...
Click to collapse
The MJ7 file errors with "SW REV. CHECK FAIL; FUSED; 5. BINARY; 3"
The MI1 No-wipe file errors with SW REV. CHECK FAIL; FUSED; 5. BINARY; 4"
Fused value for ME7 was 3. So for MJ7 the fused value should be 5. The binary values are one behind because you're using no wipe odin tars. The dev edition binary values are set to 1. Use the full odin tar instead.
Sent from my SCH-I545 using XDA Premium 4 mobile app
is there a way to edit so called fuse value and binary value in MI1 to read that same value as MJ7 when flashing ?
Surge1223 said:
Fused value for ME7 was 3. So for MJ7 the fused value should be 5. The binary values are one behind because you're using no wipe odin tars. The dev edition binary values are set to 1. Use the full odin tar instead.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are absolutely correct and somehow I managed to download ME7 thinking it was MJ7. I've downloaded MJ7 from here and so far I've gone much further in the flashing process. Crossing fingers.
The correct, MJ7 file did in fact work and the phone is back to life running Android 4.3!
Thanks for all the help guys!
delete
Surge1223 said:
Fused value for ME7 was 3. So for MJ7 the fused value should be 5. The binary values are one behind because you're using no wipe odin tars. The dev edition binary values are set to 1. Use the full odin tar instead.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. That also explains one of the other major differences in the no-wipe tar files, which is something I didn't know.
---------- Post added at 09:13 AM ---------- Previous post was at 08:48 AM ----------
enfurnic said:
is there a way to edit so called fuse value and binary value in MI1 to read that same value as MJ7 when flashing ?
Click to expand...
Click to collapse
No, the value in the binary can't be altered without invalidating the signature.
The "fuse" is an efuse that can't currently be reverted. From what I know of how it's implemented, it's simply not possible at all to restore.

[Q] Error while using ODIN to flash to stock.

Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
xMopx said:
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
Click to expand...
Click to collapse
You can't flash backwards. Flash me7.
gnubian said:
You can't flash backwards. Flash me7.
Click to expand...
Click to collapse
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
xMopx said:
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
Click to expand...
Click to collapse
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<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
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
xMopx said:
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<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
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
Click to expand...
Click to collapse
Just go to the safestrap app in app drawer on stock slot and uninstall it.
gnubian said:
Just go to the safestrap app in app drawer on stock slot and uninstall it.
Click to expand...
Click to collapse
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
xMopx said:
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
Click to expand...
Click to collapse
What happens when you start the phone?
gnubian said:
What happens when you start the phone?
Click to expand...
Click to collapse
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
xMopx said:
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
Click to expand...
Click to collapse
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
gnubian said:
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
Click to expand...
Click to collapse
Positive. I had installed the rom/recovery before anything newer than me7 was released. And I remember when I upgraded from whatever it shipped with to ME7 because the upgrade window popped up and I tapped Install by accident. I had this installed: http://forum.xda-developers.com/showthread.php?t=2351840.
Edit: to confirm, I found my old post asking about the modules to get that rom to work on ME7: http://forum.xda-developers.com/showthread.php?p=46944438
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
gnubian said:
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
Click to expand...
Click to collapse
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
xMopx said:
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
Click to expand...
Click to collapse
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
gnubian said:
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
Click to expand...
Click to collapse
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
xMopx said:
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
Click to expand...
Click to collapse
Try finding a stock recovery tar for your build and just flashing that in odin.
gnubian said:
Try finding a stock recovery tar for your build and just flashing that in odin.
Click to expand...
Click to collapse
I had the thought of doing this, but wasn't able to find one.
xMopx said:
I had the thought of doing this, but wasn't able to find one.
Click to expand...
Click to collapse
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
gnubian said:
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
Click to expand...
Click to collapse
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
xMopx said:
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
Click to expand...
Click to collapse
I believe it has to be a tar. If you can get it on there and wipe data/factory reset it may get rid of safestrap and allow you to odin the full stock tar.

Sprint S6 edge Brick

I have a sprint s6 edge that I rooted but after i rooted it I flashed twrp recovery. Ironically it bricked my phone. I've tried using odin and I got this error: <ID:0/005> Complete(Write) operation failed.
Here's the whole log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU1AOCF_G925PSPT1AOCF_G925PVPU1AOCF_HOME.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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, I have all the drivers installed and all of that. I am new to this kind of stuff and I've seen people talk about pit files. I don't kno what those are so I don't know if that would help me. I've been trying to fix this for 3 months please help.
UNICORNSRDABEST said:
I have a sprint s6 edge that I rooted but after i rooted it I flashed twrp recovery. Ironically it bricked my phone. I've tried using odin and I got this error: <ID:0/005> Complete(Write) operation failed.
Here's the whole log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU1AOCF_G925PSPT1AOCF_G925PVPU1AOCF_HOME.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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, I have all the drivers installed and all of that. I am new to this kind of stuff and I've seen people talk about pit files. I don't kno what those are so I don't know if that would help me. I've been trying to fix this for 3 months please help.
Click to expand...
Click to collapse
Have you tried SmartSwitch its easier Then odin
osman34 said:
Have you tried SmartSwitch its easier Then odin
Click to expand...
Click to collapse
When I downloaded smart switch I got a side by side error. This happened on 2 different computers. I don't know how to fix it. I also tried using kies but I'm not sure how to get the s/n or imei.
UNICORNSRDABEST said:
When I downloaded smart switch I got a side by side error. This happened on 2 different computers. I don't know how to fix it. I also tried using kies but I'm not sure how to get the s/n or imei.
Click to expand...
Click to collapse
sboot.bin fail is the bootloader is older than your current one. Flash another firmware with a newer bootloader.
If you try smart switch you must fully close odin and phone still needs to be in download mode to do the emergency firmware recovery
callumbr1 said:
sboot.bin fail is the bootloader is older than your current one. Flash another firmware with a newer bootloader.
If you try smart switch you must fully close odin and phone still needs to be in download mode to do the emergency firmware recovery
Click to expand...
Click to collapse
So that means my odin is out of date or the stock firmware?
UNICORNSRDABEST said:
So that means my odin is out of date or the stock firmware?
Click to expand...
Click to collapse
the stock firmware has a older bootloader.
flash a firmware with newer bootloader.
callumbr1 said:
the stock firmware has a older bootloader.
flash a firmware with newer bootloader.
Click to expand...
Click to collapse
I'm still new to his stuff. What is a boot loader?
UNICORNSRDABEST said:
I'm still new to his stuff. What is a boot loader?
Click to expand...
Click to collapse
its part of the firmware package.
try to flash this firmware through odin
https://www.sammobile.com/firmwares/download/119909/G925PVPU4CPL3_G925PSPT4CPL3_SPR/

Categories

Resources