Database Develop

Need Help, Bricked SM-T900

I bricked my SM-T900 Wifi while attempting to root it. Can anyone help me get it un-bricked?
Here's a step by step list of what I did and what happened:
1. Turned on USB debugging mode
2. Downloaded and installed Samsung kies
3. Downloaded the file for SM-T900 from autoroot [dot] chainfire [dot] eu/ (it won't let me post outside links)
4. Turn off tablet, get into custom firmware installation mode by holding power, volume-, and home, then confirm the warning
5. run Odin (v3.07, came in the zip file)
6. plug in tablet, tablet showed up as a com port but did NOT show any other information. I don't know if it was supposed to show anything else but I hadn't though about that at the time.
7. Clicked on PDA and selected the file CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5
8. Clicked start
9. Waited, it said it was doing something with cache, I don't recall exactly what it said
10. after about 3 minutes the screen looked wrong, all the pixels were different colors, (rainbow static?)
11. Waited about 10 minutes just in case that was not a sign of failure, then Odin reported that it failed.
Now when I press the power button, I get the screen that says "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I tried using that in Kies but Kies can't connect to my tablet any more. When I try to use Odin using the recovery with power, vol-, home, it detects that I plugged it in but when I try to click start it fails and nothing happens.

I have exact the same problem.
I have read many articles, who said it was easy to root.
That's not true !!!!.
Maybe because the tablet became an update today ?
What I did to recover the tablet: (phew !!!)
Download this bootloader:
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
Connect to Odin and flash it.
A few seconds, it says OK, reboots and voila: there's your tablet again revived !!!!.

rumaro said:
I have exact the same problem.
I have read many articles, who said it was easy to root.
That's not true !!!!.
Maybe because the tablet became an update today ?
What I did to recover the tablet: (phew !!!)
Download this bootloader:
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
Connect to Odin and flash it.
A few seconds, it says OK, reboots and voila: there's your tablet again revived !!!!.
Click to expand...
Click to collapse
Unfortunately Odin fails before it manages to even connect to my tablet so I'm not sure it will work for me but I'll give it a try. It managed to connect before when I tried to flash the root files but now it fails every time. I'll update this when I get home and try flashing that.
Edit:
Got home, tried your fix. I am happy to report it worked and it only took a few seconds. Thanks!
Edit:
To anyone reading this thread, if you tried rooting your SM-T900 using the SM-T900 files for rooting, try using the SM-P900 files instead! I just tried that and it seems to be working fine.

I'm glad I could help. :good:
It's bad for your heart when you see that your expensive tablet is bricked.

Hello everyone. Where do I flash the bootloader in odin? Do I use PDA or Bootloader and do I need to check the bootloader update box? Just wanted to confirm before further messing up my tablet. Thanks!
Edit: Never mind, figured it out. Thanks for the help!

This method just worked for me. Flashed the bootloader with Odin after getting "stuck" and it booted right up.
Jim

sizedlemming65 said:
Hello everyone. Where do I flash the bootloader in odin? Do I use PDA or Bootloader and do I need to check the bootloader update box? Just wanted to confirm before further messing up my tablet. Thanks!
Edit: Never mind, figured it out. Thanks for the help!
Click to expand...
Click to collapse
What did you do exactly to fix it? I'm having the same issue. Just sits at screen and says:
ODIN MODE
Product Name: SM-T900
Current Binary: Custom
System Status: Official
KNOX Warranty Void: 1
RP SWREV: A1
How do you use that recovery.img file?

For the top most problem flash cwm or TWRP recovery through Odin or through recovery mode then boot into cwm or TWRP recovery delete all files and install a supported rom.
If u want full explained steps mail me
- [email protected]
Sent from my SM-J500F using XDA Forums

it's 2022 & my T900 finally went into bootloop in model logo, does anyone know the real reason for this? is it hardware or software problem?
- I can flash any version via odin but still bootloops
- TWRP worked once after that can't get in anymore
- the only button working is for the download mode PWR + Vol Down
- before all this LED Stayed on until batt drained then bootloops
it's a good tab to watch movie while on a treadmill

[Q] Help Note 4 Bricked - Binary Blocked by Reactivation Lock & Boot Loops

I rooted my T-Mobile Galaxy Note 4 early last week using Odin v3.09 and cf auto root and flashed TWRP recovery using Odin. I disabled Knox as SuperSU suggested, and I created a back up after root. Saturday I flashed Dynamic Kat v 3.0, and go everything set up the way I wanted it. I didn't mess with any of the security settings, other than setting a pin for the lockscreen. This morning I rebooted into recovery to create a back up, but instead of going to recovery, I got a black screen with an exclamation point and an error message saying Custom binary blocked by Reactivation Lock. Secure Fail: Recovery that would just keep looping when I tried to restart it. I tried pulling the battery and restarting, but still had the same message at restart. I then tried to run odin and cf autoroot again, but got the same message and Odin said that it failed. Now the phone just keeps boot looping on the Samsung Galaxy Note 4 powered by android screen.
If I go to the download mode the top of the screen says:
Odin Mode (High Speed)
Product Name: SM-N910T
Current Binary: Custom
System Status: : Custom
Reactivation Lock(KK): On
Knox Warranty Void: 0x1 (4)
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download : Enable
UDC Start
How can I fix this, what can I do?

Get a stock odin flashable and start over from downloadmode...
Tryna find that link or it may be samsmobile
Look here.
http://forum.xda-developers.com/showthread.php?p=55968427
If your pc does not see the phone in download mode then you need to run kies emergency firmware recovery..

Flashvetrin said:
Get a stock odin flashable and start over from downloadmode...
Tryna find that link or it may be samsmobile
Look here.
http://forum.xda-developers.com/showthread.php?p=55968427
If your pc does not see the phone in download mode then you need to run kies emergency firmware recovery..
Click to expand...
Click to collapse
Thanks, I found where someone had the same issue with the Note 3 and used kies emergency firmware recovery to fix it as well, so I started the process. It just finished, and I'm back up and running.

omega_wolf said:
Thanks, I found where someone had the same issue with the Note 3 and used kies emergency firmware recovery to fix it as well, so I started the process. It just finished, and I'm back up and running.
Click to expand...
Click to collapse
Thats good news..
[emoji1] [emoji109] [emoji106]

can you link me to where you went? fml this just happened to me after flashing same rom you did.

jrocks213 said:
can you link me to where you went? fml this just happened to me after flashing same rom you did.
Click to expand...
Click to collapse
Yea, I followed the steps posted in this thread: http://forum.xda-developers.com/showthread.php?t=2486564&page=2
1. download KIES 3 (for note 4)
2. Click tools>Firmware upgrade and initialization
3. Put phone into download mode (press Volume down+Home Button+Power Button and then volume up)
4. Connect your phone (it is OK if it is not recognized by KIES, just keep it connected)
5. Now do as it says by typing in your Phone model number (check the battery compartment).
6. Type in the S/N.
7. Let it do its business and download the firmware.
8. Once firmware is downloaded, It will start communicating with the phone.
9. You can see a blue progress line on the screen under the android guy.
10. Let it finish and restart.
You will have to re-root after this.

omega_wolf said:
Yea, I followed the steps posted in this thread: http://forum.xda-developers.com/showthread.php?t=2486564&page=2
1. download KIES 3 (for note 4)
2. Click tools>Firmware upgrade and initialization
3. Put phone into download mode (press Volume down+Home Button+Power Button and then volume up)
4. Connect your phone (it is OK if it is not recognized by KIES, just keep it connected)
5. Now do as it says by typing in your Phone model number (check the battery compartment).
6. Type in the S/N.
7. Let it do its business and download the firmware.
8. Once firmware is downloaded, It will start communicating with the phone.
9. You can see a blue progress line on the screen under the android guy.
10. Let it finish and restart.
You will have to re-root after this.
Click to expand...
Click to collapse
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
Click to expand...
Click to collapse
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.

jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
Click to expand...
Click to collapse
Try entering the model number and S/N and pressing Ok before connecting the phone, or double check to make sure 0s aren't Os or vice versa. It took a minute or 2 to get started on my phone, and took awhile to complete.

jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.
Click to expand...
Click to collapse
This happened to me before and this is what i did. Easier than messing kies I think. Flash cf auto root in odin with the reset and auto reboot unchecked. Very important to uncheck those. It will fail to flash. Pull out your battery and put back in. It will boot as normal. Now go into security and uncheck that reactivate crap. That feature should be disabled completely custom roms to prevent this occurance i think.

Airtioteclint said:
That feature should be disabled completely custom roms to prevent this occurance i think.
Click to expand...
Click to collapse
I agree, it wasn't checked by default when I rooted the phone, nor when I flashed another ROM, so I didn't even think to check when I flashed Dynamic Kat, but I'll be double checking gem here on out.

jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.
Click to expand...
Click to collapse
Hi, Im in the same boat, locked out, etc, I am trying kies where I dump the s/n in etc, it downloads the firmware, sees the phone then crashes, same with ODIN, the blue bar underneath the android man, starts but locks up. Does not go anywhere and freezes the phone. I have to take the battery out or leave Kies to give me an error. Any idea?

smileruk.ss said:
Hi, Im in the same boat, locked out, etc, I am trying kies where I dump the s/n in etc, it downloads the firmware, sees the phone then crashes, same with ODIN, the blue bar underneath the android man, starts but locks up. Does not go anywhere and freezes the phone. I have to take the battery out or leave Kies to give me an error. Any idea?
Click to expand...
Click to collapse
Odin flash cf autoroot, it will fail but once it restarts it will boot up to your android screen,
also you can Odin flash the full firmware, but then u need to odin flash twrp again and root.

[Q] Stuck at boot loop.

I have a SM-G925V I'm trying to recover. Currently it's only able to get to download mode (Power - Home - Volume Down) and maintenance mode (Power - Volume Up - Volume Down). When you power it on you see the first splash screen then reboots over and over. Unable to get to recovery mode at all (Power - Home - Volume Up).
In download mode, using this I can get Odin 3.10.6 to successfully flash the firmware from the same thread and when it reboots it boot loops again. Also, tried the firmware from this thread.
I also tried using Odin 3.07 and 3.09. Both of these versions get stuck at <ID:0/005> NAND Write Start!! with the box at the top saying "Set Partition". Both versions will however, let you re-partition using the .pit file located in the first thread linked.
In maintenance mode, all of the options instantly reboot the phone and start the boot loop again.
Samsung's Smart Switch says "Unsupported device".
The screen shows this in download mode:
Code:
ODIN MODE
PRODUCT NAME: SM-G925V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
AP SWREV: 1
Kernel AP SWREV: 1
Any help or suggestions would be appreciated, pretty much willing to try anything at this point. I should also mention I did everything above on 2 separate computers, both running Windows 7 Pro and 2 different cables, cause that's always the problem right?

cameljon said:
I have a SM-G925V I'm trying to recover. Currently it's only able to get to download mode (Power - Home - Volume Down) and maintenance mode (Power - Volume Up - Volume Down). When you power it on you see the first splash screen then reboots over and over. Unable to get to recovery mode at all (Power - Home - Volume Up).
In download mode, using this I can get Odin 3.10.6 to successfully flash the firmware from the same thread and when it reboots it boot loops again. Also, tried the firmware from this thread.
I also tried using Odin 3.07 and 3.09. Both of these versions get stuck at <ID:0/005> NAND Write Start!! with the box at the top saying "Set Partition". Both versions will however, let you re-partition using the .pit file located in the first thread linked.
In maintenance mode, all of the options instantly reboot the phone and start the boot loop again.
Samsung's Smart Switch says "Unsupported device".
The screen shows this in download mode:
Code:
ODIN MODE
PRODUCT NAME: SM-G925V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
AP SWREV: 1
Kernel AP SWREV: 1
Any help or suggestions would be appreciated, pretty much willing to try anything at this point. I should also mention I did everything above on 2 separate computers, both running Windows 7 Pro and 2 different cables, cause that's always the problem right?
Click to expand...
Click to collapse
What did you do/flash to cause the loop to begin with?
Sent from my SM-G925V

Demiurge7 said:
What did you do/flash to cause the loop to begin with?
Sent from my SM-G925V
Click to expand...
Click to collapse
Not 100% sure but I think they were trying to flash it back to stock using the same method I'm trying now.

cameljon said:
Not 100% sure but I think they were trying to flash it back to stock using the same method I'm trying now.
Click to expand...
Click to collapse
Have you tried flashing the OE2 in Odin?
Sent from my SM-G925V using XDA Free mobile app

Demiurge7 said:
Have you tried flashing the OE2 in Odin?
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
Downloaded OE2 from sammobile. Same result.
Side note: It doesn't have a .pit file. Do they normally come with one stock? I'd like to try another .pit file and see if I can get Smart Switch to recognize the phone again.

cameljon said:
Downloaded OE2 from sammobile. Same result.
Side note: It doesn't have a .pit file. Do they normally come with one stock? I'd like to try another .pit file and see if I can get Smart Switch to recognize the phone again.
Click to expand...
Click to collapse
Yes I thought the firmware package included the partition table, but I could be wrong. I can't seem to find any .pit file for our variant on its own.
I am still curious to know what caused it in the first place, as it sounds like everything you have tried should have worked. Other than flashing the wrong variant firmware in Odin, or a corrupt .tar, I wonder how that could have caused a bootloop. And even then, if you can get into download mode, the correct full Odin package (as you tried) should have fixed it. Tried other comps, check. Tried other cables, check. Did you make sure you were plugged into primary USB ports? Did you check the md5s of the Odin packages?
I'll let you know if I run into a standalone .pit file, otherwise I am sorry I couldn't be of more help. Keep us posted though.
Sent from my SM-G925V using XDA Free mobile app

Demiurge7 said:
Yes I thought the firmware package included the partition table, but I could be wrong. I can't seem to find any .pit file for our variant on its own.
I am still curious to know what caused it in the first place, as it sounds like everything you have tried should have worked. Other than flashing the wrong variant firmware in Odin, or a corrupt .tar, I wonder how that could have caused a bootloop. And even then, if you can get into download mode, the correct full Odin package (as you tried) should have fixed it. Tried other comps, check. Tried other cables, check. Did you make sure you were plugged into primary USB ports? Did you check the md5s of the Odin packages?
I'll let you know if I run into a standalone .pit file, otherwise I am sorry I couldn't be of more help. Keep us posted though.
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
At the start of this, I did run into a USB problem. I couldn't flash at all on my desktop from my USB 3.0 front header. Works on the 2.0 front header and all of the motherboard headers. So I ruled that out by accident at least. The MD5s check out. I'm going to keep searching for a pit file that goes with the OE2, or at least find out why it's not in the firmware from sammobile. Know another source for OE2?
Without another partition file or firmware I can flash from Odin, some social engineering with the Verizon store may be the next step.

cameljon said:
At the start of this, I did run into a USB problem. I couldn't flash at all on my desktop from my USB 3.0 front header. Works on the 2.0 front header and all of the motherboard headers. So I ruled that out by accident at least. The MD5s check out. I'm going to keep searching for a pit file that goes with the OE2, or at least find out why it's not in the firmware from sammobile. Know another source for OE2?
Without another partition file or firmware I can flash from Odin, some social engineering with the Verizon store may be the next step.
Click to expand...
Click to collapse
No, no oe2 yet. I am sure it will get posted though soon.
Sent from my SM-G925V

yea its the pit file that you need, should solve your issue..

Bricked Note 4, User Death Imminent

Hello.
So, I rooted my T-Mobile Samsung Galaxy Note 4. It went flawlessly. I flashed TWRP and rooted it without a hitch. Now fast forward a few months, to today. I decide to restart my phone again. Nothing has changed, except that my "helpful" antivirus "conveniently" turned off USB Debugging. I restart it and it brings up a screen. It has a "caution" sign with the exclamation mark. Some text is there as well, saying:
Custom binary blocked by FRP.
SECURE FAIL: KERNEL
Granted, I was upset. My phone won't boot up. I've tried booting into TWRP, but the same screen appears. I can't use Odin because USB Debugging was forcibly shut off by my antivirus.
If I don't have my cell phone, I will struggle in school, as the only other device I have is this laptop which has no working battery and runs on outlet power alone. I don't have the money to purchase a new device, and I feel like I'm out of options, so if I don't get some help, I'm a dead man. If anyone could help, I'd be very grateful. On the Odin Mode screen, info is as follows:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T3
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: ON
KNOX WARRANTY VOID: 0X1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I don't know how much of that is relevant.
Help me, XDA Developers. You're my only hope.
Thanks,
A stupid Wizard with a bricked phone.

Did you try to use Odin to reflash twrp or the stock firmware? You dont need usb debugging on to reflash stock firmware. If you were on stock, i would just reflash with Odin, tuen on usb debugging and reroot. If u were on custom rom, you might have to odin back to stock, and then do factory reset from recovery.

RaySCLA said:
Did you try to use Odin to reflash twrp or the stock firmware? You dont need usb debugging on to reflash stock firmware. If you were on stock, i would just reflash with Odin, tuen on usb debugging and reroot. If u were on custom rom, you might have to odin back to stock, and then do factory reset from recovery.
Click to expand...
Click to collapse
I tried to reflash the TWRP, but it failed. An error message appears:
Custom Binary(recovery) Blocked By FRP Lock

ShadowedWizard said:
Hello.
So, I rooted my T-Mobile Samsung Galaxy Note 4. It went flawlessly. I flashed TWRP and rooted it without a hitch. Now fast forward a few months, to today. I decide to restart my phone again. Nothing has changed, except that my "helpful" antivirus "conveniently" turned off USB Debugging. I restart it and it brings up a screen. It has a "caution" sign with the exclamation mark. Some text is there as well, saying:
Custom binary blocked by FRP.
SECURE FAIL: KERNEL
Granted, I was upset. My phone won't boot up. I've tried booting into TWRP, but the same screen appears. I can't use Odin because USB Debugging was forcibly shut off by my antivirus.
If I don't have my cell phone, I will struggle in school, as the only other device I have is this laptop which has no working battery and runs on outlet power alone. I don't have the money to purchase a new device, and I feel like I'm out of options, so if I don't get some help, I'm a dead man. If anyone could help, I'd be very grateful. On the Odin Mode screen, info is as follows:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T3
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: ON
KNOX WARRANTY VOID: 0X1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I don't know how much of that is relevant.
Help me, XDA Developers. You're my only hope.
Thanks,
A stupid Wizard with a bricked phone.
Click to expand...
Click to collapse
FRP is referring to "Factory Reset Protection" , that means you had the Samsung Reactivation Lock turned on and the phone detected a change in the software preventing it from booting up. Now there are two ways to get the phone back up, first try going into download mode (Holding power button+volume down) then restart it by holding down power+volume up) if by chance this doesn't work then the other option would be to use odin and reinstalling the stock rom but it would need to be the same version currently installed.

