Database Info

Need solution for this Galaxy R

Hi guys...
I need your help if this problem are possible to fix it.
It happen just after received a call.. then i leave it for awhile.
After that, when I take phone.. its really heat and the screen doesnt turn on. It just like the device was turn off. So I remove the battery and put it back, and hit on button.. the appear on the screen like attached photo...
I'd tried all repair method to solve the bricked... but nothing change. It tend to the red text.
Additional info- before it happen..the phone is on taiwan firmware with ardadat's kernel 1.5 if I not mistaken...
So I really appreciate that if theres any solution before I wanted to send it to service centre.
Sent from my GT-I9003

looks like some problm wid ur lcd....

Did you try to nvflash it? Partition error..
Did this happen after you try to connect to odin and flash stock firmware?
xarolx said:
Hi guys...
I need your help if this problem are possible to fix it.
It happen just after received a call.. then i leave it for awhile.
After that, when I take phone.. its really heat and the screen doesnt turn on. It just like the device was turn off. So I remove the battery and put it back, and hit on button.. the appear on the screen like attached photo...
I'd tried all repair method to solve the bricked... but nothing change. It tend to the red text.
Additional info- before it happen..the phone is on taiwan firmware with ardadat's kernel 1.5 if I not mistaken...
So I really appreciate that if theres any solution before I wanted to send it to service centre.
Sent from my GT-I9003
Click to expand...
Click to collapse

akshatsourav said:
looks like some problm wid ur lcd....
Click to expand...
Click to collapse
well i'm not sure why its happen suddenly if lcd problem
ishafiq said:
Did you try to nvflash it? Partition error..
Did this happen after you try to connect to odin and flash stock firmware?
Click to expand...
Click to collapse
It just happen just after the phone heat..
So now, with this current condition, once i put battery on it,
it will turn on automatically and drop the red text...then get into download mode.
I try to flash it with stock firmware.. but it keep telling fail.
Message on Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9103DXKI3_I9103OLBKH3_I9103DXKH3_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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
I'd tried to use the "GT-I9103_Dead_Repair_By_Xiaoyuz", but seems like failed for that..plus, the instruction not really clear. How do I install the drive inside? It wont install once I plugged the device
Edit : GT-I9103_Dead_Repair_By_Xiaoyuz method done completely, but still occured like my 2nd attached picture.
p/s : I'm sorry for not rotate all the picture. Directly upload from my SL.

xarolx said:
well i'm not sure why its happen suddenly if lcd problem
It just happen just after the phone heat..
So now, with this current condition, once i put battery on it,
it will turn on automatically and drop the red text...then get into download mode.
I try to flash it with stock firmware.. but it keep telling fail.
Message on Odin:
I'd tried to use the "GT-I9103_Dead_Repair_By_Xiaoyuz", but seems like failed for that..plus, the instruction not really clear. How do I install the drive inside? It wont install once I plugged the device
Edit : GT-I9103_Dead_Repair_By_Xiaoyuz method done completely, but still occured like my 2nd attached picture.
p/s : I'm sorry for not rotate all the picture. Directly upload from my SL.
Click to expand...
Click to collapse
Ur download counter is zero better u give ur device in service centre. Tell them i was using phone and suddenly it gone off and not starting.
Sent from my GT-I9103 using Tapatalk 2

A partition problem huh.....
I know this sounds stupid , but can you try other .pit files ? Like the SII's or the SL's .
Ace-ing all tests.

Did u follow post 8/9? using pit file and all?
xarolx said:
well i'm not sure why its happen suddenly if lcd problem
It just happen just after the phone heat..
So now, with this current condition, once i put battery on it,
it will turn on automatically and drop the red text...then get into download mode.
I try to flash it with stock firmware.. but it keep telling fail.
Message on Odin:
I'd tried to use the "GT-I9103_Dead_Repair_By_Xiaoyuz", but seems like failed for that..plus, the instruction not really clear. How do I install the drive inside? It wont install once I plugged the device
Edit : GT-I9103_Dead_Repair_By_Xiaoyuz method done completely, but still occured like my 2nd attached picture.
p/s : I'm sorry for not rotate all the picture. Directly upload from my SL.
Click to expand...
Click to collapse

