Database Users

Nexus 4 hard bricked orange light

Hello, I am sorry for this but I can't find a fix anywhere. I was just benchmarking my Nexus 4 which was running PA 3.60 and Nexus 4 Community Kernel overclocked to 1.836 GHz when my phone just crashed it wouldn't turn on I plugged it into a charger and turned it on and got a orange flashing light. After a while i managed to get it to boot into Bootloader and tried wiping cache, factory reset. It made no difference I tried erasing the system and flashing the rom again but difference. Eventually I managed to get it to the new phone setup but it just crashed after that. I wiped the boot, system, userdata etc. through fastboot and flashed the stock rom but no avail. Any help would be greatly appreciated.

It doesnt look bricked, just erase and flash stock rom.

i tried that but it just gives me the orange light when i try to boot

Did try turning the phone off and letting it charge for a few hours then turning back on? Look for a thread titled "red light of death" or something to that effect in this forum. There may be a solution in there.
Sent from my Nexus 4 using xda premium

when i plug it in the orange light just flashes.

I love this one
Sent from my Nexus 4 using xda premium

isaacx said:
Hello, I am sorry for this but I can't find a fix anywhere. I was just benchmarking my Nexus 4 which was running PA 3.60 and Nexus 4 Community Kernel overclocked to 1.836 GHz when my phone just crashed it wouldn't turn on I plugged it into a charger and turned it on and got a orange flashing light. After a while i managed to get it to boot into Bootloader and tried wiping cache, factory reset. It made no difference I tried erasing the system and flashing the rom again but difference. Eventually I managed to get it to the new phone setup but it just crashed after that. I wiped the boot, system, userdata etc. through fastboot and flashed the stock rom but no avail. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try to look here,i hope that you will fix your problem, even if that's not caused by a your error i think

took out the battery and fixed it

N4 upgrade failed

Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA

Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?

If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.

BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...

As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?

Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?

Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...

Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium

Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4

TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...

Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.

tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.

[Q] Rebooting after flashing Rom

Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?

matteosaeed said:
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
Click to expand...
Click to collapse
Go back to stock first, and check if that has the same problems...

matteosaeed said:
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
Click to expand...
Click to collapse
For some reason I have tried this a lot on my old phone... Some kernels worked for mine and others not... While it should..
Flash stock and see... Keep stock kernel and flash rom, if no problems then try new kernel... If problem returns then flash stock kernel again
Sent from my GT-I9505 using xda app-developers app

DenmarkRootN00b said:
For some reason I have tried this a lot on my old phone... Some kernels worked for mine and others not... While it should..
Flash stock and see... Keep stock kernel and flash rom, if no problems then try new kernel... If problem returns then flash stock kernel again
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip. I tried that as well, but Unfortunately, the same problem. I don't have a problem what so ever when I am using the phone while it is charging or plugged in, but as soon as I take it out, and even if it is full, it shuts off, tries to turn back on and it wouldn't, it keeps rebooting, once i plug the charger in it, it would stay on.
That tells me either:
The Battery is bad!
Or
There might be a circuit problem with the phone sucking power out of the battery!

Need help, please!

Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk

Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.

I also think there's a problem with your battery, it might need to be replaced.

ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk

Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.

norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?

Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app

Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped

Lost Mac adddess [SOLVED]

Hi, I tested a lot of ROMs when I noticed, that when I connect my device to charger while it's turned off it doesn't stay turned off and auto turns on. I changed ROM, flashed new stock via RSD, nothing helps. What can I do to completly reset the device and solve it?
Klen2 said:
Now charging works
The bad thing is, that while flashing, propably in RSD, (not this firmware, I made some flashes of 98.16.1 and ICS) I lost my MAC address. Don't know how. Is there any option how to write it on RAZR M? On some phones is (msm 7225A).
Click to expand...
Click to collapse
Klen2 said:
I think it was so:
1) I flashed 98.16.1 via RSD from Vanir KK ROM
2) I forgot to wipe data before flashing, phone did not boot for long time after flashing
3) I forced reboot and booted to recovery (stock) and wiped data
4) When I rebooted, the phone booted to bootloader saying flash failure. The new flashing of new ROM failed (don't know why, maybe because low battery or the 'getprop' line on the beginning of XML in ROM zip).
5) I installed cwm from fastboot and flashed KK AOSP (The only ROM I had)
6) Rebooted, booted to recovery, wiped data and flashed 98.16.1 in RSD, then flashed cwm, booted to cwm, rooted and flashed las test arrrhggg kernel for stock JB, rebooted and then I noticed I have no WiFi
X) I think the problem was in points 1-4
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse

Klen2 said:
Hi, I tested a lot of ROMs when I noticed, that when I connect my device to charger while it's turned off it doesn't stay turned off and auto turns on. I changed ROM, flashed new stock via RSD, nothing helps. What can I do to completly reset the device and solve it?
Click to expand...
Click to collapse
Normal moto charge mode behaviour. I hate it. A real nuisance at times.

But it wasn't so in past. The phone remained turned off, just a animation of charging battery showed for few seconds.

Klen2 said:
But it wasn't so in past. The phone remained turned off, just a animation of charging battery showed for few seconds.
Click to expand...
Click to collapse
Dev did not maintain stock files.

I was a bit puzzled by this for a while. I have an old 1 amp moto charger that will charge it while powered off. My ex's s4 charger also worked, which is 2 amps.
Sent from my XT907 using xda app-developers app

Klen2 said:
Hi, I tested a lot of ROMs when I noticed, that when I connect my device to charger while it's turned off it doesn't stay turned off and auto turns on. I changed ROM, flashed new stock via RSD, nothing helps. What can I do to completly reset the device and solve it?
Click to expand...
Click to collapse
It could be a bad data app. Do a safe boot. Hold the down vol when you see the first splash screen/ big m hold all the way home.
Restore to the safestrap or custom backup you should have made when you first started messing around.
Rsd is your friend if the above does not work. See my button below.

I tried RSD, wiping data too. Nothing helped.
But now I flashed to 98.30.1 and it works!
The bad thing is, that while flashing, propably in RSD, (not this firmware, I made some flashes of 98.16.1 and ICS) I lost my MAC address. Don't know how. Is there any option how to write it on RAZR M? On some phones is (msm 7225A).
Sent from my XT907 using Tapatalk

I think it was so:
1) I flashed 98.16.1 via RSD from Vanir KK ROM
2) I forgot to wipe data before flashing, phone did not boot for long time after flashing
3) I forced reboot and booted to recovery (stock) and wiped data
4) When I rebooted, the phone booted to bootloader saying flash failure. The new flashing of new ROM failed (don't know why, maybe because low battery or the 'getprop' line on the beginning of XML in ROM zip).
5) I installed cwm from fastboot and flashed KK AOSP (The only ROM I had)
6) Rebooted, booted to recovery, wiped data and flashed 98.16.1 in RSD, then flashed cwm, booted to cwm, rooted and flashed las test arrrhggg kernel for stock JB, rebooted and then I noticed I have no WiFi
X) I think the problem was in points 1-4
Sent from my XT907 using Tapatalk

So I know where was the problem. I wiped /persist by mistake (unfortunetly, it is possible to do it by cwm I used. Here I found a solution (this post) Everything works now.
Anyway I flashed again with RSD and my phone doesn't stay turned off again, crazy.