[Q] Nexus 7 Hardbrick! QHSUSB - Nexus 7 (2013) Q&A

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

Related

[Q] Quick Question about Rooted Phone at Sprint

I'm 100% positive I just bricked my phone. I was not thinking last night and pulled the battery while flashing a radio update. I know that I've got a literal brick on my hands but I had a couple quick questions:
Can Sprint tell that my phone is rooted at all if I take the SD card out when I bring it in?
Is there are actual solution to this problem that involves NOT taking my phone to Sprint?
I'm prepared for ****ty answers, but I've got high hopes that I'll just eat the insurance cost and get a new one.
thistimearound said:
I'm 100% positive I just bricked my phone. I was not thinking last night and pulled the battery while flashing a radio update. I know that I've got a literal brick on my hands but I had a couple quick questions:
Can Sprint tell that my phone is rooted at all if I take the SD card out when I bring it in?
Is there are actual solution to this problem that involves NOT taking my phone to Sprint?
I'm prepared for ****ty answers, but I've got high hopes that I'll just eat the insurance cost and get a new one.
Click to expand...
Click to collapse
There are quite a few threads about brick restores...might want to look them up...but if you can get to recovery most problems will be solved. I would confirm brick before panic...I mean it will all good intentions.
thistimearound said:
I'm 100% positive I just bricked my phone. I was not thinking last night and pulled the battery while flashing a radio update. I know that I've got a literal brick on my hands but I had a couple quick questions:
Can Sprint tell that my phone is rooted at all if I take the SD card out when I bring it in?
Is there are actual solution to this problem that involves NOT taking my phone to Sprint?
I'm prepared for ****ty answers, but I've got high hopes that I'll just eat the insurance cost and get a new one.
Click to expand...
Click to collapse
Did something like that to my captivate on at&t and all I did was take it in and told them that when I woke up there was a black screen and I couldn't do anything, and I just acted really stupid and told them that I had no idea what happened to it. Play real stupid and it might work or idk, see they can jtag that device
Sent from my SGH-T959V using xda premium
I appreciate it. As for the brick restore methods, unless there's one for a "completely dead, USB doesn't recognize it, and LED doesn't turn on" brick, then I'm just wasting time. I looked at most of them, and they all require the phone to actually do something... which mine will not.
Damn, sorry to hear that. Yeah if its not doing ANYTHING I would just bring it in an claim insurance on it, tell them you have no clue what happened, just woke up and it was like that (like someone else said to do). Good luck. I'll keep my fingers crossed for you.
Sent from my PC36100 using XDA App
It could be if your lucky you might have just fried your battery somehow maybe and I mean MAYBE you still get lucky and that's all it is assuming you haven't tried switching batteries yet lol if that's not it, sorry for your bad luck. I'm pullin for ya man
Sent from my PC36100 using xda premium
I wouldn't worry about it. If the phone won't turn on and you take it in & just play dumb, they'll give you a replacement. You won't have to pay the deductible. You lost whatever data you didn't have backed up, but other than that you don't have much to worry about.
There's no coming back from pulling the battery during a radio update, and I doubt Sprint will make it difficult for you. If they do happen to tell you that you have to pay the deductible, argue against it or take it to a different store. Most likely they'll just file a claim and get you a new (or refurbished) phone within a day or two.
Good luck!
Sent from my PC36100 using Tapatalk
I went to my Sprint store the other day. They said they don't care if it's rooted or not. Just bring it in and they will look at it. They said usually they can fix most problems.
Just to update you folks that may have also been interested:
I went in and played stupid. I also pulled my SD Card so they couldn't use that against me. This was the dumbest thing I've ever done to brick my phone, but it looks like all is well. As of today they said they've already ordered me a free replacement due in on Monday. Apparently it won't even cost $100 due to having TEP. I'm not sure that I believe that, but that's what the guy said on the phone. If anyone is interested I can update this once I know more.
Sprint openly supports rooting.. Idk if anyone else knows that.. After the new policy kicked in, they might as well just say that seeing as how the TCs are required to work on rooted devices. If they can't fix them, its a DHRP. that's the word on the street anyway
Sent from my nocturnally stocked EVO using xda premium
That's good to know. I took my phone in 2 or 3 weeks after the Gingerbread update and all the tech did was ask if it was rooted. Someone looked at it the day before and and I had just unrooted it about an hour before that. Someone else was telling the tech to look for the s-on/s-off. I really don't think the tech cared. Glad they might have changed.
Yet my friend Rachel, who is a tech at the local store confirms yet again that they are NOT authorized to work on Rooted phones......
HipKat said:
Yet my friend Rachel, who is a tech at the local store confirms yet again that they are NOT authorized to work on Rooted phones......
Click to expand...
Click to collapse
Well that's funny seeing as how I am a TC for a corp. Store in Texas. Hmm... Seems like we're getting two different stories from the same company... Our superiors within our region have confirmed what I have said verbatim. We are required to work on them if they are rooted. If we can not fix the device we must replace it.
Sent from my PC36100 using xda premium
Best bet is to fully unroot just to be on the safe side. Then whether or not techs are authorized to work on the phone is moot.
Confirmed by three stores in Connecticut, 2 corp stores, 1 authorized reseller/repair store.. That they do not support rooted phones.. Had to unroot to get my replacement phone when the USB started only partial charging and was clearly a hardware defect and had nothing to do with software.. They opened it confirmed so physical damage after I brought it back unrooted.
Didn't mean to abandon this post guys. I just simply forgot about it. Sprint replaced my phone free of charge since I truly did fry it. They couldn't recover anything and I didn't leave the SD card in for them to check.
Best bet: unroot if it works at all or brick the **** out of it. Also note I had TEP. So, that's important. All in all I think Sprint is still a bit douche on the root business, but they handled this situation relatively easy and painless.

