Horribly Bricked Nexus 4? - Nexus 4 Q&A, Help & Troubleshooting

Alright guys, as of right now I'm trying to fix my nexus 4 after flashing Matr1x 14.0 kernel onto my phone...after It became soft-bricked. I tried resetting my factory/wipe data with dalvik cache and partition cache...no luck. It then became even more worse...after seeing that google sign, it went into the bootloop for quite a while, and then the phone doesn't display anything and what not. But I can still use my phone via the hardware buttons. Sorry if I explained this horribly, but please, PLEASE help me out here!
The file I flashed too was: matr1x/Nexus4/14.0/Matr1x-cfs_v14.0-cm-gpuoc.zip

derking1 said:
Alright guys, as of right now I'm trying to fix my nexus 4 after flashing Matr1x 14.0 kernel onto my phone...after It became soft-bricked. I tried resetting my factory/wipe data with dalvik cache and partition cache...no luck. It then became even more worse...after seeing that google sign, it went into the bootloop for quite a while, and then the phone doesn't display anything and what not. But I can still use my phone via the hardware buttons. Sorry if I explained this horribly, but please, PLEASE help me out here!
The file I flashed too was: matr1x/Nexus4/14.0/Matr1x-cfs_v14.0-cm-gpuoc.zip
Click to expand...
Click to collapse
why you did a factory reset after having your phone soft bricked? you could've flashed any other kernel to test it out.. why going for factory reset?
you want a solution.... factory reset... flash rom.. if it doesn't work.. just flash factory image through fast boot..
Sent from my rastakat powdered Nexus

snak3ater said:
why you did a factory reset after having your phone soft bricked? you could've flashed any other kernel to test it out.. why going for factory reset?
you want a solution.... factory reset... flash rom.. if it doesn't work.. just flash factory image through fast boot..
Sent from my rastakat powdered Nexus
Click to expand...
Click to collapse
+1
Try the thtat method....

I've tried and tried to soft brick my nexus 4 but never succeded
always look on the bright side of life ...

soft brick doesn't actually exist either, its either bricked or its not. you wife will never be semi pregnant.

simms22 said:
soft brick doesn't actually exist either, its either bricked or its not. you wife will never be semi pregnant.
Click to expand...
Click to collapse
Its a False pregnancy I think.

Related

[Solved (partially)]ROM can't boot after turning my phone off... So weird !

