Related
Resurrection Remix by quanganh2627
What is NOT working:GPS, FM radio, Autorotation
What is working:Other like Wi-Fi, OTG, baseband and etc.
How to install it:Step 0:
Bootloader unlock is required for every custom rom. You can use this tool for unlock:
https://drive.google.com/file/d/0B-Fin8UxrD6PWTZtR2VXX0dxcU0/view?usp=sharing
Step 1:
You should download files for flashing:
File with RR rom (Resurrection-Remix-LP-v5.5.8-20151024-a500cg.zip):
beta7.1
NOTE: RR builds for Zenfone 5 are compatible with Zenfone 6!
IMPORTANT: Do not forget to flash Xposed with RR Beta7.1. This way many issues (lags, memory bugs) will be solved.
OpenGapps: Download from Google Drive
XPOSED v78 : Download from Google Drive
ADB v1.0.32: Download from Google Drive
TWRP 2.8.7.0 recovery by quanganh2627 (new Decmber build): Download from Google Drive
Step 2:
1) Unpack archive with ADB and put TWRP image there.
2) Copy file with rom and gapps to internal/external memory of your phone.
3) Then you should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash recovery new-zen5-reco.img
Then you should reboot your phone in the recovery mode. (turn off you gadget then press Turn off button and volume - button)
Step 3:
Then you phone will reboot in the recovery. In the recovery you should instal two packages: Resurrection-Remix-LP-v5.5.7-20151012-a500cg.zip and gapps-L-x86-20150816-signed.zip.
NOTE: FlashResurrection-Remix-LP-v5.5.7-20151012-a500cg.zip file first.
Step 4:
After flashing, you should format (not wipe) data and cache in the TWRP.
Then you should reboot to system.
Bug reporting:Attach logcat and detailed describe the issue. Send this to quanganh2627:
http://forum.xda-developers.com/member.php?u=5392204
Credits:to @quanganh2627 @knoneNull @shakalaca and Hazouh
XDA:DevDB Information
Resurrection Remix V5.5.9 for Asus Zenfone 6 by quanganh2627 , ROM for all devices (see above for details)
Contributors
tank0412, dimdimdim
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: unlocked bootloader
Based On: CM 12.1
Version Information
Status: Beta
Current Beta Version: 7.1
Beta Release Date: 2015-12-06
Created 2015-10-18
Last Updated 2015-12-06
To fix camera, you should open build.a600cg.prop and copy all stuff from this file to build.prop file.
And what's wrong with camera? Mine works fine on 5.5.7 kernel 6.6
---------- Post added at 09:47 AM ---------- Previous post was at 09:45 AM ----------
Need help with Xposed. I've got boot loop with x86 sdk22 v74. Xposed for lollipop doesn't flash framework itself.
Okay, seems, the problem with Xposed is solved by flashing XPOSED X86 SDK22 v75 to 6.6 RT BETA http://forum.xda-developers.com/showthread.php?p=63396458#post63396458
some observations on beta with 6.5-6.6 kernels:
- touch freeze after call (system is still up, you can use your hard buttons to practice bringing volume panel and power menu up. by6the way, when I discussed xposed workability on zenfone 6 in my pms, one man mentioned he had same behavior within twrp recovery if flash zenfone 5 twrp on zenfone 6. IDK if this is in any way connected (anyway, we are flashing native zenfone 5 rom and recovery, so, everything is possible), but posting it here for devs, maybe it will bring them some ideas
- 6.6 kernel: burst mode on zenfone camera doesn't work. it starts working normally, but never stops and nothing saves. 6.5 seems works fine.
- Xanwars kernel v2(fixed lags) doesn't start second sim... Taking into account there is no raise in performance for me on this kernel (have no chance to test touch freezes after call due to a not working sim2) even though it allows overclock up to 2.2 and all the governors and schedulers are here.. Staying with beta 6.7 and 6.5 kernel
will update this. it's not a bug report with logcat yet as far as there is nobody here who develops for zenfone 6. yet, I hope.
ROM OS Version:*5.1.1 Lollipop
ROM Kernel:*Linux 3.10.20
Im still using beta6.6 without flashing x anwar kernel, i haven't encounter any lags and freezes, after first boot, reboot the device to twrp and try to install xposed v65,73,74 but it failed and finally succesfully installed on v75, so i think the best way after installing RR is to reboot the device 5 times after the first boot of installing RR. Then use it in 12 hours without installing anything like xposed, then observe and monitor on the performance.
Hajile caz said:
ROM OS Version:*5.1.1 Lollipop
ROM Kernel:*Linux 3.10.20
Im still using beta6.6 without flashing x anwar kernel, i haven't encounter any lags and freezes, after first boot, reboot the device to twrp and try to install xposed v65,73,74 but it failed and finally succesfully installed on v75, so i think the best way after installing RR is to reboot the device 5 times after the first boot of installing RR. Then use it in 12 hours without installing anything like xposed, then observe and monitor on the performance.
Click to expand...
Click to collapse
You don't have touch freezes after call on 6.6?
What about burst mode on asus camera? Does it work on your phone?
Which AnTuTu score do you get on 6.6?
Max what I saw on any kernel was 28900
Btw, dpi change on 6.2 kernel gives me boot loop. 6.7&6.5 both work fine.
I haven't experience freezing on calls, both incoming and outgoing calls, btw I have unlocked my bootloader from downgrading to Jellybean firmware and use the official unlocker tool from Asus.
My asus camera is working, burst mode is also working, After my first boot of RR, i have copy the a600cg build prod to both a501cg and the file build prop which i believe for a500cg, I also asked my friend, to share the media_profiles.xml from stock lollipop, and then i push it to system/etc and set permission to octal.
I have not try to flash the kernel from 6.2.
My antutu score when i was on 6.5 is 20k while after dirty flashing 6.6 it gave me 27k without flashing any kernel
My antutu score on beta6.6 without flashing any kernel
nice rom, so much faster i love it !!! recommend
my deepsleep not working at 6.7 i using 6.5 kernel and will try another
aymanz said:
nice rom, so much faster i love it !!! recommend
my deepsleep not working at 6.7 i using 6.5 kernel and will try another
Click to expand...
Click to collapse
I have not ever had any issues with deep sleep on any kernel and with no tricks or hacks. I believe it's because of some hick ups in old data or cache.
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
Hajile caz said:
I haven't experience freezing on calls, both incoming and outgoing calls, btw I have unlocked my bootloader from downgrading to Jellybean firmware and use the official unlocker tool from Asus.
My asus camera is working, burst mode is also working, After my first boot of RR, i have copy the a600cg build prod to both a501cg and the file build prop which i believe for a500cg, I also asked my friend, to share the media_profiles.xml from stock lollipop, and then i push it to system/etc and set permission to octal.
I have not try to flash the kernel from 6.2.
My antutu score when i was on 6.5 is 20k while after dirty flashing 6.6 it gave me 27k without flashing any kernel
Click to expand...
Click to collapse
So, you do believe most of the bugs come from the not completely proper bootloader unlock? If you know more details, that would be great if you can share, it's interesting.
dimdimdim said:
I have not ever had any issues with deep sleep on any kernel and with no tricks or hacks. I believe it's because of some hick ups in old data or cache.
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
So, you do believe most of the bugs come from the not completely proper bootloader unlock? If you know more details, that would be great if you can share, it's interesting.
Click to expand...
Click to collapse
In my own experience, I think that the best way to unlock the bootloader on our device is by using the official unlocker from Asus. Im always checking the forum here regarding RR, and i've noticed that the most mentioned topic is the screen freezes, which doesn't happen to me. Most of the users unlocked their BL from stock LP by flashing the dnx and ifwi files. And those users suffered from a massive lags and freezes. I have installed cm12.1 before i move to RR. When i was on cyanogenmod, i didn't experience any freezing issue. Due to my curiosity, i tried to downgrade to JB, then manual update to KK with bridge update then upgrade to LP. From stock LP, i flashed dnx and ifwi to unlock my Bootloader, then flashed cm12.1. After my first boot, im exploring my new installed rom, then suddenly my screen got frozen.
Hajile caz said:
In my own experience, I think that the best way to unlock the bootloader on our device is by using the official unlocker from Asus. Im always checking the forum here regarding RR, and i've noticed that the most mentioned topic is the screen freezes, which doesn't happen to me. Most of the users unlocked their BL from stock LP by flashing the dnx and ifwi files. And those users suffered from a massive lags and freezes. I have installed cm12.1 before i move to RR. When i was on cyanogenmod, i didn't experience any freezing issue. Due to my curiosity, i tried to downgrade to JB, then manual update to KK with bridge update then upgrade to LP. From stock LP, i flashed dnx and ifwi to unlock my Bootloader, then flashed cm12.1. After my first boot, im exploring my new installed rom, then suddenly my screen got frozen.
Click to expand...
Click to collapse
Do you think it will help for those, who have their bootloader unlocked unofficially, to lock it again and unlock with asus unlock?
I think it might be helpful for those devices that suffered from lags and freezes. Although it's a long process, but why not gave it a shot then, we all came this far.
beta 6.8 boots well http://forum.xda-developers.com/showpost.php?p=63457490&postcount=1918 on zenfone 6
first observations:
- no vibro (but this is common) -fixed the build from 24.10
- dpi change goes in some strange way: it works, but at starting apps point gets boot loop. anyway, you can break the loop forcing power off with hardware button at this point and bring it back to boot, which goes normally this way and never gets into the loop again after.
..still testing, got it in the night..
kloroform said:
thank you, downloading the ROM now, but my question is how stable is the ROM is now? Can I use all the ASUS apps with this ROM, the asus camera app mainly. Is it possible?
And can I come back to asus stock rom if I wish? I already made a backup, but a youtube channel guy on youtube told me few weeks back that it depends on the rom, he was talking about some odex-deodex thing. And if my ROM is odexed it wont boot even if I restore my stock rom backup on the same phone?
Click to expand...
Click to collapse
The rom is stable just as it is for zenfone 5. I'm using it after stock lollipop as a daily driver with hard use.
I don't know about every asus rom, but the developer includes the most usable asus apps in the rom. Remember, it's the resurrection rom for asus zenfone specifically?
The camera works fine. For me a burst mode doesn't work, but other people say it works well. I'd recommend to unlock bootloader with asus stock unlock tool in order to have less bugs.
From what I know you should go with dirty flash (no wipes before the flash process) over LP stock. See complete procedure in op.
If your rom is just stock with no modifications to the system, then it should flash fine from what I know.
But anyway, you do it all at your own risk, as always.
dimdimdim said:
The rom is stable just as it is for zenfone 5. I'm using it after stock lollipop as a daily driver with hard use.
I don't know about every asus rom, but the developer includes the most usable asus apps in the rom. Remember, it's the resurrection rom for asus zenfone specifically?
The camera works fine. For me a burst mode doesn't work, but other people say it works well. I'd recommend to unlock bootloader with asus stock unlock tool in order to have less bugs.
From what I know you should go with dirty flash (no wipes before the flash process) over LP stock. See complete procedure in op.
If your rom is just stock with no modifications to the system, then it should flash fine from what I know.
But anyway, you do it all at your own risk, as always.
Click to expand...
Click to collapse
thanks for answering my questions.
yes I have unlocked bootloader but not with the Asus's official tool. So, shall I use that tool to lock the bootloader again and then use Asus's unlock tool?
kloroform said:
thanks for answering my questions.
yes I have unlocked bootloader but not with the Asus's official tool. So, shall I use that tool to lock the bootloader again and then use Asus's unlock tool?
Click to expand...
Click to collapse
I'd like to help you, man, but I know nothing about bootloader unlock nuances on zenfone. Everything I know, I said: my burst mode on asus camera doesn't work and I have screen freezes with kernels older, than 6.2, and a man in this thread, you can check previous posts, has no these issues and he (and many others) believes it has connection to the bootloader unlock method.
Just be careful and make your decision, as playing with a bootloader lock/unlock with different tools could be dangerous. Remember, I know nothing about this.
@dimdimdim
I just dirty flashed RR 5.5.8, I have'nt flash a custom kernel, as I was confused which is the best kernel for this build, can you share which kernel did you flashed? Thanks
Hajile caz said:
@dimdimdim
I just dirty flashed RR 5.5.8, I have'nt flash a custom kernel, as I was confused which is the best kernel for this build, can you share which kernel did you flashed? Thanks
Click to expand...
Click to collapse
Hello, I'm using default one. Everything is ok with it for me, besides known bugs which are still here: screen freezes, gps, no screen rotation.
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
{
"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?
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??
nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11
walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64
Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.
Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.
Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash
{
"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