Related
[size=+2]TWRP Flashable Stock builds for the Moto G4/G4 Plus[/size]
As you all know, Moto has finally released the first Oreo soak test for select users to test. Thanks to @rajatgupta1998, we all get to try it out
[size=+1]About these builds[/size]
This is the stock firmware, repackaged to be flashable in TWRP Recovery. In an effort to make these zips safer, I have removed all bootloader and gpt (partition table) related items.
[size=+1]Requirements[/size]
-> Unlocked bootloader
-> TWRP Recovery Installed (or booted)
[size=+1]Installation[/size]
-> Download the TWRP Flashable zip (Links below)
-> Place zip on device (internal or external storage)
-> Reboot to TWRP (or boot it)
-> Flash zip && Profit
[size=+1]Downloads[/size]
Nougat 7.0 (April 1st Security Patch)
• AFH -- TWRP-athene-7.0.0-NPJS25.93-14-18.zip
• G-Drive -- TWRP-athene-7.0.0-NPJS25.93-14-18.zip
md5sum == 71cab7a1bdebb067c569366dcaa26968
Oreo 8.1.0 Soak Test (November 1st Security Patch)
• AFH -- TWRP-athene-8.1.0-OPJ28.108.zip
• G-Drive -- TWRP-athene-8.1.0-OPJ28.108.zip
md5sum == c995bcb22215346e362195447de686f8
Oreo 8.1.0 (December 1st Security Patch)
• AFH -- TWRP-athene-8.1.0-OPJ28.111-12.zip
• G-Drive -- TWRP-athene-8.1.0-OPJ28.111-12.zip
md5sum == d7f7a0acdbb8e4bd24fa89e8513ec21c
Oreo 8.1.0 (December 1st Security Patch)
• AFH -- TWRP-athene-8.1.0-OPJ28.111-22.zip <-- coming soon
• G-Drive -- TWRP-athene-8.1.0-OPJ28.111-22.zip
md5sum == coming soon
[size=+1]Other Notes[/size]
* If you want to root, use Magisk and just flash in TWRP immediately after flashing the newest Oreo build. The latest build now fully passes SafetyNet and shows the device as being Certified in the Play Store.
* If you're already on the previous Oreo build (OPJ28.108 - November Security Patch), you can easily update to the latest Oreo build (OPJ28.111-12 - December Security Patch) by dirty flashing. If you want to keep root, you'll still need to flash Magisk again after flashing the newer build.
* To root the Nougat build(s), you will need to flash a custom kernel, then flash Magisk (same as before).
[size=+2]XDA:DevDB Information[/size]
[size=+1]TWRP Flashable Stock Builds, ROM for the Moto G4/G4 Plus[/size]
Contributors
@Jleeblanch, @rajatgupta1998, Motorola Mobility LLC
ROM OS Version: Android Oreo 8.1.0 - December 1st Security Patch
ROM Kernel: v3.10.84
Version Information:
Status: Beta
Created: 2018-11-26
Last Updated: 2019-01-09
**Reserved**
Coming from Pixel Experience 9.0 rom, wiped and installed. Working great so far. I hope we see an official rom soon.
zerocoolriddler said:
Coming from Pixel Experience 9.0 rom, wiped and installed. Working great so far. I hope we see an official rom soon.
Click to expand...
Click to collapse
these ROM have the same problems with camera like a soak test bulid?
all wipes needed to install these ROM?
vlrgamaley said:
these ROM have the same problems with camera like a soak test bulid?
Click to expand...
Click to collapse
This IS the Moto Soak test build. I've just made it TWRP flashable and safer for everyone to use. But yes, to answer your question, the issue with the Camera and Flashlight tile taking a few (5 or more) seconds to open is present here. There isn't anything I can do about that, however when Moto releases a future OTA update and have fixed the issue, I will make a new zip and post it here.
I will also make a nougat build of NPJS25.93-14-18 that is TWRP flashable as well for anyone who would like to be on stock nougat or easily revert back to stock nougat.
Thanks for your Hard Work.
Jleeblanch said:
ROM OS Version: Android Oreo 8.1.0 - November 1st Security Patch
ROM Kernel: v3.10.84
Click to expand...
Click to collapse
For curiosity: Would any of the (32 bit) custom kernels work with this ROM?
Thanks, I guess I won't be bored until I decide to unlock my G6 Plus
Jleeblanch said:
[size=+1]TWRP Flashable Stock builds for the Moto G4/G4 Plus[/size]
As you all know, Moto has finally released the first Oreo soak test for select users to test. Thanks to @rajatgupta1998, we all get to try it out
About this build
What is different about this versus what's already available? Basically what I have done is taken the previous 7.0 (nougat) firmware and directly patched it using the 8.1.0 (oreo) OTA zip from this thread. In an effort to make this build safer for everyone to use, I have left out any bootloader related items which is what can potentially prevent you from being able to downgrade. If this had been an official release, I would also have removed dm-verity (and forced encryption) as needed also. But being this is a test build from Moto, they have yet to enable such features. Now, on to the good stuff.
Requirements
-> Unlocked bootloader
-> TWRP Recovery Installed (or booted)
-> You may or may not need to be on stock nougat prior, need confirmation on this
Installation
-> Download the TWRP Flashable zip (Links below)
-> Place zip on device (internal storage or external)
-> Reboot to TWRP (or boot it)
-> Flash zip && Profit
Downloads
Oreo 8.1.0 Soak Test (November 1st Security Patch)
AFH - TWRP-athene-OPJ28.108.zip
G-Drive - TWRP-athene-OPJ28.108.zip
md5sum = c995bcb22215346e362195447de686f8
Other Notes
Currently as mentioned in the other thread, the build doesn't fully pass SafetyNet as it's a test release. You can use Magisk modules to fix this if needed.
You can also easily root by flashing Magisk immediately after the TWRP zip or any time afterwards.
[size=+2]XDA:DevDB Information[/size]
[size=+1]TWRP Flashable Stock Builds, ROM for the Moto G4/G4 Plus[/size]
Contributors
@Jleeblanch, @rajatgupta1998, Motorola Mobility LLC
ROM OS Version: Android Oreo 8.1.0 - November 1st Security Patch
ROM Kernel: v3.10.84
Version Information:
Status: Beta
Created: 2018-11-26
Last Updated: 2018-11-26
Click to expand...
Click to collapse
Thanx your .zip fixed the sim issues . Thanx mate
Jleeblanch said:
This IS the Moto Soak test build. I've just made it TWRP flashable and safer for everyone to use. But yes, to answer your question, the issue with the Camera and Flashlight tile taking a few (5 or more) seconds to open is present here. There isn't anything I can do about that, however when Moto releases a future OTA update and have fixed the issue, I will make a new zip and post it here.
I will also make a nougat build of NPJS25.93-14-18 that is TWRP flashable as well for anyone who would like to be on stock nougat or easily revert back to stock nougat.
Click to expand...
Click to collapse
Waiting for the Nougat build! Really need to go back to stock. Thank you for your work!
Awesome work dont stop keep up the good work
I`ve had previously RR 5.8 (Nougat 7.1, no custom kernels) and try install your ROM (without wipes, like you describe in instruction). Result? Bootloop. I have Moto 2g RAM/16 Gb Flash, install through rajatgupta recovery v 3.2.1-r3. Try now with wipes, but i don`t have confidence for good result.
try again with wipes, works normally. woah
jer194 said:
For curiosity: Would any of the (32 bit) custom kernels work with this ROM?
Click to expand...
Click to collapse
I doubt any of the stock kernels currently available would work as they're intended for nougat (7.0).
corlatemanuel said:
Thanks, I guess I won't be bored until I decide to unlock my G6 Plus
Click to expand...
Click to collapse
Fair enough. I'm surprised you haven't unlocked the bootloader yet, LineageOS is pretty good for the G6+ and also is used as a base ROM for flashing GSI's. I'll be making a stock based custom kernel (and one for the custom rom's/GSI's soon too).
DanFaraday777 said:
Waiting for the Nougat build! Really need to go back to stock. Thank you for your work!
Click to expand...
Click to collapse
I gotta finish up some TWRP flashable builds for the Moto G6 and then I'll upload the one I made for nougat when I upload those [emoji41]
luv u
thanks a lot
Thanks for zip :good:
What do you mean by "Stock nougat prior"?
Sorry for the dump question
Henry Markle said:
What do you mean by "Stock nougat prior"?
Sorry for the dump question
Click to expand...
Click to collapse
I mean the latest stock nougat build NPJS25.93-14-18
jer194 said:
For curiosity: Would any of the (32 bit) custom kernels work with this ROM?
Click to expand...
Click to collapse
To expand on Jleeblanch's reply, you may have to wait for Motorola to release the Oreo kernel source code, so developers can work on improving the kernel. Best thing to do is to check the Motorola Mobility GitHub page every so often, where you may see a request for the Oreo source code for our device appear https://github.com/MotorolaMobilityLLC/kernel-msm/issues Once there's a request made, Motorola should release the code when it's ready for release and then pave the way for custom Oreo kernels
echo92 said:
To expand on Jleeblanch's reply, you may have to wait for Motorola to release the Oreo kernel source code, so developers can work on improving the kernel. Best thing to do is to check the Motorola Mobility GitHub page every so often, where you may see a request for the Oreo source code for our device appear https://github.com/MotorolaMobilityLLC/kernel-msm/issues Once there's a request made, Motorola should release the code when it's ready for release and then pave the way for custom Oreo kernels
Click to expand...
Click to collapse
I would make the request myself, same as I've done for other devices (currently have a request up for beckham) but being that this is supposed to be a private soak test, not sure if they'll appreciate it just yet. But best believe, when they release the official Oreo build, I'll be all over it (assuming someone doesn't beat me to it [emoji6])
Jleeblanch said:
I would make the request myself, same as I've done for other devices (currently have a request up for beckham) but being that this is supposed to be a private soak test, not sure if they're appreciate it just yet. But best believe, when they release the official Oreo build, I'll be all over it (assuming someone doesn't beat me to it [emoji6])
Click to expand...
Click to collapse
Oh yup, it'd probably be a bit soon to put in a request, and I imagine they may change the kernel source code for the final release anyway (e.g. if they update to the latest security patch). Thanks for keeping a close eye on it - exciting times ahead
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
Click to expand...
Click to collapse
What's your phone's specifications?
Lanreallenjay said:
What's your phone's specifications?
Click to expand...
Click to collapse
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
Ask for help here
https://t.me/phhtreble/283195 <---
Read before any question ^^^
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
Click to expand...
Click to collapse
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
rupert3k said:
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
Click to expand...
Click to collapse
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
rupert3k said:
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
Click to expand...
Click to collapse
Have you tried formatting data with TWRP (to the part when it asks you to write "yes") then flash no-verity?
You should at least be able to flash TWRP. If you can't, just download the proper USB drivers for your device, it might be the culprit.
Cheers!
itShouldWork said:
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
Click to expand...
Click to collapse
Phh just hinted it's likely Pie vendor causing panics:
"First you need to flash stock rom. Then install magisk and then this gsi.
Though please note that on Pie vendor, S9 kernel panics and reboot every few minutes, so it is highly unusable."
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
I have tried Android 10 GSI , using latest Q update
ZoiraP said:
I have tried Android 10 GSI , using latest Q update
Click to expand...
Click to collapse
Is it usable? any random reboots/ annoying instability?
itShouldWork said:
Is it usable? any random reboots/ annoying instability?
Click to expand...
Click to collapse
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
ZoiraP said:
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
Click to expand...
Click to collapse
Camera quality might be fixed with Google cam, if you find a good port.
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
rupert3k said:
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
Click to expand...
Click to collapse
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
A\B
itShouldWork said:
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
Click to expand...
Click to collapse
No real experience but A\B devices have two slots ie double the partitions (OnePlus has 67) .
This allows updates to be installed while running from slot A while the updated system is copied to B.
Apparently Q requires A\B so now we're on Q may as well try that next time we're curious
Phh just released:
AOSP 10.0 v208
Fix suspend/dt2w for Samsung Q vendor
Fix backlight for Samsung Q vendor
Samsung Q's fine, love gestures but the bloat is killing me.
You can tell Q's going to be so much leaner without bixby & friends.
Glad we installed it to get compatible but I think now we probably stand a better chance with 10 GSI's, hopefully LOS17 & Pixel Experience get updated again soon.
Wondering whether to following the rooting instructions yet?
Phh did say "flash stock rom then magisk and then gsi"
https://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
ZoiraP's wondering why we sooo slow lol!
Wow this looks good: https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939
Update:
Stable update has been released.
Xiaomi announced they’ll upgrade the Redmi Note 8 Pro to Android 11 late last year. They have gone to update the global models, leaving the European variants waiting for some time now. Of course, the update was going to arrive, and perhaps, the company needed some time to address a few issues before the European release. Meanwhile, as expected, the Redmi Note 8 Pro Android 11-based MIUI 12.5 update in Europe is now available to select users.
The Redmi Note 8 Pro is receiving both Android 11 and MIUI 12.5 simultaneously, unlike the Redmi Note 8, that’s currently pushing Android 11 only. It is seeding with a version number – MIUI 12.5.2.0 RGGEUXM – and weighs in at 2.2GB. Coming along with the update are the features of the new MIUI OS to improve device performance and address some problems introduced by MIUI 12. Interestingly, the Android security patch level is pushed to July 2021 to increase system security and stability.
Of course, the update brings a stable MIUI based on Android 11, meaning that you get the features of the current Android OS as well. However, some known bugs are affecting all MIUI Android 11 builds. They include third-party launcher compatibility, ugly square chat bubbles, floating windows conflicting with keyboards, glitches, and lags. Luckily, you can improve the device’s performance by performing a factory reset after upgrading. However, that won’t fix the problems with the launcher as you need to revert to the MIUI system launcher.
Again, the Redmi Note 8 Pro Android 11-based MIUI 12.5 is a limited rollout. Those in Indonesia are also receiving the build with a version number – MIUI 12.5.2.0 RGGIDXM. It brings features of the new MIUI OS and a stable MIUI based on Android 11. Also, the Android security patch level has been pushed to July 2021 to increase system security and stability.
DOWNLOAD THE REDMI NOTE 8 PRO ANDROID 11-BASED MIUI 12.5 UPDATE IN EUROPE
Device Name: Redmi Note 8 Pro
Version: MIUI 12.5.2.0 RGGEUXM
Codename: begonia
Type: Stable Beta
Region: Europe
Android version: 11
Android security patch level: July 2021
Download Link: Recovery (found here)
INDONESIA MODELS
Device Name: Redmi Note 8 Pro
Version: MIUI 12.5.2.0 RGGEUXM
Codename: begonia
Type: Stable Beta
Region: Indonesia
Android version: 11
Android security patch level: July 2021
Download Link: Recovery
Flash at your own risk. I haven't got time yet to try myself. Please report bugs.
Link to article
UPDATE12.5.3.0 has been released.
Changelog:
Optimization: Updated Android Security Patch to August 2021.
Increased system security.
Official download here.
I get the info first time from Xiaomi Firmware Updater by @yshalsager
Cross finger though, the Redmi Note 8 had already Chinese stable A11 since Feb 2021, per today it hasn't got any global A11.
x3r0.13urn said:
I get the info first time from Xiaomi Firmware Updater by @yshalsager
Cross finger though, the Redmi Note 8 had already Chinese stable A11 since Feb 2021, per today it hasn't got any global A11.
Click to expand...
Click to collapse
A11 will most likely be the last official update for this device, wouldn't be surprised if it will take till end of this year.
This works in global variant via TWRP, but I don't recommend it. I could not find a way to install Google Play, even though i tested a lot of tutorials, magisk, appstores.
donkyshot said:
A11 will most likely be the last official update for this device, wouldn't be surprised if it will take till end of this year.
Click to expand...
Click to collapse
not really since they re-release the RN8 variant....
might be A12 like the case with RN5
Global variant finally.... MIUI12.5 A11 Global sucks no fastboot so I guess you have to flash some MIUI version and then update, coming from POSP and not happy about it but oh well. Will post after I flash it and see how it is. Probably end up back on a custom ROM dislike MIUI bloated bs....
dcindallas said:
Global variant finally.... MIUI12.5 A11 Global sucks no fastboot so I guess you have to flash some MIUI version and then update, coming from POSP and not happy about it but oh well. Will post after I flash it and see how it is. Probably end up back on a custom ROM dislike MIUI bloated bs....
Click to expand...
Click to collapse
Stock MIUI is horrendous. Bloatware, permissions etc. I can't stand it.
I'm on PE+ 11 but would prefer an official LineageOS release (no such thing available for now). I would also consider a xiaomi.eu release but they dropped support for Begonia/Begoniain.
Compass.
Global variant finally.... MIUI12.5 A11 Global sucks no fastboot so I guess you have to flash some MIUI version and then update, coming from POSP and not happy about it but oh well. Will post after I flash it and see how it is. Probably end up back on a custom ROM dislike MIUI bloated bs....
nah don't.... this version is bootlooping on me....
Crescendo Xenomorph said:
Global variant finally.... MIUI12.5 A11 Global sucks no fastboot so I guess you have to flash some MIUI version and then update, coming from POSP and not happy about it but oh well. Will post after I flash it and see how it is. Probably end up back on a custom ROM dislike MIUI bloated bs....
nah don't.... this version is bootlooping on me....
Click to expand...
Click to collapse
That sucks, I haven't had time to flash it let me see what's up later today.
dcindallas said:
That sucks, I haven't had time to flash it let me see what's up later today.
Click to expand...
Click to collapse
seems it's for Mi Pilot only.... that's why it's bootloop
Actually, it's bootlooping due to custom recovery..
I just did it like this:
- Download MIUI 12.5 Global from xiaomifirmwareupdater
- Reboot to recovery
- Flash from recovery
- Reboot to bootloader (using adb reboot bootloader or just boot to fastboot mode by rebooting and holding down the VOL_DN)
- Flash stock recovery (get it from xiaomifirmwareupdater, download previous ROM and extract recovery.img)
And with above I'm currently running MIUI 12.5.1. It's basically updated, I've lost no data.
I'm gonna dig in tomorrow for flashing custom recovery if i can find some working with this..
EDIT:
It may be that in order for TWRP to work on this ROM, a full wipe will need to be performed.
It's bootlooping due to patched vbmeta (vbmeta flashed with --disable-verity --disable-verification). So I'm unable to get TWRP to work. We might need some developer assistance ?
maretodoric said:
Actually, it's bootlooping due to custom recovery..
I just did it like this:
- Download MIUI 12.5 Global from xiaomifirmwareupdater
- Reboot to recovery
- Flash from recovery
- Reboot to bootloader (using adb reboot bootloader or just boot to fastboot mode by rebooting and holding down the VOL_DN)
- Flash stock recovery (get it from xiaomifirmwareupdater, download previous ROM and extract recovery.img)
And with above I'm currently running MIUI 12.5.1. It's basically updated, I've lost no data.
I'm gonna dig in tomorrow for flashing custom recovery if i can find some working with this..
EDIT:
It may be that in order for TWRP to work on this ROM, a full wipe will need to be performed.
It's bootlooping due to patched vbmeta (vbmeta flashed with --disable-verity --disable-verification). So I'm unable to get TWRP to work. We might need some developer assistance ?
Click to expand...
Click to collapse
I got it to install no issues I had to flash whatever the latest A10 MIUI ROM is from fastboot then it updated to 12.5 on its own. I am back on POSP I really just hate MIUI its bloated and slow, not worth the time or effort to be honest IMHO
dcindallas said:
I got it to install no issues I had to flash whatever the latest A10 MIUI ROM is from fastboot then it updated to 12.5 on its own. I am back on POSP I really just hate MIUI its bloated and slow, not worth the time or effort to be honest IMHO
Click to expand...
Click to collapse
Is Google Assistant and Android Auto working fine on that ROM? I've tried couple of A11 custom ROMs, they have issues with either GA or AA or both.
maretodoric said:
Actually, it's bootlooping due to custom recovery..
I just did it like this:
- Download MIUI 12.5 Global from xiaomifirmwareupdater
- Reboot to recovery
- Flash from recovery
- Reboot to bootloader (using adb reboot bootloader or just boot to fastboot mode by rebooting and holding down the VOL_DN)
- Flash stock recovery (get it from xiaomifirmwareupdater, download previous ROM and extract recovery.img)
And with above I'm currently running MIUI 12.5.1. It's basically updated, I've lost no data.
I'm gonna dig in tomorrow for flashing custom recovery if i can find some working with this..
EDIT:
It may be that in order for TWRP to work on this ROM, a full wipe will need to be performed.
It's bootlooping due to patched vbmeta (vbmeta flashed with --disable-verity --disable-verification). So I'm unable to get TWRP to work. We might need some developer assistance ?
Click to expand...
Click to collapse
So my suspicion confirmed coz the old ROM zip got recovery image but the A11 ROM doesn't have so many files in it including recovery.img.
Thanks for confirmation & guide....
So, basically there's no way to root it for noW?
Crescendo Xenomorph said:
So my suspicion confirmed coz the old ROM zip got recovery image but the A11 ROM doesn't have so many files in it including recovery.img.
Thanks for confirmation & guide....
So, basically there's no way to root it for noW?
Click to expand...
Click to collapse
TWRP A11 file from telegram begonia group, magisk app patch boot.img and flash patched .img file
maretodoric said:
It's bootlooping due to patched vbmeta (vbmeta flashed with --disable-verity --disable-verification). So I'm unable to get TWRP to work. We might need some developer assistance ?
Click to expand...
Click to collapse
but without patching vbmeta, it'll just bootloop even with A11 ver TWRP, right?
one more question: can you activate Google Discovery feed on MIUI12.5 or it's stuck on App Vault?
Crescendo Xenomorph said:
but without patching vbmeta, it'll just bootloop even with A11 ver TWRP, right?
Click to expand...
Click to collapse
i patched vbmeta before flashing twrp_A11, no reboot loop.
try format data
sigma9988 said:
i patched vbmeta before flashing twrp_A11, no reboot loop.
try format data
Click to expand...
Click to collapse
nice, I'll try this tom...
so, flash the full fastboot A10 latest then A11, patch vbmeta, flash TWRP-A11 + magisk, then all is OK?
maretodoric said:
Is Google Assistant and Android Auto working fine on that ROM? I've tried couple of A11 custom ROMs, they have issues with either GA or AA or both.
Click to expand...
Click to collapse
Work perfect and yes I feel ya I HATE that Google assistant doesn't work on most custom roms. Let me say this POSP is updated weekly, stable, smooth and everything works. Everything. My phone will like die with this time installed. Hoping the maintainer does A12 soon.
Derpfest A13 (Tango) for the OnePlus 9 Pro.
Unofficial for now, will apply for official momentarily.
Just Posting links for now, Thread will be properly formed and Cleaned Up Later this Weekend.
Requirements : C66 FW
Known Info
Uses ZPOS and Oss display Stack, so probably third party kernels won't be supported for now, if you change the
Possible issues will be caused like broken FOD./UDFPS.
Enforcing Build.
System/ROM works just fine .
Jan security patch QPR build.
Don't panic if first boot acts weird.
Todo: Cleanup Thread
Remove some more oplus ****s
Flashing Instr: Same like any Roms.
flash boot, vendor_boot and dtbo and sideload/ Flash with TWRP.
C66 FW: https://t.me/area51lemonade/452
Download here :
DerpFest-13-Initial_Build-OnePlus9Pro.zip
drive.google.com
Report and feedback can be done at TG group
Provided : https://t.me/area51lemonade
Kernel source : https://github.com/LineageOS/android_kernel_oneplus_sm8350
Rom source :
DerpFest AOSP
"German Engineering". DerpFest AOSP has 188 repositories available. Follow their code on GitHub.
github.com
Update 2:
Standy Issue Solved (kinda, its like hit or miss now)
Sepolicy Cleaned up a bit
User build
January SP
Improved Haptics Implementation (oos like).
here are few of the builds which might be worth trying, also includes initial build.
idk which build to be specific but one of it has everything working and less display crashes and fully working oos cam
Im having my exams starting Friday, so i wont be doing AOSP for some while.
thanks and here are the links
Release - Google Drive
drive.google.com
Res
Res
Thank you friend.
Very nice. Hopefully DerpFest official for our OP9P very soon. Thank you
C.66 firmware is included in rom ?
ElitePotato said:
C.66 firmware is included in rom ?
Click to expand...
Click to collapse
no, you have to flash the FW or flash some roms which already includes them like Xtended.
Sherif Rahim said:
Derpfest A13 (Tango) for the OnePlus 9 Pro.
Unofficial for now, will apply for official momentarily.
Just Posting links for now, Thread will be properly formed and Cleaned Up Later this Weekend.
Requirements : C66 FW
Known Info : Oos Cam - Only Photo Mode works, rest all are Broken.
Userdebug Build for now, next on it will be user release type.
Uses ZPOS and Oss display Stack, so probably third party kernels won't be supported for now.
Possible issues will be caused like broken FOD./UDFPS.
Enforcing Build.
System/ROM works just fine .
December security patch QPR build.
Don't panic if first boot takes some time, give it some time.
Expect the Next build on or before 15th Jan.
Todo: Cleanup Thread
Remove some more oplus ****s
shift to user build
Merge oplus camera fully
Add Dolby
And some other under the hood improvements planned.
Download here :
DerpFest-13-Initial_Build-OnePlus9Pro.zip
drive.google.com
Report and feedback can be done at TG group
Provided : https://t.me/area51lemonade
Kernel source : https://github.com/LineageOS/android_kernel_oneplus_sm8350
Rom source :
DerpFest AOSP
"German Engineering". DerpFest AOSP has 188 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
Amazing work i like Derpfest so much! Hope you keep update
Sherif Rahim said:
no, you have to flash the FW or flash some roms which already includes them like Xtended.
Click to expand...
Click to collapse
Are you sure it is included in Xtended ? There is a separate C.66 firmware flasher on sourceforge. Can I just flash C.66 firmware over OOS13 and flash rom ?
ElitePotato said:
Are you sure it is included in Xtended ? There is a separate C.66 firmware flasher on sourceforge. Can I just flash C.66 firmware over OOS13 and flash rom ?
Click to expand...
Click to collapse
not adviced
phone is not waking up from standby
habobababo said:
phone is not waking up from standby
Click to expand...
Click to collapse
Could you maybe grab logs?
Sherif Rahim said:
Could you maybe grab logs?
Click to expand...
Click to collapse
here you go.
I don't see any flashing instructions. So my guess is just use los recovery and flash?
NameIsOptional said:
I don't see any flashing instructions. So my guess is just use los recovery and flash?
Click to expand...
Click to collapse
Yes but you need C.66 firmware which you can find in xtended rom instructions.
NameIsOptional said:
I don't see any flashing instructions. So my guess is just use los recovery and flash?
Click to expand...
Click to collapse
will cleanup and organise the thread this weekend
Does someone got problems with standby?
habobababo said:
Does someone got problems with standby?
Click to expand...
Click to collapse
yes its an known issue, will work on the rom this weekend
Standy Issue Solved
Sepolicy Cleaned up a bit
User build
January SP
Improved Haptics Implementation (oos like)
More Camera modes on Ooscam is now there, but i wasnt able to figure out Video mode.
Also Let me know if Alert Slider was working for everyone?, Because rn its ded .
Lmk
I've flashed LineageOS 15.1 immediately since I bought this phone (starlte) in 2018 or 2019. Now I want to upgrade to LineageOS 20.0 but it has the following notice:
Warning: Before following these instructions please ensure that the device is currently using Android 10 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 10, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Click to expand...
Click to collapse
I have searched all over the internet for guides how to do it and I have no idea. Would temporarly flashing to LineageOS17.1 (Android 10) upgrade the firmware? Or do I need to flash official OS image? Or something else? I have no idea, things changed so much since early Android.
Android is the ROM. firmware is the baseband/modem what samsung calls CP core processor. custom ROM won't upgrade firmware, this has to be done by flashing full official ROM/firmware BL+AP+CP+CSC from Odin3.
OK thanks. Looks like this thread has all that i need https://forum.xda-developers.com/t/...as-available-oxm-for-sm-g960f-models.3765015/