So yesterday I thought my gfs Nexus 6p was bootlooping and needed the fix that disables 4 cores. Today I found out that that is not the case and the phone can go as far the the rotating docs animation and it gets stuck there. The phone was running 8.1.0 (OPM3.171019.014, Feb 2018) so naturally I went a step up and flashed through the stock recovery this image
8.1.0 (OPM3.171019.016, Mar 2018). Nothing changed (except showing its updated in the recovery mode) and the phone is still rotating those 4 dots. How do I get this phone to work without wiping the data?
Related
My nexus 4 was rooted a while back before I got the OTA 4.3 android update via system update. Everything went fine then with that download. I was a bit anxious to get the 4.4 kit kat release and having seen it appear in system update 2 days ago I decided I was gonna download it yesterday and I did. After it finished the phone restarted and then was stuck in an infinite loop. I had no backup and so I decided to wipe; after which I had no operating system. I downloaded the
factory rom image of 4.4 (stock_mako_KRT16S.zip),
radio (cwm-radio-mako-m9615a-cefwmazm-2.0.1700.97.zip)
and bootloader (KK_4-4_BOOTLOADER.zip)
I flashed the radio first then then bootloader and both fine, then when it was turn for the factory rom it said error extracting file.. the dreaded status 7 error.
Anyways, I figured since it wasn't working I'd just go for a custom rom and I had rasbeanjelly on my phone from back when I rooted but never got around to flashing. So I thought I would try it and it flashed along with the gapps 4.3 but I've had several huge glitches such as the phone moving slowly and missing important google apps such as camera and such.
So I was up all night trying to figure out how to go back to stock rom and do a recovery and everything I tried was no luck. Kept running into the status 7 error. Watched a few videos that suggested I get Wug's Nexus Root Toolkit to unroot and then lock my bootloader and then flash a stock recovery. It didn't work because I realised one severe difference.
MY NEXUS 4 HAS A NEXUS 7 BUILD NUMBER.. I googled the internet and nothing..
Anyways. Says android 4.3
Build: JSS15Q
rasbeanjelly build: fri aug 23 2013 (probably old)
I just wanna know how I can get back to stock.
And I lost my root privileges as well when I flashed rasbean.
Any other information can be provided. THANKS MUCH.
Hello everyone. I have a issue with a new Nexus 7. Updated to 5.0.2 last night. Rooted today just fine via the Nexus Root Toolkit. Flashed ElementalX and its horribly slow on the bootup screen colored dots to android logo, then nothing. Can't get screen to show, it will sit long enough and reboot, and same slow boot sequence all over. I adjusted nothing in ElementalX besides the enable usb fast charge and OTG+charging, everything else is stock settings. I did make a backup and can still control it via the Nexus Root Toolkit, so I'm not too worried yet. Thoughts? Thanks in advance.
Yesterday some guy has changed my 3.5 mm jack in nexus 4. Old one was broken. After that I could not turned on my phone. I saw infinite boot. I had android 5 in that time.
Today I install android 4.2.2 (JDQ39) with help fastboot. Nexus 4 has booted now. But there is one problem. If I am updating nexus to android 4.4 or android 5, I see infinite boot again.
Also I tried to install CyanogenMod 13. The problem is same.
How to update my phone to android 5 or cm 13?
It seems, that the problem is bad position of rubber gasket in proximity sensor.
https://youtu.be/AZDAIgwbXk4?t=8m22s
Just so everyone's aware, I got this boot loop too today with the following scenario:
Completely stock 6p, upto date with latest MM, never been rooted, flashed, whatever.
Signed up for beta N programme today
Immediately got the N OTA update
Installed it - it rebooted post install but back into MM not N.
Rebooted - it got stuck on the Google logo for 30 minutes
Rebooted - permanent boot loop
I can get into the recovery menu and bootloader, and have tried sideloading the latest 7 OTA but still have the bootloop. Reset/cache clearing all tried.
Annoyingly my bootloader is locked - I've never tried doing anything other than installing standard OTA updates from Google so was unaware that unlocking it might save my bacon until it was too late.
I guess it's a phone call to Google tomorrow....
Update - sideloading this installed OK but I still have the boot loop:
6.0.1 (MTC20F) Link 5a1e93e9974908a0683a4ac8a732b81023f4b01182fd3ead3f091f54300de5ce
So all is not lost. I have an unlocked bootloader, but everything else the same as you. Doesn't really matter as I'm unable to flash anything....even updated my android SDK.
Anyway, I too signed up for Android beta program this morning, and instantly got the N update. Boom bootloop. Non stop. Most I could get it was 20 minutes after a factory reset.
What has worked for me (since 12pm today) was a factory reset and upon signing in to setup. I didn't. I set it up like it was brand new and didn't take ANY restore of apps or data from Google. I added my Gmail after and it's up and running with no reboots for 8 hours now.
It really sucks. The only thing I was able to salvage were my ringtones and notification sounds. It's like starting with a brand new phone ( froyo days without titanium backup). Google has a list of all your apps in the store but reinstalling all of them and logging in is a real pia. Been at it all day. But I do have a functioning stable Android 7.
Hi all,
I'm in a tricky position which is completely my fault, but cannot for the life of me get the phone to boot. In short -
1. updated to October security patch no problem, everything booted up fine
2. in an attempt to get rooted with Magisk again, I installed TRWP and *think* i installed to the wrong partition.
3. I can boot into fastboot, and can load TWRP, but as the touch screen isn't working I can't do anything in there.
4. For some reason adb doesn't seem to be detected, that may have been turned off during the update?
So, anybody got any solutions to me installing the OS again with Fastboot and a TWRP that can't be interacted with?
UPDATE - through some combination of luck and sheer determination, I've managed to get the phone to book again. I flashed the Sept boot file which seemed to kick it into gear, then re-flashed the October boot. All seems ok and I can breathe again. As you were.
Best,