Develop Bugs

March 2016 Updates Bug

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.

[Help] OP3 blocked, no windows PC, is this recoverable?

Hello,
I have been trying to go trhough google searches and this forum for a while now
Situation,
Had a working OP3 completely stock until this afternoon (not sure which ROM but latest OTA from stock)
- I currently dont have access to a windows PC and I am using ubuntu on a chromebook (chrubuntu)
Steps
I unloacked bootloader - successfully
I installed TWRP - successfully
Installed latest CM14.1 - successfully
After first boot Phone stopped rebooting. I tried to wipe everything and after this, I dont have a partition in my file explorer (on Ubuntu) therefore can't copy files to install
I tried to adb sideload. I get "error: Protocol (no status)"
Only thing that seems to work is fastboot
I have tried to install CM-14.1 recovery or original recovery but only CM14.1 works
It seems complete phone (system/boot/img) are wiped and therefore can't start.
Do you have any ideas? would like to unbrick the phone
Thank you

BeerFreek said:
Hello,
I have been trying to go trhough google searches and this forum for a while now
Situation,
Had a working OP3 completely stock until this afternoon (not sure which ROM but latest OTA from stock)
- I currently dont have access to a windows PC and I am using ubuntu on a chromebook (chrubuntu)
Steps
I unloacked bootloader - successfully
I installed TWRP - successfully
Installed latest CM14.1 - successfully
After first boot Phone stopped rebooting. I tried to wipe everything and after this, I dont have a partition in my file explorer (on Ubuntu) therefore can't copy files to install
I tried to adb sideload. I get "error: Protocol (no status)"
Only thing that seems to work is fastboot
I have tried to install CM-14.1 recovery or original recovery but only CM14.1 works
It seems complete phone (system/boot/img) are wiped and therefore can't start.
Do you have any ideas? would like to unbrick the phone
Thank you
Click to expand...
Click to collapse
Flash this recovery in fastboot
https://www.androidfilehost.com/?w=...cb8f6e7e3ae3b22eeb701f45ff43773a7ebdfe1009fa9
Enter recovery and flash
https://www.androidfilehost.com/?fid=529152257862675332
Then flash cm14.1 + gapps
Dont forget to wipe system data cache before

nadejo said:
Flash this recovery in fastboot
https://www.androidfilehost.com/?w=...cb8f6e7e3ae3b22eeb701f45ff43773a7ebdfe1009fa9
Enter recovery and flash
https://www.androidfilehost.com/?fid=529152257862675332
Then flash cm14.1 + gapps
Dont forget to wipe system data cache before
Click to expand...
Click to collapse
Thank you, just recoevered the phone with the modded TWRP from this post http://forum.xda-developers.com/one...mate-guide-t3497940/post69566175#post69566175
Question is, what are the mods on the recovery? can modded recoveries give 3rd parties access to your system?
Thanks for the quick reply, I would just like to understand what is going on so it doesn't happen again. When will it be ok to flash official TWRP?

BeerFreek said:
Thank you, just recoevered the phone with the modded TWRP from this post http://forum.xda-developers.com/one...mate-guide-t3497940/post69566175#post69566175
Question is, what are the mods on the recovery? can modded recoveries give 3rd parties access to your system?
Thanks for the quick reply, I would just like to understand what is going on so it doesn't happen again. When will it be ok to flash official TWRP?
Click to expand...
Click to collapse
No, dont be afraid of that. The recovery is simply modded to allow booting 3.5.5 based operating systems.
The recovery partition cannot share any information to any third parties because its limited to a partition that is only active when you boot to recovery and the operating system is not running. And the operating system is running independent from the recovery you are using. There is no activity between your recovery and your system/data/cache or watever partition. Because they are complete different boot states. Only action is durring the installation or wiping processes in recovery. Or if you are flashing mods/roms/kernels or changing&updating your recovery with root apps like flashify. But again it only gives a command for a flash process or wipe process to the recovery. A recovery is not able to run any kind of service app so it is not able to share any kind of information to anyone.