glm0025 said:
FRP is referring to "Factory Reset Protection" , that means you had the Samsung Reactivation Lock turned on and the phone detected a change in the software preventing it from booting up. Now there are two ways to get the phone back up, first try going into download mode (Holding power button+volume down) then restart it by holding down power+volume up) if by chance this doesn't work then the other option would be to use odin and reinstalling the stock rom but it would need to be the same version currently installed.
Click to expand...
Click to collapse
How would one install a ROM directly from Odin? I know how to do it from the recovery, but I can't access it.
EDIT: After more research and a helpful PM, I am using Kies to wipe everything and restore the stock ROM.
EDIT 2: Success! After resetting using Kies, I was able to reflash TWRP and get rooted again. Thanks to everyone who helped.

ShadowedWizard said:
I am using Kies to wipe everything and restore the stock ROM.
Click to expand...
Click to collapse
No. You should have used ODIN (from your desktop / laptop PC) to restore a stock ROM so that you could have kept your data

Anonymously_Unknown said:
No. You should have used ODIN (from your desktop / laptop PC) to restore a stock ROM so that you could have kept your data
Click to expand...
Click to collapse
I had attempted to do restore the stock ROM, and I recieved the same error as with reflashing the recovery.
I restored to stock with Keis, then flashed TWRP, re-rooted, and installed a new ROM. I then restored my important data (contacts, app info, etc.) from a Titanium Backup on a microSD.

