Develop Bugs

please help with root issue (searched for 2 days & tried everything)

yes i have searched endlessly.
no i am not in anyway new to rooting (not claiming to be on the level of probably most here)
i have tried everything to get my replacement DInc to root. one confusing issue is that the error i get seems to bounce around all over the place. from back CID missing, to failed to gain root, to failed to flash recovery and is your firmware too new. i have tried:
* multiple versions of unrevoked.
* with and without sd card
* on charge only and on disk drive
* with and without firewalls enabled.
* did factory resets
* flashed a new RUU
i am almost sure i am forgetting something here but cant think offhand as i am about to go crazy with this thing. please if you have any suggestions then i will try anything. i know it may sound childish but if i cant root this thing after being used to it then i almost assume go back to my old razor.
thanks in advance

Sure you have the correct drivers (for windows machines)? Sometimes people have had to use different computers, couldn't hurt if you have access to another machine.
Sent from my ADR6300 using XDA App

k_nivesout said:
Sure you have the correct drivers (for windows machines)? Sometimes people have had to use different computers, couldn't hurt if you have access to another machine.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
well yes i am sure that i have the correct drivers cause i broke out the other device that i havent sent back yet and it rooted using the same items that i have been attempting with this one for 2 days now. i can attempt the root on a different machine shortly when my parents are up, will post results.
any one else have any thoughts care to share?

shorty1993 said:
well yes i am sure that i have the correct drivers cause i broke out the other device that i havent sent back yet and it rooted using the same items that i have been attempting with this one for 2 days now. i can attempt the root on a different machine shortly when my parents are up, will post results.
any one else have any thoughts care to share?
Click to expand...
Click to collapse
Try setting up the drivers from scratch for you new device. The same drivers worked when I rooted my buddies phone, but I had to re-download them from scratch to get it to work.

trickster2369 said:
Try setting up the drivers from scratch for you new device. The same drivers worked when I rooted my buddies phone, but I had to re-download them from scratch to get it to work.
Click to expand...
Click to collapse
already tried this. actually i just installed windows 7 ultimate on my laptop just a few days ago so it was completely clean. did everything from square one with no changes in issues. i called verizon today and told them that the replacement device i received was doing alot a odd things (no mention of real issue obviously) so without hesitation he said he would send me another out. so hopefully there is just something about this particular device that is abnormal. i would still like to keep hearing opinions and trying solutions tho. who knows that something in the refurbish methods arent causing this currently. thanks to all.
anymore guesses.

I had problems using Unrevoked on windows. I put it on my Mac, and it worked the first time, no drivers or anything needed. Probably not the most helpful advice, but if you have access to a Mac, might as well give it a try.

Uninstall dropbox and PDA net if present. SD is fat32? Using stock USB for device? Launching unrevoked as admin? Right click on the exploit before running, see if properties show it from unknown computer, and unblock it if needed. Same story with the drivers, check and unblock from properties, then reinstall as admin.
Tried a different USB port on the PC?
Sent from my ADR6300 using XDA Premium App

Did you get this resolved?
Sent from my ADR6300 using XDA Premium App

wanted to post back the outcome which hopefully at some point will help someone. i made sure every possible combination of drivers, programs, menu options enabled/disabled appropriately. nothing fixed this. verizon sent me a new device out (obviously they werent told my reasoning), powered it up, plugged it into the same computer and 2 minutes later was rooted with not the first issue. thus i have concluded that there had to be something in the programming that would not accept root. unsure how considering i even ran the RUU multiple times. thankfully they sent me a replacement for my replacement cause dealing with a stock phone after being rooted just would not work out.
thanks all

Yea if that phone was having that much trouble getting root then it probably could have bricked in the long run. Good thing you did get a replacement and were able to root in the end.

Computer does not recognize my Phone HELLLLLLLPPPPPP!!!!

Ok sorry to be posting the same thread again but i cant seem to get any help ive tried asking in other threads but got no help.........so no computer will recognize my phone i need to odin back to stock to take my phone into the sprint store cause i cant hear anyone except through the headset or bluetooth i have
i have tried reinstalling drivers 3 different usb cords and 2 computers one was a PC and the other was a Laptop both used to work now nothing if there isnt a way to get it to recgonize it is there anyway else to get back to stock id really appriciate ur help
btw im on the newest sfr 1.2