nadejo said:
No, dont be afraid of that. The recovery is simply modded to allow booting 3.5.5 based operating systems.
The recovery partition cannot share any information to any third parties because its limited to a partition that is only active when you boot to recovery and the operating system is not running. And the operating system is running independent from the recovery you are using. There is no activity between your recovery and your system/data/cache or watever partition. Because they are complete different boot states. Only action is durring the installation or wiping processes in recovery. Or if you are flashing mods/roms/kernels or changing&updating your recovery with root apps like flashify. But again it only gives a command for a flash process or wipe process to the recovery. A recovery is not able to run any kind of service app so it is not able to share any kind of information to anyone.
Click to expand...
Click to collapse
Thanks that is quite explanatory... Running smoothly so far. It's good to learn something every day...
Big thumbs up

How to flash official nougat without wiping internal storage?

Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks

I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!

Edit : Nougat running on my op3.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?

To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!

anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.

@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.

I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0

Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.

anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.

I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...

Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.

Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.

dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.

anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.

abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....

Thanks! Will try and let you know

abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.

How to Root Using SuperSU and TWRP on Oreo OPR6 Official Release

After a bit of trial and error, I managed to find a combination of files and actions that allowed me to successfully root my 64GB Pixel C on 8.0.0 by installing SuperSU via TWRP.
Steps:
Perform a clean installation of the official release, found here
Use the unofficial 3.0.0 TWRP release found in this thread (direct download link here) and boot to recovery ("fastboot boot [TWRP filename].img") - the latest official 3.1.1 TWRP did not work, either via flashing or booting
ADB sideload SuperSU 2.82SR3 found in this thread (direct download link here)
Hope this helps!

Stuck at TWRP after
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?

Jeff Z. said:
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk

MadManMoon said:
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. My problem was my pixel kept booting to TWRP even selecting to boot the system, kind of strange. I think I missed your first step, the pad was OTA updated to 8.0 from 8.0 Beta release. I will try again with flash the factory image of 8.0 first.

Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.

NitroSS said:
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
Click to expand...
Click to collapse
Still works for me as of the September 2017 update. About to try it again with the October update.

It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.

CatThief said:
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
Click to expand...
Click to collapse
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.

Huffy1 said:
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Click to expand...
Click to collapse
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.

CatThief said:
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
Click to expand...
Click to collapse
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up

Huffy1 said:
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Click to expand...
Click to collapse
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?

CatThief said:
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
Click to expand...
Click to collapse
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.

Huffy1 said:
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Click to expand...
Click to collapse
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.

CatThief said:
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
Click to expand...
Click to collapse
Use FDE then and it reportedly works.

Huffy1 said:
Use FDE then and it reportedly works.
Click to expand...
Click to collapse
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?

CatThief said:
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
Click to expand...
Click to collapse
Don't know, only telling you what I did cause I had the same problem as you

Well I'm finally rooted. I didn't change the encryption, just tried a different method and after several tries it finally worked. I used adb sideload inside TWRP after canceling the password screen. Odd that it took several tries, though, to get through it without generating errors. We'll see how it goes next month.

I have had a lot of trouble with rooting Oreo...
I started out trying to use Magisk but gave up after many attempts. Every version, and every kernel I tried resulted in booting to recovery and not system. I could have tried the ADB method but I actually want to have TWRP so I didn't try that.
By the time I tried SuperSU my factory image had had an OTA and many apps & files installed so I can't say my system is "clean" but I have Fastboot flashed the stock boot image many (many) times to recover from whatever Magisk does to the kernel. I never looked all that hard for this unofficial TWRP people talk about so I used 3.1.1-1. At some point I converted to File Based Encryption because it is so much nicer to use, and so TWRP cannot decrypt my internal storage, but the workaround is to put zips and images on a USB drive. It also does not ask for a password. So far so good, I have my workarounds. I do also have this weird error where TWRP cannot unmount the system but I can flash kernels without problems. I have chosen to keep system read-only for superstitious reasons. I think it will fail if I look at it funny sometimes lol.
From this state I flashed the latest SuperSU and it booted! So I do have root. I still would like to try Magisk for the modules but it seems this isn't ready. However, my trusty old terminal app hangs at the su command... and several kernels will crash my tablet... so it's "working" but there is more to do. And literally just now I see I have an OTA. lol.

I followed the original instructions and got rooted with the latest version of Oreo. But, TWRP still wouldn't flash correctly without causing boot loops.
I finally got it resolved by using the original instructions, then loading the Official TWRP app from Google Play. I used the app to flash twrp-3.1.1-1-dragon.img.
Everything is working properly now. I have 8.0.0 (OPR1.170623.032, Nov 2017) loaded and rooted, and the Pixel C will boot into TWRP and see the encrypted data.