Hi, I'm desperate today. I've been without my phone since a few days.
In the first place, I wanted to flash another custom ROM. I hadn't change anything to my N4, I was using AOSPAL. You know that F2FS has come, so I wanted to test it. After some fails, some resets, I succeeded to make my phone clean & fast (F2FS & custom kernel). Now I can tell you about my problem.
I noted that, after many tests/flashs, my phone can't boot after turning it off. I stuck at "Google" logo, the ROM apparently disappeared from my phone, or something else went wront. I don't know what.
Then I did a new factory reset, I flashed a ROM/Kernel without any changes to FS, but I got the same problem. If I reboot (reboot from adb, ROM...) my phone, it works. But if I turn it off, I'll stuck at "Google" logo the next boot.
I've actually no ideas, and Google gave me no results...
I'll try to make a new reset, or try another kernel... I don't know where I'm going.
Thanks for help and I wish you to have a nice day.
PS : I'm not a newbie, I already did more than hundreds flashes, some bricks, but I've never seen a similar problem.
Why don't you try flashing the factory image and start over. That should clean everything up
Sent from my Nexus 5
hi
try use nexus tool kit for restore fone bootloop flash rom stock
jd1639 said:
Why don't you try flashing the factory image and start over. That should clean everything up
Sent from my Nexus 5
Click to expand...
Click to collapse
I've already done that each time before flashing any custom mod, since I got that problem.
eltonpestana said:
try use nexus tool kit for restore fone bootloop flash rom stock
Click to expand...
Click to collapse
This isn't the problem... I flashed the factory image many times. It works, but when I turn my N4 off and I want to boot it, I stuck at "Google".. When I reboot from the ROM or adb, there's no problems...
Diaruga said:
I've already done that each time before flashing any custom mod, since I got that problem.
This isn't the problem... I flashed the factory image many times. It works, but when I turn my N4 off and I want to boot it, I stuck at "Google".. When I reboot from the ROM or adb, there's no problems...
Click to expand...
Click to collapse
I assume you've done a factory reset in the stock recovery too? If so I think something is wrong with your phone. Is it still under warranty.
Sent from my Nexus 5
jd1639 said:
I assume you've done a factory reset in the stock recovery too? If so I think something is wrong with your phone. Is it still under warranty.
Sent from my Nexus 5
Click to expand...
Click to collapse
Mhhh when I tried F2F2 and wanted to try something else, I've not done a factory reset in the recovery (did you mean the format partitions in ext4fs or the wipe data/cache/dalvik ?). I used fastboot in order to erase all my partitions, then I flash the factory image archive through fastboot command "-w update".
I don't know whether something is wrong with my phone or not, but I've never seen that problem. It appeared when I did some tests with F2FS. That's all, that's so weird...
Diaruga said:
Mhhh when I tried F2F2 and wanted to try something else, I've not done a factory reset in the recovery (did you mean the format partitions in ext4fs or the wipe data/cache/dalvik ?). I used fastboot in order to erase all my partitions, then I flash the factory image archive through fastboot command "-w update".
I don't know whether something is wrong with my phone or not, but I've never seen that problem. It appeared when I did some tests with F2FS. That's all, that's so weird...
Click to expand...
Click to collapse
I would definitely try to flash the factory image again, then boot into the stock recovery and do a factory reset. F2FS may have borked something. I've never tried it since it does mess with the positions
Sent from my Nexus 5
hi'
I'm not sure if this can work. But it never hurts to try. After flashing stock ROM with CWM. Enter recovery and make full format of all partitions. System and Data partitions and cache and all. After that reinstall the stock rom using nexus tool kit for flashing mode in bootloop. after that flashing custom recovery again and do cleanup, but not the only formates cleanings. I believe you are having trouble reading recognition, partition boot. Uncompensated You must have notice a conflict of partitions on the system format.
eltonpestana said:
Uncompensated You must have notice a conflict of partitions on the system format.
Click to expand...
Click to collapse
I was wondering the same thing...
Thanks guys for your help, I'll flash stock again, and then I'll format correctly the partitions. I hope that's the good way...
Next time its stuck on the Google logo just try plugging in you're charger.
I had the same problem but not down to using F2FS but it did hang on the logo during boot.
After plugging in the charger it booted and hasn't stuck since.
Don't ask my why as I haven't a clue but it worked.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
Next time its stuck on the Google logo just try plugging in you're charger.
I had the same problem but not down to using F2FS but it did hang on the logo during boot.
After plugging in the charger it booted and hasn't stuck since.
Don't ask my why as I haven't a clue but it worked.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
FYI this could indicate a problem with your battery
@Diaruga did you ever find a solution?
Sent from my Nexus 5
I plugged my N4, then I tried to flash the factory image again. That was fine. After flashing a custom ROM + custom kernel, still no probems after turning my phone off.
I can't explain why...
Thanks to all, my problem has been solved.
Diaruga said:
I plugged my N4, then I tried to flash the factory image again. That was fine. After flashing a custom ROM + custom kernel, still no probems after turning my phone off.
I can't explain why...
Thanks to all, my problem has been solved.
Click to expand...
Click to collapse
Thanks, glad you got it working again
Sent from my Nexus 5

Compass module fault -> phone bricked

