Related
My recent apps button is no longer working. And when I go to Developer Options, I see Developer Options are not available for this user. Anyone else seeing that?
I installed MHC19J first and that was the incorrect version. I then flashed MMB29V and then the problems above started. I couldn't access quick menu, the recent apps button didn't work, and Developer Options showed as not available for this user. I just did a factory data reset and that seemed to get everything working again, but always a pain to have set everything up again! Damn Google! :-/
Probably due to you flashing the wrong image before flashing the correct one. Had no such problems after flashing this morning
Skickat från min Nexus 5X via Tapatalk
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
granets said:
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
Click to expand...
Click to collapse
Only do that if you are not rooted etc. If you use TWRP recovery and are not prompted for a password when booting into recovery, then you have the right image. It does work, the problem is trying to use Custom Recovery to flash SuperSU. Check that thread below.
https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
no issues here on 19J. modified boot image here
bobby janow said:
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
Click to expand...
Click to collapse
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
I'm sorry I don't know. I haven't decrypted in quite some time now. I also haven't used xposed in a long time either. I don't ever format userdata or flash the userdata.img unless I absolutely have to. I'm encrypted, systemless, 2.68 SU and twrp 3.0. I'm leery to do anything now until twrp gets fixed for the J build. Although I might flash a J kernel via OTG if there comes one.
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
mickey4mice said:
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
Click to expand...
Click to collapse
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
i had some trouble so i clicked the flash all batch file. Anyone know how to root this build? i cant get super su zip file i transfer to show up in twrp. The file is there but twrp doesnt see it.
SlimSnoopOS said:
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Bump
Dominicano2 said:
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Click to expand...
Click to collapse
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Dominicano2 said:
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Click to expand...
Click to collapse
Sweet, glad you got that figured out
How is the new update in terms of making the phone better?
gvsukids said:
How is the new update in terms of making the phone better?
Click to expand...
Click to collapse
Seems like the lag pulling down the notification window that happened time to time is gone. Feels a little snappier but will need a week of up time to know for sure.
Notice that the "keep WiFi on during sleep" setting for "never" still doesn't work on the 5x. Also still have an audio bug that duplicates the source a second behind on Bluetooth when a notification is received which is disappointing.
Hey there,
I have been really annoyed since i installed OOS 4.0.0. First because it took ages the first time to get it right, and then because i had to start from scratch with every little 30MB update AGAIN.
I didn't find any reliable source to what happens in the folowing cases, thus this thread :
1- Flashing official recovery + updating through android
=> Will it work/DM-Verity error appear ?
2- Flash official recovery and sideload OTA/Full ZIP
=> Is /data getting wiped ? Same question about DM-Verity
3-Flash full Zip in latest eng.stk TWRP followed with supersu
Has anyone explored these solutions ?
Thanks in advance
EDIT: Working way for updating:
1: Dirty flash full ROM in latest modified TWRP
2: Flash SuperSU WITHOUT booting into system
3: Wipe dalvik/cache
4: reboot to system.
For explanation about what triggers DM-Verity check out post 19
DM verity is triggered by the firmware. You can't avoid it unless you want to run old firmware
It is not an error nor a bug - it is a notification. There is no impact to performance
2x4 said:
DM verity is triggered by the firmware. You can't avoid it unless you want to run old firmware
It is not an error nor a bug - it is a notification. There is no impact to performance
Click to expand...
Click to collapse
I do know that. I simply try to find the best way to update without hassle and without getting the DM-Verity message.
Nobody07 said:
I do know that. I simply try to find the best way to update without hassle and without getting the DM-Verity message.
Click to expand...
Click to collapse
update everything (ROM/TWRP), flash old (non-4.x) firmware
FYI you're fixing an aesthetic issues and there may be more bugs from using the old firmware.
2x4 said:
update everything (ROM/TWRP), flash old (non-4.x) firmware
FYI you're fixing an aesthetic issues and there may be more bugs from using the old firmware.
Click to expand...
Click to collapse
I don't have the issue right now with a 4.x firmware ... You are not helping... My guess is using OnePlus recovery and updating through android there wont be a DM Verity message. Do you know if this is true ? If not you aren't telling me anything i do not know.
Nobody07 said:
I don't have the issue right now with a 4.x firmware ... You are not helping... My guess is using OnePlus recovery and updating through android there wont be a DM Verity message. Do you know if this is true ? If not you aren't telling me anything i do not know.
Click to expand...
Click to collapse
if you use stock recovery you won't get the dm-verity notice either.
not sure why you mentioned eng.stk TWRP if you're not trying to run TWRP.
2x4 said:
if you use stock recovery you won't get the dm-verity notice either.
not sure why you mentioned eng.stk TWRP if you're not trying to run TWRP.
Click to expand...
Click to collapse
Thank you for answering, but seriously, did you even read the first post ?
So i can flash OnePlus firmware, update android within the system and then flash twrp again. With no DM Verity appearing ?
Nobody07 said:
Thank you for answering, but seriously, did you even read the first post ?
So i can flash OnePlus firmware, update android within the system and then flash twrp again. With no DM Verity appearing ?
Click to expand...
Click to collapse
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
2x4 said:
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
Click to expand...
Click to collapse
That's were you are wrong...
I currently have twrp and no dm-verity.
Nobody07 said:
That's were you are wrong...
I currently have twrp and no dm-verity.
Click to expand...
Click to collapse
because you are on pre-nougat ROM and/or firmware
2x4 said:
because you are on pre-nougat ROM and/or firmware
Click to expand...
Click to collapse
Im getting tired of you ignoring what i say.
I'm on OOS 4.0.1. I did a clean sideload through OnePlus recovery, and flashed twrp/root afterwards. No DM-Verity. I DID NOT flash an old firmware.
it's a compilation of things not just one thing, the firmware thing is just the easy way out, if you decrypt the phone data (just wipe it) and rooted then re encrypted it, you wont get the dm verity issue...
so simply, sideload or flash the full rom , if you sideloaded immediately fastboot TWRP (the latest official or modified) , then immediately flash SuperSU... reboot to system, no dm verity will appear.
---------- Post added at 09:46 PM ---------- Previous post was at 09:45 PM ----------
2x4 said:
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
Click to expand...
Click to collapse
not true, i have the latest 4.0.2 firmware and TWRP and no DM verity .
theduke7 said:
it's a compilation of things not just one thing, the firmware thing is just the easy way out, if you decrypt the phone data (just wipe it) and rooted then re encrypted it, you wont get the dm verity issue...
so simply, sideload or flash the full rom , if you sideloaded immediately fastboot TWRP (the latest official or modified) , then immediately flash SuperSU... reboot to system, no dm verity will appear.
Click to expand...
Click to collapse
What you are saying is i can flash full ROM through twrp, followed by supersu, reboot, and i wont get dm-verity nor loose any data?
Nobody07 said:
What you are saying is i can flash full ROM through twrp, followed by supersu, reboot, and i wont get dm-verity nor loose any data?
Click to expand...
Click to collapse
yes , idid exactly that updating from 4.0.1 to 4.0.2, dirty flashed the full rom , then immediately SuperSU, and then TWRP again just to be sure...and Viola
2x4 said:
because you are on pre-nougat ROM and/or firmware
Click to expand...
Click to collapse
Did a clean flash (beta 10) with the stock recovery, flashed TWRP with SuperSU afterwards.
No dm-verity.
After dirty flashing beta11 full zip + SuperSU through TWRP the dm-verity screen is still NOT there.
Btw, this has been already discussed weeks ago.
Do your homework.
dm verity is a fail safe present in system boot.img . Nothing related to firmware. Don't know from where people getting all this hoax
cpt.macp said:
dm verity is a fail safe present in system boot.img . Nothing related to firmware. Don't know from where people getting all this hoax
Click to expand...
Click to collapse
BC whether it's a band-aid or fixes the issue, if u flash an old fw outside of nougat with trwp, it gits rid of the nag
Bradl79 said:
BC whether it's a band-aid or fixes the issue, if u flash an old fw outside of nougat with trwp, it gits rid of the nag
Click to expand...
Click to collapse
it's the worst way to "fix" the issue, you're using an old firmware that's more than likely have incompatibility issues with the OOS updated rom, so unless you're using a custom rom (not OOS or OOS based) where it doesn't matter what firmware you use it's not a recommended practice.
Neither flashing twrp, nor OOS would trigger dm-verity (unless you already have that message)
If you however boot into system, dm-verity will be triggered. The idea is to patch that before it gets triggered.
Flashing SuperSU patches DM verity. Which is great if you want root access. Again this patch won't work if you already have dm-verity warning. Once you flash the ROM, do not boot into system. Flash SuperSU 2.79 or above and verity will be patched. You will also see a line "patching dm-verity" in SuperSU installation process. Now verity message won't appear.
If you don't want root, there is a no-verity zip that you can flash which will have the same effect. I use SuperSU so I don't have any links to this but Google is your best friend.
- if you already have verity
- if you forgot patching verity, booted into system and now warning screen has appeared.
Now here is where things get tricky. Boot to fastboot, connect phone and type
fastboot format userdata
Remember the above step will wipe internal storage completely
Reboot to recovery
Format data (not wipe but format. This step is very important)
Flash OOS
Flash SuperSU
Reboot to system. Now there will be no dm-verity warning
@ungeeked great detailed explanation that should put an end to all chatter TBH your reply should be pinned in this section for some while and titled DM-Verity explained.
I just noticed my p2 has been encrypted and I think it happened after nougat update. Can others confirm? Is it nougat feature or something??
In MM is the same.
I think the stock roms have forced encryption enabled by default. It will reencrypt the phone if it was decrypted.
my p2 was encrypted since beginning with MM and same for Nougat
I cant access to twrp anymore . How to remove encryption?
kataeb said:
I cant access to twrp anymore . How to remove encryption?
Click to expand...
Click to collapse
Use latest unofficial twrp-3.1.0-0 i already fix that bugs, see in my treats
I updated with unofficial twrp but still asking for a code, it is encrypted
kataeb said:
I updated with unofficial twrp but still asking for a code, it is encrypted
Click to expand...
Click to collapse
You must remember last your pin code otherwise twrp can't decrypted
Hi, my p2 didn't ask me any code but is still encrypted.
How can I decrypted it ?
When I am in settings security, there is encryption shown, but no any option to decrypt it.
How can I fix it ? My bootloader is unlocked, but when I flash rom, I have a message after the bootanimation to reset for decrypt my phone, but it doesn't work.
Any idea or Decrypted & Insecure boot.img with adb fix ?
gui3gui said:
Hi, my p2 didn't ask me any code but is still encrypted.
How can I decrypted it ?
When I am in settings security, there is encryption shown, but no any option to decrypt it.
How can I fix it ? My bootloader is unlocked, but when I flash rom, I have a message after the bootanimation to reset for decrypt my phone, but it doesn't work.
Any idea or Decrypted & Insecure boot.img with adb fix ?
Click to expand...
Click to collapse
Happened to me too while using a custom rom and then switching to another rom :silly: There is a way to do it.. Got to TWRP change System and Cache to Ext 4 using the repair/ change file partition, doing it to data wont work because its encrypted.. But doing so with cache and system should erase and reset it.. Oh and format data after that. Then you can flash a rom.. There is also an adb command too ---- fastboot format userdata ... And then ---- fastboot reboot
Ok I will try this. Thanks for your help.
Envoyé de mon HUAWEI NXT-AL10 en utilisant Tapatalk
It's working perfectly. Thanks a lot !
How do I tell if I'm Encrypted? Where can u get the no-verity zip and when do I need to use it?
On OB4 stock rooted wanting to pull the trigger on a custom rom but haven't gone through the process yet on this phone.
Thanks!
The no verity zip is only needed to run encrypted roms when ur decrypted.
the_rooter said:
The no verity zip is only needed to run encrypted roms when ur decrypted.
Click to expand...
Click to collapse
This, plus you can tell if you're encrypted by checking settings>security & lock screen, right at the end of the menu.
I rooted my device,
Unlocked bootloader,
Installed TWRP with using some encryption disabling package, and rooted it using magisk installer.
Now my question is, can I encrypt the device again in the settings menu or will this brick or bootloop my phone?
Cremig said:
I rooted my device,
Unlocked bootloader,
Installed TWRP with using some encryption disabling package, and rooted it using magisk installer.
Now my question is, can I encrypt the device again in the settings menu or will this brick or bootloop my phone?
Click to expand...
Click to collapse
Unless you also formatted data it's probably still encrypted... Encryption != using a password/pin/etc
The encryption disabler prevents forced enabling of encryption on first boot/factory reset.
I don't know if enabling encryption is a lossless process. If it is, you should be able to do it.
I would STRONGLY recommend backing up your data first!