I've been trying to flash my nexus 4 for anything past 4.2.2 it goes into bootloop.
ive tried flashing with twrp and adb sideload as well as flash-all.sh, from clean to dirty installs. even updating on 4.2.2 through system update to 4.3 causes bootloop as well. it always hangs on "Android is starting... Starting Apps"
this kernel log is from cyanogenmod 13 fresh install, I can provide different kernel logs if needed.
pastebin.com/BhpD1D65
edit:
in 4.2.2 imei/baseband version is unknown, but in bootloader it shows M9615A-CEFWMAZM-2.0.1700.48
onikii said:
I've been trying to flash my nexus 4 for anything past 4.2.2 it goes into bootloop.
ive tried flashing with twrp and adb sideload as well as flash-all.sh, from clean to dirty installs. even updating on 4.2.2 through system update to 4.3 causes bootloop as well. it always hangs on "Android is starting... Starting Apps"
this kernel log is from cyanogenmod 13 fresh install, I can provide different kernel logs if needed.
pastebin.com/BhpD1D65
edit:
in 4.2.2 imei/baseband version is unknown, but in bootloader it shows M9615A-CEFWMAZM-2.0.1700.48
Click to expand...
Click to collapse
I may be talking out of my ass here but I seem to remember someone else fixing this by wiping cache using stock recovery.
Sent from my Nexus 4 using XDA Labs
Looks like my system partition is corrupted, i'm unable to mount it through twrp.
onikii said:
Looks like my system partition is corrupted, i'm unable to mount it through twrp.
Click to expand...
Click to collapse
I'd just flash the Google stock nexus image, then flash the ROM you want.
http://forum.xda-developers.com/nexus-4/help/nexus-runs-jelly-bean-4-2-2-downgrade-5-t3314579/page1
Try looking in this thread. There someone else seems to have a similar problem to yours. There are several solutions suggested, and there is also links to other threads with similar problems.
Sent from my Nexus 4 using XDA Labs
Related
Guys I know there are a ton of threads with this problem but no matter what I try, i'm still stuck on a boot loop.
So basically I had PA Rom 3.99 RC2 on my nexus and everything was fine. I then tried to flash PA AOSP kit kat build
but my phone would not boot so I went with a factory image occam 4.3 Phone booted and all was good. I was liking the
stock experience and then about 4 days later after a reboot, phone got stuck on the boot animation X. It would not get out of it
so I decided to flash PA Rom 3.99 rc2 again via ADB push zip. factory reset, installed the rom and gapps, wiped caches and thought i was good to go. Well the phone again would not get past the boot animation of PA.
i then decided to go with the Factory image occam 4.3 via fastboot and installed it and everything. Again stuck on the X. So then I tried PSX rom 4.3 again via adb push, did my factory reset and flashed the rom and gapps and superSu. Also got stuck on the boot animation. Left it for over 2 hours bootlooping and nothing.
Going crazy I went and fastboot the 4.2.2 JDQ39 img and downgraded bootloader, baseband. Installed it and again, stuck on the X animation. just hangs there.
Any help? i don't know what else to try, currently using my HD2 and it is sooo slow :cyclops:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion but still nothing. Updated CWMR to 6.0.4.3 and tried the 4.3 stock image. Still hangs on bootup. android file transfer recognizes the device is plugged in via usb but just gives me the error "could not connect to device"
Oh man I don't know what's wrong with my nexus
bump bump
I'm having this same issue, and it happened just like you. I flashed CM 10.2 nightly 20131114 this morning and I tested it to make sure everything was working. I decided to reboot the phone, and after that I keep getting stuck at the boot animation no matter what I did. To no avail, I reflashed a working zip, restored a backup, restored another backup, flashed the 4.4 factory image (wiping the entire phone), the 4.3 factory image, and then I read that the 4.2 baseband can fix it, so I flashed the 4.2 factory image. That 4.2 image gets it to boot, but without baseband. Right now I'm trying different radios just to see if I can get service again. If it matters, I was running the hybrid 33/84 radio for T-Mobile's LTE when this happened. Very, very peculiar situation here. I've never had anything like this happen, and especially remain an issue after wiping the entire device. I'm hoping it's not a sudden hardware issue.
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Hmmy 4444 said:
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Click to expand...
Click to collapse
just re-flash 4.2, it'll work. I've been doing that since Monday. but I want kitkat too!!
my device is stuck on the boot animation too. is there a way to reinstall the default 4.3 recovery and just rerun the update or something basic like that? my device was almost at stock before running the update. the only two things: twrp and rooted via recovery. so i thought everything will work fine and now there is no backup...
badboy47 said:
Avoid using twrp recovery.
Click to expand...
Click to collapse
Why?
Just fastboot flash all the image files (boot.img,recovery.img....) from the factory image.
Nexus 4 with stock (originally 4.4.2), which wouldn't update to 4.4.3, due to TWRP being installed, so when 4.4.4 came around, thought I would download and flash myself. Not a huge expert, but have certainly flashed several phones successfully previously.
Initially using the Nexus Root Toolkit, unrooted etc, downloaded the correct file from https://developers.google.com/android/nexus/images, tried to update, and would not write the radio file (waited for ages), tried to do using adb etc, no go.
Finally downloaded the 4.4.2 image, and using fastboot, this successfully did everything up to userdata, erased userdata successfully, and sent file, but never completes writing. (writing 'userdata'...) If I reboot, just gets stuck on the 4 circles.
Have installed CWM and tried doing a factory reset, but can not mount data....
Anyone able to assist?
Thanks
hornetster said:
Have installed CWM and tried doing a factory reset, but can not mount data....
Anyone able to assist?
Thanks
Click to expand...
Click to collapse
Panic over...
Perseverence seemed to pay off. Just did more of the same, and tried installing the userdata by itself. Seems to have worked.
But now am stock, and still doesn't seem to want to install the updates....
Well, thought it was stock, but the latest OTA didn't install. Don't really know why, as I wasn't watching, but it did the download, then kicked off the install, but when I came back to it, was just sitting at the home screen, no messages and the update hadn't happened - still sitting on 4.4.2.
I had flashed 4.4.2, and I thought the only bit that hadn't worked was the userdata, which I flashed separately, recovery has been flashed to stock recovery...
Why hasn't it updated?
And how can I tell if 'everything' is stock?
Thanks.
Hey,
i tried to flash Lollipop again because sensors were not working, but now it is stuck booting.
Flashing Android 4.4.4 worked and booted fine. I also flashed TWRP recovery and wiped everything I could but it did not help. I also ran "fastboot erase ..." on all partitions.
Any help on how to wipe stuff or ideas are much appreciated.
Is there maybe a known bug?
regards
caesium2 said:
Hey,
i tried to flash Lollipop again because sensors were not working, but now it is stuck booting.
Flashing Android 4.4.4 worked and booted fine. I also flashed TWRP recovery and wiped everything I could but it did not help. I also ran "fastboot erase ..." on all partitions.
Any help on how to wipe stuff or ideas are much appreciated.
Is there maybe a known bug?
regards
Click to expand...
Click to collapse
Are you flashing 5.0 using the factory image? If so flash the bootloader image. Then reboot bootloader in fastboot. Then fastboot -w. Then flash the rest of the images
Sent from my Nexus 9 using XDA Free mobile app
Factory image - yes. I'll try that. I'll let it boot for 30 minutes now to be sure to give it enough time.
caesium2 said:
Factory image - yes. I'll try that. I'll let it boot for 30 minutes now to be sure to give it enough time.
Click to expand...
Click to collapse
It shouldn't take 30 minutes. Flashing system will probably take less than 5 minutes. That's the longest flash and does it in five separate chunks. When it finally boots for the first time it might take 10 minutes, but no longer than that
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
It shouldn't take 30 minutes. Flashing system will probably take less than 5 minutes. That's the longest flash and does it in five separate chunks. When it finally boots for the first time it might take 10 minutes, but no longer than that
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Let's see if it works.
EDIT: Unfortunately not. Even installing 4.4.4 and then sideloading the 5.0 OTA did not help. What else can I do?
Today I installed 4.4.4 again and had it working. Trying to sideload the OTA again gives a never ending boot.
Also tried to lock/ unlock bootloader but nothing helped.
I have no ideas what I could try next... Any advice?
Right now I got this error flashing 4.4.4 with the flash-all script:
FAILED (status read failed (No such device))
Maybe I messed up some partitions?
Flashing Android 4.4.4 again worked.
caesium2 said:
Today I installed 4.4.4 again and had it working. Trying to sideload the OTA again gives a never ending boot.
Also tried to lock/ unlock bootloader but nothing helped.
I have no ideas what I could try next... Any advice?
Right now I got this error flashing 4.4.4 with the flash-all script:
FAILED (status read failed (No such device))
Maybe I messed up some partitions?
Flashing Android 4.4.4 again worked.
Click to expand...
Click to collapse
WOW, today I was able to boot and it was checking the applications, but unfortunately it took like forever when it said "starting apps" and at some point I switched off the phone. I flashed the flashable zips from another thread when it booted...
was on version 6.x.x. of Pure Nexus on my Nexus 6P
Downloaded the latest version from here for 7.0.0 r14
http://forum.xda-developers.com/nexus-6p/development/rom-pure-nexus-layers-fi-wifi-calling-t3244563
I made a full system recovery using TWRP prior to install. Used TWRP to install the .zip of the update. install was successful according to TWRP. I clicked to install SuperSU and then rebooted. Now I'm stuck in a bootloop. I tried restoring my full backup from TWRP I made prior to installing the .zip but still stuck in a bootloop. So tried again with my original backup image and also no luck. I currently don't have a USB cable for my phone as I lost it. Any ideas on how to get out of bootloop? I've left it in the boot cycle (colored google splash screen) eachtime for at least 30mins. I can still get into TWRP and bootloader. Any help would be much appreciated. Thanks in advance.
Edit:
I ensured I wiped prior to each restoration. I also ensured that on my backup prior to trying to update that I selected all options in TWRP.
What version of TWRP are u using ?
And you wiped system/data/cache b4 flashing PN 7.0 ?
Then flashed PN 7.0 ROM/Gapps/Vendor ?
Sent from my Pixel XL using Tapatalk
scoot0073 said:
What version of TWRP are u using ?
And you wiped system/data/cache b4 flashing PN 7.0 ?
Then flashed PN 7.0 ROM/Gapps/Vendor ?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
TWRP version: 2.8.7.2
I wiped system/data and cache
I didn't flash vendor or Gapps. I currently have 0 ways to put them on phone. I'm gonna try to get a cable tomorrow and attempt to put them on but I don't know how I will without being able to get into the android OS. Now I'm trying to figure out what Vendor img I need.
A little more digging and I scrounged up my long lost cable.
Used fastboot to push new vendor.img and gapps.
Booted up like a champ. Thanks man
theonlyherb said:
TWRP version: 2.8.7.2
I wiped system/data and cache
I didn't flash vendor or Gapps. I currently have 0 ways to put them on phone. I'm gonna try to get a cable tomorrow and attempt to put them on but I don't know how I will without being able to get into the android OS. Now I'm trying to figure out what Vendor img I need.
A little more digging and I scrounged up my long lost cable.
Used fastboot to push new vendor.img and gapps.
Booted up like a champ. Thanks man
Click to expand...
Click to collapse
If you are using Nougat ROMs, you need to upgrade TWRP to 3.0.2-3.
Sent from my Nexus 6P using Tapatalk
Hi guys,
so, my LG G5 has just been sent in for RMA, meaning I need a phone while I wait for that, and I have a nexus 4, however, it is stuck in a bootloop. I can access fastboot and adb, and have tried flashing Android 4.4.4 and 5.1.1, with 5.1.1 reaching "Android is starting, loading apps" as the final screen and so far with 4.4.4, just on the google colours booting animation.
I've also tried clearing cache partition, and factory resets. Currently I am using googles flash_all script, but would it be worth flashboot flash recovery etc. etc.
Could anyone suggest how I go about things to fix this?
Thanks, Conn
update
So, as of yet, I have got it to boot into 4.2.2, however, it isn't reading a brand new sim card. also updating to 4.3 through software update causes bootloop, and 4.2.2 seems to be the only working android version. I tried installing custom recovery (twrp) and a custom os (lineage 14.1) and that bootlooped.
Thanks, Conn
EDIT: Also, the IMEI is not being displayed.. From what I've read, the phone is probably stuffed?
It the OS can't read the IMEI, yeah sounds like something is borked.
Are you running flashall wiping everything, or did you take out hte -w switch to leave personal data? I've had issues with my 4 (that led to my buying a refurb 5) that trying to flash but keeping personal data failed, I had to do a full open hose reflash.
\\ Sent from an Android or iOS device //