[Q] Am I completely screwed?

I just got my E4GT a couple weeks ago...all of a sudden, it started going to hell. The touchscreen stopped working pretty much completely, it won't charge and won't acknowledge the USB cable at all, so I can't connect to Odin or flash a stock firmware, or use a usb jig.
It's a hardware issue, I know but can I still take it in? What are the chances they'll say I can't return it because I rooted it? All of the employees at my sprint store seem pretty clueless...is it worth a try just to see if they can fix/replace it?
I really don't want to pay 100 bucks for a new phone just because I rooted it -__-
Also, my parents are REALLY, REALLY pissed.
Thanks, for the love of god, help me.
I have to go on a trip in 3 days and I NEED my phone.
Isnt this same post in General?
One post in one section is all you really need...
Sent from my SPH-D710 using xda premium
First you say it's a hardware issue then you blame root. You should just take it back for a replacement. And never root again unless you know what you're doing.
Sent from the future.
I've posted this message before in the og epic forum: my grandfather always told me, of you can't afford to replace it, you have no business messing with it. Don't get started modding unless you are willing to buy another phone.
And I agree with the other guy, its either your flash issue or hardware. Not both.
Sent from my SPH-D710 using XDA App
Your screwed
Sent from my SPH-D710 using XDA App
I saw a video that someone posted here today. Let me try and find it, it's hella funny and it reminds me of you.
Here you go
http://forum.xda-developers.com/showthread.php?p=19597685#post19597685
If the battery is dead resulting in a phone that won't power on... there is no solution that can be offered here besides finding a cable that works to charge it.
If you bought this phone "a couple weeks ago" I'm going to bet we are past your window for returns, and if you modified your phone and don't know how to fix it, or can't do a simple troubleshoot of the USB cable/port... yes, you are completely screwed for the timeline you have setup.
Bring it to a sprint store, ask if you can test to see if their charger will charge your phone. If it does, its the cable and you can go buy a new one (better one) and all the other problems are probably moot.
If it doesn't charge, then its hardware issue on your phone (or an issue with something you did that we cannot reverse without the phone gaining power plus being able to be in download mode,) and you already know what I'm going to say.
SocialReject said:
First you say it's a hardware issue then you blame root. You should just take it back for a replacement. And never root again unless you know what you're doing.
Sent from the future.
Click to expand...
Click to collapse
This. Don't root your phone if you don't have the means or the willingness to deal with it if you bust it!

