Develop Bugs

[Q] Did I get a bad Galaxy Nexus?

It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?

Try to do a clean install ... or wipe your cache and Dalvik cache

and your bone stock I would DEFINately bring it back ive installed countless roms and kernels and never pulled battery yet you didnt need to spend your money on a defective phone

irizwan said:
I believe theres a rouge app responsible .. try a clean install then don't install any apps then check
Click to expand...
Click to collapse
He just said he did this.
Anyways, try flashing a kernel and raising the minimum value slightly, saw this fix every SoD on the G2x forums. You'll need CPU Master or something similar.
I'm using CPU Master Pro, in case you were wondering.
Sent from my Galaxy Nexus using Tapatalk 2

Unroot and reroot. Problem should be solved.

Sarumiso said:
It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?
Click to expand...
Click to collapse
Install a custom kernel and change your minimum CPU to 700mhz. Fixed my sods. Honestly though I'd go for an exchange.
Sent from my Galaxy Nexus using xda premium

Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA

Toad858 said:
Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Just get the Gnex, geesh. There's lemons with every product, not just phones.
Sent from my Galaxy Nexus using Tapatalk 2

Might be a bad Sim card

Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.

Sarumiso said:
Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.
Click to expand...
Click to collapse
To go to Bootloader mode requires VolUP+VoldDOWN+Power button

suggest returning defective phone
You phone seems defective.
I realize you don't want to send it back, but getting stuck with a bad phone can drive you crazy.
When I bought my Evo 3D phone a year ago, after the update, it started to reboot at random times. After talking to their support, with no solution, I insisted on a new unit.
Once I got the new phone, I had no problems ever again.
Now I have the Galaxy Nexus, and I used it a lot the first few days to make sure it wasn't defective.
I hope you can find a solution, but if you don't, consider getting a new unit. It's not worth the hassle of keeping a questionable unit.

Have u tried to unroot yet??? It fixes all the problems u could possibly have.
Use Wug's toolkit to fix this issue.

[Q] Galaxy S3 wont boot passed logo screen please help me!!

My phone was charging while I was taking an nap and when I woke up my phone was off I also noticed it was hot so I turned it on and it wouldn't boot passed logo screen. I then went to bell and they would not replace it because there is a small crack at the top right of the screen which voids software warranty. One of the bell store employees attempted to put the phone in recovery mode but the process was stopped multiple times due to the fact that the phone only powers on for a few seconds. I don't have the money to buy another gs3, is there anyways to fix this. Doing some research on the phone and i believe it is hard bricked or something of that matter
*Update* Went to a cell repair shop, turns out its actually the power button that needs replacing and this is why the phone continually turns off and on and never reaches passed the logo screen. Apparently it's common for the power button to stop working or get all messed up on the gs3, if you have not rooted your phone or played around with the software the power button may be the cause of it not passing the logo screen and your phone might actually not be bricked

me too
KeeKeeB said:
My phone was charging while I was taking an nap and when I woke up my phone was off I also noticed it was hot so I turned it on and it wouldn't boot passed logo screen. I then went to bell and they would not replace it because there is a small crack at the top right of the screen which voids software warranty. One of the bell store employees attempted to put the phone in recovery mode but the process was stopped multiple times due to the fact that the phone only powers on for a few seconds. I don't have the money to buy another gs3, is there anyways to fix this. Doing some research on the phone and i believe it is hard bricked or something of that matter
Click to expand...
Click to collapse
i have the same problem, my phone is from bell too but warranty is over its been like a month like this xS.

keviinricoy said:
i have the same problem, my phone is from bell too but warranty is over its been like a month like this xS.
Click to expand...
Click to collapse
Im sorry mate, Bell is awful just a bunch of scumbags. If i can't find any help from here im going to go visit a cell repair shop to get some help. You should try to find some as well, google search cellphone repair shops in your area! I have very little knowledge of software on androids but apparently my phone needs to be flashed

Have you tried another battery. ...thats what I would try. Also make sure all your ports are clean and debris free.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KeeKeeB said:
Im sorry mate, Bell is awful just a bunch of scumbags. If i can't find any help from here im going to go visit a cell repair shop to get some help. You should try to find some as well, google search cellphone repair shops in your area! I have very little knowledge of software on androids but apparently my phone needs to be flashed
Click to expand...
Click to collapse
Yes i tried my friends battery, this sadly did not work.

recovery
Have you tried to boot into the phones stock recovery and clear it ? Or how about odin a stock rom ? Just trying to brainstorm, but I seriously do not think your phone is toast. I would try seaching these ideas and see if you have any luck....otherwise search for how to recover a bricked phone for your carrier...the same method might work to get you up and running again???

