yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] discslinger:
Stuck in boot loop

I'm at a loss to explain what went wrong. After flashing TWRP - I could not flash the Chainfire zip I put in storage - and basically got message that said the storage would not mount. Never did I try to flash a SuperSU from inside TWRP.

Phone is stuck in boot loop it appears and I can't get adb to recognize the device.

If I hold the power button down - it says the device is corrupt/can't be trusted.

I'll work on adb recognition - but I can't even turn the phone off or on right now.

ugh. boy

what to do next?

I have read all the intructions for resoring stock and have necessary

---------- Post added at 09:04 PM ---------- Previous post was at 08:29 PM ----------

I am back into the bootloader after updating driver.

I just reentered TWRP recovery - and then the first option is to enter my password - which I do not have. At the top it says "Mount - Decrypt Data" I could push cancel like I did the first time - since I have no password. Pushing cancel takes me where I was before - swipe with the 'read only option' then to the TWRP Main Menu.

Pushing install on the menu to take me to the Install Zip screen - where again - I have 0MB storage.

Can I push super user through fastboot? Or do I have to go to step 11 and do a stock factory reinstall?

Soft brick right - so I'm not freaked. I'll beat this.

---------- Post added at 09:46 PM ---------- Previous post was at 09:04 PM ----------

Ok. Not losing any cool. I followed Heisenberg's Step 3 - and formatted. Since accordingly: " TWRP recovery cannot decrypt your data partition at this stage. In order for TWRP to be able to read/write on your data partition you will need to format it, a format will remove encryption."

I thought this was ok to skip with twrp version 2.8.7.1 or later. (I used 2.8.7.2) At any rate...

I thought I was home free - Now on the menu - Internal storage states 25,349 MB are being read. Ok cool.

I see: /supersu

but pressing that onscreen does nothing. I have the option to "Install Image" in the lower right corner button - but this is a zip. I am POSITIVE i place a zip file of Chainfire's 2.6.4 zip file on my phone's stoarge as plain as day. Checked this 3x or so before I went forward with this.

Interstingly, I pushed the soft key menu button - yes, TWRP's menu screen has an old style menu button, where I see messages "unable to find partition path for sdcard" and "unable to mount cache"

What am I not seeing - or need to do?

Man oh man.... thanks beforehand - if someone can give me insight/solution.

Sitting in bootloader or standing by inTWRP.

UPDATE:

If I select MOUNT in the TWRP menu - I see only cache partition is selected to mount. Not messing with selecting 'System" or anything else. Juts curious. I do NOT see a SuperSU zip. Suspsect I am seeing the TWRP files. Not sure anymore.

Update #2

Powered off 'til tomorrow. Downloaded stock bullhead images and files per H'berg's instructions to do a factory restore - unless I wake up and see/hear hot to 'fix' the current situation. Tx!
[Nexus 5X General] discslinger:
Unbricked - restored stock

Followed steps 11 to the 'T'. Success.

However, I restored build mmb29K - in order to root via using a modified boot image. I do not like the idea of proceeding from build mmb29P since that didn't work. I'm glad it happened in a way, because I'm not afraid to screw up - knowing I succeeded to restore my stock state manually.

If anybody can identify what I did wrong in the first attempt - that's be cool.

Tx.
[Nexus 5X General] Schrotty35:
Which modified boot image have you used? The latest is for i but not for k.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X General] discslinger:
I restored with the unmodified mmb29k image.

When I tried rooting the first time, my understanding after asking and reading was TWRP 2.8.7.2 made it un-needed to flash a modified image - since it was stated twrp would modify the existing image.

Now I have a hard time believing or understanding that. It seems some sort of boot.img must be flashed just before flashing twrp - as instructed in the OP. Is this true or not?
[Nexus 5X General] Schrotty35:
I have stock with root but i am not decypted.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X General] joetheshmo:
TWRP doesn't modify the boot image as far as I know. SuperSU 2.66 does.
[Nexus 5X General] Schrotty35:
I use it 2.66 but status is crypted and not decrypted.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X General] joetheshmo:
Format data in twrp and then flash 2.66 otherwise on first boot it will encrypt again before you have a modified boot img
[Nexus 5X General] Schrotty35:
Ok for me, i install rom, gapps (on cm based roms, format data, supersu, reboot. Right?

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X General] SlimSnoopOS:
Somehow missed your post. Yes, you should boot and remain decrypted as long as you have SuperSU 2.60+ installed. If not, fastboot format userdata again, flash SuperSU 2.60+ and then ElementalX kernel. Formatting userdata erases your entire phone, as you know.
[Nexus 5X General] discslinger:
Successfully rooted after soft brick

