yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] ecs87:
First off I can't believe [MENTION=5553888]msmercy42[/MENTION] only got 12 likes in the OP and secondly hopefully that mention brings them out of hiding! Lol. The OP needs to be updated urgently. We did get a streak of people that it helped on 4.3 but I didn't expect the guide to have to be updated so soon for 4.4.2. And we have a "test subject". I think there's a N900T at work I can mess with in case we need more bytes in an image.

I'd REALLY like to hope Samsung didn't lock this out in Kit Kat. Sure it provided some loopholes BUT it also saved them money by having users who are able to recover via this method instead of spending Samsung's time and money servicing their phones if not sending out replacements. I'm not ready to go back to just IEEE JTAG as the only source of recovering a hard brick ;-(

Sent from my SPH-L900. Please hit the thanks button if I helped you out!

---------- Post added at 08:06 PM ---------- Previous post was at 08:03 PM ----------

That's fine. Do as noobtoob says and write the image to a sd card using a Linux terminal. As long as you have it being recognized as QCHSUSB or something along those lines you're recoverable. You may need to spend some money on some class 10 SD cards but trust me...as long as you have the qualcomm port in your device manager you're recoverable (as long they didn't lock down the KK bootloader)

Sent from my SPH-L900. Please hit the thanks button if I helped you out!
[T-Mobile Samsung Galaxy Note 3] noobtoob:
It doesn't boot after you have imaged the SD card? Were you on Kit Kat? If so, this method may not work. I have a lot of people who have downloaded the image from my media-fire but no one has posted back.

I hear that. My original bootloop recovery zip and heimdall restore method had like 3 likes but close to 1k downloads. Free-loaders....LOL. I don't mind the sharing, and I like to do this as a hobby, but a simple thanks does go a long way.

Also glad to hear we have a test subject. We need to know if this actually works or not.
[T-Mobile Samsung Galaxy Note 3] Lorettaa:
So it's not yet verified if it works or not?
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
I didn't know there was a 'like' button until you guys mentioned it. I normally read XDA forums with the Android application and it only has the 'thanks' button.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Not until someone reports back. We need to have someone with a hard bricked Kit Kat boot loader try this out. Has been verified many times on 4.3, but not once on 4.4.

With the 4.4 boot loader being locked down as much as it is, it is hard to say if it will work.

---------- Post added at 03:22 PM ---------- Previous post was at 03:18 PM ----------

You don't see it? Here's a screen shot...
[T-Mobile Samsung Galaxy Note 3] Lorettaa:
We gotta wait for the test subject to report and give us an update here.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
I don't have that on my application. It's the same application I've been using since Android 1.6 so maybe it's been updated, or maybe you have a pay-version.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
No man. I was just joking. We meant the thanks button. I thought you would get my scribbled out thanks edit to reflect the "like" in my bad handwriting. LOL.
[T-Mobile Samsung Galaxy Note 3] ecs87:
Excuse me sir noobtoob...might you happen to have the PIT file for the N900T? Although I managed to help unbrick a radio corruption bootloop...I tried to go further with it and discovered the partition I'm trying to write to is probably impossible to write to in Odin because it has no filename extension Odin recognizes. HOWEVER...Heimdall might be able to help out. The thing is, I couldn't find a N900T PIT file. And I didn't want to risk using the N900A pit file (although I shouldve, considering I had both a N900A and N900T I could've installed partition manager on to compare partitions...I'm a lazy ass). Also I tried to print the PIT from Heimdall...yeah saw your thread on it too lol. KitKat BL sucks big ones.

If I do discover what I'm looking for, I doubt any GSM box will ever require root again to perform any service. Very interesting indeed.
[T-Mobile Samsung Galaxy Note 3] juan5600:
I just got from newegg 3 sd cards 10 of 32gb and i'm gonna try with linux an windows, wish me luck

---------- Post added at 02:30 AM ---------- Previous post was at 02:20 AM ----------

hey my friend can PLEASE PLEASE PLEASE tell me how to write the image from a linux terminal, ofcourse i have a ubuntu live cd and believe me i purchased 3 sd cards class 10, thank you so much
[T-Mobile Samsung Galaxy Note 3] noobtoob:
http://www.mediafire.com/?rmkwywfo8ft2825