thall302559 said:
Ok sorry to be posting the same thread again but i cant seem to get any help ive tried asking in other threads but got no help.........so no computer will recognize my phone i need to odin back to stock to take my phone into the sprint store cause i cant hear anyone except through the headset or bluetooth i have
i have tried reinstalling drivers 3 different usb cords and 2 computers one was a PC and the other was a Laptop both used to work now nothing if there isnt a way to get it to recgonize it is there anyway else to get back to stock id really appriciate ur help
btw im on the newest sfr 1.2
Click to expand...
Click to collapse
I read something about not using a computer to root; but I could not find anything on getting back to stock without a computer (the question was posed on a few different sites).
My only thought would be to have someone on stock rom, to root and do a backup with CWM; then copy that backup folder off their phone to someplace you could download it using your phone (like google documents).
then you could boot to recovery and flash EXT42RFS.zip from :
http://forum.xda-developers.com/showthread.php?t=1109362
then use cwm to restore from that backup and it would put stock ec05 on your phone; seemingly back to stock except for the recovery.

thats what i was thinking also couldnt find a downloadable back up to put on to my phone if any one is willing to help me with a flashable backup for clockwork mod im using version 3.0.0.6 i think

Similar issue.
I am looking into a solution. Let me get right back at you.

SpyFi said:
I am looking into a solution. Let me get right back at you.
Click to expand...
Click to collapse
that would be appriciated i kno alot of people having this issue would be nice to get a fix the more the better

As far as I know there is no way to unroot without a computer. However you can make it look like stock for the return. When you installed CWM 3.0.0.6 on your phone and it converted to EXT4 it made a nand backup called beforeEXT4conversion or something like that. Restore that nand and do a factory data reset from inside settings>privacy on your phone.

Click on my video link in my signature. I have a way to unroot without a pc video.
Sent from my SPH-D700 using XDA App

Who knows, that may also fix your phone to connect again. Does it make the connection noise on the computer? If so, go into Control Panel, System, Device Manager and look for something connected to your USB or Other. It will probably say Samsung Android. Choose Update Drivers on that and it will take about 10 minutes to get the drivers and install and you should be able to work from the computer again.

qbking77 said:
Click on my video link in my signature. I have a way to unroot without a pc video.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I need to see that myself....thanks q!

Damn that video on unroot w/o PC is sweet.
Dowloadning those files just incase too.

Ok here's another problem I erased the before EXT4 backup when I formatted my sd cause I thought that could have been an issue....will using another persons back up work???? And if so can someone give me theirs????
Sent from my SPH-D700 using XDA App

and also my computer doesnt make the connection noise
Sent from my SPH-D700 using XDA App

Is anyone able to give me their before EXT4 backup????? Plz lol
Sent from my Nexus S with a keyboard!

[Q] PC will not recognize T-mobile note 2

I know that there are other threads about this issues but so far the responses are useless.
I have tested the Phone in 3 different computers (1 mac/ 2 win) and nothing.
I have used 3 different usb cables and nothing.
I have all the drivers up to date, latest version of kies. (also, I uninstalled Kies and the drives and nothing)
I have plugged another note 2 to the pc using the same usb cable and it is recognized.
help or advise
Thanks.

Factory reset? Or if you're rooted, restore backup or flash a new rom or stock
Sent from my SGH-T889 using xda app-developers app

PhxDroid86 said:
Factory reset? Or if you're rooted, restore backup or flash a new rom or stock
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I have done that and nothing (stock, rooted, factory reset, restore from back up)
I think the issue started after i updated kies.
Thanks anyway.

Pirobo_Colombino said:
I have done that and nothing (stock, rooted, factory reset, restore from back up)
I think the issue started after i updated kies.
Thanks anyway.
Click to expand...
Click to collapse
I had this issue although I am running linux mint 15 ( ubuntu base) and it wouldnt recognize sd or extsd but I switched from stock rom to jedi x9 and all of a sudden it read everything. No problems since
I dont know why JB had to have junk a mtp crap . That one one of the things I really loved about android was the ability to mount as a mass usb storage device.

