yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] ecs87:
Ok. I found out something pretty interesting. While working on a N900A I tried to downgrade it back to MJ5. Must've did something wrong, even with a reset through recovery afterwards, I was hanging at the ATT logo. After 15 minutes I decided to give up and go back to MLG. But...wait the instructions mentioned Heimdall...and I was able to use Heimdall...

The MJ5 bootloader is able to be flashed over the 4.4.2 bootloader AND allows Heimdall to access the PIT properly. However, it does soft brick the device, but that doesn't really matter because we have access to download mode at all times. When finished in Heimdall you can simply flash back the MLG bootloader tarball and bring yourself out of the soft brick.

I know this probably doesn't directly help the hard bricked 4.4.2 guys but it may be beneficial for others looking to access the 4.4.2 partitions (minus the bootloader ones since they're rewritten with the MJ5 ones).
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
Ok. I have a Hard Bricked N900T - 4.4.2 (1st release), So, I was trying to fix my Imei Null (or Unknown / 00 actually).

I got there originally, - I had used Region Lock Away, and was looking at the Samsung Tool apk, and my 9 year old may or may not have pushed the Backup or Restore button, (May Not have either), but thats what was going on when I put my Att (Net10) sim in to notice the Not Recognized By Network Error Message.

Had been trying to use the Efs Pro app to Restore an Attempt at adding the Fsg and Backup Partitions off my Working N900T - when I Restored the Complete Backup (Instead of just the 2 files I was missing), and the Phone Went, Dum, Dum, Dum, Duuum. And Boom. Hard Bricked!

So, I am going to try the KkUnbrick Img. - (Already tried the other image- Using Windows, and Win32DiskImager or something similar).

Any advice?

Was about to give up and part the phone out, when I came across this thread 6 hours ago.

Just thought I would mention, to let you know there is another test candidate - Not sure if I saw any 4.4.2 restored yet?

---------- Post added at 01:00 AM ---------- Previous post was at 12:49 AM ----------

Forgot to mention.... Mine Says QCHSUSB_BULK when Drivers are looking to load.

Re-read the last few pages, and it seems this does NOT work with 4.4.2?
[T-Mobile Samsung Galaxy Note 3] noobtoob:
That totally sucks that the sd card undock method isn't working on 4.4.2 right now. Don't give up hope just yet. There is a program I am looking into. If it works, we could use your phone as a tester. Says it works on 4.4.2, so we will see...

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
I don't know if the SD unlock has been properly attempted on 4.4 yet. I've seen a couple cases where it was planned but cancelled and one where I wasn't confident that it was done properly.

Frank

ADDED: The last case might have been that the device was not even seen by the PC.
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
I would be glad to use mine as a tester. Will copy whatever is needed, dump files, etc. Just let me know.

Couldn't try last night, as my Son had baseball. He has a makeup game tonight, so not sure if I will be able to.

If anyone wants to give me the exact steps, or just critique what I have mentioned, step wise, so I can be sure to attempt it properly. That would be welcomed.

Thanks again guys, be well.
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
UPDATE....

Confirmed WORKS WITH 4.4.2 .

In download mode now, flashing fwd via odin.

Will advise shortly!

---------- Post added at 01:46 PM ---------- Previous post was at 01:45 PM ----------

Btw.

I did have to press the button sequence with the sd card in the phone, waited 10 seconds, then pressed.

Felt soo good to feel the vibration.

Will advise.

---------- Post added at 02:05 PM ---------- Previous post was at 01:46 PM ----------

Ok, success from hard brick. I am now back to where my imei is unknown.

Trying to use kies, and it says device version cannot be updated. But, I'm supposed to leave it up, and not touch for a couple of hours, it will update, right?

Thanks for all your help and support guys.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Hell yeah! That is great news. The program I was exploring last night turned out to be written from some Russian guy that only did what we did with less steps using the original .tar files instead of the image being written from a terminal. This means we will need to make one for every bootloader most likely.

As far as the IMEI, read here. It explains how to recover your imei and baseband. Link is for the SM-9005, there is a disclaimer to not follow the specific instructions unless you have that phone. With that being said, it will help you understand baseband and IMEI, but the dialer codes do work for our phone.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
[MENTION=5400078]golfcartguy[/MENTION]:

After you have recovered please write a message to this thread detailing the procedures you used to effect the recovery. Someone with the same problem will be searching for a solution and will appreciate having it all in one message. Everything else addresses 4.3 so yours will be the first which confirms the procedure for 4.4.

Frank
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
I plan on doing that when I get home tonight. (Writing out the steps)

I did have a chance to try to fix the imei via kies. No avail so far. Must be the 0x1 on Knox?

*Wonder if there is a way around that?

The phone has been Un rooted by the firware update via odin. (Btw, i kept the Nb4 version again, and not the NE6 release)and is total stock.

I had thought I would re flash just the modem via Odin. (I extracted just the modem.bin from the md5 file) is that all I have to do?

I am going to look into a program by Dr Ketan (sp) called the Checkfus downloader. Wondering if I can get Kies to set up the stock "shipped" file, and use this to get the full file prior to Kies determining the 0x1.

Anybody have any ideas? If this can be accomplished, those with the null, unknown, or generic imei #s, or just bad flashed phones period, could reinstall proper firmware and be on their way.

Samsung does make a great phone. In my humble opinion, this is the best phone on the market, but, this "no support" for those of us who choose to mess with our property, is ridiculous!

I could have probably left it bricked and got some sort of replacement, but not with the 0x1. (Plus I bought this off someone, so not 1st owner, not sure if warranty would apply anyway)

Anyway, sorry for the long letter, and I will write the steps at home.

Thanks to all who have helped either directly or by contributing!

Be well.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
It's good you kept the nb4 version because we know what already works on it. I quoted you in the other post about imei restore, read there for more info.

As far as the modem, flashing via Odin should work just fine, but only one way to find out. Grab the pit file here as well in case you need it.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] ecs87:
I realized my MLG solution was for the LEAK only! It will NOT work for the newest bootloader since it's on a new binary number. Fml. I'll keep searching...the discovery quest never ends. Fu samsung!
[T-Mobile Samsung Galaxy Note 3] noobtoob:
LOL. My sentiments exactly.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] ecs87:
Interesting...I haven't been keeping up much with unbrick methods but I figured there must've been a way to use the tarballs to unbrick.

And I really hope an EFS backup was made. Even if you're able to write back the original IMEI (without an EFS backup) the IMEI certification will fail and your phone won't connect to any mobile networks. The only way to solve this is to use a Super IMEI (they force the phone to pass the IMEI cert). Can't say much more because it's...well...illegal lol.
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
Interesting. So, what you are saying is that either way I'm F'd without a box or dongle?

Spt, or zx3 or Octo, etc.

Makes no sense as all I want is the original imei back in.

No way to force it to re write the #?

Or, saw a thread on another site, so if I manage to put back the original imei, and everything is correct, it will not connect because the certification will fail? Is there a way to change the status from enforcing to permissive then would that make a difference?

(I'm probably way off base, and don't totally understand everything going on, but want to, and am willing to try)
[T-Mobile Samsung Galaxy Note 3] ecs87:
The box would be the Octopus or SPT box.

And I've tried to write the IMEI using multiple programs. Dunno how it does it, but it does it through UART and it puts the phone in FTM while it does it. I dont even understand the UART part of it (basically because a lot of documentation focuses on READING through UART, not WRITING).

Yes it'll fail. I'm guessing the IMEI certification is in the EFS. To repair the IMEI you must clear the EFS to erase the read only protection on it (nv item 550). So you end up erasing the IMEI cert which you can't avoid. And as far as I know there's no way around this other than a backup or using a super IMEI. I'm guessing the reason why is because the EFS is encrypted (duh) and it'd be SUPER difficult to patch the IMEI certification. But this is what we're going to have to do for the S5. As far as everyone knows there isn't a super IMEI list for the S5 therefore...boned lol
[T-Mobile Samsung Galaxy Note 3] cognus:
excellent Help! kudos to the folks involved in this
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
I wanted to post the steps I used to Un brick my SM-N900T, Running 4.4.2 NB4.

Tried with a 8 gb sd card and 16 gb sd card, to no avail.

So, used 32gb sd card

Formatted to exfat using quick format on my laptop running vista.

Used win 32 disk mapper to write the kk900tunbrick.img found in this forum.