And don't turn on factory reset protection. Useful for casual users who don't root and install cudtom ROMs, but a real problem for those who do.

I believe there is a null/dummy ODIN file floating around you can flash in Odin that will clear that message and get it to boot again.
You're getting it because your lock is on and it's trying to flash something, and will continue to try every time you reboot, there doesn't seem to be a way for it to clear itself after unsuccessful attempts.
edit: pretty sure this is the one I used, but I'd recommend doing your own research before blindly taking my advice:
http://forum.xda-developers.com/showthread.php?t=1766399

RiverCity.45 said:
And don't turn on factory reset protection. Useful for casual users who don't root and install cudtom ROMs, but a real problem for those who do.
Click to expand...
Click to collapse
What is a good way to get that same protection that for a rooted/custom rom user?

blindskater39 said:
What is a good way to get that same protection that for a rooted/custom rom user?
Click to expand...
Click to collapse
There an app floating around that bypasses the reactivation lock.

gal419 said:
There an app floating around that bypasses the reactivation lock.
Click to expand...
Click to collapse
I am wondering if there are security app made for rooted devices to prevent a thief from stealing flashing or getting sensitive information in the device.

Is there a way to disable the FRP so it doesn't accidentally get turned on?

Can someone help me with a bricked 920A?

hello all, I have a bricked sm-g920A I bought second hand, I managed to get it into download mode via a usb jig, Is it possible to create a .tar I can flash in odin to get me directly to recovery mode, the usual button combination will not work, or if its possible a .tar that can allow usb debugging. I know its asking for alot but any feedback would be great
the phone is samsung account locked and it has the current firmware 7.0 (RC1)
the brick is a black screen with a solid white led. I reflashed current firmware with the pit file, but still no recovery mode

enzo13email said:
hello all, I have a bricked sm-g920A I bought second hand, I managed to get it into download mode via a usb jig, Is it possible to create a .tar I can flash in odin to get me directly to recovery mode, the usual button combination will not work, or if its possible a .tar that can allow usb debugging. I know its asking for alot but any feedback would be great
the phone is samsung account locked and it has the current firmware 7.0 (RC1)
the brick is a black screen with a solid white led. I reflashed current firmware with the pit file, but still no recovery mode
Click to expand...
Click to collapse
Try with this tool:
http://www.mediafire.com/file/gj6iead79j3ze02/Samsung+300K+Tool.7z

stek-kravari said:
Try with this tool:
http://www.mediafire.com/file/gj6iead79j3ze02/Samsung+300K+Tool.7z
Click to expand...
Click to collapse
although this is very useful, Its not really needed since i already have a usb jig