Database Users

[Q] May have bricked phone - need help

This all started when I wanted to install cyanogenmod a couple days ago. I was on 4.2.2 rooted and just wanted to play around. I used an app to back up everything, and didn't use Clockwork to make a backup (huge mistake). I finally got cyan on phone and didn't like it. then I started trying to flash stock roms back on my phone using zip files and clockwork. It would look like it was installed but would get hung up after the galazy s4 screen (never saw sprint screen or anything else). Then I tried using odin and the .tar files. I used odin 1.85 and 307. It looks like it recognizes my phone but I get a fail message. Here is what odin says:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Stock_Rooted_Odexed_MF9_Rom.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when I try to restart my phone all I see is "Firmware upgrade encountered an Issue. Please select recovery in Kies & try again". I can't even load up clockwork! Please help!

Have you tried
http://forum.xda-developers.com/showthread.php?t=2258107
It looks like you might have an issue that I ran into awhile back. I ended up using team win recovery. Also, when you changed to cm, was out still 4.2.2? Or was it something else?
Sent from my SPH-L720 using xda app-developers app

Well I am back in action! I downloaded the new philz recovery tar and used Odin 3 to flash it. I couldn't believe it worked! I was then able to boot into recovery mode where I was able to flash the stock rom that I had put on my sd card before I soft bricked the phone. I eventually put the triforce rom on the phone and like it so far. The only problem is I haven't been able to get 4g (lte) network connection yet?? Has anyone had this issue with the triforce 4.1 rom? My software version is MF9 and so is my baseband if that helps. Thanks!

Have you looked at this?
http://forum.xda-developers.com/showthread.php?t=2277480
Now that requires you to update to mja but keep you're mf9 boot loader. Not sure of that's what you want to do or not. Once you got MJA you can't go back. However if you go MK2 you can back to MJA. Just depends how updated you want to be.
Sent from my SPH-L720 using xda app-developers app

[Solved] Need help with SHV-E300L - Cannot load most roms - stuck with bad rom

Hi,
So I'm a bit of a noob with regards to roms and kernels and all that stuff and I've found myself with a bit of a problem.
I ordered a Samsung Galaxy S4 (i9500) from Korea and received it a few days ago. The phone worked fine but was Android 4.2.2. There was no updates available OTA or in Kies so I decided to try flash my own rom.
I went about doing this and discovered that CWM recovery was already on the phone...it must have been added by the supplier, however the CWM version was in Korean.
I downloaded a rom, the first one I found, called Ozcran Rom. It's Android 4.4.2. On my phone it's very unstable, it keeps rebooting and it cannot recognize my sim card but it kind of works. I've tried to change the rom to many other ones but they all either fail to install or if I can install them they load but get no further than the boot animation.
Because the CWM was in Korean and because I'm a fool I never made a backup of the original. I've since been able to update CWM to an english version and figured out how to make a backup of the (barely working) Ozcran rom but I'm not having any luck installing a rom that actually works.
I've tried loading roms with both CWM and Odin but usually Odin fails. Odin was able to update CWM recovery for me but it seems to fail everytime I try to install a rom.
I've attached a screenshot of the About screen (when it's working with Ozcran Rom). When the phone is in download mode (in korean) it says Product Name: SHV-E300L, Current Binary: Custom, System status: Custom.
Can someone please help with this?

nicenormalfiend said:
Hi,
So I'm a bit of a noob with regards to roms and kernels and all that stuff and I've found myself with a bit of a problem.
I ordered a Samsung Galaxy S4 (i9500) from Korea and received it a few days ago. The phone worked fine but was Android 4.2.2. There was no updates available OTA or in Kies so I decided to try flash my own rom.
I went about doing this and discovered that CWM recovery was already on the phone...it must have been added by the supplier, however the CWM version was in Korean.
I downloaded a rom, the first one I found, called Ozcran Rom. It's Android 4.4.2. On my phone it's very unstable, it keeps rebooting and it cannot recognize my sim card but it kind of works. I've tried to change the rom to many other ones but they all either fail to install or if I can install them they load but get no further than the boot animation.
Because the CWM was in Korean and because I'm a fool I never made a backup of the original. I've since been able to update CWM to an english version and figured out how to make a backup of the (barely working) Ozcran rom but I'm not having any luck installing a rom that actually works.
I've tried loading roms with both CWM and Odin but usually Odin fails. Odin was able to update CWM recovery for me but it seems to fail everytime I try to install a rom.
I've attached a screenshot of the About screen (when it's working with Ozcran Rom). When the phone is in download mode (in korean) it says Product Name: SHV-E300L, Current Binary: Custom, System status: Custom.
Can someone please help with this?
Click to expand...
Click to collapse
can you tell us what odin says when it fails? give us a picture please, most odin fails are because of wrong firmware for wrong devices. also did you get your stock rom from here http://www.sammobile.com/firmwares/2/ ? most recommended place.

