Related
Was on my phone when it froze, I hard rebooted (held power) now it wont turn on, and the led doesnt indicate its charging. Thoughts?
Stock, rooted, ROM, recovery, ect....?
Help us help you
Same exact thing happened to me recently. I had to get my device switched out. Apparently a partition got corrupted and the phone was in diagnostic mode and I couldn't recover it.
Sent from the Shadows.
baseballfanz said:
Stock, rooted, ROM, recovery, ect....?
Help us help you
Click to expand...
Click to collapse
Rooted running Trickdroid 6.2 & TWIRP
i was worried I might have to switch it out. I hope they still have S4 versions.
Co worker had a similar problem on a hox after she dropped it. Wouldn't turn on or have charging light indicator. Reseated the micro sim card and it came back on. Go figure...
Sent from my HTC VLE_U using xda premium
If your problem is TO access to sd-card try this guide
http://forum.xda-developers.com/showthread.php?t=1630459
Sent whit HTC ONE S
removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.
familiarstranger said:
removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.
Click to expand...
Click to collapse
This just happened to me running the same rom and custom recovery. I even created a thread... I hope you and I aren't in the same boat.
http://forum.xda-developers.com/showthread.php?p=29276808#post29276808
Might be in a sleep of death. Plug it into a computer and see if it enumerates as QHUSB_DLOAD.
I too have this problem but am really looking to avoid exchanging it. Any other options?
familiarstranger said:
removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.
Click to expand...
Click to collapse
I'm assuming you really meant your Micro SIM? Anyways also check if fastboot recognizes it with fastboot devices, then you can try fastboot booting a recovery. If you have to have it replaced and get an S3 I've read that HTC will replace with the S4 if you complain, have no source for this though.
yes I meant Micro SIM. No luck with fastboot. I am going the repair route with HTC. Does anyone have experience with this? what is the turnaround like?
frdd said:
I'm assuming you really meant your Micro SIM? Anyways also check if fastboot recognizes it with fastboot devices, then you can try fastboot booting a recovery. If you have to have it replaced and get an S3 I've read that HTC will replace with the S4 if you complain, have no source for this though.
Click to expand...
Click to collapse
familiarstranger said:
yes I meant Micro SIM. No luck with fastboot. I am going the repair route with HTC. Does anyone have experience with this? what is the turnaround like?
Click to expand...
Click to collapse
It can get pretty bad, it can be just fine. Don't return it unless it registers as QHUSB_DLOAD mode on USB, because that's the only time your phone is really dead.
I think I'm lucky...
A colleague of mine returned his, as he had the same with his One S. However he was running Trickdroid 5.2, so I don't really think Trickdroid is the point here....though he was also running the Tweaks (which do little to governing which could be a cause, not the removal of stock apps).
I have been running 6.2 for a week or so now and haven't found any worry....did have to reflash it (as I accidentally installed Tweaks, causing it to bootloop).
My colleague did say he was deinstalling Ice Age 3 game...but guess that was nothing similar.
I have seen that most people, who are running trick droid, are getting bricked devices. Chances are there that there must a minor glitch or problem in the rom that might cause the devices to become bricked.
Sent from my icecreamed Xperia Arc S
HTC warranty states I had water damage. I dont ever remember getting my phone wet, but they sent me pics that supposedly show it. The repair quote was $325. I got the phone back today, so I'll be taking it apart and see if i cant fix it....
Can you help me. My one s villec2 , unlock bootlader ok, but when flash Recovery battery low and off phone, i change battery but can not go to fastboot.
Sent from my HTC One S using Tapatalk 2
So using TWRP I flashed my clearROM and went through the installation, all seemed to go well. Once done I clicked reboot in TWRP and then my phone didn't reboot. At this point it was still plugged into my computer and the chargin light was on. I tried to boot it normally and the bottom three buttons flashed a few times and then nothing happened. After that the charging light disappeared. I am unable to boot it into bootloader as well.
I've had it in the wall charger for the last 20 minutes and still no charge light, I've done some searching and nothing helpful has come up so I'm wondering if anyone knows more about this,
You did nothing but flash cleanrom?
Sent from my HTC One X+ p_type 0.91.0
Sorry I should have been more detailed.
I unlocked via HTCdev, installed TWRP recovery, wiped the phone then installed cleanrom.
A little update, the red charging light came on about ten minutes ago while plugged into the computer. When I saw it was lit up, I transferred to a wall charger for 10 minutes. I then held the power button for a few seconds to try and boot it, but the red light just disappeared and now I'm back at square one.
Left it on wall charger all night, no red chargin light upon waking up. Decided to switch it to the computer USB about half an hour and will leave it there while I goto school. After seeing the red light last night I have hope!
Wall charger is better than USB. But if you left it on the wall charger overnight, I don't think you will see much difference with additional charging (regardless of wall charger vs. USB).
Can adb see the phone?
Can you confirm which variant of the One X you have? If you have the Tegra3 (International) One X and loaded a ROM for the Snapdragon S4/North American One X or vice versa then you may have bricked your phone. If you are unsure, which carrier did you get the phone from?
Got home from school and no charging light on. Tried to boot into bootloader and the red light came on. But no boot, or at least screen response. It was still plugged into the computer and no noise response from the computer. Tried to boot into bootloader again and the light turned off. Tried to boot into recovery and the light came on again, but no screen response. Then just held the power button for a normal boot and the light turned off and now it won't turn on again.
I tried to fastboot reboot-recovery and cmd hangs on waiting for device, so I don't think adb can find the device. I got the hox from Rogers Canada, and in bootloader it said evita.
I was tired last night this slipped my mind, but I installed clearkernel as well. In TWRP I selected the clearkernel zip and it flashed it, no installation. It then proceeded to flash the clearrom zip and sent me to the installation for clearrom.
gr3ener said:
Got home from school and no charging light on. Tried to boot into bootloader and the red light came on. But no boot, or at least screen response. It was still plugged into the computer and no noise response from the computer. Tried to boot into bootloader again and the light turned off. Tried to boot into recovery and the light came on again, but no screen response. Then just held the power button for a normal boot and the light turned off and now it won't turn on again.
I tried to fastboot reboot-recovery and cmd hangs on waiting for device, so I don't think adb can find the device. I got the hox from Rogers Canada, and in bootloader it said evita.
I was tired last night this slipped my mind, but I installed clearkernel as well. In TWRP I selected the clearkernel zip and it flashed it, no installation. It then proceeded to flash the clearrom zip and sent me to the installation for clearrom.
Click to expand...
Click to collapse
Leave it "on" and let the battery drain. Then plug it back up to the wall and let it charge. Maybe some funniness going in :-S
Sent from my One X using xda app-developers app
What is the on setting? When the red light is on and not plugged in?
Did you try to press the power button for 10 seconds then see if it reboot? You can do the same but with volume down button pressed and should go to the bootloader.
Sent from my HTC One X using Tapatalk 2
Holding it down ten seconds didnt work for normal or bootloader.
Here's my suspicion, I see in the international forums you had flashed one of their roms. This has been detrimental to several devices, but it seemed your device had somewhat survived it and you had bootloader and recovery access. I'm guessing, when what you needed to do from there is ruu or dd a signed Hboot to the proper partition to get it stable again, you flashed a one xl Rom which sealed your fate.
You may not have know the damage caused by flashing the incorrect Rom, and I mean no offense, simply letting you know that your phone is probably good for nothing but maybe a fancy door prop......
If you plug it into your pc and it comes up as qshusb_dload in your windows device manager, or it comes up as nothing after pressing power for 2-3 seconds it's probably toast
Sent from my HTC One X+ p_type 0.91.0
It didn't actually install the other roms though, it failed when reading build.prop, hence why my phone 'survived'. At least I'm hoping so, I'm a noob with androids right now. It checked to see my device type and I was the wrong device, so it didn't install. Isn't that what the ro checks are for?
Since you got the phone from Rogers it is definitely the North American variant, so at least you loaded a compatible ROM onto your device. If you also flashed CleanKernel, the issue might be that the kernel is overclocked by default and your device cannot handle it. When this happens it is not usually as serious as what you're experiencing, but it is entirely possible. Can you check if the CleanKernel is overclocked by default (as I'm not sure)? If it is, your #1 priority should be to flash a stock kernel. It going to be difficult given the state of your device, but if you manage to get into recovery or issue a fastboot command from your pc you might have a big enough window to do it.
---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------
Oh wait... Is "clearkernel" a kernel for the international One X? I thought it was just a typo and you mean CleanKernel, a kernel for our north American one X.
He means cleanrom I think.....
Ok, here's where I'm conflicting, I've been here on fairly active on this forum since release. I've helped several people with unbricking and a wave of other issues that have come up.......I've NOT seen 1 single one x brick from flashing any roms specific to the device. I've seen DOZENS brick from flashing kernels, roms and recoveries from the international one x. So, seeing that just 3 hrs. before opening this thread, you opened a thread in the international one x forums saying you were having problems flashing a endeavor rom and endeavor kernel. You asked for advise how to edit it so the device would accept the flash. You were then instructed you were in the wrong forum, that you had a one xl evita.
So again, 3 hours later your super bricked, and stating all you did was flash cleanrom. Cleanrom didn't brick the phone, and insinuating that it could have, without fully stating your scenario is obnoxious and flagrant. I also saw you posted in the cleanrom thread that you flashed his Rom and now your x won't turn on.......
XDA is here to help, but your purposeful lack of information, as an attempt to save self dignity and place the responsibility quietly on a brilliant Rom dev is unjust and should NOT be tolerated.
With that said, you have a $700 paperweight and noone to blame but YOURSELF.......Deal with it:beer:
Sent from my HTC One X+ p_type 0.91.0
18th.abn said:
He means cleanrom I think.....
Ok, here's where I'm conflicting, I've been here on fairly active on this forum since release. I've helped several people with unbricking and a wave of other issues that have come up.......I've NOT seen 1 single one x brick from flashing any roms specific to the device. I've seen DOZENS brick from flashing kernels, roms and recoveries from the international one x. So, seeing that just 3 hrs. before opening this thread, you opened a thread in the international one x forums saying you were having problems flashing a endeavor rom and endeavor kernel. You asked for advise how to edit it so the device would accept the flash. You were then instructed you were in the wrong forum, that you had a one xl evita.
So again, 3 hours later your super bricked, and stating all you did was flash cleanrom. Cleanrom didn't brick the phone, and insinuating that it could have, without fully stating your scenario is obnoxious and flagrant. I also saw you posted in the cleanrom thread that you flashed his Rom and now your x won't turn on.......
XDA is here to help, but your purposeful lack of information, as an attempt to save self dignity and place the responsibility quietly on a brilliant Rom dev is unjust and should NOT be tolerated.
With that said, you have a $700 paperweight and noone to blame but YOURSELF.......Deal with it:beer:
Sent from my HTC One X+ p_type 0.91.0
Click to expand...
Click to collapse
Hop off that horse of yours, I appreciate your help very much. With that being said, I didn't include the other details because as far as I know, and my device showed me, they did not install. As much as I would love to save my dignity on an anonymous online forum.
My red light is now flashing, any ideas?
gr3ener said:
My red light is now flashing, any ideas?
Click to expand...
Click to collapse
If you did install (or try to install) a ROM or kernel for the International One X onto your North American One X then the behaviour you are seeing is a telltale sign that your device has been bricked, very similar to others who have done the same.
"Guys someone please help.....I'm stuck" http://forum.xda-developers.com/showthread.php?t=1755156
"Flashed a ROM for the HTC quad core, ignorantly. Phone now non functional" http://forum.xda-developers.com/showthread.php?t=1905665
I wish you best of luck! Perhaps you can take the phone back to a Rogers store and play dumb?
I would keep it simple no custom kernel. i would ruu and test it for a day before unlocking again and flashing recovery, i know stock hurts but you needa find out if its your phone thats buggerd. then if all is good unlock again and flash recovery, then strip down stock rom to your liking and mess with it for another day or two. then if all is good try another custom rom. i would try jb aosp based rom since they are pretty stable these days.
also ruu should clear out alot of the issues that the international rom might have caused assuming the ruu is successful. i have not misflashed int rom so i dont know all the problems, but most users ive come across flashed an int rom using cwm which is no good our the evita, since you seem to be using twrp the whole time. im guessing you might still be good. also dont do any factory reset, clear storage, etc from the bootloader it fubared my phone to the point where i had to ruu.
if my post makes little sense, please pm me for i have had little sleep. sleepy time and i hope i was of some help.
DvineLord said:
if my post makes little sense, please pm me for i have had little sleep. sleepy time and i hope i was of some help.
Click to expand...
Click to collapse
It doesn't power on to any extent.........
Sent from my HTC One X+ p_type 0.91.0
Tried installing a ROM, and being the noob that I am it was an International Rom. I used TeamWin. Can't post outside links because I'm new. The rom was IceColdJelly AOKP ROM from onexroot.com
I realize I was stupid. I just want out of this situation and I'll be really careful for now on. Is my HOX a lost cause? I bought it about 2 weeks ago (Really unlucky with the whole price drop...). And now, I've done this.
I get it, I've learned my lesson. XDA please help me out. How can I fix this brick? (If it is a brick? I'm assuming.)
Epsilon707 said:
Tried installing a ROM, and being the noob that I am it was an International Rom. I used TeamWin. Can't post outside links because I'm new. The rom was IceColdJelly AOKP ROM from onexroot.com
I realize I was stupid. I just want out of this situation and I'll be really careful for now on. Is my HOX a lost cause? I bought it about 2 weeks ago (Really unlucky with the whole price drop...). And now, I've done this.
I get it, I've learned my lesson. XDA please help me out. How can I fix this brick? (If it is a brick? I'm assuming.)
Click to expand...
Click to collapse
Yes, it's a brick, but there is a fix if you have access to a Linux computer and know what you're doing.
beaups said:
when the device is bricked (qhusb mode), after pushing and holding power for ~10 seconds - in linux shortly thereafter all of the partitions will enumerate and expose themselves to linux for about 5 seconds (you'll see sdX1, sdX3, sdX8, about 30 partitions alltogether). During that quick 5 seconds you can DD whatever you feel like back to those partitions.
.
This is how I've recovered bricks. Corrupt hboot --> Brick device. DD back correct hboot while in this mode --> unbricked
Click to expand...
Click to collapse
It successfully flashed? Than yes follow his directions only way out if it successfully flashed and your device is unresponsive
omario8484 said:
It successfully flashed? Than yes follow his directions only way out if it successfully flashed and your device is unresponsive
Click to expand...
Click to collapse
Good point, if you were on stock 2.20 before, it's not bricked, you just need to get back into recovery and flash something else.
bricked
iElvis said:
Good point, if you were on stock 2.20 before, it's not bricked, you just need to get back into recovery and flash something else.
Click to expand...
Click to collapse
It was stock 2.20. I bought the phone a week or two ago. HBOOT 1.14. But the phone still won't turn on?
Epsilon707 said:
It was stock 2.20. I bought the phone a week or two ago. HBOOT 1.14. But the phone still won't turn on?
Click to expand...
Click to collapse
Can your computer see it? Was it fully charged before?
Try plugging into the charger for a while. The battery in this phone has a weird tendency to suddenly lose all its charge.
iElvis said:
Can your computer see it? Was it fully charged before?
Try plugging into the charger for a while. The battery in this phone has a weird tendency to suddenly lose all its charge.
Click to expand...
Click to collapse
Computer cannot see it. Atleast constantly. My computer makes a noise like a drive was plugged in, then shortly after an error-like similar sound.
I'll try charging it for a few hours. Thanks!
Epsilon707 said:
Computer cannot see it. Atleast constantly. My computer makes a noise like a drive was plugged in, then shortly after an error-like similar sound.
Click to expand...
Click to collapse
That's not good. What does it look in explorer like when it shows up? Do you see QHSUSB anywhere?
The new hboots won't allow flashing of an incompatible Rom. Make sure you charge it for a while hold power button and volume down for a few seconds and see if capacitive buttons flash. If so, release power button but continue to hold volume down and see what happens
Sent from my HTC One XL using xda app-developers app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Word of advice bro, don't flash anything what so ever from anywhere except xda. You'll be asking for trouble
Sent from my HTC One XL using xda app-developers app
iElvis said:
That's not good. What does it look in explorer like when it shows up? Do you see QHSUSB anywhere?
Click to expand...
Click to collapse
Nope. I'm running Windows by the way. I don't have access to a Linux computer right now, but I will later.
Epsilon707 said:
Nope. I'm running Windows by the way. I don't have access to a Linux computer right now, but I will later.
Click to expand...
Click to collapse
Okay, try what InflatedTitan suggested and see what happens.
InflatedTitan said:
The new hboots won't allow flashing of an incompatible Rom. Make sure you charge it for a while hold power button and volume down for a few seconds and see if capacitive buttons flash. If so, release power button but continue to hold volume down and see what happens
Sent from my HTC One XL using xda app-developers app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Word of advice bro, don't flash anything what so ever from anywhere except xda. You'll be asking for trouble
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Zero response. I'll keep trying.
Epsilon707 said:
Zero response. I'll keep trying.
Click to expand...
Click to collapse
Let it charge for a few hours and try again.
Still no avail. Any other ideas?
I could really use some help. Anyone have an idea or a suggestion on what to do? I also don't suppose this is covered under my warranty
Okay, a couple of questions:
-Are you certain you were on 2.20? I ask because there have been cases of people buying One Xs recently and getting phones on 1.85.
-The phone is completely unresponsive despite being plugged into an outlet (not your computer) for a couple of hours?
iElvis said:
Okay, a couple of questions:
-Are you certain you were on 2.20? I ask because there have been cases of people buying One Xs recently and getting phones on 1.85.
-The phone is completely unresponsive despite being plugged into an outlet (not your computer) for a couple of hours?
Click to expand...
Click to collapse
Yes, I am certain. I remember checking it in the About Phone section of settings.
Completely unresponsive, but I'll keep trying.
Epsilon707 said:
Yes, I am certain. I remember checking it in the About Phone section of settings.
Completely unresponsive, but I'll keep trying.
Click to expand...
Click to collapse
Okay, one last thing. Open up Device Manager in Windows and expand the whole directory tree. Check "DVD/CD-ROM devices" in particular. Plug your phone in and see what happens.
If nothing happens at all, try leaving it plugged in overnight and see if anything is different. If it's still dead, it's bricked, whatever you did with it. Since it's new, you should be able to return it and get a new one.
Idk what to say if you were on 2.20 it should of failed the Rom flash...but it successfully flashed ?
omario8484 said:
Idk what to say if you were on 2.20 it should of failed the Rom flash...but it successfully flashed ?
Click to expand...
Click to collapse
I'm f'ing baffled myself mate.
Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.
If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...
droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.
droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app
T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app
Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1
droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.
Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1
Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!
I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question