Develop Bugs

Can i simply encrypt my phone again without dataloss?

Hello, after i got my op3 i instant decrypted it with fastboot and installed freedomos because i heard there could be problems with rooting etc.
But now i heard, that you can use Customroms and twrp even with encrypted storage, what i find really nice so thiefes can't access my data easily.
Now the question is, can i simply encrypt my device in settings -> security with a password and can i simply enter the password in twrp then, and is the behavior the same as the forced encryption on stock oxy?
Also i have another problem, i cant use cm13, cm14 and resurrectionremix, because it stucks on the op logo on boot. I read that this because the data is decrypted. Will encryption fix this problem or do i have to do the method2 of the unbrick guide to fix it? Well, i can just use my nandroid restored freedomOS rom at the moment, any other roms results in a bootfreeze, even if i update freedomos.
Best regards and thanks for your help guys :fingers-crossed:

Oreo Roms started to break the Phone Partitions !

Hey Guys , i used to daily drive Pixel Experience rom based on Oreo, but recently every rom i try ( after flashing it and rebooting it ) breaks the partitions of the phone ! I can use the phone with no problems but when i reboot to TWRP ) im using the latest one btw ) it give me error that the partitions cant be found and mounted .
This problem isnt rom especific , only ( not sure if its true ) exception could be older builts of Oreo Roms .
So every time i flash any 8.0/8.1 rom to me to be able to use other ones i must wipe DATA ( wipe phone memory fully ) and the flash any other rom i want , either 6.0 or 7.0 .
Never saw anyone complaining about this issue but if anyone have an explanation of tips i would be very happy and greatfull !!

Never had this problem.
Did you already tried to use
fastboot -w
Than flash miui and boot it and complete the setup. Reboot to recovery,
wipe system,cache, data and flash the custom rom of your choice.

O now flashed the last PE 8.1 rom from march and everything is ok ! So there was some recent change on the ROMs that caused this problem , im waiting for the new PE that is coming with new kernel and base rom to see , this is boring having to deal with this **** because aparently im the ONLY one having this .
Still dont know what is making this happening --" .

I can't get Treble to work with the OnePlus 5T - please help

Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!

Okay there's a few things remember here after flashing the mokee trebleize pack you should have had the addition of the vendor partition included in your TWRP file system if you have the blue spark TWRP version YOU SHOULD BE ABLE TO SEE THE ADDITION OF THE VENDOR PARTITION WHEN YOU GO TO MOUNT FOLLOWING THAT.
*** Make sure that after the trebleize is installed or whatever don't touch vendor partition ever just leave it alone you don't need to do anything to it it's fine if some ROM needs to update it you don't have to worry about wiping it first because it'll take care of that with the configuration script in the zip file. Even if you want to go back to a regular Android 8. 1 ROM you don't have to worry about the vendor partition the way it's set up the vendor partition that exist inside the one plus 5T that was created for Treble is not seen by any AOSP ROMs so it's going to create its own vendor folder inside of the system partition like it normally does and that you will not conflict because the fs tab does not Mount the new vendor. By leaving vendor alone and never touching it you're just ensuring that when you flashed yes eyes you're not missing something that's essential to the boot up process and it's one thing that you can from any potential uncertainty as to why a treble mage may or may not be booting.
Follow this....
Normal Android ROMs you would usually wipe system data cache D-cache if you were going to install a new ROM that wasn't just an upgraded version of the one that you were already running you'd have to start from scratch always. This is still what you should do it whenever you want to start and flash a fresh regular ROM or treble run always do that but it's how you proceed from here that is a little difference between the two.
With a regular ROM you would just go on to flash the ROM that you want to install followed by Gapps and so on.
When you want to flash a treble image you need to be on a clean fresh ROM that has treble support already good to go in that it can see that vendor partition that was made before and that it contains the binderized HALs needed as well. Because official treble support is still in beta with the OnePlus 5T the only officially supported treble Android 8. 1 ROM is mokee so you always want to start with a clean flash of the Mokee ROM because it also contains the supported kernel and ramdisk and other things as well.
Upon flashing a fresh version of mokee you want to go ahead and Flash no-dm-variety to ensure data is not encrypted because it will lead to a bootloop and the only way to get it to work will be to either format your SD card or to install the no variety which is the way to go just install it every time you flash mokee so that way you know everything is good.
**** I've only had experience using Android 8. 1 GSi so I'm not sure exactly how it would work concerning open G apps because I've only had to do it with two 8. 1 apps I'm not touching the Android P treble ROM until it's official so anything that I'm saying here has nothing to do with that if that's the image you're trying to install that I can't help you with it because I don't honestly know I remember reading something about that changing something different with it and I got to read up more on it.****
So next part depends on whether the GSI you're trying to flash comes with GFS included inside of it some do some don't I think most do but just make sure you read the instructions on the forms from where you download them from where they will tell you about the gf's the ones that I've installed that didn't have gf's on I would install mokee then I would flashed gf's to mokee but I've seen ones where people have flashed the gf's after flashing the treble images well and they didn't have any problem so just make sure you read into that one. obviously if the GS I can change the gf's then don't flash any before flashing or after as it will be flashed when we install it to the image and everything will be.
Which brings us to the last part if you did everything right up to this point then you should have no trouble installing the GSI through either TWRP or fastboot but before you do just make sure you go back to White and you just swipe to factory reset again so that we know that we cleaned out the data and we're on something clean after on encrypting the data if you did Flash no variety but remember don't wipe any partitions you want to make sure that you leave mokee on there. if you do it correctly you won't even need to wipe anything afterwards you should literally just need to be able to install the image into the system partition now and then reboot and it should work fine
It's your choice on how to go about doing it I've had success with TWRP but I've had more success using the fastboot method if for some reason you do try TWRP and it flashes and says success in 10 seconds then just reboot to fastboot mode in just flash it from there because you probably going to run into an issue just factory reset it again before you do it by swiping you don't have to wipe any of the partitions leave those alone.
So either go to the fastboot route which is put the phone in fastboot Point your terminal to the area where your GSI is located on your computer and then type fastboot flash system xxxGSI NAMEXXX.IMG.... OBVIOUSLY REPLACE THE FIRST PART WITH THE ACTUAL NAME OF YOURS. Next press enter and give it a few seconds and then you should see it's a success at which time you can reboot the phone and it should boot after a few short minutes.
If you wanted to use the twrp I believe I saw something about how you have to be on version 3.2.2 or above most likely for blue spark version as I use that one because it has treble support and I can see the vendor image even though I don't touch it. So if you flash it here you want to make sure instead of rebooting to fastboot like before you would just go to install and select image then find the image on your phone select it and then select the system images where you are installing it and then wipe the bar at the bottom for Flash and then upon it finishing you should hit reboot and let the phone boot up the first time set it up and then you can go back and you can go back to TWRP if you want to flash magisk or any other modules or TWRP Zips I've stated first then make sure you move the phone and go back and do all the modifying after otherwise you're getting stuck. I hope this helps feel free to contact me if you have any trouble.