same thing happening to me...i can boot into recovery/download mode but only for 2-3 seconds and then the phone reboots itself...all started after I dropped it from my sofa earlier today. any suggestions anybody?

turns out it was the power button that was malfunctioning for me..got it repaired and now its working fine..

Note 2 Bricked.

I have been using this phone since 2 weeks of the initial release of the galaxy note 2. For years, there has been no problem whatsoever. A few weeks ago this happened:
1. Phone suddenly powered off and factory resetted. I was in the middle of using it. The only thing I installed recently at that time was pokemon GO, and uninstalled it a few days later (Because i have no friends to play with, lol). Luckily, i have backed up data before.
2. Phone started working normally again, then a few days later it just powered off again with no warning. I just left it for 5 minutes and that happened. It is now stuck on the "Galaxy Note II" screen. I haven't been able to get past that screen anymore.
3. I tried charging the phone, the only thing that popped up was the battery logo with the loading circle. No 5 dots at the bottom, no green battery.
What I have tried to fix this:
1. Factory resetting using Power+Menu+Volume up.
2. Flashing the stock ROM.
3. Using samsung kies.
4. Taking the phone to a samsung service center.
When i took it to the service center, the guy said that there is a "part" of it that is broken and needed to be replaced. That guy didn't specify what part it is and asked $180 for repairs. I said no, because that is the same as buying a used one right now. Also, the guy said that this is caused by using the phone while charging. Is this true?
Also, i found out that this might be caused by eMMC failure or something like that. Can you help me go through this?

TheSpartaGod said:
I have been using this phone since 2 weeks of the initial release of the galaxy note 2. For years, there has been no problem whatsoever. A few weeks ago this happened:
1. Phone suddenly powered off and factory resetted. I was in the middle of using it. The only thing I installed recently at that time was pokemon GO, and uninstalled it a few days later (Because i have no friends to play with, lol). Luckily, i have backed up data before.
2. Phone started working normally again, then a few days later it just powered off again with no warning. I just left it for 5 minutes and that happened. It is now stuck on the "Galaxy Note II" screen. I haven't been able to get past that screen anymore.
3. I tried charging the phone, the only thing that popped up was the battery logo with the loading circle. No 5 dots at the bottom, no green battery.
What I have tried to fix this:
1. Factory resetting using Power+Menu+Volume up.
2. Flashing the stock ROM.
3. Using samsung kies.
4. Taking the phone to a samsung service center.
When i took it to the service center, the guy said that there is a "part" of it that is broken and needed to be replaced. That guy didn't specify what part it is and asked $180 for repairs. I said no, because that is the same as buying a used one right now. Also, the guy said that this is caused by using the phone while charging. Is this true?
Also, i found out that this might be caused by eMMC failure or something like that. Can you help me go through this?
Click to expand...
Click to collapse
Hello
Im newbie
Try flashing stock ROM using Odin
Also you better use custom ROM like me I'm using cm13 right now , no problem at all
My phone got bricked before once I reset it
Try re flashing custom recovery
It might because of that .
The factory reset progress not finished
I flashed cwm then my phone boot up
After it works I'm using twrp instead
Sorry for my bad English hope you understand
Sent from my Samsung GT-N7100 using XDA Labs

Nexus 5x won't turn on

Last night my phone went dead. When I plugged it in. I saw the Goggle words on the screen, like when the phone is booting up from being off power. this stayed on for several seconds, then it flashed off and nothing all night. The led light was flashing on and off for a bit, but nothing. I couldn't turn it on then.
Then this morning, I was able to hold the power button and then the Google showed up for a few seconds, then nothing. I have tried holding down the power button for 10 sec to no avail, holding the power and vol down, nothing. Is there any other way to reset this or is the battery or something else on it dead and it needs to be returned to Google. Any and all help is welcomed.
Right now I have it plugged into the google cord and plug, not seeing the led light.

Good news: You're not the only one this is happening to.
Bad News: Not really a good solution yet.
Android Authority is covering it. There's some discussion in their comments.
I tried going into recovery and factory reset/wipe cache and that did nothing. Apparently some people have had luck flashing an older release, but I wasn't able to get anywhere close to that. I ended up calling calling the Google Hardware Warranty Center and they're sending me a replacement.

If bootloader is unlocked, I will be able flash factory image to fix this?

I haven't rooted the phone. It is just the basic android. I'm on with Google support right now. They are going through all the things that I have already done.

I can't get to the bootloader. The phone is off / dead right now. Once it turned off last night, I haven't been able to get it to power up again.