Pirobo_Colombino said:
I have done that and nothing (stock, rooted, factory reset, restore from back up)
I think the issue started after i updated kies.
Thanks anyway.
Click to expand...
Click to collapse
Another guy just went through this and found out it was the cable... not exactly which one he used to get everything to work though?
Outside of that or the rare manufacturer defect I'd say it has to do with the root process or with qualcomm usb settings
Sent from my SGH-T889 using xda app-developers app

Solved, but not really
After trying everything possible, i finally gave up and the only option i had left was to send it back to Samsung.
Their response was that there was and internal defect with my device..... they shipped a new one.
If you are having the same issue and it is not the cable take advantage of your warranty.

Pirobo_Colombino said:
I know that there are other threads about this issues but so far the responses are useless.
I have tested the Phone in 3 different computers (1 mac/ 2 win) and nothing.
I have used 3 different usb cables and nothing.
I have all the drivers up to date, latest version of kies. (also, I uninstalled Kies and the drives and nothing)
I have plugged another note 2 to the pc using the same usb cable and it is recognized.
help or advise
Thanks.
Click to expand...
Click to collapse
.
I understand your pain bro as I also had the same problem. I took some risk while fixing this, the problem started with me while I was in a humid place so I thought maybe the inside got wet. I opened the screws and blew heat in a moderate level. After that it was okay

What OS you running?
Hastily spouted for your befuddlement

Pirobo_Colombino said:
After trying everything possible, i finally gave up and the only option i had left was to send it back to Samsung.
Their response was that there was and internal defect with my device..... they shipped a new one.
If you are having the same issue and it is not the cable take advantage of your warranty.
Click to expand...
Click to collapse
This has happen to me on my rooted Verizion S3 and the rooted Tmobile Note2. This occurs all the time, it occurred whether it was rooted or not. Try uninstalling and re-installing the drivers.

Stuck in boot loop with no USB option

I just inherited a t-mobile phone that was rooted. I installed the latest version of TWRP and tried to re-root it but now it's in a boot loop and on top of that I can't connect the phone to a computer b/c I get the "USB Device Not Recognized" message. I've re-installed the drivers and I've tried the toothpick trick. Nothing is working. What are my options?

jconway1968 said:
I just inherited a t-mobile phone that was rooted. I installed the latest version of TWRP and tried to re-root it but now it's in a boot loop and on top of that I can't connect the phone to a computer b/c I get the "USB Device Not Recognized" message. I've re-installed the drivers and I've tried the toothpick trick. Nothing is working. What are my options?
Click to expand...
Click to collapse
First wrong section...second I'd say flash a different Rom/kernel pair... or redo your recovery from Odin
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

bmg002 said:
First wrong section...second I'd say flash a different Rom/kernel pair... or redo your recovery from Odin
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
First, I believe this is the correct section - the phone I am working with is a T-Mobile Galaxy S II... Second, I can't Odin because I don't have a working usb connection. I've tried several different ROMS from this fine section and I get the same result... Boot Loop

If you flashed TWRP 2.6.3, that's your problem.
Flash 2.6.1

This is the wrong section because it has nothing to do with ROM development.
With that being said if you can still boot into twrp you still have hope. Try loading a different ROM into an SD card using a converter and slide back in the phone to properly wipe first then re flash.
I don't understand why you can't get a proper USB connection going but above suggestion may solve it.
Sent from my SGH-T989 using xda app-developers app

You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app

jconway1968 said:
First, I believe this is the correct section - the phone I am working with is a T-Mobile Galaxy S II... Second, I can't Odin because I don't have a working usb connection. I've tried several different ROMS from this fine section and I get the same result... Boot Loop
Click to expand...
Click to collapse
Just to confirm a few things: where do you not have the working USB connection? in download mode? If so, I'd try reinstalling the drivers.
Also, I see in your sig that you state your phones are:
Asus Nexus 7
Sprint Galaxy Note 2
Neither of which is a SGH-T989. Are you sure you are flashing the correct ROM/Kernel for your device?
also you said it came rooted but you re-rooted it. What process did you use to re-root it?
One last thing: you say you got it second hand, are you sure it is a T-Mobile galaxy S 2? May want to check under the battery for a "T989" or "i9100". The i9100 is NOT a T-Mobile galaxy S 2. It should be SGH-T989 if they didn't give you incorect info about the phone.
You could also try a different USB cable or hub. I've had USB extension cables give me grief and the front ports on my PC don't like my phone.