[Q] Phone will not turn on, will only go into DL mode.

Hello,
I have been using this site for days now and accomplished everything I have needed to so far.
I rooted and flashed about 6 roms and found the Aeon v1.4 to be the best for me regarding my infuse 4g.
I tried to install the " Unofficial CM9 rom" for the ics look and it turned my phone into a paperweight.
Symptoms:
-Phone will not go into recovery
-will not turn on
-when attempting to turn it on, i get a barely noticable millisecond flash and then nothing.
The phone, however, will go into download mode.
I tried odin and did the repartition, pit, etc..
I tried heimdal (however its spelled) and it wont recognize drivers. (i installed drivers and they worked for odin)
I basically just want to put Aeon back on my phone and actually use my phone.. nothing else. I would appreciate any insight into the matter.
Thank you very much.
Chris.

I recently had the same problem when I tried to downgrade back to GB. I used Odin to reflash my phone using this.....http://forum.xda-developers.com/showthread.php?t=1613523.....

Thanks
omansteveo said:
I recently had the same problem when I tried to downgrade back to GB. I used Odin to reflash my phone using this.....http://forum.xda-developers.com/showthread.php?t=1613523.....
Click to expand...
Click to collapse
Thanks, ill definitely give it a whirl.. I have tried many different versions of Odin and different PIT, PDA files. Most of the time it just says:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NewStock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> factoryfs.rfs
and sits there... stuck for like 20 min+ (currently)... no progress bar or anything. Currently, this one is PDA .tar only. No pit or anything else with only auto-reboot and f. reset time checked.
I'll definately let you know how it worked out though, thank you!

Try other usb ports & another usb cable if possible.
Sent from my SGH-I997 using xda app-developers app

use gtg ultimate unbrick
Azrael-09 said:
Thanks, ill definitely give it a whirl.. I have tried many different versions of Odin and different PIT, PDA files. Most of the time it just says:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NewStock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> factoryfs.rfs
and sits there... stuck for like 20 min+ (currently)... no progress bar or anything. Currently, this one is PDA .tar only. No pit or anything else with only auto-reboot and f. reset time checked.
I'll definately let you know how it worked out though, thank you!
Click to expand...
Click to collapse
You need to go back to stock. Look for it in the software part. It is the ultimate gtg unbrick. It works flawless.

OP no need to double Post Threads of the same issue, your Thread in the General Section is no longer, utilize this thread for your issues. Thank You.

Is there an average time for Odin to pass?
andros11 said:
Try other usb ports & another usb cable if possible.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I've been trying all 3 ports and decided to just stick to the on directly connected to the motherboard. Also have been using "USB Deview" to remove usb connections in order for phone to recognize the infuse drivers i unzipped and put on the desktop. Ill try another cord as well, thank you.
kenetix said:
You need to go back to stock. Look for it in the software part. It is the ultimate gtg unbrick. It works flawless.
Click to expand...
Click to collapse
I have tried that one i beleive, but my phone was originally Froyo and "GTG's ultimate unbrick" is for Gingerbread.. (GB PIT file) (it said my phone couldnt upgrade to GB when i was unrooted). I'll Try again though, couldnt hurt. Thanks.

You should go back to stock rom via Odin
When in doubt go stock
Sent from my GT-S5360 using xda app-developers app

Azrael-09 said:
I have tried that one i beleive, but my phone was originally Froyo and "GTG's ultimate unbrick" is for Gingerbread.. (GB PIT file) (it said my phone couldnt upgrade to GB when i was unrooted). I'll Try again though, couldnt hurt. Thanks.
Click to expand...
Click to collapse
Really no way to go back to Froyo. You have to now assume GB is the beginning...
Sent from my SGH-I997 using xda premium

