So I recently ****ed my gnex 6 ways from sunday. Im talkin no screen no dl mode no fastboot. NOTHIN, ZILTCH. When plugged into comp i get the noise over and over again as if im removing and repluggin the cord repeatedly. sometimes after 20 minutes of that it will finally show up in device manager as unknown device or OMAP440. but thats rarely and it dont stay long. Im no noob and this seems a clear cut case of a Hard Brick. But I beg of you, PLease prove me wrong. Thanks all.
Got the jig. Yup, this thing is ****ed. Probly gna send it to the big S jus to see what they gotta say. Thanks to all those who helped.
I'm pretty sure there is a usb jig that will force odin mode. If that doesn't work I think you'd be screwed. Here's a video on how to make your own jig. http://www.youtube.com/watch?v=jKRrTZayRxU
Or you can buy one already made for $5.50 US at http://usbjig.com/
What were you flashing when this happened?
a little info on how this happened can help.
Are you unlocked and rooted?
Did you drop the phone?
If you call the phone, does it ring?
In other words, is it your screen that's broken? I recently returned a rooted HTC thunderbolt with a non functioning screen back to stock to take advantage of factory warranty.
Sorry to be vauge. to clear things up;
No, Never Dropped, still looks brand new. Definately not the screen. This things a brick. And I was running a linux installer last i'd seen the phone but i had left it unattended for probably 15 mins or so. Also, heard the jig dont work on these, can anyone elaborate? Thanks
Linux installer? No, what exactly were you doing or flashing?
Thats it. Nothing else was going when i left it
billard412 said:
Thats it. Nothing else was going when i left it
Click to expand...
Click to collapse
I think he meant "What Linux installer?"
Send it to a service center and say "I downloadz app and it won't turn onz"
I can tell you that motorola was good about rooted phones being serviced, not sure about Samsung.
Sent from my francoPhone
billard412 said:
Sorry to be vauge. to clear things up;
No, Never Dropped, still looks brand new. Definately not the screen. This things a brick. And I was running a linux installer last i'd seen the phone but i had left it unattended for probably 15 mins or so. Also, heard the jig dont work on these, can anyone elaborate? Thanks
Click to expand...
Click to collapse
That wasn't much better. You need to tell us step by step exactly what you did leading up to this problem. Be specific as possible.
Sent from my Galaxy Nexus using xda premium
There's multiple reports of the Galaxy S II jig working with the Gnex. I hope this helps. There is a forum on another website I can post the link if you want with a confirmed report of the jig working.
Anyway here's the link to buy the jig $1.60 with free shipping is a pretty good deal to save a $600 phone. http://www.dealextreme.com/p/unbric...msung-t959-i9000-i897-m110s-i8700-i9100-93514
Good Luck
Other than this, w w w . androidzoom.com/android_applications/tools/linux-installer_fuxq_comments.html , the phone was doing nothing else. started the setup process walked awayfor a bit, came back and BRICK.
ChongoDroid said:
Send it to a service center and say "I downloadz app and it won't turn onz"
I can tell you that motorola was good about rooted phones being serviced, not sure about Samsung.
Sent from my francoPhone
Click to expand...
Click to collapse
and this is why we can't have nice things....
this is one of the reasons why phone companies are so against unlocking bootloaders. people screw up their rooted, unlocked phones and then send it back to vzw or the manufacturer to cover the bill.
if you're going to root your phone and mod it, then man up and accept the consequences when you derp it.
not saying the op isn't going to accept full responsibility, but your advice is what's wrong w/ some in this rooted community.
Since the linux installer is only using chroot then one would think that it is simply adding its distro to the system partition then chrooting to start. How this bricked you is puzzling. There's no flashing operation here...
I'm guessing hardware failure. The coincidence is hard to ignore though. However, you weren't there when it actually died so who knows what happened.
i was flashing stock ICS 4.0.4 with Odin and then half way through an error came up. so i removed closed Odin from the PC and tried redoing it. and then it was saying analyzing files.
and so i closed it again and restarted the phone. and what came on the screen was a sign, with a phone dots an exclamation mark dots and a monitor. i think thats when the phones bricked rite? any help?
jaadey said:
i was flashing stock ICS 4.0.4 with Odin and then half way through an error came up. so i removed closed Odin from the PC and tried redoing it. and then it was saying analyzing files.
and so i closed it again and restarted the phone. and what came on the screen was a sign, with a phone dots an exclamation mark dots and a monitor. i think thats when the phones bricked rite? any help?
Click to expand...
Click to collapse
not bricked at all mine did it
happened to me do you have version 1.85 of odin and do you have a propper version of 4.0.4
odin 1.85 here http://forum.xda-developers.com/showthread.php?t=1394051&highlight=odin+stock
the 4.0.4 version i used here http://code.google.com/android/nexus/images.html
i had the same thing on my screen and it all worked fine the second time round.. i tried for a total of 8 hours doing different things but this worked with the latest odin.
make sure you load via the pda Make sure in the ODIN program "Re-Partition", "Phone EFS Clear", and "Phone Bootloader Update" are NOT checked.
hope that works. im a total novice but worked a dream
billard412 said:
Sorry to be vauge. to clear things up;
No, Never Dropped, still looks brand new. Definately not the screen. This things a brick. And I was running a linux installer last i'd seen the phone but i had left it unattended for probably 15 mins or so. Also, heard the jig dont work on these, can anyone elaborate? Thanks
Click to expand...
Click to collapse
The jig DOES work, it IS a brick, and YES, YOU'RE F**KED
Sorry, but I canot say this, any politer ^^
And, please. Don't take me too hard but, I think you are still a n00b ^^
This has nothing to do with you post rate, or anything, like that... But, there IS no Linux installer, for the GNex ^^
BTW, try a battery pull, and leave it for a few hours, before posting anything else... It works wanders ^^ Maybe you just fried your phone, a tiny bit...
h_10 said:
and this is why we can't have nice things....
this is one of the reasons why phone companies are so against unlocking bootloaders. people screw up their rooted, unlocked phones and then send it back to vzw or the manufacturer to cover the bill.
if you're going to root your phone and mod it, then man up and accept the consequences when you derp it.
not saying the op isn't going to accept full responsibility, but your advice is what's wrong w/ some in this rooted community.
Click to expand...
Click to collapse
The nexus has an unlocked bootloader, it's hard bricked. Samsung can cover the bill.
Poor Samsung..
Sent from my francoPhone
ChongoDroid said:
The nexus has an unlocked bootloader, it's hard bricked. Samsung can cover the bill.
Poor Samsung..
Sent from my francoPhone
Click to expand...
Click to collapse
No, they can't and won't...
It's his OWN fault, for mucking round, with this delicate piece, of technology...
We ALL have to do this, on our OWN responsibility...
If he mucks up his phone, HE can pay for it...
h_10 said:
and this is why we can't have nice things....
this is one of the reasons why phone companies are so against unlocking bootloaders. people screw up their rooted, unlocked phones and then send it back to vzw or the manufacturer to cover the bill.
if you're going to root your phone and mod it, then man up and accept the consequences when you derp it.
not saying the op isn't going to accept full responsibility, but your advice is what's wrong w/ some in this rooted community.
Click to expand...
Click to collapse
Sorry your post is so retarded I have to double reply.
Do you really think the tiny amount of repairs coming from botched hacks is the reason most companies are locking bootloaders? Like really..
My advice is what's wrong? Hmm..
Maybe the OP should "man up" and go buy a new handset instead of Samsung hiring some monkey for $12 an hour to hook his phone up to a jig.
...Jack wagon
Sent from my francoPhone
Related
i tried updating my radio to the newest one...so i clicked it...looked away and i had a gray screen then the phone turned off....now it wont power back on at all...not even in recovery...and when plugged into a/c power i dont even get the amber light...what the hell should i do....thanks
What do you mean, you clicked it? Which of the two radio versions? Were you in recovery, ROM Manager, etc..? More detail!
kris54241 said:
i tried updating my radio to the newest one...so i clicked it...looked away and i had a gray screen then the phone turned off....now it wont power back on at all...not even in recovery...and when plugged into a/c power i dont even get the amber light...what the hell should i do....thanks
Click to expand...
Click to collapse
are you rooted or stock? this happened to me once, but it seems that i had a bad rom install. i was able to boot into recovery mode and just restore my nandroid backup of the previous rom. hope this helps.
if you're not even getting the charging light, you're most probably bricked. sorry man.
RIP to your Evo.
i downloaded the newest radio like 7.28,,,then was in rom manager and selected the radio to install from sd card,,,clicked ok...i looked away for maybe 10 seconds and then i saw an all gray screen...then it powered off...now i cant get it to turn on...yes i was rooted...
kris54241 said:
i downloaded the newest radio like 7.28,,,then was in rom manager and selected the radio to install from sd card,,,clicked ok...i looked away for maybe 10 seconds and then i saw an all gray screen...then it powered off...now i cant get it to turn on...yes i was rooted...
Click to expand...
Click to collapse
I know may sound stupid but remove battery for a minute or so and try again... was your batt low when u started the update? May just have to wait for a bit of charge b4 it will turn back on...not sure if this will help but hopefully it will. Best luck to ya.
no...battery was nearly fully charged...and battery has been out for about 20 minutes...im thinking its bricked...anyone got any ideas? also...what do can i say when i take it into sprint..
I Think its bricked :/
But about your phone if it is bricked, i would say i lost it and keep the battery and sd and pay insurance to get a new one.
its hundred bucks for a new one...i was installing a htc radio,,,thinking its covered under manufactured warranty,,,also got 2 batteries for 8 dollars so not a great deal lol
My friend who is a manager at a store said that now that its legal to root a phone its still covered under warranty so is try takin it in
Sent from my PC36100 using XDA App
spencelk said:
My friend who is a manager at a store said that now that its legal to root a phone its still covered under warranty so is try takin it in
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
soo...the manufacture warranty isnt void?
spencelk said:
My friend who is a manager at a store said that now that its legal to root a phone its still covered under warranty so is try takin it in
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yea its legal and your friend is probably a cool dude and don't care and will warranty them but unfortunately they don't have to honor the warranty if user changes / modifies software that was not ota or provided by HTC or Sprint. Use at your own risk.
I would'nt tell them you tried messing with the software. I would just say you woke up this morning tried to turn on the phone and it would not turn on. Tell them you turn your phone off every night when you go to bed, keep it simple.
It's void if they know about it. That's what they said on g4 atots when they did the special on jailbreaking and rooting. But will they know if it don't turn on? I assume they (htc) would just flash new software on it and give it out as refurbished.
alright thanks guys...but it was the htc software lol...new radio update...idk,,maybe that dont count since someone had to extract it.,..but thanks guys
Its a long shot but wait a couple days for the update to come out and tell them you tried to update and it did that......
Sent from my PC36100 using Tapatalk
Yes, it is legal via an exemption to the DMCA to root/jailbreak a phone - HOWEVER, if you break the phone by doing this, it isn't going to be covered under the warranty. The warranty still only covers normal use, and hacking, however legal, isn't normal use. Sorry dude. Magnusson Moss Warranty Act, look it up. Warranty doesn't cover when you break the thing yourself, only when a manufacturer / latent defect causes a failure.
It really depends on which sprint store you go to. I always go to a 3rd party Sprint repair shop near my house. I had a rooted hero to 2.1; when the evo came out i bought one and took the hero to the sprint shop to update to the official 2.1 version to give to my dad. When they tried updating it, the phone would never fully boot so they gave us a brand new one. yes they new it was rooted and had a custom rom, i had talked to them that day and before about it and they didnt care.
anyway, best of luck in this situation. If you dont have a cool sprints guys than i would take sprink's advice and say you woke up and it wouldnt turn on. if there is no damage, what can they do?
^ Good luck with that...legal or not, he screwed the phone up. Not a warranty issue...
Just seen this thread they might be able to help you out.
http://forum.xda-developers.com/showthread.php?t=735686
Same thing happened to me...
I tried to restart my Evo today and the same thing happened. I took it to the Sprint store and the tech there said that the power button actually failed, and that they had to ship me a replacement. From what he was saying this has happened on a few of the Evos.
Ouch brick. Bring it back play stupid. I bet the issue was using rom manager to flash a radio. A radio isnt a ROM its the MOST IMPORTANT piece of code the phone has and a sure fire way to brick it if you mess it up. I wouldnt use rom manager other than to boot into recovery
So I've been rooted on my ET4G for some time, switching roms and such. Well, today I saw that a leaked version of ICS has been released for the SGS2. The model number GT-I9000 was the same, so I tried to flash it using ODIN. Unfortunately, the flash failed and I had to do a battery pull to remove the phone from download mode. I then rebooted the phone and am now given the Android System Recovery 3e screen. I tried doing a data wipe and cache partition, but I cannot get any progress. I've tried putting the phone in download mode and using ODIN to reflash a stock rom/modem/kernal but ODIN doesn't recognize the phone.
I'm fairly competent when it comes to root and custom roms, but I think I screwed up this time. Anybody have any ideas? I've tried removing the SD card, using a "Jig" and also a fresh battery. Nothing works.
Worst comes to worst, I'll have to take it to Sprint tomorrow and see what they say. In download mode it does day that I've got 1 count of custom binary. Will Sprint check for this and cause a void of warranty as a result?
Try removing drivers and reinstalling them. If you can get into Odin you should be good.
Sent from my SPH-D710 using XDA App
I think a few people did this and couldn't save it. Can you get into Odin/download mode? If so, try sfhub's full stock Odin tar file
Sent from my SPH-D710 using xda premium
Unfortunately, I cannot get Odin to recoginze the phone. Infact, I cannot get the computer to recognize the phone at all when plugged in. I think its a loss. I'll take to to sprint and see what happens
The way I understood it when someone fixed this before, you need to install the PC USB drivers for the INTERNATIONAL SGS2, then you can get into Odin. I could be wrong, though, since it sounds like your PC can't even tell there's a phone there.
bjonesy77 said:
So I've been rooted on my ET4G for some time, switching roms and such. Well, today I saw that a leaked version of ICS has been released for the SGS2. The model number GT-I9000 was the same
Click to expand...
Click to collapse
You should know that GT-I9000 is the Galaxy S, GT-I9100 is the SII. As well as our model number being SPH-D710.
Just mentioning it because if you went with the GT-I9000 ICS build which is available as a custom stripped one its even further off than you had imagined.
So far I have tried to helpout 2 other plp on this same subject and to no avail. I am in contact with one of them he is getting a replacement phone and hopefully going to send me the screwed phone so I can either kill it completely or find a fix in the process.
I would just flash my own phone to try and digout but I have no backup. But I will update as soon as I can start testing for a fix for the comp not recognizing the phone.
bjonesy77 said:
Unfortunately, I cannot get Odin to recoginze the phone. Infact, I cannot get the computer to recognize the phone at all when plugged in. I think its a loss. I'll take to to sprint and see what happens
Click to expand...
Click to collapse
dont even bother taking it to sprint, if u tell them what happened they're not going to help u, cause you were jail breaking etc on ur own risk, you'll just have to fix it or its a useless phone. Why dont u try installing the drivers for the GT-I9000 and see if that works.
klyang88 said:
dont even bother taking it to sprint, if u tell them what happened they're not going to help u, cause you were jail breaking etc on ur own risk, you'll just have to fix it or its a useless phone. Why dont u try installing the drivers for the GT-I9000 and see if that works.
Click to expand...
Click to collapse
Jailbreak? When did this become an apple forum? JK.
Hey OP just clear your Odin count via jig and play the I tried to do the OTA card. I have seen 2 plp get replacment phones by saying this. No guarantee though. Read this thread almost at the last page of posts. http://forum.xda-developers.com/showthread.php?t=1399551
I've filed an insurance claim and the phone is being replaced. I've searched far and wide and the only fix that *MIGHT* work, is JTAG.
I did take the phone to sprint, they opened it up and told me that it had water damage because they had no other explaination I guess.. I laughed, but there was no way for me to tell them "Nope, not water damage. I f***ed the software myself."
Jig doesn't work BTW
bjonesy77 said:
I've filed an insurance claim and the phone is being replaced. I've searched far and wide and the only fix that *MIGHT* work, is JTAG.
I did take the phone to sprint, they opened it up and told me that it had water damage because they had no other explaination I guess.. I laughed, but there was no way for me to tell them "Nope, not water damage. I f***ed the software myself."
Click to expand...
Click to collapse
Heh well if I ever mess up dont worry myne will "have water damage" as well. Because Ill just end up filing a claim telling them its at the bottom of a lake.
Funny that they think it does but its usually called based on the stickers that change color on water contact.
(NOTE THAT I AM ONLY EXPLAINING IN *DETAIL SO THAT SOMEONE MAY BE ABLE TO CORRECTLY ANALYZE THE PROBLEM)
Okay, so I got my new AT&T Samsung Galaxy S III less than a month ago.
My friend helped me in the past few days to root and install cyanogenmod 10. Everything was still fine, until I did something in some kind of pixel density changing app. When rebooting, it only showed the Samsung and Samsung Galaxy S III screens when booting up, but went no further. I wiped everything and restored the last backup I made (advanced restore). Everything ran fine again, with all the original factory stuff. I decided to try and see if I could reinstall cm10 (wiped everything, installed zip, rebooted), and it was successful. Then I decided I wanted to wipe that and try out Energy HD 2.0. Once trying to install the zip, it returned an error message and aborted. I then decided to scrap that idea and just go back to the original factory rom and everything. So I once again wiped and restored my last backup. Upon hitting Reboot, it just went black and didn't turn on again. Now I am completely unable to turn it on, charge it, go into cwm recovery, or download mode. Plugging into the computer just pops a driver install message for QHSUSB_LOAD. Never has anything, even the LED, so much as blinked.
Can somebody please help me? I just would like to know if there is a way to get it working. I'd be very grateful, thanks!
*detail, meaning just what I was doing, as I do not remember exact error codes and such.
Try reflashing. What stock image are you using?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
kinghorsey said:
Try reflashing. What stock image are you using?
Click to expand...
Click to collapse
Is it even possible to re-flash a recovery image (from Odin3) when the device cannot enter download mode?
I think it may have been CWM Recovery v5.0.4.2 or something that I originally installed/flashed (can't check right now though, because I was kicked off my computer). Then it had upgraded to v6.something later on my phone.
((Sent from my stupid old iPhone 3Gs))
Look into jtag service
sent from outside ur window
twanskys204 said:
Look into jtag service
sent from outside ur window
Click to expand...
Click to collapse
Haha, okay. I just don't want to spend $60 at this very moment.
Sent from omygoshwhatthehellareyoudoingoutthere
stupid iPhone
Ascyndaeon said:
Haha, okay. I just don't want to spend $60 at this very moment.
Click to expand...
Click to collapse
Yeah I would say your bootloader is messed up and the only way to breath life back into your phone is jtag repairs. I had a problem identicle to yours and I searched the net for a week solid trying to figure out how to fix it without having to fork over the money.. but alas had to send it. Luckily the guy who provides the repairs is amazing at what he does. Phone will be back in your hands within a few days if you're from the states.
fallenkirmit said:
Yeah I would say your bootloader is messed up and the only way to breath life back into your phone is jtag repairs. I had a problem identicle to yours and I searched the net for a week solid trying to figure out how to fix it without having to fork over the money.. but alas had to send it. Luckily the guy who provides the repairs is amazing at what he does. Phone will be back in your hands within a few days if you're from the states.
Click to expand...
Click to collapse
Hmm, okay. I wonder then why only JTAG Repairs knows how to fix this stuff, and the information isn't widely available.
And so if I do send it to jtag, then I guess I'll be getting it back within a few days, 'cause I live in the US.
Thanks for your input.
Ascyndaeon said:
Hmm, okay. I wonder then why only JTAG Repairs knows how to fix this stuff, and the information isn't widely available.
And so if I do send it to jtag, then I guess I'll be getting it back within a few days, 'cause I live in the US.
Thanks for your input.
Click to expand...
Click to collapse
Well there is a way for you to do the jtag repairs yourself... but i wouldn't touch the process with a 10 foot pole lol... I would rather let a pro do things like that... just youtube jtag repair and take a look at some of the process.... way beyond my comprehension atleast..
fallenkirmit said:
Well there is a way for you to do the jtag repairs yourself... but i wouldn't touch the process with a 10 foot pole lol... I would rather let a pro do things like that... just youtube jtag repair and take a look at some of the process.... way beyond my comprehension atleast..
Click to expand...
Click to collapse
Ah, I suppose you're right. Not to mention expensive. That equipment probably costs more than having them fix it. Though it would probably be worth it of you bricked it on a regular basis.
For the record I did search the forum (pretty quickly) and didn't find what I was looking for so I hope I'm not reposting the same issue.
So I was flashing the Slim Bean 4.2.2 rom to my galaxy s3 using goomanager and i think my phone is hard bricked.
In goomanager it allows you to select multiple zips to flash, and I'm pretty sure they flash in the order they are listed. Well i planned to flash the Slim-i9300-4.2.2.build.6-OFFICIAL (the rom itself), Slim_Gapps.4.2.2.build.6 (google apps for the rom), and Extras.4.2.2.build.6 (extras specific to the rom) for the Slim Bean rom from the slimroms site.
I had the Extras.4.2.2.build.6 zip listed first then accidentally pressed the flash button and without thought confirmed my actions in the pop up window (Yes i'm an idiot). So it rebooted and went through some script then my phone went black.
It wont go into download mode (home, power, vol down), it won't display anything on the screen, and it wont power on. My computer recognizes it and shows that it is connected. I don't know if that will do anything it terms of fixing it on my own? I haven't read up on bricked phones too much but i'm pretty sure its hard bricked.
Sooooooo, first off does anyone have any suggestions as to what i should do?
-If i were to take it to a Sprint store what would they say? I've had it for a year and I don't think i have any warranty (granted i know rooting my phone would technically void it anyways). If it doesn't power on or do anything could I say it turned off in the middle of the 4.1.2 OTA update and resulted in its current state?
-Would a usb JIG boot my phone into download mode and fix my problem?
-Is a jtag service my only option?
-If it is jtag does anyone know a place around the Louisville, KY area that does this sort of thing? I google searched but didn't find anything local.
-If not i guess mobiletechvideos is my best option?
Any help would be much appreciated. I'm in dire need of this phone to be fixed as I start my new job in a 2 weeks and need it for obvious communication reasons.
DrewFerg11 said:
For the record I did search the forum (pretty quickly) and didn't find what I was looking for so I hope I'm not reposting the same issue.
So I was flashing the Slim Bean 4.2.2 rom to my galaxy s3 using goomanager and i think my phone is hard bricked.
In goomanager it allows you to select multiple zips to flash, and I'm pretty sure they flash in the order they are listed. Well i planned to flash the Slim-i9300-4.2.2.build.6-OFFICIAL (the rom itself), Slim_Gapps.4.2.2.build.6 (google apps for the rom), and Extras.4.2.2.build.6 (extras specific to the rom) for the Slim Bean rom from the slimroms site.
I had the Extras.4.2.2.build.6 zip listed first then accidentally pressed the flash button and without thought confirmed my actions in the pop up window (Yes i'm an idiot). So it rebooted and went through some script then my phone went black.
It wont go into download mode (home, power, vol down), it won't display anything on the screen, and it wont power on. My computer recognizes it and shows that it is connected. I don't know if that will do anything it terms of fixing it on my own? I haven't read up on bricked phones too much but i'm pretty sure its hard bricked.
Sooooooo, first off does anyone have any suggestions as to what i should do?
-If i were to take it to a Sprint store what would they say? I've had it for a year and I don't think i have any warranty (granted i know rooting my phone would technically void it anyways). If it doesn't power on or do anything could I say it turned off in the middle of the 4.1.2 OTA update and resulted in its current state?
-Would a usb JIG boot my phone into download mode and fix my problem?
-Is a jtag service my only option?
-If it is jtag does anyone know a place around the Louisville, KY area that does this sort of thing? I google searched but didn't find anything local.
-If not i guess mobiletechvideos is my best option?
Any help would be much appreciated. I'm in dire need of this phone to be fixed as I start my new job in a 2 weeks and need it for obvious communication reasons.
Click to expand...
Click to collapse
"Slim-i9300-4.2.2.build.6-OFFICIAL" that is the international model version of the ROM. Flashing International ROMs hard brick your phone. So yes, you do have a hard brick. As to taking it to sprint, Idk if they'll do anything for you especially if you have no insurance or warranty. Sorry bud
Well your problem is not that you flashed in the wrong order. Your problem is that you flashed a rom from the International S3 (i9300) not the sprint SPH-L710. You attempted to turn your Sprint phone into an International S3. This flashed completely different partitions onto your device. JTAG is the only way to fix it. They have to open the device and repartition everything. Mobiltech is the way to go. My advice in the future is if you don't find the rom in the Sprint Galaxy S3 forums do not flash it.
Sent from the future via Xparent Green Tapatalk 2
solis888 said:
"Slim-i9300-4.2.2.build.6-OFFICIAL" that is the international model version of the ROM. Flashing International ROMs hard brick your phone. So yes, you do have a hard brick. As to taking it to sprint, Idk if they'll do anything for you especially if you have no insurance or warranty. Sorry bud
Click to expand...
Click to collapse
Well i feel retarded.... should have done some more research and not trusted a youtube video.
Is JTAG service the only way to fix it/will that fix it?
Ya, I didn't know what they'd do if i played dumb (i know, thats bad, but im desperate) and said it did this during the official OTA update.
DrewFerg11 said:
Is JTAG service the only way to fix it/will that fix it?.
Click to expand...
Click to collapse
JTAG is in fact the only way to repair it. Yes guaranteed it will be fixed.
Sent from the future via Xparent Green Tapatalk 2
DrewFerg11 said:
Well i feel retarded.... should have done some more research and not trusted a youtube video.
Is JTAG service the only way to fix it/will that fix it?
Ya, I didn't know what they'd do if i played dumb (i know, thats bad, but im desperate) and said it did this during the official OTA update.
Click to expand...
Click to collapse
Just do more research next time before flashing. And as the person above said, don't flash anything that isn't on the sprint GS3 forums.
DrewFerg11 said:
Well i feel retarded.... should have done some more research and not trusted a youtube video.
Is JTAG service the only way to fix it/will that fix it?
Ya, I didn't know what they'd do if i played dumb (i know, thats bad, but im desperate) and said it did this during the official OTA update.
Click to expand...
Click to collapse
Unfortunately yes you are hard bricked and it sucks. JTAG will fix it Google it there are good services out there for about $60 and week or so turn around.
If you pay for insurance you could also take it to sprint and tell them it won't boot and they should replace it for a deductible. Some will call this fraud but the way I see it if you pay for insurance it is there to cover mistakes. You didn't mean to brick it just like some one who dropped it in a pool didn't mean to ruin their phone.
Sent from my SPH-L710 using xda premium
Thanks for the quick response everyone. I really appreciate it. I feel dumb. I usually do my research, but I was bord and a spur of the moment action got me in trouble this time.
I guess I'll run to the sprint store tomorrow and see what they can do, if anything.
If they can't do anything, mobiletech it is! It looks to be a reliable site. Will my phone be active on the sprint network still after the JTAG? or will I have to do anything to it? I also assume I will get all the text messages and what not that my phone is currently incapable of receiving now?
Any thing else I should know about the JTAG or my phones hard bricked state before I go ahead with it since we are on the subject and I don't want this to happen again.
DrewFerg11 said:
Thanks for the quick response everyone. I really appreciate it. I feel dumb. I usually do my research, but I was bord and a spur of the moment action got me in trouble this time.
I guess I'll run to the sprint store tomorrow and see what they can do, if anything.
If they can't do anything, mobiletech it is! It looks to be a reliable site. Will my phone be active on the sprint network still after the JTAG? or will I have to do anything to it? I also assume I will get all the text messages and what not that my phone is currently incapable of receiving now?
Any thing else I should know about the JTAG or my phones hard bricked state before I go ahead with it since we are on the subject and I don't want this to happen again.
Click to expand...
Click to collapse
I doubt you will get any texts, sprint is not saving to deliver them later. Unless your using Google Voice. Your phone will be up and running rom flashed but it won't activate until you log into it with your google ID, just like when you get in the box brand new.
Sent from the future via Xparent Green Tapatalk 2
First off my device is unlocked and rooted but that is it and I did that weeks and weeks ago when the latest android patch came out.
It has been working fine but I had a sleep over with the kids last weekend and they like to play with it as usual. After they left, hours later I noticed the device showing the google start screen like it was stuck there. I tried to get it into the boot loader or recovery and nothing. Now it appears dead, no lights, etc.
I tried charging and tried using the volume and power thing, etc to no avail. When connected to the pc I am gettng the dreaded QHSUSB_Dload thing.
#First question is there a fix for this? I have searched every where and have yet to find anything substancial other than the volume thing which is not working.
# second question is can I rma this or will it not be accepted due to it being rooted? There is no way I can bring it back to stock without accessing the bootloader.
#last question - If I cannot rms it can I take it apart and do something to repair it or is there anything I can do?
Thanks guys. This really sucks. i have never had an issue up until now and this thing is totally stock besides being rooted and unlocked.
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582
That will not work with a hard brick. I cannot get into bootloader or adb.
Sent from my Nexus 4 using xda app-developers app
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Thanks for the outpouring of support here. :banghead:
I think it is clear I'm screwed.
Pretty unbelievable as I'm all stock except for recovery.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd try to send it back for repair. What do you have to lose?
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but right now you have a $200 paper weight. So why not gamble on the s/h for the rma?
I think you are misunderstanding what I am saying.
Google basically makes you pay for a replacement. Upon inspection they refund the money. If they do not refund the money then I am out the full cost.
I could find that reasonable if I was playing around or something but I have kept my devices all stock ever since the latest version came out except for unlocking and rooting.
I guess the other option would be to find someone to do a jtag repair and I could only find one guy and I don't think he touches Nexus 7s. Not sure though but waiting for him to reply. This sucks! My device was perfect and I loved it.Great battery, no touch screen issues. Not a single issue and then all of a sudden this. i really cannot understand what caused it.
Thanks for the reply. I really figured there would be others this happened too but everyone gets Hard Brick mixed up with soft brick and every hard brick post I read is not a hard brick. Hard Brick = F#cked :crying:
I gotcha. I thought you paid to send it back & then you had the option to pay to fix it if it wasn't covered by warranty.
That could be through Asus directly but not sure.
I think though if they go to repair it they will see the unlocked boot loader. That voids the warranty
Sent from my Nexus 4 using xda app-developers app
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
dkryder said:
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
Click to expand...
Click to collapse
Yeah, if you know an RMA is a very very very poor shot / don't want to try it. I guess a tear down is your second best bet.
You should check out Adam Outler's tear down videos if you feel you might be able to take this on. I'll link Outler's videos below. They MAY help you in deciding if you want to go through with it (and what you may expect to see).
http://www.youtube.com/watch?v=RMzi4K_PwPs (Transplant Nexus 7 Boards)
http://www.youtube.com/watch?v=QOFpY1nXFew (Nexus 7 Unboxed the XDA way)
Thanks guys.
I finally got an email back from those guys that do Jtag repairs and he said it was a hardware issue but I am not sure if he understood my issue.
I do not think taking it apart and unplugging the battery will work here if the bootloader is corrupt. I am going to try to let the battery go completely dead though and then try to do the volume/power key thing to see if there is any chance.
I do not know much about this but what I read is that if the bootloader is stopped somehow while loading it can become corrupt in some cases and you cannot do anything without it and there is a device specific key involved. That is why only someone with some specific software can fix it. I thought this key as called Jtag but again, I do not know much about this. The Jtag guy said it was hardware.
Man, I have an Hp touchpad that I got years ago. I installed Android on it years ago and have it overclocked it to over 1700mhz and that thing is still going strong. The kids even dropped it and it has a crack in the screen and it still will not die. Here I have a Nexus only a few months old fully stock except for root and unlock and it is dead. Kills me especially after the way I always stand up for the Nexus line. Still loving my Nexus 4 though and it is well over a year old. Oh well, if that one goes like this one I am jumping off a high bridge. :laugh:
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
whoamanwtf said:
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
Click to expand...
Click to collapse
First off, I am not sure what is wrong with it which is why I am posting here. I stated numerous times that I do not know much about this.
And yes, I know this that rooting and unlocking voids the warranty. I also know that it is my fault for doing it but I have been doing it for around 3 years now and have used various roms and kernals in the paqs and have never had an issue. Perhaps it is a hardware issue. I just do not think this issue was caused by me.
In terms of the kids playing with the device. They play games, things like that. The desktop is locked and they have no access to settings or anything. When I said messing with it I just meant playing games though sometimes they open new games and leave the old ones running. I do not know how that would cause this.
There was no ota or update.
I am not sure what you are saying about LG.
And again, I am not angry with Google or Asus. My point was that this issue was most likely not caused due to rooting or unlocking and an ota would not cause a dhsusb issue even if it did go bad.Lets try to remember that nearly everyone here roots, unlockes and installs roms, etc. I have done so as well but not on this device. This one I wanted to keep pretty much vanilla but I wanted to be able to use Titanium back up, etc. And also, I rooted and unlocked months ago when I first got the device and had to root again when the latest version came out which was awhile ago.
In terms of fixing I have not found a solution for this. I do not know if it is a hardware issue or a software issue. That is why I am posting here. I am looking for some information from people who know this stuff. I know nothing but what I have read and so far I have read many different things. I am here to learn.
OK so here is what I meant with the G2..
I had a stock/rooted/TWRP G2 and half asleep accepted an OTA Update, when it does this it downloads the update into a partition that the device checks before booting. Because I had the custom recovery obviously the update failed but it left that code in the boot partition that would now allow me to even get into download mode. See this post here for how it was fixed http://forum.xda-developers.com/showthread.php?t=2582142
I am not sure if this would be the same problem or how to go about fixing it because of the device difference, but maybe it could help? I didn't mean to come off as a ****, just far too many people like to get into their devices and void the warranty then blame everyone else.
It is really not difficult to pull the back cover off and unplug the battery, I suggest doing this it could very well help just be careful not to crack the back while pulling it off, a credit card/ID and a butter knife should do the trick without leaving marks.
No worries. I appreciate the help.
I agree with you totally.
Sent from my Nexus 4 using xda app-developers app