theandroidas said:
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Click to expand...
Click to collapse
Bro can u plz tell me how to get back to 8.1 oreo i am on 9.0 and didn't get treble support

can't encrypt after installing latest TWRP

Hello everyone,
i finally got the unlock code and moved from chinese to xiaomi.eu MIUI 10 rom . I installed lazyflasher, TWRP 3.2.3 and was good to go in a reasonable amount of time but i hit a wall. for work i need to encrypt my phone, it's non-negotiable and has to be done. but when i try to do it, the operation fails. as much as i read it's because newest versions of twrp reserve/lock/enumerate all the blocks of /data and there's not enough space to store encryption files in the /data. There are two ways out of this: either downgrade to an earlier version of TWRP ( 3.1.0 should work) or extend the /data partition. Now the problem is that i have already set up a lot on this phone so a complete wipe will be painful..
So my question is, can i get encrypted without wiping my phone? is there a way to downgrade TWRP or extend /data without formatting / wiping?

I also need an encrypted phone ...
Have you tried this?
https://forum.xda-developers.com/mi...very-twrp-3-2-3-1-nitrogen-t3866084?nocache=1
I still have to wait 255 hours to try this myself ....

ki01 said:
Hello everyone,
i finally got the unlock code and moved from chinese to xiaomi.eu MIUI 10 rom . I installed lazyflasher, TWRP 3.2.3 and was good to go in a reasonable amount of time but i hit a wall. for work i need to encrypt my phone, it's non-negotiable and has to be done. but when i try to do it, the operation fails. as much as i read it's because newest versions of twrp reserve/lock/enumerate all the blocks of /data and there's not enough space to store encryption files in the /data. There are two ways out of this: either downgrade to an earlier version of TWRP ( 3.1.0 should work) or extend the /data partition. Now the problem is that i have already set up a lot on this phone so a complete wipe will be painful..
So my question is, can i get encrypted without wiping my phone? is there a way to downgrade TWRP or extend /data without formatting / wiping?
Click to expand...
Click to collapse
use nijel8's twrp recovery for decryption
just flash recovery image in twrp

i flashed nijel's TWRP and now i can get through that window i was stuck on, but i get a toast with "find device closed unexpectedly" . i disabled find my phone and logged out of the xiaomi account i had on the phone, then rebooted and tried again. same thing. maby i should root and give full rights or something to the location app....

Android Q beta2 Rollback

Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks

nick w said:
Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks
Click to expand...
Click to collapse
Yeah you can either use the "flash-all.bat" file that comes in the android p stock image zip or fastboot boot twrp.img and once booted into twrp just restore a backup. But you'll need to create a folder on you sdcard called TWRP. Then put a backup in it. I've even booted twrp then flashed pixel dust. It's not as critical as it was years ago when once you went up bootloader then downgraded which would cause bricking. At least I haven't run into any issues. Just make sure you turn off any lock screens and have "USB debugging" enabled.

If you are enrolled in the beta, just opt out on the website where you opted in. You'll get an OTA, which will wipe your device, so back up first. Just did this last night. Couldn't have gone any more smoothly.

For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?

You have to have your phone unlocked... Yes, you will lose everything from internal memory, but can restore all your apps and settings.
I made this path twice, on beta 1 and now on beta 2.
First, make sure you have twrp. Back up on twrp everything but you will need only the data partition. Also don't forget to backup your internal memory (different from the data partition).
After that, just flash normally the last factory image from Pie, or at least the same version that you have on your nandroid backup.
After finish the installation, install again twrp. Go into twrp and restore ONLY the data partition!!! You can also restore the boot if you like (if you had magisk installed for instance). This worked flawless with me.
I repeat, no use if you try to restore ALL partitions on twrp!! At least with me, twrp would just reboot in the middle of restoring the system partition (no idea why that happened on beta 1 and now on 2). Second, the same if you try to flash factory image without the -w (without wiping internal memory), it just reboot every time it tries to enter android.

reno218 said:
For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?
Click to expand...
Click to collapse
This is a bug that was fixed in Q. You can alternatively fix it in pie by flashing a kernel that has Q patches merged in.