{
"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
08-04-21 Build - GAPPS/VANILLA
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install Android 10 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 Android 10 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!
Phone failed to run arrow OS. It just constantly going back to bootloader when restarting system. I'll figure it out later, luckily I've made backups so I have something to fall back on
You know what, I attempted an adb sideload as an "attempt", and it worked after fidgeting around TWRP for about 20 minutes. But for some reason, I'm on slot b. Weird, but it worked...
@Beetle84 Thanks for yet another one. But since you're dumping everything but this, may I ask what about arrow specifically made got want to switch to it alone?
Also, why do we need to go back to stock? Just to minimize errors? I don't understand. More precise and revelant debugging?
Thanks again I've been wanting to try this one but just had a couple questions lol
griz.droidx said:
@Beetle84 Thanks for yet another one. But since you're dumping everything but this, may I ask what about arrow specifically made got want to switch to it alone?
Also, why do we need to go back to stock? Just to minimize errors? I don't understand. More precise and revelant debugging?
Thanks again I've been wanting to try this one but just had a couple questions lol
Click to expand...
Click to collapse
Mainly the simplicity of it, and it has all the features I need.
Going back to stock first with the flash tool is mainly about prepping the b slot for TWRP flashable ROMs.
@Beetle84 is there a way to add the customization tool from the other 2 OS? I like this one based on Android 11 but I also like the customization from RR. I'm just curious.
ShadowWeasel said:
@Beetle84 is there a way to add the customization tool from the other 2 OS? I like this one based on Android 11 but I also like the customization from RR. I'm just curious.
Click to expand...
Click to collapse
Nah, not compatible, are you using telegram? I shared a build of Evo X there, that sounds like the sort of rom you are looking for.
Beetle84 said:
Nah, not compatible, are you using telegram? I shared a build of Evo X there, that sounds like the sort of rom you are looking for.
Click to expand...
Click to collapse
I just installed it
Beetle84 said:
Nah, not compatible, are you using telegram? I shared a build of Evo X there, that sounds like the sort of rom you are looking for.
Click to expand...
Click to collapse
Hey @Beetle84 where can I find the Evo X build
ShadowWeasel said:
Hey @Beetle84 where can I find the Evo X build
Click to expand...
Click to collapse
EvolutionX - 5.x - Google Drive
Beetle84 said:
EvolutionX - 5.x - Google Drive
Click to expand...
Click to collapse
Should I flash this thru stock or twrp version of fastbootd? also, gapps or vanilla?
Edit: I answered my own questions. I'll check out everything and let you know how things went. Too bad I don't know how to make roms, otherwise I'd help out
ShadowWeasel said:
@Beetle84 is there a way to add the customization tool from the other 2 OS? I like this one based on Android 11 but I also like the customization from RR. I'm just curious.
Click to expand...
Click to collapse
But he just said this ROM had all the features he needs. I like the adjustable purtiness of RR as well but I'm ready to give this a run after trying stag 11.
Theres still CR and Stag. Either way we're very fortunate to have the choices we have. I've been wanting to try my hand at building and just bought a new multi-purpose lappy but still haven't put in the time. These guys are essentially donating time, talent, and treasure (ITM) to what is a damn good cause IMHO.
I'm ready to try a no-bs os myself as my battery life is in the ditch.
Does Micro G work with this Rom?
@EpicSaga Not sure mate, ive never tried.
Absolutely it does! Microg works fine, as is or as a magisk module. I use the magisk module from the magisk app because you get basic installation and everything works. You only need to open the app and go to self test and click each item missiing their permissions for most everything to be added. Still need to get your nlp services added and enabled for network based location services.
I was just yesterday afforded the time to install and try the rom. I can definitely see the appeal of the minimalistic approach and I really like how the ROM specific settings are integrated into the existing categories instead of in a dedicated tab.
If I had only one wish it'd be for the long swipe long press options to kill apps and so on. Don't get me wrong it affords plenty of customizations and seems to be a fine ROM. I'm going to give it a go to see how things roll.
Beetle84 said:
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
08-04-21 Build - GAPPS/VANILLA
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!
Click to expand...
Click to collapse
Soon as I upgrade to the moto 5g ace u keep surprising us with your awesome work.
Hopefully you get the 5g ace and port this rom to it. If you don't get the phone thanks for all the fun you gave me on this phone and the moto g power..
Stay cool..
jhjhjhjhjhjh said:
Soon as I upgrade to the moto 5g ace u keep surprising us with your awesome work.
Hopefully you get the 5g ace and port this rom to it. If you don't get the phone thanks for all the fun you gave me on this phone and the moto g power..
Stay cool..
Click to expand...
Click to collapse
Thanks man, ive actually gone and bought the g 5g plus, awesome phone.
Beetle84 said:
Thanks man, ive actually gone and bought the g 5g plus, awesome phone.
Click to expand...
Click to collapse
Yes great phone only thing I wish it had dual speakers like the stylus but loving the 5G.
I already rooted it hours after I bought it lol.
I'll see you on the 5G Ace form then.. I'm happy you got the phone bro....lol my phone says 5G Ace yours 5G plus. Wonder what the differences are??..
How big is the battery in the g 5g plus? I live in the frigging hills and according to some coverage maps there's 5g close to home can't remember which cartier. T-mo/Sprint probably
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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is PAX?
Our release of Android 10, titled CR-8.0, is codenamed PAX after the latin word for peace and Pax, the roman godess for peace.
PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a systemwide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z3
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Nightly
Created 2020-02-08
Last Updated 2020-05-06
Reserved
@Myself5
Thx so so much for the first beta cr 8.0 build. I will check it out tomorrow.
One question:
Is possible to boot from this build directly into twrp?
I'm asking because the hardware buttons of my old z3 needs many pressure to work.
Restart to recovery
dhacke said:
Is possible to boot from this build directly into twrp?
Click to expand...
Click to collapse
All current Shinano ROMS derived from LineageOS16/17 should support restart to recovery. You may need to enable the extended restart menu under development options.
You can also trigger this via adb:
Code:
adb reboot recovery
Please report if that isn't working
Mr.Tom_Tom said:
All current Shinano ROMS derived from LineageOS16/17 should support restart to recovery. You may need to enable the extended restart menu under development options.
You can also trigger this via adb:
Please report if that isn't working
Click to expand...
Click to collapse
I can comfirm now that the boot into twrp works.
@Myself5
I believe i notice a bug: I couldn't secure the z3 with a password in the setup because after i entered the password it says 'success' but in the settings under the device security tab still stands 'swipe'.
When i try to change the display lock to the password option afterwards in the settings menu my z3 always asks me after a password and when i type in the password which i type in the setup it says wrong password.
New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.
Uploaded a new build. Contains some additional lockscreen clocks but more importantly, the PIN issue is fixed.
Code:
75ff1b7cd559ec1f61b196a831891142 CARBON-CR-8.0-PAX-UNOFFICIAL-z3-20200225-1425.zip
Can you support d6633 dual version please
Thanks for the awesome work. Flashing ASAP!
I am unable to successfully flash the 3.3.1 recovery. Android Stock marshmallow 6.0.1 build 291 installed. Rooted it by flashing 575 kernel and after root revert it back to 291 kernel file by flashing with flashtool.
Now my 6.0.1 is 23.5.A.1.291 means latest build. And flashing the recovery by typing the command "fastboot flash FOTAKernel recovery.img.
The recovery 3.3.1 which I downloaded from lineage 17.1 page. I renamed the file twrp_z3_2020-02-08.img to recovery.img
But after flashing the recovery when I enter into recovery it shows twrp 3.0.2
I downloaded the twrp 3.3.1 from different pages but same thing happened.
I'm a poor man ? and can't afford or buy android 10 device and I saw a dream that I opened xda and there someone launched mouth watering cr8.0 and lineage os 17.1
And I wish I could flash those os
But this twrp is hurdling me and that is proven a big hurdle to me which I couldn't cross
I'm on bed and doctor ? said you're guest of few days if you can't flash android 10
TWRP images flashed to the FOTAKernel partition can only be accessed by, starting with your phone completely powered off, holding both the power and volume down buttons. When the phone vibrates (as if it was being turned on), release the power button. When the screen lights up, release the volume down button. TWRP shall come up.
casouzaj said:
TWRP images flashed to the FOTAKernel partition can only be accessed by, starting with your phone completely powered off, holding both the power and volume down buttons. When the phone vibrates (as if it was being turned on), release the power button. When the screen lights up, release the volume down button. TWRP shall come up.
Click to expand...
Click to collapse
Finally someone who explains how to boot in the ( new ) recovery. I bet @KnowledgeSeekerPart2 had the correct recovery allready installed different times.
I didn't say that I couldn't enter into twrp. But whenever I flashed 3.3.1 on my 23.5.A.1 291 build I found 3.0.2 on my shinano.
Is it possible that if you flash 3.3.1 twrp, you ended up by having 2 different versions installed (3.3.1 & 3.0.2)
I simply wanna say that you mean which I understood that if you power on your device and when led light flashes then by pressing volume down button twice or thrice quickly you'll enter into 3.0.2 recovery and according to your mathod I'll enter into 3.3.1 (remember I just flashed 3.3.1 on fota kernel)
KnowledgeSeekerPart2 said:
I am unable to successfully flash the 3.3.1 recovery. Android Stock marshmallow 6.0.1 build 291 installed. Rooted it by flashing 575 kernel and after root revert it back to 291 kernel file by flashing with flashtool.
Now my 6.0.1 is 23.5.A.1.291 means latest build. And flashing the recovery by typing the command "fastboot flash FOTAKernel recovery.img.
The recovery 3.3.1 which I downloaded from lineage 17.1 page. I renamed the file twrp_z3_2020-02-08.img to recovery.img
But after flashing the recovery when I enter into recovery it shows twrp 3.0.2
I downloaded the twrp 3.3.1 from different pages but same thing happened.
I'm a poor man and can't afford or buy android 10 device and I saw a dream that I opened xda and there someone launched mouth watering cr8.0 and lineage os 17.1
And I wish I could flash those os
But this twrp is hurdling me and that is proven a big hurdle to me which I couldn't cross
I'm on bed and doctor said you're guest of few days if you can't flash android 10
Click to expand...
Click to collapse
Flash the recovery to recovery partition instead,
Code:
fastboot flash recovery (name of recovery).img
KnowledgeSeekerPart2 said:
I didn't say that I couldn't enter into twrp. But whenever I flashed 3.3.1 on my 23.5.A.1 291 build I found 3.0.2 on my shinano.
Is it possible that if you flash 3.3.1 twrp, you ended up by having 2 different versions installed (3.3.1 & 3.0.2)
I simply wanna say that you mean which I understood that if you power on your device and when led light flashes then by pressing volume down button twice or thrice quickly you'll enter into 3.0.2 recovery and according to your mathod I'll enter into 3.3.1 (remember I just flashed 3.3.1 on fota kernel)
Click to expand...
Click to collapse
Yes, that's right, it's possible, i had 2 different recoverys too in my Z2 or Z3C, don't remember exactly which device it was.
The " old way " was to press vol+ during boot process to boot in the recovery.
hey, same problem with @KnowledgeSeekerPart2
i tried all method around the web and unable to upgrade the crappy twrp 3.0.2 to shiny 3.3.1, the twrp 3.0.2 can't flash carbon, lineagos and will give you "unknown command" error....damn
let see what i tried so far
- upgrade through twrp app -> nope
- upgrade through flashing on current twrp recovery mode -> still nope
- upgrade through fastboot like "flash recovery" and "flash fota" -> still nope
i still boot to 3.0.2 with no change at all
and btw, @casouzaj recommended power+vol down combo not work too, because my z3 will not boot to recovery with that way, it boot the OS XD so i always have to : tap tap fast vol down few times to boot to recovery
very troublesome i admit
KoolKool993 said:
hey, same problem with @KnowledgeSeekerPart2
i tried all method around the web and unable to upgrade the crappy twrp 3.0.2 to shiny 3.3.1, the twrp 3.0.2 can't flash carbon, lineagos and will give you "unknown command" error....damn
let see what i tried so far
- upgrade through twrp app -> nope
- upgrade through flashing on current twrp recovery mode -> still nope
- upgrade through fastboot like "flash recovery" and "flash fota" -> still nope
i still boot to 3.0.2 with no change at all
and btw, @casouzaj recommended power+vol down combo not work too, because my z3 will not boot to recovery with that way, it boot the OS XD so i always have to : tap tap fast vol down few times to boot to recovery
very troublesome i admit
Click to expand...
Click to collapse
Again.
Download the required TWRP.
Place it in your " Fastboot and ADB " folder. ( PC ! )
Inside your " Fastboot and ADB " folder create an empty file, rename it to " flashFOTAKernel.bat "
Open ( edit ) the file, paste the following in the file :
fastboot flash FOTAKernel twrp-3.3.1-z3-20200212.img
Save the .bat file
Shut down your device complete. ( Press and hold vol UP and power until the device vibrates 3 times )
Now connect the device in fastboot mode to your PC ( press vol UP, hold the button ) and plug the USB cable in. LED should be blue.
Doubleclick the .bat file you've created before, and that's all.
Disconnect your device, press vol DOWN and power, HOLD the buttons until the boot logo appears, and your device boots in your new recovery.
0LDST4R said:
Again.
Click to expand...
Click to collapse
i appreciated your kindness highly
but sadly, your method not working for me
Shut down your device complete. ( Press and hold vol UP and power until the device vibrates 3 times)
Click to expand...
Click to collapse
i tried nothing vibrate
Now connect the device in fastboot mode to your PC ( press vol UP, hold the button ) and plug the USB cable in. LED should be blue
Click to expand...
Click to collapse
Yes, i tried this, i got blue light and into fastboot mode
Download the required TWRP.
Place it in your " Fastboot and ADB " folder. ( PC ! )
Inside your " Fastboot and ADB " folder create an empty file, rename it to " flashFOTAKernel.bat "
Open ( edit ) the file, paste the following in the file :
fastboot flash FOTAKernel twrp-3.3.1-z3-20200212.img
run the bat
Click to expand...
Click to collapse
yeah, i did, everything said file extractions are succesfully
Disconnect your device, press vol DOWN and power, HOLD the buttons until the boot logo appears, and your device boots in your new recovery.
Click to expand...
Click to collapse
i tried this, but it just boot straight into the OS
meanwhile, the "press vol down multiple time on green light logo boot up" method as i mentioned above is only the way into twrp recovery (but still old version), nothing less
my Z3 is Dual 6633, on right version, totally SuperU rooted and unlocked bootloader
tried it today... quite snappy... Better than cr 7, as fast as cr 6! Very impressed!
battery life excellent.
i ll use it for daily driver as soon as it passes beta phase!
passes safety net even with magisc!! (didnt have that with CR 6)
on the first install pixel launcher was present but force closes... quickstep worked all right.. after reinstall pixel launcher was absent.
camera did not work as well but somehow this fixed itself. (edit: the "cantt connect to the camera error returned unexpectedly)
i couldnt find how to connect to wifi with WPS push button, the setting seems to be absent.
much better than lineage (faster snappier) have to give you that.. thank you for all the work!!
excellent work for a beta build.
wishlist:
1. fm radio! pls pls pls !
2. shutdown/reset button on quick settings
I'm testing firmware on D6633. Faced with the fact that the SIM card is detected, but there is no connection. Tried to call - writes that you need to turn off flight mode. Even the APN is in place. Next, I tried to install the patch for SIM cards for the dual version, but this led to the fact that the firmware now does not see the SIM card at all. It would be nice to see a working mobile connection for D6633 in the following builds.
{
"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"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
2.3.x Gingerbread?
Just installed on my device, works great first try, only thing I've found to not work is Moto Audio with any sort of headphones, works with internal speaker tho. great work thanks!
googl-fi sofiap cannot flash to system
I am unable to flash to the system. It will not let me delete the super or system file. not sure what to do tried everything that is listed on the flash gsi. anyone with some help
lightningdude said:
2.3.x Gingerbread?
Click to expand...
Click to collapse
Typo, dude. F
rooted?
is this rom rooted?
vache said:
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
Click to expand...
Click to collapse
stolirocks said:
is this rom rooted?
Click to expand...
Click to collapse
Nope.
Although not "rooted" you can root after installation just like you would with stock.
Thank you for the ROM. First time using OmniRom and loving it so far. I have not run into any issues so far. Even on t-mobile, my WiFi calling, visual voicemail and text messages all are working without any issues.
Will you be releasing a version with just MicroG instead of gApps? I ended up just uninstalling all the gApps anyways, but just curious.
Keep up the great work!
GApps Dilemma
I am really looking forward to not having Gapps on this device, I haven't installed yet due to this, and wonder. Is this OpenGApps implentation removable using the same instructions as if it were installed manually after the CFW was flashed? Also, if it is not too much extra work, could you post a non GApps build?
Thanks for the hard work!
griz.droidx said:
Although not "rooted" you can root after installation just like you would with stock.
Click to expand...
Click to collapse
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
.Solotato said:
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
Click to expand...
Click to collapse
Greetings Solotato and Moto/Android community ,
I know this post is long excessively but hopefully it'll get the point across. Please don't think I'm talking down to you or anyone else. This whole process had me baffled at first as well and I've used others work to root and rom fur years. I've used Linux on the desktop by dual and even triple booting (Nix,Xpor2K, and 98 for old hardware slash gaming support) I even wrote a config for a guy's app called js2mouse to use 2 pointers at the same time in X(wanted to use my old logitech wingman cordless as a remote. But I'm no expert and still consider myself a little above novice. This isn't meant to offend anyone. Shew (the us is just too politically correct)
You can use twrp i think with magisk. BUT...im pretty sure i flashed twrp once in the recovery bootloader before but nothing else would take and twrp didn't function correctly.
I agree with many others now that it's easier to put a copy of the boot image on your device after installation. It's simple really
Just boot your device,
Enable developer options first thing then adb, then you can connect with a usb cable and approve adb access in your phone.
Copy the boot image to your phone and use the latest official magisk to patch the boot image. In magisk pick install then pick image, you pick your boot image which is then patched and renamed magisk_patched or similar.
It'll be in your downloads folder. Move it back to your pc, the patched one of course, and then just
fastboot flash boot magisk_patched.img
A TIP if you're new to the command line/powershell(win) or terminal(nix/bsd/mac (which is based on bsd)You can even use the up arrow if you dunt want to retype the commands then just replace boot.img with magisk_patched.img just start typing magis then hit tab and it'll complete it for you..
All this looks complicated but trust me after you do it a few times you'll be doing it in a minute or two.
Good luck take your time and read everything you can find. Don't forget to ask the command line for --help! You can find help in a jiffy that way.
Example
fastboot --help i think is the syntax i can't see it on my phone but there's a space between the two dashes and the command your asking for help. And for more details help is included in Linux with man pages. Those are handy in a pinch.
Even though I've done this since the droidx days on many phones, it still took me a lot of research and reading to get this new a/b partitioning and fastboot stuff down to where i can do it quickly.
Read and search these threads you'll be more likely to get answerers from xda members if they can tell you've been reading up on it.
Good luck!
Practice practice practice. That's the advice my uncle gave me on shooting a bow (instinctive or without sights) and he was right. This applies to everything in life.
Anyway I've preached enough. I know it's a long post but hopefully you and others who are relatively new to these moto's will get some help here.
Don't forget to thank the developers and others who made all this coolness possible for us who benefit from
If i helped any at all or you enjoyed my way too many useless details style, please hit thanks. I appreciate that. Sorry for the delay in posting I'm still setting up my most recent rom and I've doing a lot of stuff outside my home before winter.
Sent from my Moto G Stylus using XDA Labs
Sorry guys that was waaaaay too long.
Sent from my Moto G Stylus using XDA Labs
Could anyone point me in the right direction for recompiling this rom's kernel with a different config? I'm looking to poke around & try to get USB OTG/ACA mode to work (i.e. have the phone charge as well as use a usb device, like a mouse/keyboard/storage), which is apparently possible by setting CONFIG_USB_MSM_OTG and CONFIG_USB_MSM_ACA.
I've never compiled a kernel for another arch before, and I assume I need a toolchain that targets arm64 to begin with - I've also never really built anything for android before, and all the guides I've found thus far seem to either be for a specific device or building an entire system image, which seems to be too much - I'm given to understand I can replace the kernel image in boot.img by itself with a tool like mkbootimg.
Any help with where to start would be appreciated, thanks!
My Screen isn't working anymore... using an OTG to move around....
It's the touch screen
Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
ianspy1 said:
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
Click to expand...
Click to collapse
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ?
gatorz_4z said:
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ? My hope is that with that version you will be successful? Another person told me to redownload the ROM and try with a fresh one.
Click to expand...
Click to collapse
Gotta love how unsupported this ROM is... Or just busy dev...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonadep#crDroid-v7
Changelog: https://crdroid.net/lemonadep#crDroid-v7/changelog
Known issues:
- waiting for more feedback to see
Visit official website @ crDroid.net
crDroid OnePlus 9 Pro Telegram
crDroid Community Telegram
crDroid is built with passion by @neobuddy89 and @gwolfu
If you like our work, do consider a donation to support further device development
ROM OS Version: Android 11
ROM Kernel: Linux 5.4
Awesome.
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
burtonlax said:
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
Click to expand...
Click to collapse
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
gwolfu said:
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
Click to expand...
Click to collapse
it's best to go global first coming from tmo. No, as long as you don't do an ota on Global. so flash global then boot, then flash custom rom(following their guide).
If u lose service modem is provided (Just unzip) Bootloader fastboot command "fastboot flash modem modem.img
This of course is assuming u got unlock.bin and unlocked Bootloader
Here we go!
Welcome @gwolfu
Hopefully we don't need 11.2.7.7?? It's not out here in EU yet, what's the reason most of the custom roms seem to want the EU build by the way?
CRDroid, fantastic to see this here my favorite ROM since the days of my LG G3! Can't wait to try this out, will sadly be waiting till TWRP tho as I'd prefer to avaoid gapps. Unless there is any chance of a non gapps build also? Cheeky....!
I'll flash and report tomorrow .
post logs through here or telegram?
ryantf420 said:
I'll flash and report tomorrow .
post logs through here or telegram?
Click to expand...
Click to collapse
preferably here as to better keep track of stuff
I know it may not be recommended, but has anyone been able to flash this without using a computer?
phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
Since the instructions specify using fastboot (as well as sideloading the rom), that's not possible.
phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
without TWRP, not possible
TWRP is death.
This is awesome news brother
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
crazyvash1 said:
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
Click to expand...
Click to collapse
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
gwolfu said:
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
Click to expand...
Click to collapse
Think you missed the last step to use Magisk again to root the installed boot image?
djsubterrain said:
Think you missed the last step to use Magisk again to root the installed boot image?
Click to expand...
Click to collapse
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
gwolfu said:
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
Click to expand...
Click to collapse
Didn't notice that, totally right. Sorry.
truly have found nothing broken
except power menu settings only work in crdroid Settings not in System>Gestures>power menu...
Great job
{
"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"
}
VoltageOS 13.0 | Tiramisu for Mi A2 Lite (daisy)
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
More info: HERE
Telegram Voltage: Group
If you like our work you can buy us a cup of coffee
*TogoFire Maintainer Daisy
*PIX: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOAD:
VoltageOS 2.2 230123: CLICK HERE
SHA256: 3c21e3f7c2b8c6f90f8c7388e0a481c6e842f313d2dfd04c5f6c6e5fcda18385
Gapps $hit Package (Recommended): LiteGapps | Microg | MindTheGapps
Recovery: HERE
If you use instagram or any $hit like facebook, use this: LINK
Installation GuideClean Flash
1) If you are coming from any MiuiROM, GSI, or any other PortROM, edl miflash from firmware 10.0.18.0 or 11.x.x is mandatory.
2) Edl firmware 11.x.xx or 10.x.xx (install firmware via miflash if needed)
3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs).
4) Reboot to recovery
5) Boot to Recoovery
6) Format Data--Yes
7) Reboot to recovery
8) Wipe data, system, dalvik cache, internal storage.
9) Install ROM
10) Install TWRP
12) Reboot to recovery
13) Install LiteGapps (optional)
16) Install Magisk (optional)
17) Reboot to system
Dirty Flash
1) Backup Everything (Most Important)
2) Download ROM
3) Boot to TWRP (Power and vol+; or Advanced Restart > Recovery)
4) Backup Data partition (optional)
5) Install the 'update' ROM
6) Install TWRP ZIP (optional)
7) Then reboot to recovery. (Note: in current recovery the slot changes by itself, no longer need to change manually)
8) Install GApps that you've used to installed, and Magisk.
9) Wipe dalvik and reboot
10) Reboot to system
GUIDE FULL
Link
ROM Source: https://github.com/VoltageOS
Source: Kernel & Device & Vendor
Support Links:TogoFireWork Channel
TogoFireWork Group
McQuaidLab
XDA:DevDB Information
ROM OS Version: Android 13.0 | Tiramisu
ROM Kernel: Linux 4.9.X
ROM Firmware Required: 10.0.18, 11.0.04, 11.0.16 or greater
Based On: AOSP
reserved!
reserved...!!!
@TogoFire
Hi mate. Thanks for your efforts. I'm on SyberiaOS A13 version. Do i still need to flash firmware or can i install directly from recovery with format data system etc.? Thanks.
dr.bahaeddin said:
@TogoFire
Hi mate. Thanks for your efforts. I'm on SyberiaOS A13 version. Do i still need to flash firmware or can i install directly from recovert with format data system etc.? Thanks.
Click to expand...
Click to collapse
Being firmware greater than or equal to 10.0.18, it's fine. If it's coming from a Lupe rom, then just go straight to install the rom
Is this pre-overclocked? What are the clocks?
ortizjammet said:
Is this pre-overclocked? What are the clocks?
Click to expand...
Click to collapse
McQuaid Lab
McQuaid Lab Kernel: https://t.me/McQuaidKernel Download & Changelog: LINK Kernel Source If you like our work you can buy us a cup of coffee *TogoFire Maintainer *PIX: [email protected] Orangefox old OrangeFox Recovery Project...
forum.xda-developers.com
It will be helpful is guys share your experience about this rom...
New update!
Small important fixes made.
Changelog of the last commits: IMG | DT
Enjoy!
@TogoFire thanks again for the update. I wonder how can i enable Google auto fill? Apps dont recognize my saved singin infos.
dr.bahaeddin said:
@TogoFire thanks again for the update. I wonder how can i enable Google auto fill? Apps dont recognize my saved singin infos.
Click to expand...
Click to collapse
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this.
TogoFire said:
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this
Click to expand...
Click to collapse
TogoFire said:
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this.
Click to expand...
Click to collapse
If you are so focused on security, why is your ROM UNofficial?
Will it become OFFICIAL in the near future so that it is also suitable as a daily driver?
cappuccini said:
If you are so focused on security, why is your ROM UNofficial?
Will it become OFFICIAL in the near future so that it is also suitable as a daily driver?
Click to expand...
Click to collapse
Since when does it have to be official to be safe?
There are so many roms whether official or not that aren't good, so this has no relevance.
The trees are opensource, by the way.
I'm not a buildbot. So my builds are decent.
I already keep Official Xtended. It's enough for me. I don't have time to keep two official ROMs.
TogoFire said:
Since when does it have to be official to be safe?
There are so many roms whether official or not that aren't good, so this has no relevance.
The trees are opensource, by the way.
I'm not a buildbot. So my builds are decent.
I already keep Official Xtended. It's enough for me. I don't have time to keep two official ROMs.
Click to expand...
Click to collapse
...I'm sure all is as you write, however, I think it is wrong to equate Official and UNofficial. For OFFICIAL ROMs there are rules, which among other things also serve the security of the users, and not every user can read and check a source code...
Thank you for your statement and your certainly also very good work!
cappuccini said:
...I'm sure all is as you write, however, I think it is wrong to equate Official and UNofficial. For OFFICIAL ROMs there are rules, which among other things also serve the security of the users, and not every user can read and check a source code...
Thank you for your statement and your certainly also very good work!
Click to expand...
Click to collapse
Np.
These rules are useless to tell you the truth. I maintain Xtended Official, so I have an idea of how it works. It's like I told you. Being decent construction, it doesn't have any problems.
The only thing they require is that you know how to cherry-pick, know how to author commits, and have built at least one unofficial rom of theirs, and have at least a notion of how to fix bugs, and respect colleagues. They will look at your history and see how you behave. These rules will not prevent a buildbot.
TogoFire said:
Np.
These rules are useless to tell you the truth. I maintain Xtended Official, so I have an idea of how it works. It's like I told you. Being decent construction, it doesn't have any problems.
The only thing they require is that you know how to cherry-pick, know how to author commits, and have built at least one unofficial rom of theirs, and have at least a notion of how to fix bugs, and respect colleagues. They will look at your history and see how you behave. These rules will not prevent a buildbot.
Click to expand...
Click to collapse
...the requirements of the individual ROMs seem to differ a lot, with LOS for example they are supposed to be significantly higher.
what about the XDA rules? These also have to be complied with in an official ROM. what about banking apps and other security-critical apps in case of damage? Metadata is stored with every login. Even the proprietary messenger WhatsApp registers a custom ROM and refuses support.
In a Samsung thread a maintainer wrote that the unofficial ROM is only for testing.... A very difficult topic for me, ultimately everyone must decide for themselves who they trust.
Thanks for the insight into the world of developers and best regards
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
norva said:
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
Click to expand...
Click to collapse
...this installation guide has been very helpful to me:
[DEPRECATED] Detailed Installation Guide for Custom Roms (Mi A2 Lite - Daisy)
Heya, This is a guide aimed on helping you to switch to a custom rom from the stock firmware. For any questions, feel free to join our Telegram groups. PREREQUISITES 1) Stock rom recommended by the maintainer of the rom that you want to flash...
forum.xda-developers.com
P.S. I am currently testing MSM Xtended v4 with LiteGapps core, there were no problems during installation.
norva said:
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
Click to expand...
Click to collapse
Can it be that you have installed GApps for Android 12? This ROM is Android 13...
SOLVED! YEAH! Took me hours but finally got it!
So either the new stock rom (daisy_global_images_V11.0.21.0.QDLMIXM_10.0) did it or it is related to the installation with adb sideload or from SD card which caused my issue (I finally simply copy the installation zip files through USB while TWRP is active on the phone and gives access to the memory from computer, and installed them using the dedicated button (no adb sideload)).
Time to test now
@cappuccini : yeah I read this guide and had the android 13 gapps version (but you are right, it took me a while to understand it was the folder 33 on sourceforge...).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* 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 Recovery
* 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.
*/
Introduction
OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features, fixes and a host of supported devices
OrangeFox version: R11.1
For device: a32
Maintainer: Ahnet ( @Captain_cookie_200 )
OrangeFox source:
OrangeFox Recovery · GitLab
OrangeFox Recovery | OFR
gitlab.com
Device tree:
GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6.
Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6. - GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Sa...
github.com
Kernel Source: https://github.com/ahnet-69/android_kernel_samsung_a32-recovery
Features:
Code:
Synced with the latest Teamwin changes
Designed with latest Material design 2 guidelines
Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
Included assorted customizations
Inbuilt patches, like Magisk and password reset patch
Several addons
Password protection
Fully open-source
Frequently updated
Status
Stable-ish
Tested on:
SM-A325F (by me)
SM-A325M (by @filipedonato)
other models unknown. But should work.
Please report back so i can update the op
Downloads
Click here.
Bugs
1. TWRP cannot decrypt userdata if you set lockscreen. (someone said it works, other it doesn't, so I'll just leave it here, YMMV)
2. Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
3.USB-OTG
4. Saving settings is fixed but for fixing settings such as theming resetting on reboot is by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.
Installation
Code:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
1. Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
2. Go back, go to Developer Settings.
3. Turn on OEM unlock toggle.
4. Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
5. Your device will boot into download mode with a warning. Accept it.
6. Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
7. When it reboots to OS, finish setting up your device.
8. Double check to make sure OEM Unlock is still ON.
Preparing for the installation:
1. Download everything above onto your PC.
2. Rename OrangeFox recovery img file to recovery.img and add it to archive using any archiver and select gnu tar.
3. Install Samsung USB Driver.
4. Open Odin.
5. Connect your phone to your PC. There should be a COM entry on the top.
6. Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
7. Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
Installing:
1. Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: OrangeFox TAR file.
2. Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
3. In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have OrangeFox up and running now.
Post-Installation:
MUST: Trigger Multi-disabler.
1. In OrangeFox, go to Terminal.
2. Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
3. Run multidisabler again.
4. Go to main screen. go to Wipe > Format Data, type yes then swipe.
5. Reboot to Recovery. Now you can do other stuff.
Should: Backup all vital partitions:
1. In OrangeFox, go to Backup
2. Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, PBRP and the likes)
1. Download the recovery image.
2. Copy it to phone, then reboot to OrangeFox (Combo is Power + Volume-up)
3. Go: Install > select recovery.img file > select Recovery
4. Swipe to confirm flashing.
5. If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
Credits:
To the OrangeFox and TWRP team and everyone involved in making this all work.
@Long266 For his kernel and amazing work.
@ianmacd For multidisabler.
@afaneh92 For his a32x base tree and MTK-Samsung multidisabler.
@KrutosVIP For his experimental lineage kernel source from here.
reserved
reserved
I have tried to talk to various developers about the settings not saving issue. They have no idea. I have myself tried playing around with the tree but nope. So unless someone has a fix for this i have no idea
New Build!
Whats new?
Fixed the settings such as theming resetting on reboot by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.
If you see the recovery trying to decrypt storage dont worry about it. its just because of this. It does nothing.
It's stable? I mean, i can install gsi's and zips?
ApiYoshi said:
It's stable? I mean, i can install gsi's and zips?
Click to expand...
Click to collapse
yes i use orangefox. flashing gsi works fine. same goes with zips
Captain_cookie_200 said:
yes i use orangefox. flashing gsi works fine. same goes with zips
Click to expand...
Click to collapse
Ok, i flashed it and is awesome!! Thanks for great work brother!
ApiYoshi said:
Ok, i flashed it and is awesome!! Thanks for great work brother!
Click to expand...
Click to collapse
You should make a telegram group
ApiYoshi said:
You should make a telegram group
Click to expand...
Click to collapse
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates
Works in A32 A325M Brazil variant.
really nice you are keeping the a32 alive!
applesucksLmao said:
really nice you are keeping the a32 alive!
Click to expand...
Click to collapse
i did nothing tbh. all the credit goes to the people who put effort in making twrp work i just copied and built it. all the credit goes to them
Captain_cookie_200 said:
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates
Click to expand...
Click to collapse
Ooh, i undertand
One question, you will update the recovery when an update came out?
ApiYoshi said:
One question, you will update the recovery when an update came out?
Click to expand...
Click to collapse
yes i will try
Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it
Seth Ofc said:
Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it
Click to expand...
Click to collapse
sorry i didnt include it. but i think i specified. rename OrangeFox recovery img file to recovery.img
then use 7zip or winrar or any other archiver and then add to archive. There select tar and compress. I'll include tar files in next builds by default
Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it
Seth Ofc said:
Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it
Click to expand...
Click to collapse
use a generic system image.
if you want heres a list: here