Database Info

Can't get into download mode. Tablet only shows a phone, a triangle and a computer...

I can't get download mode.
My tablet was off... when I turned on, was on a bootloop. I couldn't get into recovery, then I've enter into download mode. I tried to flash a stock rom, but odin failed.
Then I lost download mode and the tablet only shows a phone, a triangle and a computer.
When I plug to charger, doesn't shows the battery icon, but battery charges.
Maybe this is a brick?...
Thanks!

help
ofwise said:
I can't get download mode.
My tablet was off... when I turned on, was on a bootloop. I couldn't get into recovery, then I've enter into download mode. I tried to flash a stock rom, but odin failed.
Then I lost download mode and the tablet only shows a phone, a triangle and a computer.
When I plug to charger, doesn't shows the battery icon, but battery charges.
Maybe this is a brick?...
Thanks!
Click to expand...
Click to collapse
I might not be able to help but you can, can you let us know what ROM/recovery/what you were doing before you turned off your tab and anything else you can think of that may be relevant
Thanks

It's download mode with a different interface Reflash your Tab, use Odin.

I've installed cyanogen 10.1 RC without problems. The tablet worked fine. Then I plugged the tablet to charge. When I took again the tablet (after 10 hours more or less) it was off.
In this mode (triangle, computer, phone), I'm trying flashing a stock rom. Without pit file, odin fails saying "write error", and with pit file and repartion checkbox marked sais "there's no pit partition".
Only way to turn off the tablet is quitting the battery. When I put again the battery, the tablet still is off; but when I try to turn on/get into download mode/get into recovery... only shows the triangle, phone and computer screen...
I think that my galaxy tab is bricked... :crying:
Sorry about my bad english and thanks for your answers.

Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

ofwise said:
Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try heimdall. Never tried by myself flashing system partition using it but work for recovery, boot, and param partition.

ofwise said:
Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to go into download mode and flash a custom recovery using odin. I recommend CWM. Then try to go into recovery mode and wipe data, cache, dalvik cache and factory reset (NOTE: It will delete EVERYTHING and your tab will be like out of the box). Now try to boot into android, if android doesn't boots up then use odin to flash a custom rom or find a stock rom for your device and then your tablet should be fine.
Good luck :thumbup: and happy flashing .
And if you found this helpful then don't forget to hit the thanks button.
Sent from my GT-P3100 using xda app-developers app

Nothing...
I've tried Heimdall and doesn't detect my device. I've tried to install another one CWM and the same problem...
I've reinstalled the samsung drivers into 2 computers, differents usb ports... no recovery, no download mode and the charging icon (battery icon) doesn't appear (but charges).
I think my tab is dead... I don't know how more I can do it.
Thanks for the ideas

OK, first off, that screen is a FORCED DOWNLOAD MODE, it will happen for several reasons (usually a bad ROM flash), all you had to do was flash the stock .tar file via Odin.
Your first mistake was checking "repartition" in Odin, YOU NEVER EVER WANT TO DO THAT EVER, now since you didn't have a PIT hopefully it just cancelled out before doing anything bad. try reflashing in Odin with the stock ROM.
Heimdall will not work just because you have the drivers for Odin, infact Heimdall has it's own DRIVER that will override the Samsung driver Odin uses on the USB port (and usually any other USB on that stack) you connect the tablet to when you do the driver install step in Heimdall.
FYI, if you are on windows 8 there is a good chance you still can't do jack yet, to my knowledge windows 8 PC's are a no go for android ROM flashing.

The computers I've tried to flash with odin are with windows 8. But I flash my phone without problems...
Maybe with another windows version. I'll give a try this afternoon at home.
Thanks!!

daniel644 said:
OK, first off, that screen is a FORCED DOWNLOAD MODE, it will happen for several reasons (usually a bad ROM flash), all you had to do was flash the stock .tar file via Odin.
Your first mistake was checking "repartition" in Odin, YOU NEVER EVER WANT TO DO THAT EVER, now since you didn't have a PIT hopefully it just cancelled out before doing anything bad. try reflashing in Odin with the stock ROM.
Heimdall will not work just because you have the drivers for Odin, infact Heimdall has it's own DRIVER that will override the Samsung driver Odin uses on the USB port (and usually any other USB on that stack) you connect the tablet to when you do the driver install step in Heimdall.
FYI, if you are on windows 8 there is a good chance you still can't do jack yet, to my knowledge windows 8 PC's are a no go for android ROM flashing.
Click to expand...
Click to collapse
I've only used Windows 8 for flashing so far and works perfectly fine in my experience

Trying with a pc on windows xp and the same situation... odin sais allways the same...
I've put a pit file that I found called "signed_espresso_20120220_16G.pit". I can't remember if I used another time... I'm not sure. But this last time I use it.
Could I do something more??...

