This morning while at work i decided to try another ROM while I had some time. I have been running VRtoxin with no issues as of this morning. I downloaded the latest pure nexus and proceeded to advance wipe everything but storage. I flashed the rom and dynamic gapps. The phone booted up and seemed to be fine until i tried to open a few of the apps i use on a regular basis. When i went to open facebook, hangouts, google plus and some others i would get a notification that unfortunately the app was stopped. I tried rebooting and reinstalling pure nexus and kept getting the same messages. I finally got sick of it and decided to flash my back up i made this morning of VRtoxin. That's when the boot loops started. I have since then mounted system, advance wiped all but storage and tried to flash both VR and pure nexus. Neither will get past boot loop. I have waited 15+ minutes for each.
Thank you in advance.
nvanells said:
This morning while at work i decided to try another ROM while I had some time. I have been running VRtoxin with no issues as of this morning. I downloaded the latest pure nexus and proceeded to advance wipe everything but storage. I flashed the rom and dynamic gapps. The phone booted up and seemed to be fine until i tried to open a few of the apps i use on a regular basis. When i went to open facebook, hangouts, google plus and some others i would get a notification that unfortunately the app was stopped. I tried rebooting and reinstalling pure nexus and kept getting the same messages. I finally got sick of it and decided to flash my back up i made this morning of VRtoxin. That's when the boot loops started. I have since then mounted system, advance wiped all but storage and tried to flash both VR and pure nexus. Neither will get past boot loop. I have waited 15+ minutes for each.
Thank you in advance.
Click to expand...
Click to collapse
Try manually flashing each stock IMG
Boot, system, vendor, recovery. Then re flash twrp then try restoring your backup.
Yup. That's exactly what I would do. I would do. Report back and let us know!
Thank you for the advice. Before the response i just started over completely. Reflashed back to stock, flashed twrp and rooted. I'm back on VRToxin now with no problems.
I'm a ROM flashing junky, what do i have to do differently now on the 6p? I've never had this problem on my N6. On my N6 i would advance wipe everything but storage and then flash a new ROM with Gapps and never had this happen.
Related
Hi,
I have a nexus 10, rooted running latest nightly CM (19/12) and has been running fine without issues.
I turned it on this morning and its sat at the Google boot logo (and doesnt go any further).
I booted to recovery and did a reflash, wiped cache, wiped dalvic etc ... no joy.
tried a complete factory reset still no joy, is not booting past the google screen.
what next?
thanks
Dan.
DanielGwalter said:
Hi,
I have a nexus 10, rooted running latest nightly CM (19/12) and has been running fine without issues.
I turned it on this morning and its sat at the Google boot logo (and doesnt go any further).
I booted to recovery and did a reflash, wiped cache, wiped dalvic etc ... no joy.
tried a complete factory reset still no joy, is not booting past the google screen.
what next?
thanks
Dan.
Click to expand...
Click to collapse
Sounds like its something in the /system or /boot partitions, maybe. You might need to download the official, completely stock N10 firmware that the device came with and flash that to fix the problem. You can probably just google search for 'stock Nexus 10 firmware' and find a download link somewhere. Of course, if you have a backup file of before you flashed the CM nightly, then you could just restore that and it would work in much the same way don't panic, there is always a way
I got seemingly the same problem. Was copying a movie to the tablet and it crashed as usual. Probably ****ed up the file system or something. Now im traveling for the first time since I bought the tablet and it doesn't work. Grrrreat. :/
Edit: while I was sulking on the way to the airport (actually I wasnt sulking as I just got a new job 20 minutes ago yay) the tablet decided to boot up just fine when I wasnt watching.
Ive been running CM12 for a long time, but today I noticed I had a few missed calls and my phone hadnt rung. I rebooted the phone and it went into a boot loop. I cleared cache, but still bootlooping, dirty flashed the latest nightlie and then a full wipe - all of which resulted in the boot loop.
I restored my phone using the TOT method, but it would get to the setting up google account/wifi etc and reboot.
I used KDZ to install 30b lollipop ROM this seemed ok until reboot and then it would factory reset, optimise apps every time and be back to the setup screen.
I managed to install KK using KDZ and this seems more stable so used IOROOT and Autorec. I then flashed CM12 and GAPPS again, but it started to boot loop again.
I hadnt done anything to my phone prior to the problems - ie. no new ROMs, kernels or even apps.
Any suggestions or does it sound like something more physically wrong?
I have managed to get Cloudy G2 2.2 working without any problems except it isn't recognising my SIM. Does anyone have any thoughts or is this a dead phone?
I'm currently running the latest PureNexus (MM) with a pretty vanilla setup, I.e. no xposed, root, etc. All the sudden yesterday I had a hard crash while doing nothing in particular, a sudden reboot that sent me into a boot loop. It reboots right before the boot animation would appear. The only way I was able to fix it was to wipe the data partition. I was subsequently able to restore my backup and it booted successfully. The frustrating part is it's happened several times since then. In fact I can't keep it running more than a few hours without the same thing happening, even after doing a full wipe. Any ideas?
Thanks!
Arg, I tried flashing the new Android N system image (the official one) which basically flashes every partition and I'm still getting a boot loop. Is it possible that my SD card went bad?
ts_mpls said:
Arg, I tried flashing the new Android N system image (the official one) which basically flashes every partition and I'm still getting a boot loop. Is it possible that my SD card went bad?
Click to expand...
Click to collapse
Did you use flash-all.bat from google image or you flashed the images one by one?
I tried both. Both N and MM. Apparently I stumped Google too, they're sending me a new one.
that's weird... Glad you got a replacement though!
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
you are on a Beta, it is expected, if you need stability flash CM13
GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
I didn't think it was the rom since I reflashed a previously working version, tried the latest version, performed several full wipes, etc. I'm fetching the latest 13.0 and will get the latest opengapps mini for it and see if that helps.
GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
johnnyrichter said:
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
Click to expand...
Click to collapse
I figured
If you don't mind answering one more for me...
I'm on OK3. Is there any path to upgrade to a newer firmware while maintaining unlocked bootloader and root, or is it advised that I stick to OK3 and use only the DEV ABOOT roms like I have been?
johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
N0rth3rnl1ght said:
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
Click to expand...
Click to collapse
My phone ran fine on CM14.1(7.1.1) for at least a month and a half. Not sure why turning the phone off made it stop working with that version. CM13.1 is stable, have you tried that?
Been having the same issues with a 7.1.1 rom Mokee. For the time I've reverted to my S4....
Exact same steps i took. Flashing, wiping, and everything minus external SD.
There is a bootloader update which I did. There is a full update bootloader (I updated and now on PL1) which takes you to Safestrap then back yo TWRP. Others have reported just flashing a PL1 firmware in Odin under AP runs stable.
At this point I'll drop to 6.0 roms, my issues is holding cell service. I can't get any clean flashed rom to give me full data and call service.
I'd like to update firmware/radios if it's possible and won't break my unlock/root and still allow TWRP. Just not sure how to do it properly, starting with my unlocked/rooted BOK3 firmware.
TL;DR O was janky after dirty flash so downgraded but now N isn't right even after super wiping everything and reflashing stock N image.
Ok so I have no idea why I decided to try out O with all the dumb bugs that are being reported and the lack of a simple night light enabler but I did anyway. Phone was working great on 7.1.2, had the night light and blue pixel accents, the round icons actually just showed up for me which I like better than all the craziness of 5 different shaped icons cluttering up everything.
I dirty flashed stable O and it was janky as hell so after a few hours I decided to downgrade using my nandroid backup I just made. All seemed fine until I got in my car and noticed Bluetooth share was broken which kept causing force closes. I tried everything to fix it but nothing worked, had to end up reflashing latest N image. From that point all went downhill.
Phone will not show all the round icons anymore no matter what (play store being one that I totally despise being that huge play button, music, games, photos, movies, maps, etc but phone, messages, camera contacts and a few other are working), assistant would not enable and only screen search was there, Google drive backup isn't working either even with turning it off and on but it just says it's disabled by the administrator (??), I even went in to twrp and wiped EVERYTHING 3 times under the advanced menu and chose to repair the system and then fully ADB flashed the stock N image again.
After that, I rooted with magisk but now BusyBox won't install as systemless to the su/bin folder, I flashed both the night light only and the full pixel mod from gerard hoping it would enable the round icons on the GNL but it didn't. I tried flashfire to flash the N system again to clean that up but it just turned the phone off every attempt. I finally got it to work by reinstalling magisk but it didn't actually flash the system even though it went through the motions and said it was successful. I had to do it again for it to work but everything just seems weird now. What the F am I doing wrong? I know it's not a pixel thing for the round icons bc my wife's Moto z force just got 7.1 this weekend and the round icons showed up for her with no mods, no root, and she has GNL like me.
Help?
Try downloading a custom ROM like Nitrogen or Aquarius. Both of those have the options you want without having to flash any other mods. As for Google Assistant I've only had luck using Beans Gapps full package or open Gapps stock package. I personally prefer Beans. Do a full wipe before you flash and you should be good.
First of all, you went from N to O with a dirty Flash.... Of course there will be bugs. If you want to go back to N, Flash N image(boot, vendor, radio, system), when it boots up, go to settings and then perform a factory reset. After that, you can restore your Nandroid backup.
Thanks All,
Yes I do understand the issues with going from N to O on a dirty flash which is why it was janky and I decided to roll back. As mentioned, I used TWRP to wipe everything 3 times and then reflashed the latest stock N image. Google assistant worked after doing that and the interesting thing I found was if I disabled or deleted apps from the phone and then redownloaded or reenabled them, the round icons began showing again (i.e. google play, docs, sheets, etc) so that issue is resolved. I did not use the nandroid backup I made, I basically just started over from scratch and even though the Google Drive backup is still showing "disabled by your administrator", I see a new backup that was made this morning at 6:13am. I also installed busybox through magisk now rather than the separate app so I guess the only thing left outstanding is why the phone still says the Drive backup is disabled by an admin.
I would grab Nexus Root Toolkit, I install to C:\NRT, download the full August Nougat image, save it to C:\NRT too, then do a complete stock restore, this will wipe everything off phone.
Put you back to starting line and then race with flashing and mods.
ossito2012 said:
I would grab Nexus Root Toolkit, I install to C:\NRT, download the full August Nougat image, save it to C:\NRT too, then do a complete stock restore, this will wipe everything off phone.
Put you back to starting line and then race with flashing and mods.
Click to expand...
Click to collapse
I did use wug's toolkit to flash over ADB. I wonder if the image might have been slightly messed up even though the SHA-256 matched. I could always try to redownload the image again. I was going to wait until 8.0.1 was released to try O again but when I did have O, the backup options were stuck on "waiting for backup" (the menus are slightly different in O) and it never seemed to move forward. I researched that and I guess it's a known issue with some phones and a fix is supposed to be coming out this month but at this point, who knows.
jrg67 said:
I did use wug's toolkit to flash over ADB. I wonder if the image might have been slightly messed up even though the SHA-256 matched. I could always try to redownload the image again. I was going to wait until 8.0.1 was released to try O again but when I did have O, the backup options were stuck on "waiting for backup" (the menus are slightly different in O) and it never seemed to move forward. I researched that and I guess it's a known issue with some phones and a fix is supposed to be coming out this month but at this point, who knows.
Click to expand...
Click to collapse
Toolkit? FFS- fully wipe your device and install full 8.0 image. Done. That is what a full image is for --> janky.
v12xke said:
Toolkit? FFS- fully wipe your device and install full 8.0 image. Done. That is what a full image is for --> janky.
Click to expand...
Click to collapse
I don't think you are fully understanding what the situation is. I have said now 2 or 3 times, I have completely wiped the phone 3 times in a row using twrps advanced settings and I flashed the latest stock N image. The only reason I used wugs toolkit was so I didn't have to ype out all the commands to flash. After the flash was done, I manually flashed twrp again and re-rooting using magisk. Anyway, things are mostly back to normal now. I will manually flash O again at a later time.
jrg67 said:
I don't think you are fully understanding what the situation is. I have said now 2 or 3 times, I have completely wiped the phone 3 times in a row using twrps advanced settings and I flashed the latest stock N image. The only reason I used wugs toolkit was so I didn't have to ype out all the commands to flash. After the flash was done, I manually flashed twrp again and re-rooting using magisk. Anyway, things are mostly back to normal now. I will manually flash O again at a later time.
Click to expand...
Click to collapse
Still wrong. Nuclear flash everything even wiping the whole twrp since its a huge leap from N under the hood. Never dirty flash and of course clean flashing still won't be enough. Do a nuclear flash, wipe everything including your storage and recovery, back it up. Don't be lazy then be frustrated at a plethora of bugs if you didn't even flash properly.
phantom146 said:
Still wrong. Nuclear flash everything even wiping the whole twrp since its a huge leap from N under the hood. Never dirty flash and of course clean flashing still won't be enough. Do a nuclear flash, wipe everything including your storage and recovery, back it up. Don't be lazy then be frustrated at a plethora of bugs if you didn't even flash properly.
Click to expand...
Click to collapse
To be clear, what do you mean by "nuclear flash" bc I'm pretty sure that is exactly what I did, 3 times. Wiped dalvik/art, system, data, userdata, cache from twrp. As for wiping the recovery, that gets done during the flash of the image. So I ask again, what did I miss? Also, it's been said many times that dirty flashing can cause issues, I get it. I wasn't being lazy with trying to get back to N which is the whole point of this thread.