bmg002 said:
Just to confirm a few things: where do you not have the working USB connection? in download mode? If so, I'd try reinstalling the drivers.
Also, I see in your sig that you state your phones are:
Asus Nexus 7
Sprint Galaxy Note 2
Neither of which is a SGH-T989. Are you sure you are flashing the correct ROM/Kernel for your device?
also you said it came rooted but you re-rooted it. What process did you use to re-root it?
One last thing: you say you got it second hand, are you sure it is a T-Mobile galaxy S 2? May want to check under the battery for a "T989" or "i9100". The i9100 is NOT a T-Mobile galaxy S 2. It should be SGH-T989 if they didn't give you incorect info about the phone.
You could also try a different USB cable or hub. I've had USB extension cables give me grief and the front ports on my PC don't like my phone.
Click to expand...
Click to collapse
Thanks for your help. Here are the answers to your questions:
I think there is something wrong with the micro USB input on the phone. I have reinstalled the drivers several times. I have tried different cables and different computers. I even tried the toothpick trick. No luck.
I do have a GN2. The SG2 is for my daughter...
It is a genuine SGH-T989 I checked under the battery.

soupysoup said:
You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Where do I find and how do I put a flashable twrp 2.6.1.0 on my micro sd card? I've always used goomanager in the past but obviously that won't work in this case...

jconway1968 said:
Where do I find and how do I put a flashable twrp 2.6.1.0 on my micro sd card? I've always used goomanager in the past but obviously that won't work in this case...
Click to expand...
Click to collapse
Everything I've found requires a computer connection. I need to be able to flash it back from v2.6.3.1 using TWRP to do it. Is that possible?

soupysoup said:
You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One more piece of information that might be helpful... When I try to wipe the cache I get this message "Formatting Data using make_ext4fs function" and it stays stuck there. I've left it for over 30 minutes and it doesn't ever move from that screen. Hope that helps... I really need some help here.

jconway1968 said:
One more piece of information that might be helpful... When I try to wipe the cache I get this message "Formatting Data using make_ext4fs function" and it stays stuck there. I've left it for over 30 minutes and it doesn't ever move from that screen. Hope that helps... I really need some help here.
Click to expand...
Click to collapse
In twrp settings change it to use rm instead of formatting
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

jconway1968 said:
Everything I've found requires a computer connection. I need to be able to flash it back from v2.6.3.1 using TWRP to do it. Is that possible?
Click to expand...
Click to collapse
If u go to the dev section on this phone and look around a bit, u will find the twrp thread, in that thread is a flashabke copy of 2.6.1.0, if u can't find it pm me, I have a copy, all u would need to do is put the zip file on any micro SD card then put it in the phone and flash it with the twrp u have now, it will revert it back to 2.6.1.0 and that should fix ur prob, but like I said of u can't find it pm me and I'll shoot u a copy
Sent from my -T989 using XDA Premium 4 mobile app

soupysoup said:
If u go to the dev section on this phone and look around a bit, u will find the twrp thread, in that thread is a flashabke copy of 2.6.1.0, if u can't find it pm me, I have a copy, all u would need to do is put the zip file on any micro SD card then put it in the phone and flash it with the twrp u have now, it will revert it back to 2.6.1.0 and that should fix ur prob, but like I said of u can't find it pm me and I'll shoot u a copy
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so I Flashed it and now it's stuck on the Blue Teamwin screen???

jconway1968 said:
Ok so I Flashed it and now it's stuck on the Blue Teamwin screen???
Click to expand...
Click to collapse
Let it sit on the TeamWin screen for a minute or so... I find it sometimes takes a little bit.
If it doesn't ever get past there, try hooking it up to a PC and see if you can get ADB to load (presuming you have ADB installed and ADB drivers installed). If you can, try to do an "adb pull /proc/last_kmsg" and a "adb logcat > logcat.txt" and zip those up and toss them on here.
If you CAN'T get into adb, I would try hooking the phone up to Kies and see if it will do anything for you.
Or you could try following this guide as you have the T-Mobile SGH-T989 (not the Telus SGH-T989D):
http://forum.xda-developers.com/showthread.php?t=1513359
BUT make sure to grab the correct stock image file for whatever version your android currently is (ie if you are on Android 2.3.6, then make sure to get the T-mobile KL1 2.3.6 stock image).
Also, what ROM did you flash? was it a 4.3 ROM? If so, did you update your radio before you flashed the ROM? I think 4.1+ needs the updated radio to function properly.
I know you said you can't connect through ODIN, but I'm hoping it is because of some odd driver or odd ODIN version. That thread has the stuff to make it all work I believe.
I'm really hoping you can get ADB to work. If you can pull a logcat of your bootup process, it will be much easier to figure out what went wrong.