Is it posible to flash latest Oreo stock factory image https://developers.google.com/android/images ryu-opr1.170623.032-factory-020f1cf9.zip using stock TWRP or do I have to side load it ?
I'm getting a Invalid zip file format error in TWRP when I try and flash it

ROM][10] LineageOS 17.1 for honor 6x

I just find out that this rom https://forum.xda-developers.com/p8...m-lineageos-17-1-huawei-p8-lite-2017-t4064121 could be installed on our device wtih minor changes.After installing all things you will need to install stock recovery and wipe cache and try to do factory reset(i tried to but i got error massage) then you will successfully boot into rom
Contributors
 @DarkJoker360

I can confirm that this works like a charm, here I posted the instructions for those who want to install it!

Hi when I try to wipe data and cache... I have an error because the data is not mounted, I've trying to change the system file to ext2 and ext4 but nothing change. I also tried to repair system file. What can I do ? My device is already emui 8 and it's an Huawei gr5 2017 bll-l22. Thanks for your help ?

Momo745040 said:
Hi when I try to wipe data and cache... I have an error because the data is not mounted, I've trying to change the system file to ext2 and ext4 but nothing change. I also tried to repair system file. What can I do ? My device is already emui 8 and it's an Huawei gr5 2017 bll-l22. Thanks for your help
Click to expand...
Click to collapse
Try the lastest TWRP in this thread
https://forum.xda-developers.com/p8...wrp-3-3-1-0-huawei-p8-lite-2017-t3953122/amp/
After installing system.img, u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb,
after that flash gapps
and MUST flash Magisk Phh 19.3
the flash the patch file.
After first boot, you need to, format data in erecovery
Everything works smoothly except......can not make and receive calls, ooopss
update, i try to roll back to emui8, and start the process again. it works now.
recommend to update, lets teach the old dog new trick

A big job ahead ?. I will try and I will tell you if it works thank you for your answer. One last question is there a way to keep a custom recovery because sometimes magisk's module causes a botloop (sorry for my bad English ?)

lucsi said:
Try the lastest TWRP in this thread
https://forum.xda-developers.com/p8...wrp-3-3-1-0-huawei-p8-lite-2017-t3953122/amp/
After installing system.img, u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb,
after that flash gapps
and MUST flash Magisk Phh 19.3
the flash the patch file.
After first boot, you need to, format data in erecovery
Everything works smoothly except......can not make and receive calls, ooopss
update, i try to roll back to emui8, and start the process again. it works now.
recommend to update, lets teach the old dog new trick
Click to expand...
Click to collapse
So I came back (finally) to emui 8 and I tried to install the recovery custom but I still cannot access the internal storage memory.
I think it comes from my model because I have a Huawei GR5 2017 which is supposed to be a 'copy' of the honor 6x but all the roms which require emui 5.x installed do not work.
In any case thank you very much for your help! [emoji106]
Envoyé de mon BLL-L22 en utilisant Tapatalk

Momo745040 said:
So I came back (finally) to emui 8 and I tried to install the recovery custom but I still cannot access the internal storage memory.
I think it comes from my model because I have a Huawei GR5 2017 which is supposed to be a 'copy' of the honor 6x but all the roms which require emui 5.x installed do not work.
In any case thank you very much for your help! [emoji106]
Envoyé de mon BLL-L22 en utilisant Tapatalk
Click to expand...
Click to collapse
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug

lucsi said:
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
Click to expand...
Click to collapse
Thanks you very much for your help!
I'll try this weekend (I don't have time in week).
I will come back to say if it worked

Has anyone tried these github projects to unlock the bootloader of his Honor (6X) or Huawei Device?
Maybe it is possible to accelerate these programs by using cuda cores on nvidia graphic card(s).
https://github.com/SkyEmie/huawei-ho...ock-bootloader
https://github.com/Martazza/Huawei-Bootloader-Unlocker

lucsi said:
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
Click to expand...
Click to collapse
I managed to find a compatible recovery but when I flashed everything and I did a factory reset from the erecovery the phone restarts and it displays the logo lineageOs for 5 seconds then it restarts and the screen remains black then it restarts and displays the logo then it restarts in erecovery telling me that the memory has been seriously damaged.
I think I will give up here([emoji28])but anyway thank you for your help [emoji106].
Envoyé de mon BLL-L22 en utilisant Tapatalk

