Develop Bugs

I think i bricked my epic.

I was angry at my current rom which was on MTD so i decided just to you the old samsung "phone flash utility" (Epic4G_FroyoUpgrade_EB13.exe) that was uploaded on their site like a year ago to go back to stock. well i think since the phone was MTD it didnt work and now its stock at the connect cable screen, is there anything i can do?

I am running CleanGB MTD. The first time I tried to install it I had a bad download & needed to redo it from scratch. I used the Samsung EB13 Windows Installer utility to restore my phone back to stock & had no problems at all. It was up & running on MTD just had a few errors that I did not have time to fix that morning & I ran it for a few days after restoring with the utility, rooting, & restoring my backup. But now I'm enjoying the MTD goodness.....
Can you get back into download mode?
If so I would get a different USB cable & try running the installer again.

endurance1 said:
I was angry at my current rom which was on MTD so i decided just to you the old samsung "phone flash utility" (Epic4G_FroyoUpgrade_EB13.exe) that was uploaded on their site like a year ago to go back to stock. well i think since the phone was MTD it didnt work and now its stock at the connect cable screen, is there anything i can do?
Click to expand...
Click to collapse
from what ive been reading on the threads, i believe you can just odin back, and back sure you have reboot and re-partition checked marked.

I found out what the problem was. I should have known this because this happened to me once before. I was using my front USB ports. Front ports on most pc's are only 1.0 and you need to use the back 2.0 ones to work. Most people think its cable issues but its usually just USB port. This samsung utility is a complete gem! screw odin. thanks for the response!!!

endurance1 said:
I found out what the problem was. I should have known this because this happened to me once before. I was using my front USB ports. Front ports on most pc's are only 1.0 and you need to use the back 2.0 ones to work. Most people think its cable issues but its usually just USB port. This samsung utility is a complete gem! screw odin. thanks for the response!!!
Click to expand...
Click to collapse
Glad you got it working. I wasn't sure if the Samsung utility repartitioned...now I know...thanks.
Sent from my SPH-D700 using XDA App

endurance1 said:
I found out what the problem was. I should have known this because this happened to me once before. I was using my front USB ports. Front ports on most pc's are only 1.0 and you need to use the back 2.0 ones to work. Most people think its cable issues but its usually just USB port. This samsung utility is a complete gem! screw odin. thanks for the response!!!
Click to expand...
Click to collapse
Good to hear!!
Glad you got it fixed......

thanks guys. Yeah ive been using that sammy file since ec05 came out. this is the 3rd brick maybe 4th it got me out of. it works for EVERYTHING. better than odin.

Wow, I didn't know this exe thing existed. Odin has NOT been working on my home PC for tje past few weeks(months?) and that has kept me from trying anything that would require Odin to recover from, i.e. mtd.
Glad I read here in the Q&A pretty regularly. Most of the time I'm seeing if there's anyone I can help, but times like this I end up learning new things.
sent from my secret underground bunker

That sounds like a great thing to have sitting on my computer. I tried to find it but was not successful. Can anyone point me to a copy of it.
Thanks
George

ghmacdonald said:
That sounds like a great thing to have sitting on my computer. I tried to find it but was not successful. Can anyone point me to a copy of it.
Thanks
George
Click to expand...
Click to collapse
I am at work so I cannot post the file I have, but I put the file name in & searched in Google & several download options popped up.
Google Search: Epic4G_FroyoUpgrade_EB13.exe
Check it out & let me know if you need me to post a copy of the file, I saw several already on services like multiupload in the search.

Look at the thread stickied in development. The Samsung tool won't work all the time.
-Marcusant via Tapatalk

So my friend gave me his phone to see if I could fix it. It loops in CWM and won't get out of it and I can't connect with odin to it. (My phone connects just fine.) This is the only other thing I can think of. Anyone else got other ideas?
---------- Post added at 01:25 PM ---------- Previous post was at 01:08 PM ----------
Well tried it and phone still not discovered by the PC. I am at a loss at what to do. I know my friend tried to install some type of rom to it and didn't make a backup. It boots in to CWM non-stop and I can flash zips but it never leaves that loop even after the flashes. I can boot into Download mode but the phone won't be recognized. Tried both Odin and this. The phone is getting charged through the cable though which confuses me even more. Any help?!

Anyone have any ideas?! I am at a loss at what to do!

KillerFu said:
Anyone have any ideas?! I am at a loss at what to do!
Click to expand...
Click to collapse
Use a different cable with odin... it may be charging it but its not getting a data connection... also put into download mode and plug in usb... then "jiggle" the cord until it recognizes it...
Sent from my SPH-D700 using Tapatalk