The difference between failing and success was installing a modified boot image before installing TWRP.

I'd like to see clarification on what it means that SuperSU "SuperSU 2.6x will patch your existing boot.img." ( and yes, I did read this entire thread and then asked on this issue)

This advice made me think to NOT install a boot.img after I unlocked the bootloader, and to proceed to install TWRP.

But it seems it is an absolute must to install a boot.img.

I did not want to take a chance to try to install any image that did not match the build number mmb29p - since there is no modified boot image for that. So after soft bricking I reverted back to stock mmb29k - and then simply repeated the rooting process and pre-installed modified mmb29k before pushing twrp. Then presto... no problems.

Another question remains. Since Chainfire's SuperSU supposedly modifies the so-called 'existing boot image' - does this mean any boot image could have been pushed prior to installing twrp and then this image would have been modified anyway?

Still curious about that.

tx to all.
[Nexus 5X General] Judim:
Is there a way to backup the encrypted data so that it can be restored (decrypted) on an unencrypted data partition?
[Nexus 5X General] SlimSnoopOS:
I don't have a firm grasp on whether encrypted to decrypted data restore is possible. I also haven't read anywhere that some has tried to do so on either Nexus device.

Edit: The most I could say is backup your app data with Titanium Backup (or similar app), transfer that to a computer, properly decrypt your phone and root (or install custom kernel), transfer that app backup to your phone and see if it will restore. I doubt it, but I also haven't tried it.
[Nexus 5X General] Schrotty35:
I dont find for k, only i.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X General] SlimSnoopOS:
MMB29K modified boot.img is in the first post, Section 7 for Traditional Root. It is just mislabeled as MDB29K
[Nexus 5X General] tacofromhell:
SuperSU 2.60+ modifies your existing boot image when you flash it, thus eliminating any need to seperately flash boot image.
[Nexus 5X General] joetheshmo:
Nothing in this guide voids your warranty
[Nexus 5X General] CBS - Development:
Awesome Guide!!!
[Nexus 5X General] aamir123:
I am having a problem when upgrading kernel, changing kernel or even updating rom. I get multiple force closes of what seems like system apps. I have tried to update kernel a few methods.

1. flash kernel, flash systemless su, even fix permissions and wipe cache don't fix this.

2. dirty flash system, flash kernel, flash systemless su still not fixed.

I'm not sure what to do. I have to do multiple clean flashes lately due to this issue. Also flashing gapps does not fix either.

I am currently on Chroma, using various kernels.
[Nexus 5X General] joetheshmo:
Flashing various kernels over each other is not a good idea.
[Nexus 5X General] aamir123:
When switching kernels I dirtly flash the rom then unsu then new kernel then systemless su. what other option do I have to change kernels?
[Nexus 5X General] joetheshmo:
Ah I see. That's fine then. Try flashing SuperSU before the kernel? Not sure it would make a difference.
[Nexus 5X General] aamir123:
Right now my main problem is the settings app force closing. I'm unable to get into swings at all. Ice tried re rooting and fixing permissions.
[Nexus 5X General] h4cky0u:
I followed the guide in order and got stuck at the Decryption step because it states I have an invalid password for decryption (using twrp-2.8.7.2-bullhead.img). Now my device just stays at the animated Google boot screen if I try to boot it normally. Any help?
[Nexus 5X General] Sytheii:
For their password request I believe if you use a pattern, you have to translate it into a numeric code, or a pin. Like so...
[Nexus 5X General] h4cky0u:
I used a password and not a pattern or pin, but the password doesn't work in TWRP. I read that "default_password" worked for some people, but it is not working for me either.
[Nexus 5X General] Sytheii:
Perhaps post a similar question asking for clarification on another thread about twrp, or maybe email them? At their site they say only a fraction of emails are returned, but you might get a response. I remember when setting up the phone they have you do a backup security setting, for me i used fingerprint first, them pattern. Did you only enter in a password?

All i can think of sorry.

:/
[Nexus 5X General] aringler:
hey,