Charged battery to 100% (on another phone as this one would not do anything. Registered qshusb_bulk on my pc.)

Then put sd card in phone, put battery in, and waited 10 seconds, nothing happened for me.

Then held the volume down, home, and power button.

And voilla, the vibration of a boot was felt, and it booted into download mode. (Odin mode)

Then flashed stock firmware back , and she sprung to life.

I still have unknown imei, as I have not had a chance to try repair steps advised.

If anyone else has any ideas I would try them in the order received.

Thanks again to all who have contributed and made this thread a source of hope to those affected.

Will advise as I try to recover fully, but at least I have a brick, no more.

Be well.

John
[T-Mobile Samsung Galaxy Note 3] ecs87:
Thank you a million for responding back. Thankfully this method still works!
[T-Mobile Samsung Galaxy Note 3] noobtoob:
No kidding. I had thought by now it didn't work as no one ever responded. But now that we have verification... Soon I will update to the new boot loader and then add another unbrick image to the mix. If only I could get a spot near the top of the thread to post all these links.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
I know you guys gave me some ideas on resting the imei, but, wondering i if there is a way to force kies to update?

I Google some information on the error message I received, and it says it's a fw mismatch.

Any ideas to force kies to give the original shipped fw?

---------- Post added at 03:33 PM ---------- Previous post was at 03:29 PM ----------

Or am I incorrect in thinking it will restore the imei #?
[T-Mobile Samsung Galaxy Note 3] ecs87:
I REALLY doubt Kies will restore your IMEI considering how it's injected through a UART interface. I've tried to do it through a regular DM usb interface. No dice.
[T-Mobile Samsung Galaxy Note 3] golfcartguy:
Got it. Thanks. I will try the suggestions given, and forget the kies route.

Will advise results.

Be well

John
[T-Mobile Samsung Galaxy Note 3] noobtoob:
I would prefer this towards the top of the thread, but alas....

NF1 Unbrick Image Here!

NE6 Unbrick Image Here!

NB4 Unbrick Image This Link!

MI7 (JellyBean) on this link!

SM-N900T PIT (Just in case).
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
deleted
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Editing now. They were working a minute ago...

---------- Post added at 11:02 PM ---------- Previous post was at 10:58 PM ----------

Alright, all good now. Had an https:// instead of http:// But it was working while logged in, go figure. I just wanted to set up one post with all the images.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
The MI7 link is a duplicated NBx link.

Frank

Got it now - thank you very much for these files.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Jesus. couldn't catch a break on my linkage. all done now. I double checked this time. thanks for the heads up... again.

Fusionized tweaking tapatalker here...
[T-Mobile Samsung Galaxy Note 3] noobtoob:
New NF1 Unbrick image posted in post #439.
[T-Mobile Samsung Galaxy Note 3] Jonnyaces187:
Can anyone point Me in the right direction for a noob guide on how to dump this image to the SD card. I have windows 8 and win32 program. Tried to use virtual box w Ubuntu to no avail. I have the sm-n900a Att note 3 just collecting dust ever since i hard hard brick a couple month ago flashing incorrect rom. Anyone that can help me work on unbrick I will give generous donation. Thanks for the help
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
You can use Linux. I assume you have a replacement phone, just put the image on the device's internal media and use 'dd if=... of=...' to a 32GB exfat removable SDcard. You can do the exfat format with Windows. With the 'dd' command, 'if=' is the downloaded image and 'of=' is the device name for the external sdcard, and that will depend of what the device is. If you are using a Note 3 to do the copy then the device name is in this thread - '/dev/block/mmcblk1p0' I think.

Not I. I'm retired and that would complicate my tax statement.

Frank
[T-Mobile Samsung Galaxy Note 3] Jonnyaces187:
Lot of unfamiliar language there but thanks anyway. I don't have Linux I only have windows. I can't Mount USB with virtual box so have to use windows to dump the image to SD card. I have 32g SD that is formatted fat 32 just don't know how to get image on it do that it will write to the phone when I put it in. The phone is 100% black no 3 button combo or anything.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
Your tagline says that you are using an SM-N900T - that is what I meant by Linux. The kernel is Linux-based and it runs Linux commands. One of the commands it runs is what Android runs in.