Hi.
One of the stock roms I tried was from sammobile yes.
I've attached an image of Odin when it fails and I've pasted the content of the message box here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUGNH4_I9500OJKGNI1_I9500JKUGNH1_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

nicenormalfiend said:
Hi.
One of the stock roms I tried was from sammobile yes.
I've attached an image of Odin when it fails and I've pasted the content of the message box here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUGNH4_I9500OJKGNI1_I9500JKUGNH1_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you say its a i9500 but you said its a SHV-E300L in download mode, try flashing one of those stock roms from sammobile might have to deal with Korean language for awhile unless Samsung Korean phones come with english. You are sure its a i9500? take out the battery and tell me the model number where the battery is supposed to go.

Trozzul said:
you say its a i9500 but you said its a SHV-E300L in download mode, try flashing one of those stock roms from sammobile might have to deal with Korean language for awhile unless Samsung Korean phones come with english. You are sure its a i9500? take out the battery and tell me the model number where the battery is supposed to go.
Click to expand...
Click to collapse
I thought perhaps SHV-E300L was the model number of the i9500 in Korea.
Under the batter the model number says GT-i9500. Is the SHV-E300L supposed to be different from the i9500?
I'll try downloading firmware from sammobile for the SHV-E300L...

I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.

Trozzul said:
I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.
Click to expand...
Click to collapse
Ok, thanks for the lead. I'll give the SHV-E300L firmware a go

Trozzul said:
I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.
Click to expand...
Click to collapse
Amazing, the firmware for SHV-E300L works perfectly. Thank you so much!

nicenormalfiend said:
Amazing, the firmware for SHV-E300L works perfectly. Thank you so much!
Click to expand...
Click to collapse
Enjoy i hope you are able to get non-korean languages if you need it. if you have any other questions please be sure to ask!

я
мне тоже дайти
nicenormalfiend said:
ok, thanks for the lead. I'll give the shv-e300l firmware a go
Click to expand...
Click to collapse

Phone bricked for unknown reasons; ODIN flash operation failed - What to do?

Good evening,
for unknown reasons my phone (Unbranded Samsung Galaxy S4) started to show weird signs of system failures. It kept restarting and hanging on the boot screen; often rapidly changed the battery percentages and then crashed. A day after these weird errors appeared the phone suddenly refused to boot at all. The boot process stopped at the Samsung logo and completely froze.
So I tried booting into recovery... But it didnt work? Sometimes it simply rebooted after showing "Recovery booting..." in the top left side of the screen and sometimes it displayed an red error showing "No command". On the 15th try or so it suddenly showed a kernel error instead:
"SET WARRENTY BIT: KERNEL"
Instead of using recovery mode I instead booted into Odin mode, where to my surprise I found that the current binary was no longer the official Samsung one, but a custom one. I decided on downloading stock firmware from the Samsung database and flashing it with Odin v3.11.
Name of the used firmware pack: " I9505XXUHOJ2 [5.0.1]"
I put it into Odin mode and then applied the firmware md5 file under AP in Odin 3.11 and it started working. Flashing the image was successful until half through the system.img.ext4 part where after half of the operation it suddenly failed and disconnected. Recovery.img and so on, however, was flashed successfully. I rebooted it into Odin mode, where the binary was now "Samsung Official" and retried the procedure.
This time it failed instantly. Shortly after starting the operation Odin said it could not open the specified file and the operation was aborted. The phone is now stuck in a "Firmware Update Failed - Use Kies Recovery" bootloop that remains even when I turn the phone off. (It simply turns back on again)
Is the phone screwed now? Re-Partioning was unchecked so I don't know if the partition table was ruined or not.
Does anyone have an idea?
Info shown after operation in Odin mode:
PRODUCT NAME: GT-I9505
CURRENT BINARY: SAMSUNG OFFICIAL [CUSTOM before operation]
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0x0
KNOX WARRENTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: ENABLED
eMMC BURST MODE: ENABLED
I can't even turn off the phone now :victory:
No customization has occured on this phone. I have never used any custom roms or custom kernels. It simply started doing weird stuff on its own.
maybe hardware faulty? NAND corrupt?

