Related
Hi all,
I'd like to enable phone encryption on my Z00AD (running 6.0.1 .134) and I'm wondering how much that may affect performance and battery life.
Anyone already using it wanting to share their experience?
Thanks
I did on LL and upgraded to MM just fine. Also when I did a factory reset in MM I re-encrypted it, no problem.
Encryption/decryption is done by hardware (Intel CPU) so there is no performance/battery issue.
Thanks, good to know.
I was more worried about battery life than performance, but if either one is negligible I'm all set.
Done, worked like a charm [emoji106]
Encrypted in 5 minutes flat, no performance or battery hit that I can see, really a no brainer.
Performance and battery life is great with encryption as others have mentioned. However, I suspect they've changed something with the encryption from Lollipop to Marshmallow given I am unable to unlock the phone in TWRP, even on fresh installs (flashing raw Lollipop with Asus Flash Tool, making sure to delete all data/cache, sideloading Marshmallow, then setting things up). It also seems since I am not able to unlock the phone in TWRP, when I go to flash SU/Magisk/Xposed, it is only temporary (I think saved in dalvik). Made a thread about this, but it doesn't seem anyone else has used encryption + TWRP in Marshmallow yet, or hasn't bothered to reply (http://forum.xda-developers.com/zenfone2/help/twrp-invalid-password-mm-update-z00a-t3453228)
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?
fred_gaou said:
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?
Click to expand...
Click to collapse
Fred, it's a 2 years old thread, yes TWRP was fixed years ago for this
Which one do you guys recommend the most?
I'm on stock Oreo (soak 4) and I'm curious about PE.
What can you guys tell me about it?
Pixel Experience!! Because it gives you some pixel like features. And I've noticed that stock ROMs usually have problems with Root!! When I had rooted my device the camera had stopped working. I tried everything but the only way to get it to work was uninstalling magisk!
S4xk said:
Pixel Experience!! Because it gives you some pixel like features. And I've noticed that stock ROMs usually have problems with Root!! When I had rooted my device the camera had stopped working. I tried everything but the only way to get it to work was uninstalling magisk!
Click to expand...
Click to collapse
But how am I getting sure that don't ruin my IMEI or persist in the process of trying Pixel Experience?
eder5jga said:
But how am I getting sure that don't ruin my IMEI or persist in the process of trying Pixel Experience?
Click to expand...
Click to collapse
Just make sure you backup those partitions on TWRP preferably on an external drive for safekeeping. Or if you loose them there's a guide here on xda that allows you to restore it but you'll end up getting your internal storage wiped in the process. I'd rather advice you to backup system, data( if you want ), persist, efs, and maybe even oem (for when you use treble ROMs in future).
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !
I have an international 6T on Verizon. I've been running AOSP ROM's without issue for about 3 weeks. A few days ago due to my own screw up I had to use the MSM tool and start over. I got back on Havoc and ever since I can't get a stable connection except on LTE only mode. But in this mode I can't text or call -- though, data works perfect and stays connected. I've tried all the kernels and various other AOSP based ROM's and it's always the same issue. Short of using the MSM tool again and starting fresh for the 4th time I've tried everything I can think of. I feel like there has to be a solution without using the MSM tool and I'd hate to go through all that and get the same problem again. There must be a solution. Thanks for any help.
I ran the MSM tool again, got everything rooted, and flashed the older version of Havoc I had working, and my radio is still acting stupid. I don't understand. I checked everything while I was on stock and everything worked perfect. This one has me stumped.
imucarmen said:
I ran the MSM tool again, got everything rooted, and flashed the older version of Havoc I had working, and my radio is still acting stupid. I don't understand. I checked everything while I was on stock and everything worked perfect. This one has me stumped.
Click to expand...
Click to collapse
Are you sure that the OOS version you are flashing with MSM tool isn't too new for the older Havoc ROM? i.e do you need to flash an older OOS base? No guarantee that Havoc has been build for the latest OOS base.
bowlandspoon said:
Are you sure that the OOS version you are flashing with MSM tool isn't too new for the older Havoc ROM? i.e do you need to flash an older OOS base? No guarantee that Havoc has been build for the latest OOS base.
Click to expand...
Click to collapse
I'm not sure why this would effect anything. Havoc isn't old since it's based on the latest Pie updates. Also, I had everything working before. It's just for some reason now no matter what I have this radio issue and can't get messages and phone to work.
imucarmen said:
I'm not sure why this would effect anything. Havoc isn't old since it's based on the latest Pie updates. Also, I had everything working before. It's just for some reason now no matter what I have this radio issue and can't get messages and phone to work.
Click to expand...
Click to collapse
I know it's not old just I know from experience customs ROM's aren't always built on the newest base for the device. However in this case it looks like the newest version of Havoc is based on 9.0.12 so it's not that...
Strange that it's happening from a clean flash of OOS. Have you tried just formatting data from TWRP and flashing OOS from recovery rather than MSM tool?
Weirdest thing. But sideloading havoc in twrp fixed the issue. I side loaded havoc and the twrp installer and rebooted system and it booted up with data working along with calling and text.
I rebooted recovery and installed gapps and magisk and all is well. Still don't know what the issue was but glad I got working.
Hi,
I was on stock Pie firmware on mi a1. I tried to install twrp recovery in my device and somehow messed it up while flashing stock roms and all those things. Now my touch is not working properly. I can flash stock pie rom via fastboot method, but cannot go through setup process because my touch is a bizzare. I then tried to flash stock oreo and nougat firmwares and stuck in bootloop. I'm even tried booting into TWRP to see if anything would help, but the touch issue seems to affect twrp as well. Please help me out with this.
Thanks.
Do you fixed your problem? I don't know what happened but after I flashed the stock ROM the touch screen is useless. I already flashed everything in miflash and the screen is still broken... I don't know what to do, help pls
Hi!
I already fix a similar problem on my phone.
After a screen replacement, I had a touch-screen issue which was detecting the touches, but at a pseudo-random position.
The solution that worked for me was to flash the first stock nougat image released (September 2017 ), and then to upgrade to pie using the classical way through OTAs.
But you have to be very careful while doing this as you will encounter some kind of weird issues if you do this the wrong way, like lost IMEIs and some others that I don't remember.
You'll find some tutorial on how to downgrade from Pie to Oreo and then I don't remember well but I think you will be able to flash directly android one 7.1.2.
I hope this will solve your touchscreen issue (let me know if that worked for you or if you have any other problem occurring)