yashsingh1/xdaforums huggingface dataset:
[AT&T LG Optimus G] dx58soi7:
So I recently moved and had to hard reset my router (Netgear WNDR3700v4) due to forgetting my admin password. After I reset the router and got all the WiFi settings the way I like them my room mate and I started having trouble with our apps on the WiFi but no problems on 4G. He has an HTC One I have the Optimus G and we were both experiencing the same problems. So here is the story of how I figured out what was bothering the phones:

First we noticed the problem on Facebook and Youtube. Nothing would load as pictures and media but text came up fine. I tried re-installing the apps, no difference. Then I tried re-installing my ROM (SlimKat latest stable) no changes. So I did what any well versed IT would do and began my hunt on Google. I found very little to nothing, mostly people blaming routers or ISP's. That would simply not do. After carefully combing through my logs and comparing the WiFi data traffic on my PC's, game consoles, etc. It seems it was only our phones that had this problem. So I put my network engineer hat on and started tinkering with the routers settings. One forum thread suggested it might be a DNS problem. I figured that TimeWarner is such a garbage ISP the DNS servers were bound to suck. Well I tried OpenDNS and GoogleDNS ip's and there was once again no change. Now I was about to head-desk when I clicked on my routers advanced WAN settings tab, and there was the culprit. In the case of my router it has an option for the IPv6 to be DNS, 4to6, off, etc... In this case the solution was to disable it entirely. Sucks. It looks like KitKat has a problem with some routers IPv6 where a bit of data makes it to the phone and then the data stops. Any DEV's out here know of a fix for the IPv6? Anyone else have this problem? Everything runs great now that I'm back on IPv4.

TL;DR Try turning off IPv6 on your router.
[AT&T LG Optimus G] 2bluesc:
That's interesting. I went out of my way to setup IPv6 on Comcast and am occasionally surprised to find devices I forget about "just work".

http://i.imgur.com/WooMp1P.png
[Verizon Galaxy Note 3 General] hsbadr:
I TAKE NO CREDIT FOR CORE METHOD. I APPLIED IT FOR OUR DEVICE !

To make long story short, I've hard bricked my device while trying to patch/unlock the bootloader after successfully flashing a custom kernel (this tripped knox counter). After reading all guides that addresses the problem for other devices, I'm posting a 100% working solution for the most hated disaster in the Android rooting/flashing world. Moreover, this is very promising info for testing bootloader exploits.

What is Hard Brick?

Hard brick is the state of android device that occurs when your device won’t boot/respond/charge at all. This is mainly caused by flashing corrupted firmware, damaged bootloader, incomplete flashing in Odin/Download mode, or interrupted OTA upgrade. You can't recover from hard brick by traditional methods since your phone is ~dead & you can't enter any Recovery or Download Modes; You'll need to use JTAG (expensive service), USB JIG (cheap, but no gurantee), or this free guide/files to get it repaired.

What do you need?

- Hard Bricked Device: Samsung Galaxy Note 3 (N900V)

- Micro SD Card: 4/8/16/32 GB micro SD card

- Unbrick Image: working dump with the same bootloader/version

- Image Writer: native commands on Linux/MacOSx or Win32 Disk Imager on Windows

How to recover?

1- Download Unbrick Image for your bootloader (MJE, NC2 or NC4) from here

2- If you're using Windows, download Win32 Disk Imager

3- Backup all files in the micro SD card you 'll use

4- Write the Unbrick Image to your micro SD card using Win32 Disk Imager or Linux/MacOSX commands

5- Remove battery, Insert micro SD card & then the battery

6- Hold Power + Home + Volume Down to enter Download Mode by bootloader on SD card

7- Flash Stock firmware via Odin & Enjoy

YOU MAY NEED TO TEST MICRO SD CARDS WITH DIFFERENT TYPES/SIZES & FORMAT AS EXFAT BEFORE WRITING AN UNBRICK IMAGE ACCORDING TO YOUR BOOTLOADER!

For Developer Edition, you need to create your own Unbrick Image since I can't share it for the device-specific bootloader. Just run this Unbrick Image Creator in recovery & it'll create "/sdcard/Unbrick_Files" in your internal SD card.

For more details, read the guides provided bellow in the credits section.

Downloads:

All files you may need are available in this folder.

Credits:

- designgears - for this guide

- Shabbypenguin - for this guide

- theramsey3 - for this guide

- dstruct2k - for this guide

- -Mr. X- - for this guide

Thanks to:

- @soundrizm - for creating the MJE image from his device

- @jrbxx7 - for creating the NC2 image from his device

- @K03WL3R - for creating the NC4 image from his device