bmg002 said:
Let it sit on the TeamWin screen for a minute or so... I find it sometimes takes a little bit.
If it doesn't ever get past there, try hooking it up to a PC and see if you can get ADB to load (presuming you have ADB installed and ADB drivers installed). If you can, try to do an "adb pull /proc/last_kmsg" and a "adb logcat > logcat.txt" and zip those up and toss them on here.
If you CAN'T get into adb, I would try hooking the phone up to Kies and see if it will do anything for you.
Or you could try following this guide as you have the T-Mobile SGH-T989 (not the Telus SGH-T989D):
http://forum.xda-developers.com/showthread.php?t=1513359
BUT make sure to grab the correct stock image file for whatever version your android currently is (ie if you are on Android 2.3.6, then make sure to get the T-mobile KL1 2.3.6 stock image).
Also, what ROM did you flash? was it a 4.3 ROM? If so, did you update your radio before you flashed the ROM? I think 4.1+ needs the updated radio to function properly.
I know you said you can't connect through ODIN, but I'm hoping it is because of some odd driver or odd ODIN version. That thread has the stuff to make it all work I believe.
I'm really hoping you can get ADB to work. If you can pull a logcat of your bootup process, it will be much easier to figure out what went wrong.
Click to expand...
Click to collapse
You guys are great!!! I really appreciate all the help. No matter what I do, ADB, Kies, different cables, different computers, nothing gets past the "USB Device Not Recognized" pop up. I let it sit for 15 minutes, twice. Still no love... I loaded TWRP_2.6.1.0_Hercules and then reboot and that's when it got stuck. Prior to that I had loaded TMobileT989UVMC6RootedDeodexed Rom. I forget where I got it. I'm pretty sure it was a 4.1.2 based rom.

jconway1968 said:
You guys are great!!! I really appreciate all the help. No matter what I do, ADB, Kies, different cables, different computers, nothing gets past the "USB Device Not Recognized" pop up. I let it sit for 15 minutes, twice. Still no love... I loaded TWRP_2.6.1.0_Hercules and then reboot and that's when it got stuck. Prior to that I had loaded TMobileT989UVMC6RootedDeodexed Rom. I forget where I got it. I'm pretty sure it was a 4.1.2 based rom.
Click to expand...
Click to collapse
weird... I am not sure why it is being so fussy with your phone.
Hopefully somebody has a better suggestion than I do, but my next thought is to try ebay-ing the phone in hopes that somebody gives you a few bucks for it. It sounds to me like the internal memory module is dying and the USB port is shot.
Is your water damage sticker pink/red or missing? It should be under the battery.
I hate thinking that the phone is just dead, but without being able to connect it to the PC in either recovery or download mode and not being able to boot into a ROM or recovery, I think the next step is to scrap it and hope somebody can send you a few bucks... or if you have experience soldering, maybe try replacing the USB connector?
I could be wrong mind you... The only time I had issues like that it was due to a badly flashed recovery and I needed to use ODIN to get back up and running. As a thought, do you have a Windows XP 32-bit computer you could try plugging the phone into? And while the phone is plugged in, can you check device manager for all devices? maybe try installing the drivers manually? I suggest windows XP 32bit because that is what I use the majority of the time with my phone. I've also used Windows 7 64-bit and it worked.

