{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. This is a straightforward port of the device tree for flame (Pixel 4) to sunfish (Pixel 4a).
Downloads:
sunfish (Pixel 4a) rom (v2): https://mega.nz/file/zG4UVTQB#ZXLw_qULzC8-an-MEdxdAvUMhmIa5qLI6YG54Feh2z0
410b3f523795d9d1481d183309adb170 lineage_sunfish-qd3a.200805.001-rel-v2.zip
sunfish (Pixel 4a) rom (v1, broken, do not install): https://mega.nz/file/jXRB2a4B#a5Dcf9T6emWAwvAj3oFvofkI0la0zf7vj5KIMn-yQaM
MD5: 86743134c3032a030d35195d44f02e1b lineage_sunfish-qq3a.200805.001.zip
This is not a recovery-installable zip! Please read below for how to install this image
Prerequisites:
Like the TWRP build for this device, this ROM build is only known to be compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
Instructions:
1. Flash the vbmeta.img file in the included zip (fastboot flash vbmeta vbmeta.img)
2. Reboot into fastbootd (fastboot reboot fastboot)
3. Run fastboot update -w lineage_sunfish-qd3a.200805.001-v2.zip
(If you do not have a working fastbootd, extract boot.img from the update zip and flash it from the bootloader first)
Working:
- Camera
- Fingerprint
- Wi-Fi
- Bluetooth
- Sound
- Mobile data (tested with T-Mobile only)
Not tested:
- Google apps (should work fine, but you never know)
Changelog/Source Code:
sunfish device tree: https://github.com/liamwhite/android_device_google_sunfish
sunfish kernel tree: https://github.com/liamwhite/android_kernel_google_sunfish
Credits:
Many thanks to all LineageOS team members and all the contributors out there in the community.
Android version: 10
Kernel version: 4.14.117
Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?
just asking because that's how I flashed a lineage test build.
thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....
Edmontonchef said:
Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?
just asking because that's how I flashed a lineage test build.
Click to expand...
Click to collapse
posıtıve said:
thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....
Click to expand...
Click to collapse
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.
liamwhite said:
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.
Click to expand...
Click to collapse
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?
TheSayaMan said:
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?
Click to expand...
Click to collapse
I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.
TheSayaMan said:
I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.
Click to expand...
Click to collapse
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.
I added a MD5 of the zip image I flashed to the OP.
liamwhite said:
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.
I added a MD5 of the zip image I flashed to the OP.
Click to expand...
Click to collapse
I'm sure it's not broken. Probably a issue with my phone. I'm getting a error in the bootloader about debug policy enabled, not in list. I know that's not normal because my wife has the same phone and hers doesn't say that. And I have no idea what or how to change verity. My bootloader is unlocked.
Same error here, getting corrupt error then it sticks to google logo
nixromancer said:
Same error here, getting corrupt error then it sticks to google logo
Click to expand...
Click to collapse
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.
TheSayaMan said:
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.
Click to expand...
Click to collapse
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.
Board: sunfish MP1.0(NA)
Bootloader: s5-0.2-6539975
Baseband: g7150-00018-200701-B-6643937
Secure boot: PRODUCTION
NOS production: yes
liamwhite said:
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.
Click to expand...
Click to collapse
any idea how to check if verity is enforcing and how to change it. Did a search, can't find anything.
Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.
liamwhite said:
Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.
Click to expand...
Click to collapse
Your going completly around what I asked. I'm done with this. Moving to another thread.
Stay away from this, it changes your file system to raw and is a complete waste of time.
I rebuilt my entire source tree, reflashed the Pixel system images and reproduced the corrupt device warning. Picking through the changes, it didn't work because I had inadvertently flashed vbmeta.img on my build but not included it in the zip. I've posted an updated version of the zip and provided new instructions for how to flash this, because Lineage's fastboot does not allow flashing the vbmeta partition (you have to first flash it from the bootloader).
I tested again with a clean wipe, reset to Pixel factory image QD4A.200805.003 and this time it worked without a problem. The android-info.txt will now ensure that you are using the right bootloader when flashing, so that issue should go away too.
Cool I'll give it a try tomorrow
TheSayaMan said:
Stay away from this, it changes your file system to raw and is a complete waste of time.
Click to expand...
Click to collapse
What does this mean
nixromancer said:
Cool I'll give it a try tomorrow
What does this mean
Click to expand...
Click to collapse
This doesn't work. That's what it means. If you want to waste about an hour of your life flashing this then having to flash back to stock or another custom rom than be my guest. This was posted by a new member, not a developer at all. I messed around with this quite awhile and no one is reporting success except the one that started this thread.
TheSayaMan said:
This doesn't work. That's what it means. If you want to waste about an hour of your life flashing this then having to flash back to stock or another custom rom than be my guest. This was posted by a new member, not a developer at all. I messed around with this quite awhile and no one is reporting success except the one that started this thread.
Click to expand...
Click to collapse
The fact that I messed up and didn't realize I had to include the vbmeta.img file in the first zip is my fault, and I totally own that. It isn't able to be flashed in Lineage's fastbootd ("file not found", presumably it's missing a devfs node) so I accidentally excluded it from the image I shipped, not realizing it was mandatory.
Yes, I'm new to this forum, but I'm not new to building Lineage and I've done it many times before. I have serial UARTs for my phones. I'm posting this build here because I'm excited to be the first to get stable lineage running on the 4a, with the full list of vendor blobs and such (see my posted device tree), and this is the first time I've ported Lineage to a new board. It took me a week of tiring work bootstrapping the board, getting the first serial output, getting into recovery, and then finally figuring out that the kernel modules were missing before getting a full boot.
I was annoyed that the flashable zip generated by mka bacon doesn't include the required modules, and in my testing applying it never worked (they were always excluded from the vendor parition, even after multiple makefile changes), which is why I decided to make an ad-hoc flash method using a fastboot update zip, which reliably worked. That was the primary source of the error here. I won't make that mistake again.
I know you're frustrated that the first image I provided didn't work, but I have looked into it, reproduced your issue, and fixed it (and it ironically was only missing one 4K file needed to make it work).
Related
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
A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"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"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.
Now I wish I can unroot my phone, lol
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?
You can extract recovery.img from the ColorOS zip.
If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you
MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)
Deleted
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota
wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?
Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader
wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23
How to re install the original recovery :crying:
{
"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?
This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll notice updates come without it for Global or on their Global support site, the firmware is outdated.
- On T-Mobile have full 5G. I don't know about AT&T and Verizon. Should be same.
If you are on Global and you just received your phone. Do all the updates from the incremental through device. If you want root, you can flash with the EU patched boot.img and everything will work as normal
**** but once you do this, you will need to wait for Global full OTA to update next time, unless you managed to have a backup copy of the unpatched boot.img
Do the usual to unlock your OnePlus 9: oem unlock, usb debugging from developer. Boot into bootloader and use adb command /fastboot flashing unlock
This will wipe your phone and reboot. Setup your phone
Install Magisk from his official github: https://github.com/topjohnwu/Magisk/releases/tag/v22.0
- Topjohn provides full instructions on how to do this yourself as well.
Reboot into bootloader
Flash boot the magisk modified boot.img. /fastboost flash boot boot.img
Go into Magisk app and install via direct install and all done.
Return to stock
- Restore boot.img from Magisk
- Uninstall Magisk
- Flash the stock boot.img
- Relock the bootloader, will wipe and return to factory reset.
Stock 11.2.33 Boot.img
boot11233_stock.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Magisk Patched 11.2.33 boot.img
boot11233_patched.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Spoiler: Previous Boot Images
Patched Boot.img for Europe (11.2.2.2.LE25DA)
boot93.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Stock Boot.img for Europe (11.2.2.2.LE25DA)
boot.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Future Full OTA Updates
- Update as usual
- Go into Magisk and choose direct install and then install to inactive slot after OTA
- This will retain root
How to do it yourself:
Download full OTA, usually Oxygen Updater App, XDA has links or from https://www.oneplus.com/support/softwareupgrade
Download Payload Dumper
payload_dumper-win64.zip | Tool by geminids14 for Utilities
Extract payload.bin in xiaomi weekly build zip for MI A1
androidfilehost.com
Extract and place payload.bin in input folder
{
"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"
}
Run the payload_dumper.exe
In the output folder will be boot.img, move that onto your phone, folder of your choice
Go to Magisk app, click install
Choose Select and Patch a File
Choose the file and it will patch it, Magisk will say where the file is located.
That is your patched boot.img file. Use that to flash / root your phone.
Remember only have do this once, you don't have to do this again with subsequent updates.
zymphad said:
Do the usual to unlock your OnePlus 9: oem unlock, usb debugging from developer. Boot into bootloader and use adb command /fastboot flashing unlock
This will wipe your phone and reboot. Setup your phone
Install Magisk from his official github: https://github.com/topjohnwu/Magisk/releases/tag/v22.0
Reboot into bootloader
Flash boot the magisk modified boot.img. /fastboost flash boot boot.img
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Go into Magisk app and install via direct install and all done.
Click to expand...
Click to collapse
What version/region of the OP9 is this boot.img for? Where did you get the original unmodified one? I need Canadian.
Slikkster2k said:
What version/region of the OP9 is this boot.img for? Where did you get the original unmodified one? I need Canadian.
Click to expand...
Click to collapse
So there seems to be confusion about version. The boot image doesn't matter. When you flash a custom rom, there isn't a EU or US version. The only difference I can think of if it's T-Mobile, so when you flash, then it would just be an international/global. This is from XDA.
Honestly I would bet the Indian version is same as well.
This is the EU, which is the same boot.img for US unlocked.
If the future you should be able to do this yourself once OnePlus adds the 9 series to their global firmware downloads list.
Good to know, thanks! I'm not planning to flash a custom rom, I just want root. So I just have to make sure the bootloader is unlocked, and then follow the steps for Magisk.
Yep, working great here. Mobile payments working fine. Using energized for adblock.
So I successfully rooted yesterday, all is working great. Today my phone prompts me that system update 11.2.1.1 is available. Of course, I cannot upgrade while rooted. However, I also can't restore my stock boot.img because I don't have a copy of it... Any way to update without doing a factory reset, or am I screwed?
Edit: From what I've found, factory reset doesn't touch the boot partition. So that won't help.
This method worked for me, though I'm now running the same issue as Slikkster2k, since I don't have an unpatched boot.img, I can't uninstall magisk to update via OTA.
I would suggest, for those wanting to be able to update in the future (until we get a custom recovery), that instead of /fastboot flash boot boot.img, use /fastboot boot boot.img and then let Magisk finish the install. When Magisk patches the boot image, it will take a backup of the stock one to be used for uninstallation.
Slikkster2k said:
So I successfully rooted yesterday, all is working great. Today my phone prompts me that system update 11.2.1.1 is available. Of course, I cannot upgrade while rooted. However, I also can't restore my stock boot.img because I don't have a copy of it... Any way to update without doing a factory reset, or am I screwed?
Click to expand...
Click to collapse
Install magisk module-a/b install-before you reboot, then select direct install to second slot and reboot. Works beautifully.
[email protected] said:
Install magisk module-a/b install-before you reboot, then select direct install to second slot and reboot. Works beautifully.
Click to expand...
Click to collapse
I can't install the OTA update at all -- I'm on global ROM, so it fails because it's attempting a partial OTA update, rather than flashing a full ROM.
@zymphad
Do you also have a copy of the unpatched boot.img file?
Slikkster2k said:
I can't install the OTA update at all -- I'm on global ROM, so it fails because it's attempting a partial OTA update, rather than flashing a full ROM.
Click to expand...
Click to collapse
With rooted phone you need to do full not partial.
We are on the February security update. The latest update for OP9 is still on it, so disappointing.
We have to wait until the March security update that is already out for other oneplus devices.
You can unroot and re-lock your bootloader and then install the partial and then do the whole process again. I am not going to do that, seems waste of time.
Uninstall Magisk -- Flash stock boot.img -- lock bootloader.
This will wipe your phone back to factory reset!!!
But I expect we will see March update soon since Nord and 8 series have them already.
zymphad said:
With rooted phone you need to do full not partial.
We are on the February security update. The latest update for OP9 is still on it, so disappointing.
We have to wait until the March security update that is already out for other oneplus devices.
You can unroot and re-lock your bootloader and then install the partial and then do the whole process again. I am not going to do that, seems waste of time.
Uninstall Magisk -- Flash stock boot.img -- lock bootloader.
This will wipe your phone back to factory reset!!!
But I expect we will see March update soon since Nord and 8 series have them already.
Click to expand...
Click to collapse
The issue is that even if we wanted to do this, Slikkster2k and I (and possibly others), don't have the stock boot.img, since we flashed the magisk patched boot.img directly. Since you provided the patched boot.img originally, do you have the unpatched version available?
That way if anyone still on the original version that came pre-loaded wants to flash back to fully stock (and maybe re-lock bootloader) they can.
Those of us on the Global/US variant (AA) don't have the full zip available, and since we can't flash incremental while rooted, we currently have no way of actually reverting to stock until OnePlus publishes the full ROM zip.
Will post the stock.
I mean dunno why would want to since to do the incremental think have to relock bootloader which would factory reset.
And the to root again would factory reset again...
The March security update is already out for Nord and 8 series. Would just wait.
The incremental is still the Feb security update which you are already on.
Thanks, I mostly just wanted to redo the root process, but use /fastboot boot boot.img instead of /fastboot flash boot boot.img, so that magisk has a backup of the stock bootloader. That way, if for some reason I need to flash back to stock before the March Security update comes out, I can do so from my phone without needing my PC.
zymphad said:
I mean dunno why would want to since to do the incremental think have to relock bootloader which would factory reset.
Click to expand...
Click to collapse
Ah, was not aware of that. In that case we'll just have to wait, hopefully OnePlus posts it soon.
Besides, the patched bootloader you posted is from 11.2.1.1 (I compared the hash to the one in the other thread), so I assume the stock image is the same. So it's no good to us anyways.
Slikkster2k said:
Besides, the patched bootloader you posted is from 11.2.1.1 (I compared the hash to the one in the other thread), so I assume the stock image is the same. So it's no good to us anyways.
Click to expand...
Click to collapse
Ahh, I didn't realize that, I guess it's just a good thing that the 11.2.1.1 boot.img doesn't cause any issues when flashed onto 11.2, since we would have had no way to undo it
reffu said:
Ahh, I didn't realize that, I guess it's just a good thing that the 11.2.1.1 boot.img doesn't cause any issues when flashed onto 11.2, since we would have had no way to undo it
Click to expand...
Click to collapse
Actually I tested it using fastboot boot boot.img before I flashed it, just to make sure it would work (I didn't know it was from 11.2.1.1 at the time, but I'm paranoid).
Seems the rest of the world is getting the March update except US again. Still no full package, and this time not even partial. Dunno what is going on with OnePlus and US, but it's annoying.
Will update for EU AB firmware in the OP. And then put disclaimer for Global to do all their updates prior to rooting.
{
"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