Even though it says kk pit file, it is the same as the original.

If you don't trust it, you can grab the one from this zip file.

http://www.mediafire.com/?qmy3oy7ph10jdow

Enjoy.
[T-Mobile Samsung Galaxy Note 3] ecs87:
dd if=/sourcefolder/filename of=/destinationfolder/filename to replace

---------- Post added at 09:43 PM ---------- Previous post was at 09:42 PM ----------

Err dumb post.

dd if=/sourcefolder/file of=/sdcardpartition/

Don't drink and develop kids.
[T-Mobile Samsung Galaxy Note 3] ecs87:
So I was an idiot and also have a hard bricked n900t. For those wondering about my specific case...I was knowingly writing things to partitions I shouldn't have. I just didn't expect it to end up in a hard brick. Facepalm. I've done some looking around and it seems that the usb jig used on all previous models might work...no one's tried it though. I emailed mobile tech videos asking them if our model is supported and am awaiting a response. If I don't get one by this evening I'll just order it. It'll be nice to have around the shop anyway.

Btw, my .02 is that system dumps won't solve anything for a HARD brick. From my limited amount of knowledge (but a whole lot of skimming through multiple hard brick incidents) it seems that the bootloader somehow gets borked. The key is getting back into download mode. After Odin recognizes the phone (which it will NOT do in the event of a hard brick) THEN you can consider yourself in the clear. When Odin doesn't recognize your phone or when you're not able to get into download mode, you've seriously messed something up.

PS: I've tried making a Linux live cd and using the n900a dead boot method by using the Linux terminal to create a boot card from an SD card. Didn't work at all. Screen still black as night with a weird QHUSB (I think I spelled that right) port showing up in device manager.

PPS: I know it says sent from my L900. I have a N900t here at the shop I was toying with, hence my appearance here :P
[T-Mobile Samsung Galaxy Note 3] KillaHurtz:
A jig will work, but that's just to get into download mode if you had, say, a broken button that is needed for the combo usually used.
[T-Mobile Samsung Galaxy Note 3] ecs87:
I figured. I called them up and ended up finding out they offer a JTAG service for the n900t despite their website not mentioning it. It is the same price as the Note 2 JTAG service. Might just have to chalk it up and go that route...unless someone wants to pull something from their n900t with adb commands to see if i can get it to boot with a SD card trick used on the n900a.
[T-Mobile Samsung Galaxy Note 3] Ms. K:
Use Kies to reset your firmware. Choose emergency firmware update up top. It, will ask you for your serial number. It resets in 2 hours.
[T-Mobile Samsung Galaxy Note 3] rambo8987:
I bricked my device over the weekend, I used the stock file in developer thread and used Odin to restore. All is well now hope it helps
[T-Mobile Samsung Galaxy Note 3] ecs87:
It's obvious how to recover from a SOFT BRICK, most of the guys in this thread with an issue are concerned with a HARD BRICK. Kies does nothing to solve this. Kies doesn't recognize a phone on this qhusb interface. AFAIK the only way to recover from a hard brick is JTAG or some clever manipulation of mmcblk0 on a working device onto an sdcard...
[T-Mobile Samsung Galaxy Note 3] keynith:
I ran nvbackup in terminal emulator and it bricked it. I can get into recovery and odin but flashing roms doesn't fix the boot loop
[T-Mobile Samsung Galaxy Note 3] devoureddreams:
Boot to factory recovery after flashing stock with odin and wipe data/factory reset it'll boot then.
[T-Mobile Samsung Galaxy Note 3] keynith:
Samsung hasnt provided the stock boot imgs for the developer edition, so i cant.
[T-Mobile Samsung Galaxy Note 3] youngchris29:
http://xdaforums.com/showthread.php?t=2507403 that should fix it.
[T-Mobile Samsung Galaxy Note 3] keynith:
I tried that too and it didn't work :(
[T-Mobile Samsung Galaxy Note 3] ecs87:
Hey, would anyone be willing to upload me something off of their phone? It's off of mmcblk0 so no personal information will be read (such as IMEI, phone number, etc.). You'll need to be rooted and I think you'll also have to have busybox installed. Run this in terminal emulator after escalating yourself to root (su)

dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=1024 count=71680

