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.
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
nikhilsnigam said:
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
Click to expand...
Click to collapse
What twrp version are you using?
Piyush lalwani said:
What twrp version are you using?
Click to expand...
Click to collapse
latest official twrp
nikhilsnigam said:
latest official twrp
Click to expand...
Click to collapse
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
I did that already. after flashing supersu immediately then also stuck at boot screen. tried with modded twrp too 3.0.2.22
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
okay now after few trial and error method i have come to the conclusion that this happens only after unencrypting the device. after eunencrypting it wont boot any other roms except those which have been already backed up.
So,
can i flash roms on encrypted device? I mean i test a lot of roms and i change frequently.
I guess no, right?
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Piyush lalwani said:
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Click to expand...
Click to collapse
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
nikhilsnigam said:
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
Click to expand...
Click to collapse
In nodded recovery too?
Piyush lalwani said:
In nodded recovery too?
Click to expand...
Click to collapse
going to try with modded recovery this time
nikhilsnigam said:
going to try with modded recovery this time
Click to expand...
Click to collapse
Yeah give a try
Piyush lalwani said:
Yeah give a try
Click to expand...
Click to collapse
how does modded recovery helps in this btw?
hope it works
OK So I am able to flash any rom with encrypted storage and latest modified twrp.
This is working for me right now but still haven't found solution why it wouldn't work on unencrypted storage.
Thank you.
This guide solved everything
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
eid_elageeb said:
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
Click to expand...
Click to collapse
You need modified TWRP 3.0.2-28 to get TWRP working with Beta 8. I had the same issue witrh my installation.
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
strumaticjoker2 said:
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
Click to expand...
Click to collapse
even without protection, twrp asking pw, need to erase use data and system.
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
eid_elageeb said:
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
Click to expand...
Click to collapse
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
yiphoming said:
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
Click to expand...
Click to collapse
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
eid_elageeb said:
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
Click to expand...
Click to collapse
No luck, can erase the storage, but it is still in encrypted.
yiphoming said:
No luck, can erase the storage, but it is still in encrypted.
Click to expand...
Click to collapse
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
rarog said:
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
Click to expand...
Click to collapse
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
AcmE85 said:
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
Click to expand...
Click to collapse
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
rarog said:
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
Click to expand...
Click to collapse
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
Do you also get the dm-verity bootscreen?
AcmE85 said:
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
Click to expand...
Click to collapse
Hm... Interesting, do you have a link? And perhaps a link to a thread with all the available versions? I searched, but found only several tutorial threads with just one or another version linked, no thread for specific modified version.
AcmE85 said:
Do you also get the dm-verity bootscreen?
Click to expand...
Click to collapse
As far as I know - no.
When would this error message pop up?
LS.xD said:
As far as I know - no.
When would this error message pop up?
Click to expand...
Click to collapse
Right at boot before or after the screen which shows that the bootloader is unlocked.
AcmE85 said:
Right at boot before or after the screen which shows that the bootloader is unlocked.
Click to expand...
Click to collapse
No such error message for me
LS.xD said:
No such error message for me
Click to expand...
Click to collapse
Did you flash SuperSU?
AcmE85 said:
Did you flash SuperSU?
Click to expand...
Click to collapse
Yes, 2.78 SR5
I have done format userdata in fastboot but my phone still shows up as encrypted. Flashed 3.0.2-1.28 and I still get a password screen when booting to recovery. Not really sure what else I can do.
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to install:
1. Unzip
2. Install fastboot tools from google's sdk on your PC
3. Enter fastboot mode on device
4. Unlock your bootloader
5. Run "fastboot flash recovery jason_twrp_recovery.img" via command line
6. Reboot
Download:
https://www.androidfilehost.com/?fid=890129502657588556
Device Tree:
https://github.com/travismills82/android_device_xiaomi_jason
ROOT OPTIONS:
SuperSU: https://forum.xda-developers.com/app...v2-05-t2868133
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Nice one buddy, works with every ROM out there
i tried it out with those ROMs:
Miui CN Dev latest
Miui Stable latest
Miui Global latest
EpicROM
MultiROM
Miui EU ROM Dev/Stable
MiuiPro/Miuisu/Miuigr
FlymeOS
LOS
Mokee latest
is this latest twrp?
Vihru said:
is this latest twrp?
Click to expand...
Click to collapse
Its Twrp 3.2.1.0
Vihru said:
is this latest twrp?
Click to expand...
Click to collapse
Yeah its
thanks, please fix Decrypt Data
not working. after flash, the twrp doesn't show anything (and it doesn't keep settings)
pepote666 said:
thanks, please fix Decrypt Data
Click to expand...
Click to collapse
Wipe then Format Data, is the first thing to do after flashing twrp, make sure to backup first
FenerKR said:
not working. after flash, the twrp doesn't show anything (and it doesn't keep settings)
Click to expand...
Click to collapse
Wipe then Format Data, is the first thing to do after flashing twrp, make sure to backup first
AL_IRAQI said:
Wipe then Format Data, is the first thing to do after flashing twrp, make sure to backup first
Wipe then Format Data, is the first thing to do after flashing twrp, make sure to backup first
Click to expand...
Click to collapse
Why this issue not happen with other twrp? The internal storage show 0 bytes
nowforever said:
Why this issue not happen with other twrp? The internal storage show 0 bytes
Click to expand...
Click to collapse
because you have to wipe your storage first
AL_IRAQI said:
because you have to wipe your storage first
Click to expand...
Click to collapse
So, It's means I will lost all my data on phone? including external storage?
nowforever said:
So, It's means I will lost all my data on phone? including external storage?
Click to expand...
Click to collapse
Hmm, yeah for the first time only, or you could boot up to system and backup everything
Can´t start session. RPC ERROR
Thank you!!!
Molgorth said:
Can´t start session. RPC ERROR
Thank you!!!
Click to expand...
Click to collapse
Im sorry i didnt get you, where did you get that error ?
i already have twrp on my phone, some turkish version with awful orange theme, is there a way for me to flash this one without reseting my system and data?
connta said:
i already have twrp on my phone, some turkish version with awful orange theme, is there a way for me to flash this one without reseting my system and data?
Click to expand...
Click to collapse
Yeah, just flash it over the old one, no need to touch system or data
First time I started twrp they would that I enter a password for data partition.
Which password is there required?
digitaliban said:
First time I started twrp they would that I enter a password for data partition.
Which password is there required?
Click to expand...
Click to collapse
Enter your system password, if it didnt work you have to format, but backup data first
Thanks for this TWRP, work perfect!
I need also to enter password and I don't have encrypted phone. Plus I had already installed twrp installed, so this image has something... not working.
PHP:
I can boot into twrp... However, when I try and flash the installer it says failed to mount system and another partition. Tried several variants, every way I can think of. Anyone else having this prob?
Zooandbio4me said:
PHP:
I can boot into twrp... However, when I try and flash the installer it says failed to mount system and another partition. Tried several variants, every way I can think of. Anyone else having this prob?
Click to expand...
Click to collapse
Have you tried flashing the twrp 3.3.0-0.img file to the recovery ramdisk partition instead of using the zip file?
Zooandbio4me said:
PHP:
I can boot into twrp... However, when I try and flash the installer it says failed to mount system and another partition. Tried several variants, every way I can think of. Anyone else having this prob?
Click to expand...
Click to collapse
TWRP gives this error but it still works. The system partition can't be mounted in 10 as of yet. I haven't had a problem flashing anything though. It will give that error after every flash but so far everything works.
PIXEL 2XL TRWP Android 10 PROBLEM
hi, i have the same isue with the stock Android 10 and twrp-3.2.3-1.... i cant mount SYSTEM and VENDOR and i dont know how to remove TRWP... any help please...?
EDIT: this is what i get when i try to start in recovery mode:
them he erase all and reboot
EDIT: i have the TRWP in the slot A then i cant boot the system in the slot B, the photo is when i try to boot in recovery mode on the slot B i think...
estemanito said:
hi, i have the same isue with the stock Android 10 and twrp-3.2.3-1.... i cant mount SYSTEM and VENDOR and i dont know how to remove TRWP... any help please...?
this is what i get when i try to start in recovery mode:
them he erase all and reboot
Click to expand...
Click to collapse
Fastboot the stock boot.img to remove twrp. Then try using twrp version 3.3.0-0. You will still throw mounting errors when you flash zips, but it will still work :good:
it worked thank you !
EDIT: twrp-3.3.0-0 still not working on my PIXEL 2XL TAIPEN
Badger50 said:
Fastboot the stock boot.img to remove twrp. Then try using twrp version 3.3.0-0. You will still throw mounting errors when you flash zips, but it will still work :good:
Click to expand...
Click to collapse
murphyjasonc said:
TWRP gives this error but it still works. The system partition can't be mounted in 10 as of yet. I haven't had a problem flashing anything though. It will give that error after every flash but so far everything works.
Click to expand...
Click to collapse
+11111
Just ignore the warning and pretend it doesn't exist, known issue, no effect on the installs.
andy6685 said:
+11111
Just ignore the warning and pretend it doesn't exist, known issue, no effect on the installs.
Click to expand...
Click to collapse
I know it works for installs, but what about nandroid backups?
andy6685 said:
+11111
Just ignore the warning and pretend it doesn't exist, known issue, no effect on the installs.
Click to expand...
Click to collapse
I'm on the Android 10 version of pixel dust rom and I had to side load the rom, trwp, and magisk because I kept getting those errors. After the rom booted up, I booted back into twrp via the rom and everything was fine. Super weird, but everything worked ?.
jlokos said:
I know it works for installs, but what about nandroid backups?
Click to expand...
Click to collapse
On Android 10 the /system partition is locked at read only so it can't be mounted in TWRP as read write. To do a nandroid backup go to mount and select mount partitions as read only and check /system and /vendor then do the backup