Related
OK for start i rooted my gs2 and installed cm9 update-cm-9-20120416-SNAPSHOT-epic4gtouch-alpha3-signed. this loaded and was running just fine. but then I noticed when trying to install update-cm-9-20120512-NIGHTLY-galaxys2-signed i had lost my cwm recovery and decided to investigate and experiment.(got an answer on bold issue) (bad Idea) So then I re flashed cwm recovery and loaded cm9 5/12 it loaded but i had no data/WiFi so i booted back into cwm recovery and formatted everything (i think this is were i messed up). I can still get into down loader but now my computer and Odin wont recognize when I connect my phone. I can get into cwm recovery but it cant mount my SD card and says there is nothing in internal storage. I have uninstalled kies and all Samsung related drivers/software. rebooted computer, reinstalled kies and software and still nothing.Any help would be great and any more information needed I will do my best.
So now, that is about everything I can think of. So I guess my main question would be How do I get my phone and computer to talk to each other again and most of all get it back up and running.
Also just for the record im not a complete noob I was a ROM addict with my transform. and I have searched forum after forum and have had no luck finding the info i need. which is why i am creating a new post.
yeehaw1130 said:
OK for start i rooted my gs2 and installed cm9 update-cm-9-20120416-SNAPSHOT-epic4gtouch-alpha3-signed. this loaded and was running just fine. but then I noticed when trying to install update-cm-9-20120512-NIGHTLY-galaxys2-signed i had lost my cwm recovery and decided to investigate and experiment.(got an answer on bold issue) (bad Idea) So then I re flashed cwm recovery and loaded cm9 5/12 it loaded but i had no data/WiFi so i booted back into cwm recovery and formatted everything (i think this is were i messed up). I can still get into down loader but now my computer and Odin wont recognize when I connect my phone. I can get into cwm recovery but it cant mount my SD card and says there is nothing in internal storage. I have uninstalled kies and all Samsung related drivers/software. rebooted computer, reinstalled kies and software and still nothing.Any help would be great and any more information needed I will do my best.
So now, that is about everything I can think of. So I guess my main question would be How do I get my phone and computer to talk to each other again and most of all get it back up and running.
Also just for the record im not a complete noob I was a ROM addict with my transform. and I have searched forum after forum and have had no luck finding the info i need. which is why i am creating a new post.
Click to expand...
Click to collapse
First question, which version of CWM were you using?
Second question, when you say that your computer didn't respond is it just not reading as an extra drive? If you have your sound on does the computer make the new hardware detected ding sound?
Looks like you flashed the intl version galaxy s2 cm9, this phone is usually listed as e4gt or epic touch in rom files not galaxy 2 so more than likely your USB is corrupted and no longer will be recognized by your PC which makes your phone FUBAR
Sent from my SPH-D710 using xda premium
thanks for the speedy response. I am using cwm 5.5.0.4 and No noise at all. The computer ain't regerstering that i plugged any device in via usb. I tryed different cords and nothing. I did try different usb devices to ensure it wasnt my usb and they worked just fine. it was working not a problem then what ever i did to my phone it stopped. My internal storage says there are no files. dont remember if i mentioned that before.
yeehaw1130 said:
thanks for the speedy response. I am using cwm 5.5.0.4 and No noise at all. The computer ain't regerstering that i plugged any device in via usb. I tryed different cords and nothing. I did try different usb devices to ensure it wasnt my usb and they worked just fine. it was working not a problem then what ever i did to my phone it stopped. My internal storage says there are no files. dont remember if i mentioned that before.
Click to expand...
Click to collapse
K. Unfortunately it is a hard brick. You will probably need to look at getting a JTAG service. Other than that it's pretty much gone.
Sorry!
Yup you flashed a rom for the intl gs2, next time read a little more carefully anything with gs2 or galaxy s2 is not for the epic touch. 2 completely different devices and anything for the galaxy s2 will Bork the epic touch. Jtag is your only hope, and I'm pretty sure it can fix your version of a brick since it can still boot. I wouldn't try doing anything else cuz if you get the blue light of death there is no hope aside from getting it replaced at that point. Mobile tech videos website will have more info on jtag for you, it'll cost around $50
Sent from my SPH-D710 using xda premium
thank you I will go drop it in a bucket of water and get insurance claim on it. thank you for the help
Just take it to Sprint and play dumb! Seems like a lot of folks are getting them replaced for free or 35 bucks tops.
I can try that to I actually tried zapping it with a 6.5mill volt tazer with a wire ran in through usb port but didnt work haha. Only issue I see is you can still boot to recovery and download and recovery is cwm recovery. I was trying to figure out how to just fry the motherboard and then play dumb.
yeehaw1130 said:
thank you I will go drop it in a bucket of water and get insurance claim on it. thank you for the help
Click to expand...
Click to collapse
Jtag is cheaper than ins deductible and if they can't fix it the refund your money so I'd give it a shot first
Sent from my SPH-D710 using xda premium
I would not drop it in a bucket of water!!! When you take it to sprint the first thing they do is check for water damage. They know because there are stickers on the inside of the phone that change colors when they come in contact with water. Trust me, I know.
I accidentally flashed ktoonsez i777 rom on my i747 in a hurry to do so and when it aborted, I realized it was wrong. Not thinking about it, I just restarted from cwm because usually when it aborts, it just reverts. Now my phone does nothing. I was able to aquire the drivers for the mode it is in when it's bricked and it detects it, but odin sees nothing. It says its on COM10 in device manager. I think it was qhusb or something. Anyway, it is not an unknown device anymore and I have read all about this and how everyone does jtag, but is there any software that CAN detect the phone to add any kind of files? I read that somebody was able to find some software to detect it, but this was one person. Any help would be appreciated and I'm sorry for possibly going on a sore topic again, but I REALLY would rather not send this to jtag if I can help it.
Can you get into download mode?
Sent from my SGH-I747 using xda app-developers app
This is his buddy, no he can't. Phone is in some other mode, and unresponsive.
Sent from my Galaxy Nexus using Tapatalk 2
RicoStang said:
I accidentally flashed ktoonsez i777 rom on my i747 in a hurry to do so and when it aborted, I realized it was wrong. Not thinking about it, I just restarted from cwm because usually when it aborts, it just reverts. Now my phone does nothing. I was able to aquire the drivers for the mode it is in when it's bricked and it detects it, but odin sees nothing. It says its on COM10 in device manager. I think it was qhusb or something. Anyway, it is not an unknown device anymore and I have read all about this and how everyone does jtag, but is there any software that CAN detect the phone to add any kind of files? I read that somebody was able to find some software to detect it, but this was one person. Any help would be appreciated and I'm sorry for possibly going on a sore topic again, but I REALLY would rather not send this to jtag if I can help it.
Click to expand...
Click to collapse
Huh? You flashed Ktoonsez's i777 rom? he doesn't have an i777 rom. you mean you flashed his kernel onto this device or what? If you flashed aokp for the i777 then you would be referring to me then. Still unsure what you are talking about flashing so I can't help you out until i know.
NickS_ said:
This is his buddy, no he can't. Phone is in some other mode, and unresponsive.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What is this other mode? Open task manager and close everything related to Kies before trying Odin.. see if that helps at all
task650 said:
Huh? You flashed Ktoonsez's i777 rom? he doesn't have an i777 rom. you mean you flashed his kernel onto this device or what? If you flashed aokp for the i777 then you would be referring to me then. Still unsure what you are talking about flashing so I can't help you out until i know.
Click to expand...
Click to collapse
I'm apologize. I used to mod the hell out of my old Motorola's before smartphones were mainstream, but I'm new to this again. I flashed his aokp for the i777. I had the 11/4 version for the i747 and I saw that something came out more recently for the aokp so I went to flash that and saw that it was the i777 version when I looked at the file after it aborted and figured I could reboot and it would work. This is when absolutely nothing happened. I accidentally did this same thing with the i747 version on my girlfriends SII and once I saw that it was the wrong version, it just reverted upon reboot which is why I thought it would do the same for me. I know you guys don't make guarantees and it was my fault. I love this aokp and I'll still use it. I'm just a bit upset that I hard bricked because I don't want to have to send my phone out to be jtagged. I can't get it into download mode and I heard on several posts that USB jigs wont work on this phone for forcing it unless the phone isn't bricked (which is kind of useless if you ask me). After this all happened, it came up in windows as QHSUSB_DLOAD as unrecognized. After searching for a while, I found and installed drivers and it now recognizes it, but it wont come up as a device in ODIN. I'm assuming I'm kind of screwed here I'd really appreciate any help or advice other than to return it. I understand I may have to do that, but I'm looking for a solution here. I see that this has happened with a lot of GS3's for various reasons and I'm surprised there isn't a fix yet. Thanks in advance for help.
Update! I'm not sure if this means anything or not, but I have QPST running and the phone is on COM11 and it is detecting it in download mode. Once again, ODIN, will not read this, but QPST is. It is asking me for a phone image to flash in the form of a .hex .hxb .pbn .bin. or .mbn
I can't do much in this software because I'm in QPST download mode, but it looks like it will allow me to flash files with these extensions. Not sure if this matters, but I'd love to find a solution to this bricking issue to save people the money of having to send a phone out or hassle insurance returns and having to run over a poor GS3 with a car to "accidentally break" it. Does anyone have files like this that I can flash?
Alright I got some .mbn files and one .bin using 7zip extracting from a stock rom. On the .bin when I try to flash it, I get "Use the phone's UI to switch it to streaming download mode" and NAK: invalid address when attempting the .mbn flash. I'm getting a bit discouraged again. The only area I can use is "software download" because I can't do anything else with the phone. I'm going to sleep though. Hopefully there will be some insight in the morning. Glad I have developers here!
Follow this thread, though it's mainly about msm8660 for now: http://forum.xda-developers.com/showthread.php?t=1914359
RussianBear said:
Follow this thread, though it's mainly about msm8660 for now: http://forum.xda-developers.com/showthread.php?t=1914359
Click to expand...
Click to collapse
Thanks!
RicoStang said:
I accidentally flashed ktoonsez i777 rom on my i747 in a hurry to do so and when it aborted, I realized it was wrong. Not thinking about it, I just restarted from cwm because usually when it aborts, it just reverts. Now my phone does nothing. I was able to aquire the drivers for the mode it is in when it's bricked and it detects it, but odin sees nothing. It says its on COM10 in device manager. I think it was qhusb or something. Anyway, it is not an unknown device anymore and I have read all about this and how everyone does jtag, but is there any software that CAN detect the phone to add any kind of files? I read that somebody was able to find some software to detect it, but this was one person. Any help would be appreciated and I'm sorry for possibly going on a sore topic again, but I REALLY would rather not send this to jtag if I can help it.
Click to expand...
Click to collapse
When i got hardbricked i sent it to samsung got it fixed completly i obviously had to pay cuz there were scratches on it but u could probably get away with it blaming a samsung software update and get it fixed for free
I like that lol. I didn't even think of that method. I am kicking myself repeatedly for not getting insurance so I could just run over the damn thing!
RicoStang said:
I like that lol. I didn't even think of that method. I am kicking myself repeatedly for not getting insurance so I could just run over the damn thing!
Click to expand...
Click to collapse
That's how I feel right about now haha
RicoStang said:
I accidentally flashed ktoonsez i777 rom on my i747 in a hurry to do so and when it aborted, I realized it was wrong. Not thinking about it, I just restarted from cwm because usually when it aborts, it just reverts. Now my phone does nothing. I was able to aquire the drivers for the mode it is in when it's bricked and it detects it, but odin sees nothing. It says its on COM10 in device manager. I think it was qhusb or something. Anyway, it is not an unknown device anymore and I have read all about this and how everyone does jtag, but is there any software that CAN detect the phone to add any kind of files? I read that somebody was able to find some software to detect it, but this was one person. Any help would be appreciated and I'm sorry for possibly going on a sore topic again, but I REALLY would rather not send this to jtag if I can help it.
Click to expand...
Click to collapse
So, I know this is basically a dead post... but I was wondering if you ever found the solution to this issue? I am experiencing basically the same thing with my i747. Luckily, I purchased a cheap HTC Inspire off of Ebay to use for the time being, but I feel like I am seriously on the brink of figuring this out and its driving me mad. If you did have any luck, I'd love to hear about it!
Ok, I have spent a really long time figuring out where to post this, but I still can't figure it out. Please forgive me if this is the improper place.
Please mind that I have looked at similar hard vs soft brick threads, and tried all of the advice given, but nothing has worked yet.
To start, I have a Samsung Galaxy S II from Sprint. The Epic 4G Touch, Model SPH-D710. I am on a MacBook Pro running 10.7.5 OSX. Recently, I followed the steps as listed by h tt p:// epic4gtouchroot .com /epic-4g-touch-root/ how-to-root-epic-4g-touch-on-mac-or-linux/
The Terminal went through the entire process and said it was successful. I thought 'Wow! That was easy!' However, upon rebooting my phone, it never booted past the splash screen which showed "Samsung Galaxy SII GT-I9100" with a yellow triangle at the bottom. At this point I could access Download mode, Recovery mode, this splash screen, and the charging battery that is shown when it is charging and powered off.
I was so confused so I spent about 3 hours on xda looking for an answer. Next, I downloaded Odin and packaged it for Mac. Then I downloaded the Samsung drivers just in case, and the stock ROM for my particular phone. I went through and tried to use Odin. Much to my dismay, Odin would not recognize my phone at all.
So then, I downloaded a .zip file containing the Official Samsung ROM, and put it on my internal sdcard. Under ClockworkMod, I wiped cache, dalvik cache, and wiped all user data. Then, I applied the .zip file using the option in CWM, and it said that it was successful. However, upon rebooting, it went back to the same screen with the yellow triangle.
Next, I downloaded the CF root, and tried to apply it the same way through CWM. Again a fail. However, now upon rebooting to splash screen, it would progressively turn from a black/gray screen to a white screen. Once it got to the white screen, it stopped and stayed there for about an hour. Then it died.
I tried to boot to Download mode but it says that the battery is too low. So now I am trying to charge it. However, it tries to load the charging battery icon that is normally shown when charging a powered off phone, and flashes to black. From this black screen it again slowly turns gray then white. Once it reaches the white screen, it turns back to the charging icon, and starts the stupid cycle over again. Its been doing that for the past 30 minutes.
UPDATE: My battery is not charging AT ALL. Whether plugged in to computer or wall it continues the cycle.
UPDATE 2: I made a video so that you can see what the phone actually does. I still can't post links, so please remove the spaces. http :// youtu .be /4LW60EknFWw
Remove the battery first, then try charging it. After, get windows onto your Mac or borrow a friend's, and use the windows Odin to get back to stock.
Sent from my SAMSUNG-SGH-I747 using xda premium
christykientzler said:
Ok, I have spent a really long time figuring out where to post this, but I still can't figure it out. Please forgive me if this is the improper place.
Please mind that I have looked at similar hard vs soft brick threads, and tried all of the advice given, but nothing has worked yet.
To start, I have a Samsung Galaxy S II from Sprint. The Epic 4G Touch, Model SPH-D710.
<snip>
Click to expand...
Click to collapse
You're in the wrong forum. This is currently posted in the i9100 forums. You want the Epic 4G Touch forum.
EDIT to add:
To clarify - the Epic 4G Touch is a CDMA phone, and the GT-I9100 is a GSM phone which doesn't even work on Sprint's network.
So according to this:
christykientzler said:
Recently, I followed the steps as listed by http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/
The Terminal went through the entire process and said it was successful. I thought 'Wow! That was easy!' However, upon rebooting my phone, it never booted past the splash screen which showed "Samsung Galaxy SII GT-I9100" with a yellow triangle at the bottom. At this point I could access Download mode, Recovery mode, this splash screen, and the charging battery that is shown when it is charging and powered off.
Click to expand...
Click to collapse
You apparently flashed something for the GT-I9100 onto your Epic 4G Touch SPH-D710. If you actually did follow the steps at http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/ properly, this should not have happened. What exactly did you download and flash? Because if you followed steps for an Epic 4G Touch, then you would not have downloaded and flashed something that would alter your bootscreen to read GT-I9100.
You MIGHT have been at a recoverable spot at this point, until:
christykientzler said:
So then, I downloaded a .zip file containing the Official Samsung ROM, and put it on my internal sdcard. Under ClockworkMod, I wiped cache, dalvik cache, and wiped all user data. Then, I applied the .zip file using the option in CWM, and it said that it was successful. However, upon rebooting, it went back to the same screen with the yellow triangle.
Next, I downloaded the CF root, and tried to apply it the same way through CWM. Again a fail. However, now upon rebooting to splash screen, it would progressively turn from a black/gray screen to a white screen. Once it got to the white screen, it stopped and stayed there for about an hour. Then it died.
Click to expand...
Click to collapse
By my count, that's you flashing 3 things meant for an GT-I9100 to an SPH-D710.
You're probably out of luck at this point, but again, check in the Epic 4G Touch forum. Maybe someone there can help you, but I wouldn't hold my breath. You might have some luck trying to get a warranty exchange at a Sprint store, if they can't get your phone to boot and see exactly how bad you buggered it. But I wouldn't hold my breath on this, either.
Oh my goodness...
ctomgee said:
You're in the wrong forum. This is currently posted in the i9100 forums. You want the Epic 4G Touch forum.
EDIT to add:
To clarify - the Epic 4G Touch is a CDMA phone, and the GT-I9100 is a GSM phone which doesn't even work on Sprint's network.
So according to this:
You apparently flashed something for the GT-I9100 onto your Epic 4G Touch SPH-D710. If you actually did follow the steps at http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/ properly, this should not have happened. What exactly did you download and flash? Because if you followed steps for an Epic 4G Touch, then you would not have downloaded and flashed something that would alter your bootscreen to read GT-I9100.
You MIGHT have been at a recoverable spot at this point, until:
By my count, that's you flashing 3 things meant for an GT-I9100 to an SPH-D710.
You're probably out of luck at this point, but again, check in the Epic 4G Touch forum. Maybe someone there can help you, but I wouldn't hold my breath. You might have some luck trying to get a warranty exchange at a Sprint store, if they can't get your phone to boot and see exactly how bad you buggered it. But I wouldn't hold my breath on this, either.
Click to expand...
Click to collapse
Oh my goodness... I knew I really had screwed the pooch on this one D:
Thanks for letting me know that I really am in a world of trouble. I had thought that GT-I9100 was a type of SPH-D710.
Also I apologize for the incorrect post location. Again, I hadn't understood the difference.
Do you think if I could charge up the battery, and get it into download mode with a jig, I might be able to use OneClick UnBrick? Or some other method?
christykientzler said:
Oh my goodness... I knew I really had screwed the pooch on this one D:
Thanks for letting me know that I really am in a world of trouble. I had thought that GT-I9100 was a type of SPH-D710.
Also I apologize for the incorrect post location. Again, I hadn't understood the difference.
Do you think if I could charge up the battery, and get it into download mode with a jig, I might be able to use OneClick UnBrick? Or some other method?
Click to expand...
Click to collapse
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
TLDR
There is no such thing as a "Soft" or "Hard" brick, Your device is either bricked or it isnt, simple as that.
If you can get into download or recovery and use them your device is not bricked.
Will do
ctomgee said:
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
Click to expand...
Click to collapse
Ok :good: Will do. I was wondering what I'd tell them if I went to a Sprint store Thanks again.
TheATHEiST said:
TLDR
There is no such thing as a "Soft" or "Hard" brick, Your device is either bricked or it isnt, simple as that.
If you can get into download or recovery and use them your device is not bricked.
Click to expand...
Click to collapse
Lol?
Softbrick is corrupted system files which result in a bootloop.
Hardbrick is a dead phone that can be fixed with a Jtag or M/B replacement...
Sent from my GT-I9100
Again, there is no such thing as a "soft brick". There is just "bricked" and the term is used too loosely by n00bs.
If you can simply re-flash a rom your device is not bricked at all.
"Soft brick" is just a n00b term that is used because they think their device is bricked if they can't get it to boot.
Your device is only "bricked" if all you can do is JTAG or mobo replace.
Sent from my GT-I9100 using xda premium
ctomgee said:
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
Click to expand...
Click to collapse
boki9999 said:
Lol?
Softbrick is corrupted system files which result in a bootloop.
Hardbrick is a dead phone that can be fixed with a Jtag or M/B replacement...
Sent from my GT-I9100
Click to expand...
Click to collapse
Is there a one-stop resource for "Jtag or M/B replacement"? I'm having trouble searching forums for some reason, otherwise I would look for it myself.
You need to get it into download mode and then reflash a ROM appropriate for your device. Your phone isn't bricked - but if you fail to get it working again and have to resign to using it purely as a surface to sniff your cocaine off, then you have only yourself to blame.
postfatal said:
You need to get it into download mode and then reflash a ROM appropriate for your device.
Click to expand...
Click to collapse
Thank you, will do.
postfatal said:
Your phone isn't bricked - but if you fail to get it working again and have to resign to using it purely as a surface to sniff your cocaine off, then you have only yourself to blame.
Click to expand...
Click to collapse
LMAO, that's true. I don't blame anyone but myself for my mistakes.
If you hadnt understood the difference then why did you decide one day to go I to your phone and per form operations that are completely unknown to you? Do you ipen up your cars engines and place honda parts into your ford Fiesta?
Sent from my SGH-T889 using Tapatalk 2
Curiousity killed the cat...
ssCISengineer said:
If you hadnt understood the difference then why did you decide one day to go I to your phone and per form operations that are completely unknown to you? Do you ipen up your cars engines and place honda parts into your ford Fiesta?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Because I am curious. This is where it often times gets me, but I like to learn new things by doing. In my eyes it's usually worth the risk. I will admit this was a stupid mistake, but I have certainly learned a lot about rooting in the process
Wow. So, hopefully by now you are in the correct forum. And hopefully have downloaded the appropriate Odin tar file to restore your phone properly. Get that at the dev section of E4GT. Charge that battery in a different phone if you have to. Get into Odin mode and run Odin from a PC (Heimdall for macs?), if the PC does not recognize your phone, its probably the cable. If Odin starts but then fails half way through, its probably the cable. BTW, check out SFHubs Odin-one clicks for your phone, probably the easiest way to restore a clean, new rom.
And in the future, be more curious before you act. Read read read.
Good luck.
Thank you
Dr. Fed said:
Wow. So, hopefully by now you are in the correct forum. And hopefully have downloaded the appropriate Odin tar file to restore your phone properly. Get that at the dev section of E4GT. Charge that battery in a different phone if you have to. Get into Odin mode and run Odin from a PC (Heimdall for macs?), if the PC does not recognize your phone, its probably the cable. If Odin starts but then fails half way through, its probably the cable. BTW, check out SFHubs Odin-one clicks for your phone, probably the easiest way to restore a clean, new rom.
And in the future, be more curious before you act. Read read read.
Good luck.
Click to expand...
Click to collapse
Yes I got to the correct forum.I still don't know which file to download. Nobody has bothered to point me in the right direction. Considering what I did to it last time with what I thought was the correct file, any direction would be appreciated. :/ I'll definitely ask in the E4GT forums. I'm currently working on getting a charged up battery, but I won't be able to do so until next Friday. I've looked into OneClick UnBrick. When I get the charged battery, I will definitely use a more reliable cord. XP I will definitely research more next time. In fact I might not mess with it at all!
Thank you for your help!
christykientzler said:
Yes I got to the correct forum.I still don't know which file to download. Nobody has bothered to point me in the right direction. Considering what I did to it last time with what I thought was the correct file, any direction would be appreciated. :/ I'll definitely ask in the E4GT forums. I'm currently working on getting a charged up battery, but I won't be able to do so until next Friday. I've looked into OneClick UnBrick. When I get the charged battery, I will definitely use a more reliable cord. XP I will definitely research more next time. In fact I might not mess with it at all!
Thank you for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1903252
If you can get into Odin mode (on a PC preferably) , download one of these files. I recommend the latest official ICS build. Read the op carefully. That will return you back to stock. All your data is gone,, but hopefully you've always backed up your contacts to Google. The play store will have your app history.
Wait what..?
Dr. Fed said:
http://forum.xda-developers.com/showthread.php?t=1903252
If you can get into Odin mode (on a PC preferably) , download one of these files. I recommend the latest official ICS build. Read the op carefully. That will return you back to stock. All your data is gone,, but hopefully you've always backed up your contacts to Google. The play store will have your app history.
Click to expand...
Click to collapse
I see that the latest is FI27. The three files shown are OneClick.exe, a zip file, and an unrooted TAR file. From those I'm assuming that OneClick.exe is a windows application that goes in and puts your phone back to the ICS build with one click? This method would be the simplest, except for the fact I have a Mac. Would the time taken to repackage it be worth it or would one of the other two options be better? And the zip file. Would I be able to put that on my internal SD card and flash it through CWM? Or would I unzip it and flash through heimdall. As for the TAR file, I am unfamiliar with this, and am not sure how this file would be utilised.
The last time I tried to understand a concept on my own, I ended up with a bricked phone so please forgive me for asking so many questions, I just don't want to mess it up a second time.
As for the data, yes it is gone. DX Yes I backed up contacts *phew*. I had a feeling going into this that I should back up something.
christykientzler said:
I see that the latest is FI27. The three files shown are OneClick.exe, a zip file, and an unrooted TAR file. From those I'm assuming that OneClick.exe is a windows application that goes in and puts your phone back to the ICS build with one click? This method would be the simplest, except for the fact I have a Mac. Would the time taken to repackage it be worth it or would one of the other two options be better? And the zip file. Would I be able to put that on my internal SD card and flash it through CWM? Or would I unzip it and flash through heimdall. As for the TAR file, I am unfamiliar with this, and am not sure how this file would be utilised.
The last time I tried to understand a concept on my own, I ended up with a bricked phone so please forgive me for asking so many questions, I just don't want to mess it up a second time.
As for the data, yes it is gone. DX Yes I backed up contacts *phew*. I had a feeling going into this that I should back up something.
Click to expand...
Click to collapse
The one clicks are full "images" flashed through Odin. I recommend this because a one click will reflash your stock rom, modem, and recovery partition. This is what you need to do to repair your phone. If you try to flash something in recovery, it will repair your rom but not necessarily your modem/radio/firmware, and this could be a problem. I'm not sure exactly what you flashed before, so I think its best if you fix it all with a One Click.
As far as using a Mac goes, I am not sure. I'll look into it, you should too. Odin used to be only for PCs, Heimdall for Macs. Maybe its changed now?
---------- Post added at 08:30 PM ---------- Previous post was at 08:19 PM ----------
You must have some schmo friend that will let you borrow his or her PC laptop for 10 minutes. Install Odin , install the proper drivers. Go into Odin mode, connect phone, once recognized... click.
Look up QBKing77 on YouTube, search on YouTube "QBking77 Epic 4g Touch" and you will see instructional videos with appropriate download links.
Why have you lot continued to answer this thread ? It's in the wrong place. More to the point, why hasn't anyone asked mods to move it to Epic 4G Q&A ? (Which I've just done)
Hi,
A friend of mine just gave me his Epic 4G touch to diagnose and fix.
He had gingerbread, I think. He first rooted it and then ended up upgrading to some ICS custom ROM through odin, did it wrong (used an AT&T GSII rom... haha). Anyway, now the phone is stuck in a boot loop. I can access recovery and download mode. Unfortunately, recovery mode refuses to mount the external SD card when I go to install a package, so I can't fix this easily. ADB through recovery doesn't seem to work either. In download mode, the phone is not detected by any of my 2 PCs using any version of kies, mini or not. In fact, there isn't even an "unknown device" that shows up. It's like I have zero communication with it.
I've reformatted the SD several times and tried different SDs. No luck.
I know my cable is good and I know the micro USB port is good, as it worked for him to install this and still charges the phone just fine.
Any ideas? Where should I go from here?
Thanks!
To the sprint store to get a new phone...
It seems that when people flash stuff from a different phone, it screws everything and makes it almost impossible to fix. You may try a Jtag repair... Find mobiletechvideos in Google.
And questions go in Q/A, not general.
Sent from my SPH-D710 using xda premium
graydiggy said:
To the sprint store to get a new phone...
It seems that when people flash stuff from a different phone, it screws everything and makes it almost impossible to fix. You may try a Jtag repair... Find mobiletechvideos in Google.
And questions go in Q/A, not general.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Jtag will work in this case. The bootloader is just borked so jtag can force the proper one to write. :thumbup:
☆SoA: Son's of Android™☆
I like to break stuff!
Try this since you can still access recovery, [edit] oh this might not work since you need adb also working
http://forum.xda-developers.com/showthread.php?t=1865102
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.