Related
*First of all, let me say that this is a repost from here (http://forum.xda-developers.com/showthread.php?t=1153310&page=27), and I apologize for that fact. I have been severely neglecting food and sleep trying to fix my phone, and I really, really didn't feel like typing the whole damned story up again. Any assistance or insight would be deeply appreciated...
-------------------------------------------------------------------------------
Well, I did it this time I think. I've hacked, modded, wiped, and flashed my phone since I got it last year, and although I've gotten to places where I thought I had totally fuxored things up beyond recovery, every single time in the past I've been able to bring it back from the brink of oblivion. I am exceedingly resourceful and tenacious, which can be both a good and bad thing. Good thing when I am able to fix things that seem unfixable. Bad when I forget about things like eating or sleeping.
Here's the present situation: 4 days ago I was trying to flash a new modem (FB15)(something I know well how to do as I've done it many, many times before) through Odin, when it stalled out near the beginning of the process. This is not unusual with Odin, so I've gotten into the habit of closing it, pulling the battery, and starting again. This time, however, no matter what I've tried, I cannot get Odin to successfully flash. It fails every single time. Either that or it stalls yet again.
At the moment I can only get into 2 modes on my phone: download mode (which can't actually download anything apparently) and the very unpleasant computer--!--phone screen when I try to boot it up or go into recovery. This is the longest my phone has been unusable. I've been intensely focused on fixing it since it was semi-bricked. The ridiculously frustrating and annoying thing is that the computer I'm using (and I've used multiple to try to fix this across Windows, Linux, and Mac) usually says "USB device not recognized" when I plug my phone in while in download mode, no matter the state of the drivers, and when it does recognize it and it is visible in Odin, it means nothing because Odin fails no matter what file I'm trying to flash. When the computer and Odin DO recognize the phone, and when Odin doesn't hang, very occasionally it will give me some odd error message like "PIT mapping not found" or "cannot open COM port". I've tried so many of the things I've tried in the past that have worked: changing USB ports, rebooting the computer between attempts, uninstalling and reinstalling drivers, going into download mode with the SD-card and battery out and in, loading Odin after or before putting the phone into download mode, trying on different computers with different versions of Windows (I even tried one Mac with iOS 10.4 and a Linux notebook with Ubuntu), trying different USB cables, flashing with the battery and SD card out, trying to flash different files (besides the original modem.bin which stalled), running Odin as administrator, yadda, yadda, yadda...on and on, for days. I even just went out and bought a high-performance, super-short USB cable (6-inches) and a USB 3.0 PCI card so I'd have dedicated USB. Nada.
Basically my phone seems to have a broken download mode with potentially wonky USB (Samsung USB has never been good). I've been seeing if I can get Heimdall to work, though there is a bit of a learning curve with that program, no matter how easy people say it is. I've never even tried flashing it with it yet since I haven't gotten together all of the apparently necessary files. I also just found One-Click Unbrick, and while I was excited originally, it seems that the same outcome is the result. No matter what I do to get everything just right to be able to succeed, it fails. Java is installed, Heimdall is apparently installed, and the One-Click Unbrick drivers have been installed every time I've tried to run it. Nada again.
If my phone is able to get into download mode, yet that seems to be borked, what is my recourse? I'm at the end of my rope...*sinks into a depressed lump on the floor*.
ANY assistance would be immensely appreciated. Thank you all in advance. I'm not incredibly hopeful at this point, but I am (fortunately or unfortunately) still tenacious as hell. :-/
Setup:
Phone: Samsung Epic 4g
ROM: SleeperROM 2.0.04 EL30/MTD (Gingerbread 2.3.6)
Kernel: The last available Samurai kernel
Recovery: ClockworkMod Recovery 5.0.2.7
Filemap/Filesystem: MTD/Yaffs2
Present Computer: Windows Vista Home Premium 32-bit/AMD desktop
Modes available on phone: download and computer--!--phone screens
Issue: cannot flash anything in download mode via Odin on present computer
Wow im glad i didnt have to go through this i was trying to flash the fb15 modem recently as well and it wouldnt go through all i did was go and find the el30modem tar and flashed that and i was all good again. ... youve tried literally every suggestion i was going to say. other than try flashing the el30modem.tar? I know for sure its good its in android development if you can get odin to COM im sure it will work...
http://forum.xda-developers.com/showthread.php?t=1501424
add me on gtalk
crystylizd[email protected] and ill see if i cant help you out.
Big Goron said:
Wow im glad i didnt have to go through this i was trying to flash the fb15 modem recently as well and it wouldnt go through all i did was go and find the el30modem tar and flashed that and i was all good again. ... youve tried literally every suggestion i was going to say. other than try flashing the el30modem.tar? I know for sure its good its in android development if you can get odin to COM im sure it will work...
http://forum.xda-developers.com/showthread.php?t=1501424
add me on gtalk
[email protected] and ill see if i cant help you out.
Click to expand...
Click to collapse
I thank you much for your suggestion. I've tried flashing the EC05 modem tar and both the tar.md5 and the straight tar file of the stock EL ROM, though surprisingly I haven't tried the straight EL30 modem tar yet. I'll try when I get home. The main problem is not getting Odin to COM, but getting it to flash anything. It either stalls, fails, or doesn't see the phone...download mode seems to be basically useless.
homam_france said:
@+Que ppc really your BA downgrade and upgrade is long story,did u finish it?i hope the answer is yes,about the hexaguns we cannot return back to it,but i can make modification to the new components of the new build,capish
Click to expand...
Click to collapse
If you get it to recognize still then Odin with the battery and sd card out.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
If you get it to recognize still then Odin with the battery and sd card out.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I usually flash in Odin with the battery and SD card out. No go.
tydynrain said:
I usually flash in Odin with the battery and SD card out. No go.
Click to expand...
Click to collapse
It is possible you have some crap in your phone's port. Or even the new cable is flaky. Get a bright light and magnifying glass and look in your phone's port. Also try fresh downloads of the files.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
It is possible you have some crap in your phone's port. Or even the new cable is flaky. Get a bright light and magnifying glass and look in your phone's port. Also try fresh downloads of the files.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I'l check the USB/charging port when I get home from work. Most of the files I've used, including the various versions of Odin, came from my synched Dropbox folder. I'm wondering now if Dropbox synches files accurately. I'll try redownloading every file I use to flash to see if it has a beneficial effect. Thanks for the suggestion.
hope this helps
tydynrain said:
I'l check the USB/charging port when I get home from work. Most of the files I've used, including the various versions of Odin, came from my synched Dropbox folder. I'm wondering now if Dropbox synches files accurately. I'll try redownloading every file I use to flash to see if it has a beneficial effect. Thanks for the suggestion.
Click to expand...
Click to collapse
Let me find you some reliable files
Odin 1.85
Stock El30
Windows 32 bit and 64bit drivers
This should be enough to get you on your way. Oh and if you can at all possible reinstall windows prior to loading these drivers. i know someone who had to do it before their computer would recognize their phone. I've been in this kind of situation i had someone root my phone and is computer was fubar'd and it took him 3 days to unbrick my phone. This is what helped him he kept recieving unknown device. This is what helped is what helped him id advice the same. Once you have windows reinstalled download the three things and install the drivers and give it a shot.
Big Goron said:
Let me find you some reliable files
Odin 1.85
Stock El30
Windows 32 bit and 64bit drivers
This should be enough to get you on your way. Oh and if you can at all possible reinstall windows prior to loading these drivers. i know someone who had to do it before their computer would recognize their phone. I've been in this kind of situation i had someone root my phone and is computer was fubar'd and it took him 3 days to unbrick my phone. This is what helped him he kept recieving unknown device. This is what helped is what helped him id advice the same. Once you have windows reinstalled download the three things and install the drivers and give it a shot.
Click to expand...
Click to collapse
Thank you so much for the time. I'll see about reinstalling Windows, though since it's not my computer I'm not too sure how that will go...hehe. I may be able to restore from the backup partition if he doesn't have a CD.
well you can do it over a virtual machine but unsure how to do this and if this will work entirely it might it might not im not too fluent with virtual machines.. but it simulates a working computer so id imagine you can install drivers and see if it will then recognize your phone.
Big Goron said:
well you can do it over a virtual machine but unsure how to do this and if this will work entirely it might it might not im not too fluent with virtual machines.. but it simulates a working computer so id imagine you can install drivers and see if it will then recognize your phone.
Click to expand...
Click to collapse
So interesting that you mention running a virtual machine, as since I can't reinstall Windows Vista on this system, I was considering partitioning the hard drive and installing a version of Linux, then running WINE under that.
Lol try that... or windows i think windows might be your best bet...
Sent from my SPH-D700 using xda premium
Whoa whoa, tdy...queston. have u manually installed ur driers directly from samsung website?
Sent from my SPH-D700 using xda premium
Kies drivers worked for me
Sent from my SPH-D700 on CM9 beta0 using xda premium
I FIXED IT! My phone which has been dead for 5 days lives again! Resurrected!
I thank you all for your time and assistance. It was very deeply appreciated.
I fixed it by circumventing Winblows entirely. I created a second partition on my friend's hard drive, installed Ubuntu Linux 11.10, then went through the pretty simple process of setting up Android SDK/ADB and Heimdall, and all of the dependencies that they required. The ridiculous thing is that I fixed it without even trying. I was simply seeing if Heimdall could detect my phone (which I had connected and in DL mode), which I noticed that it did. I had no idea what Download PIT did, so I pressed it, and lo and behold, it did something amazing, and rebooted my phone. I am elated, exhausted, triumphant!
WHOOT!!!
I kNEW I would figure it out. I always do...lol.
In messing up my phone so many times, I have gotten VERY good at fixing whatever nonsense happens to arise.
Thanks again all.
Tydyn.
EDIT: I meant PRINT PIT, not Download PIT. ;-)
YAY!
tydynrain said:
I FIXED IT! My phone which has been dead for 5 days lives again! Resurrected!
I thank you all for your time and assistance. It was very deeply appreciated.
I fixed it by circumventing Winblows entirely. I created a second partition on my friend's hard drive, installed Ubuntu Linux 11.10, then went through the pretty simple process of setting up Android SDK/ADB and Heimdall, and all of the dependencies that they required. The ridiculous thing is that I fixed it without even trying. I was simply seeing if Heimdall could detect my phone (which I had connected and in DL mode), which I noticed that it did. I had no idea what Download PIT did, so I pressed it, and lo and behold, it did something amazing, and rebooted my phone. I am elated, exhausted, triumphant!
WHOOT!!!
I kNEW I would figure it out. I always do...lol.
In messing up my phone so many times, I have gotten VERY good at fixing whatever nonsense happens to arise.
Thanks again all.
Tydyn.
Click to expand...
Click to collapse
CONGRATS im happy you got your phone back i know how you feel finally getting your phone back i went through the same deal cept it was with someone else. Oh and im jealous you have 11.10 working i couldnt get it working right with my laptop gpu drivers.. fail. anyways glad you got it
Big Goron said:
CONGRATS im happy you got your phone back i know how you feel finally getting your phone back i went through the same deal cept it was with someone else. Oh and im jealous you have 11.10 working i couldnt get it working right with my laptop gpu drivers.. fail. anyways glad you got it
Click to expand...
Click to collapse
Thank you brother! I am practically jumping around the house singing...lol. Ubuntu 11.10 is freaking gorgeous! It is the most amazing operating system I have ever used. I am in love!
tydynrain said:
Thank you brother! I am practically jumping around the house singing...lol. Ubuntu 11.10 is freaking gorgeous! It is the most amazing operating system I have ever used. I am in love!
Click to expand...
Click to collapse
Yeah i love it as well im sadly stuck with 10.04 which isnt bad but i like the newest ones UI its just so much more appealing than 10.04 but 11.10 doesnt like my GPU and is incompatible i do know a work around but have already got settled in 10.04
Big Goron said:
Yeah i love it as well im sadly stuck with 10.04 which isnt bad but i like the newest ones UI its just so much more appealing than 10.04 but 11.10 doesnt like my GPU and is incompatible i do know a work around but have already got settled in 10.04
Click to expand...
Click to collapse
My housemate is running 10.04, so I'm familiar with how it looks. If it makes ya feel any better 11.10 doesn't like my new usb wireless network adapter (Netgear N900 Dual Band), which is MUCH better than the one to which I had to revert to get internet access, though I'm hoping that I can get it working somehow soon.
tydynrain said:
My housemate is running 10.04, so I'm familiar with how it looks. If it makes ya feel any better 11.10 doesn't like my new usb wireless network adapter (Netgear N900 Dual Band), which is MUCH better than the one to which I had to revert to get internet access, though I'm hoping that I can get it working somehow soon.
Click to expand...
Click to collapse
I had alot of trouble even getting internet to comply... i finally got it to speed up using wifi and even that was a pain in the arse luckily other people had my same issue and had a resolution for it. I know you have to have the drivers for said wireless adapter installed for it to work correctly otherwise its not going to work
I'm on stock and I decided I wanted to try CM10. I've been flashing for almost 2 years now with my captivate and S2.
I went here: http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
Flashed the first file and noticed no recovery...
I then noticed I had no more internet, so I decided to try and go back to stock.
Now ODIN will recognize, but hangs before any actual flashing. I am at a loss here. The phone works, but I can't flash anything! Help please?
I would suspect the reason Odin isn't working properly is because the one mention on that site is not the proper (or atleast recommended) version to use with i747. Also their logic to flash custom recovery before achieving root, although possible (maybe??), seems flawed to me. Also, flashing anything other than an officially signed .tar through Odin trips the flash counter, which from a so called 'Noob Friendly' guide seems counter intuitive. Try using the guide posted HERE over on in the development forum here on XDA and see if you get better results.
Ok I figured it out. I was using my old Captivate USB cable and not the one that came with the new phone. CM10 is up and running. Thanks for the link btw, that helped.
Good to hear you got it working , glad to help.
offtopicjack said:
Ok I figured it out. I was using my old Captivate USB cable and not the one that came with the new phone. CM10 is up and running. Thanks for the link btw, that helped.
Click to expand...
Click to collapse
I have flashed via Odin with my cappy cable! Maybe it varies in effectiveness? One thing I did notice however is adb can't see my captivate when I use my gs3 cable(odd eh?)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
It is definitely an intermittent problem that I can recall happening since I started with android back on the Samsung Moment. Some devices like certain cables, and doesn't like others.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
The instructions on are for Windows with twrp etc, .exe files... I've rooted Samsung Phones on my Mac, but this tablet seems different from what I'm reading and don't want to screw it up lol. I read a few different things on twrp on Macs and a lot of issues people ran into, unless they did something wrong?? Basically I just want to know how to root and use twrp on Mac with this tablet so I can use other roms I've used on my phones (currently Sho3).
Thanks in advance for any help
115 views and nobody?? lol ... searching online it seems there are multiple ways (unless people wrote instructions differently) for similar on a Mac. I just want to make sure I don't screw this tablet up, I've done my Samsung phones on my Mac.
How were you doing them on a Mac? What was the process, I mean.. I would imagine that you could use Heimdall and load the TWRP image with it, in order to get the custom recovery, then root/install SU after that on the device.
I'm not sure if Heimdall is actually going to work with the gt3, but it's worth a shot.. It's the only cross-platform image writer, for Samsung devices, that I know of. I could be wrong, however.
Edit: here's the link for it: http://forum.xda-developers.com/showthread.php?t=755265
foil said:
How were you doing them on a Mac? What was the process, I mean.. I would imagine that you could use Heimdall and load the TWRP image with it, in order to get the custom recovery, then root/install SU after that on the device.
I'm not sure if Heimdall is actually going to work with the gt3, but it's worth a shot.. It's the only cross-platform image writer, for Samsung devices, that I know of. I could be wrong, however.
Edit: here's the link for it: http://forum.xda-developers.com/showthread.php?t=755265
Click to expand...
Click to collapse
Sorry forgot about this, yeh used Heimdall. I may try later on.
1. Install most recent Heimdall from http://forum.xda-developers.com/showthread.php?t=755265
2. Open Heimdall frontend from applications folder of your Mac.
3. Put device into download mode with power+vol down+home. Will sometimes require multiple attempts. When successful you will see warning about adding custom software to your device.
4. Click utilities tab of Heimdall and detect device.
5. Download pit file to your Mac with the save as dialouge.
6. Click on flash tab of Heimdall.
7. Select pit file you just created
8. Hit add partition select RECOVERY and then select the custom recovery you have already dowloaded from the other threads. Extract to .img before selecting the recovery though. Make sure repartition is NOT selected
9. I unchecked no reboot and resume. (Near bottom right by the start button)
10. Hit start.
11. Verify by restarting with power+vol up
Check my other post at http://forum.xda-developers.com/showthread.php?p=47060381#post47060381 for screenshots describing these steps. And possibly some answers to questions already asked in that thread.
Just did this to mine and it worked fine is OSX 10.9 & Heimdall 1.4.0 and the TWRP_T31x_r3.tar recovery. I should note that this is the SM-T310 8" Tab
zibrah3ed said:
1. Install most recent Heimdall from http://forum.xda-developers.com/showthread.php?t=755265
2. Open Heimdall frontend from applications folder of your mac.
3. Put device into download mode with power+vol down+home.
4. Click utilities tab of heimdall and detect device.
5. Download pit file to your mac with the dave as dialoge.
6. Click on flash tab of heimdall.
7. Select pit file you just created
8. Hit add partition select RECOVERY and then select the custom recovery you have already dowloaded from the other threads. Extract to .img before selecting the recovery though.
9. I unchecked no reboot and resume.
10. Hit start.
11. Verify by restarting with power+vol up
Just did this to mine and it worked fine is OSX 10.9 & Heimdall 1.4.0 and the TWRP_T31x_r3.tar recovery. I should note that this is the SM-T310 8" Tab
Click to expand...
Click to collapse
Thanks a lot for the steps. But I'm getting an error. It says Initialising protocol...
ERROR: Protocol initialisation failed! at the last step where I'm flashing the recovery. Could you please help me? I did exactly as you said.
Thanks.
EDIT: also, I'm on OSX 10.9 as well, and using all the same versions as yours.
---------- Post added at 04:30 PM ---------- Previous post was at 04:20 PM ----------
sw6lee said:
Thanks a lot for the steps. But I'm getting an error. It says Initialising protocol...
ERROR: Protocol initialisation failed! at the last step where I'm flashing the recovery. Could you please help me? I did exactly as you said.
Thanks.
EDIT: also, I'm on OSX 10.9 as well, and using all the same versions as yours.
Click to expand...
Click to collapse
NVM, I got it to work. Searched on google, and someone had the same problem with heimdell and he just rebooted and tried next day or something. So I rebooted and it worked.
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
zibrah3ed said:
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
Click to expand...
Click to collapse
Awesome it worked. Didn't get a chance to do so yet, was honestly a little nervous even though I've used Heimdall on Mac for phones. There's like no support or anything for this tablet, not sure why, it's selling like crazy, BB can barely keep them in stock and it's been out for months. Yet other newer tablets have huge support already and roms etc.
Love it, but kinda wish I got something else now, only thing you can do is root this thing.
surf1 said:
Awesome it worked. Didn't get a chance to do so yet, was honestly a little nervous even though I've used Heimdall on Mac for phones. There's like no support or anything for this tablet, not sure why, it's selling like crazy, BB can barely keep them in stock and it's been out for months. Yet other newer tablets have huge support already and roms etc.
Love it, but kinda wish I got something else now, only thing you can do is root this thing.
Click to expand...
Click to collapse
With Cyanogen not building stable releases for Exynos 4 devices I don't think we will see a ton of action on the AOSP front for this device. With that being said Xposed works on this tablet and provides some of what I'm looking for in custom roms. I use Wanam and Gravity Box modules and I am happy now with stock rooted and using Xposed.
zibrah3ed said:
With Cyanogen not building stable releases for Exynos 4 devices I don't think we will see a ton of action on the AOSP front for this device. With that being said Xposed works on this tablet and provides some of what I'm looking for in custom roms. I use Wanam and Gravity Box modules and I am happy now with stock rooted and using Xposed.
Click to expand...
Click to collapse
yeh I wish we had roms like my i777, I've stuck with Shostock on it, and the phone is so smooth and fast and stable.
zibrah3ed said:
Good to hear you got it working. Not a lot of people around to help on this tablet.
Sent from my HTC6500LVW
Click to expand...
Click to collapse
I just realized I still have Heimdall 1.3.1 still on my Mac, as I'm still on 10.5.8 , I don't think the newer versions of Heimdall work unless on the current OS/X as one says there are issues with 10.6 etc. Wonder if I can still use 1.3.1?
surf1 said:
I just realized I still have Heimdall 1.3.1 still on my Mac, as I'm still on 10.5.8 , I don't think the newer versions of Heimdall work unless on the current OS/X as one says there are issues with 10.6 etc. Wonder if I can still use 1.3.1?
Click to expand...
Click to collapse
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
zibrah3ed said:
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
Click to expand...
Click to collapse
I just never updated it after they cut support for 10.5.8 to keep buying OS after that lol, I've had other MBP and just sold my Retina, too many glitches and odd stuff with the recent OSs, and waiting to see the new model that should have some nice fixes both hardware wise and software. Plus I use Win7 in a virtual system and it's so stable, Virtuals have run into so many issues on the newer OSs from peoples reports and my experience. Only thing is I know people say you can use that to root these easier, I've never gotten any phone to show up to work with in Win in a Virtual System, plug usb in and nothing happens (still goes to OS/X). I only kept this 13" Pro as it's reliable and stable lol, even spilled a big ass jug of water on it once when the dogs when crazy chasing each other and one got caught on my cord and knocked the water over onto the keyboard. I flipped it over and turned it off and stuck it in rice, somehow works fine.... my good luck charm hahaha
Wonder if the new Heimdall (1.4) will work on os/x 10.5.8? I'll msg the dev
zibrah3ed said:
Reading the change logs from 1.3.1>1.3.2>1.4.0 compatibility with some devices was enhanced/added. It does not mention ours specifically. I personally wouldn't try it on 1.3.1 but it is your tablet. Why are you stuck on Leopard? PPC?
Click to expand...
Click to collapse
So I totally forgot about this thread as there was no rom development anyway. Now there are some nice roms for this tablet so want to root and flash. Except can't figure this out, I tried different Heimdalls and they all do the same thing, they say "heimdall crashed" when opened up, but the program is there. When you click on detect devices it says "FRONTEND ERROR Heimdall Crashed".
I messaged the Dev but never heard back. On os/x 10.5.8 and tab is T310 wifi. Some say this Heimdall works for these devices but not on osx version whatever, then vice versa..... ughh confusing lol. No clue what heimdall works with this combo or if there's another way on a Mac. I have Win7 in a virtual machine, but Android never mounts in a VM or at least I've never gotten an Android to do so all these years.
I got this error when I try to download the .pit file:
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
Click to expand...
Click to collapse
Any ideas?
The device I try to root it's a Tab3 7.0 SM-T211 with Android 4.1.2
This method doesn't work for me either.
I'm on Ubuntu 14.04 and using Heimdall 1.4.0.2
I've tried uploading TWRP 2.6.3, 2.7.0 and 2.7.1
I've tried using ADB too, but to no avail. It seems that the only mode I can get ADB to work is sideload, but when I sideload images it says signature failed. I'm starting to hate this phone.
EDIT: Somehow, after 12 attempts, it worked!!! (with TWRP 2.7.1 flashable recovery)
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.
Hi, just got my note 4 3 days ago and I'm not new to rooting, however I can not get Odin to recognize, I've tried several Odin versions, 3 computers and 4 cables. I also just finished the last update to PL1 today. What gives, I need trwp to root, not unless there's an adb method.
ddarkone said:
Hi, just got my note 4 3 days ago and I'm not new to rooting, however I can not get Odin to recognize, I've tried several Odin versions, 3 computers and 4 cables. I also just finished the last update to PL1 today. What gives, I need trwp to root, not unless there's an adb method.
Click to expand...
Click to collapse
Install samsung usb drivers.
If you already have installed then uninstall them and install new again then reboot pc.
See if it fix the issue
I've tried that, thanks for the suggestion
ddarkone said:
I've tried that, thanks for the suggestion
Click to expand...
Click to collapse
Cheap hackers number one attack is to uninstall drivers. Once you get rooted I suggest you chown your USB settings to no where. I have to reinstall by samsung drivers before I use Odin every time. There's some great apps like pdanet that will fix your windows drivers but in some cases to well. You basically got a debugging bridge for the world. As far as the drivers in your note the scam is to get you to pay for remote help. I chowned the drivers in it and it's good but I can't get them to let up on my son's S4. Here's the trick - it they don't stay inactive in recovery or dl mode. When you boot into dl they default disable (this may even be Samsung). Pull the battery and wait for about 30 seconds - replace the battery and boot straight to dl. This works for me every time.
Sent from my SM-N910P using Tapatalk
---------- Post added at 02:38 AM ---------- Previous post was at 02:32 AM ----------
ddarkone said:
I've tried that, thanks for the suggestion
Click to expand...
Click to collapse
Sorry if this is redundant, I can't see that my first reply posted. To get your usb too work in DL mode you have to give it a cooling period from the time you shut it of. The more I think off it it is a samsung thing on new firmware. All though when it happens too me I always get a link from people wanting money to fix it. Pull the battery, wait 30 seconds then boot straight to dl = volume down + home + power. The USB resets after the cool down.
Sent from my SM-N910P using Tapatalk
ddarkone said:
I've tried that, thanks for the suggestion
Click to expand...
Click to collapse
Are you using stock usb cord? I've heard of people having problems with cheap cords.
finally, got it just now, I have never went through this before, I had to remove driver and disable driver about 8 times, and Odin finally did it's thing for me. Now to get rid of those ads!, thanks
ddarkone said:
finally, got it just now, I have never went through this before, I had to remove driver and disable driver about 8 times, and Odin finally did it's thing for me. Now to get rid of those ads!, thanks
Click to expand...
Click to collapse
It has been getting way bad for my Note 4 S4 and puter. My S4 got so it wouldn't even charge after cold boot. If I didn't have extra batteries and a wall charger I probably would have never figured it out. My pc updated to a invalid copy of sevice pack one and when I plugged my note in to it a note popped up saying this device can not communicate with the device it is connected to. It said that you have to make windows like Mac for it to work right and a bunch of other absuuird stuff. It gave me a link to androidfilesystems.com and said I'll find it there. I downloaded a package called android drivers to check it out. This app says you have to fet your ADB drivers for windows from your android. I was lauging my ass the whole time but I had to check it out. This app opens and it prtends to be pulling stuff from your device. Once out it tries to install and then says it failed becuase my device has been tampered with but they can fix it for me remotely for $200. It seems to have come with stalk firmware from SamM##### They haven't been watching me as closely as I thought. Because the would have noticed the APK decompiler the PDAnet (which has a straight awesome ADB for windows driver. The fast ADB, the android SDK and all of the other things that show that not only do I know windows drivers don't come from android, I will also be taking their app apart to figure out if they are infecting me worse. I pulled it a part and it does have a pretty good driver package for windows and the only malice had to come pre installation and the lie about what they are doing. I still have the apk. it gves me a good laugh when I'm down.
If you had this issue it will persist. Your going to have to fix your driver issues every time you adjust your firmware, unless your straight change all of it. The first step is to not install busy box. A couple of apps will refuse to try but for the most part will run better. It makes way to many sym links to ever break them all. Another is in recovery use the terminal to go to /sbin/recovery chmod the dev files and then chown the usb file -Rwith -L. They are all ready set. There is no reason for it to be sym linked other than for malicious outsiders to turn it off. When you go to sbin you are going to notice TW home has been given down load capabilities and crypto files. Neither of those serve a purpose for the user. I don't know how to break the download on the tw other than to freeze and/or uninstall it and use a differnt driver. You can lose the crypto files with chmod 0755 and cmd wipe_data_crypto. Good luck.