Development [ROM] [OOS12FW] RisingOS v1.1 Android Project [dre] [UNOFFICIAL] [Updated June 16] - OnePlus Nord N200 5G

{
"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"
}
Proudly Presenting RisingOS for OnePlus Nord N200 5G [Dre] !!!
What is RisingOS?
RisingOS is a Open Source Aftermarket Android Operating System that aims to deliver unique and refreshing android experience.
Based on Android 13 | Tiramisu QPR2 | with LineageOS
Screenshots
Device specific changes
Based on OOS 12 C.23 Firmware, Flashing OOS 12 firmware is a must before installing
Known Issues:
Same as LineageOS 20
Credits
@andr01dfr3ak - for Device Tree, Kernel, Vendor tree, and sooooo much ground work for supporting the sm4350 platform.
Tattoorepairman (aka Howie Feltersnatch on Telegram) for letting me use his dev rig for this project.
Notes
Download Link: https://androidfilehost.com/?w=files&flid=338327
Installation Guide
Sideload
1. fastboot flash the 4 recovery image from download link under the "Recovery_Files" directory
2. Reboot device into recovery mode
3. Enter ADB sideload mode
4. adb sideload ROM.zip
5.Wipe data/cache/dalvik-cache
6. Sideload preferred zip files (magisk, etc.)
7. Reboot to system
Android OS version: 13.0.0_r43
Security patch level: May 2023
Build author/Device Maintainer: Travisholt92
Kernel source code: https://github.com/LineageOS/android_kernel_oneplus_sm4350
Firmware source code: https://github.com/risingTechOSS
Firmware created by: The risingOS Team & ME
Based on OOS 12 C.23 Firmware
Telegram group: https://t.me/YeetROMs

Can you point to the C.23 firmware that is a requirement for this ROM?
I don't see that in the list of available firmware for N200.
https://www.getdroidtips.com/oneplus-nord-n200-5g-stock-firmware/

Are you gonna make more updates to the core version or are you gonna focus on the gapps version now? And what’s the difference because I have the core version but there’s still gapps that can be turned off is it the same way with the gapps version? Also can I just upgrade to the gapps version?

can you use the same method as lineage upgrade os method to sideload this from los 19.1?

talejandroamazom said:
can you use the same method as lineage upgrade os method to sideload this from los 19.1?
Click to expand...
Click to collapse
No lineage 19.1 is based on Android 11 stock firmware. You have to upgrade your stock firmware to Android 12 before flashing this build.

Curiously said:
Are you gonna make more updates to the core version or are you gonna focus on the gapps version now? And what’s the differencek because I have the core verbutpj butpj thKeepere’s still gapps that can be turned off is it the same way with the gapps version? Also can I just upgrade to the gapps version?
Click to expand...
Click to collapse
GAPPS version is the only one I'm supporting now (it just has a few extra apps installed).
The "Core" version was using flags for minimal GAPPS functionality. Builds without GAPPS would have been labeled "Vanilla" if I would have made it. I figure there's no point in supporting GAPPS and gappsless builds when GAPPS is easily disabled within the ROM.

zm55 said:
Can you point to the C.23 firmware that is a requirement for this ROM?
I don't see that in the list of available firmware for N200.
https://www.getdroidtips.com/oneplus-nord-n200-5g-stock-firmware/
Click to expand...
Click to collapse
I'm running these builds TMO C.21 firmware. C.23 specifically is not required, though that is what the vendor blobs are based on.

Travisholt92 said:
No lineage 19.1 is based on Android 11 stock firmware. You have to upgrade your stock firmware to Android 12 before flashing this build.
Click to expand...
Click to collapse
thanks, also i flashed it and did everything right but when i boot in the touchscreen wont respond, is there something to fix this

talejandroamazom said:
thanks, also i flashed it and did everything right but when i boot in the touchscreen wont respond, is there something to fix this
Click to expand...
Click to collapse
Which stock firmware version are you running?

Travisholt92 said:
Which stock firmware version are you running?
Click to expand...
Click to collapse
c.23 de2117

talejandroamazom said:
c.23 de2117
Click to expand...
Click to collapse
Did you flash the "copy-partitions" zip in recovery to make sure the c.23 firmware is on both slots?

Travisholt92 said:
Did you flash the "copy-partitions" zip in recovery to make sure the c.23 firmware is on both slots?
Click to expand...
Click to collapse
yes i did

talejandroamazom said:
yes i did
Click to expand...
Click to collapse
Can you get a logcat and email it to me @ [email protected]
USB debugging should still work on first boot without enabling it in dev options.

talejandroamazom said:
yes i did
Click to expand...
Click to collapse
Also, could you test to see if you have the same issue with LineageOS 20 or Pixel experience? Both of those are based on the same firmware.
I occasionally encounter this issue in recovery but haven't had it happen in the ROM