Perhaps try flashing TWRP until it's successful, and then use it to flash the framework file(s) you've placed on the SD (use another phone for this end, or an mSDcard adapter that comes with the SD (most laptops have a slot for this). This does away with many underlying assumptions, like the soundness of the cable, port, laptop/pc, and flashing software.
First just charge the battery until it's full.
KNOX WARRENTY VOID: 0x1
Click to expand...
Click to collapse
Seems like a potential security threat. Are you sure you haven't rooted your phone somehow?
Btw, if the partition is indeed ruined, use TWRP to make a backup of the phone (even if there's nothing to backup). It'll restore the partition table. Then proceed to flash the framework from the SD via TWRP.

ThePrick said:
Perhaps try flashing TWRP until it's successful, and then use it to flash the framework file(s) you've placed on the SD (use another phone for this end, or an mSDcard adapter that comes with the SD (most laptops have a slot for this). This does away with many underlying assumptions, like the soundness of the cable, port, laptop/pc, and flashing software.
First just charge the battery until it's full.
Seems like a potential security threat. Are you sure you haven't rooted your phone somehow?
Btw, if the partition is indeed ruined, use TWRP to make a backup of the phone (even if there's nothing to backup). It'll restore the partition table. Then proceed to flash the framework from the SD via TWRP.
Click to expand...
Click to collapse
Before I read your post I tried flashing a 4.X software for GT-I9505, which was successful with ODIN.
Recovery still wont work, as it crashes the phone instantly. Booting normally got to the Samsung logo part and then froze.
Sometimes the phone shows very weird graphical glitches. It boots up with a green dotted screen and slowly turns brightness up to max. I think this might mean its hardware faulty.
Concerning the KNOX issue: The phone was never rooted nor modified. I have no idea how the system picked up a rooting process when there was none.
I'll try flashing TWRP... Atleast download mode still works even though everything else doesnt.
Thanks for your reply
EDIT: Flashed TWRP successfully but S4 is refusing to boot into recovery
following error is dísplayed:
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRENTY BIT: RECOVERY

Noroxuz said:
Before I read your post I tried flashing a 4.X software for GT-I9505, which was successful with ODIN.
Recovery still wont work, as it crashes the phone instantly. Booting normally got to the Samsung logo part and then froze.
Sometimes the phone shows very weird graphical glitches. It boots up with a green dotted screen and slowly turns brightness up to max. I think this might mean its hardware faulty.
Concerning the KNOX issue: The phone was never rooted nor modified. I have no idea how the system picked up a rooting process when there was none.
I'll try flashing TWRP... Atleast download mode still works even though everything else doesnt.
Thanks for your reply
Click to expand...
Click to collapse
I LITERALLY had the EXACT same problem.
See the thread here for some ideas: http://forum.xda-developers.com/gal...oft-bricked-s4-gt-i9505-t3430921/post68024954
I didn't mention the green screen and glitching because I didn't see it as relevant.
Just happenstance that it worked eventually.
I flashed the framework and it was successfully, but the system still didn't boot. I tried flashing the framework after a couple of days of persistent failure as a last ditch effort, and it worked, surprisingly, and I cannot explain it fully. I had planned to put the framework on an SD card and use TWRP i.e. recovery to flash it. That's still the best method imo. Try flashing TWRP and doing just that! It should work if there isn't any hardware damage. By the way, I tried older versions of Odin (3.07) when the newer versions didn't work. Additionally, perhaps flashing more recent ROMs would be a better idea (5.0.1, 5.1.1 (if Samsung has bothered updating it to that point)).
Once TWRP ((((or CWM )))) is flashed successfully, boot into recovery mode and do a backup. This should automatically restore the partition table. Then flash the framework file/tar and reboot. If it doesn't work, try flashing different firmware versions (5.0.1, 5.1.1) using the older versions of Odin, say, if TWRP was flashed successfully but the phone still won't boot into recovery.
Alternately, maybe the battery is dying, but I doubt it. Be ABSOLUTELY sure the power button is in perfect condition. The Galaxy S3, S4, Note 4, have a terrible history with defective power buttons causing all sorts of problems.

ThePrick said:
if TWRP was flashed successfully but the phone still won't boot into recovery.
Click to expand...
Click to collapse
Yeah... I flashed TWRP but got the
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRENTY BIT: RECOVERY
stuff instead. Last time I tried flashing a 5.X rom ODIN failed halfwax through so
Then I flashed stock ROM again and it got to the Samsung logo with the jingle but it goddamn crashed again.
Booted into recovery (which suddenly worked) and deleted user data/ cache.
Now it doesnt do anything anymore lol?
Probably broken GPU or NAND corrupting itself every 2 sec.
I dunno.
Samsung should really fix their stuff.

HELP ME IM NOT ABLE TO FLASH STOCK ROM ON GT I9505 <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_OXA_I9505OXAHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!

abdulkareemsid said:
HELP ME IM NOT ABLE TO FLASH STOCK ROM ON GT I9505 <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_OXA_I9505OXAHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Click to expand...
Click to collapse
Try a different USB port and/or cable.

Odin failures can happen when using incompatible USB cables and ports so try everything available.

I Guess I'm the Only One Screwed....

I just bought and received the unlocked S8+ Int'l version (955FD) yesterday. I'm not a newbie to rooting but I'm by no means advanced. I haven't had an unlocked phone in years and was anxious to root it. I tried using CF Root but afterward my phone got stuck on the black setup/title screen with the message "Recover is not SeeAndroid Enforcing." I realized after it was probably because I was already on the latest firmware version (it updated the same day I received the phone).
From this point I tried many things but everything I do in ODIN fails. I noticed that it says "there is no PIT partition" when I try to flash anything and for that reason it keeps failing. I even tried to install a PIT file as suggested here: https://forum.xda-developers.com/showthread.php?t=2659635 but with no success. I've searched on Google for hours and didn't find a way to resolve this issue yet (and I seem to be the only one in this spot).
How do I flash Odin files to get my phone working if there's no PIT which will prevent Odin from failing? UGH :crying:

icydius said:
I just bought and received the unlocked S8+ Int'l version (955FD) yesterday. I'm not a newbie to rooting but I'm by no means advanced. I haven't had an unlocked phone in years and was anxious to root it. I tried using CF Root but afterward my phone got stuck on the black setup/title screen with the message "Recover is not SeeAndroid Enforcing." I realized after it was probably because I was already on the latest firmware version (it updated the same day I received the phone).
From this point I tried many things but everything I do in ODIN fails. I noticed that it says "there is no PIT partition" when I try to flash anything and for that reason it keeps failing. I even tried to install a PIT file as suggested here: https://forum.xda-developers.com/showthread.php?t=2659635 but with no success. I've searched on Google for hours and didn't find a way to resolve this issue yet (and I seem to be the only one in this spot).
How do I flash Odin files to get my phone working if there's no PIT which will prevent Odin from failing? UGH :crying:
Click to expand...
Click to collapse
Look for the newest modded version of Odin. I saw it over day try that
Sent from my SM-G955U using Tapatalk

How about smart switch? Did you try flashing firmware from there?

icydius said:
I just bought and received the unlocked S8+ Int'l version (955FD) yesterday. I'm not a newbie to rooting but I'm by no means advanced. I haven't had an unlocked phone in years and was anxious to root it. I tried using CF Root but afterward my phone got stuck on the black setup/title screen with the message "Recover is not SeeAndroid Enforcing." I realized after it was probably because I was already on the latest firmware version (it updated the same day I received the phone).
From this point I tried many things but everything I do in ODIN fails. I noticed that it says "there is no PIT partition" when I try to flash anything and for that reason it keeps failing. I even tried to install a PIT file as suggested here: https://forum.xda-developers.com/showthread.php?t=2659635 but with no success. I've searched on Google for hours and didn't find a way to resolve this issue yet (and I seem to be the only one in this spot).
How do I flash Odin files to get my phone working if there's no PIT which will prevent Odin from failing? UGH :crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857

I also heared that the very latest Odin will manage that issue.

I think it's the new Odin, try an older version
Also be sure to use the original cable , try USB 3.0 , 2.0, try a different cable , try a different USB host
I feel so sad for you man, the phone still new, it's not a good idea to root it before even trying it for the first time
Sent from my VS987 using Tapatalk

Sorry, I forgot to mention in that I've tried the option in the thread by Nameless no less than 4 times. I realized after I started my own post that I mentioned it not working on that thread instead.

sayyro said:
I think it's the new Odin, try an older version
Also be sure to use the original cable , try USB 3.0 , 2.0, try a different cable , try a different USB host
I feel so sad for you man, the phone still new, it's not a good idea to root it before even trying it for the first time
Sent from my VS987 using Tapatalk
Click to expand...
Click to collapse
I've also tried various versions of Odin, 3.09, 3.10 and the latest 3.12 without success

sayyro said:
I think it's the new Odin, try an older version
Also be sure to use the original cable , try USB 3.0 , 2.0, try a different cable , try a different USB host
I feel so sad for you man, the phone still new, it's not a good idea to root it before even trying it for the first time
Sent from my VS987 using Tapatalk
Click to expand...
Click to collapse
Nameless said:
https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
Click to expand...
Click to collapse
Sorry, I forgot to mention in that I've tried the option in the thread by Nameless no less than 4 times. I realized after I started my own post that I mentioned it not working on that thread instead.

sayyro said:
I think it's the new Odin, try an older version
Also be sure to use the original cable , try USB 3.0 , 2.0, try a different cable , try a different USB host
I feel so sad for you man, the phone still new, it's not a good idea to root it before even trying it for the first time
Sent from my VS987 using Tapatalk
Click to expand...
Click to collapse
I was using the original cable, thanks. I had gotten to use it for a day, but yeah, pretty dumb of me.

njdan30 said:
Look for the newest modded version of Odin. I saw it over day try that
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
I have not tried this yet but I will. I may have to wait until after work this evening. Never heard of modded Odin but just did a Google search. Thanks for the suggestion.

tasked28m said:
How about smart switch? Did you try flashing firmware from there?
Click to expand...
Click to collapse
Not yet. I saw it in another thread but didn't try it yet because I was too scared to be disappointed again. Yeah, I'm crazy. *embarrassed*
Will probably have to try it this evening after work.
Thanks for the reminder.

tasked28m said:
How about smart switch? Did you try flashing firmware from there?
Click to expand...
Click to collapse
I tried it and it wouldn't recognize the phone but when I put it in download mode, it said it was an unsupported device. According to the instructions it seems like you have to be able to at least boot your phone. Sigh
I really can't believe that I'm the only moron who hasn't been able to fix this issue. Everyone that's had it has fixed it. Must be operator error.

icydius said:
I just bought and received the unlocked S8+ Int'l version (955FD) yesterday. I'm not a newbie to rooting but I'm by no means advanced. I haven't had an unlocked phone in years and was anxious to root it. I tried using CF Root but afterward my phone got stuck on the black setup/title screen with the message "Recover is not SeeAndroid Enforcing." I realized after it was probably because I was already on the latest firmware version (it updated the same day I received the phone).
From this point I tried many things but everything I do in ODIN fails. I noticed that it says "there is no PIT partition" when I try to flash anything and for that reason it keeps failing. I even tried to install a PIT file as suggested here: https://forum.xda-developers.com/showthread.php?t=2659635 but with no success. I've searched on Google for hours and didn't find a way to resolve this issue yet (and I seem to be the only one in this spot).
How do I flash Odin files to get my phone working if there's no PIT which will prevent Odin from failing? UGH :crying:
Click to expand...
Click to collapse
Hi
You are not the only one with this problem. I solved it when i root my phone.
First flash TWRP latest version using Odin.
Go to twrp recovery.
In recovery go to wipe option.
Select data and click on format
Change its type to Fat32 done
Again select data an format it in ext4 file type.
And last go back select wipe
Type yes
Ok
Then see in backup option
Is internal storage show its size or not if yes
Flash supersu zip file to root your phone.
And reboot
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
drparvez said:
Hi
You are not the only one with this problem. I solved it when i root my phone.
First flash TWRP latest version using Odin.
Go to twrp recovery.
In recovery go to wipe option.
Select data and click on format
Change its type to Fat32 done
Again select data an format it in ext4 file type.
And last go back select wipe
Type yes
Ok
Then see in backup option
Is internal storage show its size or not if yes
Flash supersu zip file to root your phone.
And reboot
Click to expand...
Click to collapse
You received this message because your 64GB internal storage was corrupt. You have to reformat it.

njdan30 said:
Look for the newest modded version of Odin. I saw it over day try that
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
The only download I can find is here http://d-h.st/gsDA and it keeps giving me a time out error that the page took too long to long to respond.
Although I'm not convinced it will work, I'll be dumb and try it. Can you suggest some place to find an Odin mod?

drparvez said:
Hi
You are not the only one with this problem. I solved it when i root my phone.
First flash TWRP latest version using Odin.
Go to twrp recovery.
In recovery go to wipe option.
Select data and click on format
Change its type to Fat32 done
Again select data an format it in ext4 file type.
And last go back select wipe
Type yes
Ok
Then see in backup option
Is internal storage show its size or not if yes
Flash supersu zip file to root your phone.
And reboot
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
You received this message because your 64GB internal storage was corrupt. You have to reformat it.
Click to expand...
Click to collapse
I have tried flashing TWRP recovery yesterday twice as well but as everything else I did using ODIN, I got the FAIL after pressing START.
Are you saying I should reformat it before I flash TWRP because nothing works using ODIN? Anything I try to flash fails. Thanks

I'm running late for work so I'll check back later. Thanks for everyone's help so far!!

icydius said:
I have tried flashing TWRP recovery yesterday twice as well but as everything else I did using ODIN, I got the FAIL after pressing START.
Are you saying I should reformat it before I flash TWRP because nothing works using ODIN? Anything I try to flash fails. Thanks
Click to expand...
Click to collapse
Use this method to flash twrp
Go to download mode
Uncheck reboot option in odin
flash twrp file
Press 3 button combination to reboot it when it boot hold volume down bixby button to go download mode again tben flash the same file with uncheck reboot option in odin.
Flash twrp file boot it and again go to download mode.
Now this third time flash the file normally with reboot option.
Hope this will fix your issue.
Best of luck

Okay, so I'm home and was able to try this. I got the same results = FAIL. I think I should clarify what happened.
My S8+ was on the latest firmware (AQF7) and I didn't read enough to find out that CF Auto Root could only be used on the previous firmware. When I flashed CF Auto Root using ODIN and the phone rebooted, it got stuck on the S8+ title/boot which shows "Recovery is not Seandroid Enforcing."
Since then, I've tried to flash TWRP and all of the suggestions listed above (all but one I tried before I started this post) and ALL fail because ODIN said something about the PIT partition. Now it seems it doesn't mention the PIT partition since I'm using ODIN 3.12 but it still fails.
<ID:0/003> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried flashing the previous firmware as well (see copied and pasted text) but again unsuccessfully.

icydius said:
Okay, so I'm home and was able to try this. I got the same results = FAIL. I think I should clarify what happened.
My S8+ was on the latest firmware (AQF7) and I didn't read enough to find out that CF Auto Root could only be used on the previous firmware. When I flashed CF Auto Root using ODIN and the phone rebooted, it got stuck on the S8+ title/boot which shows "Recovery is not Seandroid Enforcing."
Since then, I've tried to flash TWRP and all of the suggestions listed above (all but one I tried before I started this post) and ALL fail because ODIN said something about the PIT partition. Now it seems it doesn't mention the PIT partition since I'm using ODIN 3.12 but it still fails.
<ID:0/003> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried flashing the previous firmware as well (see copied and pasted text) but again unsuccessfully.
Click to expand...
Click to collapse
Did you try my method flashing twrp 3 times without let your phone boot.
Try this.

Downgrade Nougat to marshmallow 6.0

Hi
Please it's possible back downgroad to marshmallow ?

stootie said:
Hi
Please it's possible back downgroad to marshmallow ?
Click to expand...
Click to collapse
Not as of now, as the bootloader has been updated on exynos variants in january update patch. If you haven't updated to january patch, you could downgrade using odin, but be sure to check repartition and select CSC in csc tab of odin, NOT THE CSC_HOME.
Sent from my S7 Edge using XDA Labs

Thanx for answer !
I don't update the patch january

shah22 said:
Not as of now, as the bootloader has been updated on exynos variants in january update patch. If you haven't updated to january patch, you could downgrade using odin, but be sure to check repartition and select CSC in csc tab of odin, NOT THE CSC_HOME.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Well, in theory it is. I just done it, after I upgraded to newest bootloader. The only thing is (at the moment) vibration does not work on Marshmallow. Everything else seems to be fine.

I'm surprised they would block downgrading with the january update patch.

Cholek3 said:
Well, in theory it is. I just done it, after I upgraded to newest bootloader. The only thing is (at the moment) vibration does not work on Marshmallow. Everything else seems to be fine.
Click to expand...
Click to collapse
were you able to flash old firmware after flashing the jan 2018 update..?if yes .how ? i tried everything was able to flash but the most of the system apps force closes and not able to use the phone .

saurabh808 said:
were you able to flash old firmware after flashing the jan 2018 update..?if yes .how ? i tried everything was able to flash but the most of the system apps force closes and not able to use the phone .
Click to expand...
Click to collapse
I flashed BL and CP (BTU) from newest firmware and AP and CSC from desired old firmware (BTU). In that case it was going back to MM. Aparat from no vibration, no other issues found.

i tried downgrading once ,, camera didnt work

No issue with camera here, at all.

so is there any way to downgrade after installing January security update?

TBS2002 said:
so is there any way to downgrade after installing January security update?
Click to expand...
Click to collapse
Read post #7

Cholek3 said:
Read post #7
Click to expand...
Click to collapse
after done lateraly what they say in #7 the devive refuse to boot and stays on the logo screen
so now what ? my device is 7 edge with model sm-g935f?
---------- Post added at 12:32 PM ---------- Previous post was at 12:24 PM ----------
Please anyone can you send me the marshmallow and nougat flash files for the model 7 edge sm-g935f M

TBS2002 said:
after done lateraly what they say in #7 the devive refuse to boot and stays on the logo screen
so now what ? my device is 7 edge with model sm-g935f?
---------- Post added at 12:32 PM ---------- Previous post was at 12:24 PM ----------
Please anyone can you send me the marshmallow and nougat flash files for the model 7 edge sm-g935f M
Click to expand...
Click to collapse
Just flash now newest firmware (all files) and make sure you use CSC files (not home_csc).

Cholek3 said:
Just flash now newest firmware (all files) and make sure you use CSC files (not home_csc).
Click to expand...
Click to collapse
I have made it and now we are at the point 0.
my phone is looked with FRP and the problem is that I have forgotten the last email and I want to open it ?also i have updeted it with January 2018 update accidentally

Frp lock lasts something between 24 and 72 hours. So you have to wait. In the meantime, you can try flashing again (BL and CP you just used, and AP and CSC, not home_csc, of old software of you desire).

Thanks for the guide I used it successfully to get to Marshmallow as I wanted to get the Galaxy Labs feature, I now want to get back to Nougat but when I use the automatic update it says that I am on the latest version.

Hey, i have a S7 Edge, but my issue is the same: odin.
I try to root S7 Edge, now my Wlan, my Camera doesn’t work and my screen is to half red.
Now i try to flash my phone to 6.0.1 with G935FXXU1BPLB
The driver of Smart Switch and Kies are installed, but deinstalled and the Driver Booster installed the last driver what i need.
On my Download Screen stay:
Produkt Name: SM-G935F
Current Binary: Custom
System Status: Custom
Fap Lock: OFF
Secure Download: Enabled
Warranty VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
SW REV, Check Fail. Device: 2. Binary: 1
Allte the same Odin v3.12 Log:
<ID:0/005> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/005> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After i googled, someone says that i should do a factory reset, now my phone can start and the Bootloop is gone, but i have the same error like before.
Every times when i try to flash 6.0.1 i get the same error like above, what should i do ?
How can i fix my Camera Issue?
How i can flash Mashmellow and deinstall the false SuperSu version ?

No work for me
i tried it several times and always it stuck on boot.. And i can only enter download mode...
Maybe you have some idea??
I use:
NEW:
BL_G935FXXS2DRAA_CL12365438_QB16535167_REV00_user_low_ship.tar.md5
CP_G935FXXU2DRA9_CL648265_QB8671796_SIGNED.tar.md5
Old:
AP_G935FXXU1APAW_CL7042588_QB8405580_REV00_user_low_ship.tar.md5
CSC_OXX_G935FOXX1APB1_CL7114241_QB8433836_REV00_user_low_ship.tar.md5
Maybe it is something wrong with this file??
It's a mystery to me..

But flash custom rom MM over newest Nougat is possible? I reached max 2h40min with last update, battery is new, 3 full chargings. On MM battery life was much better ...
LE : After flashing SupermanROM V1.15.5 over stock rooted nougat, with last security patch from march(i think), vibration doesn't work and on "Always On Display" no icon for notifications.. I tried to flash BL and CP but not working .. I will try more next week ...

Cholek3 said:
No issue with camera here, at all.
Click to expand...
Click to collapse
I flashed as you said and it went well on Odin, but it wont boot from the galaxy edge logo. is there any solution for it?