bmg002 said:
weird... I am not sure why it is being so fussy with your phone.
Hopefully somebody has a better suggestion than I do, but my next thought is to try ebay-ing the phone in hopes that somebody gives you a few bucks for it. It sounds to me like the internal memory module is dying and the USB port is shot.
Is your water damage sticker pink/red or missing? It should be under the battery.
I hate thinking that the phone is just dead, but without being able to connect it to the PC in either recovery or download mode and not being able to boot into a ROM or recovery, I think the next step is to scrap it and hope somebody can send you a few bucks... or if you have experience soldering, maybe try replacing the USB connector?
I could be wrong mind you... The only time I had issues like that it was due to a badly flashed recovery and I needed to use ODIN to get back up and running. As a thought, do you have a Windows XP 32-bit computer you could try plugging the phone into? And while the phone is plugged in, can you check device manager for all devices? maybe try installing the drivers manually? I suggest windows XP 32bit because that is what I use the majority of the time with my phone. I've also used Windows 7 64-bit and it worked.
Click to expand...
Click to collapse
Thanks again for your time and suggestions... I've always been very impressed with the xda community. I actually got this phone, used, from Swappa. And I am in the process of returning it for a refund. But the seller is being difficult and is trying to stick me with the phone. I was just trying to salvage it on my own, just in case... Thanks again.

jconway1968 said:
Thanks again for your time and suggestions... I've always been very impressed with the xda community. I actually got this phone, used, from Swappa. And I am in the process of returning it for a refund. But the seller is being difficult and is trying to stick me with the phone. I was just trying to salvage it on my own, just in case... Thanks again.
Click to expand...
Click to collapse
that sucks. I've heard good things about Swappa, but living in Canada I can't use it. My opinion it sounds like you got a dud and based on how hard the guy is fighting to not give you a refund, I wouldn't be surprised if he knew it was doa and just fluked out and get it running before he sold it. Or maybe it got water damaged and he knew it would fail soon so he sold it before it completely quit.
I hope you get it all sorted out.
Good luck and sorry I couldn't be more helpful.

bmg002 said:
that sucks. I've heard good things about Swappa, but living in Canada I can't use it. My opinion it sounds like you got a dud and based on how hard the guy is fighting to not give you a refund, I wouldn't be surprised if he knew it was doa and just fluked out and get it running before he sold it. Or maybe it got water damaged and he knew it would fail soon so he sold it before it completely quit.
I hope you get it all sorted out.
Good luck and sorry I couldn't be more helpful.
Click to expand...
Click to collapse
You were great!!! Thanks again...

[UPDATE 12/24/13 ] SOLVED! Hard-bricked? Un-hard brick using sd card SM-N900T/N9005