Travisholt92 said:
GAPPS version is the only one I'm supporting now (it just has a few extra apps installed).
The "Core" version was using flags for minimal GAPPS functionality. Builds without GAPPS would have been labeled "Vanilla" if I would have made it. I figure there's no point in supporting GAPPS and gappsless builds when GAPPS is easily disabled within the ROM.
Click to expand...
Click to collapse
Can I convert to the gapps version from the core? Or do I have to factory reset?

Curiously said:
Can I convert to the gapps version from the core? Or do I have to factory reset?
Click to expand...
Click to collapse
You can dirty flash

Travisholt92 said:
Also, could you test to see if you have the same issue with LineageOS 20 or Pixel experience? Both of those are based on the same firmware.
I occasionally encounter this issue in recovery but haven't had it happen in the ROM
Click to expand...
Click to collapse
wait forget it it works! i forgot to sideload the zip file and i thought it did bc it said install complete

talejandroamazom said:
wait forget it it works! i forgot to sideload the zip file and i thought it did bc it said install complete
Click to expand...
Click to collapse
Glad to hear you got it working

If anyone is prepared to do the legwork I have a firmware flashable zip with instal scritps from my op 7 pro which could be modified to flash the appropriate firmware to a n200...replace all the partition images, change the device checks etc. I'm not going to straight out attach it because I don't want anyone trying to patch an op 7 pro firmware file on their n200.

famewolf said:
If anyone is prepared to do the legwork I have a firmware flashable zip with instal scritps from my op 7 pro which could be modified to flash the appropriate firmware to a n200...replace all the partition images, change the device checks etc. I'm not going to straight out attach it because I don't want anyone trying to patch an op 7 pro firmware file on their n200.
Click to expand...
Click to collapse
can i participate in this as a tester

Related

[ROM][OREO][OFFICIAL] lineage-15.1 for Pixels (marlin/sailfish)

