Related
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.
Hey all, I was installing MultiRom so that I could try out different roms with the primary purpose of getting GameCih working on my Nexus 7 (1st Gen). I went through the first steps but got the "Kernel: doesn't have kexec-hardboot patch!" message. So following the guide at http://forum.xda-developers.com/showthread.php?t=2457063, I went ahead to patch that kernel. However, when I hit install, I realized it said it was a 4.1 stock kernel. The install ran and when the boot started, it just sat on the colorful X for 10-15 minutes. I booted into recovery and tried to figure out a way to get the proper kernel on the device and install that, but had no luck. Unfortunately, I backed up using the Wugs Nexus Toolkit and forgot to do it within the recovery on the device. So are my only options to wipe the device and start over or can I install the proper kernel, or is there another solution? Thanks so much for your help.
Sorry for the double post, but I waited several days to reply. I ended up going ahead and doing a wipe. It kept the rom, but did seem to fix the issue. I also tried installing the AOSP 4.2.2 ROM in MultiRom, but that one isn't working. And once I did that, several of the apps stopped working in the PAC Rom. It doesn't look like I'm going to get much help here, but I thought I'd at least respond to my original post
I am not new to ROMs and flashing etc., but I am completely stumped on this one. I have looked everywhere I know to look (supposedly) but if you find some easily locatable solution that I have missed, please feel free to call me mean names and share the solution with me. Otherwise, this is what I have tried so far (I will start from the beginning):
First, the 4.3 OTA update bricked my phone. I hadn't rooted my N4 yet because it was an updrage from D1 (yes, big jump). I decided to root the phone and install a custom ROM. Can't be too hard right? Its a Nexus for crying out loud. WRONG. Well I rooted pretty easily, and installed my first custom ROM for N4. To install this ROM, I had to erase boot.img, system.img, and userdata.img and then flash each individually from the ROM zip file I downloaded. This worked! I was winging it and it worked out. However, from then on, EVERY ROM I tried to install ended up in a bootloop. I have wiped cache/data, dalvik cache, and even my own (c)ache before flashing new ROM. They all end in bootloop (never ending).
I am able to revert to stock 4.2 easily every time. However, any attempt at installing a custom ROM from there is void. Today I downloaded 4.4.2.tgz from google and ran flash-all.bat. Everything works great! Until I try to boot up; bootloop. I fastboot format this and fastboot erase that, then fastboot flash each .img individually. I fastboot flash new radio, new kernel, etc. etc. but still bootloop.
I really am clueless as to what I am doing wrong or how I screwed myself somewhere along the way, but I am humbly coming before my superiors and asking for help. Please offer me the simplest solution and call me dumb for not seeing it, I will hold you in my heart 4eva
CausableMidget said:
I am not new to ROMs and flashing etc., but I am completely stumped on this one. I have looked everywhere I know to look (supposedly) but if you find some easily locatable solution that I have missed, please feel free to call me mean names and share the solution with me. Otherwise, this is what I have tried so far (I will start from the beginning):
First, the 4.3 OTA update bricked my phone. I hadn't rooted my N4 yet because it was an updrage from D1 (yes, big jump). I decided to root the phone and install a custom ROM. Can't be too hard right? Its a Nexus for crying out loud. WRONG. Well I rooted pretty easily, and installed my first custom ROM for N4. To install this ROM, I had to erase boot.img, system.img, and userdata.img and then flash each individually from the ROM zip file I downloaded. This worked! I was winging it and it worked out. However, from then on, EVERY ROM I tried to install ended up in a bootloop. I have wiped cache/data, dalvik cache, and even my own (c)ache before flashing new ROM. They all end in bootloop (never ending).
I am able to revert to stock 4.2 easily every time. However, any attempt at installing a custom ROM from there is void. Today I downloaded 4.4.2.tgz from google and ran flash-all.bat. Everything works great! Until I try to boot up; bootloop. I fastboot format this and fastboot erase that, then fastboot flash each .img individually. I fastboot flash new radio, new kernel, etc. etc. but still bootloop.
I really am clueless as to what I am doing wrong or how I screwed myself somewhere along the way, but I am humbly coming before my superiors and asking for help. Please offer me the simplest solution and call me dumb for not seeing it, I will hold you in my heart 4eva
Click to expand...
Click to collapse
This is why once I have my phone rooted, there's no turning back to stock.
Are you sure that you wiped system, along with everything else between adventures? (factory reset via recovery)
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
This is why once I have my phone rooted, there's no turning back to stock.
Are you sure that you wiped system, along with everything else between adventures? (factory reset via recovery)
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Yes. I even just did it again to make sure, but I am still watching the beautifully colored circles fold in on themselves.
CausableMidget said:
Yes. I even just did it again to make sure, but I am still watching the beautifully colored circles fold in on themselves.
Click to expand...
Click to collapse
Ok, gonna make a suggestion, and it's totally on you if you want to take it, and of course I won't be held responsible. I have had a bootloop or two on my G2 (the original), I would get impatient and pull the battery. (wish the Nexus 4 had a removable battery) Without fail, that cured the bootloop. Just remember, that was a G2, not a Nexus 4.
Don't ask me why it worked because I have no clue.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Ok, gonna make a suggestion, and it's totally on you if you want to take it, and of course I won't be held responsible. I have had a bootloop or two on my G2 (the original), I would get impatient and pull the battery. (wish the Nexus 4 had a removable battery) Without fail, that cured the bootloop. Just remember, that was a G2, not a Nexus 4.
Don't ask me why it worked because I have no clue.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I have cycled power a few times during the boot to no avail. I also just reverted back to stock 4.2 and then installed OTA 4.3 update hoping outcome would be different (definition of insanity according to Vaas). I don't know what to do. It's just not in me to run 4.2 forever
CausableMidget said:
I have cycled power a few times during the boot to no avail. I also just reverted back to stock 4.2 and then installed OTA 4.3 update hoping outcome would be different (definition of insanity according to Vaas). I don't know what to do. It's just not in me to run 4.2 forever
Click to expand...
Click to collapse
Have you tried calling an Exorcist?
I've run out of ideas!
Sent from my Nexus 7 (2013)
For everyone interesting into upgrading to Android 7 be warned that are some issues going around right now and no one really knows what is causing the problems or what the fix is. So I was running the latest Pure Nexus rom and upgraded to Android 7 using the OTA file and the boot.img provided. Everything went fine and the system boot correctly. Well I decided to flash Pure Nexus back and the system was stuck in a boot loop between the white google logo and the "The system can't be checked for corruption" screen (unlocked boot loader). Well the good man Heisenberg got involved and recommend his full system stock restore guide (without locking the boot loader; don't do it or you will be completely out of luck). I used his guide and flashed 6.0.0 (MDA89D) and also 6.0.1 (MTC20F). The phone continued to boot loop and never boot. I was still able to boot into TWRP, so I tried a manual flash of Pure Nexus and MTC20F Vendor, no luck... Then I tried reflashing the Android 7 OTA update and boot.img, still a boot loop... There was an earlier thread about this issue, but I felt led to make sure this news and warning gets out!!! I ended up contacting google and project fi and I am getting a replacement phone.
While this issue seems to be rare I want to list my conditions in hoping preventing the issue for you!
- I was on MTC20F Vendor (with Pure Nexus)
- I flashed the Android 7 OTA update from the latest Pure Nexus build
- I did a semi dirty flash (could be root of problems) (I did this due to a recommendation, that was meant for a stock android 6 to 7 upgrade)
- The root of the issue could be going from a custom rom to the stock Android 7
- My system was rebooting and restating just fine with Android 7
- I wiped my system and flashed Pure Nexus back and the issues started
- This issue for now has no fix; Heisenberg (really thanks man) was a big help but didn't know what to do about it
Hey anyone who sees and reads this; would super appreciate answering the poll so we as a community can collect data about this problem to help prevent it in the future. Currently there is no fix for this weird semi(can access recovery)/hard(never boots into system) brick
Thank you!
Sounds like you should have just flashed stock before flashing the N OTA.
dratsablive said:
Sounds like you should have just flashed stock before flashing the N OTA.
Click to expand...
Click to collapse
same thing happened to me, i cant return to stock or 7 or backup, nothing
An important warning to all upgrading to Android 7 right now!
I currently find myself stuck on the boot animation (the colored circles) after trying to flash 7 then going back to Pure Nexus. I did a full data and system wipe before trying to install 7, but it still hung on the boot animation. Now after restoring my nandroid and reflashing Pure Nexus I'm still stuck on the boot animation.
Edit: Whew, reflashing Pure Nexus then restoring just the vendor image seem to have gotten me back to M.
Sent from my iPad using Tapatalk
I am stuck like this as well. I can't figure out how to fix this.
---------- Post added at 11:09 AM ---------- Previous post was at 11:08 AM ----------
TheBiles said:
I currently find myself stuck on the boot animation (the colored circles) after trying to flash 7 then going back to Pure Nexus. I did a full data and system wipe before trying to install 7, but it still hung on the boot animation. Now after restoring my nandroid and reflashing Pure Nexus I'm still stuck on the boot animation.
Edit: Whew, reflashing Pure Nexus then restoring just the vendor image seem to have gotten me back to M.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
My computer is not even detecting my phone with ADB... You know anything I might not?
UPDATE: Just had to unplug and replug my phone when in Recovery/Apply UPdate from ADB
stuck in bootloop as well....having google rma my device...flashed the aosp build of nougat just to test it out, then restored my backup of official noougat and got the bootloop...no clue what else to do in this case
I updated to 7 and then downgraded to 6.01. Boot loop city. I've spent 10 hours trying everything I could to fix it.
So i wanted to go for some Pie rom and it turns out i cannot do that because reasons. Done everything that was listed in instructions, done even more things like flashing stock image, wiping everything, flashing fbe recovery, wiping everything again (besides recovery ofc), then pushing the rom to /sdcard, flashing it, wiping internal storage. It doesnt really matter what i do and what rom do i flash. Every time i end up staring at Google's boot logo (AOSPExtended is stuck at boot animation). I know there is a line like "be patient" in the instructions, but my patience had to come to an end eventually and it was after like 2 hours of boot logo, and another 2 hours of AOSPEX's boot animation. The phone is not heating up, but it would crash on the 1st phase of boot animation and reboot till infinity after restoring TWRP backup. I really wanted to use Pie, but i have run out of ideas on how to make it boot.
It's really an unusual case. But I had it on my previous phone, the LG Optimus G. I'm from stock 4.4 and every higher Android version rom won't boot on my phone. I gave it up but two months later, I tried again and bizarrely, It boot fine without any reasons. Sorry I can't help you what the problem is, but I can only tell you that you can try Pie roms a few time later and wait for you luck
Kornafee said:
So i wanted to go for some Pie rom and it turns out i cannot do that because reasons. Done everything that was listed in instructions, done even more things like flashing stock image, wiping everything, flashing fbe recovery, wiping everything again (besides recovery ofc), then pushing the rom to /sdcard, flashing it, wiping internal storage. It doesnt really matter what i do and what rom do i flash. Every time i end up staring at Google's boot logo (AOSPExtended is stuck at boot animation). I know there is a line like "be patient" in the instructions, but my patience had to come to an end eventually and it was after like 2 hours of boot logo, and another 2 hours of AOSPEX's boot animation. The phone is not heating up, but it would crash on the 1st phase of boot animation and reboot till infinity after restoring TWRP backup. I really wanted to use Pie, but i have run out of ideas on how to make it boot.
Click to expand...
Click to collapse
Did you format data? Not wipe. Format.
pe81ge said:
Did you format data? Not wipe. Format.
Click to expand...
Click to collapse
How do i do that?
Kornafee said:
How do i do that?
Click to expand...
Click to collapse
By reading the flash instructions CAREFULLY.
Format data after flashing. It's the button next to advanced wipe button.
pe81ge said:
By reading the flash instructions CAREFULLY.
Format data after flashing. It's the button next to advanced wipe button.
Click to expand...
Click to collapse
Then yeah, I did it.
Did you ever get this working? I'm having the exact same issue. I've tried several Pie Roms and so far no luck getting past the boot animation.
Oreo Roms work and boot up quick. I've updated to the latest TWRP as well. Is there a v9 Vendor Image we can try flashing?
---------- Post added at 12:13 PM ---------- Previous post was at 12:07 PM ----------
Did you ever get this working? I'm having the exact same issue. I've tried several Pie Roms and so far no luck getting past the boot animation.
Is there a v9 Vendor Image we can try flashing maybe?
Sniggity said:
Did you ever get this working? I'm having the exact same issue. I've tried several Pie Roms and so far no luck getting past the boot animation.
Oreo Roms work and boot up quick. I've updated to the latest TWRP as well. Is there a v9 Vendor Image we can try flashing?
Click to expand...
Click to collapse
Didn't really have time to mess with this lately, as i need my phone up 24/7, but i tried to get this working as soon as first Pie ROM's started to come out. Couldn't get it working then, and 2nd time was about the time i created this post.
The lastest vendor image is OPM7.181205.001, Dec 2018, as far as i know, so... We are kinda stuck with 8.1.0 for now.