I wanted to root my nexus 5x too, first I tried to do so with the nexus tool kit....

it was all working until it came to the root process:

it said in the log:

Rooting....

Waiting for your device....

and nothing else happened anymore.

So I tried it manually with your guide.

As the bootloader was already unlocked, I continued with flashing the recovery (twrp 2.8.7.2) in fastboot.

Then it rebooted into the recovery.

Then twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.

I allowed the system modification then... so then before rebooting, twrp wasn't asking me if I want to flash the SuperSu.

Since this I'm stuck in a bootloop.

I can boot into the bootloader and recovery, I also tried to do a factory wipe or also formating data. But none of them worked for me. I'm still stuck in the bootloop...

I have no idea what to do now....

I'm really thankfull for every kind of help!
[Nexus 5X General] Mawth:
It's hoped you've resolved your bootloop by now, but if you haven't, and it was me, I'd take a clean slate approach and follow the OP's Step 11 to get everything back to stock. Once you've successfully done that and booted the stock ROM, then I'd flash TWRP via fastboot, boot into TWRP, make an nandroid of the stock system, then flash the latest SuperSU.zip via TWRP. After booting, you should have root.

I've never used the nexus tool kit you reference, so I'm not sure what all it does. The method I describe above has worked for me on many occasions.
[Nexus 5X General] queerquirks:
Is the stock kernel found in the boot image? Do I need to flash supersu to root again? Am on systemless root with stock and elementalx kernel.
[Nexus 5X General] Mawth:
Yes. Boot.img contains the kernel.

SuperSU modifies the system.img so it shouldn't be necessary to flash again.
[Nexus 5X General] discslinger:
You are where I was a wek or so ago.

I has same situation: "TWRP wasn't asking me to flash SuperSU."

I followed step 11 to the T - but I restored mmb29K instead of mmb29p - becuase there is no modified image for that build yet, as far as I know.. I then successfully rooted - but used a modified boot.img (for mmb29K).

I am glad I soft bricked - not saying you should be - but it feels good to know you can restore the system after screwing up. Take your time. Good luck.
[Nexus 5X General] alwaysbelieve1:
I just unlocked my boot loader and flashed TWRP. I set it for Read Only so I can root systemless. I am trying to follow the instructions to make a backup, but it is not working. It is erroring. Any advice please.
[Nexus 5X General] tacofromhell:
You have to give us more information. What error?
[Nexus 5X General] alwaysbelieve1:
Appreciate the support! I actually I was able to figure it out and everything is now working the way it should. :)
[Nexus 5X General] jamy015:
Please post the problem you had as well as the solution, so that other forum members who run into the same issue may use your solution! :)
[Nexus 5X General] SlimSnoopOS:
Sorry for the delay [MENTION=4316331]georgiapi[/MENTION], my browser deleted my initial reply!

1) Yes. Being that you use a custom rom, all that you need to do is flash your monthly custom rom update, the vendor.img and radio.img. The vendor.img is essential in that it contains proprietary blobs that allow the rom to function properly. Google apparently has not updated the radio.img in December or January, so it is likely the February radio.img is unchanged. Flashing the radio is not always necessary.

2) No, they are always useful! What matters is what you backup or how you title them. If you use a rom or something that modifies your vendor.img, say Layers themes, then you should note that in your nandroid title. Then backup data, system, boot, and vendor.

Most roms leave the vendor alone but if it is stated that vendor is modified, make sure to flash the stock vendor before moving to another rom.

3) This means update only what you need to. Just like I explained in #1, not everything is necessary. For you, being that you use Omni rom, all you need to do this month is flash the vendor.img and flash the February Omni update when it is released. Ideally for custom rom users, we just need to flash our monthly rom update, vendor, and radio.

Again, my apologies for the delay.
[Nexus 5X General] georgiapi:
Thanks SlimSnoopOS,

Still a little UN-surefooted but its clearing up.
[Nexus 5X General] SlimSnoopOS:
That's fine, don't hesitate to ask and I'm sure things will get cleared up
[Nexus 5X General] Schrotty35:
I have install latest stock rom complete with decrypt but my phone is crypted and not decrypt.
[Nexus 5X General] berndblb:
You have to flash a modified boot.img after decrypting or it will encrypt again on next boot
[Nexus 5X General] KostisTTT:
Restoring backup TWRP, stuck in bootloop

