nexus 5X bootloop - Nexus 5X Q&A, Help & Troubleshooting

Dear Xda community,
i could really use your help.
So i had a working cyanogenmod 14.1 rom on my nexus 5X. I wanted to have cyanogenmod 13.0 on it, because of the theme engine.
So i made a backup using twrp. Then i completely wiped my phone. (twrp>wipe>advanced wipe>chose everything>executed).
Then i flashed cm 13.0. thereafter i booted my phone, but i couldnt get past the "google" screen. Then it booted again, but it wouldnt get past the "google" screen. And so on.
I tried wiping my phone and restoring my backup, but the same issue occured again. This issue keeps coming back no matter what I do.
I dont know how the fix this, please help.
thank you in advance. ~Jens

It sounds like a bootloader mismatch problem. Going from CyanogenMod 14 (Android 7) to CyanogenMod 13 (Android 6). This should theoretically solve your problem, although I haven't tried it. Flash marshmallow (Android 6) Factory image from https://developers.google.com/android/images#bullhead. Pick the last marshmallow release, MTC20K, let it boot once, do a factory reset, unlock bootloader, reinstall twrp and then try CM13.
Sent from my Nexus 5X using XDA-Developers mobile app

The bootloader is rarely a issue. Most likely the vendor is the culprit. Flash any recent MM vendor an it will let you boot.

Related

TWRP Invalid Password after MM Update (Z00A)

Hello,
I have recently flashed the Marshmallow update to my phone coming from WW-2.20.40.194. It was encrypted and used a PIN on both the boot and the lock screen. With Lollipop, I can decrypt my phone in TWRP by entering my lock screen PIN. However, neither TWRP 3.0.2.0 nor a TWRP repack (found at: https://drive.google.com/drive/folders/0Byp0425xydUaYzk1anRCak0zZXc) on Marshmallow are able to decrypt the phone, saying the password is invalid. I have tried the lock screen PIN, "default_password", as well as using an app called "SnooperStopper" to change my encryption password to something other than my lock screen PIN, with no luck. Is anyone else experiencing this or have a fix?
If i recall you must unencrypt before any flash. Your encryption key is now lost along with all your data. Sorry.
Sent from my ASUS_Z00AD using XDA Premium HD app
Maybe you'll need to downgrade to L, decrypt the phone, upgrade to M again and encrypt it a second time.
After uploading the M update, Asus also uploaded a rom to downgrade from M to L, so anyone can perform a downgrade just the same way they did the upgrade.
Thanks for the replies! I haven't lost any data, since I backed everything up manually beforehand. However, even if I didn't backup the data, I can still unlock the phone itself (get past the lock screen and to all my files), just not through TWRP's lock screen. I've tried encrypting before and after upgrading to Marshmallow, with the same results.
UPDATE:
Just tried again with TWRP (tethered and untethered) on a clean install, same results. Steps:
Used fastboot to completely erase phone (data, cache, dalvik, system, etc).
Flashed stock recovery for Lollipop (WW-2.20.40.194).
ADB sideloaded WW-2.20.40.194 in stock recovery.
Wiped data and cache again in stock recovery.
ADB sideloaded Marshmallow (WW-4.21.40.134).
Rebooted to system, logged into Google account, set up system, etc.
While setting up system, chose to lock device with PIN.
After setup, encrypted the phone.
Rebooted to bootloader.
Fastboot boot TWRP.
Tried to enter PIN, says invalid. Tried to enter "default_password", says invalid.
Fastboot flash TWRP, same results.
Hi yes, ive had the exact same problem running a nightly build of CM13 / Android 6.0.1. It just tells me the password is wrong. TWRP 3.0.2.0
Personally I think something changed in recent Android builds and TWRP just hasnt figured out that its broken yet. TWRP 3.0.2.0 is almost 6 months old now ...
I need to find a way to update my roms also so this is a problem.
I am glad to hear it is not just me having this issue. I believe this as well, though TWRP 3.0.2.0 worked just fine on an older version of XOSP (CM13-based, I think from a build around December 2015). Something must have changed since then.
I have discovered the problem. You can read all about it here.
http://forum.xda-developers.com/gal...wrp-mount-encrypted-partition-recent-t3468989
tl;dr
Snapdragon 800+ CPU phones (any maybe others) have HW_Crypro (hardware crypto chip) and Android 6 + enables this. Which requires recompiled TWRP with support for HW_Crypto
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?

Cyanogenmod not booting after install

Hi,
I'm completely new to customROMs at all, so please bear with me..
So, first I tried to flash Cyanogenmod 13 nightly on my G3 which failed with "system partition has unexpected contents after ota update". At this point I was unable to get past the "LG powered by Android" boot screen, but I figured that was okay, since the install failed. I was running Android 5.0 beforehand and after a quick Google search I decided to try CM 12.1 first.
So I started again with wiping the device and installing CM 12.1 which succeeded. However, I still couldn't get past the LG boot screen. I tried wiping and reinstalling CM 12.1 several times with no success.
I was following the official guide rooting my phone and using LG G3 AutoRec-Lollipop to install TWRP.
I don't really care about my data (it's all in the cloud anyway), but I'd like to get my phone to work again. Any ideas?
Thanks in advance!
what's your current twrp version?

