cliffs at end
Nexus 5 in boot loop.
Almost all sources point to power button being the issue.
Finally call a local place ( AZcellphones in Tempe AZ) that says: 20 dollar diagnostic, 39 total if its software, 49 if its hardware. I take it in the next day.
Two days later i call the guy and he says. its fixed, the software was bad you owe me 30 bucks. Uhm you said 39 total if software( i already knew i was going to have an issue with this guy so i didn't say anything on the phone.
( i am going to digress here for a bit) I go in the following day i stop in, and explain id like to pick up the Nexus5, he brings it out hands it to me and says 30 bucks, it wont boot. Hold on i said, i want to see it run, battery is dead. Plugs it in, i start it and it starts to boot and begins the "optimizing apps routine".
By now the owner is over at his desk and the the tech is standing behind the counter explaining to me, "its just updating, i load the oldest factory image of android and then it take a couple boots for it to update.
Ok, fine, lets watch it do just that, i happen to have an identical N5 with me that is fully updated, i check its at version M. "broken" N5 finishes boot and seems to be working fine, i check version, still not current, check for software update and it finds on and starts the download and reboots, seems legit so far.
This is where things start to get hairy... as the N5 starts the optimizing apps routine again for this update, the owner get up and comes over to the desk and start telling me, "This is normal, why are you wasting our time, its going to work, why don't you just take it home and and let it finish updating on your wifi instead." I was floored.
are you kidding dude?
Cmon man just give me the 30 bucks and get the F%&* out of here.
WHAT?
listen i say, first of all, you told me that the charge was 20 for the diagnostic, and a total of 39 if it was software, so at best i owe you 19 PLUS you didn't finish the job.
BUT to top it off i never gave the ok to repair, the receipt even say "diagnosis please"( which i show him). You are a Liar he says, i never told you 39 give me the 30 bucks and the receipt( my copy) and go away( hes holding the phone).
NO chance.
Now im pissed and i dont really give a crap and i tell him i didn't authorize the repair but i ll give you 10 extra for it.
F( you he says. you just wanted it diagnosed? He hands the phone to the tech and say "BREAK THE F&$%#* PHONE", turns to me and says, you will get it back the way you brought it in, Tech now has the phone, and i am on my phone with the non emergency police line.
I explain to them that i am at a local repair facility, the owner did some unauthorized repair on a device and he is no strong arming me for payment. They send and officer, while i wait he tells me to get out of his store its private property and im trespassing, it tell HIM to go F$#% him self. (Tech has back of phone open and is fiddling with a screw driver). I say , that thing better boot loop when i get it back or you are going to have a problem. ( i figured he just hosed it completely) He says "ill call the cops" i said, ill already did they are on the way. Silence.
So, officer arrives, i explain the situation, she explains to me that unfortunately this is civil, not a lot she can do but goes inside with me **** for brains is all nice hands me my phone back that flashes the google logo and the goes black. Tech explains to officer that he just removed the software that they installed. We go outside , i apologize for wasting her time and she says..Did you Yelp this place? Nope, you should have ( she is very nice about it)this isnt the first time ive had problems here with this guy, lesson learned i guess.( i yelped them and sure enough, loads of crappy comments)
http://www.yelp.com/biz/azcellphones-tempe-2
So back to my question: I connected this phone to my computer via usb cable and it inst recognized even when boot looping.
How did the tech get access to it and how do i get access to it or am i SOL?
Cliffs, N5 was boot looping Tech did unauthorized software( factory image flash) repair which they reversed.
To add: i posted this on reddit as well and got a lot of help first it was trying to use Wugfresh Nexus tool kit which didnt seem to work other than unlock the boot loader and i was walked through and learned on the fly how to flash from command prompt and manual flashed 5.1.1 (LMY48I) along with TWRP for this unit.
all that said , the phone will not power up when not connected to usb. when connected to usb it cycles between the google logo and a white battery indicator, i can get into bootloader but any choice i make( like boot into recovery) starts the cycle again.
From the story above, when the tech had the phone after the owner told hi to break it, i think he opened the back up and did something to it. ive looked and cant see anything obvious.
any suggestions?
There are a lot of terms you misused above, I don't mean to be rude about it but it makes it hards to understand your problem.
with that said, back up your personal files and follow this guide Tutorial How to Flash Factory Image
If you any more trouble let me know.
appologies for the misuse of terms as i am a novice, BUT over the course of the last few days i have done the following..
since i could get to the boot loader when on usb i:
Learned to use WUGfresh Nexus tool kit, unlocked the boot loader and flashed a factory image.
Phone remained unusable as it would just go into this weird cycle of flashing the google logo and showing the battery indicator as long as it was plugged into usb, as soon as it unplugged, it went dead.
So i learned to manually flash the image files similar to the link you provided.
Flashes all finished with no errors yet the phone remained int he same weird cycle.
I started to suspect something else( especially after remembering the tech had the back off the phone to "break it" form my story)
So today i opened it up and found the issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tech cut the connector off the ribbon cable of the battery.
So i ordered a new battery of amazon, that will resolve the issue.
Consider yourself lucky damaging the battery was all he did. It could have been so much worse.
So now you're out much more than the extra 19 dollars? I'm not sure that was worth all the hassle. I would have pushed the 19 then complain to police or whatever. Then just reverse charges on cc. I know that's not how it should work, but if it's something you care that much about 19 dollars seems pretty trivial. All that said your power button works fine now?
frigidazzi said:
So now you're out much more than the extra 19 dollars? I'm not sure that was worth all the hassle. I would have pushed the 19 then complain to police or whatever. Then just reverse charges on cc. I know that's not how it should work, but if it's something you care that much about 19 dollars seems pretty trivial. All that said your power button works fine now?
Click to expand...
Click to collapse
im not out more than the extra 19, the new OEM battery was 12 bucks shipped.
I actually did try to pay him the 19 dollars he refused and said i owed him 30, that how this went downhill. I took it in expecting that it was the power button, wasn't sure, he said it was a software issue and though i was skeptical, it was working, for a bit.
And hopefully the battery is the only things he hosed, i don't see anything else glaringly obvious and if so i AM lucky.
Though, i am a clever and determined individual, he hasn't heard the last of me in one form or another.
Received the new Battery, installed and the N5 booted up without issue.
The entire boot loop was cause by the battery cable being cut by that POS.
So fresh factory image, latest TWRP and rooted.
Related
Hey, Just thought I should post this... To reset the Captivate without removing the battery, there is a connection on the board called "TP". It is right below the MMC card and you can barely see it with the phone's case on it. Here is a picture of the rear case removed. The TP is the white dot. It is covered with white paint to avoid accidental connection.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can stick a needle through and ground "TP" to the side of the SDCard. Your phone will reset.
It's a signal line. and it's separated from bat+ by 1000ohms.
Thats very useful. Thanks!
Will this reset work on "soft" bricks and/or paperweight states?
Sent from Gingerbread on a Captivate using XDA Premium App
It will work on soft bricks. I'd like to see how a hard brick would react to UART communications. I've got one comming, so I will be able to tell you more soon.
This is a great find for flashing addicts. Thanks so much for sharing this. When I get to my PC I will hit the thanks button.
Sent from Gingerbread on a Captivate using XDA Premium App
I've found it quite useful... but I've been doing some non-standard things with my phone...
That looks sick! Someone's been having fun. Has your phone orbited the Earth yet?
Haha not quite... I've been researching non-invasive methods of recovering bricks, and it requires invasive techniques for analysis. Its amazing how many people brick their phones and how expensive jtag methods are.
Doesn't work on Hard Bricks. Tested.
So is it possible to fix a soft brick using this method instead of making a jig?
On my way home right now, guess I will find out soon enough, thank you
Wasn't quite sure what it was gonna do, and hoping it would magically get me into download mode, where the usb or power wouldn't. big down side, it botch'd something in my hardware, and my battery will no longer charge, can not run the phone without being pluged into the wall or pc. unbricked using a standard ol jig, flashed to 2.1 via 1 click, dunno if it just fried battery or did something else. Any ideas what to trouble shoot first? i've tried reflashing, few different roms, tried reseting battery stats, tried factory reset via settings, and via 1 click with no luck, wont be able to test another battery till tomorrow
bloodforge said:
Wasn't quite sure what it was gonna do, and hoping it would magically get me into download mode, where the usb or power wouldn't. big down side, it botch'd something in my hardware, and my battery will no longer charge, can not run the phone without being pluged into the wall or pc. unbricked using a standard ol jig, flashed to 2.1 via 1 click, dunno if it just fried battery or did something else. Any ideas what to trouble shoot first? i've tried reflashing, few different roms, tried reseting battery stats, tried factory reset via settings, and via 1 click with no luck, wont be able to test another battery till tomorrow
Click to expand...
Click to collapse
You did something else....
I used this method about 50 times consecutively. No ideas for you on your issue.
This reboots the phone and that's it. Its easy for bench testing purposes. How long did you hold it?
Just until the screen shut off, then released, not really what sure happened. Is there something rom side that controls the charging of the battery or is it strictly hardware?
Just hoping battery just decided to die, needed excuse to get a bigger one anyways.
Edit-Yeah definetly thinking battery is bad now, it showed 100% charge this morning finally, but as soon as i unplugged from wall it died, plugged it back in and was showing it dead again. Soo hmm, dunno sound like bad battery? fixin to make the 30min trip to ATT store to see if they can check it or swap it.
just wanted to say, i wasn't trying to imply the reset you pointed out had killed the phone, i just wasn't quite sure what happened, and this had been one of the last things i had done.
I just didn't realize a battery could go that quickly, had it tested today, and the guy at store said i was the first person he could tell without a shadow of a doubt there battery was dead.
1500mAH battery, and it read dead at first then full charge on tester at 28mAH.
This looks very interesting and I would like to try it out. Before I try it, I was wondering if you could explain it more in depth like if the battery should be in the phone, if it is necessary for the battery to be fully charged and if this method will work on all Captivates. I also noticed a number on your sd card slot that is different than mine but I assume all phones have a different one. Thanks in advance
So I'm kind of stuck. I was on the ICS OTA update (stupid move, I know) and I attempted to flash to CM10 (probably an equally stupid move), and the flash proceeded for awhile, but ended up failing. So now I can't access bootstrap, and I'm essentially stuck in a soft brick. In Fastboot flash mode I can't get it to connect via USB, so there's no real hope of FXZing to anything as far as I know.
Do I just call it quits, or is there something I can do? :| I need an adult.
Kay, a little more info is required.
You're on the official OTA? If so, you're stuck mate. There are a couple of semi writing ways to get out of this, you just gotta search and read.
This is why we recommend against the ota update man.
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
Kay, a little more info is required.
You're on the official OTA? If so, you're stuck mate. There are a couple of semi writing ways to get out of this, you just gotta search and read.
This is why we recommend against the ota update man.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yeah, I OTA'ed to the official without thinking, before I checked the forums. Wasn't even thinking about the fact that there might not be an fxz.
I've been reading up and researching for a couple hours, but I still can't find a way to get it to connect via USB in fastboot. :| Have you come across anything that might actually help? Realistically I think it's still under warranty, and we have an AT&T wireless device help center thing here that does same day warranty exchanges, so I think I'm probably just going to go there tomorrow and tell them my phone died during the OTA update and now it won't turn on all the way. Does that sound believable at all? haha They're usually pretty lenient anyway, I got a warranty replacement there on my Atrix 1 and they gave me a bad battery, and when I came back in do get a replacement the guy noticed I was running CM7, and said something jokingly about how "yeah the battery was bad, but the ****ty CM7 port probably didn't help much". lol
Joewee3 said:
Yeah, I OTA'ed to the official without thinking, before I checked the forums. Wasn't even thinking about the fact that there might not be an fxz.
I've been reading up and researching for a couple hours, but I still can't find a way to get it to connect via USB in fastboot. :| Have you come across anything that might actually help? Realistically I think it's still under warranty, and we have an AT&T wireless device help center thing here that does same day warranty exchanges, so I think I'm probably just going to go there tomorrow and tell them my phone died during the OTA update and now it won't turn on all the way. Does that sound believable at all? haha They're usually pretty lenient anyway, I got a warranty replacement there on my Atrix 1 and they gave me a bad battery, and when I came back in do get a replacement the guy noticed I was running CM7, and said something jokingly about how "yeah the battery was bad, but the ****ty CM7 port probably didn't help much". lol
Click to expand...
Click to collapse
I don't know why it wouldn't be working in fastboot. try reinstalling drivers if you are on windows.
If you can get an exchange do it, just play dumb, and you'll be fine. I hardbricked when the first ICS hell hit (kind of on purpose, I had a problem that they would not replace for) testing some stuff for how to get back, and I brought it in and just acted sad and said I took it off the charger and it wouldn't turn on. I had a new one in a week.
P.S. I have done much stupider things, so don't worry, you are far from alone.
Thats acually the same thing I said when I flashed the razr developer edition of mbmloader. Just say that the OTA failed and trust me in order to get a new phone
Cheers and good luck!!!
Joewee3 said:
So I'm kind of stuck. I was on the ICS OTA update (stupid move, I know) and I attempted to flash to CM10 (probably an equally stupid move), and the flash proceeded for awhile, but ended up failing. So now I can't access bootstrap, and I'm essentially stuck in a soft brick. In Fastboot flash mode I can't get it to connect via USB, so there's no real hope of FXZing to anything as far as I know.
Do I just call it quits, or is there something I can do? :| I need an adult.
Click to expand...
Click to collapse
I stupidly did the same thing as the OP :/. I need to get a replacement and my device is under warranty. How do i proceed? When booting up the device says "Cyanogenmod", so I don't really want to get caught with that! Any help would be appreciated. Thanks!
007bond said:
I stupidly did the same thing as the OP :/. I need to get a replacement and my device is under warranty. How do i proceed? When booting up the device says "Cyanogenmod", so I don't really want to get caught with that! Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Attempt at your own risk:
Take out the phone's battery, and find a couple of lead wires with small alligator clips on both ends. Then, attach the negative black lead wire to a 12v lantern battery (you can find these just about anywhere) and to the negative terminal of the phone. Then attach the positive red lead wire to the battery, and then just touch the end of the positive lead wire to your phone's positive terminal - only takes a second. This will fry the motherboard completely, and it will never turn on. Contact Motorola via their website and open a warranty exchange ticket. They'll send you an email with a shipping label to print, affix to your shipping box, and just drop it off to any FedEx pickup location. I got mine back in less than a week.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my rooted Mayan calendar
Apex_Strider said:
Attempt at your own risk:
Take out the phone's battery, and find a couple of lead wires with small alligator clips on both ends. Then, attach the negative black lead wire to a 12v lantern battery (you can find these just about anywhere) and to the negative terminal of the phone. Then attach the positive red lead wire to the battery, and then just touch the end of the positive lead wire to your phone's positive terminal - only takes a second. This will fry the motherboard completely, and it will never turn on. Contact Motorola via their website and open a warranty exchange ticket. They'll send you an email with a shipping label to print, affix to your shipping box, and just drop it off to any FedEx pickup location. I got mine back in less than a week.
Sent from my rooted Mayan calendar
Click to expand...
Click to collapse
Also if you have a car battery charger, set it at a 2AMP charge and connect it the same way ^^, for a min or 2 and it will all be over... it does not matter what phone you have that will do the job just fine. If you send a phone that only needs 2 volts to charge, a 14 volt 2 amp signal, it will be dead. Just make sure the battery is not in the phone when you do this, that will be VERY bad.
I am just saying, and do this very carefully, this can hurt you, if not done correctly.
I wasn't daring enough to follow those steps, so I decided to be creative and use this guide:
http://forum.xda-developers.com/showthread.php?t=1935485
Essentially, I did everything but flash the OTA. It didn't fix my issue completely, but it did stop my phone from showing the CyanogenMod logo. I then called AT&T and asked for a replacement I told them that the OTA stopped my phone from booting. They gave me free priority shipping and it arrived this morning (ordered yesterday afternoon).
So i've recently come back again with an issue i had before with my S2 where i had an issue of it randomly shutting off then vibrate. Back then i just restock to ATT and made sure the power button wasn't stuck. It wasn't happening for a while until just yesterday. [ I did go back to Jellybean after the problem stopped happening as well]
Now currently i've restock back to ATT 2.3 /
So now im almost positive it isn't my battery because once that problem started happening [still stocked] again. Also it would randomly shut off when im and listening to music with headphones and emit a high freq. pitch and the LED camera was flashing when it vibrated as well. Its also very hard to get it back to recovery/download mode but i can and also just starting it up again with the power button and i have to also take out the battery as well .
So so far i've gone back ATT with Odin, and was wondering if someone could help me.
You restored to stock 2.3? Gingerbread? I've only experienced this when uninstalling apps on jellybean, particularly apps with root access. Will do a hot boot. Likely because the system is not mounting or unmounting properly during process. I assume. Never once have I experienced this on any ICS Rom. Try Sky ICS or Embryo 5.x.x Rom. They're both pretty stable.
Sent from my SGH-I727 using xda premium
aliysared said:
So i've recently come back again with an issue i had before with my S2 where i had an issue of it randomly shutting off then vibrate. Back then i just restock to ATT and made sure the power button wasn't stuck. It wasn't happening for a while until just yesterday. [ I did go back to Jellybean after the problem stopped happening as well]
Now currently i've restock back to ATT 2.3 /
So now im almost positive it isn't my battery because once that problem started happening [still stocked] again. Also it would randomly shut off when im and listening to music with headphones and emit a high freq. pitch and the LED camera was flashing when it vibrated as well. Its also very hard to get it back to recovery/download mode but i can and also just starting it up again with the power button and i have to also take out the battery as well .
So so far i've gone back ATT with Odin, and was wondering if someone could help me.
Click to expand...
Click to collapse
Can you get me a copy of the info tag under the battery please? There was a series (which I had 3 of) that had the same hardware issue that you are experiencing. I'm not near my SR of the series, but will look when I get home and post. It is however an issue that AT&T and Samsung are aware of. AT&T gave me a GS III due to the issue.
risondi 1650
Edit: I see!
aliysared said:
Sure:
Model: sgh-i727
fcc id: a3LSGHi727
Rated 3.7 1500ma
IMEI:
S/N : R2CBA64411R
SKU: 65319
Click to expand...
Click to collapse
Well that looks like it was from a different batch. Same factory but different batch. Most likely you have the same hardware issue I had. My recommendation is to contact AT&T via PHONE, not the international line. You don't want warranty dept. Tell them that you are on a Sky Rocket, and that this is your "x" one that was under warranty, and that all "x" of them have failed under the same known hardware issue. The options you will have are either get a replacement, file under any extended warranty you purchased, OR you can tell them that it is unacceptable, and you would like a different device. They cannot offer you a note, note 2 or any of the iphones. I opted for the S III, and have been happy ever since.
Just so you know it is not the best idea to post you're IMEI publicly.
hechoen said:
Just so you know it is not the best idea to post you're IMEI publicly.
Click to expand...
Click to collapse
man now i cant even remove it from the other users qoute, but i think i found out it is the powerbutton because when i eventual am able to boot up my phone, if i press the powerbutton to wake up it , it then a few seconds later will shut down randomly and start vibrating with either the flash or no flash at all [camera LED] also it seems like my phone was wet and the power button is not stuck because i opened up the entire phone and its still clickable with no problems.
aliysared said:
man now i cant even remove it from the other users qoute, but i think i found out it is the powerbutton because when i eventual am able to boot up my phone, if i press the powerbutton to wake up it , it then a few seconds later will shut down randomly and start vibrating with either the flash or no flash at all [camera LED] also it seems like my phone was wet and the power button is not stuck because i opened up the entire phone and its still clickable with no problems.
Click to expand...
Click to collapse
Done did, well get a dental pick (not a tooth pick) and gently clean around the edges of the power button. When you do get it powered back up, make a backup to your sd card, JUST IN CASE you need to send it back to sammy.
I dunno if I'm having something similar happen. My phone was working completely normally (CM 10). Working this AM ok, I pull up an email, and then it shuts off, tries rebooting, the Samsung logo comes up, I get a brief flash on the screen (sometimes just a single line that varies in position on the screen) and then it keeps vibrating. Never had this happen before....and of course it happens as I am at the airport without my laptop to try and put it into download mode...I can't even get it into recovery. Ugh!
Any thoughts?
jslanger said:
I dunno if I'm having something similar happen. My phone was working completely normally (CM 10). Working this AM ok, I pull up an email, and then it shuts off, tries rebooting, the Samsung logo comes up, I get a brief flash on the screen (sometimes just a single line that varies in position on the screen) and then it keeps vibrating. Never had this happen before....and of course it happens as I am at the airport without my laptop to try and put it into download mode...I can't even get it into recovery. Ugh!
Any thoughts?
Click to expand...
Click to collapse
sticky power button, 1stop sticky has a few links for that problem
Or take the phone apart and clean it. Its not hard like 6 00 screws and a box cutter then its really easy to clean.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what the power button looks like
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Thx. I did take it apart. Luckily I had a micro screwdriver for glasses with me, since I am out of town. Took the board off, blew into it, pressed the button a bunch, etc. Seems to be working now.
Sounds like this is not an uncommon problem though. Makes me wonder about the quality of the parts... This phone is just over a year old, and has always had a case on it (though I do keep it in a pocket so there could be some lint working its way in).
I am a novice at taking this phone apart, and I managed to do it with the following:
An old laminated Blockbuster video card
A hotel door key
A glasses flathead screwdriver.
So if you are nervous about taking it apart, don't worry... It's not hard.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I rooted my Verizon Galaxy S III a long time ago (at least 6 months), and never really did anything with the root (it was running the most recent Touchwiz that updated a few days before this happened). A few days back, after leaving my phone on and plugged into a wall charger the night before, I woke up to it being nonresponsive. This has happened before, so I removed the battery and put it back in. It booted fine, but with the time in the upper corner an hour fast. I thought that was weird, so I decided to reboot it. I started to reboot it and then turned away to take a shower. When I get out of the shower, I discover that the phone is now hard bricked and will not boot in any mode (download, recovery, normal). It won't respond to anything. The only thing that it will do is illuminate the red LED when it is plugged into the wall without a battery for about 90 seconds (then, when you put in a battery, it won't do anything). When I plug it into a computer, all that comes up is that "QHSUSB_DLOAD" popup.
My family has GS3's as well, so I tried swapping out the battery and charger. That doesn't change anything.
So I decided to go ahead and call verizon, and the replacement phone came in. Now, however, realizing that my phone used to boot up to a Samsung screen with a lock and "Custom" below it, and it looks an awful lot like I hardbricked it myself, since it's rooted, I question whether or not I will get charged that $600 if they think that I killed my phone (which I think I didn't, but I AM a noob).
My question to you knowledgeable people is: Do you think it is safe to send it to Verizon as it is? Is there anything I can do to make it safer to send in? Or should I send back the replacement phone and look for a $250 used one on craigslist?
TL;DR It looks like I hardbricked my rooted Touchwiz GS3 when I didn't. Is it safe to send it into Verizon's Warranty Department?
Check this out http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Definitely cheaper than buying a used device. I don't think I would send in a sgs3 that has that "custom" display on it. If you took it into verizon, they wouldn't replace it after seeing that it has been modded. I would think as soon as they see that in their facility, they would charge you for the replacement. I don't know for sure but that would be my guess. I wouldn't risk getting charged $600. Though maybe someone can help you troubleshoot it more but it definitely seems bricked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.everyjoe.com/files/2007/03/cellphoneart4.jpg
tu3218 said:
Check this out (URL)
Definitely cheaper than buying a used device. I don't think I would send in a sgs3 that has that "custom" display on it. If you took it into verizon, they wouldn't replace it after seeing that it has been modded. I would think as soon as they see that in their facility, they would charge you for the replacement. I don't know for sure but that would be my guess. I wouldn't risk getting charged $600. Though maybe someone can help you troubleshoot it more but it definitely seems bricked.
Click to expand...
Click to collapse
I am of the understanding that JTAG brick repair is aimed at solving problems arising from software, but I suspect that this is a hardware issue (seeing as there were about 6 months between the root and the brick) that wouldn't be fixed by that.
IF it does'n;t boot at all, I doubt Verizon will spend the time to do anything with it other than send you a replacement. As long as you didn;t drop it in water.
DigitalMD said:
IF it does'n;t boot at all, I doubt Verizon will spend the time to do anything with it other than send you a replacement. As long as you didn;t drop it in water.
Click to expand...
Click to collapse
The water stickers still show purple X's, so I'm not worried about that. I'm more inclined to agree with you than tu3218. And it looks like I'll need to brick a few more phones before I can get that earlier work of art going. Haha.
Triforce11 said:
I am of the understanding that JTAG brick repair is aimed at solving problems arising from software, but I suspect that this is a hardware issue (seeing as there were about 6 months between the root and the brick) that wouldn't be fixed by that.
Click to expand...
Click to collapse
Well you could email the folks at Mobile Tech and get their input on this. I wouldn't necessarily rule them out entirely just cuz you didn't hard brick it yourself.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
Well you could email the folks at Mobile Tech and get their input on this. I wouldn't necessarily rule them out entirely just cuz you didn't hard brick it yourself.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Not a bad idea. I'll shoot them an email and post whatever they say here. If anyone else has any input though, I'd be glad to hear it.
If all fails put in microwave for 15-30 seconds and you will be good for exchange.
Sent from my can on a string using Tapatalk 4
Triforce11 said:
The water stickers still show purple X's, so I'm not worried about that. I'm more inclined to agree with you than tu3218. And it looks like I'll need to brick a few more phones before I can get that earlier work of art going. Haha.
Click to expand...
Click to collapse
AS bad as Verizon is in most regards, they really can't afford to accuse everyone that comes in with a dead phone of breaking it and refuse to honor the warranty.
QHSUSB_DLOAD = hard brick
jtag is aimed at fixing a software problem, but more specifically your base coding of your phone. Technically, a hard brick isn't always a hardware malfunction (although it can be), but your base coding to your phone which tells it to boot at its most essential level.
Getting that message when you plug it into your computer means your phone is unrecognizable. It's trying to read what you're plugging in, but your base coding is gone so it can't tell what device is plugged in making it impossible to odin back to stock.
A jtag will rewrite your base coding and allow the phone to be able to boot into recovery and download mode. I would send it in to mobile tech videos and not to verizon. $60 isn't too bad for a working phone.
Sent from my SCH-I535 using Tapatalk 2
I just Odin my s3 back to stock for the warranty reason. Started having some issues with the power button and need another warranty replacement. I didn't want it flashed with no way to get back to stock. With this being my 3rd or 4th replacement I think I might try to guilt them into the s4.
Sent from my GT-P5113 using xda premium
Any luck with this or did you ever return it? I'm in the same situation. Rooted phone a while back, no problems until yesterday when the phone turned off at some point while not in use and would never turn back on or charge, same QHUSB_DLOAD message when connecting to a Windows machine. It would seem to be unrelated to rooting, but I'm afraid if I send it to Verizon, they'll notice and charge me. I'm not sure what their actual procedure is with returned phones and how far they'll go in troubleshooting/doublechecking a phone that's bricked in this way. I don't feel like this is warranty fraud, but Verizon may disagree.
I tried searching. Didn't find any other thread for a broken button.
So I was using my phone normally, until today morning. Suddenly the power button got stuck up.(is what i can diagnose out of it).
It keeps restarting to google logo , animation comes up, and then back again.(~8 seconds)
Im rooted and on a custom rom.
I have my phone in warranty, but the bootloader is unlocked, and custom romed.
So, what I wanted to ask is, can I go to a service center and be okay with it?
P.S: Im from India
Try pressing the power button firmly and see if it loosens up? If it's just the power button which is stuck, then I don't think the unlocked bootloader will matter... If it's broken, then you will have to pay for it irrespective of the bootloader being locked or unlocked.
However, since it's LG (India), nothing can be certain.. Here's an email I had got from them when I had asked them about unlocking/rooting:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vin4yak said:
Try pressing the power button firmly and see if it loosens up? If it's just the power button which is stuck, then I don't think the unlocked bootloader will matter... If it's broken, then you will have to pay for it irrespective of the bootloader being locked or unlocked.
However, since it's LG (India), nothing can be certain.. Here's an email I had got from them when I had asked them about unlocking/rooting:
Click to expand...
Click to collapse
I tried. Now its doing nothing.
But when i plug it into the charger, it just keeps doing the same thing and that padlock symbol.
Seriously, no warranty?
Its a hardware fault, right?
And what are the lockup to broken possibilities?
a 6 month old phone.
Reflash stock factory images followed by locking your boot loader through fastboot.
Sent from my XT1032 using XDA Premium 4 mobile app
frictionbuster said:
I tried. Now its doing nothing.
But when i plug it into the charger, it just keeps doing the same thing and that padlock symbol.
Seriously, no warranty?
Its a hardware fault, right?
And what are the lockup to broken possibilities?
a 6 month old phone.
Click to expand...
Click to collapse
Well, there's nothing you can do other than sending it in to LG. Try holding the power button for 20-30 seconds and see if it switches off? and then try to boot it?
When you unlock/root there's always a possibility of getting screwed (even though this hardware issue isn't related to unlocking). Take it to the nearest LG Service outlet and hope for the best. Since it's just the power button which is at fault, I think they might cover it! :fingers-crossed:
That's why I always lock the bootloader after I'm done flashing via the bootunlocker app. You can lock/unlock the bootloader without wiping data!
1c3_5n0w said:
Reflash stock factory images followed by locking your boot loader through fastboot.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The power button is stuck, his phone is rebooting constantly! How can he flash factory images while his device reboots??
vin4yak said:
Well, there's nothing you can do other than sending it in to LG. Try holding the power button for 20-30 seconds and see if it switches off? and then try to boot it?
When you unlock/root there's always a possibility of getting screwed (even though this hardware issue isn't related to unlocking). Take it to the nearest LG Service outlet and hope for the best. Since it's just the power button which is at fault, I think they might cover it! :fingers-crossed:
That's why I always lock the bootloader after I'm done flashing via the bootunlocker app. You can lock/unlock the bootloader without wiping data!
The power button is stuck, his phone is rebooting constantly! How can he flash factory images while his device reboots??
Click to expand...
Click to collapse
:'(
Should i wait for a few days?
and thanks vin4yak for the help.
Is there a possibility that something stuck up in between?
Dirt or some particle?
And, if its broken, how much will it cost me?
Thanks.
Try a service center, tell them the button stucked and you have unlocked bootloader, then ask them will they repair your phone under warranty if they do then ask for a repair. If they do not repair it under warranty then ask them for the price. It must be cheap for unstuck the power button. If you think that price is too much for you then disasdemble the phone and fix power button.
If the guys at the service centre know nexus 5 then they should repair it under warranty.
Tapatalk-kal küldve az én Nexus 5-el
frictionbuster said:
:'(
Should i wait for a few days?
and thanks vin4yak for the help.
Is there a possibility that something stuck up in between?
Dirt or some particle?
And, if its broken, how much will it cost me?
Thanks.
Click to expand...
Click to collapse
You could wait and see if it sorts out?? Possibilities are always there of something like that happening... It's best you show it to a professional (LG SC). No idea about the pricing. Contact LG and get a quote.
Did you buy your phone via play store? If so, you could contact google and see what they have to say about this.
vin4yak said:
You could wait and see if it sorts out?? Possibilities are always there of something like that happening... It's best you show it to a professional (LG SC). No idea about the pricing. Contact LG and get a quote.
Did you buy your phone via play store? If so, you could contact google and see what they have to say about this.
Click to expand...
Click to collapse
Yes. I,m waiting for a day or two.
And trying.
Nope. I bought it from a normal retailer.
So no chance of Google / Google warranty.
Ill go first to the LG SC and see what they say.
Update: I give a few thumps, on the power button side, using my hand, the button seems to release. Phone tries to boot. and then the button goes back down again.
Hope this is just some dust or a particle of some sort. No damage
frictionbuster said:
Yes. I,m waiting for a day or two.
And trying.
Nope. I bought it from a normal retailer.
So no chance of Google / Google warranty.
Ill go first to the LG SC and see what they say.
Update: I give a few thumps, on the power button side, using my hand, the button seems to release. Phone tries to boot. and then the button goes back down again.
Hope this is just some dust or a particle of some sort. No damage
Click to expand...
Click to collapse
Okay. This is amazing.
Today it started working normally. So i flashed stock and locked the bl using the toolkit.
Although I can't feel the problem, I'm gonna go the SC for making sure what that was.
Thanks everyone. Appreciated.
frictionbuster said:
Okay. This is amazing.
Today it started working normally. So i flashed stock and locked the bl using the toolkit.
Although I can't feel the problem, I'm gonna go the SC for making sure what that was.
Thanks everyone. Appreciated.
Click to expand...
Click to collapse
I had this issue at one point. I fixed it when I was trying to take out one of the screws and my drill hit the phone side and popped it back into place. Who knew.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I had this problem twice, and when I opened the back cover it fixed itself like magic. Yesterday I had it again and no luck so far.
I open the phone up to check the internal button, and if "feels" normal. But it's stuck.
Why is this soldered to the mother board? It's such a simple problem and I may have to get a new phone because of it.
I had this happen to my volume rocker. I eventually hit it and pressed it enough that it fixed itself.
I got mine to work again just throwing it several times on my bed hahaha
I'm kinda scared to use the power button now... using software for that now
Febag92 said:
I had this problem twice, and when I opened the back cover it fixed itself like magic. Yesterday I had it again and no luck so far.
I open the phone up to check the internal button, and if "feels" normal. But it's stuck.
Why is this soldered to the mother board? It's such a simple problem and I may have to get a new phone because of it.
Click to expand...
Click to collapse
Same thing. After I flashed stock, locked the bootloader, the button got stuck again.
Thankfully, I had copied my data and wiped my phone completely.
Went to the service center, and they asked me to submit my phone.
Luck, is the only word appropriate here.
bumping this thread a little bit, my N5 has started showing signs of a sticky power button,just a minute ago I felt it constantly vibrate in my pocket but no sound and when I checked, it was bootlooping... tapped the power button quite hard a few times and now it boots, ain't the first time it happened either, once it took me one full day to get it back to normal.
Is this something that happens only to the first phones? I know that the rattling was fixed at some point in production but mine has it so its one of the first to come out of the factory. What about fixing it myself? or how does warranty work with nexus devices? I bought it from a retailer in Finland that imported them from germany (possibly straight from play store) and the retailer has since gone out of business, is my 24month warranty still valid if the store that issued it is gone?
Notn4 said:
bumping this thread a little bit, my N5 has started showing signs of a sticky power button,just a minute ago I felt it constantly vibrate in my pocket but no sound and when I checked, it was bootlooping... tapped the power button quite hard a few times and now it boots, ain't the first time it happened either, once it took me one full day to get it back to normal.
Is this something that happens only to the first phones? I know that the rattling was fixed at some point in production but mine has it so its one of the first to come out of the factory. What about fixing it myself? or how does warranty work with nexus devices? I bought it from a retailer in Finland that imported them from germany (possibly straight from play store) and the retailer has since gone out of business, is my 24month warranty still valid if the store that issued it is gone?
Click to expand...
Click to collapse
Hard to say. Mine is a day 1 device and has never had this issue not has it rattled. Also you can still get rattling devices so it doesn't look like they've fixed it at all
Sent from my Nexus 5 using Tapatalk
Just stop it from rattling by your favourite method, be it paper, um blutack, um anyways noone will know
Ten min cutoff app.
power button removed - need to power on device
I have a question, same problem as dozens and dozens are having with the nexus 5 power button. I had looked around for fixes and came across a workaround for a galaxy s3. remove the 4mm power switch and turn the phone on by holding volume down and plugging the usb cable in. then from the recovery screen hit cancel (reboot) and the phone started up. then there are many apps that allow locking and unlocking of screen without the use of a power button.
...so I removed my power switch, which was the cause of the problem and plugged the phone in with down pressed and VOILA! I was in...or so i thought. I cannot select any option from that menu without a power button. Next i tried to flash a blank .tar file with auto reboot checked even though odin didnt give a com port. When I connected it to my pc it started to install drivers for it, I thought that was a good sign so i opened up ADB and tried to reboot from there, but it didnt pick up the device. (theres a small chance the drivers arent installed correctly, its a friends phone) Since I have a G3 i thought the drivers would be compatible sort of an umbrella of devices by LG.
My question is: is there any way at all, to signal to the phone to power up so i can install workaround apps while the 4mm power switch arrives in the mail? I've also tried a battery pull/plug cable in combo to no avail. if theres a timing trick i'd love to know about it.
thanks all!
with phone booted in bootloader mode you can use "fastboot reboot" command and phone will boot to system .