The unbrick.img now on your SD card is what I need. I plan on writing this to an SD card in Linux and then putting it in my hard bricked N900T to see if it'll at least get into download mode.
[T-Mobile Samsung Galaxy Note 3] msmercy42:
Anyone? This could help quite a few, and lead to a hard unbrick method for all note 3 variants, not just the SM-900A.
[T-Mobile Samsung Galaxy Note 3] ecs87:
Sure would be nice to try this before sending it out for JTAG -.- Unfortunately it doesn't look like anyone with a N900T is going to step up to the plate...
[T-Mobile Samsung Galaxy Note 3] Melodic13:
Tried but got an error...

I tried but got "/dev/block/mmcblk0: cannot open for read: Permission denied sh-4.2$"

I am not familiar with terminal emulator, but I wanted to help, sorry it didn't work :(
[T-Mobile Samsung Galaxy Note 3] bigbiff:
You need to su to root.
[T-Mobile Samsung Galaxy Note 3] ecs87:
Thanks anyway Melodic13! Like bigbiff mentioned, you do need to be rooted, and you may need busybox installed after you root (not too sure about that one). If you don't want to root, I don't blame you. Knox is a nightmare for everyone. I might be sending my N900T out to mobiletechvideos (I think thats the name of the company) for JTAG today or tomorrow. Note to self...don't mess with partition 3 *facepalm*
[T-Mobile Samsung Galaxy Note 3] Melodic13:
The thing is my phone IS rooted, also I have busy box, lol.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Here you go...

removed, see page 17

Good luck.
[T-Mobile Samsung Galaxy Note 3] ecs87:
Odd. I Mightve messed up the command... I see someone was able to get it though. I'll throw this on a few various sized SD cards at work tomorrow to the bricked N900T and see if I can get it into download mode. Hopefully it'll be dead at work seeing as how I woke up at 7 am today and it was 0 degrees F. Shouldn't be too different tomorrow, eek.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
It's kind of hard to specify how to help you or as we don't know the directories you are going to have everything in. But, before we begin, ensure you format the sd card as exfat. This is the formatting it needs to be in before we write the image.

In a terminal, you will write pretend it is on your desktop):

dd if=/user/home/desktop/kkunbrick.IMG of=/dev/sdb

This will then write the image to the card. The sd card may not be sdb though. In order to confirm, before writing, browse to /Dev and look at the properties of sdb to ensure it is in fact there (it might be sda, sdb, sdc, etc...)

In windows I haven't a clue. I'm sure there is an image writing program out there you can grab...
[T-Mobile Samsung Galaxy Note 3] hoangps:
It's my phone N900T :(

I can use to this method for my phone?
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
[MENTION=2614663]shabbypenguin[/MENTION], there were some reports of this progrsm not working, so in case you have been wondering about it, I have not had any trouble with it on either my N-900V or N-900T.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
If on 4.3, definitely. If on 4.4, well, the verdict is still out there. Both images are here for you though.
[T-Mobile Samsung Galaxy Note 3] ecs87:
You're the man. I think I was able to put together a package in Heimdall and wrote a batch file that'll accomplish my goal (completely resetting the EFS without needing root; root being the biggest pain in the ass since every GSM devices needs root to service the EFS). Unfortunately I wasn't bright enough to take a Note 3 from the shop on Monday that I could've used at the other place I work at (today) to test it out. D'oh.

I'm pretty darn excited. Hopefully this won't draw too much attention from the authorities considering it's not illegal...but can lead to illegal things lol.