Google wanted me to put it on their cord and charge for an hour to see if anything changed. Hoping it works. I have to travel this weekend, and he was saying it could take up to 7 business days to get a new phone.

No power after 2 1/2 hours on the google cord. Guess to get a replacement.

hope you have a backup phone to use.

I have an iphone 5 I use for Ipod. Would it be too much work to use this until I get the other one, or will it probably not have the right sim card?

I'm in the same boat too. Google sent me out a warranty replacement. Mine just crashed when making a call and it would no longer power on after that. The only thing it would show when plugged in to my computer was Qualcomm downloader for USB.

When I updated to Nougat, I now get the screen that says Firmware Update with a message telling me to keep it plugged in. It's been at 0% for a few hours. Rebooting the phone results in the same thing. Phone's not rooted or anything. Guess I have a brick now.

90s
Sent from my Nexus 7 using XDA-Developers mobile app

There are lots of reports that nexus5x die after the nougat update

I got it to boot up last night, and I was able to get it to recovery mode, then tried to reboot, but nothing else. I'm contacting Google again to get the warranty started.

Just ordered a replacement, bummer that it is a refurb, not new, but sometimes the refub units are tested more than new. Is there any way that I can ensure that the data on the phone won't wind up in the wrong hands after it is fixed by Google and sent out, or is it just a roll of the dice?

They said they were sending me a refurb but its was a brand new one. It came in a retail box. Wondering if they ran out of refurbs with all the people having issues.

So I have the refurb unit at home. It is asking to update to nougat. Are the software updates safe enough to put on the phone. Mine is just stock not rooted.
Can't wait. I've been limping by on the iPhone 5.
Sent from my iPhone using Tapatalk

Mine died, LG told me to send it to them for repair, but only have me a FedEx ground, would have liked more like Air delivery for faster processing

Nexus 5X hard bricked. Is there definitely no way to fix it?

I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.

@gwynlordofcinder: sad for you. But why you ask the same question as 20 others before? Try freezer and/or oven to get back the mainboard-connections. If successfull, you can save your data or go on with a kernel-profile which makes the big core sleep. Use search for details.

gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.

Most likely fixable, but with the need of special files.
Search up on QD Loader 9008 on this subforum and read through it.
i'm on the hunt to find a fix for it, hopefully i'll make it. gonna share my findings asap!

Voicebox said:
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.
Click to expand...
Click to collapse
There is no extended warranty in the UK, which is where I purchased the phone.

gwynlordofcinder said:
There is no extended warranty in the UK, which is where I purchased the phone.
Click to expand...
Click to collapse
Since this happened from normal usage and not from you installing a custom ROM or updating the bootloader, or something like that, I think you have the bootloop problem. I normally think of a hard brick being the result of flashing say the incorrect bootloader, or a corrupt file, etc. which can then hopefully be undone by software means to get the right software back on there.
If you have the bootloop, it is a hardware problem. The fact that the phone doesn't bootloop does not mean you don't have the hardware problem. Boot looping was just the most common way to identify it, but many, like mine would just either never even start booting, or would start, then go black.
If you don't figure out any software way to do anything, then try to look for bootloop fixes. Searching for that might get you further. But with a hardware problem, everything except the fix for disabling the big cores (in XDA threads), is temporary unless you are lucky.
Assuming you have a hardware issue, here's some steps to maybe try. I was able to get the rescue fix installed on my phone after using a hair dryer on the motherboard. But that didn't fix anything since my problem was hardware. But if your OTA update was maybe slightly corrupted, maybe it'll help.
https://productforums.google.com/forum/#!topic/nexus/G_0s70PzK_s
To jump right to trying a rescue OTA, go here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/nexus/hdrNONCCoNE
If it doesn't react enough to do anything from a computer, you may have to resort to putting it in the freezer for a while first. Which may give a short period where it'll boot and you can maybe adjust the settings so you can try one of the XDA fixes that disable the big cores.
One fix that disables the big cores:
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E

Voicebox said:
which can then hopefully be undone by software means to get the right software back on there.
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E
Click to expand...
Click to collapse
except that the files needed for unbricking corrupt bootloaders/eMMCs' are so hard to find it's incredible.
bought a used 5X that "suddenly died in a pocket", now that you mention all of this, i might try doing the hardware fixes and then apply the big core disabling and hopefully get my phone to work.
the phone did get serviced though, so they might've installed bad firmware since the phone is in QDLoader & in EDL mode (PC recognizes the phone, while fastboot/adb/LGUP doesn't)

gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
Can you update driver "QHSUSB_BULK" in device manager by choose driver manually . I have problem like this in Inew V3 (Chaina Phone) and can fix by choose driver manually.