Uninstall and reinstall the drivers. Then also try Odin with the battery and phone plugged in. Make sure you use a better cable than stock.

Device is soft bricked. Can get into download. What next?

I was running the ICS leaked release and decided to try another ROM. I think my mistake was that I didn't flash a custom recovery like Rogue's and just threw the ROM on my SD, went into the stock recovery that came with the ICS leaked ROM, ran Calkulin's wipe and flashed the ROM.
The phone won't boot up. I can get into Download Mode but I don't know where I can download a stock tar to flash in ODIN 1.85. If I try and go to the stock recovery it doesn't work.
Any help would be appreciated.
***EDIT***
It's still stuck at the data.img portion of the process (end process). It's probably not going far from there.
I can't get into the stock recovery but it does allow the download mode still.

Android300ZX said:
I was running the ICS leaked release and decided to try another ROM. I think my mistake was that I didn't flash a custom recovery like Rogue's and just threw the ROM on my SD, went into the stock recovery that came with the ICS leaked ROM, ran Calkulin's wipe and flashed the ROM.
The phone won't boot up. I can get into Download Mode but I don't know where I can download a stock tar to flash in ODIN 1.85. If I try and go to the stock recovery it doesn't work.
Any help would be appreciated.
Click to expand...
Click to collapse
In the dev threads look for sfhubs oneclick el29. Download it and follow instructions. It will be fine.
Team-Nocturnal Blended ICS

Right here is all you need. http://forum.xda-developers.com/showthread.php?p=21134991
Then use autoroot to get cwm back.
Team-Nocturnal Blended ICS

I tried that earlier and it didn't work. I deleted all the files and will try it again. When I tried the steps it just hung at waiting for connection or something to that effect.

Android300ZX said:
I tried that earlier and it didn't work. I deleted all the files and will try it again. When I tried the steps it just hung at waiting for connection or something to that effect.
Click to expand...
Click to collapse
That really sound like you don't have the drivers quite right. When you open the regular odin, and your phone is in download mode, does a yellow box on odin show up? If not its the drivers.
Team-Nocturnal Blended ICS

bigtoysrock said:
That really sound like you don't have the drivers quite right. When you open the regular odin, and your phone is in download mode, does a yellow box on odin show up? If not its the drivers.
Team-Nocturnal Blended ICS
Click to expand...
Click to collapse
Yes. It shows COM port I in yellow which is a good thing because it recognizes something is connected.

Android300ZX said:
Yes. It shows COM port I in yellow which is a good thing because it recognizes something is connected.
Click to expand...
Click to collapse
Then the one click should work just fine. Make sure you follow his instructions to the T. Also on his page he has some drivers, you should install those, it uninstall or over write the old ones. Just to be sure.
Team-Nocturnal Blended ICS

Thanks. It looks like it's working now. It's installing right now and then we shall see but I'm pretty sure it'll work. I'll leave it stock for now until ICS comes out. I'm so buy working on my new car that I barely have time to geek out anymore on my phone.

Don't try to flash anything with stock recovery ...it has to be officially signed by Samsung ...won't work
Sent from my SPH-D710 using XDA App

It didn't work. Last night I went to run the EL29 Restore - Rooted and it got stuck on the data.img portion. The progress bar on the phone and computer just hung there. I disconnected the cable and went to bed (after 1.5 hours of it just sitting there stuck).
I'm trying it again today and lets see if it gets stuck.
I'm reflashing EL29 over the FB21 (w/e the leaked version of ICS was) I had. Is that the issue?

Sorry but I think your bricked. There is a "Stuck at Data.img" thread here in q&a.
The issue still isn't repairable.
The way you went about getting stuck here is a little different tho. So hopefully I'm wrong.
Good luck

Are you stuck in a bootloop? If so, do you get any further than the Samsung splash screen?
Try re-flashing the ICS leak. I read somewhere that it could be a filesystem issue with switching to and from GB. If that doesn't work, maybe you'll have better luck with using ODIN as opposed to the one-click method. You'll find the tars here-
http://forum.xda-developers.com/showthread.php?t=1391732
In most cases you'll be flashing them in PDA, but read everything closely, and follow the steps.
If you have insurance, I almost suggest going to Sprint while it still seems there's no evidence you've been flashing (yellow triangle), as they'll likely just replace it for you.
If none of that works, then it sounds like a rare problem that happened to mine a few months ago. This was the only thread I found at that time, but it was for AT&T's GSII.
http://forum.xda-developers.com/showthread.php?p=20834412#post20834412
I ended up getting a new one, but I would love to finally find a solution since I still have it. Pretty much the only thing I haven't tried is a JTAG service.