XDA:DevDB Information

How to recover from a HARD BRICK, Tool/Utility for the Verizon Samsung Galaxy Note 3

Contributors

hsbadr

Version Information

Status: Stable

Created 2014-08-01

Last Updated 2015-02-15
[Verizon Galaxy Note 3 General] jrbxx7:
Nice work! Thanks

Tapped from an annihilated N10.1
[Verizon Galaxy Note 3 General] ncdub:
This is amazing progress for our devices [MENTION=5868929]hsbadr[/MENTION]. I, for one, can't thank you enough for all you're doing to keep our beautiful albeit locked down Note 3's on the forefront! Donation coming asap!
[Verizon Galaxy Note 3 General] ihavenewnike:
Wait, how can this help with unlocking bootloader? I have no developing background so this would be nice to know
[Verizon Galaxy Note 3 General] kvnhmmd:
This won't reset knox to 0 though, correct? So there's no way to reset to 0 yet?
[Verizon Galaxy Note 3 General] Night_Watcher:
I see there is a nc2 and nc4 unbrick image... If i am on the unified kk Jasmine rom firmware which image do i use... I thought i read on the Jasmine thread that it contained components of both...

Samsung Note 3 - VZW

Jasmine 2.0 v4

XDA Pro
[Verizon Galaxy Note 3 General] hsbadr:
Testing bootloader exploits could easily HARD BRICK the device; now, we've a tested fully working fix for this disaster. So, devs can feel better with their tests.

This just enables booting the device from SD card so that you can enter Download Mode & revive it from HARD BRICK state. The knox counter won't change unless you've already tripped it while messing with your device at/before HARD BRICK.