at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
finally i managed to get it work, so now i'm going to post every single thing i did to make this rom works and i will try to be as noob friendly as possible
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy

Raxul said:
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
Click to expand...
Click to collapse
Have you followed all these instructions?
matyrock said:
How can there be such awesome people? It works in my Honor 6X! And it's fully de-googled man this is just perfect! Thank you very much for this...
These are the steps (thanks @DunoCZ) I followed if an Honor 6X user want to install this ROM:
- *Upgrade to EMUI 8!*
- *Remove the saved fingerprints and Google Accounts just in case*
- Flash the TWRP recovery from @Dil3mm4
- Format cache, dalvik cache, data and system: TWRP -> Wipe -> Advanced Wipe
- Flash the ROM via TWRP (you can try with fastboot but it already works with TWRP): TWRP -> Install -> Install Image
- Resize the system partition: TWRP -> Wipe -> Advanced Wipe -> System -> Resize (DO NOT FORMAT!)
- (Optional) Install GApps, Magisk
- (Required) Install patch
- Reboot and wait
Click to expand...
Click to collapse

D0ping said:
Have you followed all these instructions?
Click to expand...
Click to collapse
i did and the diffferent thing i did is to flash back stock recovery as mentioned by op, wipe the cache and then flash huaweitwrp.im provided by lusci
i edited my post above

Yea, i cant get it to work. No matter what i do after
- flashing system.img
- resizing the system partition
- installing opengapps
- installing magisk
- installing the patch
followed by either:
-straight up booting it.
- doing everything i can in every bootloader.
evenm if i freshly format /data the system get stuck in a boot. Have tried all of the recoveries in this thread. All are basically the same, from what i have observed.
Edit: Figured it out. apparently my gapps was somehow broken. Downloaded a fresh arm64-ogapps and all is working now

Darkitz said:
Yea, i cant get it to work. No matter what i do after
- flashing system.img
- resizing the system partition
- installing opengapps
- installing magisk
- installing the patch
followed by either:
-straight up booting it.
- doing everything i can in every bootloader.
evenm if i freshly format /data the system get stuck in a boot. Have tried all of the recoveries in this thread. All are basically the same, from what i have observed.
Click to expand...
Click to collapse
follow my guide here, this is how i managed to get it work, make sure you flash the rom with your CLEAN STOCK rom
Raxul said:
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Click to expand...
Click to collapse

Raxul said:
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
finally i managed to get it work, so now i'm going to post every single thing i did to make this rom works and i will try to be as noob friendly as possible
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Click to expand...
Click to collapse
Ok let me make it simple for you.
1. Flash stock Oreo Rom (no need to boot it)
2. Flash TWRP by Dilemma in fastboot.
3. Go to recovery and wipe data by typing yes to decrypt data partition (if not already decrypted)
4. Go to fastboot and flash system.img
5. Reboot to recovery and resize system partition
6. Flash GApps
7. Flash los patches zip
8. Flash disable Dm verity patch
9. Flash magisk-phh zip in the end.
10. Reboot and wait.
I used these steps to flash different GSIs/ROMs and it works perfectly.

I managed to flash the rom but without flashing the gapps because I don't know exactly which one to flash should I flash gapps for android 10 arm64 or gapps for android 8.0 ??
try both and it gives me error 20

victorgrey999 said:
I managed to flash the rom but without flashing the gapps because I don't know exactly which one to flash should I flash gapps for android 10 arm64 or gapps for android 8.0 ??
try both and it gives me error 20
Click to expand...
Click to collapse
You need to resize the partition
flash android10 arm 64

lucsi said:
You need to resize the partition
flash android10 arm 64
Click to expand...
Click to collapse
I managed to flash the rom successfully, but I don't know if this only happens to me, I feel it is slow and the cell phone is heating up more than normal. ?

victorgrey999 said:
I managed to flash the rom successfully, but I don't know if this only happens to me, I feel it is slow and the cell phone is heating up more than normal. ?
Click to expand...
Click to collapse
Mine is ok. battery backup is ok.
Antutu ~96K point
You can install kernel management app to tweak the CPU freq