[OFFICIAL] LineageOS 19.1 for Moto G7 Plus - Moto G7 Plus ROMs, Kernels, Recoveries, & Other De

{
"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.

Related

[ROM][OFFICIAL] LineageOS 14.1 for Nexus 6 (shamu)

15.1 oreo builds are now available. See new thread here:
https://forum.xda-developers.com/nexus-6/orig-development/rom-lineageos-15-1-nexus-6-shamu-t3773143
{
"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. And if you would like to contribute to LineageOS, please visit our Wiki.
Important Info
DON'T USE TWRP 3.0.2-0 OR OLDER WITH LINEAGEOS. IT DOES NOT WORK CORRECTLY. USE NEWEST VERSION HERE
Current lineage 14.1 shamu nightlies are based on the N6F27M October 2017 update from google. So you should be using the radio and bootloader img from that update. They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
Note: The radio and bootloader img is the same as the ones in last month's google update (NGI55D), so if your phone already has them you don't need to flash them.
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Beans GApps (recommend mini)
HEADS UP: When you initially install lineage, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after the fact, you're gonna have a bad time.
SU addon zip: Addon Install zip / Addon Removal zip NOTE: LineageOS does not come with root, so this is now provided for those that want it. The install zip is a one time flash, like gapps. Meaning, it persists when updating to a new LineageOS nightly. REF: https://download.lineageos.org/extras
Changelog
https://download.lineageos.org/shamu/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
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
LineageOS device maintainers:
Elektroschmock, razorloves
Source Code:
Device tree: https://github.com/LineageOS/android_device_moto_shamu/tree/cm-14.1
Kernel tree: https://github.com/LineageOS/android_kernel_moto_shamu/tree/cm-14.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-14.1
Android Version: 7.1.2 Nougat
Kernel Version: Linux 3.10.40
Status: Nightly
Reserved
is f2fs supported in the latest (12-07) nightly build? if it is supported, can you build the latest twrp version with f2fs support?
thanks for the answer and the device support
8zabi said:
is f2fs supported in the latest (12-07) nightly build? if it is supported, can you build the latest twrp version with f2fs support?
thanks for the answer and the device support
Click to expand...
Click to collapse
F2FS is supported since the first CM-14.1 nightly. I'm not maintaining TWRP right now.
Perhaps I will do that in the future but right now I have to less time to do that.
USB tethering seems to be broken in the 20161207 build. When you toggle it on, it immediately turns back off. I went back to 20161206 and it works again.
i am using these nighlys since ~11.24. (maybe), they are stable for dialy usage, only facebook likes to crash to desktop, but who cares
Elektroschmock:
have you got info about the direct boot feature? is it included in this version? cm recovery supports it?
i upgraded from 6.0.1 without wiping /data/media folder, so i have the older full disk encryption
Hurray for official cm14.1!!! And, just a reminder, the latest bootloader and radio are also available as flashable zips here: http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
---------- Post added at 06:41 AM ---------- Previous post was at 06:31 AM ----------
What's the current best practices for flashing gapps? I remember we used to flash gapps with each new nightly. Then in cm13, that was no longer necessary, and, in fact, seemed to mess things up. I've been flashing the latest opengapps with each new cm14.1 nightly, but am not sure if that's necessary or recommended
---------- Post added at 06:48 AM ---------- Previous post was at 06:41 AM ----------
psycho_asylum said:
USB tethering seems to be broken in the 20161207 build. When you toggle it on, it immediately turns back off. I went back to 20161206 and it works again.
Click to expand...
Click to collapse
I have more-or-less the same problem: if I go into settings / tethering & portable hotspot and toggle portable wf-fi hotspot on, it looks like it's trying, but after about a second it says "error"
dbrickg said:
What's the current best practices for flashing gapps? I remember we used to flash gapps with each new nightly. Then in cm13, that was no longer necessary, and, in fact, seemed to mess things up. I've been flashing the latest opengapps with each new cm14.1 nightly, but am not sure if that's necessary or recommended
Click to expand...
Click to collapse
i have flashed gapps two weeks ago and just installed nighlies over them, gapps backup / restore is working flawlessly
Stock kernel in latest night build cm 14.1 force encrypt or not?
Tysovwik said:
Stock kernel in latest night build cm 14.1 force encrypt or not?
Click to expand...
Click to collapse
official cm kernels are always force encrypt
Does google assistant work on this?
Noticing some additional weirdness on 12/7. Double pull-down on the notification shade doesn't work and neither does the home button or the task switcher. Even rolling back to 12/6, it is still broken. Something didn't upgrade correctly when going to 7.1.1.
psycho_asylum said:
Noticing some additional weirdness on 12/7. Double pull-down on the notification shade doesn't work and neither does the home button or the task switcher. Even rolling back to 12/6, it is still broken. Something didn't upgrade correctly when going to 7.1.1.
Click to expand...
Click to collapse
Maybe I don't understand what you mean, but those all seem to be working just fine for me
Hello,
sorry for the noobness
i've been using cyano 13 on my nexus 6 for a while and i'm quite sure i never flashed anything about bootloader or radio
do i need to flash them to use cm14? is this something will wipe all my data? (i'd like to try with a dirty flash..)
Pattagghiu said:
Hello,
sorry for the noobness
i've been using cyano 13 on my nexus 6 for a while and i'm quite sure i never flashed anything about bootloader or radio
do i need to flash them to use cm14? is this something will wipe all my data? (i'd like to try with a dirty flash..)
Click to expand...
Click to collapse
Yes you need the new bootloader and radio for CM-14.1 to work properly.
It won't touch your data.
psycho_asylum said:
USB tethering seems to be broken in the 20161207 build. When you toggle it on, it immediately turns back off. I went back to 20161206 and it works again.
Click to expand...
Click to collapse
Tethering was broken by the 7.1.1 platform merge. Hopefully it'll be fixed with this:
https://review.cyanogenmod.org/175663
Please test with the next nightly.
Elektroschmock said:
Yes you need the new bootloader and radio for CM-14.1 to work properly.
It won't touch your data.
Tethering was broken by the 7.1.1 platform merge. Hopefully it'll be fixed with this:
https://review.cyanogenmod.org/175663
Please test with the next nightly.
Click to expand...
Click to collapse
Hey, just a small request.
Is there any way you can make the ROM to not force encrypt the device by default?
athulele said:
Hey, just a small request.
Is there any way you can make the ROM to not force encrypt the device by default?
Click to expand...
Click to collapse
Hey, just a small request,
Is there any way you can count back 6 posts and read what it says?
razorloves said:
Hey, just a small request,
Is there any way you can count back 6 posts and read what it says?
Click to expand...
Click to collapse
I did read the post.
Any specific reason why the kernels must be force encrypted? The earlier post didn't state why
athulele said:
I did read the post.
Any specific reason why the kernels must be force encrypted? The earlier post didn't state why
Click to expand...
Click to collapse
smh http://forum.xda-developers.com/showpost.php?p=69976710&postcount=533
athulele said:
I did read the post.
Any specific reason why the kernels must be force encrypted? The earlier post didn't state why
Click to expand...
Click to collapse
The reason is security is more important than performance. In the case of encryption the gain by not encrypting is negligible.
There are better ways to improve performance of the device.

[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.

[ROM][OFFICIAL][PAYTON][NIGHTLIES]Lineage OS 17.1

{
"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, 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.
Introduction:
This is the official Lineage OS thread for the Motorola Moto X4, codename payton.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
Lineage OS 17.1, ROM for the Moto X4
Contributors
erfanoabdi, Lineage Team
Source Code: https://github.com/LineageOS
ROM OS Version: 10.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Official Pie
Version Information
Status: Stable
Created 2018-09-01
Last Updated 2019-03-02
Copy Partitions Zip
- courtesy @ @filipepferraz
Download
Firmwares
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
About OTA: see post #778
Back to Stock :
Nice work, guys!
Excellent work! It's impressive that you could get this done when one person didn't have the phone. That's a good ol' fashioned hackathon.
Can somebody confirm if encryption works?
i love you guys <3
igna.98 said:
Can somebody confirm if encryption works?
Click to expand...
Click to collapse
It says "Phone Encrypted" under Settings. So, yes.
---------- Post added at 03:15 AM ---------- Previous post was at 02:53 AM ----------
Also happy to report that Magisk works successfully by sideloading the zip in TWRP (Data will not get decrypted when you boot into TWRP after the first boot - just hit cancel to get to the TWRP main menu > Advanced > ADB Sideload and sideload the Magisk ZIP.) SafetyNet passes too! And Google Pay works (finally!!! ...It was broken for me on stock).
Just got set up:
- AOSP firmware flash working on google fi version running 7.1
- Twrp decrypt not working with pin on the linked twrp or 3.2.1.1. Have to remove pin before booting to recovery
- videos recorded are choppy and lag during playback through camera app. I'll check when I install another gallery app but I rarely record so not a huge issue right now.
- bluetooth working well
Liking Lineage so far, especially the dark theme it seems to default to. I'll update with more as I play around with this. Thanks.
Speaker not working
Edit: seems it's just media, not phone
Just ran into an issue, speaker doesn't work with any app I've tried. There is sound with Bluetooth in the same apps. Attached some logcats.
brandontowey said:
Edit: seems it's just media, not phone
Just ran into an issue, speaker doesn't work with any app I've tried. There is sound with Bluetooth in the same apps. Attached some logcats.
Click to expand...
Click to collapse
Interesting. Working for me - tested using the Amazon Music app.
Edit: YouTube was used to test as well. However, the speaker volume level across all apps is lower than stock.
smmankad said:
Interesting. Working for me - tested using the Amazon Music app.
Huh, just tried and it stutters and no sound in YouTube. What model are you using and did you have Oreo already? I'm on the Google fiber variant and came from 7.1. maybe I need to upgrade to stock Oreo then flash.
Click to expand...
Click to collapse
brandontowey said:
smmankad said:
Interesting. Working for me - tested using the Amazon Music app.
Huh, just tried and it stutters and no sound in YouTube. What model are you using and did you have Oreo already? I'm on the Google fiber variant and came from 7.1. maybe I need to upgrade to stock Oreo then flash.
Click to expand...
Click to collapse
I was on stock Oreo 8.0.0/March 2017 (am having the XT1900-1 RETUS non-Fi version). Maybe that's why.
Click to expand...
Click to collapse
Thank you so much, my Payton is now flying. XT1900-7
igna.98 said:
Thank you so much, my Payton is now flying. XT1900-7
Click to expand...
Click to collapse
which firmware file did you use? xt1900-1 or xt1900-6?
Dumb question, can you flash if you're on 8.1?
munchy_cool said:
which firmware file did you use? xt1900-1 or xt1900-6?
Click to expand...
Click to collapse
XT1900-1
Wow nice job.
Sent from my Moto G5 Plus using XDA Labs
Not using it yet...
But I wanted to thank you guys SO much for working on this. I see using Lineage as the long-term plan for my phone (and my wife's) but these are our daily drivers and can't afford them to be offline for long. Once it is verified solid, I will likely switch. Thank you again!
ebrandsberg said:
But I wanted to thank you guys SO much for working on this. I see using Lineage as the long-term plan for my phone (and my wife's) but these are our daily drivers and can't afford them to be offline for long. Once it is verified solid, I will likely switch. Thank you again!
Click to expand...
Click to collapse
Its pretty damn solid as is. I've been using it since yesterday and no random reboots, no glitches, and super fast. My X4 is my daily driver too, btw.

[ROM][11.0][marlin] PixelExperience [AOSP][OFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Google Pixel XL [marlin]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11.0
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 11.0.0_r46
Security patch level: December 2021
Build author/Device Maintainer: PixelBoot
Device Source code:
https://github.com/PixelExperience-Devices/device_google_marlin
https://github.com/PixelExperience-Devices/kernel_google_marlin
https://gitlab.pixelexperience.org/android/vendor-blobs/vendor_google_marlin
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Reserved
Niceeeeee!!! I have been waiting too long for this <3
Awesome! Thanks alot for this! Couple of questions before flashing. Does it include stock google camera? Does it retain unlimited photos storage and also is it possible to flash over stock without losing all data? I know the last isn't recommended, but would be nice.
BoboBrazil said:
Awesome! Thanks alot for this! Couple of questions before flashing. Does it include stock google camera? Does it retain unlimited photos storage and also is it possible to flash over stock without losing all data? I know the last isn't recommended, but would be nice.
Click to expand...
Click to collapse
1. The camera included is one provided by cstark. It is a modded version of Google Camera which includes features from later Pixels, but should still hold the original features.
2. Yes, you can still upload unlimited photos in original quality.
3. Unfortunately, it is not possible to directly flash PixelExperience over stock. In fact, 11 requires a full device repartition. It's easy as flashing a .zip file before the ROM to do so.
If you have any more queries, make sure to let me know!
PixelExperience - OFFICIAL | Android 11
Updated: 14/03/'21
Links:
Sailfish [1.06GB]
Marlin [1.06GB]
️Telegram Group
Disclaimer:
This build requires you to re-partition your device in order to flash.
Kindly read the Pre-install instructions before flashing.
Changelog:
Initial stable release for Google Pixel/XL
PixelExperience (Plus Edition) - OFFICIAL | Android 11
Updated: 14/03/'21
Links:
Sailfish [1.06GB]
Marlin [1.06GB]
️Telegram Group
Disclaimer:
This build requires you to re-partition your device in order to flash.
Kindly read the Pre-install instructions before flashing.
Changelog:
Initial stable release for Google Pixel/XL
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
kartikb said:
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
Click to expand...
Click to collapse
Hey dude! (or dudette), would you please walk me throught the installation process? I'm a noob on flashing custom roms, and i'm facing some difficulties flashing this rom. I downloaded the repartition zip form the link, and I'm flashing it throught twrp recovery and then the rom zip file but it gets stuck on a bootloop. What am I missing? (Please forgive any misspellings, I'm also a noob at english)
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Great great work! Will surely be trying this at the first available free time!
kartikb said:
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
Click to expand...
Click to collapse
Hi. Are you able to download Google Camera from playstore and does it work fine?
Is selinux enforced? Tks
Going through Pixelexperience site, came across two versions for Pixel XL- Stable android 11 and Stable Android 11 (plus edition).
What's the difference between the two? Apologies if this is common knowledge, but this is the first time for me using Pixelexperience.
pantsaregood said:
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Click to expand...
Click to collapse
I'm facing with this issue too. Have done repartitioning successfully. :'(
lmvuong1997 said:
I'm facing with this issue too. Have done repartitioning successfully. :'(
Click to expand...
Click to collapse
I have solved the issue, this is what i have done:
- Boot into twrp from fastboot, using the latest twrp 3.5.0
- Advanced Wipe (system, dalvik, data), change active slot and then repeat (just to be sure)
- adb sideload the repartitioning zip
- Format data (where you type 'yes') then reboot into twrp
- (From Kartik Billimoria on Telegram)Push rom zip file to /sdcard via adb push command then flashed the rom
- Change to inactive slot (the slot you flashed the rom), reboot to fastboot to make sure the active slot has changed (for me it has not), if not change it by 'fastboot set_active a' (or b). Reboot.
josegarfer01 said:
Hey dude! (or dudette), would you please walk me throught the installation process? I'm a noob on flashing custom roms, and i'm facing some difficulties flashing this rom. I downloaded the repartition zip form the link, and I'm flashing it throught twrp recovery and then the rom zip file but it gets stuck on a bootloop. What am I missing? (Please forgive any misspellings, I'm also a noob at english)
Click to expand...
Click to collapse
It will not work via TWRP recovery.
1. Kindly go on the downloads page and install the PE recovery.
Code:
fastboot flash boot recovery.img
(It may bootloop once or twice, but then it will show up in PE recovery)
2. Go into Apply update via ADB.
Code:
adb sideload repartition-ogpixel-**gb.zip
3. Factory Reset/Wipe Data.
4. Apply update via ADB and sideload the ROM.
Code:
adb sideload PixelExperience-**.zip
5. Reboot and wait patiently.
Hope this helps.
pantsaregood said:
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Click to expand...
Click to collapse
lmvuong1997 said:
I'm facing with this issue too. Have done repartitioning successfully. :'(
Click to expand...
Click to collapse
If you are still in difficulty, follow the mentioned post below:
PixelBoot said:
It will not work via TWRP recovery.
1. Kindly go on the downloads page and install the PE recovery.
Code:
fastboot flash boot recovery.img
(It may bootloop once or twice, but then it will show up in PE recovery)
2. Go into Apply update via ADB.
Code:
adb sideload repartition-ogpixel-**gb.zip
3. Factory Reset/Wipe Data.
4. Apply update via ADB and sideload the ROM.
Code:
adb sideload PixelExperience-**.zip
5. Reboot and wait patiently.
Hope this helps.
Click to expand...
Click to collapse
gverma1 said:
Going through Pixelexperience site, came across two versions for Pixel XL- Stable android 11 and Stable Android 11 (plus edition).
What's the difference between the two? Apologies if this is common knowledge, but this is the first time for me using Pixelexperience.
Click to expand...
Click to collapse
PixelExperience Plus Edition provides extra tweaks that you can apply.
One that comes to mind is further customization to the notifcation bar to include network stats.
If you're up for extra customization from ROMs like LineageOS, consider flashing Plus instead.
gverma1 said:
Hi. Are you able to download Google Camera from playstore and does it work fine?
Is selinux enforced? Tks
Click to expand...
Click to collapse
By default, the ROM includes Google Camera PX by cstark27, which is more up to date than the stock (marlin/sailfish) Google Camera app. It includes newer features such as Portrait mode and Timelapse.
However, from the Google Play Store, you are still free to install the stock one.
As for SELinux, yes. It is enforced.
For stable releases from PixelExperience, it is required that builds are on Enforcing.
lmvuong1997 said:
- Change to inactive slot (the slot you flashed the rom), reboot to fastboot to make sure the active slot has changed (for me it has not), if not change it by 'fastboot set_active a' (or b). Reboot.
Click to expand...
Click to collapse
No need for this last part. If on TWRP, after flashing the ROM, you just need to reboot back to recovery and it will automatically set to the inactive slot.

Development [ROM] [OOS12FW] RisingOS v1.1 Android Project [dre] [UNOFFICIAL] [Updated June 16]

{
"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

Categories

Resources