Database Info

[Q] [HELP THE NOOB] A weird case of softbrick.

Dear XDA,
Such a warm heartening welcome I felt after watching the Noob video. I am noob.
I've been a lurker for quite a long while, but only this harrowing case of a softbrick that has hit my N8000 that has encouraged me to register and actually post.
Here's how it went:
I took a nap on Monday afternoon, my Note was left charging, it was working just fine. I get up, I look around for it, It was stuck on "Samsung Galaxy Note 10.1", the bootscreen.
I've been trying a lot of stuff for the past three days, here it goes:
Good news:
I can boot into download mode. I can get into recovery mode (High On Android's CWM)
Bad news:
I can't flash anything through ODIN, it gives me a "Complete(Write) operation failed."
Recovery mode always displays "E:can't mount cache/recovery/log" "E:Can't open /cache/recovery/last_log"
I can only mount /cache and /system in "Mounts and Storage", the rest give me a mounting error.
I tried getting into it through adb, but it says "unauthorized" next to my device.
Is there hope? I read this might be a corrupt NAND because of the NAND fail on ODIN. But I can get into both download mode AND recovery, so there is hope, right? RIGHT?
I also have tried a couple USB cables, both ODIN 1.85 and ODIN 3.07, I wanted to try Heimdall; I tried 1.1, it doesn't detect my device. Heimdall 1.4 on the other hand detects my device, but I can't flash recovery through it (It only acceps Heimdall Firmware? Packages?)
Also on Good news, I ran an emmc scanner, and it gave me OK on every singe line from start to end. (0 to 15750 *or something round that number*)
HELP THE NOOB. HELP THE NOOB. HELP THE NOOB. :fingers-crossed:

try to do a factory reset from recovery

Sounds like a corrupt .pit file.
What's your tablet model?

@jaspreet: I tried Factory recovery, but it's useless.
@kalashiencof: It's a 16gbs N8000.
I'm wondering if there's any way to get it to boot from an external sdcard? Until I can fix the internal sdcard? Nuke it and rebuild it or something?
ANY HOPE?

The tablet appers to be useless as of now, I would recommend you to flash a new .pit with Odin, then flash the original firmware.
You can find the .pit file for your model here in the forum.
Note: flashing a new .pit file is very dangerous. It could brick your tablet even more. Make sure you only flash the correct one!
Just a personal opinion: High On Android CMW is now pretty out dated, I recommend you to install TWRP, or Philz Recovery (this one is based on CMW)
Sent from my GT-I9000 using XDA Premium 4 mobile app
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
I found a thread with a N8000 .pit file.
http://forum.xda-developers.com/showthread.php?t=2363703
When you go to download the firmware for the tablet make sure you choose the correct firmware, that .pit file is for android 4.0.4 (ICS).
To download the correct firmware go to http://www.sammobile.com/firmwares/2/, make sure you have an account (it´s free) and choose the correct firmware for your tablet.
PS: Any (4.0.4) firmware should work but just to make sure, you should choose the one that came with your tablet.
Best of luck in restoring your tablet.

@kalashenicof : I'd like to thank you for trying to help. I tried what you posted again and again and again, but not luck. Still getting problems flashing from Odin.
There must be any other way, it can't be dead, can it? Like, I still can access both Recovery and Download mode, any hope?

@ayeladawy
What appened when you try to flash the .pit file?
---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------
Have you tried to flash another rom via recovery?

kalashenicof said:
@ayeladawy
What appened when you try to flash the .pit file?
---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------
Have you tried to flash another rom via recovery?
Click to expand...
Click to collapse
@kalashenicof Flashing a pit file gives me a "Re-partition operation failed." message, almost everything else says Complete(Write) operation failed.
I've tried to flash another cyanogenmod rom via recovery, didn't make a difference, but I haven't tried flashing a different rom, any suggestions?

ayeladawy said:
@kalashenicof Flashing a pit file gives me a "Re-partition operation failed." message, almost everything else says Complete(Write) operation failed.
I've tried to flash another cyanogenmod rom via recovery, didn't make a difference, but I haven't tried flashing a different rom, any suggestions?
Click to expand...
Click to collapse
Take a look here -> http://forum.xda-developers.com/showthread.php?t=804695
It seens that some times the problem is with odin it self. Try to flash a stock firmware several times without closing odin, see if that helps.
And try diferent versions of odin, i think there's a new version 3.09??

bump!!?

[Q] GT-I9300I dead

Hi, Samsung Galaxy S3 Neo of my friend is dead, it can boot only into fastboot mode (it goes in bootloop if I boot it normally, and it powers off if I boot in recovery).
I've tried flash by Odin all firmwares with different basebands from here: https://www.sammobile.com/firmwares/database/GT-I9300I/ .
All gave me same error (NAND (write) error).
Seems that Odin can't writes on the device, but it flashes recoveries and the root package, infact appears "PASS" on Odin.
However if I try to boot in recovery appears written "RECOVERY IS NOT SEANDROID ENFORCING" or the device powers off after 2 seconds.
Sorry for bad english.
Thanks if someone can help me.
Cheers.

Pendragon2000 said:
Hi, Samsung Galaxy S3 Neo of my friend is dead, it can boot only into fastboot mode (it goes in bootloop if I boot it normally, and it powers off if I boot in recovery).
I've tried flash by Odin all firmwares with different basebands from here: https://www.sammobile.com/firmwares/database/GT-I9300I/ .
All gave me same error (NAND (write) error).
Seems that Odin can't writes on the device, but it flashes recoveries and the root package, infact appears "PASS" on Odin.
However if I try to boot in recovery appears written "RECOVERY IS NOT SEANDROID ENFORCING" or the device powers off after 2 seconds.
Sorry for bad english.
Thanks if someone can help me.
Cheers.
Click to expand...
Click to collapse
Samsung doesn't have fastboot, they have download mode also known as Odin mode.
You've probably got a locked bootloader, that would prevent TWRP from booting, it would also prevent Odin flashing firmware that is older than what you already had. With locked bootloader you a only flash your current stock firmware or newer, you can't flash an older firmware than the previous version you had.
Try using Odin again with the newest available stock firmware for your model number, there is a thread in the S2 GT-I9100 forum for troubleshooting a failed Odin flash.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Samsung doesn't have fastboot, they have download mode also known as Odin mode.
You've probably got a locked bootloader, that would prevent TWRP from booting, it would also prevent Odin flashing firmware that is older than what you already had. With locked bootloader you a only flash your current stock firmware or newer, you can't flash an older firmware than the previous version you had.
Try using Odin again with the newest available stock firmware for your model number, there is a thread in the S2 GT-I9100 forum for troubleshooting a failed Odin flash.
Click to expand...
Click to collapse
Is this: https://goo.gl/6ooKfR ? Can you link me the tread?

Pendragon2000 said:
Is this: https://goo.gl/6ooKfR ? Can you link me the tread?
Click to expand...
Click to collapse
I'd rather teach you how to use XDA to find it yourself.
View this forum in a browser then look at top of page and find the "search all forums" search box, in that box type:
"Failed Odin flash"
That will find the thread I'm talking about.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
I'd rather teach you how to use XDA to find it yourself.
View this forum in a browser then look at top of page and find the "search all forums" search box, in that box type:
"Failed Odin flash"
That will find the thread I'm talking about.
Click to expand...
Click to collapse
I've only found the thread linked on my last post and another one that describes how unbrick a device with a micro SD.

Pendragon2000 said:
I've only found the thread linked on my last post and another one that describes how unbrick a device with a micro SD.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Sent from my SM-S903VL using Tapatalk

Droidriven said:
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Click to expand...
Click to collapse
Ok it's the thread that I've already linked.
I've read the guide, however the odin flash fail. I think the mother board is dead, because pit flash fails.

No OS Found \ SW Check Fail [aboot]: fused 3/Binary 2 Error

If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.

Rawbert.Watkins said:
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Click to expand...
Click to collapse
CFW?
You need a revision 3 firmware.

Rawbert.Watkins said:
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Click to expand...
Click to collapse
Did you do your NANDROID backup to the phone? If so, wiping it would of course wipe out your backup. If you chose a complete wipe, it would even wipe the sd card.
Doh!
I'm not laughing, I did this not long ago myself, and I've rooted dozens of devices.
I'll search for a solution to this, no promises.

ashyx said:
CFW?
You need a revision 3 firmware.
Click to expand...
Click to collapse
CFW=Custom FirmWare
Sent from my Samsung Galaxy Trend Plus using XDA Labs

I'm getting the same error. I was fortunate enough to have another device available and pulled a backup from that device. But I need to use Odin to flash a different modem to get WiFi working again. It currently won't turn on and stays greyed out. It's been a couple weeks since this topic was posted. Any luck getting Odin to work?
Sent from my SM-G950U using Tapatalk

equitube said:
Did you do your NANDROID backup to the phone? If so, wiping it would of course wipe out your backup. If you chose a complete wipe, it would even wipe the sd card.
Doh!
I'm not laughing, I did this not long ago myself, and I've rooted dozens of devices.
I'll search for a solution to this, no promises.
Click to expand...
Click to collapse
Any word by chance?
Sent from my SM-G950U using Tapatalk

lancemulvihill85 said:
Any word by chance?
Click to expand...
Click to collapse
You need a matching NON-HLOS.bin flashed to the APNHLOS partition. You can flash this with TWRP.
However if you'd have paid attention to my previous post all you need to do is flash the correct firmware with odin.

ashyx said:
You need a matching NON-HLOS.bin flashed to the APNHLOS partition. You can flash this with TWRP.
However if you'd have paid attention to my previous post all you need to do is flash the correct firmware with odin.
Click to expand...
Click to collapse
I can't figure out how to flash to that partition with twrp. Just zipping the .bin to .tar and flash just doesn't fly. I apologize for my ignorance in the matter. However I was paying attention, and read the few previous posts. My situation is a little different. The last 3 letters of the current firmware end in QL3. And I can't seem to find that build ANYWHERE. When using the sammobile app to figure out what it's currently running, the CSC partition is empty. I have no CSC. When googling how to flash a CSC with twrp, I run into dead ends about using Odin (which will not work for my build). I'll post screenshots in a lil bit if anyone would help. I'm at a loss right now
Sent from my SM-G950U using Tapatalk
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
Basically, I have a working build, but WiFi is broken. It won't turn on. That's all I need. And I've been googling for about 2 weeks trying to figure this out
Sent from my SM-G950U using Tapatalk

lancemulvihill85 said:
I can't figure out how to flash to that partition with twrp. Just zipping the .bin to .tar and flash just doesn't fly. I apologize for my ignorance in the matter. However I was paying attention, and read the few previous posts. My situation is a little different. The last 3 letters of the current firmware end in QL3. And I can't seem to find that build ANYWHERE. When using the sammobile app to figure out what it's currently running, the CSC partition is empty. I have no CSC. When googling how to flash a CSC with twrp, I run into dead ends about using Odin (which will not work for my build). I'll post screenshots in a lil bit if anyone would help. I'm at a loss right now
Sent from my SM-G950U using Tapatalk
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
Basically, I have a working build, but WiFi is broken. It won't turn on. That's all I need. And I've been googling for about 2 weeks trying to figure this out
Click to expand...
Click to collapse
You don't need to flash the same build, you just need the right revision and version of Odin.
What is the error on the device when flashing the firmware?

Need help with Odin, cannot return to stock :(

Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try

GODSPD said:
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Click to expand...
Click to collapse
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk

Droidriven said:
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...

GODSPD said:
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...
Click to expand...
Click to collapse
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk

Droidriven said:
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
Thanks for the feedback.
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...

GODSPD said:
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...
Click to expand...
Click to collapse
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
more than you can imagine, every possible wipe and combination has been done with no luck at all

GODSPD said:
more than you can imagine, every possible wipe and combination has been done with no luck at all
Click to expand...
Click to collapse
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
That definitely makes sense that i cannot downgrade but i am flashing either the same firmware or slightly newer staying on the same bootloader version.

Any ODIN flashable Rom Request

hi all, I've managed to brick my SM-P900.
Could someone point me to where I can get an Odin flashable rom please, with all the individual bits such as PDA / Phone / CSC.
I can't flash normal roms, it's not working with just the md5. Ideally stock, but happy with any rom as I can flash something else with TWRP.
I can't use any of the normal samsung sites as they're paid, and I'm broke =(
I would really appreciate it if you could help me fix this.
Many thanks

Google
SM-P900 - Samsung Firmware | Samsung Updated
---------- Post added at 03:14 AM ---------- Previous post was at 03:09 AM ----------
https://forum.xda-developers.com/galaxy-note-pro-12/general/firmware-firmware-t3038178

Where you able to solve your problem?

bmwdroid said:
Where you able to solve your problem?
Click to expand...
Click to collapse
x2 for me also

sp000n said:
x2 for me also
Click to expand...
Click to collapse
Sorry, don't understand.
Problems or just interested as well?

Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!

Zophixan said:
Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!
Click to expand...
Click to collapse
Did you get the multiple part ROM using samfirm_reborn tool?

bmwdroid said:
Did you get the multiple part ROM using samfirm_reborn tool?
Click to expand...
Click to collapse
Just tried downloading it and I get .tar.md5 file, not sure how i did it but from a previous attempt at fixing it, I have the same thing but in seperate files, with boot, cache, hidden, recovery s boot and system. Do i need to put them into odin? where do they go? I get stuck on initialising, tried pulling out cable and putting it back in, then it says it can't find a pit partition... tried flashing a pit file but still stuck on initiailising so pit doesn't flash.

@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?

bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
I've tried odin 3.07 and 1.85. I downloaded samfirm_reborn and upon use it downloaded just one file "SM-P900_1_20170222195126_gly008r5gf.zip" and inside it is the tar md5. Where can I get the separate items?
Even if I am not using the seperated one, shouldn't odin flash? It's always stuck on intiailising, I don't know if this matters but it says knox warranty 0500 on the download screen, and custom kernal / binary.
I remember having a similiar problem years ago on the same tablet but no idea how I fixed it, vaguely remember downloading seperate files to flash in each of the odin sections.
thanks.
EDIT, found the binary option nature option, will download now and try flashing each bit and report back...

bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
Still stuck on initializing, tried samsung drivers, even tried heimdall (and installed it's drivers), is there anything else I can try?
It says AP SWREV A1 and know warranty voide 0500, and current binary / system status as custom on the tablet.

Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.

bmwdroid said:
Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.
Click to expand...
Click to collapse
I tried both 3.10 and 3.09 but still stuck on initialisation... (do i need to do anything with CP or UMS field?),
does the current binary/ system status as custom ,or AP SWREV A1, or knox warranty mean anything?
Do you have any other suggestions, I can't think of anything else! =(

Knox was triggered when flashing other than stock.
Forget about it.
Other is shown on mine as well.
CP stays empty at WiFi models.
UMS I've never did anything with.
Try to use other cables and USB ports.