I can flash and use only Lineage and LeeDroid ROMS, none of other ROM can be flashed.

Hi,
I m using Lineage 16 (20190813 111617)build on my HTC 10 (European model) I wanted to to try Pixel Experience with full wipe, format. But after flashing the ROM could not connect with WiFi. So could not continue with setup. Therefore after re-boot with TWRP I did following :
1) Restored all data except System and System image.
2) Then re-booted and device opened without any problem. However, HTC 10 could not detect SIM card and having error phone dialer.
I have replaced the SIM, re-booted the phone, wipe and factory reset. None of them helped. So I have again restored the Lineage again.
Then I had attempt to flash other 9,0 ROMs such as XenonHD, AOSİP 9.0. But all of them had stacked on boot-loop logo. I hope you can help to resolve above problem so I can enjoy to taste those ROMs on my beloved HTC 10.
Many thanks in advance.

Oneplus 5T bootloop

Hi there,
Yesterday I rooted my oneplus 5T and installed TWRP 3.2.1 & masgisk. Then, I´ve installed Pixel experience AOSP which seemed like fairly stable from the description. Everything went fine, the OS started I started configuring it then after setting the password I got the OS having always the setting app to crash. So, I thought well, I can just go to recovery and try once again factory reset. Otherwise, I can mount the recovery and install another ROM. I went to recovery and to my surprise it was asking for a password and mine didn´t work. I tried the factory reset and still the encryption stayed. I found that this version has a decryption problem and all my files were encrypted and not accessible, that was fine, since I had everything backed up. So, I have installed the new version of TWRP which seems to fix this issue after loosing all encrypted file. I have formated the data, system, dalvic and cache and installed once again pixel exerience but the OS keeps on bootloop. Have anybody seen something like this? How should I fix it? My best guess was to reinstall stock OS via adb, but in the past I've rooted a couple of devices and I've never seen something like this.
Thanks in advance

Oneplus One Bacon New Bootloop!?

Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
AnotherStupidUser said:
Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
Click to expand...
Click to collapse
You already lost apps by wiping data, but you still have your photos.
If you had GApps installed before android version upgrade, you now need to flash android 11 GApps. Wiki.lineageos.org tells you what and how.
Thank you for your help. Surprisingly for some reason I found a work around as the unofficial GApps didn't work as well. I wiped data again, so the apps were gone (it took me 3 hours to restore that), but all files were still there and I flashed back to 17.1 with GApps and it worked. Phone is working same way as before. Guess I will wait a LOOOOOOOONG time now until I will try 18.1 again. But again thank you

Categories

Resources