Database Info

[Q] Problem with Soft-Bricked SideKick 4g

Hello everyone, before I start, I want to let everyone know I have searched endlessly for a fix, etc.
I have a SideKick 4G that I purchased maybe a month ago, and yesterday I went ahead and tried to flash a custom ROM on it. Now my issue is, I was hap-hazardly strolling through the menus and doing the procedure so I didn't back anything up or check the mounts etc.
My issue is, I have Odin and the sk4g.pit file, but I can't find the KD1OdinSTOCK.tar or KG2OdinSTOCK.tar files, because the file hosts are down... permanently.
I also do not know if I have the KD1 or KG2 firmware, what the difference is, and if any problems could be caused by flashing one or the other onto my device. I'm pretty new to the whole process and I was only looking to make my phone faster and less clunky.
If I get the files, a quick walk-through for my specific situation would be very highly appreciated.
Thanks in advance!
EDIT: I found a newer firmware for the SideKick 4G, called KH1, Not KD1, KG2, or KJ1.
To get the file:
1) Go to SamFirmWare.com and make an account
2) Search T839UVKH1
3) Make sure you find the firmware for this model. "SGH-T839"
4) Download it
5) Make sure to look for what password you'll need to open the file (This one is marked with "##")
6) Input password when extracting the file to wherever you want to put it (The password for this one is samfirmware.com)
That should be it.
My issue now is that Odin isn't recognizing my device. It's in download mode and I have the factory cable but I must be doing something wrong as I can set the PIT file and the PDA file, tick boxes etc. but I can not for the life of me get my device detected.

Alright, later update.
I got Odin to recognize my phone, and now I'm trying to flash it.
I don't seem to be having any negative impact with my firmware (KH1) and sk4g.pit, however it always fails at write boot.sbl OR, it gets stuck at Set PIT file.
My phone changed from the Downloading... mode to the Phone - ! - PC picture, however, I was told I can still flash from this mode. I've been continuing to flash with different settings in hopes of reaching recovery, and so far what has NOT worked:
Auto Reboot
Auto Reboot + Re-Partition
Auto Reboot + Re-Partition + F. Reset Time
I don't believe I've tried Auto Reboot + F. Reset Time without Re-Partition, or Re-Partition with F. Reset Time.
Any advice or comments?

Update #2.
http://forum.xda-developers.com/showthread.php?t=1350060&page=6
This thread seems to have a link to a oneclick stock recovery as well as KG2 firmware, judging by the 254 MB download (THAT WORKS BY THE WAY.)
Hopefully after I download this, I can get the phone running. Will post later to inform a yay or nay.
Edit: I almost successfully flashed to stock KG2 Firmware. All went well (Kernal, Recovery, etc) Except it failed at the modem.
It rebooted after failing modem and now I'm stuck at sidekick boot logo. It's better than having Phone - ! - PC though.
EDIT 2: Seems that it keeps failing at Modem, part 3 of 6. along with that, it does restore the phone to Download mode rather then the broken sync picture. Odin now does not recognize the phone, but I think that's due to the other drivers the oneclick method prompted me to install. I'm going to try to disable those drivers temporarily and see what odin thinks about it.

Update #3.
I discovered the drivers downloaded to run the oneclick as provided by the link in the previous update did infact block connection to odin with the same device.
Uninstalling the driver got the connection going again. Every time in Odin, I fail at writing either boot.sbl or cache.rfs.
I took the files from the KG2 firmware and compiled my own .tar out of them and when I flashed using my compiled tar, that's when I got the cache.rfs write error. Phone has shown no signs of improving or deteriorating. I can go back to oneclick recovery and get the phone out of broken sync picture mode, and back into Download mode. However, here are my 2 issues flashing.
In Odin:
I either have no connection, or
I can't write boot.sbl or cache.rfs and fail.
In Heimdall One-Click KG2:
I need the driver Odin doesn't like, and
I flash almost all the way through, but fail halfway through uploading MODEM.bin.
It's giving me the opportunity to flash Boot Loaders along with KG2 kernal, recovery, modem, etc. It's the only thing I haven't tried yet.