UPDATE:Thanks to the hard work and diligence of XDA members @noobtoob, @ecs87, and recognized contributor @DocHoliday77, recognized developer @shabbypenguin, and others who will be added to this list after I go through some threads for their names -
It is my pleasure to announce that owners of the T-Mobile Samsung Galaxy Note 3 who have unfortunately hard-bricked
their device, (will not turn on, no led light, qhusb_download mode as device status when plugged into pc) are NOW able to boot their device using sd card mode, instead of expensive JTAG repair!!
noobtoob has been so kind as to ship me the sd card that he successfully flashed, with uncorrupted files from a working tmobile note 3, using odin! Thank you! These files contain all of the prerequisite files needed to boot in this state, to download mode! Once there, a stock firmware flash with ODIN will totally restore your device, just as the SM-N900A variant (at&t), and tmobile and sprint galaxy s3 hard-unbrick methods right here on XDA, can accomplish as I type!
Now, owners of this device can flash with alot more ease, and also this could not only lead to discovery of this method for the entire Note 3 series, perhaps other devices as well!
Read the thread! Why just look for a quick fix when you can actually learn more about the way file systems in android work - and what to avoid doing so that the chances of this happening in the future are less likely? I conducted quite a bit of research, and spoke to some very talented people to get this thread where it is - and to learn some new things myself. This thread contains alot of good insight and discussion about how to solve this issue. Perhaps you could learn something. Either way, all of what you need to fix a hard brick for these two devices is here.
[Update] 12/17/13]
I do in fact now have the sd card. Thanks @noobtoob! The device will not boot still.
I'm going to try a jig also.
[UPDATE] 12-21-13
Thanks to time, guidance, and commands from @shabbypenguin, we found the reason why the sd card noobtoob wrote the umbrick.img to will not boot. It is simply not large enough! So now thanks to proper guidance and this is from shabbypenguin, Tmobile Note 3 users are almost safe from a hard-brick!
If anyone deserves credit for this all, it is @shabbypenguin and @KAsp3rd, and ultimately Samsung, for at least programming their phones to be virtually fail-safe! Special thanks @zinnium to be the first to report this working for them! Thank You!
We have the new .img , so the proper method, and files will be in this post for all to use. For now, they are in this thread. Of course all contributors will be thanked. Give me a little time to get myself together here in the real world, this has happened so fast I've barely had time to keep up!!!!!
Pm me, or post if this method works for you. Now, I mean this only if you first are aware that **IF YOU FLASH ANYTHING OR USE THIS METHOD IT IS AT YOUR OWN RISK - I OR NO ONE ELSE IS RESPONSIBLE BUT YOU!!**
Also, only if you are simply using the very last unbrick.img posted by noobtoob, in this thread. It is ONLY FOR THE TMOBILE NOTE 3 SM-N900T VARIANT!!!! USING IT FOR ANY OTHER MODEL WILL NOT WORK!! THERE IS AN UNBRICK.IMG FOR THE SM-N9005 ALSO AT THE BOTTOM OF THIS POST! **AGAIN - ONLY USE THE .IMG THAT IS FOR YOUR SPECIFIC DEVICE!!!! YOU HAVE BEEN WARNED AND IT IS NOT MY RESPONSIBILITY IF ANYTHING GOES BAD!!!**
The file is 165mb in size, and needs to be written to a 32 or 64 gig sd card with Linux or another image writing tool, even using a CORRECT dd command in terminal emulator, with a rooted device. It has also been confirmed by XDA member zinnium to work with a 310mb system dump from of course - a WORKING T-Mobile Note 3. Also, XDA member aiti1980 has confirmed success with hard-unbricking the SM-N9005 model. The slimmer file does however, also contain all of the necessary partitions to correctly re-write improperly overwritten ones, including recovery!
Do not try to start a new thread and take credit for this!! This is the thread where this method started specifically for the t-mobile note 3 , and I take no credit for this method!!!! The real thanks should go to @shabbypenguin, and @KAsp3rd, who have brought this method, from unknown origins of my knowledge at the time of writing this - to XDA. @shabbypenguin has been kind enough to lend his expertise and time here in this thread, for the t-mobile note 3!! YAY Just in time for Christmas! Merry Christmas All!
UPDATE: 12/24/13 - Here's a Christmas gift for all SM-N9005 owners with a hard-bricked device...
aiti1980 said:
ooo! Thanks!!!
I use adb driver
into cmd win 7 i run:
ADB SHell
su
and you command and get unbrick.img
waiting for result...
I writting *.img on adata Microsd card from win 32 Disk Image
Update: WOW!!! My hard bricked phone power up!
Many thanks from RussiaЖ)))
Where me put unbrick.img: dropbox, or another service?
Click to expand...
Click to collapse
This method works for the SM-N9005 variant too! CONFIRMED!
One step closer for a universal hard-unbrick method for ALL
Galaxy Note 3 Models! HURRAH Special thanks to aiti1980 for being the first to try and succeed! Congrats!
MERRY CHRISTMAS!*
Note 3 SM-N900T unbrick.img
http://www.mediafire.com/?6nu61z43y51v3k4
Thanks to noobtoob for the above SM-N900T unbrick.img
https://mega.co.nz/#!UtNhgAja!XLL6Xy7qxW0L9t4ZgXgowHFNlSsLuz5RIQ-fQc5Ctxk
Thanks to aiti1980 for the above SM-N9005 Unbrick.img upload! ENJOY

Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2

NeoAndroid said:
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?

msmercy42 said:
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
Click to expand...
Click to collapse
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app

chstewart said:
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
The help is much appreciated, however I cannot turn on the phone at all...

msmercy42 said:
The help is much appreciated, however I cannot turn on the phone at all...
Click to expand...
Click to collapse
You should be able to get into download mode still. Try pushing a new recovery with Odin. If still having issues Odin stock or you can also use kies to restore your phone....
Sent from my SM-N900T using xda app-developers app