Install a terminal emulator ( http://jackpal.github.com/Android-Terminal-Emulator/downloads/Term.apk) and you can use a command-line interface to make the copy using 'dd'.

One step at a time. Install Term and run

dd --help

just to see that it is there.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Besides franks recommendations, which are spot on, are you using the images posted here? These are for the n900t, and you mention you are trying to revive an n900a. Even if you write the image successfully, it won't work unless you are using the proper bootloader image for that specific model.

Also, when you connect your phone to computer does it show qhusb mode under devices? You may have a completely different issue.

Get these questions answered really quick and we can better assist.

Sent from the dirty flashed note 3!
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
[MENTION=4404580]noobtoob[/MENTION]:

I missed his reference to the 900a - is there a 900a sdcard boot image?

I don't run Windows so I was going to walk him through a 'dd' copy, but if you know how to write a disk image in Windows that would be better.

Even without qhusb it won't hurt the device to try an sdcard boot. Right now all it has is a boot image that it does not recognize and can not use. If it doesn't or cannot recognize the sdcard boot image then nothing is done; if it does recognize it as being it's own then it will be used; and if it is the wrong image then it would be similar to a bricked problem, except that in this case the image causing the brick can be removed and replaced. With this in mind I don't even think it would hurt to try a tmo image on an att device - or viceversa. I don't think it would work, but it wouldn't hurt.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
[MENTION=5545307]Frank Westlake[/MENTION]

There is an image of the n900a around their forums. I don't know what bout loader it is, the last one I saw was the 4.3 image.

I don't use windows either except at work, but the win32 disk imager is an easy open source program that does it for you. All you have to do is format your SD card to exfat and then select the image you want to write to it.

Edit: I agree with the not hurting of trying the boot images out, but I know it won't work because we tried it using the att bootloader image when attempting this fix back in the day. We also tried 4.3 image on a 4.4 boot loader brick and it also failed. That is why I wanted to make sure we give him the right advice.

Sent from the dirty flashed note 3!
[T-Mobile Samsung Galaxy Note 3] ecs87:
I think I posted a N900A unbrick image for kit kat a few pages ago.
[T-Mobile Samsung Galaxy Note 3] Jonnyaces187:
Sorry could you post link for 4.4 N900A again. Only could find the one for 4.3 bootloader. I think I have got enough of an understanding to give it a try if someone could post a link. Thanks again for all the help.
[T-Mobile Samsung Galaxy Note 3] LordSacha:
SM-N900 unbrick.img

Can you please make one for SM-N900.

My Exynos Note 3 is fine, but I'm really scared of hard brick while I'm going to Install VN-Rom Kitkat v13.1

I had a soft-brick before.. So I'm really scared of doing fancy stuff with it..

I just shocked bcoz it never happend before ( I had Galaxy Young, Galaxy Tab, and Galaxy Camera all rooted except Camera)

I just wanna backup plan because Note 3 is expensive unlike Young. I can't just ( Hard ) Bricked it.

There is no unbrick IMG for Exynos varient, you'll be the first one to make..

B4 I get my unbrick.img I would never want to flash anything again ever since I soft bricked be Chainfire Auto Root!!!

:confused::confused::confused::rolleyes::eek::eek::rolleyes::confused::confused::confused:
[T-Mobile Samsung Galaxy Note 3] ecs87:
As far as I know the N900 has to be shorted out to achieve the same results? At least that's what I read from the leaked Samsung documentation.
[T-Mobile Samsung Galaxy Note 3] Miguel_Exe:
Hi, I recently bought 1 Galaxy Note 3 on ebay, which I had a problem with the battery, chargin only over 90% because he show as an error: ". Charging paused. battery temperature is too LOW." Anyway, I used the phone a few days charging it up where permitted, after trying several things i enter to the DOWNLOAD MODE to see if in that mode loaded percentage go up, (Note, I never installed any custom rom or anything like that) I just went to download mode with the cable plugged to the electricity and then to turn off the celphone to exit he give me a loop, he showed Samsung Galaxy Note 3 balblab, then a part of the logo of Samsung and he turned off, then after that I went to RECOVERY mODE I make a wipe /factory reset, and then i push reebot now, and after that mon galaxy no longer turns on, and I can not enter to DOWNLOAD mode or RECOVERY mode. The only thing that "works" is that when connected to my computer it "recognizes" (not Kies not Odin).

ht t p : / / prntscr . com / 3xizj5

Again, never tried to install a custom rom, or anything like that. Any idea what happens and if you have any solution? :/ ]