It only depends on the bootloader version. The unified KK firmware doesn't include any bootloader; so, you'll need to use the Unbrick Image based on your bootloader (NC4 for OTA update or full NC4 tar via Odin & NC2 otherwise). You may try the NC2 image 1st which won't boot if you're on a newer NC4 bootlooder; if so, use the NC4 image.
[Verizon Galaxy Note 3 General] ihavenewnike:
So now we can just randomly try bootloaders, like maybe the DE bootloader modified for a device?
[Verizon Galaxy Note 3 General] hsbadr:
NO, don't! This is only for devs or users who know exactly what they're doing. If you flashed another device's bootloader, you may kill your device forever. However, you can use it to recover when you ACCIDENTALLY made your device hard bricked.
[Verizon Galaxy Note 3 General] ihavenewnike:
Ok. Thanks. Curious, how do you learn about these things. I would love to try some stuff. Hey I got the device for 50 off contract.
[Verizon Galaxy Note 3 General] ol`DXer:
Thank you, Thank you, Thank you! Makes me feel better about trying different roms &mods.

had a Droid HD unlocked bootloader, bricked it many times.
[Verizon Galaxy Note 3 General] LillieBennett:
Could the unbrick files be made flashable. The DE 4.4 bootloader is now on new devices and many DE guys (me too) are interested in upgrading from 4.3? I bow low to [MENTION=5868929]hsbadr[/MENTION] really great work!
[Verizon Galaxy Note 3 General] hsbadr:
You're welcome! Glad I could help.

The purpose of Unbrick Image(s) is to revive a ~dead (hard bricked) device by booting from external SD card to enter Dwonload Mode & flash firmware to recover. You can pull all images from your device & on DevED, all of them can be flashable.
[Verizon Galaxy Note 3 General] NetworkPIMP:
Is the process similiar for a phone that was on MJE?

Scenario:

Phone was stock MJE.

Rooted w/ TowelRoot, installed SS 3.7.1

Rebooted to DL mode, Odin'd "unified firmware" from Jasmine thread (*I think this is where things went sideways b/c no NC2/4 rom was installed to stock slot, just the leftover MJE+TR+SS install).

Phone shutdown at the end of that Odin, and now will not power up / vibrate / enter DL mode / nothing ...

I put the NC2 debrick image on a 32GB Class4 MicroSD - no joy.

I was wondering if it's because the MJE bootloader is still there? Wouldn't I then need an MJE unbrick microSD img?

I figured as much so I made one by Odin'ing another phone back to Stock MJE, and doing a "dd if=/dev/block/mmcblk0 of=/sdcard/unbrickMJE.img count=524288" and used that .img to make the MicroSD card (with Win32DiskImager)...

Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...

(Yes, the card is fine, the battery is at 100%...)

I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:

Thoughts?
[Verizon Galaxy Note 3 General] Dc4479:
Does your phone vibrate when you attempt to turn it on? With the battery or without the battery but plugged into the charger? In my experience with hard bricks, the phone should at least vibe when you go to power it up. Also, not sure if it will make a difference but, try a class 10 card with the same amount of memory as the phone.

Other than that everything you did sounds correct.
[Verizon Galaxy Note 3 General] hsbadr:
1st: you should have flashed full firmware to upgrade from JB; the unified firmware is for KK only !!!

2nd: If you can enter Download Mode, flash the firmware linked above to recover.

3rd: You should use Unbrick Image for the same bootloader & device (N900V MJE in your case)

Update: you may also try a USB JIG to enter Download Mode & flash the required firmware; you can create one or order it from Amazon.com (it's very cheap).
[Verizon Galaxy Note 3 General] ihavenewnike:
Can someone do a video tutorial on this.
[Verizon Galaxy Note 3 General] ryanbg:
An unbrick image may only be viable on a 32GB+ MicroSD. It must be at least the size of the eMMC chip on-board.
[Verizon Galaxy Note 3 General] rneteoriteflo:
Kudos to all the folks that are involved in this, a life saver for those in need for sure!:good:
[Verizon Galaxy Note 3 General] bossnyce:
Any luck with mj7 debrick.img
[Verizon Galaxy Note 3 General] ween101:
What a sigh of relief when I saw this posting I though for sure my Note 3 and my hard earned $60 bucks where about to make and unscheduled trip to Texas. Though I'm not out of the woods yet

I had the original 4.3 installed, rooted (towelroot), and Safestrap (JB) installed

I booted into Safestrap and installed hltevzw_root_odex_nc2.zip

I then fired up Odin v3.09 and loaded n900v_kk_firmware.tar.md5.zip

Once complete the phone shut down and would not power back on (I tried just battery, battery & power cord, no battery power cord)

There are no signs of life.

I have tried 2 different 32gb MicroSD cards using the unbrick images N900VVRUCNC2_UNBRICK and N900VVRUBMJE_UNBRICK

Still will not power on or vibrate

I have even attempted to use a jig but no luck powering on.

Any advice would be greatly appreciated
[Verizon Galaxy Note 3 General] bossnyce:
I have the same problem where you updating from mj7 like I did thats the only debrick/unbrick.img I cant find
[Verizon Galaxy Note 3 General] ween101:
It was I was installed the stock 4.3 image and was trying to update to 4.42 when it all came crashing down
[Verizon Galaxy Note 3 General] hsbadr:
WRONG!!! I recovered from Hard Brick using a 4GB MicroSD. POINT.

It depends on the device & the size of debrick image created.
[Verizon Galaxy Note 3 General] ween101:
May I ask what I am doing wrong then? I have had no success using this method with various microSD cards

Thanks in advance I'm getting desperate
[Verizon Galaxy Note 3 General] hsbadr:
The recovery from hard brick using this method is NOT 100% guaranteed & really needs patience with many trials. I failed to recover several times using 64GB Extreme & 32GB Ultra SanDisk cards. Then, I tried with a very old 4GB card that I wasn't even using & finally recovered!

How did you brick your device? Some situations always fail & may need a JTAG service. I feel that most/all hard bricks could be recovered with this method though.

I've received many thanks with successful recovery & someone reported a failure. I can fix your device with ~90% probability, but I don't want to open the door & receive many devices especially if you can really do it yourself.
[Verizon Galaxy Note 3 General] hsbadr:
MicroSD Card Type/Size/Format

you may need to try micro sd cards with different types/sizes & format as exfat before writing an unbrick image according to your bootloader!
[Verizon Galaxy Note 3 General] ween101:
Exfat I didn't think of that have been formatting in fat32 will give that a try

If I format the microSD exfat and then write the image does win32 Disk Imager reformat the card to fat32 ?

Thanks for the insight :)
[Verizon Galaxy Note 3 General] hsbadr:
Actually, old SD cards may work better (device will recognize them easily during boot & if device's bootloader doesn't boot, it'll use the extSD). I haven't tested the ExFAT format, but it has been reported by a user who has successfully recovered from a hard brick using this guide.
[Verizon Galaxy Note 3 General] hsbadr:
[MENTION=249779]moe[/MENTION], would you share your experience with this guide & ExFAT format? Thanks!
[Verizon Galaxy Note 3 General] ryanbg:
If you plug your device into a computer, and it does not emulate as 'QHSUSB_BULK or DOWNLOAD' or something similar, this method will not work. You will need a device replacement. AKA if the USB is dead, it won't work. Also, make sure you are writing the image correctly. Use win32diskimager on Windows, or dd on Linux/OS X.

JTAG is disabled on SM-N900V, and there are no JTAG pads or headers on the board. They are programmed via USB using a hex programmer. Most production 8974 boards are JTAG disabled via QFPROM. Your only option is to program via direct ISP to eMMC, or device replacement.
[Verizon Galaxy Note 3 General] ween101:
I appreciate the knowledge yep I get sign of life when I plug the phone via USB from the PC

Sounds like the phone might be taking a vacation then :eek:
[Verizon Galaxy Note 3 General] OrangeAndBlueDroid:
I am trying to flash a Rom on note 3. I have flashed many many times newbie but it has been about a year. Every time I flash and I reboot I get the black screen. Yes I have busy box installed and went through installation, as well as SS. Any recommendations?
[Verizon Galaxy Note 3 General] ryanbg:
What version were you running? NC4?
[Verizon Galaxy Note 3 General] ween101:
These were the steps I took

I had the original 4.3 installed, rooted (towelroot), and Safestrap (JB) installed

I booted into Safestrap and installed hltevzw_root_odex_nc2.zip

I then fired up Odin v3.09 and loaded n900v_kk_firmware.tar.md5.zip

Once complete the phone shut down and would not power back on (I tried just battery, battery & power cord, no battery power cord)

There are no signs of life.

the hltevzw_root_odex_nc2.zip was installed ok so I'm assuming NC2?

Thanks
[Verizon Galaxy Note 3 General] anticloud:
what I have done...

What I have done - is break out odin and the pit file. of course we are talking the condition where it gets stuck at the samsung logo. flashing the pit seems to upright the phone and in 99% of the cases, well, it brings me back to the last OS etc. depends on how bad the flash went, right?

anyway -
[Verizon Galaxy Note 3 General] hsbadr:
Hard Brick = Dead-like situation = No logos/charging...
[Verizon Galaxy Note 3 General] Penz89:
Can this method works for other samsung devices such as galaxy s2? thanks [MENTION=5868929]hsbadr[/MENTION]
[Verizon Galaxy Note 3 General] hsbadr:
The method may work, but you need to create unbrick image from S2 device with the same bootloader.
[Verizon Galaxy Note 3 General] keynith:
So i bricked my dev note 3 last year by doing the nvbackup in terminal mode. After a couple months i decided to try different things to see what happened. Somehow i got the bootloader changed to the retail one. So i know no more dev edition, but do you think i could fix it even if it ended up being a retail version? Last thing i odined on it was a stock rom to see if that would just flash a stock bootloader and rom so i could use it, but that did nothing

Sent From My Galaxy Note 3
[Verizon Galaxy Note 3 General] mihajlo27:
har brick note 3

So i have been trying to unbrick my phone for 3 days now. with this step i get the unbrick image loaded on sd card and put in my phone but when i go to downloader mode it doe snot look any different and for odin i use odin 3 v3.9 and i use ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5 and am not sure is this correct o rnot. i have also tried to do root de la vega and samsung kies and am desperate. please help. :(
[Verizon Galaxy Note 3 General] jrbxx7:
Edit. Misread sry

NoTe III'd
[Verizon Galaxy Note 3 General] thornev:
You do not want the MI9 rom. It's way old. What rom did you have before?
[Verizon Galaxy Note 3 General] radionerd:
keynith

If your DE is still bricked from the toxic nvbackup command, check out my thread. I did the same thing, and found a fix.

http://xdaforums.com/showthread.php?t=2657519
[Verizon Galaxy Note 3 General] Cobaltikus:
1. Does it matter what name I give the img file?

2. Does it matter where I put the image on the SD card?

3. The unbrick image creator executes dd with bs4096 and count=50000. What is the logic behind these two values? And do they even matter?
[Verizon Galaxy Note 3 General] donc113:
Yes they matter. dd is a disk dump program. It reads the image a block at a time and for a certain number of blocks. The input and output sizes must be the same (bs) and the number of blocks read or written must be the same (count).

Since you're using the program to create an image....you want the parameters to match how you write the image back if ever needed.
[Verizon Galaxy Note 3 General] Cobaltikus:
Thank you for the response. However I still have the same questions. By "values" I meant the 4096 and the 50000. Why 4096? How do we know to specify a block size of 4096? What if specified a block size of 2048? Would that have the same result as long as I specified a count of 100000? Does the resulting image need to be exactly 200 MB?
[Verizon Galaxy Note 3 General] donc113:
Because that's the block size of the device....how much the hardware reads at one time (or writes) no matter what. It is the number of bytes....in this case 4096 or 4KBytes.

As an example....lets just take a text file that simply has the single word "Sunshine" in it. Adding a Line Feed to end the file makes it 9 Bytes long. But when you go to save (or read) that file the hardware will read 4096 Bytes (or write that much) because that makes the firmware for that device much easier to write and relates only to how the hardware (not software) reads and writes most efficiently.

The hardware block size does not have to match the filesystem blocksize....because filesystem blocks deal with how the software (not hardware) reads and writes most efficiently.

In a modern Operating System, hardware and software are totally independent of each other and a hardware access layer (part of the kernel) does all the translations. To use new hardware, you only need to change the kernel...not thre whole OS.

In Linux (or UNIX) devices (which Android is based on) you have "device" access by either a character oriented device file or block oriented device file. Those device files are in /dev and below and are not real files but merely pointers into the kernel.
[Verizon Galaxy Note 3 General] legion423:
Will this work with HTC one M7 :( . Thanks
[Verizon Galaxy Note 3 General] brex91:
any chance this would work with a galaxy tab pro 10.1? I somehow bricked mine several months ago(first time ever, since my Fascinate)

It doesn't boot into odin or show any signs of booting.

Could I somehow use that unbrick creator?
[Verizon Galaxy Note 3 General] Sterben Pistole:
HTC Devices do not work with Odin. Odin is a program for Samsung devices. I think HTC users need to use HBOOT and have the .zip in the extSD. Wait, just go to the HTC One M7 forum to ask this question.
[Verizon Galaxy Note 3 General] shawnjag:
NK1 Unbrick Image

I have a Note 3 that bricked during an OTA update to NK1. It's definitely a hard brick because it's detected as QHSUSB_BULK in Windows. Would anyone be able to use the Unbrick Creator script provided by the OP to create an Unbrick image for NK1 users?

I'd greatly appreciate it. Thanks.
[Verizon Galaxy Note 3 General] brex91:
Hey, I know this isnt quite the same, but I managed to find a dump image online for my model tablet (tab pro 10.1)

It came in a .7z that extracted to a boot.img and system.7z, is there a way to make a unbrick image out of these?

The diskimager proram won't use a folder or 7z archive for me.
[Verizon Galaxy Note 3 General] zimmar:
Create Image for other Samsung Phones

Hi hsbadr

I need to create a custom image for another model of phone: Samsung Galaxy Note 4 (N910GDTU1BOD3).

It is totally unresponsive and definitely HARD bricked.

Not sure if I need it, but I downloaded the full firmware from sammobile.

Can you please help explain how to create the image to unbrick it? I've downloaded all the files you posted previously and have also downloaded ODIN 3.10.

Really appreciated.

Zimmar
[Verizon Galaxy Note 3 General] Nrk411:
hard brick on verizon note 3?

Hi there, my first post. Thank you for all of the great resources and contributions on here. I really appreciate all of this info and enjoy learning more about Android.

I had my 1.5 year old Verizon Note 3 (SM-N900V) that was acting weird so I warrantied and got a new one 2 months ago. It has been working great ever since. I have not rooted the phone or anything, running all stock software, Android 5.1.1. Last Tuesday I pulled my phone out of my pocket after lunchtime (had just spoken to my wife, sent a couple texts, you know the normal stuff maybe 30 minutes before) and it was dead.... I thought it was weird, thought maybe it just turned off o something, battery was about half full the last time I saw it. But nothing, nada, no response from leaving plugged in for a couple hours to charge. No vibrate on power+vol down+home button, not so response no vibrate from power button alone.

I have tried the mje and nc2 unbrick image with Win32Disk imager and am still getting zero response from the phone.

I'm def. a newb in terms of my android rooting and flashing ROM's experience, I have only experimented with 2 different phones.

I have a feeling the phone is toast but I'm so confused by how it died... Wondering if maybe they sent me a refurb device when I warrantied it and it was just volatile? I'm also temped to order a new motherboard for it off of ebay but again I don't know enough to determine if it would work or it this is just a crapshoot. I am due for an upgrade but was hoping that I wouldn't have to upgrade for a few more months until the Note 5 drops in price a little, I was even going to just get the Note 4 because it has a microSD slot but it's the same price as the Note 5! I am using my old school Galaxy Nexus for the time being and it's killing me, the thing is a dinosaur!

Any help is appreciated.
[Verizon Galaxy Note 3 General] Odin2015:
Can someone do this dd if=/dev/block/mmcblk0 of=/sdcard/Unbrick_Files/200MB.img bs=4096 count=50000; for gt-i8190 and send me the file please?
[Verizon Galaxy Note 3 General] asadnow2k:
any solution for N915g note edge? if yes let me know guys i have one unit on qusb 9008 mode it seems hard bricked. dont wanna jtag with wires. if any sd card method available please link me to that..