Thanks for the help, I can't get the phone on at all though... it doesn't even recognize my device other than windows stating that it cannot recognize it, as it
malfunctioned.
Kies, will recognize it, even in this case?
Lastly, are you telling me that there is a way to push recovery with Odin even though the device is off, will not go into download mode, or recovery? If so, that's great!

Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium

d12unk13astard said:
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue avaiable. Again, thanks a lot.

msmercy42 said:
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue available. Again, thanks a lot.
Click to expand...
Click to collapse
Update - I tried using Odin 1.85. I see the device being recognized in one of the ports, but flashing the stock firmware, or twrp yielded no results.
I tried reinstalling the Samsung drivers, nothing. I even tried Odin 3.07, and 3.09. Since the device will not power on, I guess that is why it will not work.
I then tried an emergency firmware recovery using kies. It did not detect the device, which is normal, so I disconnected and reconnected the device repeatedly,
with no success. I uninstalled an reinstalled kies, and that did nothing either.
I installed the android 4.3 sdk, and used adb in an attempt to recognize the device using commands like adb reboot recovery.
Adb replied with : no devices found.
I attempted through windows, to examine the ports, and found that there were different drivers present. The drivers installed on the PC were named QHUSB_DOWNLOAD 9008. When I first plugged the device to the PC, I noticed the device named as QHUSB_BULK, before changing to the above name, the same as the name for the drivers.
So my device is still alive.
Any advice? Can anyone help me get my phone on, at least into download mode? From there I can get it going. Please help if possible.

Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app

chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I tried everything. No, download mode is not working, though I agree that it should theoretically still. I am still trying the three button method.
Would a jig work? I am working on one. Any ideas besides that?

i was going to suggest a jig actually. if that doesn't work you're probably out of a phone. could try warranty since it's REALLY bricked they probably won't be able to tell, did it with T-Mo on my G1, said it stopped turning on.

Have you tried removing the battery and holding down all the buttons before reinserting the battery again. My phone wouldn't turn on once and this helped. If not call tmobile tell them all kinds of funky things are happening with your phone and it keeps turning off. Once they tell you to factroy reset your phone, act like you are following their instructions, then when they tell you to turn it back on, tell them it will now not even turn back on. They are so slow there & will send you out a new one you'll have in 24hrs. Trust me Ive had to do this numerous times due to ocd when it comes to phones and having to have reasons to return them for the slightest flaw. I returned my galaxy note 2 before i got this note 3 like 8x's & even returned it the wk before i bought my note 3 just to get 1 with all new parts if not maybe even a new phone so the note 2 i sold would be in practically new condition if not like i said brand new,lol. im sure someones gonna get all butt hurt and start talking about fraud,lol

In the future you can flash Twr using Goo on your phone with No computer. Use JRummy 's rom Toolbox pro.
Sent from my Nexus 4 using xda app-developers app

chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?

msmercy42 said:
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
Click to expand...
Click to collapse
It doesnt look good. I sent my vzw dev note 3 to Samsung with the same reboot problems and not being able to flash anything, and even they couldn't fix it.
Sent from my SCH-I535 using Tapatalk

msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Sorry to hear! I'll save you a whole bunch of time, I did the same thing to my galaxy s3 while trying to upgrade my installed clockworkmod. Long story short the commands I entered into terminal emulator we're fine its just that I put the wrong memory block which apparently flashed the image to the wrong area of the chip. I rebooted the phone and nothing happened. When I plugged it into the PC I would get the same thing you're getting. After a ridiculous amount of time I managed to get my hands on the correct drivers and installed them and found that flashing a stock firmware through Odin was a waste of time.
You need to send your phone into Samsung and the only solution is a motherboard replacement. Or you can find someone locally who can do a JTAG mod for you. But doing so will definitely void your warranty. When I shipped my phone into Samsung I told them I was using the phone and all of a sudden it got very hot and turned off and wouldn't turn on. Back in the S3 days I had to wait 3 weeks to get my phone back repaired. But these days there now Samsung service centers everywhere so you can probably get replaced phone on the spot.
Sent from my SM-N900W8 using Tapatalk 4

Qhusb_bulk drivers??
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...

M1k3Carson1369 said:
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
Click to expand...
Click to collapse
Nothing yet....and I'm looking everywhere
for a system dump of the T-Mobile note 3, so I can maybe find the files needed for the fix.