I tried this, but i dont know im doing well,,, the .img 165MB but when i use ImageWriter the sdcard its only loke 75MB, it's that normal? I need to use another img writer? ubuntu?
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
Fixed URL: http://prntscr.com/3xizj5

I haven't checked that image but it is not abnormal for a 'disk image' to appear smaller when viewed as a 'file system'. Try it - it won't hurt.

Please report results.

Frank
[T-Mobile Samsung Galaxy Note 3] Miguel_Exe:
With Windows ImageWriter dont work, i have used two sd, 16gb class 4 and a brand new 32gb 8Like internal storage of my N9005) class 10, and the two unbrick.imgs i found here in this topic from the guy from Russia and this 4.4 from valente http://xdaforums.com/showthread.php?t=2625332

Now i will try with Ubuntu, if this dont work i dont know what can i do ::(:(:(
[T-Mobile Samsung Galaxy Note 3] noobtoob:
What exact model are you trying to resurrect? There is a slight difference in how to do this process depending on if you have a Qualcomm (which it seems you do) or an exynos device. Also the n900 needed to be shorted out like ecs mentioned earlier. I am wondering if the process is the same with the 9005 variant.

I can't say I have been following the other threads on their specific process. This one is quite simple.

1. Format your external sd card to exfat (must be same size as your internal storage).

2. Write the correct image to it.

3. Put it in slot.

4. Boot to download mode via 3 button combo.

5. Flash stock tar in Odin.

From the behavior of your phone though, we may not have a typical hard brick. You mentioned you have never rooted your phone and the battery was displaying something funny. May have a board short somewhere in there that is causing the brick.

Sent from the dirty flashed note 3!
[T-Mobile Samsung Galaxy Note 3] Miguel_Exe:
Thank you for your reply, my SM-N9005 its Quad Core 2,3 GHz (I read that in the french box) , i already do the external sd 32gb cart to external fat, when i write the image with Image Writer i can see in my PC that memory card passed from 29 aprox GB to only 70 or something MEGABYTES, i suppose because is just 1 partition showed in my pc, but i put the sd in my phone, try to turn it on, or boot download mode via 3 button, but it didnt work, still no led ligth, no download mode, no recovery, nothing :( maybe this is the step i dont understand and maybe its the missing piece in my restore:

Also the n900 needed to be shorted out like ecs mentioned earlier.

Can u explain me that pls?

My Galaxy Note 3 its a SM-N9005 Procceseur Quad Core 2,3 GHz, LTE
[T-Mobile Samsung Galaxy Note 3] noobtoob:
There was a leaked Samsung document where you had to short some fuses together and have it powered via USB in order for the boot to take. SD card portion was pretty much the same.

Sent from the dirty flashed note 3!
[T-Mobile Samsung Galaxy Note 3] Miguel_Exe:
So i need to do something to the hardwre? that not my force, so i will need to call SAT ?

My phone showed something about the battery temperature (very week, (faible en francais)), but i can use it normally, then i see a SO STUPID video in youtube who said if you charge it in DOWNLOAD MODE you can reach the 100% porcent of battery, i do that, and when i put off the download mode i had a loop, the phone reset in samsung logo and i then i make a recovery mode swipe/factory, then reebot know and brickbrickbrick :C

i add this images in the processus of sd creator:

]http://prntscr.com/3xvddu

http://prntscr.com/3xvddu http://prntscr.com/3xvdmt
[T-Mobile Samsung Galaxy Note 3] noobtoob:
No hardware short, seems to be n900 only. Just saw this video http://m.youtube.com/watch?v=6VENX15naBA which are the same steps we did in this forum for the 9005. What firmware were you running when this phone bricked? We need an image from a working phone with the same firmware. So far we have discovered the bootloader needs to have the image match it, as in why I have posted 4 separate images in post 493. Is there an image floating around that had the same firmware as your device? If not, see if someone can write one for you.

Sent from the dirty flashed note 3!