{
"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"
}
Mostly copied from @asineth
Disclaimer: You decided to flash your phone. I'm not responsible for bricking phone or data loss.
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.
Downloads:
Ziped images for suggested install:
lineage-17.1-20210329-UNOFFICIAL-sofiar-images.zip
sha256sum: c57d69ade235f5c76c6eea038ad29f81e522ef713ea00b89c10010a52d6cf17f
Build for TWRP/sideload:
lineage-17.1-20210427-UNOFFICIAL-sofiar.zip
sha256sum: 9c2ada552cdb3ea29ffe63f175fe514daae429c1a727cd41a574e46e97f9ffe9
lineage-17.1-20210329-UNOFFICIAL-sofiar.zip
sha256sum: dae9ec116de163a46efea1a1316a86dfdffda625cc568109c268f255722134e4
Lineage 18.1 - not tested:
https://mega.nz/file/8gonBIgD#6Kon0qwOZS8WdrUAgQqAPJjO7qy1tDiKcua_EMjHYOA
Last updated: 2021.04.27
This ROM includes:
FDroid
FDroidPrivilegedExtension
Flashing:I recommend GNU/Linux for this.
1. Flash TWRP
2. Extract the zip and open a shell with ADB and fastboot.
3. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
4. Flash boot, system, product, and vbmeta.
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
4. Wipe userdata.
5CODE]fastboot -w[/CODE]
If you are on the Moto G8/G Fast and your display cutout is misbehaving, enable your overlay like so:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
Update:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Working:
Display
Touchscreen
Wi-Fi
Bluetooth (including audio)
Headphones via 3.5mm
Internal Speaker
Moto Actions
Calls/SMS/LTE/VoLTE on Verizon
GPS
Notification LED
Hotspot
Bugs:
After turning hotspot off, phone reboots
Inbuild screen recording app broken, phone reboots
Source:
LineageOS
Device tree
Vendor tree
Kernel tree
Telegram:
https://t.me/MotoG8Official
Credits:
@Vachounet - helped a lot, original device/vendor tree, TWRP build
@kjjjnob - some LineageOS changes to @Vachounet's tree
@asineth
LOS team
XDADevDB Information
[ROM][RAV*/SOFIA*][10][UNOFFICIAL] LineageOS 17.1, ROM for the Moto G Power
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: stable
Created 2021.03.15
Last Updated 2021.04.27
I downloaded and installed this yesterday. So far, I haven't encountered any issues or found anything that doesn't work. Good job!!!!
tcaudill01 said:
I downloaded and installed this yesterday. So far, I haven't encountered any issues or found anything that doesn't work. Good job!!!!
Click to expand...
Click to collapse
Cool, thanks for info!
Did you just dirty updated or wiped?
sifrax said:
Cool, thanks for info!
Did you just dirty updated or wiped?
Click to expand...
Click to collapse
I always use the recovery program and go all the way back to stock before installing a ROM. It takes more time and is more complicated that way but if I encounter a problem, I know it's the new ROM and not carryover garbage from the old one.
So far, everything is working. VoLTE, GPS, QS Tiles, etc. Battery life seems good. Performance is good. No crashes or reboots.
Seems to be solid.
Thank you. Your work and efforts are appreciated.
I'm gonna dirty flash on top of the dpcioc build from the previous thread. I had to wipe data to get that one to boot coming from the asineth build. I'll let you know what happens.
EDIT: Doesn't work. lol
Hi I'm new to custom roms. What is the difference between the first zip file with images and the 2nd zip file on this post? Thanks!
Never mind. I posted my question before the files downloaded and clearly see the differences afterwards.
Update: Great success!!! Had 0 issues installing this. Thank you for the code as well!
I finally tried to install. Dirty flash over asineth's LOS 17.1.
Sideload did not worked phone rebooted and entered into TWRP. So I tried flashing from fastboot and that worked. I lost apps, but it remebered my PIN.
I have only one issue - hotspot works, but when I turn it off, phone reboots.
sifrax said:
I finally tried to install. Dirty flash over asineth's LOS 17.1.
Sideload did not worked phone rebooted and entered into TWRP. So I tried flashing from fastboot and that worked. I lost apps, but it remebered my PIN.
I have only one issue - hotspot works, but when I turn it off, phone reboots.
Click to expand...
Click to collapse
I never use hotspot so I hadn't checked it out. I tried it and my phone reacts the same way as yours does.
SO as I understand there is no need a computer for this
SO this my very first time doing this and just wanted to be clear do I or do I not need a computer
Aasdnivj said:
SO this my very first time doing this and just wanted to be clear do I or do I not need a computer
Click to expand...
Click to collapse
Even though if you have unlocked phone I'd still recommend use computer and first zip with images.
New build 2021-03-25
https://mega.nz/file/VopiVQST#bAJQ2-3hI-LbED2uPoCXoEEA0HoyGw0h50ESr7H3A4A
SHA256: d2c474b5d0ec40ad0f807e0a3dc2c0fbfabfa7fe04bc8c0243ce72b8faadfc9b
sifrax said:
New build 2021-03-25
https://mega.nz/file/VopiVQST#bAJQ2-3hI-LbED2uPoCXoEEA0HoyGw0h50ESr7H3A4A
SHA256: d2c474b5d0ec40ad0f807e0a3dc2c0fbfabfa7fe04bc8c0243ce72b8faadfc9b
Click to expand...
Click to collapse
Just installed today right before you posted this new build! Its working so far, thank you! Whats new in the build?
Banana_sam said:
Just installed today right before you posted this new build! Its working so far, thank you! Whats new in the build?
Click to expand...
Click to collapse
Hi, it's just updaed LOS. Nothing regarding device.
I'll try to merge github repos with some updated and then buid new version later.
sifrax said:
Downloads:
Ziped images for suggested install:
https://mega.nz/file/VopiVQST#bAJQ2-3hI-LbED2uPoCXoEEA0HoyGw0h50ESr7H3A4ASHA256: d2c474b5d0ec40ad0f807e0a3dc2c0fbfabfa7fe04bc8c0243ce72b8faadfc9b
lineage-17.1-20210315-UNOFFICIAL-sofiar-images.zip
uloz.to
SHA256: b8708803104fa831490255fc0c7e3fb0fd5cee9934d0d402e761b73648c42ab4
Build for TWRP/sideload:
520.91 MB file on MEGA
mega.nz
SHA256: 04d8417608166dadb3276725d032167ce702bdc8621065c7129b44508abd0f9c
lineage-17.1-20210315-UNOFFICIAL-sofiar.zip
ulozto.net
SHA256: 895a0e088d3bd9ba93ed29a4b04dbc8c77bb2d3f61aa9313fa6207e91dc90a76
Last updated: 2021.03.25
Click to expand...
Click to collapse
No idea how these files differ, which one do I use or how.
sifrax said:
This ROM includes:
FDroid
FDroidPrivilegedExtension
Click to expand...
Click to collapse
No idea what this means or why is it important and listed as second most important paragraph.
sifrax said:
Flashing:
1. Extract the zip and open a shell with ADB and fastboot.
Click to expand...
Click to collapse
Don't know what that means.
sifrax said:
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
Click to expand...
Click to collapse
Don't know what `fastbootd` mode is.
sifrax said:
3. Flash boot, system, product, and vbmeta.
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Doesn't work, after reboot the command line says "waiting for any devices". Can't continue.
Every year I try some Android device and venture to XDA to try some custom ROMs. It never works.
mcsoap said:
No idea how these files differ, which one do I use or how.
No idea what this means or why is it important and listed as second most important paragraph.
Don't know what that means.
Don't know what `fastbootd` mode is.
Doesn't work, after reboot the command line says "waiting for any devices". Can't continue.
Every year I try some Android device and venture to XDA to try some custom ROMs. It never works.
Click to expand...
Click to collapse
This is a very stable and well presented ROM. It is also very easy to install.
I'm not trying to be a ****, but with all the questions you have, you obviously have no idea what you are doing! If other people are successfully installing and using a ROM and you can't, the problem is not the ROM.
For starters, is your bootloader unlocked? If not, you need to do that before trying anything. If you don't know how, use search.
Most of your answers are here
"Moto G Power Guides, News, & Discussion"Do your homework first and read everything you can.
So after a few days everything still seems really good. One flaw I've just realized is that screen recorder doesn't work and forces the phone to restart after launching.
Not really a deal breaker for me since I very rarely use the app and its not really necessary for my purposes. Just thought I'd test it out, since I think I remember seeing in another thread here how this was happening with another custom rom for this device
Banana_sam said:
So after a few days everything still seems really good. One flaw I've just realized is that screen recorder doesn't work and forces the phone to restart after launching.
Not really a deal breaker for me since I very rarely use the app and its not really necessary for my purposes. Just thought I'd test it out, since I think I remember seeing in another thread here how this was happening with another custom rom for this device
Click to expand...
Click to collapse
This is true. The ones from the play store will work.
Banana_sam said:
So after a few days everything still seems really good. One flaw I've just realized is that screen recorder doesn't work and forces the phone to restart after launching.
Not really a deal breaker for me since I very rarely use the app and its not really necessary for my purposes. Just thought I'd test it out, since I think I remember seeing in another thread here how this was happening with another custom rom for this device
Click to expand...
Click to collapse
OK, thanks for information. I can verify that the bug is there, it restarted.
I merged github repos with some more updated (Odin1101) and it's compiling.
mcsoap said:
No idea how these files differ, which one do I use or how.
No idea what this means or why is it important and listed as second most important paragraph.
Don't know what that means.
Don't know what `fastbootd` mode is.
Doesn't work, after reboot the command line says "waiting for any devices". Can't continue.
Every year I try some Android device and venture to XDA to try some custom ROMs. It never works.
Click to expand...
Click to collapse
Sorry to hear, but you know as it was suggested to you - try to study a little bit more before. Hope you can make it next time.
Related
{
"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"
}
Enjoy Your Asus Zenwatch 3-Swift-AND-FEEL THE SPEED
Please read the instructions and notes before flashing anything.
Code:
###Disclaimer###
I am not responsible if your phone will be damaged, broken, boot looping. YOU are choosing to make these modification.
WARNING:
IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS.
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE ME HERE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
Requirements
- An unlocked bootloader
- adb and fastboot drivers
- TWRP recovery
You can download adb and fastboot package from here. https://developer.android.com/studio/releases/platform-tools.html#download
--------------------
HOW TO FLASH THE ROM
0- Attach your devices to your PC and enable USB Debugging
1- Boot your device with TWRP from
Custom-TWRP-thanks to @Maxr1998
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot boot name-of-the-twrp.img
Or
fastboot flash recovery name-of-the-twrp.img
2- Now move the build/ROM to your watch
3- Make a backup - there's always 1% chance something goes wrong.
4- Full wipe is recommended....Wipe data/Factory reset
5- Flash the ROM
6- Reboot
7- Setup your initial settings
8- GO TO MY KERNEL THREAD AND DOWNLOAD THE LATEST VERSION AND FLASH THAT.
9- Done
--------------------
HOW TO ACHIEVE ROOT
- Reboot into TWRP
- Copy the root-wear.zip (ROOT AND BUSYBOX_1.5_AND_2.0) package inside your device
- Flash the root-wear. zip and reboot
- Open busybox and install
- Done
--------------------
HOW TO ACHIEVE ROOT AFTER FLASHING THE NEW BOOT IMAGES
- DOWNLOAD THE LATEST VERSION FROM (KERNEL THREAD)
- Reboot into TWRP
- Flash the new kernel and reboot
- Complete your device setup
- Reboot into TWRP again
- Flash root-wear.zip (ROOT AND BUSYBOX_1.5_AND_2.0) package
- Reboot
- Open busybox and install
- Done
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
KERNEL/BOOT IAMGES FOR LATEST UPDATE
-NOTE: YOU NEED TO FLASH THE ROM FIRST (Setup your initial settings) AND THEN FLASH THE LATEST KERNEL FROM KERNEL THREAD
ROMs-ANDROID_WEAR_2.0 [DEODEXED][ODEXED] [LATEST]
Short changelog-[DEODEXED] [27/8/2018]
- Based on latest release NWD1.170623.001- June_1_2017 security patch
- Kernel is compiled with LINARO GCC: 4.9.4-Optimized/based on latest available source 3.18.24 Kernel
- All *apk system/data, system/app, Framework & priv-app zipalign & optimized for better RAM utilization
- Can be root - Flash the following Root/BusyBox if you want to achieve root access.
- dm-verity disabled
- forced-encryption disabled
- SELinux permissive
- init.d script support
- Tweaked for Best Performance
- adb is enabled by default
- Update script
- Tweaks to achieve better battery life
- Clean
------------------------------------------------------------
Download-Link [LATEST-27/8/2018]
BUILD_WEAR_2.0 [DEODEXED] /ROM
MD5:0ceb5c2c3261cb0026b1365940efc839
------------------------------------------------------------
BUILD_WEAR_2.0 [ODEXED] /ROM
MD5:131ab240ec04f8a5ecbf7acb6d42ad51
------------------------------------------------------------
Download-Link
ROOT AND BUSYBOX_1.5_AND_2.0
------------------------------------------------------------
------------------------------------------------------------
ROMs-MWG68_ANDROID_WEAR_1.5
Download-Link
Deodexed/ROM
MD5:3913568ed1d59d90340962b24a3a46b7
Odexed/ROM
MD5:ee3dbf24fcc19a713ddcf819e24c43bb
----------------------
Kernel Source
https://github.com/toffyjan/Asus-zenwatch-3-kernel
----------------------
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF COFFEE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE ME HERE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE-HEREhttps://www.paypal.me/JANJANXDA
paypal.me/JANJANXDA
----------------------
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Chainfire for great work in android
@Maxr1998 thanks for script and twrp recovery
@superR for the kitchen
@Captain_Throwback
@SuperThomasLab for great tools
-Take a look here. And support the dev.
@Xmaster24 for system-less root-
Willi Ye for his great app
-Take a look here. And buy the donate version to support the dev.
Please always support devs and others (soon).
Thanks! What's the decryption key? Apparently I need that to download.
ups gonna fix it soon.
go gO
You meant to flash this with TWRP, right? I did that and did a wiped it (factory reset in TWRP). Seems to hang at the ASUS IN SEARCH OF INCREDIBLE loading screen. Could just be my watch of course.
jobarr said:
You meant to flash this with TWRP, right? I did that and did a wiped it (factory reset in TWRP). Seems to hang at the ASUS IN SEARCH OF INCREDIBLE loading screen. Could just be my watch of course.
Click to expand...
Click to collapse
Offcourse flashing with TWRP..You need to wipe your data too. And fast boot takes some time. 5-10 minutes. I tested on two watches and it works. Be patient
I removed boot animation so that is why see only Google with capital letters. It make the boot process a bit faster.
@janjan Nice one!
Will try it out asap. Just a small tip, could you rebase your kernel onto the swift branch of the kernel-msm repo on android.googlesource.com? That way, the commit history isn't lost and we can see all the changes you made (and improve on them as well). Precondition of course is that the repo already contains the latest MWF76 sources, I didn't check that yet. But if yes, you could just clone it, and drop the .git folder into your kernel folder, verify all is fine and commit the changes.
janjan said:
I removed boot animation so that is why see only Google with capital letters. It make the boot process a bit faster.
Click to expand...
Click to collapse
You mean splash, don't you? Did you just wipe it with zeroes or how did you do it?
After 10 minutes I still only see "ASUS IN SEARCH OF INCREDIBLE". It never even shows "Google".
jobarr said:
After 10 minutes I still only see "ASUS IN SEARCH OF INCREDIBLE". It never even shows "Google".
Click to expand...
Click to collapse
Tell me what you did. You procedure please.
Booted TWRP via "fastboot boot recovery.img"
Flashed your zip
Wiped Dalvik/cache/data
Rebooted
jobarr said:
Booted TWRP via "fastboot boot recovery.img"
Flashed your zip
Wiped Dalvik/cache/data
Rebooted
Click to expand...
Click to collapse
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Maxr1998 said:
@janjan Nice one!
Will try it out asap. Just a small tip, could you rebase your kernel onto the swift branch of the kernel-msm repo on android.googlesource.com? That way, the commit history isn't lost and we can see all the changes you made (and improve on them as well). Precondition of course is that the repo already contains the latest MWF76 sources, I didn't check that yet. But if yes, you could just clone it, and drop the .git folder into your kernel folder, verify all is fine and commit the changes.
You mean splash, don't you? Did you just wipe it with zeroes or how did you do it?
Click to expand...
Click to collapse
I will check it out. need to prepare my self for my exam ..I try to
janjan said:
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Click to expand...
Click to collapse
Yes. Ahhh....ok, lemme try that.
janjan said:
I will check it out. need to prepare my self for my exam ..I try to
Click to expand...
Click to collapse
Sure, school's always first. Good luck in your exam!
Maxr1998 said:
Sure, school's always first. Good luck in your exam!
Click to expand...
Click to collapse
Thank you. I didn't add too much right now. But we will do that. My last exam in wireless communication.
janjan said:
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Click to expand...
Click to collapse
It still won't leave the ASUS screen after 5 minutes. :/
jobarr said:
It still won't leave the ASUS screen after 5 minutes. :/
Click to expand...
Click to collapse
Try to flash the kernel after flash the build. Or
Flash the root after flashing the build or
Wipe everything also your system and then flash the ROM. You have to wipe everything.
I just test again and it seems working without and issue
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
jobarr said:
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
Click to expand...
Click to collapse
Sounds like the best idea to me actually.. @janjan, didn't you also flash my extracted boot image with fastboot before?
jobarr said:
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
Click to expand...
Click to collapse
jobarr said:
Thanks! What's the decryption key? Apparently I need that to download.
Click to expand...
Click to collapse
Maxr1998 said:
Sounds like the best idea to me actually.. @janjan, didn't you also flash my extracted boot image with fastboot before?
Click to expand...
Click to collapse
Yes I did. But actually It could be a good idea for @jobarr to try it out. I will suggest him to flash your extracted boot image and your system.img and then flash my kernel or my build.
It seems any modification or even by booting into twrp and allow modification causes boot loop and rebooting every 30 seconds. It is due to dm-verity stock kernel feature which provides integrity checking of block devices Or STATE CHECKING. I had the same issue with boot loop and then fixed the issue by flashing my build + kernel.
janjan said:
Yes I did. But actually It could be a good idea for @jobarr to try it out. I will suggest him to flash your extracted boot image and your system.img and then flash my kernel or my build.
It seems any modification or even by booting into twrp and allow modification causes boot loop and rebooting every 30 seconds. It is due to dm-verity stock kernel feature which provides integrity checking of block devices Or STATE CHECKING. I had the same issue with boot loop and then fixed the issue by flashing my build + kernel.
Click to expand...
Click to collapse
Yeah, dm-verity is a pain.. Shouldn't SuperSu also patch dm-verity? Might be worth a try as well.
Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.
Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.
{
"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"
}
carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!
links not works
vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.
Thank you very much
Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one
Install global via fastboot, all is included or in qfil ROM is all in zip file
vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again
i tired and failed again
galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it
hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?
galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot
{
"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"
}
" #DroidOnTime "
ROM Version: 5.2.1
Device: OnePlus Nord N10 5G [billie]
Maintainer: @kronflux
Build Status: UNOFFICIAL
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
1. Download the ROM and Recovery image
2. Boot into bootloader/fastboot mode
* adb reboot bootloader
3. Flash the Recovery image
* fastboot flash recovery recovery.img
4. Boot into Recovery
* fastboot reboot-recovery
5. Perform a Factory Reset/Wipe in Recovery
6. Go to Apply Update and choose Apply from ADB
7. Sideload the ROM
* adb sideload rom.zip
Reboot and voila!
ROM [VANILLA]: https://www.androidfilehost.com/?fid=2981970449027577449
MD5: F852EB929ED7DA566EBC0F291678CB6A
SHA-1: 3CD283C4AA9AF0B4290261BD3F19D5DED0DD947F
ROM [WITH GAPPS]: https://www.androidfilehost.com/?fid=2981970449027577450
MD5: 14F7938C0982CC0749FC160F412453B6
SHA-1: BFD74BC13CBF2AA69ABA9ACB45D44E5B70BBFAC8
*NOTE: dotOS Recovery not currently working properly, included PixelExperience recovery in the meantime, which will work fine*
RECOVERY: https://www.androidfilehost.com/?fid=2981970449027577417
MD5: BFE3114F2A966E03CFD0CF6C0040146B
SHA-1: B14B3102C97C15E3C7C045182489514C0827713F
In case you need it for magisk or any other reason, here's the boot image as well:
BOOT IMAGE: https://www.androidfilehost.com/?fid=2981970449027577448
MD5: EAD909E81843EAB13E1DA1FA95B0FEBB
SHA-1: 81CC6D595C1802E9E839408CB717BCB62C40289B
Complete Changelogs: https://changelogs.droidontime.com/
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Important Links
dot OS source
Telegram Channel
Website
REPORTING BUGS !
As soon as the problem occurs, take a LOGCAT!
for more READ THIS
Contributors: @iamsaalim, @kronflux
Source Code: https://github.com/DotOS
Device Sources: - https://github.com/kronflux/device_oneplus_billie
Kernel Sources: - https://github.com/danascape/kernel_oneplus_sm6350
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.2.1
Stable Release Date: 27-01-2022
Last Updated: 21-03-2022
ROM Firmware Required: OxygenOS 11.x
ROM Kernel: 4.19.125
Nice work!
Can this be flashed with twrp?
Thrilled to see this! Any known issues like DTW and/or Adaptive Brightness not working? Or no known issues at this point?
First of all thank you for this amazing ROM! I noticed that Bluetooth audio works fine but when you plug in headsets/headphones they still produce sounds from the speakers and not the headphones/headsets. WiFi is also a tad bit weak so I transitioned to ArrowOS. Thank you again for the good work. I appreciate it!
heyho i have a few questions about this rom. Is it possible to install a own gapps packet like the pico variant? If yes which one should i use? Arm64/Android 11/Pico is this the right package?
Whats about root can i flash magisk for rooting?
Andariyel said:
heyho i have a few questions about this rom. Is it possible to install a own gapps packet like the pico variant? If yes which one should i use? Arm64/Android 11/Pico is this the right package?
Whats about root can i flash magisk for rooting?
Click to expand...
Click to collapse
I am not sure about the gapps, but as for the rooting Magisk works for me just fine.
I'm new to all this, so I hope I do this right, but I bought this phone specifically to be a 5G hotspot, and OnePlus disabled 5G after Android 11 update.
I'm on build number 11.0.3.BE89BA, so EU model, and before I take the plunge into installing custom ROM for the first time since I owned an LG G3 like 7 years ago, I'd like to at least confirm this will work on my build and it will re-enable 5G.
Thank you for answering, and if you have any extra tips or info how to make it as easy as possible, I'd be grateful.
EDIT: I've followed the instructions to the best of my understanding, and it gets stuck at 47%, which I've heard is normal, but I always reboot into stock firmware. I tried it at least 5 times so far, even following Youtube videos (different OnePlus phones on YT though), but the result is always the same. Instructions say nothing about TWRP, but can I maybe try that way?
@wanamy thx for your reply good to read. For gapps i google it and from what i read on other phones with dotos it works flashing after the Dotos. So i guess it should be okay. Will try it at the weekend when i have time.
Sophos437 said:
I'm new to all this, so I hope I do this right, but I bought this phone specifically to be a 5G hotspot, and OnePlus disabled 5G after Android 11 update.
I'm on build number 11.0.3.BE89BA, so EU model, and before I take the plunge into installing custom ROM for the first time since I owned an LG G3 like 7 years ago, I'd like to at least confirm this will work on my build and it will re-enable 5G.
Thank you for answering, and if you have any extra tips or info how to make it as easy as possible, I'd be grateful.
EDIT: I've followed the instructions to the best of my understanding, and it gets stuck at 47%, which I've heard is normal, but I always reboot into stock firmware. I tried it at least 5 times so far, even following Youtube videos (different OnePlus phones on YT though), but the result is always the same. Instructions say nothing about TWRP, but can I maybe try that way?
Click to expand...
Click to collapse
I MsM back to stock rom which for me was version 10 at which point I needed to update os to 11 twice to make sure that 11 was on both partitions. After that I unlocked, flashed recovery, reboot recovery, format data, adb sideload rom, then adb sideload partition fix, then reboot to bootloader, fastboot--set-active=a( or b depending on what partition you were on. you want to be on the other partition), boot back into recovery, adb sideload rom again for the different partition, format data again, then reboot. works fine for me. here is the link for the copy partition zip https://www.androidfilehost.com/?fid=2188818919693768129
boffster99 said:
I MsM back to stock rom which for me was version 10 at which point I needed to update os to 11 twice to make sure that 11 was on both partitions. After that I unlocked, flashed recovery, reboot recovery, format data, adb sideload rom, then adb sideload partition fix, then reboot to bootloader, fastboot--set-active=a( or b depending on what partition you were on. you want to be on the other partition), boot back into recovery, adb sideload rom again for the different partition, format data again, then reboot. works fine for me. here is the link for the copy partition zip https://www.androidfilehost.com/?fid=2188818919693768129
Click to expand...
Click to collapse
Hey man, thank you for the help, but I'm really bad at understanding this, so please have some patience with me asking a few questions. I've only started looking into this a couple of hours ago, and I'm not the most tech savy when it comes to phones.
I don't know what MsM is, but I'll look around the forum and try to find more info. Question is, do I really need to flash back to 10 just to install 11 again, since I'm already on an official 11? Honestly, I'm not really sure my phone ever was on 10, I just know when I got the phone I updated to the new firmware straight out of the box, then discovered about 5G being turned off in 11 afterwards.
I've read about partitions in comments for Pixel Experience Custom ROM, and I've tried to do that, but Powershell insisted there's only partition A, and no matter what I would do it wouldn't switch. Is that the zip file for? How do I use it?
Sophos437 said:
Hey man, thank you for the help, but I'm really bad at understanding this, so please have some patience with me asking a few questions. I've only started looking into this a couple of hours ago, and I'm not the most tech savy when it comes to phones.
I don't know what MsM is, but I'll look around the forum and try to find more info. Question is, do I really need to flash back to 10 just to install 11 again, since I'm already on an official 11? Honestly, I'm not really sure my phone ever was on 10, I just know when I got the phone I updated to the new firmware straight out of the box, then discovered about 5G being turned off in 11 afterwards.
I've read about partitions in comments for Pixel Experience Custom ROM, and I've tried to do that, but Powershell insisted there's only partition A, and no matter what I would do it wouldn't switch. Is that the zip file for? How do I use it?
Click to expand...
Click to collapse
Did you go into fastboot or fastbootd?
Fastboot allows you to switch slots, fastbootd does not.
fastboot --set-active=a and the commands pertaining to dynamic partitions also requires a newer version of adb and fastboot. Old version will just give you an "unknown command" response.
Sophos437 said:
Hey man, thank you for the help, but I'm really bad at understanding this, so please have some patience with me asking a few questions. I've only started looking into this a couple of hours ago, and I'm not the most tech savy when it comes to phones.
I don't know what MsM is, but I'll look around the forum and try to find more info. Question is, do I really need to flash back to 10 just to install 11 again, since I'm already on an official 11? Honestly, I'm not really sure my phone ever was on 10, I just know when I got the phone I updated to the new firmware straight out of the box, then discovered about 5G being turned off in 11 afterwards.
I've read about partitions in comments for Pixel Experience Custom ROM, and I've tried to do that, but Powershell insisted there's only partition A, and no matter what I would do it wouldn't switch. Is that the zip file for? How do I use it?
Click to expand...
Click to collapse
If your on stock 11 then no shouldn't need to MsM. I've tried the rom for a few days. At first it was pretty good. noticed some wifi glitching and although it would allow me to establish a hot spot, it did not allow internet access doing it. So I never was able to get the hos spot working.
ninjasinabag said:
Did you go into fastboot or fastbootd?
Fastboot allows you to switch slots, fastbootd does not.
fastboot --set-active=a and the commands pertaining to dynamic partitions also requires a newer version of adb and fastboot. Old version will just give you an "unknown command" response.
Click to expand...
Click to collapse
I followed the instructions a few times and I'm sure I typed fastboot not fastbootd, unless that has nothing to do with entering fastbootd. As for the versions, I've downloaded the Platform tools r32 from the adb tutorial on this website, which I guess is the newest version. I also tried the 15 second adb tool I found on some youtube tutorial, but CMD just immediately crashes when I tried to run it, so I had to do everything in Poweshell. When I tried to switch partition powershell would say something in the lines of "looking for any device", then pretty much freeze and get unstuck 30 seconds later with nothing happening.
boffster99 said:
If your on stock 11 then no shouldn't need to MsM. I've tried the rom for a few days. At first it was pretty good. noticed some wifi glitching and although it would allow me to establish a hot spot, it did not allow internet access doing it. So I never was able to get the hos spot working.
Click to expand...
Click to collapse
Oof, that's a deal breaker for me, hotspot is a must for me. I'll try another ROM and hopefully I have more luck with it. The thing is, I don't know if it's stock 11 or not, I've never checked, my phone just pretty much downloaded a software update on the first run and I clicked install without thinking too much about it.
Cant sideload the ROM. I get the following error
C:\Users\Harrison\OneDrive\Desktop\Metro pcs\platform-tools_r32.0.0-windows\platform-tools>adb sideload C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip
serving: 'C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip' (~0%) adb: failed to read command: No error
C:\Users\Harrison\OneDrive\Desktop\Metro pcs\platform-tools_r32.0.0-windows\platform-tools>adb sideload C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip
Total xfer: 0.00x
umaga2012 said:
Cant sideload the ROM. I get the following error
C:\Users\Harrison\OneDrive\Desktop\Metro pcs\platform-tools_r32.0.0-windows\platform-tools>adb sideload C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip
serving: 'C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip' (~0%) adb: failed to read command: No error
C:\Users\Harrison\OneDrive\Desktop\Metro pcs\platform-tools_r32.0.0-windows\platform-tools>adb sideload C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip
Total xfer: 0.00x
Click to expand...
Click to collapse
usually get that error if your coming from the wrong Os or from a custom rom. Are you running stock OOS 11 on your phone?
Sophos437 said:
I followed the instructions a few times and I'm sure I typed fastboot not fastbootd, unless that has nothing to do with entering fastbootd. As for the versions, I've downloaded the Platform tools r32 from the adb tutorial on this website, which I guess is the newest version. I also tried the 15 second adb tool I found on some youtube tutorial, but CMD just immediately crashes when I tried to run it, so I had to do everything in Poweshell. When I tried to switch partition powershell would say something in the lines of "looking for any device", then pretty much freeze and get unstuck 30 seconds later with nothing happening.
Click to expand...
Click to collapse
Are you typing in adb reboot bootloader or adb reboot fastboot?
Bootloader leads to official fastboot.
Fastboot leads to fastbootd which doesn't do the fastboot things oddly enough.
boffster99 said:
usually get that error if your coming from the wrong Os or from a custom rom. Are you running stock OOS 11 on your phone?
Click to expand...
Click to collapse
I'm coming from OOS11. My device is the Metro version. Apparently these new ROMS only work on the global devices
ninjasinabag said:
Are you typing in adb reboot bootloader or adb reboot fastboot?
Bootloader leads to official fastboot.
Fastboot leads to fastbootd which doesn't do the fastboot things oddly enough.
Click to expand...
Click to collapse
I'm typing ./adb reboot bootloader. Like I've said, my knowledge is limited, so I've followed the tutorial word for word. Anyway, I'll have a few days off next week, so I'll try to do all sorts of things, starting with downgrading to OOS10 with MSM. That by itself should fix my 5g problem, and if it doesn't then I'll do more Custom ROM shenanigans.
{
"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"
}
ArrowOS
Code:
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel
Github: https://github.com/ArrowOS
WHAT WORKS?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Bluetooth
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
WHAT DOESN'T WORK?
DT2W
You tell me
Be sure to include a log : check how to
DOWNLOADS
ROM [VANILLA]: https://www.androidfilehost.com/?fid=2981970449027577433
MD5: 3BEBDBD50CEF18A0BC7EE4B91FFB4556
SHA-1: 088D01620FAC2198C41BAAB5C4B7373545CE0F1C
ROM [WITH GAPPS]: https://www.androidfilehost.com/?fid=2981970449027577434
MD5: 2CB7B3426A300BB3CC3975936A50B4A3
SHA-1: 8C8DE3CA640C769FEE44A6BA413C28E70DDC430D
*NOTE: ArrowOS Recovery not currently working properly, included PixelExperience recovery in the meantime, which will work fine*
RECOVERY: https://www.androidfilehost.com/?fid=2981970449027577417
MD5: BFE3114F2A966E03CFD0CF6C0040146B
SHA-1: B14B3102C97C15E3C7C045182489514C0827713F
In case you need it for magisk or any other reason, here's the boot image as well:
BOOT IMAGE: https://www.androidfilehost.com/?fid=2981970449027577435
MD5: F1C858AF7E4037098595016570ACF773
SHA-1: 75B9B0337651D09813FBF494715C93AF307953CA
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
Contributors: @iamsaalim, @kronflux
Source Code: https://github.com/ArrowOS
Device Sources: - https://github.com/kronflux/device_oneplus_billie
Kernel Sources: - https://github.com/danascape/kernel_oneplus_sm6350
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Release Date: 27-01-2022
Last Updated: 21-03-2022
ROM Firmware Required: OxygenOS 11.x
ROM Kernel: 4.19.125
Please provide instructions on how to install it.
Thank you!
I agree with the person above, there should be installation instructions.
Michael0620 said:
I agree with the person above, there should be installation instructions.
Click to expand...
Click to collapse
I agree as well, I wanted to install this on my phone, but I was running into error's.
art2111 said:
Please provide instructions on how to install it.
Thank you!
Click to expand...
Click to collapse
arrow os installation in nord n10 5G with 100% working method
Just wanted to say that I've been having a hell of a time lately getting my N10 5g back up and running properly everything fails in twrp or otherwise. First install attempt with arrow well see for yourself. Works wonderfully so far.
How long should I be watching the boot screen? I have had problems getting almost anything to install on this phone, I though OP was supposed to be more friendly to tinkerers! That being said, Orangefox Recovery installed like a champ, Arrow seemed to flash without any problem, now I'm going on 30min watching the Arrow icon on the boot screen. Am I stuck in a bootloop? There hasn't been any noticeable restarting of the boot screen animation
***Please ignore my question, after watching the install video I realized I was missing a couple crucial steps. Arrow is installed and working perfect!***
Nds99 said:
How long should I be watching the boot screen? I have had problems getting almost anything to install on this phone, I though OP was supposed to be more friendly to tinkerers! That being said, Orangefox Recovery installed like a champ, Arrow seemed to flash without any problem, now I'm going on 30min watching the Arrow icon on the boot screen. Am I stuck in a bootloop? There hasn't been any noticeable restarting of the boot screen animation
***Please ignore my question, after watching the install video I realized I was missing a couple crucial steps. Arrow is installed and working perfect!***
Click to expand...
Click to collapse
hello,can you tell me how stable is this rom?
BloodMist said:
hello,can you tell me how stable is this rom?
Click to expand...
Click to collapse
Only been running for a couple days but I haven't had one single problem out of it.
Honestly, when I get the time I want to install this ROM since I pretty much ripped everything google related out of pixel experience when I realized that I didn't have to.
I might post the step-by-step instructions I followed
Isabelinc said:
Honestly, when I get the time I want to install this ROM since I pretty much ripped everything google related out of pixel experience when I realized that I didn't have to.
I might post the step-by-step instructions I followed
Click to expand...
Click to collapse
Yes please,instructions will be appreciated
BloodMist said:
Yes please,instructions will be appreciated
Click to expand...
Click to collapse
INSTRUCTIONS (leave a like so that more people see this):
So everything is going well but here is how I did it (Note be sure to have a computer with android-tools (for adb and fastboot):
1. make sure your device is unlocked
2. Download your desired version of the rom (Vanilla or GAPPS, I picked Vanilla), the boot image (for rooting with magisk or flashing if you have another rom previously installed), and the recovery image
3. From within your normal rom, make sure adb debugging is enabled then do "adb reboot bootloader"
4. Flash the recovery image with "fastboot flash recovery recovery.img"
5. Perform a system wipe from within the recovery
6. Go to apply update then choose apply from ADB
7. adb sideload rom.zip
8. Voila
With my phone I had to repeat steps 4-7 again in slot a(or b)* and flash the boot image on both slots*
*Enter fastboot mode and enter fastboot --set-active=(a/b)
*fastboot flash boot.img
Side Note: it can be finicky entering fastboot mode so make sure you reboot to a screen that says one plus fastboot mode or something of the sorts
Isabelinc said:
So everything is going well but here is how I did it (Note be sure to have a computer with android-tools (for adb and fastboot):
1. make sure your device is unlocked
2. Download your desired version of the rom (Vanilla or GAPPS, I picked Vanilla), the boot image (for rooting with magisk or flashing if you have another rom previously installed), and the recovery image
3. From within your normal rom, make sure adb debugging is enabled then do "adb reboot bootloader"
4. Flash the recovery image with "fastboot flash recovery recovery.img"
5. Perform a system wipe from within the recovery
6. Go to apply update then choose apply from ADB
7. adb sideload rom.zip
8. Voila
With my phone I had to repeat steps 4-7 again in slot a(or b)* and flash the boot image on both slots*
*Enter fastboot mode and enter fastboot --set-active=(a/b)
*fastboot flash boot.img
Side Note: it can be finicky entering fastboot mode so make sure you reboot to a screen that says one plus fastboot mode or something of the sorts
Click to expand...
Click to collapse
i think i did same,but after flashing recovery and sideloading the rom,i was getting stock rom!
i forgot -set active command and boot image i think lol
thank you!
just installed and works perfectly!
is there any chance i can have stock camera back though?
BloodMist said:
just installed and works perfectly!
is there any chance i can have stock camera back though?
Click to expand...
Click to collapse
Which stock camera app, the one plus camera app or the google one? On the Vanilla version is came with the one plus camera app which I disabled and replaced with SImple Camera.
For the google one, I bet you could find the apk or on the play store/aurora store.
Also I'm glad I was able to help!
Isabelinc said:
Which stock camera app, the one plus camera app or the google one? On the Vanilla version is came with the one plus camera app which I disabled and replaced with SImple Camera.
For the google one, I bet you could find the apk or on the play store/aurora store.
Also I'm glad I was able to help!
Click to expand...
Click to collapse
i mean the Oneplus stock camera one,it would be better with it,any chance i can have it back?
thank you
BloodMist said:
i mean the Oneplus stock camera one,it would be better with it,any chance i can have it back?
thank you
Click to expand...
Click to collapse
Try looking for apk mirrors online of it and see if they work
Isabelinc said:
Try looking for apk mirrors online of it and see if they work
Click to expand...
Click to collapse
no they don't,they crash immediately without warning right when clicked open
BloodMist said:
no they don't,they crash immediately without warning right when clicked open
Click to expand...
Click to collapse
ah rip, well I guess you're going to have to get used to something different
Isabelinc said:
ah rip, well I guess you're going to have to get used to something different
Click to expand...
Click to collapse
there is no way to get stock one back? even with root?
May the peace, blessings, and mercy
This is a simple explanation of root and ROM gsi
Before starting the process, you must install all these drivers and restart your computer
_Realme USB Driver https://realmefirmware.com/usb-driver/
_\QcomMtk_Driver_Setup_3.0.9 https://realmefirmware.com/realme-usb-driver-installation/
_ADB Fastboot https://drive.google.com/file/d/1G4-4FexYDncZik18xDhCnJqoEygC7NgE/view Explanation of installation
_Universal ADB Drivers https://adb.clockworkmod.com/
1_Now you must install the original ROM with Boot Rooting and Unlocking Bootloader
RMX3265_11_A.33
Realme Firmware Update (Stock ROM) - Realme Firmware
Flash your Realme phone with latest firmware rom (Flash File) via Realme Flashtool.
realmefirmware.com
boot :https://www.mediafire.com/file/2n27361m4p3nnbv/Rooting+and+Unlocking+Bootloaderboot.rar/file
install:https://forum.xda-developers.com/t/realme-c25y-rmx3269-root.4437641/
spd flash tool:https://spdflashtool.com/category/download
turn off the phone. After that, press and hold the Volume Down button and at the same time connect the phone to the PC using the USB cable. You will see that the Upgrade Download program was able to identify the phone and the flashing process will start automatically.
{
"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"
}
When the installation of the original ROM is completed with the modified boot Activate usb debugging developer options
Connect the phone to the computer
1_extraction gsi rom I used CorvusOS version: vS4.0 Leviathan 12 It looks like the original rom
Tipz Team Builds - Browse /GSIs/CorvusROM/Official/20221015 at SourceForge.net
sourceforge.net
2_Download and extract platform-tools https://developer.android.com/studio/releases/platform-tools
commands:
1_adb devices
2_adb reboot fastboot
3_fastboot devices
4_fastboot delete-logical-partition product_a
5_fastboot reboot fastboot
6_fastboot erase system
7_fastboot flash system patch(CorvusOS )
8_fastboot erase userdata
9_fastboot reboot
enjoy
to explain:
bugs:I didn't have a problem
Note: It is not recommended to install 13 where there are camera and light brightness problems
Credit:ramzidz15
punalt boot
Youssef//busy
Fix brightness
Termux
su
setprop persist.sys.qcom-brightness 4095
ramzidz15 said:
Fix brightness
Termux
su
setprop persist.sys.qcom-brightness 4095
Click to expand...
Click to collapse
Well done bro
Does this ROM have Floating Windows? I terribly need that feature.
Also, should I download VNDK Lite version? Would there be anything bad if I didn't use VNDK Lite GSIs?
Last thing, so Android 13 GSI works but has camera issues?
Reyproject said:
Does this ROM have Floating Windows? I terribly need that feature.
Also, should I download VNDK Lite version? Would there be anything bad if I didn't use VNDK Lite GSIs?
Last thing, so Android 13 GSI works but has camera issues?
Click to expand...
Click to collapse
1_I don't know, you can try it yourself
You can install any version you want to try
Android 13 has problems with the camera, video, watching YouTube, etc.
ramzidz15 said:
1_I don't know, you can try it yourself
You can install any version you want to try
Android 13 has problems with the camera, video, watching YouTube, etc.
Click to expand...
Click to collapse
Bro i sen a message you on Telegram..
mirkolo said:
Bro i sen a message you on Telegram..
Click to expand...
Click to collapse
+213 659 95 69 50
ramzidz15 said:
1_I don't know, you can try it yourself
You can install any version you want to try
Android 13 has problems with the camera, video, watching YouTube, etc
Click to expand...
Click to collapse
I cannot get fastboot to detect the device. I tried the drivers you provided and followed the video and yet it still doesn't show up...
Also tried different drivers but still nope.
Tried different computers and still not detecting fastboot.
Edit: Phone gets detected when put in bootloader so I'm sure it's not a driver issue. Only when it's in fastbootd it won't get detected.
Nevermind as I got it to finally work.
Installed Lineage OS 19.1 Android 12, everything is smooth. Although does not pass SafetyNet. Headphones also are not working for me. Gonna see if there are other bugs and will try other GSIs such as crDroid to check which one is suitable for daily driving.
I won't be testing GSIs with no Gapps.
Reyproject said:
Nevermind as I got it to finally work.
Installed Lineage OS 19.1 Android 12, everything is smooth. Although does not pass SafetyNet. Headphones also are not working for me. Gonna see if there are other bugs and will try other GSIs such as crDroid to check which one is suitable for daily driving.
I won't be testing GSIs with no Gapps.
Click to expand...
Click to collapse
Will this remove the stock ROM?
JA sunny said:
Will this remove the stock ROM?
Click to expand...
Click to collapse
Yes it will, if you want to go back to stock then you can just flash stock firmware again
ramzidz15 said:
May the peace, blessings, and mercy
This is a simple explanation of root and ROM gsi
Before starting the process, you must install all these drivers and restart your computer
_Realme USB Driver https://realmefirmware.com/usb-driver/
_\QcomMtk_Driver_Setup_3.0.9 https://realmefirmware.com/realme-usb-driver-installation/
_ADB Fastboot https://drive.google.com/file/d/1G4-4FexYDncZik18xDhCnJqoEygC7NgE/view Explanation of installation
_Universal ADB Drivers https://adb.clockworkmod.com/
1_Now you must install the original ROM with Boot Rooting and Unlocking Bootloader
RMX3265_11_A.33
Realme Firmware Update (Stock ROM) - Realme Firmware
Flash your Realme phone with latest firmware rom (Flash File) via Realme Flashtool.
realmefirmware.com
boot :https://www.mediafire.com/file/2n27361m4p3nnbv/Rooting+and+Unlocking+Bootloaderboot.rar/file
install:https://forum.xda-developers.com/t/realme-c25y-rmx3269-root.4437641/
spd flash tool:https://spdflashtool.com/category/download
turn off the phone. After that, press and hold the Volume Down button and at the same time connect the phone to the PC using the USB cable. You will see that the Upgrade Download program was able to identify the phone and the flashing process will start automatically.
When the installation of the original ROM is completed with the modified boot Activate usb debugging developer options
Connect the phone to the computer
1_extraction gsi rom I used CorvusOS version: vS4.0 Leviathan 12 It looks like the original rom
Tipz Team Builds - Browse /GSIs/CorvusROM/Official/20221015 at SourceForge.net
sourceforge.net
2_Download and extract platform-tools https://developer.android.com/studio/releases/platform-tools
commands:
1_adb devices
2_adb reboot fastboot
3_fastboot devices
4_fastboot delete-logical-partition product_a
5_fastboot reboot fastboot
6_fastboot erase system
7_fastboot flash system patch(CorvusOS )
8_fastboot erase userdata
9_fastboot reboot
enjoy
to explain:
bugs:I didn't have a problem
Note: It is not recommended to install 13 where there are camera and light brightness problems
Credit:ramzidz15
punalt boot
Youssef//busy
Click to expand...
Click to collapse
Noob question: did u rooted the rom with adb? Or its already rooted
Andromix3345 said:
Noob question: did u rooted the rom with adb? Or its already rooted
Click to expand...
Click to collapse
I think you did not follow the explanation well boot The attachment contains root and unlock the bootloader in the fastboot
ramzidz15 said:
I think you did not follow the explanation well boot The attachment contains root and unlock the bootloader in the fastboot
Click to expand...
Click to collapse
Well I rooted my phone with this guide do I have to do this step or just continue to install corvus gsi?
Andromix3345 said:
Well I rooted my phone with this guide do I have to do this step or just continue to install corvus gsi?
Click to expand...
Click to collapse
yes Directly follow the installation steps
I successfully manged to flash it but I have 3 bugs
1- headphones jack not working
2- when I'm on a call speaker not working
3- brightness slider is too weak and the fix you provided isn't working
Please give a solution if you know
ramzidz15 said:
yes Directly follow the installation steps
Click to expand...
Click to collapse
Andromix3345 said:
I successfully manged to flash it but I have 3 bugs
1- headphones jack not working
2- when I'm on a call speaker not working
3- brightness slider is too weak and the fix you provided isn't working
Please give a solution if you know
Click to expand...
Click to collapse
Yes, I noticed that there are many problems. I have returned to the original. I cannot help you with anything.
i have problem with error kode 10 adb driver win 10 when put command adb reboot fastboot dont see my phone i duing step by step sory for my english adb devices see
Andromix3345 said:
I successfully manged to flash it but I have 3 bugs
1- headphones jack not working
2- when I'm on a call speaker not working
3- brightness slider is too weak and the fix you provided isn't working
Please give a solution if you know
Click to expand...
Click to collapse
Headphone jack is not working rightnow
i try to fix it
i can"t this command fastboot delete-logical-partition product_a
Deleting 'product_a' FAILED (remote: 'Command not available on locked devices')
fastboot: error: Command failed I have root on a44