Develop Bugs

Any way to root my GN without wiping it?

I think I prob already know the answer here but hoping Im wrong, I have a stock 4.0.4 GN with locked bootloader. I have loads of files, games with lots of progress etc. I want to root my phone but I dont want to wipe it and end up back at square one. I really want to keep things like game saves anfd connected accounts etc.
Is there ANY way I can unlock bootloader and root without wiping everything?

Use my guide.
Linked in sig.
Details on backing-up included.

Something funny is going on. Im trying to follow those instructions but I cant get the adb command to work after the adb reboot bootloader command in the backup step. ADB devices doesnt work. Fastboot devices does work. ADB works fine when the phone is in normal mode.
Im pretty sure I have the latest samsung drivers too.
Jubakuba said:
Use my guide.
Linked in sig.
Details on backing-up included.
Click to expand...
Click to collapse

Maybe boot into bootloader manually if you haven't already?
(While power is off: Volume up + Volume down + Power)

Still not working. ADB runs fine when the phone is on. Bet when its in bootloader mode its not at all.

TheBishopOfSoho said:
Still not working. ADB runs fine when the phone is on. Bet when its in bootloader mode its not at all.
Click to expand...
Click to collapse
Googled around a bit...
And users are reporting this as a driver error.
Try installing PDANet?

On linux, this is not possible as far as i know. Using adb when in bootloader function i mean. I find it hard to believe that it works on windows, especially when the os has many issues with drivers and fastboot itself had a rough history too shortly after it was ported to win, if i recall it correctly.
Sent from my i9250 using Forum Runner

bk201doesntexist said:
On linux, this is not possible as far as i know. Using adb when in bootloader function i mean. I find it hard to believe that it works on windows, especially when the os has many issues with drivers and fastboot itself had a rough history too shortly after it was ported to win, if i recall it correctly.
Sent from my i9250 using Forum Runner
Click to expand...
Click to collapse
You are correct: you can NOT use adb when your device is booted into the bootloader. On any OS..
Sent from my Galaxy Nexus using Tapatalk 2

Toolkit may be coming soon to you guys!

Looking to bring you guys into the action. I'm gonna purchase a kindle fire online on Monday and then make a toolkit on it.
Just a few questions.
You guys use Fastboot commands or no?
Ex: Fastboot flash recovery recovery.img, Fastboot flash boot boot.img
A personal question myself, since there is no removable battery, is there a button trick to shut it off if it freezes?
I have to put all this into consideration when I make the toolkit.
Thanks!
If you don't know what a toolkit is, look in my signature. Just don't look at the Sensation or MT4GS since I still have to update their UIs

Yep you just hold the power button if it freezes and itll shutoff pretty much no matter what. Also please do bring tool kit here