Official 15.1 nightlies have been discontinued.
Go here for the official 16.0 thread.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki.
Important Info
Make sure you have the vendor, radio, & bootloader img's installed, from the stock oreo 8.1 OPM4.171019.021.P1 July 2018 factory image. More info below.
Download Links
marlin rom: https://download.lineageos.org/marlin
marlin vendor, radio, & bootloader img's: https://androidfilehost.com/?w=files&flid=278595
marlin twrp: https://twrp.me/google/googlepixelxl.html
sailfish rom: https://download.lineageos.org/sailfish
sailfish vendor, radio, & bootloader img's: https://androidfilehost.com/?w=files&flid=278596
sailfish twrp: https://twrp.me/google/googlepixel.html
google apps (Optional): https://wiki.lineageos.org/gapps.html
root su addon (Optional): https://download.lineageos.org/extras Note: Use arm64 zip. After installing the su addon, you can enable root in developer options.
Instructions
Initial Install
NOTE#1: Make sure you have the correct vendor, radio, & bootloader img's installed in BOTH slots before installing lineage. They can be extracted from the oreo 8.1 OPM4.171019.021.P1 July 2018 factory image or use the ones in the download section above that I already extracted for you. You can flash them using the following commands:
fastboot flash --slot all vendor VendorFileName.img
fastboot flash --slot all radio RadioFileName.img
fastboot flash --slot all bootloader BootloaderFileName.img
NOTE#2: The official mindthegapps build that's linked in the wiki are very minimal (like opengapps pico), so i made my own mindthegapps build that is pretty much the same as opengapps nano. download link
NOTE#3: If you're a Project Fi or Sprint customer, you need some extra gapps, so use this one instead. download link
NOTE#4: If you want to update from my unofficial 15.1 build to official without wiping, you can follow the "How to dirty flash an official weekly over an unofficial build" steps here.
1. boot into twrp and wipe data and system
2. flash rom zip
3. flash twrp zip
4. in twrp main menu, select reboot then recovery (this will reboot you into the other slot)
5. flash gapps zip (optional)
6. flash su addon zip for root (optional)
Reboot & enjoy.
Updating
If you've already done the initial install, then you can use the LineageOS Updater to install new builds. It's in settings->system->about phone->lineageos updates.
It will give you a notification when a new build is available.
Weather Provider Addons (Optional)
For those that like to use the lineage cLock widget, here are some weather provider apk's you can use that i compiled.
https://www.androidfilehost.com/?w=files&flid=243785
Changelog
https://download.lineageos.org/marlin/changes/
Bug Reporting
If a bug is discovered, confirm it with other users in this thread, then report it following our wiki here: https://wiki.lineageos.org/bugreport-howto.html
LineageOS Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Source Code:
Device tree: https://github.com/LineageOS/android_device_google_marlin/tree/lineage-15.1
Kernel tree: https://github.com/LineageOS/android_kernel_google_marlin/tree/lineage-15.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-15.1
Android version: 8.1.0 Oreo
Kernel version: Linux 3.18.70
Omg LOS 15 ! Any Sailfish compatibility ?
Nice
Nice!!!!! Bugs?
Anyone Flash this yet?
Thanks very much for this. Op instructions were flawless and booted right up. Feel's good to be running los, everything I've tested/used works perfectly
billiepreks said:
Any Sailfish compatibility ?
Click to expand...
Click to collapse
nope, sorry. But it can be built and works fine. I know a person that uses it.
TotoBerto02 said:
Bugs?
Click to expand...
Click to collapse
Only a couple things come to mind that are worth mentioning...
Livedisplay has not been implemented yet. But Night Display is working fine.
And I cherry-picked the buttons settings changes into this rom, which is still a work-in-progress. So some of them don't work yet, but most do.
JS.zip said:
Op instructions were flawless...
Click to expand...
Click to collapse
Thanks to @kgjel for that :good:
He gave me a set of detailed instructions that I revised slightly and put in the first post.
JS.zip said:
Thanks very much for this. Op instructions were flawless and booted right up. Feel's good to be running los, everything I've tested/used works perfectly
Click to expand...
Click to collapse
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
Same problem here, i get about 3-5 Boot Loops and then it finally stops at the G with the line under. I tried multiple times...
mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
I saw that as well. I was on 8.1, I took the main op too be correct.
mrhds said:
The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013.
Click to expand...
Click to collapse
thanks. fixed.
unfortunately, flashing stuff on a marlin is a major pain in the rear. very easy to mess up.
make sure you follow the steps EXACTLY.
AndroidDevices said:
Same problem here, i get about 3-5 Boot Loops and then it finally stops at the G with the line under. I tried multiple times...
Click to expand...
Click to collapse
mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
The lineage MK file linked in the detailed instructions shows OPM1.171019.011. Not sure which one you're looking at? The link goes here: https://github.com/razorloves/android_device_google_marlin/blob/15.1-testing/lineage.mk#L22
hokiealumnus said:
The lineage MK file linked in the detailed instructions shows OPM1.171019.011. Not sure which one you're looking at? The link goes here: https://github.com/razorloves/android_device_google_marlin/blob/15.1-testing/lineage.mk#L22
Click to expand...
Click to collapse
I read the detailed instructions, im not looking at what he's looking at...FYI
TWRP 3.2.0-0 is unable to decrypt the factory "opm1" /data store. 3.2.1-0 is able to decrypt but fails to flash LOS. Something is not quite correct here.....
carbinefreak said:
TWRP 3.2.0-0 is unable to decrypt the factory "opm1" /data store. 3.2.1-0 is able to decrypt but fails to flash LOS. Something is not quite correct here.....
Click to expand...
Click to collapse
Do you have a pin or password on your lockscreen? If so you must remove it first
so are you the new maintainer? officially?
Zehlek said:
Do you have a pin or password on your lockscreen? If so you must remove it first
Click to expand...
Click to collapse
Good catch, Removed the password and ran through the procedure just fine. Phone just finished first boot and is in the process of updating apps now......
Thanks! Super Cool!
@razorloves is this always required when flashing any rom on Maril?
f - Go to `Mount` and select to mount `Vendor`. Go back to TWRP home
g - Go to `Advanced` - > `File Manager`. Navigate to /vendor/overlay/, then click the checkmark in the bottom right. Select `Delete`.
Click to expand...
Click to collapse
Thanks to @razorloves for making me actually read directions and stop being such a noob....
jmiller3342 said:
so are you the new maintainer? officially?
Click to expand...
Click to collapse
Yes. Intervigil is a maintainer too.
Zehlek said:
@razorloves is this always required when flashing any rom on Maril?
Click to expand...
Click to collapse
not necessarily.
Google put a couple theme apk's and frameworks apk in that folder. It will override a lot of changes we make to our custom rom. So I think it's best to remove it.
You can see my comments in this change to give you an idea of one of the problems that frameworks apk can cause. https://review.lineageos.org/198569
When you flash stock rom or flash the vendor img from the stock rom, it will replace that folder that was deleted.

[WIP][Ali] Android AOSP 9.0 Pie (android-9.0.0_r1)