ofwise said:
Trying with a pc on windows xp and the same situation... odin sais allways the same...
I've put a pit file that I found called "signed_espresso_20120220_16G.pit". I can't remember if I used another time... I'm not sure. But this last time I use it.
Could I do something more??...
Click to expand...
Click to collapse
YOU shouldn't EVER use a PIT file in Odin, especially if your not even sure it's the right one, using an incorrect PIT file can totally screw up your device.
The ONLY time you could ever need a PIT file is if you flashed a ROM that changed the format of the partition tables (like rfs to mtd or bml) which to my knowledge non of the ROM for these tablets do that.

Hrmmm... Have you tried to see if Samsung Kies can do anything about it?
I mean, really. Your system partition is corrupt so i doubt it can detect anything.
As a last resort could you open up the tab and pull out the battery? Or even let the battery completely run out?

I've already pulled out the battery many times. Letting the tab without battery at least 1 hour... 1 day... and when I plug it and try to access to download mode... only the same screen (triangle, phone and computer).

ofwise said:
I've already pulled out the battery many times. Letting the tab without battery at least 1 hour... 1 day... and when I plug it and try to access to download mode... only the same screen (triangle, phone and computer).
Click to expand...
Click to collapse
Check this out ofwise- h**ps://www.youtube.com/watch?v=pJnoiMTw5cY&feature=youtube_gdata_player
Note-replace (**) in the link with (tt).
Sent from my GT-P3100 using xda app-developers app

Fastboot sais "Waiting device"...

ofwise said:
Fastboot sais "Waiting device"...
Click to expand...
Click to collapse
Well, your f*cked.
Sent from my GT-P3113 using Tapatalk HD

Rooting Help