Hello everybody.

Very disappointed and stuck...

I have a Nexus 5x, rooted and everything was normal.

Today, I tried to restore a backup with TWRP and I got the message "Cannot mount, read only''.

I entered the "Mount" menu in TWRP and I changed the permissions.

Then I tried again to restore a backup.

I think that it was loading the image (then I stopped looking my phone for a while) and then I am in a bootloop... (about an hour)

Any ideas??

Thanks in advance
[Nexus 5X General] SlimSnoopOS:
Hold the power and volume down to boot into the bootloader. Then go into TWRP, do a factory reset and then try to restore your nandroid. If you need to, mount system once again.
[Nexus 5X General] ryanwalexander:
TWRP recovery only seems to be launching right after I flash it. After I reboot the phone it doesn't launch from bootloader anymore. I get the triangle android guy thing. Is this happening to anyone else?
[Nexus 5X General] SlimSnoopOS:
When you boot into TWRP, are you giving it write access or installing root either by itself or via custom rom? TWRP will not stick in any other case.
[Nexus 5X General] georgiapi:
If ryanwalexander's experiance level is as weak as mine he may want to use the Nexus Tool Kit by Wugfresh to recover?.
[Nexus 5X General] KostisTTT:
Hello again..

Thanks for the help.

I entered TWRP

Just did a dalvic, cache wipe and restored backup.

Now the problem is that the first lock pattern dont let me unlock the device.

The shape I was using for the first unlock of the phone does not function (shows "wrong pattern")

Any Ideas???

Thanks again..
[Nexus 5X General] georgiapi:
Yeh, I learned the same thing. When making backups I remove my screen lock PIN which takes out the finger print too. When you do a wipe and load a BU with a pin and finger print it don't work.

You most likely need to do a full wipe and factory reset.
[Nexus 5X General] SlimSnoopOS:
There's a remedy for that :good:

Edit: As of right now, TWRP unfortunately fails to backup secured lockscreens. Hopefully this is addressed in a future TWRP update and the loophole is closed.
[Nexus 5X General] KostisTTT:
One (last) problem

Hello again, guys.

I managed to restore the backup and bypass the first's screen security pattern by deleting the file data/system/locksettings.db in TWRP.

I noticed that the smart lock setting in Security menu is missing...

Any way to restore it???

[Edit]: Ok, found it... (Enabling under Trust Agents)

Thanks in advance..
[Nexus 5X General] SlimSnoopOS:
You're welcome! Enjoy your day :highfive:
[Nexus 5X General] georgiapi:
What rom are you running?

---------- Post added at 10:33 AM ---------- Previous post was at 09:56 AM ----------
[Nexus 5X General] SlimSnoopOS:
Not sure if you were asking me but I'll reply haha I use Chroma! I just wanted a rom that is mostly stock but included a few tweaks like advanced reboot and the ability to hide the nav bar in certain apps (like Chrome). Plus the recommended Banks gapps package leaves almost nothing installed except the Play Store and I love that. I may try something else down the road, but wanted to keep things simple for now.
[Nexus 5X General] KostisTTT:
Hello again, guys..

Today, I received an Android System Update.

I 'm rooted with systemless root and I have Xposed, GravityBox and Gel Settings installed [6.0.1 (MMB29P)]

How can I update?

Should I download and flash the factory image as described by Heisenberg's How To - in section 10

or should I just press the download button in my device??

Thanks in advance..
[Nexus 5X General] SlimSnoopOS:
Hi there,

If you are on stock rooted, use section 10 but just update system, boot, cache, and vendor. Then root again and install Xposed. Do not flash radio, recovery, or bootloader as they are the same as previous updates.
[Nexus 5X General] KostisTTT:
Thanks a lot, SlimSnoopOS..
[Nexus 5X General] Rozalina340:
Thank you for this awesome How-To!

I really want to try this out , but I'm worried about my warranty , I know it's kinda stupid but.... I just got my phone a few days ago so... I think I will come back once I'm ready ^^
[Nexus 5X General] jamy015:
Thanks a lot for this How-To! I was able to successfully unlock bootloader, backup the EFS using the tutorial :D

