{
"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.
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"
}
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.
{
"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
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!
View attachment 5273685View attachment 5273649View attachment 5273651View attachment 5273653View attachment 5273655
View attachment 5273657View attachment 5273659View attachment 5273661View attachment 5273669View attachment 5273671View attachment 5273673View attachment 5273675View attachment 5273677View attachment 5273679
Agh, plain AOSP. I miss Havoc already.
Testing it out and everything thing seems smooth. I did find one minor issue for the people that like their temperatures in imperial units. You can change the lockscreen temp to imperial and it displays an F for farenheit but the temperature value is still Cecius.
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
jonshmorg said:
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
Click to expand...
Click to collapse
You will need to go back to rooted stock, and copy your apn_conf.xml file from product/etc to your sd card, amd replace it on arrow (or another rom)
Quantumstate said:
Agh, plain AOSP. I miss Havoc already.
Click to expand...
Click to collapse
Closest thing to havoc is crDroid ATM mate, it's on the forums here
This ROM is marked as only being compatible with sofiar, but I can confirm that everything seems to work on my sofia device.
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Edit: It turns out I was using the wrong build of TWRP. Use the one linked in the original post, not the one elsewhere on the forums.
RaspberryPiBen said:
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Click to expand...
Click to collapse
While in twrp, if you select reboot to fastboot, that is fastboot d
Beetle84 said:
While in twrp, if you select reboot to fastboot, that is fastboot d
Click to expand...
Click to collapse
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
RaspberryPiBen said:
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
Click to expand...
Click to collapse
Using the twrp linked here or another?
Beetle84 said:
Using the twrp linked here or another?
Click to expand...
Click to collapse
I just noticed that. I was using the TWRP build from https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ because I assumed that was what the link was for. Thank you.
Apps aren't able to see registered fingerprints. Fingerprint auth is grayed out and the apps complain "register fingerprints on the device settings".
I have tried:
Deleting and redoing fingerprints (just one and multiple) with and without rebooting.
Confirmed the fingerprints work for screen unlock and gestures.
Re-installed 08-04-21 Vanilla build with full format, issue persists.
Anything I missed to check? I do not have my phone rooted, so cannot see system logs using the logging app.
Using sofiar (moto g8 power). Tested the apps themselves on my second phone klte (Samsung S5 Lineageos 16) and fingerprints work just fine there.
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
jdude520 said:
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
Click to expand...
Click to collapse
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Carl-Robert said:
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
Click to expand...
Click to collapse
I'm not the person with the problem, but thank you for the explanation. I installed my ROMs before Android 11 came out for this phone and I was planning to test the stock Android 11 ROM, so this information will be very useful.
jdude520 said:
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Click to expand...
Click to collapse
I believe you have to roll back to Android 10. Custom Android 11 ROMs may work, but you can't install custom ROMs so that doesn't help.
actually it is rescuing me to android 11 no matter what i do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for OnePlus Nord N10 5G [billie]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Code:
/* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Bluetooth
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
DT2W
You tell me!
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
ROM: https://www.androidfilehost.com/?fid=2981970449027577418
MD5: 53C4B515DDCC722A59510C161209F916
SHA-1: CCA686001DA7959C0E953D1948FB3626CF66987F
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=2981970449027577416
MD5: CFE13188A29FD82AD8134DA706D06730
SHA-1: FC023DEC26372B2F9E8EEF054635561092DCF2EF
INSTRUCTIONS
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!
Translation
Help with project translation
Stay tuned
Follow us on Telegram
Contributors @iamsaalim, @kronflux, @billaids
ROM source: https://github.com/PixelExperience
Device sources: https://github.com/kronflux/device_oneplus_billie
Kernel source: https://github.com/danascape/kernel_oneplus_billie
ROM OS Version: 11.x
ROM Kernel: 4.19.125
ROM Firmware Required: OxygenOS 11.x
Based On: AOSP
Version Information
Status: Community Beta
Created 22-01-2022
Last Updated 22-03-2022
Is this an update, and if so do you update through the recovery. Also does updating reset userdata
For some reason adb sideload stops at 47% and I see step 2/2 on my screen. With no indication of it's complete or not. Upon backing out it immediately says complete but doesn't boot, and instead boots into the bootloader
dieudeglace said:
For some reason adb sideload stops at 47% and I see step 2/2 on my screen. With no indication of it's complete or not. Upon backing out it immediately says complete but doesn't boot, and instead boots into the bootloader
Click to expand...
Click to collapse
If it gets to 47% it's finished. (It happens with every recovery and rom for some reason)
It goes right to the bootloader because you have to flash both slots with the rom.
You're halfway there basically.
Use fastboot to switch slots and sideload PE again.
You should be all good to go, just make sure to factory reset after sideloading.
CodeNotSoGenious said:
Is this an update, and if so do you update through the recovery. Also does updating reset userdata
Click to expand...
Click to collapse
It is not an update, you can't go from the previous version of pixel experience to this one.
Unlike the previous version which requires you being on Android 10 before installing pixel experience, you've gotta be on Android 11.
You'd lose user data by having to go back to stock for the Android 11 update (again when unlocking bootloader, and again if you choose to format your device after installing the rom)
It's a bit of time, but the effort is definitely worth it if you have somewhere to store your files momentarily.
ninjasinabag said:
If it gets to 47% it's finished. (It happens with every recovery and rom for some reason)
It goes right to the bootloader because you have to flash both slots with the rom.
You're halfway there basically.
Use fastboot to switch slots and sideload PE again.
You should be all good to go, just make sure to factory reset after sideloading.
Click to expand...
Click to collapse
you are a god send. i thought i was doing something entirely wrong lol
yeah works like a charm now. Deeply appreciate this. Im still new to all this and accidentally bricked my tcl 20 pro 5g a little while ago.
dieudeglace said:
yeah works like a charm now. Deeply appreciate this. Im still new to all this and accidentally bricked my tcl 20 pro 5g a little while ago.
Click to expand...
Click to collapse
Glad to hear you've got it up and running.
Yeah, it's always a coin toss when flashing anymore. Almost always worth it once you get those kinks out.
ninjasinabag said:
It is not an update, you can't go from the previous version of pixel experience to this one.
Unlike the previous version which requires you being on Android 10 before installing pixel experience, you've gotta be on Android 11.
You'd lose user data by having to go back to stock for the Android 11 update (again when unlocking bootloader, and again if you choose to format your device after installing the rom)
It's a bit of time, but the effort is definitely worth it if you have somewhere to store your files momentarily.
Click to expand...
Click to collapse
Thanks, I'll put in some time to flash this!
What's different from the last pixel experience ROM?
CodeNotSoGenious said:
What's different from the last pixel experience ROM?
Click to expand...
Click to collapse
Updated kernel and built officially around Android 11 instead of 10.
ninjasinabag said:
Updated kernel and built officially around Android 11 instead of 10.
Click to expand...
Click to collapse
Appreciate it
Seems I have had one issue so far. Using Android auto and receiving/making calls with people ends up with them not being able to hear me.
dieudeglace said:
Seems I have had one issue so far. Using Android auto and receiving/making calls with people ends up with them not being able to hear me.
Click to expand...
Click to collapse
I'll try and test this myself soon, I haven't been driving much lately so it's a tough thing to test
Make sure you try re-pairing your phone with the vehicle. and by that I mean, entirely delete it from your vehicle as well as delete the pairing in the phone itself. set it up as if it's a new device, and see if that makes a difference
Will try it later to see if it works, otherwise this is a very solid build so thank you for making this!
Now I may habve missed this through the pages but I am getting
"Eackage is for product OnePlusN10 but expected OnePlusNordN10" one device and on laptop cmd it says "failed to read command" is that because I need to flash both slots or is this soem other error?
brncgreen said:
Now I may habve missed this through the pages but I am getting
"Eackage is for product OnePlusN10 but expected OnePlusNordN10" one device and on laptop cmd it says "failed to read command" is that because I need to flash both slots or is this soem other error?
Click to expand...
Click to collapse
Do you happen to be using the metro version of the Nord n10? (Or TMobile since they're basically the same phone.)
ninjasinabag said:
Do you happen to be using the metro version of the Nord n10? (Or TMobile since they're basically the same phone.)
Click to expand...
Click to collapse
I am using t mobile. How ever I did figure it out.... It was ignorant for me to do this but... I didnt realize how PE was suppose to look and when it booted up for the first time I thought it was just stock oneplus OOS.... This time i flashed both a/b and when I booted it was the same thing so I was doing it right all along just failed to realize that it isnt really any different than stock at least from the cosmetic.
Trying to install this but when I get to adb sideload rom.zip (I did rename it after several failed attempts with it's original name). I keep getting
E:\Profile\Desktop>adb sideload rom.zip
loading: 'rom.zip'
* cannot read 'rom.zip' *
Any suggestions?
happened to me. I tried to install over a custom rom that had os11 on it, but it did not like it and kept giving me the same "cannot read" error. 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.
{
"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?
Your warranty will be void after any of these procedures.
* I am not responsible for the outcome for using any of this information, e.g. bricked devices, dead devices, boot loops
* do some research regarding flashing, custom ROM and unlocking bootloaders
* you chose to make these modifications under your own responsibility.
The following guide is for flashing any Treble Project compatible ROM (GSI) on the Samsung Galaxy Tab A8 2021 (SM-X200)What's working on android 12 / 12.1 ROMs :
Everything
What's working on android 13 ROMs :
Everything
There are two ways of flashing GSI, generic system images, for treble compatible devices:
ROM flash from fastboot mode.
Dynamic System Updates (DSU) loading
Prerequisites:
First you should check if your device is treble compatible, this has been already checked by me. Here's the app link for checking it if you make sure yourself
Then you should unlock your bootloader and flash TWRP, here's the link for it
Enable ADB over USB.
Wipe the Data Partition from TWRP
You can root with Magisk if you like.
Option 1 ROM flash from fastboot mode:This is my preferred mode
Instructions:
Turn off the device and Hold Power & Vol Up buttons during restart to enter TWRP recovery
Format data from TWRP and wipe all partitions
Navigate to reboot and select Fastboot mode
Download a GSI image, including LineageOS, Google Android, AOSP, or any other custom GSI Treble compatible ROM for AB partition scheme.
fastboot flash system system.img
also a fastboot -w after flashing for additional wiping wouldn't hurt
IMPORTANT: remember to always only flash *.img files, never flash zip, img.xz, img.tar, gz, or img.tar.zx files, look for the tools for unzipping these file formats and always extract just the system.img file for these procedures. NEVER flash the vbmeta.img this can brick your device
Option 2 Dynamic System Updates (DSU) loading:Instructions:
Enable the DSU feature flagBefore using DSU, ensure the corresponding feature flag is enabled. You can enable the flag using one of the following methods:
On a device with a userdebug Android build: You can enable the feature in Settings > System > Developer options > Feature flags > settings_dynamic_system.
On other devices: Use the following adb command:
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Launch DSUAfter the feature is enabled, launch DSU using the adb tool.
Download a GSI image, including LineageOS, Google Android, or any other custom GSI Treble compatible ROM for AB partition scheme.
Note: If you build your own GSI from source, or if you download a GSI from another image server, your GSI might not be unsparsed. Use the following command inside your build tree to convert the image to an unsparsed image: simg2img system.img system_raw.img
gzip the GSIand then Push the GSI to the device:
gzip -c system_raw.img > system_raw.gz
adb push system_raw.gz /storage/emulated/0/Download/
Launch DSU using adb.
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b *.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
The KEY_SYSTEM_SIZE should be for the uncompressed image file, otherwise it will fail
IMPORTANT: remember to always only flash *.img files, never flash zip, img.xz, img.tar, gz, or img.tar.zx files, look for the tools to uncompressed these file formats and always extract always the system.img file for these procedures. NEVER flash the vbmeta.img this can brick your device
Boot into the GSI
{
"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"
}
Figure 1. A persistent notification that you can use to control DSU.
After DSU installs the GSI, a DSU menu appears as a persistent notification inside the system notification drawer (see figure 1).
At this point, you can do one of the following:
Boot into the GSI by tapping Restart.
Clean up the GSI by tapping Discard.
Switch back to the device's original system imageAfter you are done testing your app using the GSI, you can perform a cold reboot to boot the system back into its original system image.
When setting the next reboot to use a GSI, you can have the GSI stay installed through multiple boot cycles (until discarded) by enabling sticky mode, or have it used for only one boot cycle by disabling sticky mode.
The following command enables sticky mode:
adb shell gsi_tool enable
The following commands disable sticky mode:
adb shell gsi_tool disable
adb shell gsi_tool enable -s
adb shell gsi_tool disable
Install GSIs using DSU and the DSU LoaderAndroid 11 introduced the DSU Loader, a tool available in the device's developer options that lets you download, install, and manage GSIs entirely through the system's UI.
To install a GSI using the DSU Loader, follow these steps on a device running Android 11 or higher:
Enable developer options on your device.
Open your device's Settings app, then tap Developer options > DSU Loader.
Choose the GSI that you want to install on your device.
Agree to the GSI terms and conditions.
After you agree to the terms and conditions, the GSI that you selected starts downloading. You can check the status of the download through the DSU notification.
After the download has finished, tap Restart to boot the GSI.
When you want to switch back to your device's original system image, tap Restart from the DSU system notification.
[IMG alt="DSU notification with an option that lets you reboot the device using the
original system image"]https://developer.android.com/static/images/topic/dsu/restart-original-system-image.png[/IMG]
Thanks to Magendanz for the TWRP recovery
Does anyone know if selinux and encryption work with this gsi?
only issue is rainbow six mobile and pubg new state detect it as a emulator so how would we fix this?
Twrp keeps saying entering fastboot but never does.
I think it was using older versions of adb and usb drivers
jeffbar2 said:
Twrp keeps saying entering fastboot but never does.
I think it was using older versions of adb and usb drivers
Click to expand...
Click to collapse
When it says that, try checking "fastboot devices" from the PC. I think you'll find you are in fastboot mode.
Does this trip knox like on s22 etc, or does it go back to normal if you restore back to original and relock bootloader?
MarcusGuy1108 said:
Does this trip knox like on s22 etc, or does it go back to normal if you restore back to original and relock bootloader?
Click to expand...
Click to collapse
AFAIK, the knox bit is a physical "fuse" and once it is tripped, it will never restore back. But normally Sansung will still honor the warranty so long as you go back to a stock ROM and relock the bootloader. That will also re-enable OTA updates.
lewmur said:
AFAIK, the knox bit is a physical "fuse" and once it is tripped, it will never restore back. But normally Sansung will still honor the warranty so long as you go back to a stock ROM and relock the bootloader. That will also re-enable OTA updates.
Click to expand...
Click to collapse
I see, just like the phones... damn samsung. Thank you very much for the quick response.
MarcusGuy1108 said:
I see, just like the phones... damn samsung. Thank you very much for the quick response.
Click to expand...
Click to collapse
It isn't just Samsung. Installing a custom ROM or rooting your device will void the warranty with all makers. But at least Samsung will still honor the warranty unless there is some indication that what you did caused the problem. Like bricking the device. But if it is really a hardware problem, they'll still fix it for free during the warranty period.
lewmur said:
It isn't just Samsung. Installing a custom ROM or rooting your device will void the warranty with all makers. But at least Samsung will still honor the warranty unless there is some indication that what you did caused the problem. Like bricking the device. But if it is really a hardware problem, they'll still fix it for free during the warranty period.
I mean the knox warrantee bit
Click to expand...
Click to collapse
I know what you meant. Yes, the warranty bit is blown. But as I said, Samsung will honor it anyway unless they feel something you did caused the problem. Of course, you will still have to reflash to a stock rom, relock the bootloader and factory reset before sending in for repair.
lewmur said:
I know what you meant. Yes, the warranty bit is blown. But as I said, Samsung will honor it anyway unless they feel something you did caused the problem. Of course, you will still have to reflash to a stock rom, relock the bootloader and factory reset before sending in for repair.
Click to expand...
Click to collapse
Maybe I'll try it then. I like a lot about this tablet but god is it sluggish on OneUi. Games and all that work fine (even smooooth) but animations and stuff on OneUI are just.... wow
MarcusGuy1108 said:
Maybe I'll try it then. I like a lot about this tablet but god is it sluggish on OneUi. Games and all that work fine (even smooooth) but animations and stuff on OneUI are just.... wow
Click to expand...
Click to collapse
There is a fix for that. It has to do with using ADB to change the options for how to size the ramdisk to zero. You might try googling "Samsong One Ui laggy". Lineage doesn't have One Ui so it doesn't have the problem.
MarcusGuy1108 said:
Maybe I'll try it then. I like a lot about this tablet but god is it sluggish on OneUi. Games and all that work fine (even smooooth) but animations and stuff on OneUI are just.... wow
Click to expand...
Click to collapse
This will fix your issue - https://www.androidpolice.com/samsung-ram-plus-phone-how-to-disable/
kevinco1 said:
This will fix your issue - https://www.androidpolice.com/samsung-ram-plus-phone-how-to-disable/
Tried that - made a bit of difference but just gonna return the tablet.
Click to expand...
Click to collapse
if you still own it: maybe you're in the mood to take a look here:https://forum.xda-developers.com/t/samsung-galaxy-one-ui-optimization-guide.4376755/
The SM-X200 is a budget device so if you've had a higher end Sam tab then yeah this will seem very slow
Hey all. I just recently bought a Tab A8 32GB and was looking for a way to load a ROM on it so I can use the SD Card as internal storage.
I found this guide, but I'm not seeing some of the steps it says to take on my device. I've enabled Developer Options, but I don't see the DSU/GSI stuff. Nor the 'feature flag' to turn that on.
I know back in the old days all you have to do way flash a recovery image and then you could load the ROM from recovery. Is that still the basic process? Can I flash TWRP and then flash the ROM, or is more detailed now than that?
ke4peo said:
Hey all. I just recently bought a Tab A8 32GB and was looking for a way to load a ROM on it so I can use the SD Card as internal storage.
I found this guide, but I'm not seeing some of the steps it says to take on my device. I've enabled Developer Options, but I don't see the DSU/GSI stuff. Nor the 'feature flag' to turn that on.
I know back in the old days all you have to do way flash a recovery image and then you could load the ROM from recovery. Is that still the basic process? Can I flash TWRP and then flash the ROM, or is more detailed now than that?
Click to expand...
Click to collapse
The full process for flashing is in the first post, in case you don't have the DSU option