I opened up the camera from within the facebook messenger bubble window which presented me the front camera. Having tried to switch to front camera my phone rebooted and is now endlessly in a reboot loop. This is the log:
http://pastebin.com/9Gt8fGxW
I even did a full device wipe but no dice. Any explanation?
(I'm on Cyanogenmod nightly and so far my phone was stable)
Have you tried going into recovery? If you are able to, try to do a wipe from there, and then reflash cyanogenmod.
Marvlesz said:
Have you tried going into recovery? If you are able to, try to do a wipe from there, and then reflash cyanogenmod.
Click to expand...
Click to collapse
As I've said, I did a complete wipe. Even flashed cyanogenmod again. Phone is still in reboot loop.
It definitely did not brick your phone. If you still have any issue flash the factory image in fastboot and start over. If you were bricked you're phone wouldn't even turn on
Sent from my Nexus 5
jd1639 said:
It definitely did not brick your phone. If you still have any issue flash the factory image in fastboot and start over. If you were bricked you're phone wouldn't even turn on
Sent from my Nexus 5
Click to expand...
Click to collapse
Well, I just did a factory image. Apart from losing all my data it didn't help either. I guess some kind of hardware is dead now which is necessary to boot Android...

[Q] Help! Phone bricked itself trying to update. Factory Reset isn't helping!

Last night my phone wanted to update to 4.4.4 because it's been wanting to for a while, but I know it wouldn't work because my phone is rooted. It had tried this at least 3 times before and everything was fine; download update, tries to install, fails, boots right back up. I wanted to get rid of the Update notification in the top bar, so I just ran it again thinking it'd be okay. Well, this time it bricked my phone, leaving me at a neverending loop at the boot animation. I first tried to wipe the cache and dalvik cache, which did nothing. Then I tried a factory restore, which also did nothing. Then I reinstalled the stock 4.4.3 rom I had been using, which did nothing. Then I wiped the SD card completely and reinstalled a stock 4.4.4 rom through sideload, which has done nothing. My phone just sits at the boot animation and taunts me. Worse yet, I have a 16-hour drive tomorrow and my phone was going to be the majority of my sanity during that time.
What should I do?? Is there anything I can do? Normally I would just contact Google to get a replacement (I've done this before when the 4.2 update was causing a lot of bricks,I think it was 4.2 anyway, I forgot) but I'd like to have a working phone for my 16 hour trip..... if possible. Any help would be greatly appreciated! Thank you.
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
CCody said:
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
Click to expand...
Click to collapse
I had a Vanir 4.4.3 rom on my phone that I tried to flash as well, but for some reason it went right into "Optimizing Apps" after the first boot, something I hadn't seen before. Then it got stuck at "Starting Apps...", then after a restart, it too was stuck at the boot animation.
I can boot into recovery luckily, but that's all I can do. I have CWMR v6.0.3.5. I've tried just about everything I can think of. [edit] I was able to contact Google for some live chat support and am now #2 in the queue. Hopefully they can either help me or get a replacement going. Either way, I'd still love any help you guys can give me, I'd really like to get it fixed rather than waiting for a replacement.
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
CCody said:
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
Click to expand...
Click to collapse
I've done that already, Factory Reset + wipe cache + wipe dalvik cache + format system/data/cache/sdcard/data/media. The phone was completely bare and that's when I sideloaded the stock 4.4.4 rom (otherwise it's stuck at the Google boot screen). I'll try it again, though.
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
RawrNate said:
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
Click to expand...
Click to collapse
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
CCody said:
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
Click to expand...
Click to collapse
Yeah haha, it's really really strange. I appreciate you trying to help me, though! Lucky for me I'm getting a "One-time exception replacement" since my warranty is expired but they must be super stumped with the issue as well xD
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
CCody said:
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
Click to expand...
Click to collapse
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Wait, how do I flash the binaries since they're .tgz files?
RawrNate said:
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Click to expand...
Click to collapse
This is really strange man. Flashing stock ROM is the last resort but even that seems to be failing for you.
Have you tried downloading the stockRom again (just to make sure it isn't corrupted). Also, maybe you can try using TWRP instead of CWM this time.
Good luck.
RawrNate said:
Wait, how do I flash the binaries since they're .tgz files?
Click to expand...
Click to collapse
No need to flash them, since you are on a factory image, sry.
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
RawrNate said:
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
Click to expand...
Click to collapse
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
CCody said:
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
Click to expand...
Click to collapse
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
RawrNate said:
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
Click to expand...
Click to collapse
Jesus!
What about custom ROM? Cyanogenmod maybe? Make sure to downlaod the M7-Release.
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
RawrNate said:
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=tZbvuikfnks
CCody said:
https://www.youtube.com/watch?v=tZbvuikfnks
Click to expand...
Click to collapse
Oh good that was easier than I thought xD

Soft-bricked Nexus 4, no guide will work

My Nexus 4 had been running Cyanogenmod (cm-12.1-20151007-SNAPSHOT-YOG4PAO334-mako) correctly for months. Two days ago, the screen failed to auto-rotate when I tilted the phone so I decided to reboot and see if that worked. Not only did it not work, the device went into a bootloop. It would boot, ask for my encryption password, accept the password but the OS would never start (I waited over 2 hours).
I'm able to use adb, fastboot, and access TWRP.
I tried reflashing CM12 to no avail. I've also tried going back to stock by reformatting all partitions in fastboot and flashing stock bootloader, radio, and system image (also in fastboot). That's where I'm at right now. I have everything stock except for the recovery partition where I have TWRP.
Here's the TWRP log: http://pastebin.com/MCKD73G0
Here's the dmesg log: http://pastebin.com/BdVjV2vz
Here's the last kernel message log: http://pastebin.com/DBQQBFQv
Any ideas?
I have a very strong hunch that this problem has got something to do with the sensors.
I flashed Android 4.2.2 and, to my surprise, the phone booted correctly into Android. No other ROM (stock or otherwise) would boot correctly. As I mentioned in the OP, screen auto-rotation isn't working so I downloaded an app to test other sensors. The proximity sensor, pressure sensor, light sensor, and the gyroscope don't work. I strongly doubt this is a software issue but I'm not ruling it out yet. I will try to open the phone case later tonight and move the sensor around, it might be stuck.
Just had a pro take a look at my phone. He said there's nothing wrong with the sensors so it must be a software problem. I've been trying to fix this for days now.
Any ideas would be greatly appreciated.
I just noticed that my phone does not have the /sys/class/sensors/ or /sys/devices/virtual/sensors/ folders, is this normal? If not, how can I solve this?
Feareilo said:
I just noticed that my phone does not have the /sys/class/sensors/ or /sys/devices/virtual/sensors/ folders, is this normal? If not, how can I solve this?
Click to expand...
Click to collapse
I had this issue twice.. flashing an old version of Frank ROM (in L preview times).. all my sensors got screwed... and trying to flash other roms or factory resetting the phone didn't work!
So I downloaded latest factory image and flashed it with the flashall.bat script
VoilĂ ! All the sensors started to work again!! And they still work! So... some very deep part of the system can be wiped only by the stock recovery factory reset.. I don't know why though.. but that's it!
bart.found said:
I had this issue twice.. flashing an old version of Frank ROM (in L preview times).. all my sensors got screwed... and trying to flash other roms or factory resetting the phone didn't work!
So I downloaded latest factory image and flashed it with the flashall.bat script
VoilĂ ! All the sensors started to work again!! And they still work! So... some very deep part of the system can be wiped only by the stock recovery factory reset.. I don't know why though.. but that's it!
Click to expand...
Click to collapse
Thanks for your input. Unfortunately, that didn't work. Flashing stock ROMs didn't work and neither did doing the factory reset.
Feareilo said:
Thanks for your input. Unfortunately, that didn't work. Flashing stock ROMs didn't work and neither did doing the factory reset.
Click to expand...
Click to collapse
Sad to hear that... did you already factory reset from the stock recovery?
bart.found said:
Sad to hear that... did you already factory reset from the stock recovery?
Click to expand...
Click to collapse
Yeah

Lock Screen Wallpaper No Longer Centered? Latest Oxygen OS

I've noticed that after going back to stock Oxygen with root my lock screen wallpaper is not centered. It seems to be shifting to the left of center. Is there a fix or reason why this is happening? Don't have this issue with any other ROM...
Try factory reset, it maybe hanged out. Coudl help it this way.
Seimus said:
Try factory reset, it maybe hanged out. Coudl help it this way.
Click to expand...
Click to collapse
I'd give it a shot but when I installed this time around I actually followed the Unbrick method from here.. Unbrick Guide .. I can only assume this wiped everything and anything from the phone? I sometimes wonder if I'm getting a good wipe.
jbarcus81 said:
I'd give it a shot but when I installed this time around I actually followed the Unbrick method from here.. Unbrick Guide .. I can only assume this wiped everything and anything from the phone? I sometimes wonder if I'm getting a good wipe.
Click to expand...
Click to collapse
Well if you want to wipe everythink you need to do the factory + wipe data. I also suggest to wipe dalvik and partition cache. This will not only wipe your data but your current OS. So you need to flash it again.

Categories

Resources