Going stock
An1mus said:
You should go back to stock rom via Odin
When in doubt go stock
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
I would absolutely love to flash it back stock, problem is I can find good files to drop me back to stock.. or maybe its the phone, idk. I even tried files used from the dump of someones stock phone to recreate a "stock" version. Next step is trying Gtg's Ultimate unbrick again.
I'll keep you guys updated, thanks for all your help.
I dont have enough posts to be able to put in outside links but if someone needs the GTG's_Ultimate_Unbrick.zip link, i found it. )Most of the links are broken and its a pain to find) Just PM me.

Odin update
20 min into it.
Odin shows this:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.rfs
And phone is in DL mode with the blue progress bar showing about 1% since the beginning and hasnt moved. Odin isnt saying that its not responding or anything... any ideas?

If you want stock Froyo: http://forum.xda-developers.com/showthread.php?t=1629079
If you want stock GB : http://forum.xda-developers.com/showthread.php?t=1524081
Many thanks to qkster for this.

5 days and counting.. =(
Pony Express said:
If you want stock Froyo: http://forum.xda-developers.com/showthread.php?t=1629079
If you want stock GB : http://forum.xda-developers.com/showthread.php?t=1524081
Many thanks to qkster for this.
Click to expand...
Click to collapse
Thank you very much, I have tried those. This is my fifth day doing this and i cant seem to get Heimdall to work. I tried doing as much research as possible before posting a problem.
For Heimdall even though when it asks for drivers I can click on "Samsung usb composite device" and reflash but it just says "installing drivers" and loops over again.
For Odin its just not continuing to increase the progress bar or add anything new to the log screen.. Pretty confused at this point.
My phone is bricked from flashing the wrong rom. I dont mind which OS i go to because im going to end up flashing Aeon v1.4 again anyways since it looked and worked great.
Thanks for the links!

Update
[Well, i still cant get odin to get past the factoryfs.rfs ...
Phone is still only showing an 1/8 inch progress bar..
I keep trying Heimdall but no luck... i do not have file upload options in Heimdall though... is that normal?
If anyone has any other ideas, please share..

Here is a post I did for someone else, I hope it will be helpful to you.
http://forum.xda-developers.com/showpost.php?p=33215877&postcount=15
(The link I mention in post 13 is qkster's Heimdall link)

I'll get right on it. Thank you.

I think im missing some tar files... only thing in the video i can think of is that he mentions having odins tar files for some reason while using heimdall on-click.. I do have some files on my desktop > pit, phone and pda files but no other ones..
Also in the video it mentions the binary at the top of your screen in download mode. Mine says: Custom binary download: NO
Current binary: Samsung official
That normal for someone who flashed 6 roms?
On top of it all dev-host isnt downloading anything for me... click and click and nothing.
I think i just need some expert phone help, lol...

I just put mine in download and binary also says 'no'. I have lost count as to the number of roms I have flashed.
I think you are close but from my end I can't tell what is missing. I have used odin with no problem and yet my preference is Heimdall.
Maybe take some time and go through some of qkster's threads, including the link to his Heimdall tutorial. Some have found that they did not have the latest version of Java while others did not know that you have to use the same port you were using each time you use Heimdall. Others did not know that Heimdall has it's own drivers or that they should uninstall kies first.
Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know.

I installed then uninstalled Kies
I do have the latest version of Java.
I downloaded a binary version of Heimdall for the Zadig driver file so that i can manually put in the samsung driver before opening the one click Heimdall
I have followed tutorials to the letter so much that when i watched the video it seemed like I was knowledgeably far beyond the video's tutorial.
Im am however, unsure what you mean by using the same port (please keep in mind that im on the computer trying to fix my phone about 45 min out of every hour for about 8 hours a day for the past 5 days)... I actually had to erase all the zip files and tar files and such just to re-grasp where i was at because my desktop was overloaded...
Oh and i read a thread about bricking your phone (good read) and i think i screwed it up somewhere in the bootloaders... its not enough to hard brick it since i can still go into DL mode but something is definately wrong.
I do appreciate your advice and concern. Thank you again.
Hopefully we can come to a conclusion soon and i can pass on my knowledge...

Pony Express said:
Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know.
Click to expand...
Click to collapse
Thanks for the vote of confidence, Pony. I'm not very good at getting the drivers installed.
What you noted is all that I can recommend.
Update java. Install Samsung USB device. Install Zadig from Heimdall. Sometimes it take a reboot or two with the PC. Other times, it takes a different PC altogether. It may also work by moving the USB cord to a different usb port.
It has been almost a year since I tried Odin. No help there.
I can tell you that after you get the heimdall to work, save that cord and that usb port only for heimdall and don't install Odin over it.
With all the heimdall-1-click packages available, there are many options to restore from soft brick or return to stock.
jscott30 made a bunch of Odin packages as well if Heimdall is not working for that person.
Perseverance is the key. We have all been there. I can tell you that the more mistakes you make, the more you will learn.

Boot loop after trying to flash phone.

Hello,
I came here to look for help. I have a Verizon Samsung Galaxy s3. I rooted my phone and had CM10.2 on my phone.
I used casual to root phone/unlock boot loader and everything.
I decided I wanted to put CM11 on my phone. I downloaded everything from CM site for my phone. I made sure it was for my phone. I have TWRP recovery on the phone. put on debugging and everything.
I went into TWRP and started the process of putting CM11 on the phone. I made a nandroid back up in TWRP. I did a wipe data/factory reset.Once did all this, I went into install and installed zip file from my external sd-card. I believe it said failed, but i don't remember the exact thing that happened or the message I got. I know that doesn't help, but I am going to try and type everything I have done. Once that happened, I think i stupidly went to reboot and it said about super user rights needing to be fixed. I think i pushed fix. I know i probably did a big mistake there. The phone started to reboot.
When the phone is rebooting what happened was it would got to samsung galaxy logo and then CM logo. It would then immediately reboot. It just kept going through this cycle. So i tried to boot into recovery. It starts to attempt to boot in recovery. TWRP logo starts popping up. Boom it reboots again. So i can't get into recovery mode.
So i started to read around about my problem. I found articles saying about using odin to correct this boot loop (soft brick i think from what I read). I started to follow this article: http://forum.xda-developers.com/showthread.php?t=1840030
When I followed that article I got steps one through six done with odin saying pass. I start to do step 7. I actually tried to do step 7 twice. I got fails both times. I don't have the results form the first time. I downloaded the root66 tar file from somewhere else. I don't remember. When I got the failure, I pulled the root66 tar file i found here: http://forum.xda-developers.com/showthread.php?t=1984436 I used the main on on there. I go through and it fails: Here is the log from it.
<ID:0/005> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> root66_VZW_I535VRBMB1.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/005> Odin v.3 engine (ID:5).. <ID:0/005> File analysis.. <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> Erase... <ID:0/005> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)
I am completely stuck on what to do at this point. I am growing tired of trying stuff and I am completely stuck. I have tried to look around, but no luck.

Have you tried Odin flashing the VRBMF1 4.1.2 stock image? You would need to root and unlock your bootloader afterwards. This file formats /sdcard as well.

I'm downloading the image right now. I will try and use it and see what happens. I'll get back to you as soon as it downloads and I run odin again.

thunderisraw said:
I'm downloading the image right now. I will try and use it and see what happens. I'll get back to you as soon as it downloads and I run odin again.
Click to expand...
Click to collapse
Cool, just do not accept the 4.3 OTA if this flashes fine and boots up for you

SlimSnoopOS said:
Cool, just do not accept the 4.3 OTA if this flashes fine and boots up for you
Click to expand...
Click to collapse
Okay i got odin to work. I got it flashed on there. thank you so much! Now i just got to unlock the bootloader again. Which I'll do real fast with casual. Thank you again for being so fast to respond!

thunderisraw said:
Okay i got odin to work. I got it flashed on there. thank you so much! Now i just got to unlock the bootloader again. Which I'll do real fast with casual. Thank you again for being so fast to respond!
Click to expand...
Click to collapse
Great! You'll have CM11 installed in no time :thumbup:
Sent from my SCH-I535 using Tapatalk 4

*[HELP]* Need help unbricking Galaxy Note 10.1

Hi guys,
My galaxy note 10.1(2013) is was on <Stock> Android Kitkat .
Out of curiosity of rooting, i flashed CF Auto Root using odin.
The device restarted, and features seemed fine with new Root App too.
In few minutes however, device rebooted.. and went into a bootloop. :crying:
which still is, as long as device is on - has battery.
SUMMARY:
1. Recovery mode is not accessible now - device goes into recovery mode and restarts.
2. Normal boot is going into bootloop.
3. Download mode - HOWEVER is available !
PROBLEM :
-on trying to reflash stock rom/any Tar File for my device using odin,
odin fails with message :
NAND WRITE START
FAIL
----------------------------------------------------------------------------------------------------------------
Please help solve.
I do not want my beloved<soft bricked> device to die a sudden death .
Will appreciate you guys putting life back in it !

Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.

chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now

chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
will get back with update tomorrow.

glorifiedg said:
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now
Click to expand...
Click to collapse
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.

Anand.prashar said:
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.
Click to expand...
Click to collapse
'Cause you probably didn't try the 4.0.4. I have nand write fail with the most recent versions also :S

Suggestion to no avail
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?

Anand.prashar said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?
Click to expand...
Click to collapse
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.

[/COLOR]
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.[/QUOTE
same problem here but i thing we need to clear all those built up cache in order to proceed right? but no boot recovery just the Odin downloading image. now if we can find a way to clear all those cache i'm sure'll work but don't know how to clear it from the "downloading do not turn off target" unless somebody figure this out.
Click to expand...
Click to collapse

* Serious issue awaiting resolution *
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.
Click to expand...
Click to collapse
Sorry for delay, work kept busy.
You have the N8000. Correct?
-Yes
If you're working on a desktop ?
-No
- On laptop :
same laptop i used to root my tab using CF-Auto Root.
and have flashed ones in past on the older rom for this tab.
- Port : used USB 2.0
TWRP recovery ?
- Getting same error on odin as stock Rom.
<< I am attaching 3 snapshots >>
- Odin desktop Software in work
- Download mode of device
- Texts on download mode screen of device
<i believe it says custom, coz i had already 'seemingly' rooted stock rom>
------------------------------------------------------------------------------------------------------------
It would be worthwhile to mention the last flashing trial.
- it was upgraded to Kitkat released for this device
2 months ago : using Odin [as i had rooted the previous Default firmware too]
- having gotten bored with non-SU controls,
i flashed CF Auto Root
that would give me "SuperSU app" control without changing existing Firmware.
- Device rebooted after flashing (hopefully correct steps, i think)
"Super SU" app was available for me.
- Note : Upon opening app, i was prompted with a message
"KNOX has been detected on this device... would i like to remove/disable ?"
- I hit Yes.
Got a popup soon, that KNOX was successfully removed.
- and then, it went FINE for about an hour.
AND THEN CAME THE BOOTLOOP all of a sudden.
------------------------------------------------------------------------------------------------------------
Summary:
I am not able to figure out what could have caused this...
flashing/knox/ anything else ?

I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.

ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
Did you already tried to flash the 4.4 leaked version with the 5 files over odin?
And also the pit file provided there.
That solved my problem a couple of months ago.

ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
hey,
what do you mean by "useless" ?
please explain clearly.
i just got one of these the other day,gt-n8013, maybe it's possible to whip up a fix.
a thought i have is that a boned odin install may take on the same behaviour
as a certain kernel function where a temporary kernel to be booted to
may be being stored into ram, meaning when you reboot to odin mode
you basically pick up where you left off. poweroff your tab and then plug in
your charger like normal. if your battery image shows up then, your kernel is intact or mostly so.
if that's the case maybe running your battery dead or disconnecting it will
work like pulling the cmos battery in a pc to correct a bad bios configuration.
meaning after the power is finally and truly off then ram will clear completely and when
you recharge and reboot back to odin you will be at baseline again.
the above approach has worked with some lower end tabs i've owned
including the galaxy tab 2 7.0
m

Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?

dough30i said:
Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?
Click to expand...
Click to collapse
okay, try for odin now, but try recovery first.
@dough30i
going back through this thread if you did the same thing with cf-root-crap you may have
damaged you bootloader. which is very not good. if you've gotten recovery up let me know.
you will need to get adb running and just for verification i need your model i.d.

No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...

dough30i said:
No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...
Click to expand...
Click to collapse
okay, are you trying to write a full firmware image or just a recovery or boot tar.md5?
or is it flat out no go?

Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-

dough30i said:
Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-
Click to expand...
Click to collapse
okay,
first, we do not put ourselves down. technology is unnatural, we make mistakes.
second, we do not panic or act rashly.
that being said if you can still get into odin, all is not yet lost. while i am pulling the pit file from
my device you will need to look up the correct way to write it to your device using odin.
i will be back in about 10 - 15 minutes.
use the force.
m

@dough30i
okay,
this is the pit file pulled from my n8013 . what i've read it should do the trick.
however, let's be clear.
1 you are in a bad situation, with nothing to lose.
2 this may not work but, then again it might.
3 you are the the final say as to wether or not you will attempt this
4 you have secured the correct knowledge on applying the pit file and writing in odin.
if yes to all of the above, download the attached file and remove the .txt extension
m
this is the thread i pulled the information from
http://forum.xda-developers.com/showthread.php?t=2268735

Custom Binary Blocked by FRP Lock

I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!

mryanmarkryan said:
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
Click to expand...
Click to collapse
If you can't even mount it on Windows or get into recovery that's not good.

True Dat!
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?

mryanmarkryan said:
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
Click to expand...
Click to collapse
I would suggest pushing the root kernel to it anyway just to see if it will go.. I do have an FRPbypass but it's an apk meaning you need to install it and if you cannot mount to push it and then try to do adb shell pm install FRPbypass.apk then there's no point in that either.. Can you even get into download mode? If not the last thing I could suggest is the PIT file to repartition it. Unless someone else has a better idea? I do have the PIT file for odin too.
Also I think you're past the point of losing your data and if you can hold the volume down button and power button at the same time until it shuts off and turns back on again you can select factory reset and that's going to ruin all data..

My god, this happened to me on my first Note 5 I had. I was trying to restore it to stock before selling it and like an asshole I forgot to check for "OEM Unlock" and ran into that exact message. It put the fear of god into me. Like you I didn't have the serial number written down and I couldn't get it from anywhere. T-Mobile tech reps tried to tell me the IMEI number acts as a serial number, cool, that doesn't help me. I gave up on Kies and just played around with Odin after I was FINALLY able to find a stock firmware. I can't believe how difficult that was to get. I managed to flash the stock firmware thru Odin and I got the phone back! Stock as it came out the box.
I can't remember how I was able to get it into download mode but whatever button order I kept trying I finally did because Odin recognized the mofo and I flashed that stock firmware as fast as I could. It rebooted and I saw that beautiful stock welcome screen once more. Try to do this, I didn't need to do anything else.
For this reason I now keep a copy of stock firmware along with screen shot of my phone's status screen showing the serial number and everything else. All that's backed up to one of my external drives. Alone with several nandroid backups of various stages of owning this second Note 5 I have now. I'm running V10 of Darthstalker but I haven't heard of other users running into FRP lock. That would mean something tripped their OEM unlock option but how would that happen without you doing it? Is there something inside the ROM (a bug) that's tripping the option in Developer Options?
Best of luck with this, I know how stressful this can be. As far as getting your data back, yeah that's likely a no go. At this point you should be hopeful of getting a working phone back, let alone recover any personal data. Hope you can sort this.

More Info
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..

mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Yeah if you can get it into download mode and you've got the stock firmware you should be good to go and flash tru Odin. That's key. If I were you I'd be like, "To hell with my personal data! Get me a working phone back!".
Good luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!

MrMike2182 said:
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
Click to expand...
Click to collapse
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..

mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
Try downloading the newest odin version sometimes that can help.. Can you tell me how it's failing? Like what exactly happens when you try to do all the flashing? Did you try the adb commands that I suggested? You only need to install minimal adb and Fastboot on the windows pc and then connect your device and then open a terminal in the same exact folder where adb and Fastboot were installed and then type Fastboot devices or adb devices if it give you a bunch of numbers it means that it can see the device and we can then manually push and install the firmware. The other thing I suggest you try to do is flash the Lollipop 5.1 T-mobile firmware because I think it doesn't have frp on it yet and before flashing it go into the actual firmware you downloaded and delete cm.bin then rezip the firmware again and flash that one without the cm.bin but first try flashing the entire firmware as is with the md5 and all before resorting to deleting cm.bin.. Don't try flashing the Marshmallow 6 rom because that's where they started that frp bullcrap if you ask me. FRP stands for Factory Reset Protection... I understand the need for it and it's importance but Google could have been a lot more open about it and explaining to its customers what it's for and what it does not just do it and let most of us learn the hard way!!
When you try to flash in Odin tell me what file it fails on.
If none of this works this page is your last bet buddy
https://www.sammobile.com/forum/showthread.php?t=31136

I'm working on it now! Give you guys a summary of what happened as I as check off your suggestions..

SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol

Progress!
mryanmarkryan said:
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Click to expand...
Click to collapse
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<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..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Advice?
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
mryanmarkryan said:
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<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..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.

mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
It stopped right while trying to flash the recovery part of it so here's what I suggest you try to do.. unzip the 5.1.1 firmware you downloaded and unzip it again until you can see all the files in it and then manually flash them 1 by 1 in the AP slot but don't allow the phone to auto reboot uncheck that option and after 1 files flashed hold the volume down button and power button until you can select shut down device or turn off whichever then again hold the buttons to get into download mode again and continue until they are all flashed and then finally again hold the volume down button and power button and when it comes back on then select factory reset.
---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------
E-POUND said:
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
Click to expand...
Click to collapse
If he flashes the latest firmware with the security updates he can never go back to 5.1.1 so I don't suggest he do that yet

Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?

mryanmarkryan said:
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
Click to expand...
Click to collapse
You're not rooted at all right now but you should not have needed to turn the imgs back into md5s again you should have just flashed them the way they were they don't need md5 just to flash. Try holding the volume down button and power button until it shuts off and turns back on again then select factory reset if that doesn't work then go into download mode again and connect to a Windows pc and use Smart Switch to try and fix it.

The reason I converted them was because Odin wouldn't find the files.. I tried just running them by typing a *.img but it didn't work. I'll go read about smart switch.. I"m learning stuff here
Update,: On a hunch I went back and ran the firmware install again, but just in it's original format. It succeeded and I'm setting up the phone now.. Thanks for your help MrMike. I appreciate you putting the time in..

mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
You are using the wrong stock firmware. Download the DPG1 firmware since that is was darthstalker v.11 is on. If you backed up your ROM then you don't have any troubles at all. Just ODIN back to stock, root, twrp recovery data only and done. But not all at once. First get the firmware going and reboot your phone. Once you know it's working the try rooting. Once you are rooted download TWRP and recover your data only.
Btw - FRP is when you log into your google account in the beginning of the setup so don't do that if you want to flash other ROMs.
P.S. I'be been running Darthstalker v.11 since it came out with no problems.