HaiKaiDo said:
Yep you just hold the power button if it freezes and itll shutoff pretty much no matter what. Also please do bring tool kit here
Click to expand...
Click to collapse
Thanks for the reply! What show I know about the device? Anything in particular?
Why is it necessary to flash a different bootloader? (I should be reading on it now, but I'll get a better analysis on it when I order it)
The toolkit is gonna basically be like this but with a graphical user interface
http://forum.xda-developers.com/showthread.php?t=1399889
Will add other options as well, just gotta see how this works since it is different than HTC phones.

bump
help me out so I can help you guys out as well!

Theres already a toolkit

trter10 said:
Theres already a toolkit
Click to expand...
Click to collapse
Who said another one won't hurt? It's good to have choices. Would you rather use one ROM or have choices to choose from?
Sent from my HTC_Amaze_4G using Tapatalk 2

Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2

jacewt said:
Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Can you explain what you mean?
Sent from my HTC_Amaze_4G using Tapatalk 2

jacewt said:
Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
This is true.
Sent from my ADR6400L using Tapatalk 2

What's wrong with the drivers?
Sent from my HTC_Amaze_4G using Tapatalk 2

hasoon2000 said:
What's wrong with the drivers?
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Lets just say If you can get it to connect through adb you are a genius.
Sent from my ADR6400L using Tapatalk 2

the device requires different drivers for adb/fastboot.
once u get adb working, and reboot into fastboot, it usually doesn't get seen by the PC. its one of the biggest issues and lots of people have them when rooting.
Sent from my HTC Glacier using xda premium

I used hasoons toolkit with my amaze and gotta say thanks.hasoon andcant wwait to see what you do fornthe kindle users too.
sent from my kindle fire running gedeROM

Fastboot works real well with the fire. Its a nice device to use with adb and fastboot.
The drivers are really finicky and once you get them set up....don't change anything with regard to your computer as far as your kindle fire development setup. The trick for me (windows 8) is to force disable windows driver signing protocol and to use the windows device manager and USB deview to get the kindle fire drivers established. I would not start off with the kindle fire utility kit or put that in the same directory as your kindle fire development file.
Its a great device and I think a new toolkit does no harm and promotes further development. I strongly advise using TWRP recovery and not clockwork mod as there's some unresolved issues with damaged emmc partitions causing brickedness. (See hashcodes thread with regard to cwm recovery for the 3.0 kernel)
That 3.0 kernel (by Hashcode) pumped massive growth into this device as we did not have hardware acceleration prior to that (outside of the Amazon forked build.)
Now I've no idea what a toolkit is but I'll help test drive anyhow. What's the other toolkit? Vashypoors KFU? That is a nice setup but IMHO people ought to be able to handle ADB and fastboot business before using that KFU or any other toolkit.
You asked about the bootloader? Great write up about why the stock image was replaced by FIREFIREFIRE by Pokey9000 I'll try to find it later but it should be one if the stickied threads here. You can't do a thing with the stock bootloader.
Edit --- I now know what you mean by a toolkit... I didnt realize you made one for the One-S. (nice work, that!!)
Now Im going to get a bit straightforward, dont get me wrong --- these toolkits are great, but they are akin to giving just about anyone on the street a loaded gun... toolkits give an absolute noob or a person who has absolutely no idea whatsoever what they are doing a false sense of security and they believe they have full control of the device where they clearly do not. You effectively give people the easy mind-numbingly-easy opportunity to change something on their device and then they have no idea what its doing or how to get out of any predicament. Thankfully, there are things called "Drivers-Education" and then a "Test" prior to all 16 year olds getting permission to operate motor vehicles!
IT WOULD be cool if you made your toolkit lockable which is unlocked only by the user successfully performing various executions of simple adb and fastboot activities.... i use these toolkits only when my keyboard is broke, or my hands are broke or otherwise occupied by children.
Sent from my HTC One S using xda premium

If you use the KFU on your kindle to root everything should go well. You may encounter problems if you do it manually at least I did a little a bit others my have not. For the driver issue the KFU comes with drivers use them instead when your computer asks for the location. I wish you luck with the toolkit the more the merrier
Sent from my Galaxy Nexus using xda premium

While I'm a huge proponent of the manual method of rooting/modifying the Kindle Fire, I don't think having programs like the KFU is a major problem. The only way Kindle Fire development is going to grow is with more users, even if those users are noobs looking to take the easy way out. The more popular the device becomes, the more likely experienced developers will jump on board.
There really isn't much you can do about people who refuse to follow directions or educate themselves before getting into trouble, other than complaining about it and posting stupid threads like "This is what you people sound like". It all comes with the territory, especially in a world where a mentally retarded two year old can jailbreak an iPhone and feel like a genius afterwards.
As long as people are still searching for the "any" key, I'll still be mumbling TSTFO and yelling HLMGIFY until my face turns blue but I'll be more than willing to put up with it to see this community grow and get some awesome development in the process. So yes, I say bring on the Toolkit, the worst that could happen is I get more fuel for my sick sense of humor.

build something that restores a kindle in an sbf like process to stock original correctly partitioned then you might have a tool that could rescue a whole bunch of people who have broken systems, bootloaders,recoveries and completly wacked out partitions then you will have a tool that will get used to death.

Thepooch said:
build something that restores a kindle in an sbf like process to stock original correctly partitioned then you might have a tool that could rescue a whole bunch of people who have broken systems, bootloaders,recoveries and completly wacked out partitions then you will have a tool that will get used to death.
Click to expand...
Click to collapse
I just have to learn more about it first before I get into doing that unless there is a fix that I can look at.
soupmagnet said:
While I'm a huge proponent of the manual method of rooting/modifying the Kindle Fire, I don't think having programs like the KFU is a major problem. The only way Kindle Fire development is going to grow is with more users, even if those users are noobs looking to take the easy way out. The more popular the device becomes, the more likely experienced developers will jump on board.
There really isn't much you can do about people who refuse to follow directions or educate themselves before getting into trouble, other than complaining about it and posting stupid threads like "This is what you people sound like". It all comes with the territory, especially in a world where a mentally retarded two year old can jailbreak an iPhone and feel like a genius afterwards.
As long as people are still searching for the "any" key, I'll still be mumbling TSTFO and yelling HLMGIFY until my face turns blue but I'll be more than willing to put up with it to see this community grow and get some awesome development in the process. So yes, I say bring on the Toolkit, the worst that could happen is I get more fuel for my sick sense of humor.
Click to expand...
Click to collapse
First, I loved the link to the humor thread. I started laughing because we always deal with that!
Second, I agree. Manual method is the way to go for new users to learn in case anything happens. I just hate doing commands manually all the time so I automate them to make it easier on me.
I would need you guys to help out since you guys have way more experience than me with the Kindle (I'm gonna order it soon). As long as you guys don't mind, then this will definitely come!
Kheladu said:
If you use the KFU on your kindle to root everything should go well. You may encounter problems if you do it manually at least I did a little a bit others my have not. For the driver issue the KFU comes with drivers use them instead when your computer asks for the location. I wish you luck with the toolkit the more the merrier
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thank you sir! I'll see if I can get the drivers issue fixed.
androidcues said:
Fastboot works real well with the fire. Its a nice device to use with adb and fastboot.
The drivers are really finicky and once you get them set up....don't change anything with regard to your computer as far as your kindle fire development setup. The trick for me (windows 8) is to force disable windows driver signing protocol and to use the windows device manager and USB deview to get the kindle fire drivers established. I would not start off with the kindle fire utility kit or put that in the same directory as your kindle fire development file.
Its a great device and I think a new toolkit does no harm and promotes further development. I strongly advise using TWRP recovery and not clockwork mod as there's some unresolved issues with damaged emmc partitions causing brickedness. (See hashcodes thread with regard to cwm recovery for the 3.0 kernel)
That 3.0 kernel (by Hashcode) pumped massive growth into this device as we did not have hardware acceleration prior to that (outside of the Amazon forked build.)
Now I've no idea what a toolkit is but I'll help test drive anyhow. What's the other toolkit? Vashypoors KFU? That is a nice setup but IMHO people ought to be able to handle ADB and fastboot business before using that KFU or any other toolkit.
You asked about the bootloader? Great write up about why the stock image was replaced by FIREFIREFIRE by Pokey9000 I'll try to find it later but it should be one if the stickied threads here. You can't do a thing with the stock bootloader.
Edit --- I now know what you mean by a toolkit... I didnt realize you made one for the One-S. (nice work, that!!)
Now Im going to get a bit straightforward, dont get me wrong --- these toolkits are great, but they are akin to giving just about anyone on the street a loaded gun... toolkits give an absolute noob or a person who has absolutely no idea whatsoever what they are doing a false sense of security and they believe they have full control of the device where they clearly do not. You effectively give people the easy mind-numbingly-easy opportunity to change something on their device and then they have no idea what its doing or how to get out of any predicament. Thankfully, there are things called "Drivers-Education" and then a "Test" prior to all 16 year olds getting permission to operate motor vehicles!
IT WOULD be cool if you made your toolkit lockable which is unlocked only by the user successfully performing various executions of simple adb and fastboot activities.... i use these toolkits only when my keyboard is broke, or my hands are broke or otherwise occupied by children.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No offense taken! Positive criticism at its finest! lol. You really gave me a lot of info and helped out. As I said earlier, I'm new to this. (Still didn't order the kindle yet) so I'm trying to gather all the knowledge so I have a heads up.
I will user TWRP and not add CWM since we don't want anyone to have bad partitions. If you can, link me why the bootloader was replaced by FFF so I have an understanding on that please
I'm gonna update the One S toolkit soon just so you know!
I did have users who had no clue start using the toolkit. The issues they had were not reading the Post I have on Bugs (A directory issue) and they say it doesn't work. The other issue was root (which I fixed) and flashing a GB kernel onto an ICS ROM. They didn't know what it was and thought it was mandatory (even though it is under the optional section) and soft bricked their phones. I removed kernels and if they want to flash a kernel, they have to do it themselves so they can't blame me or anything.
But thanks again for all the info!
smirkis said:
the device requires different drivers for adb/fastboot.
once u get adb working, and reboot into fastboot, it usually doesn't get seen by the PC. its one of the biggest issues and lots of people have them when rooting.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Will do. Thanks for the heads up!
tgamble160 said:
I used hasoons toolkit with my amaze and gotta say thanks.hasoon andcant wwait to see what you do fornthe kindle users too.
sent from my kindle fire running gedeROM
Click to expand...
Click to collapse
Glad you liked my Amaze toolkit (btw, I updated it a few days ago if you didn't check yet)
------------------------------------------------------------------------------------------------
Everyone, I would like to thank you all for all the info you have given me! Feel free to pitch in some links of anything or anything I should know about before I make the toolkit!

Honestly, an absolute majority of the problems stem from not having the proper drivers installed. With that out of the way, I'm sure there would be a lot less posts from people complaining about stuff not working.

hasoon2000 said:
...
I will user TWRP and not add CWM since we don't want anyone to have bad partitions. If you can, link me why the bootloader was replaced by FFF so I have an understanding on that please
...
Click to expand...
Click to collapse
kinfauns wrote an excellent "Kindle Fire for Beginners" (http://forum.xda-developers.com/showthread.php?t=1552547) which goes into the details of things like why the stock bootloader was replaced w/ FFF. Main benefits of FFF is that it kicks in a temporary fastboot, and also enables easy access to recovery.
In the above-linked document, look under the "How do I unbrick my Kindle Fire?" heading for details of the benefits of FFF's temporary fastboot and access to recovery.
Having been a flashaholic, tinkerer and dabbling themer type on my Moto Droid X for the last 1.25 yrs (with several soft-bricks along the way), the general concepts w/ the Kindle Fire were familiar but the devil's in the details. Thanks to kinfaun's guides and other posts in the forums here, I learned the Kindle Fire stuff more quickly and understand things a lot better than I probably would have otherwise.

Help

okay so i flashed ubuntu and i want to return to android. didnt really like ubuntu. my problem is that i cant connect my phone to my computer (windows 7) via usb and put in an android rom. i cant connect my phone to my computer via usb through recovery when i select "mount usb".
there isnt seem to be any "settings" on ubuntu that allows me to select usb mount. D:> help will be appreciated

This thread makes me think we need a dedicated Ubuntu section, I have a feeling this is the first of many many Ubuntu questions. Anybody agree? Is that even possible?
OP can you not download it straight to the phone instead of using the computer? Is there not any file manager apps yet or something?

WiredPirate said:
This thread makes me think we need a dedicated Ubuntu section, I have a feeling this is the first of many many Ubuntu questions. Anybody agree? Is that even possible?
OP can you not download it straight to the phone instead of using the computer? Is there not any file manager apps yet or something?
Click to expand...
Click to collapse
we need a ubunto section for sure
i dont see any file manager apps on ubuntu. it doesnt even have a market place.
i was assuming my phone will automatically connect to my computer so i can drag files into it. ubuntu didnt do that and the phone isnt listed under "my computer"
im just going to get the stock images from google's website and install it using the galaxy toolkit.

WiredPirate said:
This thread makes me think we need a dedicated Ubuntu section, I have a feeling this is the first of many many Ubuntu questions. Anybody agree? Is that even possible?
OP can you not download it straight to the phone instead of using the computer? Is there not any file manager apps yet or something?
Click to expand...
Click to collapse
we already have one:
http://forum.xda-developers.com/forumdisplay.php?f=2068&nocache=1&z=1780378127004951
itsmarkxd said:
we need a ubunto section for sure
i dont see any file manager apps on ubuntu. it doesnt even have a market place.
i was assuming my phone will automatically connect to my computer so i can drag files into it. ubuntu didnt do that and the phone isnt listed under "my computer"
im just going to get the stock images from google's website and install it using the galaxy toolkit.
Click to expand...
Click to collapse
you dont need a toolkit. you need to make sure fastboot works on your computer and verify you have fastboot drivers installed.
the google img flash will work just fine, as long as your drivers are proper and you have fastboot

Pirateghost said:
we already have one:
http://forum.xda-developers.com/forumdisplay.php?f=2068&nocache=1&z=1780378127004951
you dont need a toolkit. you need to make sure fastboot works on your computer and verify you have fastboot drivers installed.
the google img flash will work just fine, as long as your drivers are proper and you have fastboot
Click to expand...
Click to collapse
unfortunatly for me i dont know how to do do.
i have all the drivers and i have fastboot on my phone. but i dont know how to push files doing it manually. thank god for the toolkit

itsmarkxd said:
unfortunatly for me i dont know how to do do.
i have all the drivers and i have fastboot on my phone. but i dont know how to push files doing it manually. thank god for the toolkit
Click to expand...
Click to collapse
it would literally take you 5 minutes to comprehend what the toolkit does, considering the hardest part (installing the drivers) is already done.....
I wish I understood why people think its soo hard to learn it.

Pirateghost said:
I wish I understood why people think its soo hard to learn it.
Click to expand...
Click to collapse
they dont think its hard to learn, they just dont want to learn. they enjoy being spoon fed everything.

itsmarkxd said:
okay so i flashed ubuntu and i want to return to android. didnt really like ubuntu. my problem is that i cant connect my phone to my computer (windows 7) via usb and put in an android rom. i cant connect my phone to my computer via usb through recovery when i select "mount usb".
there isnt seem to be any "settings" on ubuntu that allows me to select usb mount. D:> help will be appreciated
Click to expand...
Click to collapse
I can't see any reason why you wouldn't be able to mount usb from recovery. Did you follow the method from the Ubuntu wiki or did you use CWM?

BslBryan said:
I can't see any reason why you wouldn't be able to mount usb from recovery. Did you follow the method from the Ubuntu wiki or did you use CWM?
Click to expand...
Click to collapse
we dont have sdcards... you cannot mount usb period.

U should of read before flashing this. Ubuntu os is NOT!!! a daily driven rom. But just like any other rom you flash u should of backed up and paid attention to what u where doing. Sorry to hear what happens to u but it is what it is.
Sent from my Galaxy Nexus using xda premium

Zepius said:
they dont think its hard to learn, they just dont want to learn. they enjoy being spoon fed everything.
Click to expand...
Click to collapse
you know who spoonfeeds me answers when i dont know something?
http://google.com
fkn amazing what that man knows....

OP you don't have to flash anything. It's enough to restore a nand backup.

I'm in awe, people actually dare to mess around with things without knowledge of fastboot..........
Beamed from my Maguro.

Mach3.2 said:
I'm in awe, people actually dare to mess around with things without knowledge of fastboot..........
Beamed from my Maguro.
Click to expand...
Click to collapse
Exactly this.

And... What a good and intuitive subjective..."help"
Way to go OP!!
Sent from my Galaxy Nexus using xda app-developers app

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

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.