{
"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"
}
Hello all,
I tried to play a bit with AOSP and thank to phhusson experiments with Treble I managed to have an AOSP 9.0 Pie ROM for our Moto G6, of course this is a WIP, I still have a lot of stuff to work on but it's a good starting point!
Since I use my Moto G6 also for my work I can't backup/format/flash my device every day, would be very very nice if anyone would like to help me to buy a new one dedicated to the development.
The goal is 250CHF (see here: https://goo.gl/mWeKFz)
If you would like to contribute you can donate here: paypal.me/pools/c/88dRQdo7o5
BIG thanks!
What works:
RIL
SMS
Camera
WiFi
Mobile data
Bluetooth
Root
What doesn't works / Not tested yet:
NFC
Dolby Audio
FM Radio
Fingerprint
Other?
Next steps:
Update to latest Android version
Add GApps
Add Browser
Add WebView
Update the kernel
Cleanup & optimize
Download:
[26.09.2018][TESTING] Moto G6
SHA1: 53dcbf3d678e2b985556edf02e109063a674ed41
How to install:
!!! First all you must have unlocked the bootloader.
Extract the .tar.gz file.
Put the device in fastboot mode: Press and keep pressed Volume - and then press and keep pressed Power for about 2-3 sec.
Flash .img file using fastboot with:
Code:
$ fastboot flash system system.img
Once done, reboot with:
Code:
$ fastboot reboot
Have Fun!
XDA:DevDB Information
Android AOSP 9.0 Pie, ROM for the Moto G6
Contributors
secuflag
Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/tree/oreo-8.0.0-release-ali
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Abandoned
Current Beta Version: Pie-R01
Beta Release Date: 2018-09-26
Created 2018-09-26
Last Updated 2019-03-19
Reserved
I'm already installing it, thanks dude
whats different between this and the 9.0 GSI available on the project treble forums?
Does VoLTE work?
Does it work moto g6 play
Anyone know if someone is developing any rom for the G6 Play?
Dadud said:
whats different between this and the 9.0 GSI available on the project treble forums?
Click to expand...
Click to collapse
I don't know, never saw that ROM.
teckgiik101 said:
Does VoLTE work?
Click to expand...
Click to collapse
It should since the RIL works fine but I can't test it.
Ken.McVishen said:
Does it work moto g6 play
Click to expand...
Click to collapse
I don't know. Install this app and post the result.
secuflag said:
I don't know, never saw that ROM.
It should since the RIL works fine but I can't test it.
I don't know. Install this app and post the result.
Click to expand...
Click to collapse
LTE didn't work for me on the Treble project (phh's 9.0 GSI)
secuflag said:
I don't know, never saw that ROM.
It should since the RIL works fine but I can't test it.
I don't know. Install this app and post the result.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
I really appreciate the work you are doing here! :good:
What about SafetyNet? Does it pass or fail? It's kinda important to me.
SnapDrag910 said:
What about SafetyNet? Does it pass or fail? It's kinda important to me.
Click to expand...
Click to collapse
Didn't test it yet, it's not a priority at the moment.
secuflag said:
Didn't test it yet, it's not a priority at the moment.
Click to expand...
Click to collapse
Oh okay. Actually I don't have the device. I'll probably get it next week, and as an android enthusiast, I couldn't stand Lenovo pushing updates late to the Moto G6 so I got excited when a Custom kernel and now your GSI showed up... Thanks for your work again.
@secuflag
I was successfully able to root phh's AOSP GSI.
If this ROM is based on that, root might most likely work on this one as well.
I'm just waiting to be able to flash gapps, that's the only thing stopping me from moving to 9.0
I just tested root access, it works :good:
Anyone tested this with the moto g 6 play?
I have one more question. Is this a 32bit or 64bit firmware? I'm really interested in using the GCam port with this device.
teckgiik101 said:
@secuflag
I was successfully able to root phh's AOSP GSI.
If this ROM is based on that, root might most likely work on this one as well.
I'm just waiting to be able to flash gapps, that's the only thing stopping me from moving to 9.0
Click to expand...
Click to collapse
you can flash Gapps just fine, back when treble roms didnt come with android go gapps baked in, you would have to boot the phone up once, reboot into recovery, install gapps from unencrypted sd card or internal memory if you're using the encryption disabler zip, and then wipe/reboot again.
SnapDrag910 said:
I have one more question. Is this a 32bit or 64bit firmware? I'm really interested in using the GCam port with this device.
Click to expand...
Click to collapse
G6 is not 64 bit compatible yet, there's a 64bit twrp out there and progress is being made, but nothing public yet.
Dadud said:
G6 is not 64 bit compatible yet, there's a 64bit twrp out there and progress is being made, but nothing public yet.
Click to expand...
Click to collapse
But The Moto G6 runs on Snapdragon 450 which is a 64BIT SoC, so...? I thought maybe This GSI would be 64bit?
SnapDrag910 said:
But The Moto G6 runs on Snapdragon 450 which is a 64BIT SoC, so...? I thought maybe This GSI would be 64bit?
Click to expand...
Click to collapse
technically yes, but moto decided to compile everything in 32bit. 64 bit will come in time, but probably not for a few months.