EDIT: Nevermind...heimdall can't even flash anything to the N900T. It fails at reading the PIT, so it doesn't try. I also tried loading the PIT in Odin 3.09 and it fails too. Secure check fail: PIT. Did they completely lock down download mode? Wtf...?
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Tell me about it. This truly has soured me on Samsung devices. And I was looking more and more at the lg g flex, I may just sell this guy and buy one of those. Heimdall broken after kk update, Knox BS, Odin fails all the time. Recovery from SD card may be "patched" to not work... Their goal may just be to cater to those who follow blindly from now on... Kind of like that one phone sheeplike people keep flocking to, that i something or other.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
If that's the curved one, I looked at to see if it would replace my N-900V. I often set my Note on a desktop while I tap so I tried that with the Flex -- it doesn't work. So I replaced the N-900V with an N-900T.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
It is the curved one. I just think it is a cool phone. Mind you, this thing has more ram, better tweaks, and a real glass screen, and to notch features like s pen; but the flex looks cool as hell...
[T-Mobile Samsung Galaxy Note 3] ecs87:
It's just stupid. This really is getting as bad as the iPhone. I just want a device where development isn't stopped in its tracks because..."we said so". KNOX wasn't that bad. The secured bootloader wasn't even that bad. Add in locked bootloaders, new EFS versions, JTAG and UART blocks, and now an unreadable PIT? Yeah, NOW I'm pissed! :banghead:
[T-Mobile Samsung Galaxy Note 3] noobtoob:
That is what I an talking about. In definitely getting the OnePlus one. Again, this guy may be on eBay really soon.
[T-Mobile Samsung Galaxy Note 3] ecs87:
It's going to be sad to see a lot of good contributors/developers leave. Especially since I JUST got decent at recovering and hacking Galaxy devices. Sigh.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
And I really like finding out how to dig deep and fix things on here. But just straight up locking everything down is the reason I really hated the iPhone in the first place. It's my device, I will do what I want with it. I used to build personal computers all the time for people (sometimes still do), and love to customize them up, install Linux, windows, or Mac os on it (with the right combo of hardware).

Customization is what android is supposed to be about. Leave it to companies who previously built a solid device to muck it up after becoming power hungry.

After that incipio case shredded my phone, and all these new issues with bootloader are coming out, I am actually getting tired of it.

Don't get me wrong, this device is top notch, and I really like it. Rooted and ROM'd up it runs like a champ. But jumping through hoops to have to do so.... Meh.
[T-Mobile Samsung Galaxy Note 3] Lorettaa:
Strongly agree with you. never ending issues :(
[T-Mobile Samsung Galaxy Note 3] ahmedmelm:
Would anyone confirm the issue here can be fixed by this method?

http://xdaforums.com/galaxy-s3/help/galaxy-s3-wont-power-charge-read-usb-t2747281
[T-Mobile Samsung Galaxy Note 3] ecs87:
For what it's worth, sounds like you've fried the board. To be completely sure you can throw it on a USB cable going to your computer and see if it pops up in device manager. If not...you need a new board.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
Only you can make that confirmation by trying it. The SD card boot trick is from a leaked document that described the procedure, and I don't think that document gave us any information about how or why or when it works. We have had success under certain circumstances and it is easy to rationalize that those circumstances are required, but we can only know by successes and failures.

It is an easy procedure and I don't see that it could cause damage.

Frank
[T-Mobile Samsung Galaxy Note 3] dreeds:
help. ive got my phone dead!! HARD BRICKED MTK6589 N9000 devices.

hello, I have flashed my phone using sp flash tool, and end up with my phones totally bricked.

NO power,NO nothing. even before ive tried to connected it to pc, it was recognised as unknown device.

ive fix that problem and now..

I have trouble of flashing new ROMs for it. I always end up with error dialog says "S_FT_ENABLE_DRAM_FAIL (4032).

I need guide for this one. please helpppppp. what actually I need to overcome that error??? any suggestions??
[T-Mobile Samsung Galaxy Note 3] ecs87:
SP flash tool? Not too familiar with that. Is this concerning a Samsung phone? It sounds like the flash program doesn't know where to write, which means the partitions are messed up.
[T-Mobile Samsung Galaxy Note 3] dreeds:
Thanx for the reply...

So if my partitions were messed up..is there any way that I can access it and repartition? Its a totally bricked phone, and only a "din dong" sound rings when connected to PC. Really wished to revive this phone. I'll do appreciate if u guys can help. Any way out?
[T-Mobile Samsung Galaxy Note 3] ecs87:
What kind of phone is it? And from which carrier?
[T-Mobile Samsung Galaxy Note 3] dreeds:
Its actually from HDC note 3 N9000 mtk6589 chipset android device.

Just bought it recently and bricked it since I have tried to flashed it using a different ROMs. Now I need to know how to access the internal storage so that I can reformat it and make it readable again so that I cn proceed to the flashing process.

Is there any pc software that can detect android phones internal memory and repartition it? Or any other method that u suggest????
[T-Mobile Samsung Galaxy Note 3] ecs87:
If it were an official Samsung phone I'd say there's a chance. Most likely if you've bricked a clone...There's no coming back. Unfortunately they don't have the same amount of support as the official models do. I may be wrong; I see flash files every now and then for MTK chipsets but it's very rare.
[T-Mobile Samsung Galaxy Note 3] dreeds:
Yes. Its a clone Android phone for Samsung note 3.

I do agree with ur answer..its true,the official Android phones tend to give a variety of "supports".

As for my view.those clones were also Android base smartphones,

which I thinked its still very possible to access, reformat and reprogrammed the internal storage.

That's just my view..because now my phone are HARD BRICkED. And as u mentioned maybe my internal storage got mess up*.

and my phone somehow back to its early "dead state" before it knows Android..

(m still thinking how these Android phones internal storage were been program before).

So if u have any info on how to access those internal storage..u might help not just me..but lots of people. :)
[T-Mobile Samsung Galaxy Note 3] ecs87:
From my understanding (and this may be completely wrong) there is a partition file that tells the flashing program where to write certain files to. Without the right partition map, I couldn't see any flashing program attempting to write any files. I've seen Samsung partition files (they end in .pit) but haven't seen any at all for the MTK chipset phones. I'll do some searching though.

