Team Win Recovery Project 3.0.2-0
This is for the Xiaomi Mi MIX only, do not flash on other models!
WARNING: As of Android Marshmallow, factory boot images have dm-verity enabled, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
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.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
For official stock/dev firmware: http://teamw.in/devices/xiaomimimix.html
For (slightly newer) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc1-eu-lithium.img
For (the latest EU) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc2-eu-lithium.img
(touchscreen will not respond if not matching firmware)
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
You must first unlock your device. To do this, follow the instructions on the MIUI forums. (tedious, I know)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract adb & fastboot to your computer.
Download TWRP for Xiaomi Mi MIX (lithium).
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Power] buttons while your device reboots.
Once you're in fastboot mode, you're ready to flash TWRP. To do this, run these commands in order:
fastboot flash recovery twrp.img
fastboot boot twrp.img
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Official release on twrp.me
v3.0.2-0-rc1 - Initial release candidate and first XDA build
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
There's absolutely none that I know of. Rejoice. You even have working hardware encryption!
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (Official): https://github.com/TeamWin/android_device_xiaomi_lithium (android-6.0)
Device tree (Development): https://github.com/jcadduono/android_device_xiaomi_lithium (android-6.0)
Kernel: Unavailable (waiting on Xiaomi source release, using MIUI stock binary for now)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thank you to @wolfgart for requesting device support and reporting feedback on my initial builds.
Great Work
Now Xiaomi MI MIX is the greatest device we can have atm
@jcadduono @wolfgart Wolfgart request your help just because in Italy I've already published italian rom with my recoveryas you see from here
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=999961
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=1000010
But your official support is obviously better than mine. I follow you in a lot of thread so I know your great work:good::good: Very happy for this
development is starting , great work OP
agriculture said:
development is starting , great work OP
Click to expand...
Click to collapse
Best device now has best TWRP ever made before.
tnx @jcadduono
Looks like it won't be showing up on twrp.me until 3.0.3 or 3.1.0 depending on what's next. There's a few incompatibilities in the device tree and I'd prefer to wait it out till then. Ex. 3.0.2 doesn't support f2fs or ntfs on omnirom trees right now, but our current source does. If I made an official release neither would be supported.
Update: Official release made on newer TWRP build tree.
Wow, a thousand thanks.
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
mega00 said:
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
Click to expand...
Click to collapse
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
mega00 said:
Wow, a thousand thanks.
Click to expand...
Click to collapse
don't quote the entire thread opener.... edit your post and remove it, if you need to make adjustments use the edit button, don't make another post immediately after your own
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Update: Yes, I changed to stable rom and it works.
Click to expand...
Click to collapse
mega00 said:
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Click to expand...
Click to collapse
you have to flash CN Stable rom V8.0.8.0.MAHCNDI (MIUI8) and use original TWRP for it and if you want Cross-Flash your CN rom with International one Here too .
When you are on International rom up&running you can flash over the EU TWRP .
As explained from @jcadduono this is the only solution for the moment until XIAOMI release his Kernel stuff officially
Click to expand...
Click to collapse
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
cultofluna said:
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
cause Stock kernel still was not relased you have to simply flash EU Rom using stock TWRP and after you done you have to change to TWRP EU to make it working again .
We are waiting official sources from Xiaomi
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
I waited about 4 hours after submitting the application, 2 weeks is a maximum estimation.
knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
you have to wait few minutes or at last 24 hours to receive sms unlock approve
:good::good:
wolfgart said:
you have to wait few minutes or at last 24 hours to receive sms unlock approve
Click to expand...
Click to collapse
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
jim380 said:
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
Click to expand...
Click to collapse
you have to Log On with your MIUI account on device too and the retry to unlock
---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------
knives of ice said:
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
Click to expand...
Click to collapse
it works ! I can confirm. And it works using Flashify too
Related
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]OnePlus One[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread, we have an entire q&a section for that.
If you have any suggestions for additional questions/answers please feel free to contact me, any potential additions and improvements are welcome.
You can find some detailed guides here:
[GUIDES][UNLOCK/ROOT/FLASH]How-To Guides For Beginners.
See also:
[INDEX] OnePlus One.
Q1: What is adb/fastboot?
Guide - What is adb and how do I use?
[Guide] How To Setup And Use Fastboot
Q2: Does unlocking/rooting my phone void my warranty with OnePlus?
No.
Q3: How do I unlock/root my phone?
Rooting this device is simple, all you need to do is unlock the bootloader, install a custom recovery, and from there you can install SuperSU to root your stock ROM, or you can install a pre-rooted custom ROM. Here is a guide that outlines the details:
[GUIDE] Unlock/Root/Flash for OnePlus One
Q4a: Can I flash ROMs or SuperSU or anything else with the stock recovery?
No, the stock recovery can only flash zips that are signed by CM, this means official updates only. You need a custom recovery to flash anything else.
Q4b: Which custom recovery should I use?
We have a few options for recovery, you can use choose from the following:
[OFFICIAL][RECOVERY] Cannibal Open Touch
[RECOVERY]ClockWorkMod Recovery (CWM)
[Recovery]CWM-based Recovery for Oneplus
[bacon][CWM Advanced Edition] PhilZ Touch
[RECOVERY][bacon] TWRP Touch Recovery
Q5: How do I flash my custom recovery?
Flashing a custom recovery is pretty easy using fastboot and you'll find full instructions in these threads:
[GUIDE] Unlock/Root/Flash for OnePlus One
Q6: Can I still receive and install an OTA on my rooted device?
Yes you can. But, if you have any modified system files or Xposed Framework installed the OTA will fail. You can use the built-in update feature in Settings>About Phone>Updates to update, or you can manually download an OTA and flash it. You can even flash an OTA update with your custom recovery. Here's a thread with all of the current CM11S full ROMs and OTA updates:
[ROM][OTA] Mirrors for official Cyanogen roms & OTA updates
Q7: Do I need to relock my bootloader or have stock recovery to run Cyanogen OS again and have full OTA functionality?
No you don't need to relock your bootloader or have the stock recovery installed to run Cyanogen OS again with OTA functionality. All you need to do is flash the stock images via fastboot or flash a recovery flashable version of Cyanogen OS via your custom recovery and you'll be on the stock ROM again with OTA capability. See this thread:
[ROM][OTA] Mirrors for official Cyanogen roms & OTA updates
Q8: How do I return my phone to being completely stock?
Just follow this tutorial:
[GUIDE] Return your OPO to 100% Stock
Q9: How do I flash a boot.img via fastboot?
Flashing a boot.img is taken care of with fastboot, full instructions here:
[GUIDE] Unlock/Root/Flash for OnePlus One
Q10: Is my phone Bricked?
If you can boot into fastboot mode or recovery then the answer is No. If your phone will not boot at all, and/or shows up as a QHSUSB in Device Manager on your PC, then yes you're bricked. But, there's an effective unbrick tool here:
[GUIDE] [UNBRICK] Unbrick Oneplus One
Q11: My PC won't connect to the phone by USB (for fastboot, adb, etc.), what do I do?
Make sure you have the correct/latest adb/fastboot drivers installed, make sure you have usb debugging enabled in Settings>Developer Options, and/or try another usb port/cable.
Q12: How do I relock the bootloader, or return to stock (or close to stock as possible)
Connect your phone in fastboot mode and issue the following fastboot command:
Code:
fastboot oem lock
Q13: Will rooting affect my battery life?
No, simply rooting the phone should not hamper battery life. However, battery life can change dramatically from ROM to ROM.
Q14: What is the best radio?
Reception and battery life are subject to exact geographic location, and other variables, therefore nobody can suggest a radio for you. Picking a radio is often trial-and-error, flash a radio and note the signal strength and battery performance. Not the bars in your status bar, but the actual signal strength measured by db (-110db is poor strength and -51db is good strength). This can be found in Settings/About Phone. Repeat the process until you've found the best radio for you. See the radio thread:
[REF] [RADIO] OnePlus One Modem Collection
Q15: What is the best ROM?
There is no 'best' ROM, each user has different tastes and needs from a ROM, the best way to find out which ROM is best for you is to test them for yourself
Q16: How can I find custom ROMs and kernels for my phone?
Just have a look through our development sections, but do not stray out of the OnePlus One section because flashing a ROM from a different device will brick your phone. There is a full OnePlus One index thread that lists all current ROMs, kernels, and everything else here:
[INDEX] OnePlus One
Q17: How do I know which kernel is compatible with which ROM?
It's pretty simple, usually the OP in each kernel thread will state what Android versions it is compatible with. If not, there's usually a discussion taking place that answers the question.
Q18: What is an md5 and why is it important?
An md5 is like a digital fingerprint of a file. The md5 should be listed on the download page for a file. Once you've downloaded a ROM/kernel/radio/mod etc you must check that the md5 of the downloaded file matches the md5 listed on the download page exactly. This ensures that the integrity of the file is intact and it hasn't become corrupted during the download. If a file has changed even slightly during a download the md5 will change dramatically. If the md5 of your downloaded file doesn't match, do not flash it, it could cause major problems on your device.
Q19: Google Play Services (or Android OS) is killing my battery, how do I stop it?
See my detailed guide here:
[GUIDE][PSA] Google Play Services battery drain fix
Q20: What do I need to do when changing from KitKat to Lollipop or vice-versa?
When going from KitKat to Lollipop you need to flash the Lollipop firmware and modem. When going back from Lollipop to KitKat you need to flash the KitKat firmware and modem.
See section 9 of my guide for full instructions:
[GUIDE] Unlock/Root/Flash for OnePlus One
Q21: I just flashed a ROM and now I can't turn the screen on with the power button, or I have a black screen during calls, what's going on !?
See question 20
Q22: I've updated to CM12S and now I can't flash a custom recovery, why?
For some reason CM12S doesn't respect the on/off toggle for the "update CM recovery" option in Developer Options, it just replaces whatever custom recovery you've flashed with the CM recovery regardless of whether that option is unelected.
Flash your custom recovery again, but after flashing don't do a normal reboot. After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button down, once it's powered off use the power + volume down button combo to boot directly into recovery. This first forced reboot into recovery somehow subverts what was keeping it from staying flashed and all subsequent normal reboots into recovery will boot into the custom recovery of your choice. See section 2 of my guide for full instructions:
[GUIDE] Unlock/Root/Flash for OnePlus One
'This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.'
Forum Rules | New Users Guide | XDA Tour | Report Posts
Donate To Me
Transmitted via Bacon
@timmaaa you've forgot one question
is it necessary to re-lock the bootloader in order to run CM11S again.?
currently on MAHDI with un-locked bootloader and TWRP on board.
what are the options I have to bring back Stock on board (by Stock I mean CM11S w/ working OTA and root if possible).
Thank you
funCrash93 said:
@timmaaa you've forgot one question
is it necessary to re-lock the bootloader in order to run CM11S again.?
currently on MAHDI with un-locked bootloader and TWRP on board.
what are the options I have to bring back Stock on board (by Stock I mean CM11S w/ working OTA and root if possible).
Thank you
Click to expand...
Click to collapse
Thanks for the suggestion, I'll add that one soon.
Transmitted via Bacon
Updated 06/10/2014!
Added:
Q7: Do I need to relock my bootloader or have stock recovery to run CM11S again and have full OTA functionality?
Q8: How do I return my phone to being completely stock?
Transmitted via Bacon
Q2: Does unlocking/rooting my phone void my warranty with OnePlus?
No.
Click to expand...
Click to collapse
what is the source of this info?
thanks!
Lanchon said:
what is the source of this info?
thanks!
Click to expand...
Click to collapse
OnePlus.net
P1nGu1n_ said:
OnePlus.net
Click to expand...
Click to collapse
Correct, straight from OnePlus.
Transmitted via Bacon
adamo86 said:
Does xposed work on the opo or does it break features
Click to expand...
Click to collapse
P1nGu1n_ said:
Yes it works, no it doesn't break anything, why would it?
Sent from my phone, please forgive any tpyos.
Click to expand...
Click to collapse
As per the OP, this is not a Q&A thread, please take this discussion elsewhere.
Transmitted via Bacon
Updated 2015/02/03!
Added:
Q20: What do I need to do when changing from KitKat to Lollipop or vice-versa?
Transmitted via Bacon
Is the latest twrp3 recovery and su.zip the latest version compatible with cm12 YNG1TAS213(stock unrooted)
Confused with many comments
Thanks
I flashed cos13 bacon signed zip thru twrp 3.0.2-3. And after successfully installing it changes also my recovery to cm recovery and my twrp is gone. Do I need to flash twrp thru fastboot again??
dxlevel81 said:
I flashed cos13 bacon signed zip thru twrp 3.0.2-3. And after successfully installing it changes also my recovery to cm recovery and my twrp is gone. Do I need to flash twrp thru fastboot again??
Click to expand...
Click to collapse
Yep
---------- Post added at 02:03 PM ---------- Previous post was at 02:02 PM ----------
Reeve005 said:
Yep
Click to expand...
Click to collapse
If u wany twrp recovery u have to flash
hi guys im using Oneplus one and im new to this world! N im so confused whether to use xposed or not!! coz my ROM dev posted that he isnt responsible for the bugs if we flash xposed !! im using DIRTY UNICORN 10.6 currently... so whats ur suggestion?? can i flash xposed?? this may be an simple issue bt im a noob hence i see this as a big one.. sorry if i wasted ur time bt pls consider to give me a solution
Is any ROM available for OPO that support VoLTE please tell me
Resurrection remix rom is the best rom i suggest and it also meets your need of working voLte in it without setting changed
Sri vignesh said:
hi guys im using Oneplus one and im new to this world! N im so confused whether to use xposed or not!! coz my ROM dev posted that he isnt responsible for the bugs if we flash xposed !! im using DIRTY UNICORN 10.6 currently... so whats ur suggestion?? can i flash xposed?? this may be an simple issue bt im a noob hence i see this as a big one.. sorry if i wasted ur time bt pls consider to give me a solution
Click to expand...
Click to collapse
Is Dirty Unicorn Stable and Bug Free?Need help going to flash it
Hey people try this..
rHn7113 said:
Is Dirty Unicorn Stable and Bug Free?Need help going to flash it
Click to expand...
Click to collapse
Yes it is!
Hm
How to Install Nethunter on OPO with secondary Rom as slim rom(NOUGAT) or LOS ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you @shunjou for helping RS988 to go official!
This is the official support thread for TWRP for RS988.
Installation from Stock:
**If your bootloader isn't already unlocked, go to the LG Developer website. You'll need to create an account. You can get the necessary ADB and fastboot tools from the Android SDK Platform Tools.**
If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
1. Reboot into the bootloader with the command "adb reboot bootloader" and issue the command "fastboot flash recovery twrp-x.x.x-x_rs988.img", replacing "twrp.x.x.x..." with the location of the TWRP image on your drive.
2. Once it is done writing the image and says "finished," detach all power sources and remove the battery. This step is important—if you reboot into the system instead, TWRP will be overwritten by the stock recovery.
3. Reinsert the battery. Then start the phone, holding down both the Volume Down and Power button. When the LG logo appears, quickly release and re-press the Power button, continuing to hold Volume Down. This should bring you to a Factory Data Reset screen.
4. Confirm "Yes" on the two prompts (don't worry, no data will be deleted—we've overwritten the stock recovery) and you will be in TWRP.
Make sure to follow these steps as written, and make backups if necessary. You wouldn't want to risk saying "Yes" and actually wipe your data, right?
Click to expand...
Click to collapse
Working:
It works. If there are any problems, report them here.
Click to expand...
Click to collapse
Downloads:
Builds may be downloaded from the TWRP website.
Production builds: twrp.me/lg/lgg5rs988.html.
Test builds will depend on the current version of TWRP. For example, for v3.2.3.0 : http://build.twrp.me/twrp-3.2.3-0-rs988.img
Click to expand...
Click to collapse
XDA:DevDB Information
[OFFICIAL] TWRP 3.3.1-0 for LG G5 RS988, Tool/Utility for the LG G5
Contributors
NextDroid, shunjou
Source Code: https://github.com/TeamWin/android_device_lge_rs988
Version Information
Status: Stable
Created 2018-06-14
Last Updated 2019-06-11
Reserved?
Encryption not working for Linage 15.1
If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
Click to expand...
Click to collapse
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.
djskribbles said:
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.
Click to expand...
Click to collapse
Hey @djskribbles,
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Also, you'll be better off if you use Magisk instead of SuperSU. Flash Magisk before LineageOS, because the script used to flash it automatically wipes the /system partition, which is where SuperSU, for example, makes its changes to enable root access.
NextDroid said:
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Click to expand...
Click to collapse
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.
shunjou said:
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.
Click to expand...
Click to collapse
All right, that's great to hear! I'll admit, I wasn't sure when I made that second comment... it had been a while since I'd heard anything on stock encryption.
I actually just finished cooking up a fix for Oreo encryption from work on the G6... I'll head over to zl1 if it doesn't work out.
We'll see what happens... --fingers crossed--
On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?
Awkydee said:
On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?
Click to expand...
Click to collapse
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.
NextDroid said:
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.
Click to expand...
Click to collapse
Yippie! Flashing now!
can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
bmanuelangel said:
can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Click to expand...
Click to collapse
Are you referring to stock? Hopefully you won't need to re-lock the bootloader. When a .kdz package is published, hopefully @Unscedeo will make one of his COMPLETE INSTALLERS for it, and you could just flash it.
Hmm, I ought to keep up with this thread a bit more...
I've made some updates today and created a test build. Here is the link for anyone who wishes to test: http://build.twrp.me/twrp-3.2.3-0-rs988.img
Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html said:
* Fix selinux issues during formatting - dianlujitao
...
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Click to expand...
Click to collapse
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?
Ascii3 said:
Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
I have been very busy for the past couple of months, but the G5 hasn't left my mind... I use it every day I'll see when I can update TWRP and my other builds.
Thanks for keeping us updated, @Ascii3!
NextDroid said:
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
Click to expand...
Click to collapse
Maybe, if I have some time, myself. It is looking like something for August 2019.
NextDroid said:
I have been very busy for the past couple of months...I'll see when I can update TWRP and my other builds.
Click to expand...
Click to collapse
I am glad to see that you your are still around.
NextDroid said:
Thanks for keeping us updated, @Ascii3!
Click to expand...
Click to collapse
Sure.
Ascii3 said:
Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
I can and shall answer this question that I posed before:
TWRP allows for both RAW and file-based backups. Usually, however, the GUI provides few items for RAW backup; there is typically a backup option for "System Image" which is a RAW backup.
@NextDroid - I noticed that more recent versions of your TWRP do not have the System Image backup option despite it being in your older TWRP 3.2.3-0 build. The System Image backup functionality from TWRP 3.2.3-0 seemed to work OK. Did you deliberately exclude the "System Image" backup option? I the option missing for good reason?
Team Win Recovery Project 3.6.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash custom binaries to your phone. Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904
Reserved
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.
costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!
costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data
Everything working!
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:
Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.
Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?
toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733
ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)
xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?
ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Asus Max M1
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight(back)
Camcorder
Bluetooth
FMRadio
Fingerprint reader
Lights
Sound / vibration
Facelock
Known issues
MSM8917 variants
Telegram Group
Link
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Build author/Device Maintainer: Saalim
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
XDA:DevDB Information
pixel-experience, ROM for the Asus ZenFone Max M1
Contributors
saalimsam
Source Code: https://github.com/pixelexperience-devices/device_asus_X00P
ROM OS Version: Android 11
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie firmware.
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-04-15
Created 2020-04-09
Last Updated 2020-10-12
Nice work ?
Any guides on how to unlock the bootloader and install TWRP?
Thanks in advance.
althafvly said:
Nice work
Click to expand...
Click to collapse
I am sure you will achieve the same with the Moto x play. You are the best!
manishurfmannu said:
Any guides on how to unlock the bootloader and install TWRP?
Thanks in advance.
Click to expand...
Click to collapse
download this apk and follow instructions to unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE620KL/AsusLauncher_5.0.1.70_190801_generic.apk
you need to install twrp via fastboot . And download image from here.
https://twrp.me/asus/asuszenfonemaxm1.html
iamsaalim said:
download this apk and follow instructions to unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE620KL/AsusLauncher_5.0.1.70_190801_generic.apk
you need to install twrp via fastboot . And download image from here.
https://twrp.me/asus/asuszenfonemaxm1.html
Click to expand...
Click to collapse
But the apk link is just launcher. I tierd installing it on the device but installation fails with the error "app not installed"
iamsaalim said:
download this apk and follow instructions to unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE620KL/AsusLauncher_5.0.1.70_190801_generic.apk
you need to install twrp via fastboot . And download image from here.
https://twrp.me/asus/asuszenfonemaxm1.html
Click to expand...
Click to collapse
I had successfully unlocked the bootloader and installed TWRP. After flashing the latest build the device is encrypted and asks for a password every time I reboot the device & when I open the TWRP it also asks for a password to decrypt. So is there any way to remove the encryption?
manishurfmannu said:
I had successfully unlocked the bootloader and installed TWRP. After flashing the latest build the device is encrypted and asks for a password every time I reboot the device & when I open the TWRP it also asks for a password to decrypt. So is there any way to remove the encryption?
Click to expand...
Click to collapse
You can use your screen lock to decrypt the data, if it still doesn't work, format the data partition and flash magisk before first boot.
manishurfmannu said:
I had successfully unlocked the bootloader and installed TWRP. After flashing the latest build the device is encrypted and asks for a password every time I reboot the device & when I open the TWRP it also asks for a password to decrypt. So is there any way to remove the encryption?
Click to expand...
Click to collapse
Format data or use unofficial twrp
Which version of pixel experience should I install
10 or 10 plus?
Help me
saurabhw said:
Which version of pixel experience should I install
10 or 10 plus?
Help me
Click to expand...
Click to collapse
Is there ten plus??
raza231198 said:
Is there ten plus?
Click to expand...
Click to collapse
Yup there is ten plus, you can check on official website
saurabhw said:
Yup there is ten plus, you can check on official website
Click to expand...
Click to collapse
:/ Ask saalim he didn't give for testing ?
saurabhw said:
Yup there is ten plus, you can check on official website
Click to expand...
Click to collapse
There's no Plus version for this device go and check website yourself first.
I will try this as soon as possible: has the wifi reception, by any chance, been improved compared to stock rom? IRRC back in the days there was the "radio" part of the software that could be modded.
What camera app does it use? the stock Asus cam, gcam, or the aosp cam?
I got a new X00PD (ZB555) and I wanted to try putting this rom on it out of the box. I have done:
1) Unlocked bootloader via Asus apk
2) Booted into fastboot and flashed unofficial TWRP
3) Rebooted into TWRP.
4) Flashed twrp in twrp (I wasn't sure if this was needed or not)
5) Rebooted into recovery
6) Wiped dalvik, system, cache, data
7) Flashed Pixel Experience. TWRP says it was successful.
Here is where I have a problem. On reboot its a boot loop.
I've tried flashing this rom now 4 times, keeps giving me a boot loop. I just booted into fastboot and reflashed TWRP and then tried to flash the rom from there, still boot loop.
I have questions:
1) Did I do things right?
2) Could the message on TWRP's site have something to do with this "This device uses dm-verity! This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel."? I never got a request to allow system modification.
3) Yikes, what do I do now?
reao8890 said:
I got a new X00PD (ZB555) and I wanted to try putting this rom on it out of the box. I have done:
1) Unlocked bootloader via Asus apk
2) Booted into fastboot and flashed unofficial TWRP
3) Rebooted into TWRP.
4) Flashed twrp in twrp (I wasn't sure if this was needed or not)
5) Rebooted into recovery
6) Wiped dalvik, system, cache, data
7) Flashed Pixel Experience. TWRP says it was successful.
Here is where I have a problem. On reboot its a boot loop.
I've tried flashing this rom now 4 times, keeps giving me a boot loop. I just booted into fastboot and reflashed TWRP and then tried to flash the rom from there, still boot loop.
I have questions:
1) Did I do things right?
2) Could the message on TWRP's site have something to do with this "This device uses dm-verity! This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel."? I never got a request to allow system modification.
3) Yikes, what do I do now?
Click to expand...
Click to collapse
Have you msn8917 or msm8937 variant
raza231198 said:
Have you msn8917 or msm8937 variant
Click to expand...
Click to collapse
Uh oh, did not consider checking for that. Using 'getprop' in TWRP's terminal (had to search for this command), it says
[ro.board.platform]: [msm8937]
then it also says
[ro.boot.platformtype]: [msm8917]
Does that help or is that more confusing? Any other things I can do in fastboot or TWRP to produce better information?
Thank you so much for helping!
Edit: The exact model number of this phone is: ZB555KL-4G151TW but I can't find reference to this exact model number with websearches.
Edit2: On your Lingeage OS page it says to flash FIRMWARE-ASUS_X00P-WW-16.00.1906.411-user.zip. I never did this, should I do this for this rom too? Is it safe to flash a stock rom after putting on TWRP (I was about to try your ROM but wasn't sure if I could flash this stock firmware))? Thanks again!
raza231198 said:
Have you msn8917 or msm8937 variant
Click to expand...
Click to collapse
Ok I am like 85% sure this is msn8917. Does anyone know if this ROM works with this CPU?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
OOS 12 H.38 firmware is mandatory (can update via firmware update tool found on download page, firmware button)
Download recovery (from download page, recovery button)
Optional NikGapps core (download - note that you may also need setup wizard addon if you rely on Google restore)
Optional Magisk (boot.img used to patch with Magisk in order to get root, can be found in recovery folder from download page)
First time installation (clean flash):
Backup your data to PC, OTG flash drive
Make sure you have OOS 12 firmware installed (if used firmware flash tool from download page, proceed straight to install crDroid.zip)
Enter fastboot
Flash our boot.img in fastboot
Code:
fastboot flash boot boot.img
Boot to recovery (can do from bootloader or with buttons from power off state)
Now in recovery go to factory reset and confirm the reset
Reboot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload
Code:
adb sideload crDroid.zip
Go back to main menu and reboot to recovery to install gapps (if you don't want gapps, reboot to system)
To install gapps, simply reboot to recovery again and sideload gapps.zip the same way you installed crDroid.zip then reboot to system
Update installation:
Via recovery (recommended way):
Boot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload and reboot
Code:
adb sideload crDroid.zip
If you had gapps, reboot to recovery and sideload gapps.zip and reboot
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
If you have Magisk installed, don't click reboot when prompted and go to Magisk and choose install to inactive slot
Reboot
Note: In some cases where incompatible gapps used, may result in boot issues that should get fixed by flashing gapps again in recovery.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8150
Download:
ROM https://crdroid.net/guacamole/9
Visit official website @ crDroid.net
crDroid OnePlus 7 Pro Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
Hi dev, your rom title date is wrong we still in october . Anyway thanks for the rom. Is there any specific oneplus settings available in this rom?.
yakuzax1 said:
Hi dev, your rom title date is wrong we still in october . Anyway thanks for the rom. Is there any specific oneplus settings available in this rom?.
Click to expand...
Click to collapse
hehe
yeah... sorry about that )
@gwolfu Thanks for the first 13 build.
Is EROFS planned in the future? just curious.
Toutatis_ said:
@gwolfu Thanks for the first 13 build.
Is EROFS planned in the future? just curious.
Click to expand...
Click to collapse
not really
last I tried, had issues with gapps with it
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Can I upgrade to firmware 12 directly over OOS 9? Or do I need to upgrade over firmware 11?
Solved
gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
Hello Dev, thanks for a new support for android 13. To be root through magisk, is it done as in crdroid v8? that is, is the boot patched with magisk and flashed with fastboot?
gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
Wow that is awesome I was going to ask for clarification on that (if OOS 12 beta was indeed required or if it was a typo). And it seems it really is required but you made it super easy instead of needing to flash the full OOS 12.
MUCH thanks and appreciation for bringing us CRDROID 13 along with an easy to use flash tool for OOS 12 firmware. Been waiting for A13 of crdroid, crdroid being the best with features and stability. + a great dev to boot
Are you talking about the OOS12 H.31 gloabal beta? Either way, the firmware tool does the job and makes it easy.
Also, will features like smart pixels eventually be on A13 like in A12? nvm seems like all features are still here after dirty flash and firmware change. Switched to big fingerprint now, but it's miscentered like in the pic.
Well flashed the firmware update and the new build, everything went smooth. Nice!
I have a few bullet points:
--After flashing the firmware tool, the stupid "warning" that the bootloader is unlocked is now gone that is awesome. I've wanted that gone since I unlocked but I read it's dangerous to mess with...so I did not plan on that happening but love it
--Seems all crDroid settings from A12 are here and maybe a few extra. Sweet! I was thinking there may be a few things missing because it's a new base but nope, think it's all here.
--The "taskbar" for the crDroid launcher? Super amazing! Not sure if that was there on the previous A12 builds? I've been on Nova Launcher for years now so I'm not sure if this is new to the A13 build. But I absolutely love the taskbar idea (everything still works the same, swipe up for home, swipe up far for recents and drag left-right on taskbar for previous app). I'll attach a pic for those wondering incase it's new.
--Speaking of the launcher, is there any topic/place where we can talk about it? Request features, ask things? Like I'd like to request being able to hide drawer icons/apps and be able to put them into folders (in the app drawer). Also any way to back it up? Like the settings and placement of icons? Using nova and having a backup/restore makes it easy to clean flash ROMs and be right back to normal after. But I think I'd like to stick to crDroid launcher because of this taskbar feature - it's so handy!
--I notice the "Smooth Display" (going from 60Hz to 90Hz) works properly in this ROM. That is nice for people that want to save battery (if you don't want that half second delay from the change-over, in dev-tools it can be still forced to 90Hz all the time).
--Not a big deal but I think I notice the status bar icons very high up, almost touching the top bezel. The OCD in me says arrgg lol. WHY does google mess with the dang paddings on these things...
Those are the few things I've noticed so far. A very nice "initial" release! Seems really smooth too! Thanks again @gwolfu
I am having problems with the back gestures on the screen, anyone else having this problem?
Will wait for feedback regarding the Qualcomm crash dump issue many users and I had on v8 before flashing. Hopefully it's gone for good...
Toutatis_ said:
Will wait for feedback regarding the Qualcomm crash dump issue many users and I had on v8 before flashing. Hopefully it's gone for good...
Click to expand...
Click to collapse
That is not ROM related. That is firmware related.
I only had that happen to me once in the past 6 months (and I've tried every ROM possible during that time), I updated my firmware and never had it again on any ROM. So, updating the firmware here (to OOS 12 as instructed) you should be good to go.
If you still don't want to take the chance, I'd recommend sticking with stock OOS for full stability. These ROMs are basically always beta as it's cutting-edge and you'd have to deal with bugs/testing.
SLAlmeida said:
I am having problems with the back gestures on the screen, anyone else having this problem?
Click to expand...
Click to collapse
Like swiping back? Nope all working good here. I've had no bugs yet. Except 'maybe' slight lag in a game while auto brightness was on (I turned it off and there is now 0 lag).
theslam08 said:
That is not ROM related. That is firmware related.
Click to expand...
Click to collapse
I've always flashed latest OOS version available to both slot prior to flashing any crDroid v8 build, but always had the Qualcomm dump crash at some point regardless.
theslam08 said:
I only had that happen to me once in the past 6 months (and I've tried every ROM possible during that time)
Click to expand...
Click to collapse
I used quite a lot of A12 ROMs too (YAAP, KOSP, Bliss, PixelExperience, Project Elixir, EvolutionX, DerpFest) and only had this issue with crDroid.
theslam08 said:
So, updating the firmware here (to OOS 12 as instructed) you should be good to go.
Click to expand...
Click to collapse
Hopefully, I'll try v9 eventually and see how it goes.
gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
keeps "waiting for devices" at fastbootd mode, doesn't detect my device
Whatever it did prior to this stage killed the system and now I have to msm back to oos11 manually...
theslam08 said:
Like swiping back? Nope all working good here. I've had no bugs yet. Except 'maybe' slight lag in a game while auto brightness was on (I turned it off and there is now 0 lag).
Click to expand...
Click to collapse
Yes, but when I enable the bottom navigation bar in in the crDroid settings, it works again.
I just can't use the on-screen gestures without enabling the navigation bar, and one thing has nothing to do with another.
does this rom have a problem with screen wake up/fod with ambient display on? or is that stable on this one
also, anyone who used evolution x (a13), how does the battery life compare?
Toutatis_ said:
I've always flashed latest OOS version available to both slot prior to flashing any crDroid v8 build, but always had the Qualcomm dump crash at some point regardless.
I used quite a lot of A12 ROMs too (YAAP, KOSP, Bliss, PixelExperience, Project Elixir, EvolutionX, DerpFest) and only had this issue with crDroid.
Hopefully, I'll try v9 eventually and see how it goes.
Click to expand...
Click to collapse
Hm yeah I'm not sure then. Something weird going on there - I've personally never had any crash dumps on this ROM (it was on FlamingoOS) and rarely see anyone say they're having crash dumps on it either. The few times I have, they were told to update the firmware which they supposedly did and didn't have any problems after.
Your best bet if possible would be to get a log of it when it happens: https://pastebin.com/GGaRZ2nJ