I rooted using phh's open source SuperUser instead of the closed-source SuperSU, this works perfectly on this phone! (ENG version). Maybe I will write a tutorial for this, but it's not hard (just flash the boot image, and install the APK)
[Nexus 5X General] Bogie_Inbound:
Does anyone know if there is a modified boot img for the MMB29P build? From my searching, it seems there was not.
[Nexus 5X General] queerquirks:
Can I use systemless root on latest MMB29Q?
[Nexus 5X General] :
Yes. I did it last week, just as easily as the previous security patch.
[Nexus 5X General] queerquirks:
Dayummmm, this reply came in just when I click reboot in twrp :eek: Now on optimizing apps..

What did you flash to update? Vendor img only since its incremental update or the whole deal ( system, boot, vendor, cache?)

Which SuperSu version, 2.66 or 2.67?

Thanks!
[Nexus 5X General] :
I wanted a clean slate so I flashed the entire build with SuperSU 2.66. (This was so I had a fresh start to maintain my long-term ElementalX build, but should work fine for you too :p). Honestly the security updates are a pain to me - I'm waiting until the next major MM increment before spending that much time on a system update again.
[Nexus 5X General] Rozalina340:
Well I decided to finally install a custom recovery and install a ROM. It worked perfectly! Thank you! :D
[Nexus 5X General] matase:
Cannot copy item. the device has either stopped responding or has been disconnected. I'm trying to copy SU file to my internal storage. What is up with this?
[Nexus 5X General] berndblb:
You enabled file transfer under USB for charging notification?
[Nexus 5X General] :
thanks for the directions
[Nexus 5X General] naselKiDD:
These instructions were super helpful! Ran into one small hickup. Running

adb devices

worked no problem the first time. However, once in the bootloader running

[STRIKE]fastloader[/STRIKE] fastboot devices

had no response. Took me a while to find out that the google usb driver didn't install correctly. Not to mention I couldn't download it through the SDK Manager as suggested every where. I was able to let Windows suggest drivers and one of them worked. Everything else was smooth sailing. Did this running 6.0.1 with the latest patches.
[Nexus 5X General] SlimSnoopOS:
The command is

Good that you resolved your driver issue.
[Nexus 5X General] shindiggity:
Sorry if this is a dumb question but is there any difference using this method compared to Wugs method? I'm coming from LG G3 but want to make sure I get this done the best/easiest way possible. Any advice is appreciated!!
[Nexus 5X General] Scottchy014:
Not too sure about all of it but I do know the recovery flashing kind of messes up on the NRT. Maybe it's a setting preference but if you flash TWRP, NRT will also restart your 5X. Since TWRP is initially in "read only" (mine always starts this way) mode, your factory recovery ends up taking over after the first boot. I might be missing something but the procedures in the OP, especially the custom recovery, are pretty full proof. It's totally up to you. I've been working on both procedures to see what works well.
[Nexus 5X General] shindiggity:
Thanks for the insight I appreciate it, phone doesn't get here until Fri so I guess I'll keep reading both threads.
[Nexus 5X General] jonasdoess:
Hi everybody ! I need your help :)

I'm trying to unlock the bootloader and fastboot doesn't work, I followed exactly the Heisenberg Guide and adb works well but not fastboot, I don't understand why... Drivers are installed but it still doesn't work when I try to check the fastboot via the bootloader with "fastboot devices" command. Do you have any idea to fix it ?
[Nexus 5X General] joetheshmo:
Please try to use search [MENTION=4635598]jonasdoess[/MENTION] ;)
[Nexus 5X General] rydare:
"fastboot devices" will only detect your device if you reboot into the bootloader mode on your phone and then have it connected. It is the screen where you can select to boot to recovery or a normal boot, accessed by holding volume down when you power on the device. It's a little ambiguous in your post whether you're actually in bootloader mode on the phone itself, maybe you are and this is a different issue, but it is the only reason I can think of why adb would recognize it and not fastboot.
[Nexus 5X General] Gig103:
Does installing TWRP wipe the phone a second time? The guide is written for someone following the instructions from start to finish, but the first thing I did after receiving the phone in October was Step 1 - unlock the bootloader. I never got around to rooting but I'm tired of those sh**ty ads that hijack the browser or open the Play Store.

I'm interesting in installing TWRP and doing a systemless root per #2 and #6.
[Nexus 5X General] SlimSnoopOS:
Installing TWRP does not wipe the phone at all. It only alters the recovery partition.