Juq said:
Are you stuck in a bootloop? If so, do you get any further than the Samsung splash screen?
Try re-flashing the ICS leak. I read somewhere that it could be a filesystem issue with switching to and from GB. If that doesn't work, maybe you'll have better luck with using ODIN as opposed to the one-click method. You'll find the tars here-
http://forum.xda-developers.com/showthread.php?t=1391732
In most cases you'll be flashing them in PDA, but read everything closely, and follow the steps.
If you have insurance, I almost suggest going to Sprint while it still seems there's no evidence you've been flashing (yellow triangle), as they'll likely just replace it for you.
If none of that works, then it sounds like a rare problem that happened to mine a few months ago. This was the only thread I found at that time, but it was for AT&T's GSII.
http://forum.xda-developers.com/showthread.php?p=20834412#post20834412
I ended up getting a new one, but I would love to finally find a solution since I still have it. Pretty much the only thing I haven't tried is a JTAG service.
Click to expand...
Click to collapse
If I turn on the phone I get a screen that says
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I don't get to the point where it even shows me a Samsung logo; just straight to that screen.
When I go into Download Mode I see
ODIN MODE
Product Name: SPH-D710
Custom Binary DOwnload: No
Current Binary: Samsung Official

Here's the thread caspersfi mentioned. I'm reading through it myself now.
http://forum.xda-developers.com/showthread.php?t=1504808&highlight=stuck+at+data+img
Good luck!

Juq said:
Here's the thread caspersfi mentioned. I'm reading through it myself now.
http://forum.xda-developers.com/showthread.php?t=1504808&highlight=stuck+at+data+img
Good luck!
Click to expand...
Click to collapse
I'm reading it now. I want to add that it was CWM touch that messed up my phone because I had flashed that before attempting to flash another ROM since ICS build came with the default factory recovery. So I'm guessing my file system is corrupt. I'll keep reading through the thread. (I skipped to the last couple of pages.

Hey so can you still get into download mode? I ran into the same problem where it kept getting stuck in odin. Try a different usb cable and a different port. Odin is very fussy with usb cables. When I had the trouble I was using a Logitech usb cable. Switched to the one that came with my phone and it worked like a charm.

rbtrucking said:
Hey so can you still get into download mode? I ran into the same problem where it kept getting stuck in odin. Try a different usb cable and a different port. Odin is very fussy with usb cables. When I had the trouble I was using a Logitech usb cable. Switched to the one that came with my phone and it worked like a charm.
Click to expand...
Click to collapse
I'm using the one that came with the phone and I tried different ports. I don't have another cable to use but I doubt that will help me out. Thanks for the suggestions though.

Android300ZX said:
I'm using the one that came with the phone and I tried different ports. I don't have another cable to use but I doubt that will help me out. Thanks for the suggestions though.
Click to expand...
Click to collapse
I didnt think it was possible that a simple cable swap would help me when I was in the exact same position as you either but it sure did. What could it hurt to just try a different cable? I am sure you could borrow one from a friend just to try it. According to qbking77 samsung cables are pretty bad when it comes to using odin.

rbtrucking said:
I didnt think it was possible that a simple cable swap would help me when I was in the exact same position as you either but it sure did. What could it hurt to just try a different cable? I am sure you could borrow one from a friend just to try it. According to qbking77 samsung cables are pretty bad when it comes to using odin.
Click to expand...
Click to collapse
I will try that shortly then. I have a paper that's due today to write so school before phone, lol.

Alright i really hope it works, let us all know.
Sent from my SPH-D710 using XDA App

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.

Note 7 SM-N930F bricked / / need help!

I flashed TWRP with odin.
After that I was not able to boot or start recovery.
Only download mode is possible.
In download mode it shows
warranty void 1 (0x030c)
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Can anybody help me, how to get this beautiful phone running again?
Thanks so much!
MOD EDIT:
This member is talking about this.
TEKHD

bill340 said:
I flashed TWRP with odin.
After that I was not able to boot or start recovery.
Only download mode is possible.
In download mode it shows
warranty void 1 (0x030c)
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Can anybody help me, how to get this beautiful phone running again?
Thanks so much!
MOD EDIT:
This member is talking about this.
TEKHD
Click to expand...
Click to collapse
try to download the firmware from http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/ and try to flash via odin.
Never ever try to flash anything till the time there is no evidence of success.

I tried that, but the problem is that I always get this error in Odin when trying to flash...

Did you check OEM unlock before you flash as per the instructions? not doing so will result in a boot loop.

