I recently received my phone back from Samsung. It was send in to replace external speaker that stopped working for no reason. Samsung fixed the speaker (or replaced it) however my volume keys don't work anymore.
I can get by using any widget or volume slider control to adjust the volume but the problem is I booted into bootloader mode (adb) and tried unlocking bootloader. By default option "No" was highlighted and in order to toggle between "Yes" or "No" volume keys are required and I don't have those working.
Is there any other way to achieve the same control functionality using touch screen to highlight "Yes" or "No" option on the unlock bootloader screen?
Any help would be appreciated. I want to explore some ideas before sending it back to Samsung again or try opening the phone and replace or fix keys myself.
(by the way, I am in US and it took 2+ months for my phone to come back after first repair because expansys-us had to send it back to Samsung UK to get it repaired.)
________________________________________________
Updates:
I wanted to post a quick update on this thread to help out anybody who might run into a similar situation.
So I received my phone back and the note from my shipper (expansys-usa) says that phone couldn't be fixed because the volume key ribbon is ripped off the main board. Now funny thing is that either Samsung or Expansys-USA opened up my phone to repair the external speaker (reason it went out the first time) and when I received it back the volume keys were not working. So much for getting your device repaired by the OEM.
Only way to repair this sort of problem is to change the board which is technically possible but not possible because your motherboard carries information like IMEI etc . They never offered to send me a new phone or anything but just a note saying that ... can't repair. Also, to make things worse, they flashed Yakjuxw (samsung) image on my phone to restore it back to stock. Which killed the updates for me.
Anyways, I kept looking and ran into a post where chainfire posted a thread with roms packaged into ODIN. Now most important thing about this sort of thing is that it unlocks your bootloader in the process. Once I got that things started getting better and better.
I got the ODIN rom. Used the USB jig to initiate download mode, from there I flashed the rom package. Once I got the rom flashed and bootloaders unlocked. I downloaded Gnex toolkit from the main development thread and flashed custom touch recovery.
Well after having custom recovery I was back in the game and the rom flashing game started again. Only difference is that I have to be now very careful before flashing anything because if any rom fails to boot then I am stuck and can't do anything other than to just to break out my USB jig and fire up ODIN and start from zero ... all the way to JB 4.2.
Hope this helps anybody who is or will be facing the same problem (which I hope not).
No, there is no way to unlock the bootloader without the volume and power keys.
But you can still root if you are running 4.0.1 or 4.0.2. See link in my sig.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks efrant for the suggestion. I tried looking into that method but my rom is already updated to the patched kernel version.
So, I have sent it out again for repair. Let's see if Samsung can fix it without giving me anymore trouble.
enaybee said:
Thanks efrant for the suggestion. I tried looking into that method but my rom is already updated to the patched kernel version.
So, I have sent it out again for repair. Let's see if Samsung can fix it without giving me anymore trouble.
Click to expand...
Click to collapse
Demand they pay for shipping, or depending how long you've had your device, that they send you a new one.
Supposedly, its 14 days and they'll ship you a new device as long as you provide credit card info and ship the old one back. I was 21 days in, the power buttons stopped working, and all they could offer me was a repair. Idiots at Samsung (not reps, the ones that tell them what to do/say) told me to call T-Mobile to give me a "loaner" phone while Samsung fixes it.
I immediately said "One, I bought this phone without a contract, so they have no obligation. And two, why should T-Mobile have to deal with me for your faulty device?". Then I told them I would just sell it as is and get the HTC One S since HTC phones don't have these issues, and the rep immediately passed me over to where they set up a warranty phone.
Again, this depends on how long you've had it. Rules say a Max of 14 days, they bent it only a week more for me. I wouldn't expect any more than that.
Sent from my Galaxy Nexus using Tapatalk 2
enaybee said:
Thanks efrant for the suggestion. I tried looking into that method but my rom is already updated to the patched kernel version.
So, I have sent it out again for repair. Let's see if Samsung can fix it without giving me anymore trouble.
Click to expand...
Click to collapse
Although I haven't tested it out, this may work for you:
On the Nexus One, we were still able to flash signed images, even with a locked bootloader. If this holds true for the Galaxy Nexus, you can flash an older version of the stock images (say 4.0.2), then you can root, and once you have root, we have figured out how to unlock the bootloader without the physical keys. I can guide you through it all if you want.
efrant said:
Although I haven't tested it out, this may work for you:
On the Nexus One, we were still able to flash signed images, even with a locked bootloader. If this holds true for the Galaxy Nexus, you can flash an older version of the stock images (say 4.0.2), then you can root, and once you have root, we have figured out how to unlock the bootloader without the physical keys. I can guide you through it all if you want.
Click to expand...
Click to collapse
This signed images tidbit is intriguing. Not that its needed anymore on gnex anyway but who knows when that may come in handy again. Good to know.
Sent from my Galaxy Nexus using xda premium
ian42086 said:
This signed images tidbit is intriguing. Not that its needed anymore on gnex anyway but who knows when that may come in handy again. Good to know.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I finally tried it and It doesn't work on the GNex.
Sent from my Galaxy Nexus using Tapatalk 2
I mainly figured for a future phone model or a friends phone or something it may come in handy. Thanks for response tho sir.
Sent from my Nexus 7 using xda premium
You actually don't need fastboot or volume buttons to unlock the bootloader this way: http://forum.xda-developers.com/showthread.php?p=41612401#post41612401. HTH!
Related
Ok so iv had my GN for four days now and its developed a problem with the power button.
Sometimes when i try to turn the screen on via the power button it wont respond, at first. It happend last night for the first time, i tried to unlock it and nothing happend, then after trying about 5_6 times it rebooted. Same thing happend this morning.
Has anyone else had this problem?
Does anyone think this could be software or hardware issue?
The phone is completely stock running 4.0.1 on tmoble uk.
Anyones help or opinion would be appreciated.
Try updating to 4.0.2 before you write it off as hardware problem.
Sent from my Galaxy Nexus using xda premium
Thought about that but it would mean rooting , my fear is that it becomes permenant , then my warrenty would be void , i did have it on face unlock when this was happening i have now changed to slide and as yet ive had no problem , i will post here if the problem is fixed for anyone who is interested
I thought the stock build is 4.0.2?
Have you tried pinging for an update in the settings menu?
Sent from my LTE Galaxy Nexus using xda premium
Rooting is not permanent. You can remove it by delete the SuperUser apk and binary; that's what root is. Or if you're paranoid, flash a stock image.
Then lock the bootloader. Hooray, your device is stock.
mwestendorf said:
I thought the stock build is 4.0.2?
Have you tried pinging for an update in the settings menu?
Sent from my LTE Galaxy Nexus using xda premium
Click to expand...
Click to collapse
yeah several times, and its defo 4.0.1
chirea.mircea said:
Rooting is not permanent. You can remove it by delete the SuperUser apk and binary; that's what root is. Or if you're paranoid, flash a stock image.
Then lock the bootloader. Hooray, your device is stock.
Click to expand...
Click to collapse
Yeah i do understand that, my fear is while rooted that the problem becomes permanent (at least for me) then while off for repairs they see that its rooted and tell me to get lost!
Iv had a few problems with this phone like locking up while adding widgets to home screen, locking up half way though a phone call, browser hanging all the time and of course the power button all of which resulting in a battery pull.
Id come to expect this kind of behavior over the last year & 1/2 from my hd2 as it wasnt ment to run android in the first place, but this is a google flagship.
Maybe i just got a dud or maybe its the stock 4.0.1 has anyone on custom rom had any of the above problems?
i think the point is that you can unroot it and they cannot tell the difference that it was ever rooted in the first place. and get your warranty fix.
RogerPodacter said:
i think the point is that you can unroot it and they cannot tell the difference that it was ever rooted in the first place. and get your warranty fix.
Click to expand...
Click to collapse
Yes, but his point is if the power button becomes unresponsive while he is attempting to root/unroot the phone then he wont be able to complete the process.
I haven't experienced anything like what you're describing on my Galaxy Nexus, even while I was running 4.0.1. Does the power button only become unresponsive when you're turning the phone on/off? Or does this happen while trying to lock/unlock the phone as well? If it only happens while you're using the face-unlock feature then it could be a software bug and flashing could fix it...
I would call either Samsung or your carrier about it before deciding to root/flash it myself. Perhaps your carrier will just switch it out for another one they have in stock.
I have experienced this problem as well with the power button. I have the GSM version and I haven't received the 4.0.2 update but I did receive the ITL41F update. After about three or four presses of the power button it becomes responsive again. I think you might be getting the resets if you press the power button repeatedly without waiting a few seconds I'm between presses to get it responsive again. I also do not think it is hardware related and may be some kind of software bug. I am waiting patiently for the updates.
Sent from my Galaxy Nexus using XDA App
Kinbote said:
Yes, but his point is if the power button becomes unresponsive while he is attempting to root/unroot the phone then he wont be able to complete the process.
Click to expand...
Click to collapse
yes thats exatly my point, although i really am leaning toward software as tk123456789 pointed out if i wait a few seconds it will come on though only after i got rid of the face unlock, using face unlock it was a lot worse. Im thinking if it were hadware it would either work or not,
BTW this problem is when i unlock the phone and not when turning it on, i dont think i made that clear.
my power button has stopped working....it only works sometimes but it usually acts like im holding it down....if i pull the battery and put it back in, it boots up by itself and i dont even press anything...idk what to do and im freaking out
I wonder if this is becoming a known problem with Samsung devices. Do me a favor and shake your phone a few times. Try it every now and then until it wakes your phone or the power menu pops up. Means the switch is busted and the contact is floating around. This is what was going on with my Captivate and I haven't found a fix, nor do I want to solder on a new power button.
I left it in rice overnight and now everything is working perfectly! Hopefully it stays that way! It may have gotten wet from my XO skin application! Never ever ever again with a wet apply! NEVER!
Edit: its still doing the same thing again...spoke too soon
sent from my Nexus Prime
I got my GSM Unlocked Galaxy Nexus from the Play Store two days ago and am experiencing the same issues with the power button. It worked fine for the first 24 hours.
I'm on the phone with Google right now to get a replacement phone which is nice because they're contacting Samsung on my behalf.
(I'm within the 14-day replacement policy for new devices)
Flash manually the official 4.0.4 IMM76I.. And relock your bootloader after that and try.. Thats it
Sent from my Galaxy Nexus using xda premium
similar Issue:
I bought a used, rooted Galaxy Nexus. Due to my own (drunken) stupidity not long after my purchase I caused a scratch on the glass covering the display. As I did not want to pay for a out-of-warrenty repair, I left the device as it was.
Some time after, my power button became unresponsive. As it took 3-5 presses to activate the screen I installed the app "PGM Galaxy Nexus" that allows to wake the device with a swipe gesture. Not to long after, the power button stopped responding all together. While researching a permanent solution, my battery died.
In order to be able to use my phone as soon as possible, I brought it to a local (and unfortunately, unauthorized) repair shop. The repair shop tested quicky for any further defects (by plugging the phone into a wall charger - I had done the same at home) and quoted me 50€ for the repair. Some time after, they emailed me that the replacement of the power button did not repair the device. They said however, that the "main power supply IC" is most likely at fault and that a replacement would cost about 120€. As I could not find this chip in the teardown pictures at ifixit, I am not sure if I should invest further trust in the repairshop. In addition and as writen above, charging the device was no problem at all. In fact, I charged the battery that was in my Galaxy Nexus to 100% before bringing it in.
This is where my questions start:
1.: Is a defect of the "main power supply IC" a known defect at all? If there are known defects of the "main power supply IC" are those defects linked to a faulty power button?
2.: Currently, my plan of action is to collect the device and contact Samsung to have it repaired by Samsung itself. Does this mean sending it in? Do they have authorized repair centers like Nokia used to have (NSC) where I could just bring it in?
3.: What might the cost of the repair be? Can it be noticed that the device was opened before? Is root a problem when sending it in for repair?
I would be greatly thankfull for any device and in case I forgot to provide any details, please feel free to ask.
Related Information:
Galaxy Nexus GSM unlocked, bought in Germany
Android 4.2, running no custom firmware but rooted
Purchased by the first owner on 24th March 2012
Running on E+ (simyo) and o2 networks
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
xThaNaturalx said:
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
Click to expand...
Click to collapse
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
aybarrap1 said:
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
Click to expand...
Click to collapse
Absolutely true, but if its not the battery the atat rep will point you to an atat service center for assistance and its a safe bet that they have a few more tools at their disposal to troubleshoot the phone. If they somehow see any system modification, you are capital F****d. Do you have the wireless insurance with atat? I just dealt with this except I dropped the phone, shattered the screen and it would only power on for 10 mins at a time and then reboot. I paid my $$$ deductable and sent the broken phone to the insurance provider and yes the system still showed as being "modified" when I sent it to them.
Sent from my Atat S3 that now thinks its a Galaxy Nexus........
I would send your s3 to Samsung if it still under warranty. I sent over my bricked s3 and they fixed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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
I finally was forced to update to android 5.0.1. I updated at work but it failed halfway through and is now in a boot loop. I've tried every solution the internet can provide me. What do I do now? The device IMEI has a limited warranty until 2017. I purchased through swappa. I have original box but no documentation besides the barcode sticker on the side. Will AT&T replace this? It was their update that caused this anyway. Any experiences with this sort of thing please? I dropped a large chunk of change on this paperweight. Thanks
Wildstar34 said:
I finally was forced to update to android 5.0.1. I updated at work but it failed halfway through and is now in a boot loop. I've tried every solution the internet can provide me. What do I do now? The device IMEI has a limited warranty until 2017. I purchased through swappa. I have original box but no documentation besides the barcode sticker on the side. Will AT&T replace this? It was their update that caused this anyway. Any experiences with this sort of thing please? I dropped a large chunk of change on this paperweight. Thanks
Click to expand...
Click to collapse
The first thing to do is find a local Best Buy with a Samsung Experience shop. They can reflash the firmware or send the phone in for repairs. This would be the best and easiest option. Most likely, you'll be able to get everything fixed in around an hour max.
BTW, it doesn't matter if the device was purchased from somewhere other than Best Buy!
I'm not sure if ATT will replace the phone if you didn't buy it from ATT. You can contact them to see though. Call them and tell them that you bought the device from Swappa. Though, most likely, they'll turn you away unless they have some sort of business alliance with Swappa.
Do this as a Plan B.
The third option is to get in contact with Swappa. I don't know anything about that service though. Usually in order to claim warranty, you need the device and proof of purchase. If Swappa has an online receipt, or even just an online purchase history, that should work. They most likely would just need some sort of proof that you actually bought the device from or through them. Like I said, I don't know anything about Swappa, so you'll have to contact them to get specifics of what you'd need.
When all else fails, go directly to Samsung. Again, tell them that you got the device from Swappa. Though, this would basically be like the first option, except that it would take longer.
All options except the first one may result in you getting a refurbished replacement. Just an FYI. The only way that Best Buy will give you a refurbished replacement is if they were to send the phone back to Samsung and it was replaced.
PM me if needed!
Sent from my SM-P600 using Tapatalk
spexwood said:
The first thing to do is find a local Best Buy with a Samsung Experience shop. They can reflash the firmware or send the phone in for repairs. This would be the best and easiest option. Most likely, you'll be able to get everything fixed in around an hour max.
BTW, it doesn't matter if the device was purchased from somewhere other than Best Buy!
I'm not sure if ATT will replace the phone if you didn't buy it from ATT. You can contact them to see though. Call them and tell them that you bought the device from Swappa. Though, most likely, they'll turn you away unless they have some sort of business alliance with Swappa.
Do this as a Plan B.
The third option is to get in contact with Swappa. I don't know anything about that service though. Usually in order to claim warranty, you need the device and proof of purchase. If Swappa has an online receipt, or even just an online purchase history, that should work. They most likely would just need some sort of proof that you actually bought the device from or through them. Like I said, I don't know anything about Swappa, so you'll have to contact them to get specifics of what you'd need.
When all else fails, go directly to Samsung. Again, tell them that you got the device from Swappa. Though, this would basically be like the first option, except that it would take longer.
All options except the first one may result in you getting a refurbished replacement. Just an FYI. The only way that Best Buy will give you a refurbished replacement is if they were to send the phone back to Samsung and it was replaced.
PM me if needed!
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks a lot. This may be the single most helpful forum post I've ever read. I will drive up to BestBuy tomorrow and give it a shot. I wasn't able to flash a AT&T stock rom through Odin, but I guess it's worth a shot. I believe the flash failure was due to the AT&T bootloader being locked?
Wildstar34 said:
Hey, thanks a lot. This may be the single most helpful forum post I've ever read. I will drive up to BestBuy tomorrow and give it a shot. I wasn't able to flash a AT&T stock rom through Odin, but I guess it's worth a shot. I believe the flash failure was due to the AT&T bootloader being locked?
Click to expand...
Click to collapse
Welcome!
Most likely something just went wrong during the installation. The bootloader is not a factor in this matter since all ATT Note 4s have it locked and the firmware is meant for this phone.
Now, if you had the phone rooted (permanently), installed a custom kernel and recovery, etc, then the update failure would be 100% explainable. But since you can't do any of that with this phone, then the most likely cause is just "sh1t happened" or the installation was interrupted (like battery died).
Sent from my SAMSUNG-SM-N910A using Tapatalk
Have you tried kies to reflash your phone?
floatingtrees said:
Have you tried kies to reflash your phone?
Click to expand...
Click to collapse
I used Kies, Kies3 and Swap Sync or whatever to do an emergency restore. All of them failed. Kies 3 recognized the phone and was 98% done downloading the firmware and then failed.
Also i am not rooted and never attempted a root (on this phone anyway).
Good news. Just got off the phone with AT&T and they have a replacement on the way. Thanks for your help everybody. We have achieved the best case senario for me as i was having problems with the volume buttons anyway
I would consider this case solved.
Wildstar34 said:
Good news. Just got off the phone with AT&T and they have a replacement on the way. Thanks for your help everybody. We have achieved the best case senario for me as i was having problems with the volume buttons anyway
I would consider this case solved.
Click to expand...
Click to collapse
Awesome! Win-win for you (I guess?)
If the volume keys were messed up, then I wonder if there was some other problems with the phone too. Ones you couldn't see... ones that prevented proper firmware installation.
Sent from my SM-P600 using Tapatalk