FWIW, I think the partitions get setup, system and recovery are loaded and the EFS is loaded through a raw write in ADB shell. I couldn't find any way to load an EFS (I was able to find modemst1 and modemst2 but not FSG) through the download mode interface on samsung devices which leads me to believe this theory.
[T-Mobile Samsung Galaxy Note 3] ReLL1K:
Guys,

My note 3 died yesterday. I left it chargind all night and when I woke up it never came on, removed the battery, used another battery, other charger, nothing.

After searching here I found this thread, but after flashing the img (win disk imager) into several micrSD (4gb, 8gb, 16, 32gb, 32gb class 10) it never woke up :(

Any advice? When I plug it to my computer, I got it on device manager as SAMSUNG Android ADB interface.

The device was unroot, just running stock software 4.3
[T-Mobile Samsung Galaxy Note 3] ecs87:
Your screen just bit the dust.
[T-Mobile Samsung Galaxy Note 3] ReLL1K:
It's not the screen, already changed the logic board with a partner note 3 from T-Mobile too and it worked.
[T-Mobile Samsung Galaxy Note 3] ecs87:
Interesting. If it's recognizing it as an ADB device, it's not hard bricked though. Or at least I wouldn't think it was. You could try writing a whole mmcblk0 to it from a same model.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
You probably tried this but you didn't say, so here it is. And this is just a wild guess, but try swapping the batteries. I'm wondering if something happened during the charge that caused the battery to shutdown.

Frank

---------- Post added at 12:24 PM ---------- Previous post was at 12:20 PM ----------

You probably tried this but you didn't say, so here it is. And this is just a wild guess, but try swapping the batteries. I'm wondering if something happened during the charge that caused the battery to shutdown.

Frank

Oh -- you did say, I just didn't read. Sorry.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Have you just straight tried the adb reboot command to see if it reboots normally from there? I'm wondering...

ecs is right though. If being recognized by your computer as adb interface, it should definitely be recoverable. You need to try out some adb commands and see what we can get to work or not work.

This is however a very strange issue.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
ADB, I think.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
yep. I just finished editing when I got notified. I was leaving work when I first replied. My reply was a mess... Hopefully this is some weird fluke. I am wondering what adb commands can be run when phone is in this state.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] ReLL1K:
Neither ABD or fastboot recognize the device.

Device manager shows it but I cannot install the drivers, already download different drivers and always get the error This device cannot start. (Code 10).
[T-Mobile Samsung Galaxy Note 3] noobtoob:
So no adb reboot -download? I was hoping... What about getting into download via hardware button combo? Have you tried flashing via Odin at all yet? Just trying to weed out more suggestions that will come up.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] ReLL1K:
Odin doesn't recognize it too. Device is dead, can't boot on download mode :(
[T-Mobile Samsung Galaxy Note 3] ecs87:
Are you sure that you have the right drivers for it...? Did you try to replace an unknown device with the ADB drivers when it's supposed to be the QCHSUSB driver?