Weird issues with my 2nd HTC Desire Z

Love the phone but getting kind of sick of this stuff. The phone has been crashing lately, went into a boot loop today that took me at least half an hour to get working again (pulled the sim, sd card and battery till it worked), about 5 minutes ago my phone was on charge and I was sending sms messages using browser texting, and I noticed I hadn't received any replies for a while, so I looked at my phone and noticed it was a phone icon with a red triangle and a red exclamation mark, I pulled the battery and everything booted up like normal, then I went to unlock my phone a minute later and it wasn't responding, but the green notification led was flashing. This is the second phone I've bought, this time with warranty so that's good, I generally really like the phone and I feel if I can fix these weird problems and get the battery life a little better it'll be perfect. Anyone have any ideas? I was thinking of doing a factory restore but I basically just got this phone, and I have so many apps installed (May possibly the problem). I'm running Juice Defender Beta... I think I might try and use Ultimate and not beta and see if that helps the situation, other then that, any ideas guys?
Okay so right now after rebooting my phone again, the phone locked and isn't responding again with the bottom soft keys lit up. This phone is driving me crazy I'm going to uninstall juice defender see if that helps.
Is the phone rooted? If you installed a buggy custom rom it could cause the problems you're seeing.
Sent from my T-Mobile G2 using XDA App
jgummeson said:
Is the phone rooted? If you installed a buggy custom rom it could cause the problems you're seeing.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Thanks for the reply, my phone is completely stock running the 2.3.3 OTA firmware. I uninstalled a few programs, juice defender beta being one of them and everything is working wonderfully now hmmm, besides my poor battery life of course.
Just had another crash while downloading 2 things from the market and now I have the red triangle and exclamation mark thing again..
And now my phone isn't turning on again!. I'm having so much luck with these wonderful devices. What should I do?
the only things, that comes to my mind needs root. root breaks your warranty.
So - i would try factory reset and after this, if it wount help, give it back to the shop for repair.
The red triangle/exclamation mark is stock recovery, you can pull up a menu in it by pressing vol up + power.
Do you get any error messages in that recovery? especially along the lines of:
E: Can't mount cache
If so, it might be a bad emmc chip.
-Nipqer
I didn't see any errors and now the phone wont turn on at all. Looks like I'll have to take it back
Okay so I got a brand new one replaced through warranty, it was the 28th day of the 28 day return period and it was the last one in stock, this one has nothing wrong with the screen which is good. Anyway I was wondering if anyone is willing to bounce ideas off me as to why this has happened to me twice. Bad apps? Juice defender? Custom launcher? (Zeam)? I find it hard to believe this is possible, but it could be.
Definitely don't think it was Zeam. Could just be rotten luck. Perhaps try installing your desired apps one at a time to verify that wasn't the cause. Best of luck.
Sent from my HTC Vision using XDA App
Ditamae said:
Definitely don't think it was Zeam. Could just be rotten luck. Perhaps try installing your desired apps one at a time to verify that wasn't the cause. Best of luck.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Good because I like Zeam . The problem with that is it's pretty much impossible to narrow it down like that, the first one took 3 months to die, second one took 2 weeks, I can't install an app then wait until it dies then determine that's the app that does it.
Don't think it was apps that caused your device to behave like that. Probably just faulty device...
Sent from my GT-I9100 using Tapatalk
mikk_ said:
Don't think it was apps that caused your device to behave like that. Probably just faulty device...
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I think this has to be the case, an app couldn't fry the device like that could it? Even if it was trying to? I just sincerely hope this one isn't faulty... 3rd times the charm . So basically everyone's in agreement I don't have to do anything special just use the device like normal? Some people are saying don't install too many things, while others are saying just use it like normal what do you guys think. I don't think the amount of apps installed would do that, I had plenty of space left on my phone.
JDogg1329 said:
Okay so I got a brand new one replaced through warranty, it was the 28th day of the 28 day return period and it was the last one in stock, this one has nothing wrong with the screen which is good. Anyway I was wondering if anyone is willing to bounce ideas off me as to why this has happened to me twice. Bad apps? Juice defender? Custom launcher? (Zeam)? I find it hard to believe this is possible, but it could be.
Click to expand...
Click to collapse
It's probably closer to what Nipqer said with bad EMMC chip. I fully bricked my Desire Z and boy the s--t I did to that phone warranty would have been gone in a few seconds of research. I mean I rooted it, flashed it well over a hundred times. I took it into the HTC repair shop opened up my phone into CWM -- remember if a tech sees CWM -- warranty voided period. I showed him the E:/ can't mount error and he replaced the phone no questions asked. I think this is something that HTC is keeping under wraps instead of doing a massive recall just replacing any unit where this occurs no questions asked. Probably worried about getting a massive class action lawsuit where a judge will force them into doing a recall and giving thier customers a major settlement. Obviously this is only speculation, but I also talked to a good friend who is the west coast business manager for all of Rogers in Canada and he said that every Desire Z that is having problems is getting returned no questions asked, and he said that is completely out of the ordinary for HTC. So my guess something is up and we will never really find out the truth, just count your blessings with this.
Hmm interesting, thanks for your reply gave me something to think about. I guess it makes sense, the phones over a year old and HTC doesn't want to deal with it. I was surprised how quickly and easily I walked out of the Vodafone store with a brand new desire z, tho I've never done it before and it could be standard procedure. Anyway I hope this ones okay, otherwise I'll just take it back again.