So I decided to try and root my SM-P900. Everything I read online said it was fairly easy to do. Download Odin 3.07 - 3.09, Download the samsung usb drivers, boot into download mode, plug tab in, put in the CF-Auto-Root md5 and off you go. I get a bar that makes it a quarter way accost and then a bunch of red dotted lines come down the screen and a few minutes later Oden gives me a Fail! This is my first adventure into rooting and its seemed to have gone horribly wrong and I need some help. Right now I'm downloading what I think is the stock firmware and will be trying to push that though Odin (P900ueu1anc5). What am I doing wrong and am I doing the right thing to fix it?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Originally Posted by Bizack View Post
1st thing. When you root your tab knox gets tripped. no way around this. So if this is a deal breaker, step on it and take it back. you will not get root love however.
If you do want Root, knox is tripped so why not? Follow these steps.
1. charge your tablet.
2. Down load these files.
Recovery Boot img nb3
TWRP Custom Recovery
Stock NC5 Firmware
CF-AutoRoot (go to His Post in General Section)
When charged, boot into download mode and flash the full stock package. (PDA in 3.07, AP in 3.09 ODIN) don't mess with the check boxes, when it finisheh verifying the md5 just hit start... Go take a break...
When that is done you will be back to stock, original just like you bought it.
Now boot back in to download mode and this time you are going to flash the NB3 recovery image tar... same place in ODIN as before. ( uncheck reboot in ODIN)
When that completes, disconnect your tablet and boot it back into download mode.
When you are back in Download mode, then you can safely flash the CF-AutoRoot.... (leave checks default and flash it in same slot in ODIN.
Finally, when that reboots, go back into odin and flash the custom recovery and then you will be able to boot into recovery and make a back up, (always good to make a back up) you can restore back to point in time. (that you made the backup.)
after you are all done, you can get Xposed installed and tweak the hell out if your rom. At minimum install Titanium Back up and freeze all of the knox apps.
Click to expand...
Click to collapse
Did this, got it back to stock. Letting it juice up seeming how it only has 28% battery life left before I try and press on. Bizack, I don't know who you are man but I owe you a beer ( more like a case).

Read this thread. http://forum.xda-developers.com/showthread.php?t=2761352

dodo99x said:
Read this thread. http://forum.xda-developers.com/showthread.php?t=2761352
Click to expand...
Click to collapse
Yup, thats where I found my answer. Thanks!
I do have another question now that I'm rooted. Im trying to use titanium back up and it wants me to tic the "Unknown Sources" box. Where is it in settings?

ZeroXephon said:
I do have another question now that I'm rooted. Im trying to use titanium back up and it wants me to tic the "Unknown Sources" box. Where is it in settings?
Click to expand...
Click to collapse
Settings - General - Security

[Q] [HELP] GT-N8013 - Soft Bricked(ODIN MODE ONLY)

GT-N8013
Blue/Gray
16GB Wifi Only Model
I was watching a youtube video, my tablet froze for an hour, died, then I let it charge and it rebooted into the samsung logo. After that it decided to go white screen and goes to a white screen every time it's booted. I've been trying to resolve this on my own with various resources for about a month now.
I can get to ODIN mode no problem, but I can't flash anything. I have recently bought a new OEM Samsung USB cable and tried multiple versions of ODIN on two different machines. Directly connected to the motherboard and not USB 3.0 ports.
I think the solution to my problem may be answered:
Here: http://forum.xda-developers.com/showthread.php?t=2268735
or
Here: http://forum.xda-developers.com/showthread.php?t=2713297
It is hard for me to comprehend the English used in the first link as I think Authors first language is not English. I think what he is saying is that if ODIN is not working then you have to flash the PIT file via adb and a SD card, but I cannot access Recovery, and I don't recall fully how to use ADB in Downloading Mode, if that's possible at all. He also states I may need to downgrade my bootloader version based on the last ROM that I had on my tablet. If someone could educate me on that I'd appreciate it.
The 2nd link says I need the stock firmware for my country(I live in the U.S. of A.) and to nand erase all but I feel like that should be used as a last resort. I did download both N8013UEALI3(4.0.4) & N8013UEUCMI3(4.1.2) from sammobile.com though.
When I try to flash just a Recovery/ROM, with Autoreboot checked, I get the PIT error message below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.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>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT by its self, with Auto Reboot & Re-partition checked, I get the error message:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT by its self, Re-partition checked, I get the error message:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT w/ Recovery/ROM, Re-partition Checked and Auto-Reboot checked, I get:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Any assitance would be greatly appreciated, I've been without my tablet for a month now. I have any backup, I don't recall the ROM I flashed because it was so long ago, but I'm pretty sure the version was Jellybean. I know my recoevry was one of the later CWM TouchScreen Rom recoverys but I can't recall the version. Thanks for any help, please let me know what information I'm lacking or what I can do, thank you all for your time.

Update
Any assistance would be greatly appreciated. I have tried to different PIT files for the PIT mapping and they both failed. Getting pretty desperate now. I can't even NAND Erase All, I gave that a shot and it failed:
When I select NAND Erase All, stock rom(4.0.4 or 4.1.2), Pit, & Re-Partition checked, Nand Erase all Checked, I get the following in ODIN 3.07 and 3.09:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm starting to think its the ECCM and maybe I need a JTAG repair. Like I said before, I can't get into recovery, I just get a all white screen. When the tablet first died I got the Samsung logo and then it rebooted and went White, I never got the Samsung logo again. Any help please? Even if it's just recommendations for trusted JTAG repair sites, because I don't trust the ones I've found ths far. Or know PIT files that have worked for flashing on the N8013. Anything at all.

BUMP
I found this article here: http://www.sammobile.com/forum/showthread.php?t=23562
Exact same problem I am having, I think I'm going to need a JTAG repair. I just posted a request to get some fresh PIT files from multiple android versions. I ill keep posting updates on how this is going, I feel alone in this issue since no one has said anything but I get multiple views...but I see more and more people are starting to post in the help section for this particular brand of tablet in the past 3-5months, it sounds terrible but I'm glad I'm not alone since I feel like im talking to myself here.
Just contacted Mobiletechvideos guys, I hope they are legit. I'm will to pay $50 for a jtag repair if i can have this tablet back.

onlysafonne said:
I found this article here: http://www.sammobile.com/forum/showthread.php?t=23562
Exact same problem I am having, I think I'm going to need a JTAG repair. I just posted a request to get some fresh PIT files from multiple android versions. I ill keep posting updates on how this is going, I feel alone in this issue since no one has said anything but I get multiple views...but I see more and more people are starting to post in the help section for this particular brand of tablet in the past 3-5months, it sounds terrible but I'm glad I'm not alone since I feel like im talking to myself here.
Just contacted Mobiletechvideos guys, I hope they are legit. I'm will to pay $50 for a jtag repair if i can have this tablet back.
Click to expand...
Click to collapse
@onlysafonne what file fails? I see your log above

carl1961 said:
@onlysafonne what file fails?
Click to expand...
Click to collapse
I've tried to use both ODIN & Heimdall. All files are failing for me. I tried stock 4.0.4 & 4.1.2 Roms, 3 different PIT files, I even tried to NAND erase all with a stock rom and ODIN continues to fail for me. I installed a virutal box on multiple machines running XP SP3 since windows 7/8 weren't working for me as well, that failed as well. When I try to flash the PIT files I get the output from ODIN in my OP, nothing is working for me. I'm just thinking I experienced instant death on this tablet for no reason at all. The most success i've had is with Heimdall just being able to reboot the tablet for me and then go back to Downloading mode, but nothing else is responding for me.
I'f I can get some fresh pit files from fully operational devices I will know that I've done everything I can excluding JTAG repair myself. If I can't get some fresh PIT files from multiple android versions, then I might just have to send it to the Mobiletechvideos guys to see if they can repair.
Thanks for the reply and interest in my issue!

onlysafonne said:
I've tried to use both ODIN & Heimdall. All files are failing for me. I tried stock 4.0.4 & 4.1.2 Roms, 3 different PIT files, I even tried to NAND erase all with a stock rom and ODIN continues to fail for me. I installed a virutal box on multiple machines running XP SP3 since windows 7/8 weren't working for me as well, that failed as well. When I try to flash the PIT files I get the output from ODIN in my OP, nothing is working for me. I'm just thinking I experienced instant death on this tablet for no reason at all. The most success i've had is with Heimdall just being able to reboot the tablet for me and then go back to Downloading mode, but nothing else is responding for me.
I'f I can get some fresh pit files from fully operational devices I will know that I've done everything I can excluding JTAG repair myself. If I can't get some fresh PIT files from multiple android versions, then I might just have to send it to the Mobiletechvideos guys to see if they can repair.
Thanks for the reply and interest in my issue!
Click to expand...
Click to collapse
no I got the pit file from here http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
tell me how to grab it and I will get it from my tablet now for you

Heimdall
carl1961 said:
no I got the pit file from here http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
tell me how to grab it and I will get it from my tablet now for you
Click to expand...
Click to collapse
To download a copy of your PIT all you have to do is install Heimdall, with zadig driver (Samsung/General Device) , boot your tablet into Download mode, and download a copy of your PIT by going to Heimdall Frontend, clicking utilites, and downloading and saving your PIT to your desktop(or where ever you want) and uploading it for me.
Heimdall can be found here: http://glassechidna.com.au/heimdall/
After you are down with Heimdall, make sure you uninstall the driver from "Device Manager" in your USB Devices, that way, you can use ODIN again. A;; of this should only take about 5-10mins, as all the files are really small. i really appreciate this.

onlysafonne said:
To download a copy of your PIT all you have to do is install Heimdall, with zadig driver (Samsung/General Device) , boot your tablet into Download mode, and download a copy of your PIT by going to Heimdall Frontend, clicking utilites, and downloading and saving your PIT to your desktop(or where ever you want) and uploading it for me.
Heimdall can be found here: http://glassechidna.com.au/heimdall/
After you are down with Heimdall, make sure you uninstall the driver from "Device Manager" in your USB Devices, that way, you can use ODIN again. A;; of this should only take about 5-10mins, as all the files are really small. i really appreciate this.
Click to expand...
Click to collapse
@onlysafonne
ok I did it also a compair to My-N8013.pit that you said did not work, they or identical so that may be bad news for you.
thread
http://forum.xda-developers.com/showthread.php?t=1916936
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer

carl1961 said:
@onlysafonne
ok I did it also a compair to My-N8013.pit that you said did not work, they or identical so that may be bad news for you.
thread
http://forum.xda-developers.com/showthread.php?t=1916936
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Click to expand...
Click to collapse
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.

onlysafonne said:
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
Click to expand...
Click to collapse
if you not under warenty I would maybe buy a used one on ebay that might just have a cracked screen, you might even find a 32GB one
http://www.ebay.com/itm/Samsung-Galaxy-Note-10-1-32-GB-Wi-Fi-GT-N8013-/361155880699?pt=US_Tablets&hash=item54169166fb

onlysafonne said:
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
Click to expand...
Click to collapse
onlysafonne, I have the same problem. I can use Odin and get to CWM but nothing I flash will get me past the Samsung Galaxy Note 10.1 image I cannot even get it to shut off. It will go black then power right back up.
I have flashed with Nand Erase All checked only
KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_u ser_low_ship.tar
Any ideas? I have not heard of JTAG

I have a N8010 and I'm also in this kind of bootloop.
Nothing works.
I had OmniRom 4.4.4 installed and the newest TWRP.
I only can get into Download Mode.
When I try to get into Recovery the blue TWRP Screen pops up for a second and then it's going back to "Samsung Galaxy Note 10.1" Logo.
I even tried to disassemble the battery. But this didn't work either.
Any ideas what I can do? If not, I'll have to take it to repair. Got some warranty left, but I rather fix it myself.
Thanks

Flying_Phil said:
I have a N8010 and I'm also in this kind of bootloop.
Nothing works.
I had OmniRom 4.4.4 installed and the newest TWRP.
I only can get into Download Mode.
When I try to get into Recovery the blue TWRP Screen pops up for a second and then it's going back to "Samsung Galaxy Note 10.1" Logo.
I even tried to disassemble the battery. But this didn't work either.
Any ideas what I can do? If not, I'll have to take it to repair. Got some warranty left, but I rather fix it myself.
Thanks
Click to expand...
Click to collapse
have you tryed to odin install your firmware? usally the bootloop is caused because you need to do a factory reset to get rid of (in your case OmniRom 4.4.4) your firmware as I see is http://www.sammobile.com/firmwares/confirm/31427/N8010XXUDNE4_N8010BTUDNF1_BTU.zip/

Yes, I did try that. Is still in bootloop afterwards. I also tried to flash stock recovery or cwm recovery. But there is still twrp.
I can't open your link :-/

Flying_Phil said:
Yes, I did try that. Is still in bootloop afterwards. I also tried to flash stock recovery or can recovery. But there is still twrp.
I can't open your link :-/
Click to expand...
Click to collapse
try this N8010 recovery with the included 3.07 odin put in PDA slot and do no check re-partiton look at picture
@Flying_Phil
yes samfirmware is picky go here and search your N8010 you most likly need to signup (it's free) and as you see most odin updates or "home" which means it does not do a factory reset which is ok if your updating a stock unrooted rom so you need to do a factory reset when coming from a custom rom.

well I tried to flash your attached file. Odin said "Pass!" but my Tablet still does the bootloop.
Like I said, I tried to flash several firmwares. All with this same result. First I tried the German version, then the Austrian and the Australian.
Now yours was the version for new zealand.
I have no clue, why this doesn't work.
Here is the log from Odin and I attached a screenshot.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_N8010XXUDNK1_N8010NZCDNK1_Recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!

Flying_Phil said:
well I tried to flash your attached file. Odin said "Pass!" but my Tablet still does the bootloop.
Like I said, I tried to flash several firmwares. All with this same result. First I tried the German version, then the Austrian and the Australian.
Now yours was the version for new zealand.
I have no clue, why this doesn't work.
Here is the log from Odin and I attached a screenshot.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_N8010XXUDNK1_N8010NZCDNK1_Recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Click to expand...
Click to collapse
ok so did you try and reboot to stock recovery and do a factory reset

carl1961 said:
ok so did you try and reboot to stock recovery and do a factory reset
Click to expand...
Click to collapse
sorry, I forgot to tell about it.
Yes I tried to go into Recovery, but there ist still TWRP on it and it still crashes after a second.
I even tried the flash without checking "Auto reboot", so I could boot directly into recovery, but it worked neither.

Flying_Phil said:
sorry, I forgot to tell about it.
Yes I tried to go into Recovery, but there ist still TWRP on it and it still crashes after a second.
I even tried the flash without checking "Auto reboot", so I could boot directly into recovery, but it worked neither.
Click to expand...
Click to collapse
ok lets backtrack
what is your tablets stock info? and or you 16 GB or 32 GB

carl1961 said:
ok lets backtrack
what is your tablets stock info? and or you 16 GB or 32 GB
Click to expand...
Click to collapse
GT-N8010 16GB. Need more?

S6 SM-G920F bricked after software update

My S6 is a SIM FREE unlocked SM-G920F bought from Amazon UK, version: PHONE: OGE(BTU). I saw a software update available, so I selected it to install the update on the phone. However, the update stuck at 72%, I had to reboot the phone manually, after that the phone loop at the Samsung logo screen…
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU2BOG8_G920FBTU2BOG9_G920FXXU2BOGE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to use Odin to flash the system, but failed. I tried Kies, also failed… says "The PC failed to recognise the mobile phone."
Any suggestions? Thanks!!!

This happened to me with my S5. It was solved applying a custom ROM (If I recall well, it was WanamLite Rom) and then when it booted correctly, I used Odin to flash an official Rom.
Now with my S6, yesterday while I was flashing custom recovery into 5.1.1 and something happened when I rebooted my phone as it was stuck at samsung logo. So I flashed a custom Kernel using Odin and problem solved.
First, I would recommend to flash this ROM (G920F) in Odin first: https://mega.nz/#!fRNwGZ5A!5hS8vFU66FODwUvgxP4FCDG06I5y7nAVQZAqbsFkUCE
Drivers: https://mega.nz/#!XNdBUCpa!fbPSU3aaHSbBrlZVwWF_PaVDvtKqJc5EorGwFtXkel4
Odin: https://mega.co.nz/#!epshkJAa!y7pFS5-9RVhp4vDxTRAQARAwkjyQAB_9mDZWfXkLqko
This would give you a clean and official update.
Also, there's a guide here in XDA you can follow to get out of samsung loop, the guide is here: http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/how-to-to-5-0-2-t3142946
Hope it solves your problem.

Try a different USB cable or USB port then reflash again via odin.
---------- Post added at 02:16 AM ---------- Previous post was at 02:14 AM ----------
If above suggestions don't work bring your S6 back to Samsung for warranty repair.

You need to be 100% sure about your CSC.
Mine also fails when updating with wrong CSC. Went back to original and update went normal.

Nees3 said:
You need to be 100% sure about your CSC.
Mine also fails when updating with wrong CSC. Went back to original and update went normal.
Click to expand...
Click to collapse
Where can I get the right CSC? I only use AP in Odin and it failed!

I tried every suggestions above and a different PC, no luck... really sad... why install the official update can brick the phone!! Is there anything more I can do, or should I try the Samsung warranty?

Have you tried the hidden.img fix? If you haven't let me know and I'll try to dig up the thread for you

you could put your phone into download mode, enter smart switch PC application, select emergency firmware recovery. key in SM-G920F, then key in your Serial number found at the back of your physical device S/N: XXXXXXXXX and then it'll start downloading the firmware appropiate for your phone. hang tight and should be done shortly after.

If the above fails I'd recommend taking it to a samsung shop, it's failed to update the official way so they should be fixing it themselves for you, they can do a service flash / update on your phone in about 20 minutes.

T-Mobile Samsung Bricked: Error Code SW rev.check fail. Device 3 Binary 2

So I recently decided to root my T-mobile Galaxy Note 5 (SM-N920T) and the root was a sucess. After the root, i installed Xposed Framework and somewhere in the process of installing the .zip in the recovery mode, it locked into a bootloop on the t-mobile screen...
So I look into how to re-flash the phone back to stock, knowing that i can just re-root but when i did the factory reset, i noted that after the process, it said Go back or reboot system. when i hit reboot system in says NO OS INSTALLED ARE YOU SURE YOU WANT TO CONTINUE?...
After hitting yes, it loads a boot looped in the "samsung powered by Tmobile" screen, not even making it to the tmobile splash screen...
When i connect my phone to the computer via micro USB, it still actually connects with the name "SM-920C" as the device name, and when you click into it there is only one folder (no Andriod, pictures music etc) and the folder was TWRP, my recovery.
Here is my phone setting:
Phone: Samsung Galaxy Note 5
Model: SM-N920T
H/W: REV0.2
S/W: N920TUVS2COKC
Date: 3/18/16
Here's my setting info proir to bootloop:
-USB Debugger was active / enabled
-OEM Option in dev options was actice / enabled
-TWRP is installed prior but no backup was made.
-TWRP still actively works when holding volume up+home+power
-ADB is enabled on my PC / Device
-Latest Samsung Drivers are up to date
Here's where i am at:
8:00am - Bricked with bootloop (tmobie splash)
8:30am - Downloaded odin 3.10.7
9:00am - Watched/Read multile tutorials on the process to reflash back to stock
10:00am - Downloaded N920TUVU1BOH6_HOME.tar.md5
11:00am - -Attempted flash with odin 3.10.7 (FAILED) SW rev check fail: Device 3 Binary: 2
11:30am - Downloaded N920TTMB3DPG1_TMB_Home.tar.md5
12:30pm - -Attempted flash with odin 3.10.7 (FAILED) SW rev check fail: Device 3 Binary: 2
1:00pm - Downloaded N920TUVU2DPD1_HOME.tar.md5
2:30pm - -Attempted flash with odin 3.10.7 (FAILED) SW rev check fail: Device 3 Binary: 2
3:00 - 5:30 Dowloaded verion over versions of the firmware from a site and the download crashed after 99%
6:00pm Found Box for Note5, Box notices: "S/W N920TUVS2COKC"
6:30pm - Downloaded 2 versions of N920TUVS2COKC from Sammobile.com and Samsung-Firmware.org
10:00pm First of 2 finshed downloading (Samsung-Firmware.org)
10:15pm - -Attempted flash with odin 3.10.7 (FAILED) SW rev check fail: Device 3 Binary: 2
10:20pm - writing the Forum for help.
ODIN LOG:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N920TUVS2COKC_N920TTMB2COKC_N920TUVS2COKC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I know the main response will be to Download the appropriate firmware as the comments ive read in similar threads insist and i assure you that my phone box as well as the firmware i downloaded and flashed last before giving up and writing here is S/W: N920TUV2COKC and thats the same firmware i am trying to flash when given the error in Download Mode.
Can Someone please Help me? Much Appreciated.
EDIT: ODIN ATTEMPT WITH ODIN 3.11.1 (supposely better compatability with Marshmellow...?)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ON PHONE
ERROR: SW REV. CHECK FAIL: DEVICE:3 Binary: 2

Use smart switch on pc and go to emergency software recovery then initialization
Sent from my SM-N920T using Tapatalk
---------- Post added at 08:28 AM ---------- Previous post was at 08:28 AM ----------
Also be sure your usb cable is in good shape
Sent from my SM-N920T using Tapatalk

aPoCxMoDz said:
So I recently decided to root my T-mobile Galaxy Note 5 (SM-N920T) and the root was a sucess. After the root, i installed Xposed Framework and somewhere in the process of installing the .zip in the recovery mode, it locked into a bootloop on the t-mobile screen...
So I look into how to re-flash the phone back to stock, knowing that i can just re-root but when i did the factory reset, i noted that after the process, it said Go back or reboot system. when i hit reboot system in says NO OS INSTALLED ARE YOU SURE YOU WANT TO CONTINUE?...
After hitting yes, it loads a boot looped in the "samsung powered by Tmobile" screen, not even making it to the tmobile splash screen...
When i connect my phone to the computer via micro USB, it still actually connects with the name "SM-920C" as the device name, and when you click into it there is only one folder (no Andriod, pictures music etc) and the folder was TWRP, my recovery.
Here is my phone setting:
Phone: Samsung Galaxy Note 5
Model: SM-N920T
H/W: REV0.2
S/W: N920TUVS2COKC
Date: 3/18/16
Here's my setting info proir to bootloop:
-USB Debugger was active / enabled
-OEM Option in dev options was actice / enabled
-TWRP is installed prior but no backup was made.
-TWRP still actively works when holding volume up+home+power
-ADB is enabled on my PC / Device
-Latest Samsung Drivers are up to date
Here's where i am at:
8:00am - Bricked with bootloop (tmobie splash)
8:30am - Downloaded odin 3.10.7
9:00am - Watched/Read multile tutorials on the process to reflash back to stock
10:00am - Downloaded N920TUVU1BOH6_HOME.tar.md5
11:00am - -Attempted flash with odin 3.10.7 (FAILED) SW rev check fail: Device 3 Binary: 2
11:30am - Downloaded N920TTMB3DPG1_TMB_Home.tar.md5
12:30pm - -Attempted flash with odin 3.10.7 (FAILED) SW rev check fail: Device 3 Binary: 2
1:00pm - Downloaded N920TUVU2DPD1_HOME.tar.md5
2:30pm - -Attempted flash with odin 3.10.7 (FAILED) SW rev check fail: Device 3 Binary: 2
3:00 - 5:30 Dowloaded verion over versions of the firmware from a site and the download crashed after 99%
6:00pm Found Box for Note5, Box notices: "S/W N920TUVS2COKC"
6:30pm - Downloaded 2 versions of N920TUVS2COKC from Sammobile.com and Samsung-Firmware.org
10:00pm First of 2 finshed downloading (Samsung-Firmware.org)
10:15pm - -Attempted flash with odin 3.10.7 (FAILED) SW rev check fail: Device 3 Binary: 2
10:20pm - writing the Forum for help.
ODIN LOG:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N920TUVS2COKC_N920TTMB2COKC_N920TUVS2COKC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I know the main response will be to Download the appropriate firmware as the comments ive read in similar threads insist and i assure you that my phone box as well as the firmware i downloaded and flashed last before giving up and writing here is S/W: N920TUV2COKC and thats the same firmware i am trying to flash when given the error in Download Mode.
Can Someone please Help me? Much Appreciated.
EDIT: ODIN ATTEMPT WITH ODIN 3.11.1 (supposely better compatability with Marshmellow...?)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ON PHONE
ERROR: SW REV. CHECK FAIL: DEVICE:3 Binary: 2
Click to expand...
Click to collapse
You need to extract the files from the md5 and flash them individually and do not let the phone auto reboot turn that off and every time you flash 1 shut the phone down boot back into download mode and do it again until all files are flashed then boot.
By the way extract the md5 and then again extract the tar to get the files!

Smart Switched FAILED
{
"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"
}
Picture link (This site wont post my screenshot picture)
h TEE TEE PEE://
postimg.......... DOT.....ORG
/image/ xbpt3lpj5)
- added link phonetically because site wont let me post "outside links" to Postimg dot org, you'll have to reconnect the link to see the error.
Thanks for the reply but Smart Switch failed before it even started. (See picture)
It says that my phone (NOTE5 SM-N920T) is not supported with Smart Switch the second that i plugged it up.
I also wanted to note that my phone is new (purchased June 2016) so the USB cord that i am using is the stock white cord that came with the phone and it is in excellent condition.
I also wanted to update my progress from my last post when i noted that i downloaded 2 different versions of the N920TUVS2COKC firmware as this is the SW noted on the bo of my phone:
-Both N920TUVS2COKC's Downloaded 100% (Sammobile.com and Samsung-Firmware.org)
-Both Extracted the 1.7G file 100%
-Both mounted into the "AP" section of Odin
-Used two different versions of ODIN (3.10.7 and 3.11.1)
-Both concluded with the same ERROR in download mode: SW rev check failed: Device 3 Binary 2
Is there something i need to do with ADB and CMD? on my PC if i type ADB i get a LOT of options.... or do i need to, or can i do this process in the recovery TWRP mode that i still have access to? Since ODIN doesnt work for Note5's, I am exhausted of any ideas to get the OS back on the phone.
(See picture for ODIN and Smart Switch details
Please help me find a fix. Greatly appreicated.

aPoCxMoDz said:
Picture link (This site wont post my screenshot picture)
h TEE TEE PEE://
postimg.......... DOT.....ORG
/image/ xbpt3lpj5)
- added link phonetically because site wont let me post "outside links" to Postimg dot org, you'll have to reconnect the link to see the error.
Thanks for the reply but Smart Switch failed before it even started. (See picture)
It says that my phone (NOTE5 SM-N920T) is not supported with Smart Switch the second that i plugged it up.
I also wanted to note that my phone is new (purchased June 2016) so the USB cord that i am using is the stock white cord that came with the phone and it is in excellent condition.
I also wanted to update my progress from my last post when i noted that i downloaded 2 different versions of the N920TUVS2COKC firmware as this is the SW noted on the bo of my phone:
-Both N920TUVS2COKC's Downloaded 100% (Sammobile.com and Samsung-Firmware.org)
-Both Extracted the 1.7G file 100%
-Both mounted into the "AP" section of Odin
-Used two different versions of ODIN (3.10.7 and 3.11.1)
-Both concluded with the same ERROR in download mode: SW rev check failed: Device 3 Binary 2
Is there something i need to do with ADB and CMD? on my PC if i type ADB i get a LOT of options.... or do i need to, or can i do this process in the recovery TWRP mode that i still have access to? Since ODIN doesnt work for Note5's, I am exhausted of any ideas to get the OS back on the phone.
(See picture for ODIN and Smart Switch details
Please help me find a fix. Greatly appreicated.
Click to expand...
Click to collapse
Odin works fine for the Note 5. The error you are receiving is because you have the latest software and security on your phone. You cant downgrade once you take the latest update PG1. You need to download the PG1 firmware and flash it.
You did not factory reset in the recovery. You went to advanced and you wiped system partition, that's why it told you you had no OS installed. Please find proper instructions before attempting next time. also use odin 3.10.6 or 7.

Sounds like you have the advice you need but I would also suggest if you are going to use xposed always also have the uninstall zip in case you need it, also after installing xposed it takes a while, a good while to boot up.

supreme83 said:
Odin works fine for the Note 5. The error you are receiving is because you have the latest software and security on your phone. You cant downgrade once you take the latest update PG1. You need to download the PG1 firmware and flash it.
You did not factory reset in the recovery. You went to advanced and you wiped system partition, that's why it told you you had no OS installed. Please find proper instructions before attempting next time. also use odin 3.10.6 or 7.
Click to expand...
Click to collapse
This is exactly the correct answer...i neglected to notice you had taken the pg1 update...once the bootloader is updated it sometimes will not allow you to go back, this is often the case in security updates, so yes it will DEFINITELY fail on any earlier version...and again, the odin version matters, for some reason I've always had the best luck with 3.10.6 until mm and then 3.10.7 seemed to get the job done where 6 did not, but i would still recommend TRYING 6 with pg1 fw and see how it goes, then again w/7 if 6 fails...lastly, if nothing else works i can extract the fw tar.md5 and repackage it into BL, CP, AP, RECOVERY for flashing individual files in odin...if you still have access to twrp just flash a stock rooted pg1 rom zip...if none exists yet I'll make you one...
Sent from my SM-N920T using Tapatalk

EDIT: Thanks all in the thread, the PG1 stuck finally, and it the conflicted is solved. Thanks agains, jabs and all

aPoCxMoDz said:
EDIT: Thanks all in the thread, the PG1 stuck finally, and it the conflicted is solved. Thanks agains, jabs and all
Click to expand...
Click to collapse
Sweet!
Sent from my SM-N920T using Tapatalk

When you say the DPG1 finally stuck, What do you mean? I mean what was your exact procedure to getting your phone up and running again? Just in case anyone else runs into the same problem..
Thanks in advance..

Satan_Neil said:
When you say the DPG1 finally stuck, What do you mean? I mean what was your exact procedure to getting your phone up and running again? Just in case anyone else runs into the same problem..
Thanks in advance..
Click to expand...
Click to collapse
yes i would love to know what this means, am also having problems unbricking my note 5

HI guys I'm sort of new here but I'm haveing similar problems Ive read a lot of posts in the last few days in hope of finding a solution for phone. I'm stuck with a frp lock and a drk is there anyway to fix this. All help is welcomed and appreciated I can't go even getc passed stock recovery