Try different cable and USB port. I had trouble with both that had me running in circles.
Sent from my SM-N910T using Tapatalk

Yes, I did OEM unlock before the flash.
Different cable and USB port makes no difference...

Usually when I have issues I try to uninstall all drivers related to phones and only install the one I need. Then after a restart and forcing the phone into Odin I'm able to flash without issues.

It might be failing because of a Partition size error. Have you tried the Samfirm Tool to download a firmware from your region?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
Also, I'm doubtful whether this is a new trick up from Samsung's sleeve. This Phone is still new, so it's quite a learning process. Maybe Samsung has implemented something to block these unofficial flash attempts. However I thank you taking the risk and trying the recovery first.

Can you help me, where I can get this?
Have you tried Emergency Device Recovery from SmartSwitch PC ?

bill340 said:
Can you help me, where I can get this?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
Click to expand...
Click to collapse
Download and install SmartSwitch for PC. Then follow this Video.

I really have no luck here...
Any idea?
Googled already, but did not really find anything besides reinstalling...

I dont think theres a fix for this issue yet. There's also no subtantiated literature in the larger cummunity pertaining to rooting the Note 7.
I am guessing this is an additional precaution taken by Samsung therefore the rooting process needs a very specific set of steps in order to circumnavigate the systems Sammy has put in place. The thread itself says WIP, so I applaud you for your courage.
Nonetheless my suggestion is to instead of waiting for an answer which no one can provide, go to Sammy and bull**** to them that u plugged in the computer and it became a brick.
Theres is no possible senario whereby the internet can help you because we know next to nothing about Note 7.
I sincerely hope that you can come out of the situation with a working Note 7 in your hands whilst not burning a hole in your wallet due to the repairs. God-speed my friend, God-speed.

bill340 said:
I really have no luck here...
Any idea?
Googled already, but did not really find anything besides reinstalling...
Click to expand...
Click to collapse
This seems to be an issue in your drivers, Please uninstall all samsung related and flash box related (if exists) in your PC and try installing it again.
Alternatively, you can just walk into a Samsung Care store and get it done while you wait.

I did that already... No luck. I will try on a different pm next.

Bill sad to see this happened to you
I am exactly coming for the same forum and was following the same steps thought u were, but u took one more step forward and flashed the vitanamese firmware, your phone just messed up there. Was actually about to do the same thing but then read your comments. My phone starts but with errors and has battery drainage , i havent lost anything as it is still virgin and havent transfered anything to it yet. Will wait probably 4 to 5 days more for the official firmwares to release and fire it in.
Sorry to say but u had become the test subject...
---------- Post added at 11:07 AM ---------- Previous post was at 11:03 AM ----------
The recovery mode cannot be accessed, no matter how hard you try
Sent from my SM-N920C using XDA Free mobile app

I just was in the Samsung Care Center in Singapore with my bricked phone.
After 1 hour waiting time, a Samsung guy explained me, that they cannot do anything about it, because they don't have parts ? for this phone in Singapore because it was not launched yet and also there is no international warranty on it.
He had no idea about any software recovery or anything and suggested to get back to Dubai, where I got the phone from.
Really a bad Customerservice experience.
I also want to thank all of you for your great help and suggestions!
I think I will send the phone back to the store in Dubai now.

Well tht will be a good choice
But if u give it three more days and wait for the official firmwares to release would save you some time.
I am still following up with it.
Sent from my SM-N920C using XDA Free mobile app

I really doubt, that this will help, since I cannot flash anything in odin. After initialization I always get the error "FAIL (DeviceInfo)"

bill340 said:
I just was in the Samsung Care Center in Singapore with my bricked phone.
After 1 hour waiting time, a Samsung guy explained me, that they cannot do anything about it, because they don't have parts ? for this phone in Singapore because it was not launched yet and also there is no international warranty on it.
He had no idea about any software recovery or anything and suggested to get back to Dubai, where I got the phone from.
Really a bad Customerservice experience.
I also want to thank all of you for your great help and suggestions!
I think I will send the phone back to the store in Dubai now.
Click to expand...
Click to collapse
Same here in (Dubai) Mate, They don't even have the parts, or Tools to open the device up. If you remember me, I screwed up my Note 7 a week back, Just after two days from launch, and I still didn't receive it. They are still unable to sort it out.
I'm sure when a proper firmware for XSG (Dubai - Same as your device) and a proper ODIN is released to flash the Note 7, this will be a piece of a cake. Just hope for the best, As just like you - I too took a leap of faith and did something stupid.
Anyway, Wishing you luck !

I am not sure if this will help....
What happens when you try a older version of Odin?
Its worked for me in the past, with my s6 edge.