HTC Warranty Workaround ?

I read through few posts about people being able to claim their warranty even after unlocking their bootloader , now these people had almost the same problem ..there screen wouldn't display anything or their phone wouldn't boot up at all. So I guess HTC won't check for your warranty if your phone is not booting up ...they'll just check your bill and see if its under warranty and do it for free ...
Sent from my HTC One X using xda app-developers app
Well I've seen people get away with this, but I still darent unlock/root.
Because I know what my luck is like and I would be the only one that doesn't get repaired !!
It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.
Awt67 said:
It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.
Click to expand...
Click to collapse
lol sounds like a good plan, now everyone who needs repair will burn it's phone and get new replacement under warranty
Awt67 said:
It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.
Click to expand...
Click to collapse
Yeah I've been debating for about 3 weeks now, would you really say its worth it?
What ROM you using?
And, about the warranty, what does completely dead mean?
Not booting?
Or bricked etc?
Cheers mate.
I am using Cyanogen Domination 10. It is still work in progress but it stable enough for everyday use. I would also say if you do unlock your phone try roms other as well because they all offer something different.
Dead as in bricked, although if you follow unlock steps carefully there is little chance of bricking your phone
I unlocked my phone the day I bought it ... I'm not regretting it all but the little yellow spot in the bottom left corner is annoying sometimes ..
Sent from my HTC One X using xda app-developers app
lets just make this clear, its certainly posted here already in many many threads...
if you read the unlocking stuff properly on the htc website, it clearly says that the warranty will be invalid for anything caused by unlocking the bootloader
so if you have a blatant hardware problem, ie the wifi antenna problem, they still have to repair it foc
so basically, unless you brick your device, you still have a warranty.
they might try insisting on replacing the main board for a cost, which i've heard quite often. the wifi fix requires changing the main board anyway, so for at least that problem, they shouldn't charge to fix.
still, it does depend on the type of problem as to whether you could convince them not to change the main board..