[TWRP][UNOFFICIAL] TWRP [64 Bit][3.7.0]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Unlocked bootloader is required.
{
"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
To temporarily boot this recovery:
fastboot boot twrprolakv5.img
To permanently install it:
fastboot flash recovery twrprolakv5.img
Download
SourceForge
Troubleshooting
1.: Permanently install show error.
R.: You need to boot recovery and install the Image by Recovery to Recovery
2.: Recovery missing afeter install and boot into stock (OEM) system.
R.: Stock (OEM) system clear 64 bits recovery by defaut, so you need to install the TWRP 64bits install a Custom ROM right away.​
Code:
Changelog:
2021-09-02
- First release
2021-12-08
- Tried to fix OTG test it!!!
2022-03-31
- Fixed format "auto" when format External SD-CARD
- Bump to version 3.6.1*
2022-07-09
- Changed vfat to exfat on SD format options.
- Bump to version 3.6.2
2022-10-15
-Update kernel prebuilt source to match with last kernel sources
- Bump to version 3.7.0
XDAevDB Information
TWRP for Moto G6, Tool/Utility for the Moto G6
Contributors
@jeangraff30
@brunogroa
Version Information
Status: Stable
Kernel: 3.18.140-Stable
TWRP: Source
Device: Source
Created 2021-09-02
Last Updated 2021-12-08
Thank you so much for the hard work mate! ✌
One question:
Is the FW of Moto G6 (Ali) upgradable?
Or it comes included with the ROM zip?
Also, I just flashed latest version and it says it's 3.6.1, not 3.6.2. Is that right?
rambomhtri said:
One question:
Is the FW of Moto G6 (Ali) upgradable?
Or it comes included with the ROM zip?
Also, I just flashed latest version and it says it's 3.6.1, not 3.6.2. Is that right?
Click to expand...
Click to collapse
ohh sorry for this, is 3.6.1 i just writed wrong XD
brunogroa said:
ohh sorry for this, is 3.6.1 i just writed wrong XD
Click to expand...
Click to collapse
Ok, thanks!
What about this question?
rambomhtri said:
Is the FW of Moto G6 (Ali) upgradable?
Or it comes included with the ROM zip?
Click to expand...
Click to collapse
rambomhtri said:
Ok, thanks!
What about this question?
Click to expand...
Click to collapse
FW you just need to flash most recently STOCK ROM for your region... just it, this never changes in rom flash
brunogroa said:
FW you just need to flash most recently STOCK ROM for your region... just it, this never changes in rom flash
Click to expand...
Click to collapse
How can we check the FW version?
The baseband maybe?
I'm pretty sure I updated 2 years ago or more, I don't remember, to the latest official stock ROM via OTA. I wanted to check the numbers, just that.
rambomhtri said:
How can we check the FW version?
The baseband maybe?
I'm pretty sure I updated 2 years ago or more, I don't remember, to the latest official stock ROM via OTA. I wanted to check the numbers, just that.
Click to expand...
Click to collapse
Running 'fasboot getvar all' is a good way to check and compare values. My US Retail G6 was updated through OTA to the final official update PPS29.118-15-11-16. Bootloader version 'MBM-2.1-ali_retail-a49aaf13a93-200423', baseband 'M450_23.31.10.89R ALI_NA_CUST' and release key '3afd9'.
pocky-stick said:
Running 'fasboot getvar all' is a good way to check and compare values. My US Retail G6 was updated through OTA to the final official update PPS29.118-15-11-16. Bootloader version 'MBM-2.1-ali_retail-a49aaf13a93-200423', baseband 'M450_23.31.10.89R ALI_NA_CUST' and release key '3afd9'.
Click to expand...
Click to collapse
Yeah, I have the exact same baseband version. Is that enough to guarantee we have the same version and the latest?
rambomhtri said:
Yeah, I have the exact same baseband version. Is that enough to guarantee we have the same version and the latest?
Click to expand...
Click to collapse
It can be tricky with Motorola devices because sometimes elements like the baseband aren't updated each version, see if you notice discrepancies in the other values.
You can always grab the stock PPS29.118-15-11-16 from lolinet and flash it. If you're running a custom ROM, I suggest backing up your data, flashing the entire image, then reinstalling the custom ROM. Attempting to update the radio/bootloader over a custom software has given me a few blankflash-level bricks before.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
brunogroa said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Unlocked bootloader is required.
View attachment 5400275View attachment 5400287
Installation
To temporarily boot this recovery:
fastboot boot twrprolakv5.img
To permanently install it:
fastboot flash recovery twrprolakv5.img
Download
SourceForge
Troubleshooting
1.: Permanently install show error.
R.: You need to boot recovery and install the Image by Recovery to Recovery
2.: Recovery missing afeter install and boot into stock (OEM) system.
R.: Stock (OEM) system clear 64 bits recovery by defaut, so you need to install the TWRP 64bits install a Custom ROM right away.​
Code:
Changelog:
2021-09-02
- First release
2021-12-08
- Tried to fix OTG test it!!!
2022-03-31
- Fixed format "auto" when format External SD-CARD
- Bump to version 3.6.1*
2022-07-09
- Changed vfat to exfat on SD format options.
- Bump to version 3.6.2
2022-10-15
-Update kernel prebuilt source to match with last kernel sources
- Bump to version 3.7.0
XDAevDB Information
TWRP for Moto G6, Tool/Utility for the Moto G6
Contributors
@jeangraff30
@brunogroa
Version Information
Status: Stable
Kernel: 3.18.140-Stable
TWRP: Source
Device: Source
Created 2021-09-02
Last Updated 2021-12-08
Click to expand...
Click to collapse
Hi Guys,
I'm getting this when attempting to flash the TWRP image. Any suggestions?
sternz said:
Hi Guys,
I'm getting this when attempting to flash the TWRP image. Any suggestions?
Click to expand...
Click to collapse
your bootloader is not unlocked ¬¬
brunogroa said:
your bootloader is not unlocked ¬¬
Click to expand...
Click to collapse
I see! Is that the process of getting an unlock code from Motorola as shown at the beginning of the 5 minutes mark in this video
sternz said:
I see! Is that the process of getting an unlock code from Motorola as shown at the beginning of the 5 minutes mark in this video
Click to expand...
Click to collapse
is same in all motorola, turn on unlock on dev options on stock, go to bl an get the code, insert on site, pick the unlock code and unlock (and it will clean all your data on phone), so yes
brunogroa said:
is same in all motorola, turn on unlock on dev options on stock, go to bl an get the code, insert on site, pick the unlock code and unlock (and it will clean all your data on phone), so yes
Click to expand...
Click to collapse
Got it! Thank you for the response and helping a total n00b!
Whats the difference to official twrp for ali?
zitronenmelissa said:
Whats the difference to official twrp for ali?
Click to expand...
Click to collapse
official dont allow to install custom roms cos is only 32 bits.... the uno one is 32/64
Can't imagine the hours in this- thanks!
My error when installing twrprolakv5.img
"Image not signed or corrupt"
Confession- attempted install of twrprolakv5.img with twrp v3.2.3 already installed.
Any brief flashes of wisdom?
brunogroa said:
official dont allow to install custom roms cos is only 32 bits.... the uno one is 32/64
Click to expand...
Click to collapse
Does that still applies to the lastest official version (3.7.0_9-0)?
pocky-stick said:
Running 'fasboot getvar all' is a good way to check and compare values. My US Retail G6 was updated through OTA to the final official update PPS29.118-15-11-16. Bootloader version 'MBM-2.1-ali_retail-a49aaf13a93-200423', baseband 'M450_23.31.10.89R ALI_NA_CUST' and release key '3afd9'.
Click to expand...
Click to collapse
thanks! Double checked and mine is this!

[OFFICIAL] LineageOS 19.1 for Moto G7 Plus

{
"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"
}
Moto G7 Plus
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Moto G7 Plus.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
lake - Official builds
lake - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8998
Amazing!
Thanks a lot for the continuing support!
npjohnson said:
​Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
lake - Official builds
lake - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Click to expand...
Click to collapse
This mean rooted device would not get support here?
when you start doing non-standard things with your phone, people aren't going to be able to help you troubleshoot problems as well. The more you deviate, the less likely people will be willing to help you. That's to be expected. It's the reason I keep things pretty vanilla (LOS + opengapps pico)...
proza said:
This mean rooted device would not get support here?
Click to expand...
Click to collapse
Correct.
NpJ, do you have recommend vendor firmware updates from official moto builds similar to this guide for OnePlus?
Update firmware on fajita | LineageOS Wiki
wiki.lineageos.org
I don't see any link to a similar sorta page from lake:
Info about lake | LineageOS Wiki
wiki.lineageos.org
Just wondering, because I haven't touched Moto ROMs since buying the phone.
retry0001-coffee said:
NpJ, do you have recommend vendor firmware updates from official moto builds similar to this guide for OnePlus?
Update firmware on fajita | LineageOS Wiki
wiki.lineageos.org
I don't see any link to a similar sorta page from lake:
Info about lake | LineageOS Wiki
wiki.lineageos.org
Just wondering, because I haven't touched Moto ROMs since buying the phone.
Click to expand...
Click to collapse
Nope, newest for your device. That's about it.
OK but should we grab the latest MOTO stock ROM, and copy the same partitions over as outlined in the 6T guide? If we do not do that, will it make latest LOS 19 buggy? Out of curiosity, what does *your* vendor patch level date say?
retry0001-coffee said:
OK but should we grab the latest MOTO stock ROM, and copy the same partitions over as outlined in the 6T guide? If we do not do that, will it make latest LOS 19 buggy? Out of curiosity, what does *your* vendor patch level date say?
Click to expand...
Click to collapse
nope - Just as long as you're on latest Android version - say lake, you should be on android 10, doesn't matter which sub version.
Vendor SPL is dependent on lineage, not stock - we build vendor - the 6T didn't used to - so they had to have users flash vendor themselves.
Oh interesting. Thanks for that clarification.
I looked for version 19.1 on the official website and didn't find anything to download. A few hours ago it was available. What happened?
Cool, thanks for the hard work!
fNttRX said:
I looked for version 19.1 on the official website and didn't find anything to download. A few hours ago it was available. What happened?
Click to expand...
Click to collapse
There is a new version built this night ( 20220427) now online. This worked now for me and even the first boot was really fast (~2 min). https://download.lineageos.org/lake
Had issues the whole night with the 20220426 build. I was always in a boot loop after sideloading the 26 version.
Later, I tried to go to Stock Rom first with the Lenovo Rescue and Smart Assistance (to my XT1965-3 (EU) ).
Sideloaded Recovery and Lineage 19.1 again -> bootloop.
Went to bed late, saw a new version right after getting up -> works as expected
First, Thank you @npjohnson for your work!
Do you have a personal donation link?
Version 27 hasn't bootloop
Do you have any problems installing gapps? I can't add google account after installation. i get application error. Wipe doesnt change anything
After installing 27.04 LOS, system updates info shows it is version 26. I can update to 27 but after reboot nothing happens and it still shows 26 with the option to install 27 again.
Can TWRP be used to flash this? If yes, any special version of TWRP needed?
I boot to TWRP using fastboot and not installing it on the phone.
dr.haggis said:
There is a new version built this night ( 20220427) now online. This worked now for me and even the first boot was really fast (~2 min). https://download.lineageos.org/lake
Had issues the whole night with the 20220426 build. I was always in a boot loop after sideloading the 26 version.
Later, I tried to go to Stock Rom first with the Lenovo Rescue and Smart Assistance (to my XT1965-3 (EU) ).
Sideloaded Recovery and Lineage 19.1 again -> bootloop.
Went to bed late, saw a new version right after getting up -> works as expected
First, Thank you @npjohnson for your work!
Do you have a personal donation link?
Click to expand...
Click to collapse
PayPal.me/nolenjohnson
jmozmoz said:
Can TWRP be used to flash this? If yes, any special version of TWRP needed?
I boot to TWRP using fastboot and not installing it on the phone.
Click to expand...
Click to collapse
Probably but I'd just use lineage recovery.
I installed it with the latest TWRP. It bootlooped with flamegapps but installed successfully with mindthegapps.
I install twrp on the system and it has a handy choice to reflash itself after installing the rom. You then must reboot to twrp to add the gapps zip or it will not work.
For anyone else interested I also installed magisk and it works perfectly but be aware of @npjohnson's point re loss of support.
petexd said:
I installed it with the latest TWRP. It bootlooped with flamegapps but installed successfully with mindthegapps.
I install twrp on the system and it has a handy choice to reflash itself after installing the rom. You then must reboot to twrp to add the gapps zip or it will not work.
For anyone else interested I also installed magisk and it works perfectly but be aware of @npjohnson's point re loss of support.
Click to expand...
Click to collapse
Thank you for your answer. Did you do a fresh install/wipe the data partition?
I have currently installed Lineageos 18.1 + Open Gapps for Android 11 (nano). Can I do a dirty flash/install with Lineageos 19 and MindTheGapps?
Which version of Magisk do you use? And which version of TRWP?
jmozmoz said:
Thank you for your answer. Did you do a fresh install/wipe the data partition?
I have currently installed Lineageos 18.1 + Open Gapps for Android 11 (nano). Can I do a dirty flash/install with Lineageos 19 and MindTheGapps?
Which version of Magisk do you use? And which version of TRWP?
Click to expand...
Click to collapse
I did a format data AND wipe with twrp-3.6.1. Make sure you follow the install instructions on twrp for motorola g7+. You need the img file and the zip.
I don't use open gapps- too mush bloat - but I got a bootloop with flamegapps so I followed npj's advice and used mindthegapps.
I didn't try a dirty flash so I don't know but I would go for the full wipe.
Good luck but if you do it properly you shouldn't need it.

Development [ROM][UNOFFICIAL][13][dre] PixelExperience for OnePlus Nord N200 5G [AOSP]

{
"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"
}
(Unofficial) PixelExperience for OnePlus Nord N200 5G [dre]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13
Installation and info
See post #2
Known issues
microSD cards aren't detected unless the SIM card tray is popped out
???
Whats working?
Everything else
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from SourceForge
​
Android OS version: 13
Security patch level: May 2023
Kernel source: https://github.com/lzgmc/kernel_oneplus_sm4350-1
Device tree: https://github.com/lzgmc/device_oneplus_dre
hardware/oplus fork: https://github.com/lzgmc/hardware_oplus
Source code: https://github.com/PixelExperience
Oh boy, another custom ROM!
Make sure to update your device to the latest version of OxygenOS 12 (C.23) BEFORE installing this ROM. Mismatched firmware can cause weird issues.
How do I install this?
Installation is more or less the same as LineageOS. In short, if you're coming from stock:
- Update to the latest version of OxygenOS
- Unlock your bootloader
- Flash the dtbo, vendor_boot, and boot files in fastboot
- Reboot to recovery, wipe data, reboot to recovery again
- Sideload the copy-partitions zip
- Sideload the PixelExperience zip
- Reboot & enjoy
Detailed instructions
Does this work on the T-Mobile/Metro variants?
Yes. Keep in mind that the method to unlock the bootloader on carrier vatiants is different than on the unlocked variant. Once you unlock the bootloader, the rest of the installation procedure is the same.
Is this ROM stable enough for daily use?
I think it is. Check the known issues section to know what's not working before you install.
Does this ROM pass SafetyNet/Play Integrity out of the box?
Yes. Note that installing mods, such as Magisk, may trip SafetyNet/Play Integrity.
Where's PixelExperience Plus?
I didn't feel like building it, sorry.
A note about building PixelExperience:
If you want to build PE for this device, you'll need to make a few modifications:
You'll need the kernel build tools from AOSP. Add
XML:
<project path="prebuilts/kernel-build-tools" name="kernel/prebuilts/build-tools" clone-depth="1" remote="aosp" revision="refs/tags/android-13.0.0_r0.60" />
to your local manifest.
Use my hardware/oplus fork.
Get the proprietary files from TheMuppets.
Thanks to everyone who helped bring custom ROMs to this device, including:
@andr01dfr3ak
@elginsk8r
@Travisholt92
@ArtiicPanda
whats your donation link ?
Does carrier aggregation/LTE+ work??
while charging screen has problems coming back on just backlight black until unplugged then will tun back on and allow to unlock the screen nvm reflashed after going back to stock and just fine
michaelwaycraig67 said:
whats your donation link ?
Click to expand...
Click to collapse
My donation link is the Like button
when I enter the download links it says
''Page Not Found!​Page you are trying to open does not exist. You may have mistyped the address, or the page has been moved to another URL. If you think this is an error contact support.''
is there any way to fix this
talejandroamazom said:
when I enter the download links it says
''Page Not Found!​Page you are trying to open does not exist. You may have mistyped the address, or the page has been moved to another URL. If you think this is an error contact support.''
is there any way to fix this
Click to expand...
Click to collapse
wait nvm im so stupid i had to download it from sourceforge
@lzgmc - thanks a lot for this.
PixelExperience has been my favorite ROM and I have been looking for this for my N200(s) for a while.
Do you think you would be able to provide regular updates for the ROM?
I don't see any update option in the System settings.
Are updates not supported?
The cell network is extremely flaky - going in and out every 2 seconds.
I am using an xfinity mobile (verizon mvno) sim, in case that matters.
zm55 said:
@lzgmc - thanks a lot for this.
PixelExperience has been my favorite ROM and I have been looking for this for my N200(s) for a while.
Do you think you would be able to provide regular updates for the ROM?
Click to expand...
Click to collapse
Yes, once a month.
zm55 said:
I don't see any update option in the System settings.
Are updates not supported?
Click to expand...
Click to collapse
There's no updater app in unofficial builds. You're gonna have to wait for official builds
zm55 said:
The cell network is extremely flaky - going in and out every 2 seconds.
I am using an xfinity mobile (verizon mvno) sim, in case that matters.
Click to expand...
Click to collapse
What firmware are you flashing from?
Thanks a lot for the support..
I'm using the latest firmware from the zip file linked here -
https://www.reddit.com/r/LineageOS/comments/136kkn8
@lzgmc - could you please recommend a device firmware that would go well with this rom?
Currently, I am using DE2117_11_C.16 and the combination is completely unusable. Thankfully, this is not my primary phone so I could wait for this to get fixed.
Unlocked (DE2117_11_C.16)
Full C.16 update
https://android.googleapis.com/packages/ota-api/package/6be3f133f8fb9bbcc30d787679bd7b5da5e30995.zip
There was a problem with my N200 and it got fixed after a device reset. Sorry for the false alarm.
This ROM is quite stellar
zm55 said:
Currently, I am using DE2117_11_C.16 and the combination is completely unusable. Thankfully, this is not my primary phone so I could wait for this to get fixed.
Click to expand...
Click to collapse
You should be using C.23 or later.
lzgmc said:
You should be using C.23 or later.
Click to expand...
Click to collapse
Would you mind pointing me to the C23 firmware that I could download? I am seeing a lot of references to it but I couldn't find any download link to the firmware for N200.
Thanks
zm55 said:
Would you mind pointing me to the C23 firmware that I could download? I am seeing a lot of references to it but I couldn't find any download link to the firmware for N200.
Thanks
Click to expand...
Click to collapse
Sadly, the only way to get this firmware version (at least for now) is by taking OTA while running stock.

Categories

Resources