Update #4.
I'm about to flash bootloaders. Wish me luck
EDIT: I'm about to cry :') I THINK IT WORKED. I'm loading boot screen.. got animation and now got samsung screen, waiting for the phone to boot. got a fully successful oneclick and it's looking well at the moment
YEAH!!!!!!!!!!!!!!!!!!!! HOME SCREEN!!!!!

Nice monologue.

Thank you sir. What do you think of the things I did to get my phone working again? Anything you think I shouldn't have done? o_o''

No download mode, no recovery, detected by odin, not kies

Hi,
I rooted my brandnew GT-P3110 with cf, flashed pacman and cwm recovery. I do not blame anybody alse for my issues but myself. I guess I messed up the restoring of NON-system-apps:
After a day of troublefree use the tablet randomly rebooted and came back with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". No booting into recovery possible, no booting into download mode, no regular boot. Just the same message over and over again. Battery is unremovable.
I installed Kies, updated it, it downloaded drivers but under "emergency recovery" my tablet didn't appear. I then followed the "Firmware Upgrade and Initialization" procedure wich downloaded the necessary files but aborted with a korean text shown in the attachment after replugging the tablet. I tried this with 2 different USB-cables on several USB-ports. Kies btw asked me to remove the battery (not possible) after entering device number and serial-number. I turned off by pressing the off button instead and it turned on again.
I uninstalled Kies, rebooted, installed the samsung drivers manually, rebooted. I installed odin 1.85 (and later 1.3) and downloaded my contry's stock firmware (and later a newer version of the same firmware and another country's stock) from sammobile. I tried to flash them first without "repartition" ticked, later with it ticked but without a pit file (i can't find it!). I got four different errors, two are attached, the third was somethign like "cant write (line 1876)" and "cant write (line 1440)".I tried three stock firmwares with two version of odin with two USB cords on everal ports on ONE computer. I remove the tablet every time, exited odin every time, run it as admin, disabled firewall, xp-antispy and antivirus. I'm on Windows 7.
Besides a million other threads I found this one, but I wasn't able to solve my issue with it: http://forum.xda-developers.com/showthread.php?t=1652398
For 48 hours i tried to solve this problem by myself. Now I hope to find out if there's a point in continuing or if I can give up and throw away the piece of samsung.
Cheers,
404

android404 said:
Hi,
I rooted my brandnew GT-P3110
404
Click to expand...
Click to collapse
Try odin 1.61 1.85 sometimes itll jar it loose

vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?

vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
Thanks but it didn't work.
wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Mine is still bricked. Good luck.

facing same problem in my samsung tab 2 p3100 after root

wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.

novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
Click to expand...
Click to collapse
Thanks. Well, I understand the theory. I have had trouble finding a PIT file that I am sure is for my device. I did save a PIT file but I think it is corrupt because using it requires me to let the battery die afterwards to get back to download mode. Same for the bootloader. I have a few things I've tried, but not sure I have one that is exactly for the GT-P5113 (in fact, I never did find a JB for the 5113 just the 5110 and it never would load).

Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.

I can do each thing you mentioned, but my device is not getting detected by my PC. When I insert USB it says USB not recognized and it is not detected by Odin, adb and anything else. I am stuck on Boot Logo for my P3100 and when I go into recovery, it says USB not recognized. Fully messed up. Can you help me out here.
novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.
Click to expand...
Click to collapse

2 years later .... did you ever unbrick this? I'm dealing with a P5113 now that's stuck at the "Firmware upgrade encountered an issue" screen. <sigh>
wd5gnr said:
Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.
Click to expand...
Click to collapse

No. I finally sent it to one of these ebay guys who will JTAG it since I was too lazy to wire up one of my JTAG probes. They worked on it and said it was simply dead and the only alternative would be to replace the flash chips.
Bought a Nexus 7.

I've got the pit files for P311x and P3100 on my website https://sites.google.com/site/jrc2swebsite/downloads/samsung-galaxy-tab-2-70-p31xx

Firmware upgrade encountered an issue

First off: Ive searched the forum and there are a few similar posts to my problem but I thought I would ask my question before trying any of the things Ive found because I think its in this mess because Ive messed somehting up so dont want to make it worse.....
So I got given an AFAIK unrooted GT-P5100 (from Belgium) by my friend to try and fix as they had got the Interpol/ FBI thing on it. So i looked around the web and tried Safe Mode but couldnt get that to work at all so I thought I would just do a factory reset. So I got into the options by pressing volume up or down (whichever one it is) and selected wipe cache partition it displayed "erasing" then followed by "error" and the tablet rebooted back to the Interpol screen. Then I tried wipe data/factory reset it seemed to go through it very quickly, no errors displayed and then it either rebooted automatically or I selected reboot I cant remember, but straight back to the Interpol screen.........
Then I thought Odin, Ive used it in the past to flash custom ROMs on my rooted phones...
I downloaded the firmware from sammobiles - P5100XXDNA1_P5100PRODNA1_P5100XXDMG1_HOME.tar.md5
I followed these instructions with odin v3.10
- Run Odin3.exe
- Click on PA button and Select the firmware file.
- Connect your phone to PC via USB cable, And wait until Odin3 detects the phone.
- Click on Start button and wait until the operation done.
All seemed to be going OK, it added it on Com3 and several bits of text appeared saying success
Then Odin came up with fail when it seemed to be abou 90% of the way across, the bar stopped on the tablet and didnt move. Im guessing at this point I should have asked for help
Like a muppet I also closed Odin before I took a screenshot... doh!!!!!!
After a while I disconnected the cable and tried to put it back into download mode but all that comes up on the screen now is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
So I installed Kies and tried recovery mode but it doesnt detect the tablet at all.
Odin can still connect, this time on Com5
I've read about installing TWRP through Odin, is this something I should try or have I just trashed this tablet now?
Thanks for any advice!!

SM-G920T: Custom binary blocked by FRP Lock [FIXED]

This is my first experience with rooting a phone and I think I messed up...big time! All I wanted to do was get rid of preloaded garbage on the phone to save battery life. Now I have a red message, "Custom Binary blocked by FRP lock".
My G920T was completely stock until today when I loaded CF_Auto_Root into it with Odin.
The phone immediately went into a boot loop after the install. I was able to boot into device recovery and did a factory reset at that point. I didn't know until after I reset to factory that I had accidentally installed Auto_Root for the G920F.
No problems here, booted back into initial setup, and I completed all of the setup items. Logged into Google, Samsung, etc. Because this was my first time and ended with a boot loop, I decided I'd just deal with the battery life problems. I turned off USB Debugging and the Bootloader modify option. The phone seemed to be working normally until I unplugged the phone from my computer, plugged it into wall fast charger, the rebooted the phone.
Now all I get is the Samsung home screen with the red message in the upper left corner. It will continually loop between the home screen and a black screen if the phone is plugged in. I cannot get back into the recovery menu as the phone is unresponsive to home + power + vol. up. I can however boot into the download menu.
I have tried reflashing the stock tar file, a stock bootloader, and stock modem with Odin 3.10.6 and 3.10.7. When I attempt the reflash I get the failed message in Odin, and "SW Rev. Check Fail. Device: 3. Binary: 2.
Are there any other options I have at this point, or something I'm doing wrong or incompletely?
Thanks
Edit:
I have fixed the phone after about 10 hours of messing around with stock firmwares, Odin, Smart Switch, Kies, etc. If the option was there, I tried it.
The FRP Lock is easily fixed by flashing in the stock firmware, but it must be the version the phone was at before rooting. This seems to be pretty common knowledge but my problem was I didn't know which version I had. I started with 0F6, that didn't work because I would then get "sw rev check fail device 3 binary 2" in the download screen and Odin would show a red fail almost immediately.
At this point I was getting pretty beat up by the phone and was trying anything I could find. I noticed, when entering the download menu before you press the vol. up button, that you can press the home key and the phone will show the barcode. This was the turning point for fixing my phone. It was in the barcode screen that I found my phone's S/N. Perhaps it is located other places, like behind the battery I can't remove, or on a carriers website (checked T-Mobile and didn't see it), but this is where I found it. I then remembered that Smart Switch had an option for 'Emergency software recovery and installation'. When you enter that menu the program asks you for your phone's model number, then the phones S/N. I could now use this option because I had the required info. I thought I was making progress but this method failed at 60% of downloading the software and drivers and an error in the download screen of "sw rev check fail device 3 binary 2".
The key for Smart Switch is, after you enter your model number and serial number, the program tells you what firmware version the phone was at. The 3 fields that pop up all read "OJC". More progress! The firmware version I was trying to install, which was the newest one I could find without knowing what to look for, was 0F6. I found the OJC .zip file at sammobile.com. It took 2 hours to download to 95% and the download failed. Restarted the download and waited 2 more hours.
While the OJC was downloading I was still messing with options I was reading about from google searches. I read multiple times to try different versions of Odin, try different USB ports, try different sequences of loading/connecting device to pc. I changed USB ports on the PC and the samsung drivers started installing for the device. A second driver installed this time for Samsung Modem 2 (I only particularly remember the Modem 2 part) that I didn't see install on the other USB port. At this point I decided to try Smart Switch again. This time, with the extra driver, the download completed to 100% and started to install some files onto the phone. But, it only got to 20% installed and erred again. This time the error was "sw rev check fail device 3 binary 1". I also noticed that the Current Binary field on the download screen changed from "custom" to "Samsung Official". More Progress. At this point there was nothing more I could do until the OJC was finished downloading.
As soon as I unzipped the OJC I opened Odin v3.10.7 and loaded the firmware into the AP, plugged in the phone, hit start. Red Fail. Then tried loading the firmware with Odin v3.10.6. Loaded OJC into the AP, connect device, hit start. Red Fail, but, I made it past the Nand Write Start and got all the way down to the system installation part before it failed. More Progress! Tried v3.10.7 again and didn't make it past Nand Write before it failed again. Then I started changing the order of when I opened Odin, loaded the firmware, and connected the device. There are tutorials everywhere that specifically say, "CONNECT IN THIS ORDER OR THE FLASH WONT WORK", I found this to not be entirely true.
How I eventually got the OJC firmware loaded back onto the phone was to Restart the phone into the Download screen, connect phone to pc and wait for Odin to recognize the device, then load OJC into the AP, hit start. In v3.10.7 the install failed every way I tried at different points in the install. v3.10.6 is the one that ended completely re-flashing the phone to stock OJC firmware.
If you're new, or stuck, make sure you do the following:
- Verify you are trying to load the correct firmware with smart switch. (OJC is the last 3 characters of the file names)
- Try different versions of Odin
- Try different orders of setup processes
- Try different USB ports and MAKE SURE you have all Samsung device drivers installed

I might add .. don't forget to run ODIN as administrator.
Also, to avoid this in the future, disable the OEM Lock in Developer Options.

YOUR AN ANGEL :d

Hello there. I got "Custom Binary(RECOVERY) Blocked By R/L, I have odin and firmware but odin can`t see my phone. What i have to do?

1sicgsr said:
This is my first experience with rooting a phone and I think I messed up...big time! All I wanted to do was get rid of preloaded garbage on the phone to save battery life. Now I have a red message, "Custom Binary blocked by FRP lock".
My G920T was completely stock until today when I loaded CF_Auto_Root into it with Odin.
The phone immediately went into a boot loop after the install. I was able to boot into device recovery and did a factory reset at that point. I didn't know until after I reset to factory that I had accidentally installed Auto_Root for the G920F.
No problems here, booted back into initial setup, and I completed all of the setup items. Logged into Google, Samsung, etc. Because this was my first time and ended with a boot loop, I decided I'd just deal with the battery life problems. I turned off USB Debugging and the Bootloader modify option. The phone seemed to be working normally until I unplugged the phone from my computer, plugged it into wall fast charger, the rebooted the phone.
Now all I get is the Samsung home screen with the red message in the upper left corner. It will continually loop between the home screen and a black screen if the phone is plugged in. I cannot get back into the recovery menu as the phone is unresponsive to home + power + vol. up. I can however boot into the download menu.
I have tried reflashing the stock tar file, a stock bootloader, and stock modem with Odin 3.10.6 and 3.10.7. When I attempt the reflash I get the failed message in Odin, and "SW Rev. Check Fail. Device: 3. Binary: 2.
Are there any other options I have at this point, or something I'm doing wrong or incompletely?
Thanks
Edit:
I have fixed the phone after about 10 hours of messing around with stock firmwares, Odin, Smart Switch, Kies, etc. If the option was there, I tried it.
The FRP Lock is easily fixed by flashing in the stock firmware, but it must be the version the phone was at before rooting. This seems to be pretty common knowledge but my problem was I didn't know which version I had. I started with 0F6, that didn't work because I would then get "sw rev check fail device 3 binary 2" in the download screen and Odin would show a red fail almost immediately.
At this point I was getting pretty beat up by the phone and was trying anything I could find. I noticed, when entering the download menu before you press the vol. up button, that you can press the home key and the phone will show the barcode. This was the turning point for fixing my phone. It was in the barcode screen that I found my phone's S/N. Perhaps it is located other places, like behind the battery I can't remove, or on a carriers website (checked T-Mobile and didn't see it), but this is where I found it. I then remembered that Smart Switch had an option for 'Emergency software recovery and installation'. When you enter that menu the program asks you for your phone's model number, then the phones S/N. I could now use this option because I had the required info. I thought I was making progress but this method failed at 60% of downloading the software and drivers and an error in the download screen of "sw rev check fail device 3 binary 2".
The key for Smart Switch is, after you enter your model number and serial number, the program tells you what firmware version the phone was at. The 3 fields that pop up all read "OJC". More progress! The firmware version I was trying to install, which was the newest one I could find without knowing what to look for, was 0F6. I found the OJC .zip file at sammobile.com. It took 2 hours to download to 95% and the download failed. Restarted the download and waited 2 more hours.
While the OJC was downloading I was still messing with options I was reading about from google searches. I read multiple times to try different versions of Odin, try different USB ports, try different sequences of loading/connecting device to pc. I changed USB ports on the PC and the samsung drivers started installing for the device. A second driver installed this time for Samsung Modem 2 (I only particularly remember the Modem 2 part) that I didn't see install on the other USB port. At this point I decided to try Smart Switch again. This time, with the extra driver, the download completed to 100% and started to install some files onto the phone. But, it only got to 20% installed and erred again. This time the error was "sw rev check fail device 3 binary 1". I also noticed that the Current Binary field on the download screen changed from "custom" to "Samsung Official". More Progress. At this point there was nothing more I could do until the OJC was finished downloading.
As soon as I unzipped the OJC I opened Odin v3.10.7 and loaded the firmware into the AP, plugged in the phone, hit start. Red Fail. Then tried loading the firmware with Odin v3.10.6. Loaded OJC into the AP, connect device, hit start. Red Fail, but, I made it past the Nand Write Start and got all the way down to the system installation part before it failed. More Progress! Tried v3.10.7 again and didn't make it past Nand Write before it failed again. Then I started changing the order of when I opened Odin, loaded the firmware, and connected the device. There are tutorials everywhere that specifically say, "CONNECT IN THIS ORDER OR THE FLASH WONT WORK", I found this to not be entirely true.
How I eventually got the OJC firmware loaded back onto the phone was to Restart the phone into the Download screen, connect phone to pc and wait for Odin to recognize the device, then load OJC into the AP, hit start. In v3.10.7 the install failed every way I tried at different points in the install. v3.10.6 is the one that ended completely re-flashing the phone to stock OJC firmware.
If you're new, or stuck, make sure you do the following:
- Verify you are trying to load the correct firmware with smart switch. (OJC is the last 3 characters of the file names)
- Try different versions of Odin
- Try different orders of setup processes
- Try different USB ports and MAKE SURE you have all Samsung device drivers installed
Click to expand...
Click to collapse
HOW can i get The Serial NUMBER AND WRITE IT DOWN ON SMART SWITCH OR KIES ?? IF IT IS A BARCODED IN THE DEVICE ?!??!

Likebeast said:
HOW can i get The Serial NUMBER AND WRITE IT DOWN ON SMART SWITCH OR KIES ?? IF IT IS A BARCODED IN THE DEVICE ?!??!
Click to expand...
Click to collapse
smh, there is number on top of barcode that saids S/N
After Reading this post i felt dumb, because I thought imei on back of my phone was S/N whole time
I used SmartSwitch Emergency software recovery and installation, went through 2 cycles of installation somehow and it finally fixed my phone.
I'm using SM-920T galaxy S6

Hey sir did u just flash the stock rom u downloaded and it fix the frp lock?? I need ur help i also accidentally activated the oem.. please helppp sir

SOLVED: N986B/DS KSA and Odin is failing to flash. Would greatly appreciate assistance. Thanks!

Condensed for brevity:
Unlocked bootloader and Debug USB enabled. Went to flash an AP and it failed. Tried to use Frija to get the most recent update, found N986BXXS3EULH REV01, tried to flash the AP/BL/CP/CSC to refresh the phone and it's failing.
Everything matches my phone when I typed *#1234# (EULB/EULH) except the download has REV01 added to the end.
Phone is stuck in download mode no matter how I reboot it. Phone isn't bricked but won't do anything else.
Edit: Updated to using Odin 3.14.4 instead of 3.13.1
Edit 2: Figured out the phone is freezing after any fail (brightness doesn't change with volume keys). I get the failed PIT as well as "Can't open specified file (Line:2006)"
Edit 3: Re-opened Frija and it gave me an entirely different FW this time that superseded what I had on the phone originally and the DL'd file (*3EULH became *3EVA9).
Tried to use new CSC and it keeps failing at prism.img. It's progress but not really at the same time.
Edit 4: It lets me install the BL and CP for either/or EULH or EVA9 but neither CSC or AP work ever. I'm thinking I just have a bad firmware or something.
Final update for the night: The files are good. Compared hashes across multiple downloads. Phone isn't seen in Samsung Smart Switch and there doesn't seem to be a recovery menu. TWRP or otherwise.
If anyone has any ideas please let me know. I'm pulling my hair out because it's brand new. All I did was try to start by updating the stock firmware with Odin (after bootloader unlocking and USB debug enabling) and this happened.
-------------------------------------------------------------------------------------
Day 2: Moved back to Odin 13.1 and extracted PIT from EULH CSC, installed it, then did the BL/CP, installed fine. Still froze with CSC/AP. Then attempted to try it all at once. PIT, CP, BL, CSC, and AP. It actually starts installing now. But it specifically always freezes at the super.img portion. So while I'm unsure what's going on now since I'm still trying to install the correct official ROM, I'm starting to think the ROM is somehow incompatible with my phone.

HERE'S THE ANSWER! Many thanks to those who attempting to help. We were doing and advising everything correctly.
The problem is the PC itself. Which was why the issues seemed so varied. I attempted every USB in my computer, none would flash (they drop out randomly with my phone), and the first sign I didn't realize was a sign was the phone wouldn't work on my USB-C ports, only 3.0/3.1.
I run a Threadripper 3960x on an Aorus TRX40board. I had to go to a 2015 touchscreen laptop to do this. If you're having issues then literally try a new PC if possible. If you see that it isn't connecting to Odin on USB-C, then you may well have the same issues I was having.
Note: this may be a driver issue, as I used every one of my 20-ish ports and they all still failed, as well as about 5 different cable options to go between USB/USB to C and USB-C to USB-C.