I Just bricked My Galaxy s iii

I cant even get it to start in bootloader
grunted said:
I cant even get it to start in bootloader
Click to expand...
Click to collapse
Are you asking for help? Or just announcing?
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
help
Whiplashh said:
Are you asking for help? Or just announcing?
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Click to expand...
Click to collapse
Help please
I hit the power button nothing happens not even boot loop please help
grunted said:
I hit the power button nothing happens not even boot loop please help
Click to expand...
Click to collapse
Give us the story of what you were doing before or when it crapped.
epic4GEE said:
Give us the story of what you were doing before or when it crapped.
Click to expand...
Click to collapse
I tried to flash cwm touch
grunted said:
I tried to flash cwm touch
Click to expand...
Click to collapse
Hold volume down and power and home
Does it do anything? If so, get Odin and flash a stock tar for jellybean.
******WARNING: THIS WILL WIPE EVERYTHING ON PHONE (not external sdcard, the PHONE).*******
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Whats the name of the cwm file you flashed and how you flashed it
Sent from my SPH-L710 using xda app-developers app
evo4gnoob said:
Whats the name of the cwm file you flashed and how you flashed it
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
This ^
Also, if you did it through the app, I've heard a lot of reports lately of people bootlooping after updating their recovery.
So if you can get it recognized in ODIN, flash a recovery through that and then see if you can get into it
I think i did the same. i was installing liquidsmooth for the S3 and went to reboot it and bam! bricked. i realized i did not do a wipe i just did an install on top of the rom. I have since then tried all button combos but no luck. I have installed odin and seems like when i plug in the phone to the computer and hold VOL UP+home+power my PC recognizes it but i dont think odin does. So I plan on going and buying one off craigslist and activating it in the morning if i cant do anything by then.
CNexus said:
This ^
Also, if you did it through the app, I've heard a lot of reports lately of people bootlooping after updating their recovery.
So if you can get it recognized in ODIN, flash a recovery through that and then see if you can get into it
Click to expand...
Click to collapse
My phone is dead can't get it in to Odin or recovery nothing happens
grunted said:
My phone is dead can't get it in to Odin or recovery nothing happens
Click to expand...
Click to collapse
Then it sounds to me like you have yourself a fancy paperweight. Where did you find the ROM you were flashing when it occurred?
tkepk181 said:
Then it sounds to me like you have yourself a fancy paperweight. Where did you find the ROM you were flashing when it occurred?
Click to expand...
Click to collapse
He was trying to flash cwm touch
I sent my phne to mobiletechvideo and got it fixed to stock. Cheaper than buying a new phone
Sent from my SPH-L710 using Tapatalk 2
They fix a hard brick
Sent from my SPH-L710 using Tapatalk 2
FYI if you had a hard brick call Samsung and tell them it just stopped working and they will send you a box pre paid to send your phone in and a refurbished phone for your replacement. I end up getting a new phone as a replacement as I bricked mine a few weeks after the phone can out. I did this three times and the last time got a refurbished one. You don't pay nothing and the phone come in about a week the only thing that stuck is you have to setup your phone all over again. There really nice on the phone and didn't ask me about flashing or rooting my phone they just tried to have me trouble shoot the phone which I couldn't. Oh one thing our phone I's covered for one year manufacture warranty that has nothing to do with the carrier.
Sent from my SPH-L710 using XDA Premium App
bonebeatz1234 said:
FYI if you had a hard brick call Samsung and tell them it just stopped working and they will send you a box pre paid to send your phone in and a refurbished phone for your replacement. I end up getting a new phone as a replacement as I bricked mine a few weeks after the phone can out. I did this three times and the last time got a refurbished one. You don't pay nothing and the phone come in about a week the only thing that stuck is you have to setup your phone all over again. There really nice on the phone and didn't ask me about flashing or rooting my phone they just tried to have me trouble shoot the phone which I couldn't. Oh one thing our phone I's covered for one year manufacture warranty that has nothing to do with the carrier.
Sent from my SPH-L710 using XDA Premium App
Click to expand...
Click to collapse
Shouldn't be doing this when you hard brick your phone, that's for actual phone defects and your dumb mistake doesn't fall into that category... :banghead:
SPRINT GS3 FAQ
bonebeatz1234 said:
FYI if you had a hard brick call Samsung and tell them it just stopped working and they will send you a box pre paid to send your phone in and a refurbished phone for your replacement. I end up getting a new phone as a replacement as I bricked mine a few weeks after the phone can out. I did this three times and the last time got a refurbished one. You don't pay nothing and the phone come in about a week the only thing that stuck is you have to setup your phone all over again. There really nice on the phone and didn't ask me about flashing or rooting my phone they just tried to have me trouble shoot the phone which I couldn't. Oh one thing our phone I's covered for one year manufacture warranty that has nothing to do with the carrier.
Sent from my SPH-L710 using XDA Premium App
Click to expand...
Click to collapse
You hard bricked three times!!!! Don't experiment use stuff you know will work!!!
Sent from my blue galaxy
bonebeatz1234 said:
FYI if you had a hard brick call Samsung and tell them it just stopped working and they will send you a box pre paid to send your phone in and a refurbished phone for your replacement. I end up getting a new phone as a replacement as I bricked mine a few weeks after the phone can out. I did this three times and the last time got a refurbished one. You don't pay nothing and the phone come in about a week the only thing that stuck is you have to setup your phone all over again. There really nice on the phone and didn't ask me about flashing or rooting my phone they just tried to have me trouble shoot the phone which I couldn't. Oh one thing our phone I's covered for one year manufacture warranty that has nothing to do with the carrier.
Sent from my SPH-L710 using XDA Premium App
Click to expand...
Click to collapse
This is called fraud. It's not a manufacturer defect that you screwed up. It's a you defect :thumbdown: people like you are the reason prices keep going up instead of going down.
☆SoA: Son's of Android™☆
I like to break stuff!
bonebeatz1234 said:
FYI if you had a hard brick call Samsung and tell them it just stopped working and they will send you a box pre paid to send your phone in and a refurbished phone for your replacement. I end up getting a new phone as a replacement as I bricked mine a few weeks after the phone can out. I did this three times and the last time got a refurbished one. You don't pay nothing and the phone come in about a week the only thing that stuck is you have to setup your phone all over again. There really nice on the phone and didn't ask me about flashing or rooting my phone they just tried to have me trouble shoot the phone which I couldn't. Oh one thing our phone I's covered for one year manufacture warranty that has nothing to do with the carrier.
Sent from my SPH-L710 using XDA Premium App
Click to expand...
Click to collapse
Please do not encourage other members to commit fraud.
Fraud: A false representation of a matter of fact—whether by words or by conduct, by false or misleading allegations, or by concealment of what should have been disclosed—that deceives and is intended to deceive another so that the individual will act upon it to her or his legal injury.
Click to expand...
Click to collapse
Whether or not they do replace it is irrelevant. When you decided to root your phone, you voided any and all claims on your warranty (which covers manufacturers defects only). If all of the people who hard-brick their phones claim it on the sprint warranty, you'll see a drastic increase in one (or all) of the following:
Phone Costs
Plan pricing
TEP Costs
"Premium Data" charges
By "claiming ignorance," you are willfully misrepresenting your situation to Sprint, with the intent to deceive Sprint so that they may pay for your mistake. This, by definition, is fraud. Now, you probably won't be sitting in front of a Grand Jury because of one (or three) replaced phones, but it honestly speaks volumes to your moral character if you see no problem with this.
What you're doing is passing the buck on your mistake off to Sprint. Sprint, in turn, will pass that cost onto us. Please don't recommend this course of action again.

Categories

Resources