OFFICIAL LINEAGE OS 17.1 NIGHTLIES
LineageOS Downloads
download.lineageos.org
The most recent build was dated 25th Feb 2021. [Edit UPDATED to most recent build date].
The previous offerings were 2021-01-28; 2021-02-04 ; 2021-02-11; 2021-02-18.
{
"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"
}
CEDRIC WIKI
Info about cedric | LineageOS Wiki
wiki.lineageos.org
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
QRXpMUvS said:
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
Click to expand...
Click to collapse
Any oero firmware will do as your base
Flash via fastboot - if you don't know which to choose use the latest retail version
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
How to flash rom
Go to twrp
Select wipe
Format data - option on the right (will format everything on phone including personal files so backup first!)
Restart to twrp
Wipe then advanced wipe
Wipe system data and cache
Select install from main menu
Install rom zip
Install gapps (you want arm64 android 10 nano)
Install magisk (optional for root access & to hide apps from detecting root/custom rom)
Wipe delvik cache
Restart
Encrypt phone again if required once booted from phone settings menu
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
QRXpMUvS said:
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
Click to expand...
Click to collapse
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Hi,
i updated my G5 to the official LOS. Although VoWifi and VoLTE are enabled in settings, none of them are working (They didn't work on the unofficial version either).
According to my network operator, these functions are activated.
Unter Phone Info (*#*#4636#*#* in dialer's app) it says "IMS Registration: Not Registered"
Is there anything I can do about this?
Thanks!
TheFixItMan said:
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Click to expand...
Click to collapse
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
QRXpMUvS said:
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
Click to expand...
Click to collapse
I have the same problem. I can't get Lineage or Mint to boot on my Cedric.
I've tried TWRP 3.4 , and 3.5 and neither made a difference. I have been through the instructions on the lineage site many times, and I'm sure I'm not missing a step
But every time the device sticks at lineage boot logo for a long time, before returning to fastboot mode.
If I re-flash 8.1 using fastboot, the phone works again, then go from the top with twrp and lineage, and we're back to logo and eventually fastboot again.
So, although I cannot help yet, you are not alone.
Edit:
My cedric is the 3GB RAM XT1676 model which I think might be somewhat rare version?
HarpingOn said:
So, although I cannot help yet, you are not alone.
Click to expand...
Click to collapse
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
QRXpMUvS said:
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
Click to expand...
Click to collapse
I have only tried mint and official 17.1. Get the same problem with both sadly.
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
For your info everyone: the OP is not the developer. I am neither. I just patch the official builds and that is Mint.
HarpingOn said:
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
Click to expand...
Click to collapse
If you could give me logs, I'll check.
nift4 said:
If you could give me logs, I'll check.
Click to expand...
Click to collapse
My problem was that I was starting from the GB release of Cedric stock 8.1 as I'm in the UK. If I flashed the GB version, then no Lineage ROM would boot. Not this, and not the Mint one.
If you check out the Mint thread, what I did was use Fastboot to flash an international version of stock 8.1, then I could add TWRP and flash this successfully.
I ended up testing Lineage With microG, but actually successfully flashed this, and Mint as well.
So I'd say to anyone struggling to get a working flash of this ROM, try a different CEDRIC set of fastboot files.
as im aware, you need to flash from stock 8.1 but sometimes if youre on pie you gotta flash nougat and then oreo to flash custom roms i tried flashing that rom before but got no succes with bootlop but i didnt knew this i have tried unnoficial los 17 but never though about trying again the one from los page, guess its Worth a try
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Lighto97 said:
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Click to expand...
Click to collapse
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
TheFixItMan said:
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
Click to expand...
Click to collapse
oh damm i always forgot i have to send the log for them to track the issue, i already uninstaled anyway.
i did followed the steps the right way (thank you), right now im flashing stock nougat to try out LOS 14.1 (which i love and seems to be reeealy stable)
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
tfbb said:
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
Click to expand...
Click to collapse
i know how to boot with that LOS recovery, instead of flash comand you use boot command so the device will bot into recovery suing the image.
Related
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
As a result of this, I am not even able to do a manual factory reset from the setting menu in OOS 2.2.3, because when i try to initiate this the phone again gets stuck at the logo screen of recovery mode.
Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
{
"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"
}
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Joshwin Aranha said:
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Click to expand...
Click to collapse
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Shalabh21 said:
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Click to expand...
Click to collapse
Whatever rocks your boat buddy, glad you sorted that out.
OPX stuck at oneplus logo after following the procedure
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
hbansal24x7 said:
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
Click to expand...
Click to collapse
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Joshwin Aranha said:
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Click to expand...
Click to collapse
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
hbansal24x7 said:
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
Click to expand...
Click to collapse
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Joshwin Aranha said:
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Click to expand...
Click to collapse
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
hbansal24x7 said:
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
Click to expand...
Click to collapse
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Joshwin Aranha said:
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Click to expand...
Click to collapse
MD5 is the same for UNCHANGED zip. i guess md5 will differ on a modified zip due to the changes you mentioned in the process.
{
"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"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 18.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 18.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the latest Android 11 release (T510XXU5CVG2).
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2.tar.md5 (Odin tarball)
lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20220907:
Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
Update to TWRP v3.6.2 custom recovery on AOSP 11.
20220417:
Based on the latest build of LineageOS 18.1 GSI (20220414) with April 2022 Security Patch.
Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVB1).
Update to TWRP v3.6.1 custom recovery on AOSP 11.
Replaced default wallpaper with custom one inspired by my Nexus ROMs.
Boots normally for offline (cold) charging.
20210526:
Based on the latest build of LineageOS 17.1 GSI (20210512) with May 2021 Security Patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU4BUA1).
20201121:
Based on the latest build of LineageOS 17.1 GSI (20201114) with November 2020 Security Patch.
Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
20200812:
Based on the latest build of LineageOS 17.1 GSI (20200808) with August 2020 Security Patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
20200713:
Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 Security Patch.
Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
20200413:
Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
Fixed crash on first two attempts to launch Phh Treble Settings.
Based on the latest build of LineageOS 17.1 GSI (20200413).
Updated to the OEM T510XXS3ATB4 kernel and vendor partition.
20200321:
Switched to latest stable version of ext2simg command for sparse image conversion.
20200314:
Now based on the latest build of LineageOS 17.1 GSI (20200309).
Fixed potential image corruption issue from outdated img2simg command.
20200308:
Charging after full shutdown will no longer hang during level-of-charge animation.
20200301:
Initial release based on lineage-17.1-20200227-UNOFFICIAL-treble_a64_bvN
MTP file transfers no longer require USB Debugging to be enabled.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, Install Image, select your update (.img file), and then swipe to install
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Does the ethernet-function (LAN) work?
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
andreasoz said:
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
Click to expand...
Click to collapse
Yes, I've noticed that myself, and it seems to occur when writing to certain modified vendor partitions. Anyone have an idea of what might cause that?
Magendanz said:
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Click to expand...
Click to collapse
Hiya
Just got this device today.. pretty stoked to get it rooted & Lineage going.. thanks for your projects & info
I'm curious do I need to change any of the Options tab in Odin ?
Auto Reboot off for example ?
Auto Reboot & F. Reset Time are checked by default none of the others are.
At this point in this device's progress assuming I unlocked correctly & get into Download mode.. flash with Odin successfully I should just Auto Reboot right into TWRP & can go from there ?
NoKnox is a thing of the past ?
What about Multi-disabler ?
If I install Magisk & plan to how do I ensure I don't "boot outside Magisk" I keep hearing people say.. where Vaultkeeper & similar things may become problematic or so I've read.
Someone did offer some advice on not booting outside Magisk a few weeks ago I'm going to go find their message too but yeah I've read a lot of threads here & it seems like since certain packages & older methods like patching TWRP with Magisk are things of the past.. I just want to confirm what all else is
is charging past 80% an issue at all with this ROM ?
That's one thing I see people mention about custom kernels is they fix that.. well that & EX or Franco would be rad if they exist for this device & rom
/salute
jaladhjin said:
I'm curious do I need to change any of the Options tab in Odin ? Auto Reboot off for example ?
Click to expand...
Click to collapse
Nope.
jaladhjin said:
NoKnox is a thing of the past ?
Click to expand...
Click to collapse
Yep.
jaladhjin said:
What about Multi-disabler ?
Click to expand...
Click to collapse
You still need to run Multi-disabler if you're installing TWRP, but it's baked into this custom ROM.
jaladhjin said:
is charging past 80% an issue at all with this ROM ?
Click to expand...
Click to collapse
No longer an issue with this custom kernel.
jaladhjin said:
If I install Magisk...
Click to expand...
Click to collapse
I don't use Magisk, and so I'm really not the person to ask. Note, however, that custom kernels in boot and recovery partitions are slightly different wrt MTP. Boot kernel uses Google MTP and recovery one uses Samsung MTP to maintain compatibility with OEM system if patched with Magisk.
Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.
Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.
andreasoz said:
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
Click to expand...
Click to collapse
OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
https://sourceforge.net/projects/opengapps/files/
https://www.cyanogenmods.org/downloads/bitgapps-for-android-10-download/
I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"
I cannot get back into lineage any advice?
I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more
Warrenchild said:
I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"
I cannot get back into lineage any advice?
I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more
Click to expand...
Click to collapse
Did you re-enable Developer mode and OEM?
lewmur said:
Did you re-enable Developer mode and OEM?
Click to expand...
Click to collapse
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
I even downgraded to sk1 and then let it do a OTA update while locked
Warrenchild said:
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
I even downgraded to sk1 and then let it do a OTA update while locked
Click to expand...
Click to collapse
I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.
edit: The original instruction are a little confusing. They tell you that after each step you have to boot and enable Dev mode in order to chech OEM enable. The real reason is that you have to enable Dev mode in order to flash anything but stock. Without it enabled, you get the message in red saying that only original firmware can be installed.
lewmur said:
I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.
Click to expand...
Click to collapse
I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.
Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
Error : "only official released binaries are allowed to be flashed(BOOT)"
and the flash stalls out on odin.
So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.
Warrenchild said:
I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.
Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
Error : "only official released binaries are allowed to be flashed(BOOT)"
and the flash stalls out on odin.
So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.
Click to expand...
Click to collapse
Did you read my "edit" where I said that was caused by not having enable Developer mode?
lewmur said:
Did you read my "edit" where I said that was caused by not having enable Developer mode?
Click to expand...
Click to collapse
I did not see your edit, thank you I will try and inform the community.
installing
BiTGApps-arm-10.0.0-R1_signed
BiTGApps-arm-10.0.0-v0.2_signed
open_gapps-arm-10.0-pico-20200219
open_gapps-arm-10.0-nano-20200305
with twrp will force reboot while installing
what maybe not work is miracast/widi. i can't find my tv with my tab.
phh-treble entry in settings does nothing / does not open.
(both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])
[email protected] said:
installing
BiTGApps-arm-10.0.0-R1_signed
BiTGApps-arm-10.0.0-v0.2_signed
open_gapps-arm-10.0-pico-20200219
open_gapps-arm-10.0-nano-20200305
with twrp will force reboot while installing
what maybe not work is miracast/widi. i can't find my tv with my tab.
phh-treble entry in settings does nothing / does not open.
(both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])
Click to expand...
Click to collapse
Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.
lewmur said:
Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.
Click to expand...
Click to collapse
my mi a1 with stock pie and the t510 stock rom still can use it
[email protected] said:
my mi a1 with stock pie and the t510 stock rom still can use it
Click to expand...
Click to collapse
Maybe so. But it isn't officialy supported, so if it doesn't work, it doesn't work. I tried it with several apps on several ROMs and could only get it work on my T580 by reverting to an Android 8. Every thing I tried in Pie either froze or caused the tablet to reboot.
Warrenchild said:
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
Click to expand...
Click to collapse
You triggered Samsung's VaultKeeper "feature" when you rolled back to the OEM firmware. In order to prevent that, you need to immediately enable Developer Options while connected to the Internet after setup (before rebooting). If you don't, VaultKeeper places the device in a hybrid state where it looks like the bootloader is still unlocked, but it still won't allow Odin to flash firmware unless it's signed with Samsung's release keys.
Flashing a known-good OEM firmware should remedy the problem, provided you verify that the OEM Unlocking setting is enabled in Developer Options and go back for a Volume Up long press from the blue warning screen to complete the bootloader unlock. Did you do that after booting while holding the Volume Up & Down with the USB cable attached?
betacrypt said:
Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.
Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.
OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
https://sourceforge.net/projects/opengapps/files/
https://www.cyanogenmods.org/downloads/bitgapps-for-android-10-download/
Click to expand...
Click to collapse
No luck for me with this, TWRP still reboots when trying to install gapps/bitgapps . I'm not sure what else to try.
OrangeFox Recovery Project
{
"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"
}
Installation
* Download Latest OrangeFox
* Assuming you already have twrp installed, copy the downloaded zip to device. Then Install.
* After successful installation it auto-reboots to OrangeFox recovery. Enjoy
Working
ADB
Decryption of /data
Screen brightness settings
Correct screenshot color
MTP
Flashing (opengapps, roms, images and so on)
Backup/Restore
OZIP decryption
Vibration support
USB OTG
Bugs
Report with proper logs.
Credits:
@MrYacha & @DarthJabba9 for this amazing custom Recovery
And the most 4j17h for pushing me to make it...
And whole HyperTeam for all the help in the beginning of my android development...
XDA:DevDB Information
[Official][Stable]OrangeFox Recovery for realme X2 Pro [R11][RMX1931], ROM for the Realme X2 Pro
Contributors
Jerry08, 4j17h
Source Code: https://gitlab.com/OrangeFox/
ROM OS Version: Android 10
Version Information
Status: Stable
Created 2020-08-04
Last Updated 2020-09-03
How to use F2FS
- boot to OrangeFox,
- go to 'Manage partitions'
- format data,
- select 'data', change filesystem, f2fs,
- select 'cache', change filesystem, f2fs,
- reboot,
- enjoy...
Reserved
Android 10 compatible?
tidschi said:
Android 10 compatible?
Click to expand...
Click to collapse
Depends, I tried on rui and it was fine. But it seems to have issues with decryption on a10 gsi, but first I let users report it as I'm not sure.
Will you need a modified vbmeta like the one on twrp?
And will it work on my global version?
Sent from my Realme RMX1931 using XDA Labs
SebTech33 said:
Will you need a modified vbmeta like the one on twrp?
And will it work on my global version?
Click to expand...
Click to collapse
Yes you will need vbmeta and yes it will work on global.
Jerry08 said:
Yes you will need vbmeta and yes it will work on global.
Click to expand...
Click to collapse
Thank you for your answer. Can i use the one from the twrp thread?
Sent from my Realme RMX1931 using XDA Labs
SebTech33 said:
Thank you for your answer. Can i use the one from the twrp thread?
Click to expand...
Click to collapse
Yeah or the one from my guides thread. It's up to you.
Jerry08 said:
Depends, I tried on rui and it was fine. But it seems to have issues with decryption on a10 gsi, but first I let users report it as I'm not sure.
Click to expand...
Click to collapse
By any chance was fingerprint working after installing RUi using this recovery?
There are reports of FP broken when using twrp
P1f said:
By any chance was fingerprint working after installing RUi using this recovery?
There are reports of FP broken when using twrp
Click to expand...
Click to collapse
Nope fp wasn't working after flashing rui, tested by me. Probably need to wait for official rui release.
Jerry08 said:
Nope fp wasn't working after flashing rui, tested by me. Probably need to wait for official rui release.
Click to expand...
Click to collapse
So what needs to be done to have a working FP sensor? But it's broken even without root?
---------- Post added at 06:03 PM ---------- Previous post was at 05:55 PM ----------
asusgarb said:
So what needs to be done to have a working FP sensor? But it's broken even without root?
Click to expand...
Click to collapse
I know I could simply flash it from twrp and try but, except for OTG working, are there any particular reasons to use this instead of twrp?
I've read that OrangeFox is based on twrp, but offers a better support to Treble than twrp.
asusgarb said:
So what needs to be done to have a working FP sensor? But it's broken even without root?
---------- Post added at 06:03 PM ---------- Previous post was at 05:55 PM ----------
I know I could simply flash it from twrp and try but, except for OTG working, are there any particular reasons to use this instead of twrp?
I've read that OrangeFox is based on twrp, but offers a better support to Treble than twrp.
Click to expand...
Click to collapse
Having also magisk/app manager, flashlight(if anyone would ever use it in recovery), password change. Just try it and check yourself.
Hi!
Switch to this recovery today. I'm having some trouble, stucked in a bootlooad: realme white logo and reeboots to recovery. Can someone help me?
I've tried the normal procedure, with the latest rom from Realme support in UK, after wiping system and data. No good.
What should I do? Do I need to install other rom? What about vbmeta? What should I wipe different?
johnnyjoe said:
Hi!
Switch to this recovery today. I'm having some trouble, stucked in a bootlooad: realme white logo and reeboots to recovery. Can someone help me?
I've tried the normal procedure, with the latest rom from Realme support in UK, after wiping system and data. No good.
What should I do? Do I need to install other rom? What about vbmeta? What should I wipe different?
Click to expand...
Click to collapse
It's a issue with vbmeta. You have to flash vbmeta via fastboot with disable flags:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Jerry08 said:
It's a issue with vbmeta. You have to flash vbmeta via fastboot with disable flags:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Hi @Jerry08! I've tried that, many times, but no luck. I get the "fastboot.exe: unknown option -- disable-verity" error.
I've tried to download all short of adb/fastboot versions, I've installed the latest android studio, minimal adb, etc., but I can't find a way to get a fastboot that works.
I'm sure that my phone is seen after typing fastboot devices. I'm open my powershell window on the folder that has the files.
Can you please help? I'm not sure what I'm doing wrong. Thanks! : )
---------- Post added at 12:39 PM ---------- Previous post was at 12:14 PM ----------
[/COLOR @Jerry08, I think I get it to work:
C:\vbmeta>fastboot devices
513a895e fastboot
C:\vbmeta>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (0 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
After that, It keeps rebooting to recovery.
How can I format and install everything from scratch?
Here's what happened.
Yesterday, I tried to reboot to TWRP but, for some reason I can think off, I couldn't. I thought to try oragefox. When I was installing oragefox, and since I got the fastboot error, I maybe installed vbmeta and then the recovery - or I installed it without vbmeta, can't be sure now. After that, it kept rebooting to recovery. After a while, since I could'n fix it, I eraser caches, system and data and tried to flash the rom from scratch. No luck, I can't pass the reboot to recovery. I switch back to twrp, oragefox sometime got a full black screen and only the flash worked by vol up and power, and it was difficult o restart the phone.
Thanks! : )
What can I do to get my phone back?
johnnyjoe said:
It's a issue with vbmeta. You have to flash vbmeta via fastboot with disable flags:
Hi @Jerry08! I've tried that, many times, but no luck. I get the "fastboot.exe: unknown option -- disable-verity" error.
I've tried to download all short of adb/fastboot versions, I've installed the latest android studio, minimal adb, etc., but I can't find a way to get a fastboot that works.
I'm sure that my phone is seen after typing fastboot devices. I'm open my powershell window on the folder that has the files.
Can you please help? I'm not sure what I'm doing wrong. Thanks! : )
---------- Post added at 12:39 PM ---------- Previous post was at 12:14 PM ----------
[/COLOR @Jerry08, I think I get it to work:
C:\vbmeta>fastboot devices
513a895e fastboot
C:\vbmeta>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (0 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
After that, It keeps rebooting to recovery.
How can I format and install everything from scratch?
Here's what happened.
Yesterday, I tried to reboot to TWRP but, for some reason I can think off, I couldn't. I thought to try oragefox. When I was installing oragefox, and since I got the fastboot error, I maybe installed vbmeta and then the recovery - or I installed it without vbmeta, can't be sure now. After that, it kept rebooting to recovery. After a while, since I could'n fix it, I eraser caches, system and data and tried to flash the rom from scratch. No luck, I can't pass the reboot to recovery. I switch back to twrp, oragefox sometime got a full black screen and only the flash worked by vol up and power, and it was difficult o restart the phone.
Thanks! : )
What can I do to get my phone back?
Click to expand...
Click to collapse
Did you wipe or format data(option where you type "yes")? The best you can do now is to format data(option where you type "yes") and try boot to os. And if it does not help, than follow Updating colorOS via Custom Recovery and as last step format data(option where you type "yes").
Now for the RUI users.
There's still a lot issues i face in rui. So BEWARE! Like today I updated Magisk Canary to latest and got bootloop, couldn't boot to recovery and data partition got ****ed up. I had to flash ofox via fastboot and format data to get it back working.
Jerry08 said:
Did you wipe or format data(option where you type "yes")? The best you can do now is to format data(option where you type "yes") and try boot to os. And if it does not help, than follow Updating colorOS via Custom Recovery and as last step format data(option where you type "yes").
Now for the RUI users.
There's still a lot issues i face in rui. So BEWARE! Like today I updated Magisk Canary to latest and got bootloop, couldn't boot to recovery and data partition got ****ed up. I had to flash ofox via fastboot and format data to get it back working.
Click to expand...
Click to collapse
@Jerry08, format data, after installing rom, did work! Thanks a lot. : )
I did format data to install rom. After installing the rom I would get the phone to bootloop. Formating data after the rom was installed did solve it.
Thank you, one more time. : )
P1f said:
By any chance was fingerprint working after installing RUi using this recovery?
There are reports of FP broken when using twrp
Click to expand...
Click to collapse
FP works fine for me using this recovery before i update to rui i turned of lock screen password and booted to orange fox than wiped dalvik cache , cache, system. vendor and internal storage kept un touched than flashed rui after that i try to reboot back to recovery to install magisk but internal storage is not decting so i reboot to system and phone booted to rui every thing works fine sofar now finding a way to root it
Jerry08 said:
Did you wipe or format data(option where you type "yes")? The best you can do now is to format data(option where you type "yes") and try boot to os. And if it does not help, than follow Updating colorOS via Custom Recovery and as last step format data(option where you type "yes").
Now for the RUI users.
There's still a lot issues i face in rui. So BEWARE! Like today I updated Magisk Canary to latest and got bootloop, couldn't boot to recovery and data partition got ****ed up. I had to flash ofox via fastboot and format data to get it back working.
Click to expand...
Click to collapse
Exact same thing happened to me, and i did the same format data to fix it, I thought it was my fault somehow.
I will stay unrooted for now in order to use fingerprint and since Safetynet check was failing for me anyway ever since the server side change from Google
{
"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/10.0/README.mkdn
Downloads
Official Website
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partitions zip is crucial in order to prevent bricks. It only needs to be done if you're coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.
Only use TWRP version 3.3.1-0, it has an advanced option for recovery bootloop fix. Sorry for some hassles with TWRP. It is not ROM related but the version I use works 100% of the time.
My apologies for any confusion/problems flashing!
Preparation for A/B Roms:
01. Download TWRP version 3.3.1-0 (do not use any other version)
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use the terminal to boot the latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmware.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash GAPPS + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
SOURCES:
ROM: https://github.com/crdroidandroid
Changelog::
https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_ocean.txt
Known issues:
<!-- list here -->
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
© 2020 GitHub, Inc.
XDA:DevDB Information
CrDroid, ROM for the Moto G7 Power
Contributors
Rondeau79
Source Code: https://github.com/Rondeau79/android_kernel_motorola_sdm632
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest TWRP unlocked bootloader
Based On: AOSP, Lineage OS
Version Information
Status: Stable
Current Stable Version: QQ2A.200305.003
Stable Release Date: 2020-03-22
Created 2020-03-22
Last Updated 2020-06-23
Reserved
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
flash713 said:
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
Click to expand...
Click to collapse
Thanks, this one was a tough task to get done. I don't mind a permissive kernel. I really don't dive too far into the Android system. I am a fan first and a developer second! I still really don't have an understanding of code and stuff. I just go with my instincts.
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
danny8 said:
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
Click to expand...
Click to collapse
You are not bricked. When coming from one version of android to another a clean flash must be done. You can dirty flash after that. Wipe both boot slots and then go about flashing like normal. First boot takes a while. It won't boot without wiping the system partition.
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
D13Gho said:
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
Click to expand...
Click to collapse
With the A/B partitions scene. When you flash a ROM it will be installed to the opposite slot. If you are on A then the zip will be installed to B and vica versa. Gapps are flashed after you reboot to recovery when you are on the boot slot the ROM was installed on same as Magisk.
Thank you, Rondeau79. I got it installed.
It looks great!
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Johnfoo19 said:
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Click to expand...
Click to collapse
Give it a little time to set in. Usually a fresh install takes a bit.
danny8 said:
Thank you, Rondeau79. I got it installed.
It looks great!
Click to expand...
Click to collapse
You're welcome.
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
cgrimm9 said:
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
Click to expand...
Click to collapse
Go to display styles and wallpapers to change to colors.
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
n00b Samurai said:
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Click to expand...
Click to collapse
Sorry there isn't, I can't change the base features of the ROM. However you can change the color and thickness of the bar and it's position on the screen.
You can always adjust the screen in order to account for the notch. It's in the developer settings.
barados742 said:
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
Click to expand...
Click to collapse
You need an external sdCard for flashing ROMs. Wiping the user partitions properly is essential for a properly working ROM. If you just have internal storage then the installation of an OS won't be done right.
Thanks for the reply! I just bought an SD card and will try it tomorrow and will respond if it worked.
Good morning, guys I tried to install on my MOTO G 7 POWER 3/32 and the rom does not install says it is not compatible with the system. Any tips?
{
"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:
/*
* 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.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's not working:
Moto Fingerprint Gestures
You tell me
Instructions:
Download the ROM
Backup each and every partition from TWRP Recovery(optional)
Make a full wipe (system, vendor, data, cache, dalvik)
Flash LineageOS Package
Flash gapps
And at last Reboot!
[First boot will take few minutes]
Clean Flash is always recommended!
Downloads:
ROM
GAPPS
XDAevDB Information
LineageOS 17.1 for Ali, ROM for the Moto G6
Contributors
@BetoxxDios
@Electimon
@abhishek_d9
@jeangraff30
ROM OS version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked bootloader, Custom recovery
Based On: AOSP
Version information
Status: Stable
Current Stable Version: LineageOS
Stable Release Date: 2020-10-06
Created 2020-10-06
Last Updated 2020-10-06
Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.
roypen said:
Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.
Click to expand...
Click to collapse
Hi, I request to Moderators move the thread to that section. I don't have permissions to move it.
tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint
tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint
Thank you
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP
fwiep said:
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP
Click to expand...
Click to collapse
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit
nightmw said:
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit
Click to expand...
Click to collapse
Thanks for the reply. I used twrp-3.4.0-0-ali, downloaded from the official download page.
Is there a special download page for 64bit TWRP?
Kind regards,
FWieP
tomarc said:
You can find it here : https://forum.xda-developers.com/moto-g6/development/twrp-twrp-64-bit-ali-t4093879
Click to expand...
Click to collapse
Once again: thank you all. I downloaded the mali.img and booted TWRP from it.
Then, I flashed the new LineageOS 17.1 and OpenGapps - without any problems, warnings or errors.
If there is no way to flash TWRP into the recovery partition permanently, I can live with that.
Most important thing is, I can flash the system partition when needed.
Hope to see more of your work!
Kind regards,
FWieP
BetoxxDios said:
What's not working:
Moto Fingerprint Gestures
You tell me
Contributors
@BetoxxDios
@Electimon
@abhishek_d9
@jeangraff30
Click to expand...
Click to collapse
Having flashed this ROM a few days ago, I find it nearly perfect. Nearly
the October 2020 security patches are available from LineageOS; can they be included?
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself. Perhaps contribute, at least providing a mirror for the ROM files?
If not you (@BetoxxDios), perhaps the other contributors (@Electimon, @abhishek_d9, @jeangraff30) ?
Thanks!
Kind regards,
FWieP
failed to load kernel!
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?
Close, but no cigar - yet
fwiep said:
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself.
Click to expand...
Click to collapse
Thanks @BetoxxDios for providing the links to kernel, device and vendor trees in a private message.
After expanding the RAM of my machine to 16GB and some very educational experiments, the build finally succeeded.
TWRP flashed the ROM without any errors. Yeah!
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
P.S. For the moment, I've flashed @BetoxxDios' original ROM. It's better (and safer) than Motorola's stock firmware.
fwiep said:
.
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Cheers.
Click to expand...
Click to collapse
Baronstragen said:
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Click to expand...
Click to collapse
Thanks for the tip.
I'm afraid this is another issue - I haven't flashed any Gapps with my ROM (yet), and have never even used Magisk before.
@BetoxxDios has shown me a way to get logfiles during boot: build an -eng variant instead of -user or -userdebug.
Now, we're investigating what's going wrong. To be continued!
Kind regards,
FWieP
tomarc said:
Yes, you can flash it permanently :
Fastboot flash recovery xxx.img ; xxx.img being the name of the recovery file.
Click to expand...
Click to collapse
Up until today, I thought this wouldn't work. When doing so, fastboot would say:
Code:
writing 'recovery'...
(bootloader) Image not signed or corrupt
And thus, I thought it had not flashed at all.
Today, I read elsewhere on this forum, to simply ignore this message and check whether it flashed. It actually has!
So, thank you, once again
Kind regards,
FWieP
---------- Post added at 17:22 ---------- Previous post was at 17:08 ----------
fwiep said:
Now, we're investigating what's going wrong. To be continued!
Click to expand...
Click to collapse
And continue it does.
Right from the start, while building this ROM, I got an error about an undefined shared library: libqsap_sdk in /device/motorola/ali/libshims/Android.mk.
I saw it was in a section marked "optional", so I commented it out. And the build succeeded. Yes! After flashing, I got the looping boot-animation. D'oh!
But then, while trying to build another ROM (Resurrection Remix OS 8.6.3 by @abhishek_d9), I got the same error.
I again commented the section out, built the ROM successfully, but got the same looping boot-animation after flashing.
So, XDA to the rescue: I found this post which explains to include '/system/qcom' from LineageOS to get that libqsap_sdk included. I've added it to my roomservice.xml and have started another build. It looks very promising.
Maybe case solved? I'll let you know.
Update
Close, but no cigar. The looping boot-animation still persists. I'll investigate further...
Kind regards,
FWieP
whats-in-a-name said:
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?
Click to expand...
Click to collapse
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?
Solved 'kernel not found'
whats-in-a-name said:
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?
Click to expand...
Click to collapse
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system
whats-in-a-name said:
Solved 'kernel not found'
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system
Click to expand...
Click to collapse
I tried all of that and keep getting "updater process ended with ERROR: 255 Error installing zip file...." Any way to fix this issue? I'm on XT1925-6 32gb.
Never mind, I had the wrong TWRP installed like a dope.
I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!
I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!