So here's my problem, I have a nexus 6p on which I am unable to install CM13 nightlies . I have tried installing other roms like chroma rom and they seem to work fine but when i try to flash cm 13 nightlies (yes, i am doing a clean flash), it flashes without an error, but i get stuck on the google logo screen. I have tried waiting, erasing all user data and every other thing. I cant seem to get any thread or anything about this online, so whats the problem? Any help would be appreciated
I had an issue like this. Try flashing the latest vendor image via fastboot rather than the flashable zip file.
Sent from my Nexus 6P using Tapatalk
Related
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
No suggestion, but I just flashed SlimBean on mine from a full wipe, and I'm having the same issue.
I tried SlimBean again, and it worked. Here's what I did:
1. Updated my bootloader. Mine was still 4.13, and it looks like the most recent version is 4.23. I flashed the img from this post using NRT.
2. Went back to unrooted stock with NRT. (I had to update my bootloader to do this.)
3. Let it boot back into unrooted stock, wept with joy, made a nandroid from NRT.
4. Flashed the SlimBean 1.9 weekly and minimal gapps from NRT's advanced area.
5. Watched in amazement as it boots obediently. Let sit about 10 min, and rebooted.
I'm essentially lazy, so yes I used NRT instead of manually pushing everything with ADB. ADB was plan B. It was briefly plan A, but I got tired of trying to convince the Android SDK that I did in fact have the Java JDK installed.
Mhhhh....
PatrickMac said:
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
Click to expand...
Click to collapse
Well I have the same problem with booting Ubuntu touch.... Either it's stuck on white Google Logo or stuck on Cyanogenmod Logo... Have flashed it with TWRP and MultiROM...
I recently got a nexus 7 2012. I unlocked it and installed the custom recovery (CWM) according to the guides given in the forum and elsewhere. The problem comes when I install a custom ROM like CM10.2, It installs fine, but the boot does not resume after the CM animation. I tried another rom like AOKP and even TWRP as recovery, still the problem persists. My bootloader is 4.23 and flashing back to stock ROM works as normal. Please help.
What recovery you use. And what tool you use to root. For I use WUG toolkit. And install TWRP. And install CM 10.2 with no problem. Maybe you not really root. Update your superuser before that
Sent from my Nexus 7 using XDA Premium 4 mobile app
Stupid question: are you sure you are flashing grouper ROMs?
Tried a lot of combinations with ROMs and recoveries finally I solved it. CWM wasn't working with its wipe options and tried TWRP and gave the full wipe of all partitions before flashing CM and gapps and it worked!!!!
Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5. Any help would be much appreciated.
Did you flash vendor?
Sent from my Nexus 6P using Tapatalk
Ovrclck said:
Did you flash vendor?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean like Rom from google direct?
Ovrclck said:
Did you flash vendor?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not sure that would be an issue, I ran a ROM with an outdated vendor and all that happened was I'd get a popup reminding me that it was out of date
Chief_runningwater said:
Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5.
Click to expand...
Click to collapse
WOW! What a sentence! :silly:
Chief_runningwater said:
Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5. Any help would be much appreciated.
Click to expand...
Click to collapse
I'm having the same problem as you. No matter what I end up bootlooping at the rom splash screen eventually. Even after the rom appears to be doing well.
dirtyreturn said:
I'm having the same problem as you. No matter what I end up bootlooping at the rom splash screen eventually. Even after the rom appears to be doing well.
Click to expand...
Click to collapse
Most likely a vendor issue. I had the same. Most roms are fine with the stock Google vendor, except for SinLess rom (which I use) that has its own vendor file. Its a new thing that came with the 6P and 5X I believe.
If you're on stock already and you have the factory image from Google, extract it, you'll find the flashall script with another zip file containing system and other images. If you're fine with flashing over, run the script. If not just extract the second file, you'll get the system, boot, cache.. imgs as well as vendor.img
Code:
fastboot flash vendor vendor.img
Dissmeister said:
Most likely a vendor issue. I had the same. Most roms are fine with the stock Google vendor, except for SinLess rom (which I use) that has its own vendor file. Its a new thing that came with the 6P and 5X I believe.
If you're on stock already and you have the factory image from Google, extract it, you'll find the flashall script with another zip file containing system and other images. If you're fine with flashing over, run the script. If not just extract the second file, you'll get the system, boot, cache.. imgs as well as vendor.img
Code:
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
Must we flash the vendor.img after every rom?
dirtyreturn said:
Must we flash the vendor.img after every rom?
Click to expand...
Click to collapse
Nope, once, and you should be good. Unless you somehow managed to erase it in recovery or something. If you see a bootloop again, you know what to do. Its just another partition like system, cache, recovery..
Like I said, only some roms require you to flash their own vendor images. From what I know so far, SinLess and PureNexus.
I'd try a stock rom with the stock vendor first, if I were you, just to get things running. Then flash a custom rom.
Dissmeister said:
Nope, once, and you should be good. Unless you somehow managed to erase it in recovery or something. If you see a bootloop again, you know what to do. Its just another partition like system, cache, recovery..
Like I said, only some roms require you to flash their own vendor images. From what I know so far, SinLess and PureNexus.
I'd try a stock rom with the stock vendor first, if I were you, just to get things running. Then flash a custom rom.
Click to expand...
Click to collapse
Slight correction, aside from screwing over with the actual partitions being the cause, it's mandatory for every major android update from google (e.g. 6.0 --> 6.0.1) if you want to update your rom to the following android version (For just nexus as far as i'm aware).
The images that needs to be flashed when updating are radio, vendor, boot and bootloader. (Unless stated otherwise by the developer of the rom you wanna use)
Sent from my Nexus 6P using Tapatalk
So I did everythign I normally do with a new device!
1)I unlocked it through Fastboot
2) I downloaded the latest TWRP recovery image for that device and flashed it with Fastboot
3) I rebooted the device into recovery to check if everything is ok.
4) Proceeded to download Cyanogenmod for Nexus 6p (Angler) and OpenGapps ARM64 for 6.0 stock package and put them on the phone
5) Opened the Zips from the phone to check that none are corrupted
6) Wiped Everything on the phone via Advanced Wipe incl System, Data, Cache etc,
7) Flashed Cyanogenmod Zip first after that the Gapps package
8) Rebooted to System and waited for the phone to finish its first boot
This is where my problems begin. No matter what I do and how much I toubleshoot the first boot never seems to finish. I have played with devices long before I got the 6p and know that the first boot taked a long time but not this long!
I checked if it was the recovery, or the CM zip or Gapps but no matter how many scenarios I try and rule out Im stuck at the CM boot logo (Which seems pretty laggy). I even tried without gapps.
I searched online and cant find ppl with a similar problem. There are people who cant get past the Google logo but I get past that with no problem. Its just that I cant boot the OS.
I even checked a few guides to see if I missed a step when I was doing it on my own but no! I have done everything absolutely correctly and cant seem to find an issue this time (usually finding issues with Android and repairing them is my specialty ).
I can not think of ANYTHING that ive missed here. I just cant seem to find the problem. The hardware boots Stock/Factory imaged perfectly so its working fine. Where am doing wrong?
bogomil4e said:
So I did everythign I normally do with a new device!
1)I unlocked it through Fastboot
2) I downloaded the latest TWRP recovery image for that device and flashed it with Fastboot
3) I rebooted the device into recovery to check if everything is ok.
4) Proceeded to download Cyanogenmod for Nexus 6p (Angler) and OpenGapps ARM64 for 6.0 stock package and put them on the phone
5) Opened the Zips from the phone to check that none are corrupted
6) Wiped Everything on the phone via Advanced Wipe incl System, Data, Cache etc,
7) Flashed Cyanogenmod Zip first after that the Gapps package
8) Rebooted to System and waited for the phone to finish its first boot
This is where my problems begin. No matter what I do and how much I toubleshoot the first boot never seems to finish. I have played with devices long before I got the 6p and know that the first boot taked a long time but not this long!
I checked if it was the recovery, or the CM zip or Gapps but no matter how many scenarios I try and rule out Im stuck at the CM boot logo (Which seems pretty laggy). I even tried without gapps.
I searched online and cant find ppl with a similar problem. There are people who cant get past the Google logo but I get past that with no problem. Its just that I cant boot the OS.
I even checked a few guides to see if I missed a step when I was doing it on my own but no! I have done everything absolutely correctly and cant seem to find an issue this time (usually finding issues with Android and repairing them is my specialty ).
I can not think of ANYTHING that ive missed here. I just cant seem to find the problem. The hardware boots Stock/Factory imaged perfectly so its working fine. Where am doing wrong?
Click to expand...
Click to collapse
I'm not sure but on an old HTC phone I had the same issue which was caused by a mismatch between the rom version and phones firmware. I'm not sure how it works on the nexus hope someone here can help
Try different GAPPS ?
Sent from my Nexus 6P using Tapatalk
Have you tried flashing a vendor zip yet? Sounds like not booting cause missing binaries.
https://www.androidfilehost.com/?w=files&flid=43551
If you're able to get to twrp, wipe everything, flash cyanogen reboot, and then flash a different gappd
Sent from my Nexus 6P using Tapatalk
You must format data in TWRP or it won't boot.
Hey guys,
I have a little problem with my new OP2.
I unlocked the bootloader and rooted etc.
I installed Paranoid Android and I wanst sure which kernel works on it.
So I tried flashing one for CM13 and one for OOS3, but both of them wouldnt work.
Now Im trying to get back to stock or atleast flash the boot.img from the Paranoid ROM.
I can boot, access the recovery and bootloader. I flashed different boot.imgs (Stock and Paranoid) and recoverys. But none of them helped.
The touchscreen wont react at all. If I boot, if I am in the recovery. It just wont work. Hardware button seems to be fine though.
Any ideas how to fix that?
Try wiping system partition and flash the PA ROM again (and Gapps of course) and it will restore system and kernel back to PA default.
If touch still doesn't work, then you'll probably have to wipe userdata partition as something you installed with the kernels not supporting other than official latest CM13 sources is messing with your system.
You need to flash full stock using fastboot from unbrick guide.
Sent from my ONE A2005 using Tapatalk
google megaunbrick guide oneplus2 and follow that!
didn't got your logic behind flashing custom kernel that too on paranoid android, I can understand that for cm13 as the battery life sucks there but pa easily gives 6+ hrs of sot which any other rom or even a custom kernel can't even come closer to it in my personal experience.
meaning you can try to flash the whole rom through fast boot or use unbrick guide to go full stock.