Warning :-
1. Only works if Oreo stable update zip file is newer than the pie beta update zip file.
2. Will delete all data in /data (internal storage), don't forget your email/password you used to login on the phone otherwise you're screwed. I'm not responsible for anything that happens to your device.
Let's go
1. Download the latest stable oreo rom
asusdotcomslashPhone/ZenFone-Max-Pro-M2/HelpDesk_BIOS/
2. Rename the file, change .15 to .16 and .2016 to .2017 in the filename ( this step is very imp).
3. Reboot the device, u will get a notification to install the update, do it
4. Once device is updated, it'll ask your decryption password while booting(since i had a basic lockscreen pattern i had no idea how to move ahead so i proceeded to reset device from recovery, if you have the means to unlock the device thats great).
5. To reset device, shut it down, hold the upper vol and power button(or is it lower :silly, wait till the asus logo and then leave the buttons.
6 you'll get the stock recovery options, used vol buttons to move and power button to select wipe data.
7. Reboot device and login with your previous email account
Thats it.
rahul0012 said:
Warning :- will delete all data in /data (internal storage), don't forget your email/password you used to login on the phone otherwise you're screwed. I'm not responsible for anything that happens to your device.
Let's go
1. Download the latest stable oreo rom
asusdotcomslashPhone/ZenFone-Max-Pro-M2/HelpDesk_BIOS/
2. Rename the file, change .15 to .16 and .2016 to .2017 in the filename ( this step is very imp).
3. Reboot the device, u will get a notification to install the update, do it
4. Once device is updated, it'll ask your decryption password while booting(since i had a basic lockscreen pattern i had no idea how to move ahead so i proceeded to reset device from recovery, if you have the means to unlock the device thats great).
5. To reset device, shut it down, hold the upper vol and power button(or is it lower :silly, wait till the asus logo and then leave the buttons.
6 you'll get the stock recovery options, used vol buttons to move and power button to select wipe data.
7. Reboot device and login with your previous email account
Thats it.
Click to expand...
Click to collapse
Do u mean from Beta to Stable Oreo rom?
Adi.s said:
Do u mean from Beta to Stable Oreo rom?
Click to expand...
Click to collapse
Yes
rahul0012 said:
Yes
Click to expand...
Click to collapse
So mention that in the form.
rahul0012 said:
Yes
Click to expand...
Click to collapse
Adi.s said:
Do u mean from Beta to Stable Oreo rom?
Click to expand...
Click to collapse
Can we install the Oreo ROM by using TWRP
Using the same file downloaded from Asus website.
I actually want to go back Oreo from stable pie .
Zaid Ansari Xtm said:
Can we install the Oreo ROM by using TWRP
Using the same file downloaded from Asus website.
I actually want to go back Oreo from stable pie .
Click to expand...
Click to collapse
Yes u can. All versions are available on their website
I tried this from the stable Pie update and it fails with an error message," Can't install this package (Tue Feb 26 22:26:55 CST 2019) over newer build"
It's from the updater-script file, so if I comment out the first line then it should install right?
Code:
(!less_than_int(1551191215, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Feb 26 22:26:55 CST 2019) over newer build (" + getprop("ro.build.date") + ").");
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X01BD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
getprop("ro.build.asus.sku") == "WW" || abort("E3009: This package is for sku: \"WW\"; this is a sku: \"" + getprop("ro.build.asus.sku") + "\".");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/15.2016.1902.192-20190226:user/release-keys");
show_progress(0.650000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.100000, 0);
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
I tried it. The progress bar got almost halfway, I saw an error quickly and the phone restarted.
And again using recovery, the error is, "Signature verification failed". Now to find where the signature is stored.
Adi.s said:
Yes u can. All versions are available on their website
Click to expand...
Click to collapse
Pie is not uploaded on official website.
{
"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"
}
Sent from my ASUS_X01BDA using Tapatalk
So is there a way to install the last stable Oreo UL-ASUS_X01BD-WW-15.2016.1902.192-user.zip using the stock recovery?
I have the OTA Pie 9.0 from Asus and my screen blinks continiuously so I am trying to rollback to the last Oreo release.
@rahul0012, have you actually tried this method? Because the updater-script checks the build date in build.prop.
(!less_than_int(1551191215, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Feb 26 22:26:55 CST 2019) over newer build (" + getprop("ro.build.date") + ").");
And not the file name you mentioned to rename. So just renaming the file doesn't let you to flash earlier builds over the new ones. You'll get an error as mentioned by @damole in this post. Even if you remove that line in updater-script, you can't flash the zip file using stock recovery.
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
damole said:
I have the OTA Pie 9.0 from Asus and my screen blinks continiuously so I am trying to rollback to the last Oreo release.
Click to expand...
Click to collapse
A new build is out. It seems to have fixed the screen flickering issue. And nothing else.
anagramgenius said:
@rahul0012, have you actually tried this method? Because the updater-script checks the build date in build.prop.
(!less_than_int(1551191215, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Feb 26 22:26:55 CST 2019) over newer build (" + getprop("ro.build.date") + ").");
And not the file name you mentioned to rename. So just renaming the file doesn't let you to flash earlier builds over the new ones. You'll get an error as mentioned by @damole in this post. Even if you remove that line in updater-script, you can't flash the zip file using stock recovery.
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
A new build is out. It seems to have fixed the screen flickering issue. And nothing else.
Click to expand...
Click to collapse
I'm sorry I'm not an expert but what i tried was to rename the file so that it seemed like a newer version of the pie beta update file and then the updater recognised it after reboot and installed it, since my phone was encrypted i had to clear data to able to use my phone again. Thats all i can say. Sorry if it doesn't work.
anagramgenius said:
@rahul0012, have you actually tried this method? Because the updater-script checks the build date in build.prop.
(!less_than_int(1551191215, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Feb 26 22:26:55 CST 2019) over newer build (" + getprop("ro.build.date") + ").");
And not the file name you mentioned to rename. So just renaming the file doesn't let you to flash earlier builds over the new ones. You'll get an error as mentioned by @damole in this post. Even if you remove that line in updater-script, you can't flash the zip file using stock recovery.
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
A new build is out. It seems to have fixed the screen flickering issue. And nothing else.
Click to expand...
Click to collapse
Also thanks for the notification on newer build, could you tell me of its safe to install? Thanks.
rahul0012 said:
Also thanks for the notification on newer build, could you tell me of its safe to install? Thanks.
Click to expand...
Click to collapse
I never had screen flickering issue before. So I didn't notice any change over the previous "Stable" Pie build. But I have seen users saying the screen flickering issue is gone after updating to this new build. But update at your own risk.
anagramgenius said:
I never had screen flickering issue before. So I didn't notice any change over the previous "Stable" Pie build. But I have seen users saying the screen flickering is gone after updating to this new build. But update at your own risk.
Click to expand...
Click to collapse
Thanks, i think I'll take the risk
damole said:
I tried this from the stable Pie update and it fails with an error message," Can't install this package (Tue Feb 26 22:26:55 CST 2019) over newer build"
It's from the updater-script file, so if I comment out the first line then it should install right?
Code:
(!less_than_int(1551191215, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Feb 26 22:26:55 CST 2019) over newer build (" + getprop("ro.build.date") + ").");
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X01BD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
getprop("ro.build.asus.sku") == "WW" || abort("E3009: This package is for sku: \"WW\"; this is a sku: \"" + getprop("ro.build.asus.sku") + "\".");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/15.2016.1902.192-20190226:user/release-keys");
show_progress(0.650000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.100000, 0);
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
Click to expand...
Click to collapse
I apologise, I've tried it over beta pie update and it worked since the oreo build was a newer build(with the new month security patch) than the old pie beta update file. That is why it worked for me and not for you. I will edit the OP to reflect that.
anagramgenius said:
I never had screen flickering issue before. So I didn't notice any change over the previous "Stable" Pie build. But I have seen users saying the screen flickering issue is gone after updating to this new build. But update at your own risk.
Click to expand...
Click to collapse
Installed the rom, seems file to me.
I have installed the new ROM and the blinking screen issue is resolved.
Yes the reason it worked for you is that the beta pie came out before the last stable oreo so it passed the date check. The reason for changing the file name is so that the Android update check sees it as a new firmware to install, if you use recovery of course you don't need to change the file name.
I am sill intent on finding out how to sign the file properly which means generating a correct otacert file, it could be useful in future.
Related
Omnirom
{
"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"
}
Flash at your own risk!
IMPORTANT:
Since 5.1.1.-20151021 nightly we changed the vendor files to find7a including camera. If you have Problems with a recorded video file you can fix this maybe with this Link ! So far it's tested with VLC on Linux and Windows Media Player on Windows 10. It worked like a charm !
This is a very cool thing ... you are now able to install OPPO Camera and use the awesome 50 MPixel feature -> Link
Sources: http://www.github.com/omnirom/
(the Oneplus One source is called find7op)
Gerrit: https://gerrit.omnirom.org/
Gapps: http://forum.xda-developers.com/showthread.php?t=2792842
SuperSU: http://download.chainfire.eu/supersu
Recovery http://twrp.me/Devices/
Bug reports: http://jira.omnirom.org
How to flash:
1. Boot into your TWRP recovery.
2. Backup your existing Rom.
3. Wipe partitions.
4. Flash the Rom.
5. Flash Gapps.
6. Wipe Cache and Dalvik.
(7. If you need it flash SuperSU.)
Reboot your device.
Bugs: You tell me !
Download Nightly Builds [5.1.1]: https://dl.omnirom.org/find7op
Download development (homebuild) builds: https://www.androidfilehost.com/?w=files&flid=22231
XDA:DevDB Information
Omnirom for Oneplus One, ROM for the ONEPLUS ONE
Contributors
samstone86, maxwen, scanno, Entropy512
Source Code: http://www.github.com/omnirom/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Nightly
Created 2014-09-22
Last Updated 2015-10-21
Reserved
Updates:
20141007
fix watching captured videos on PC
add 4k videocapture modes (thanks to maxwen)
20140925:
fixed install for other recoverys
20140924:
changed Touchscreen Firmware
changed Device Name
Reserved
Been waiting for OMNI for a good while now! THANK YOU!
While flashing in Phillz full wipe im getting a "this package is for 'find7op, bacon' devicesthiss is a A001' ?
*After changing the flash script is boot fine ! runs pretty smooth as well ! nice work
*Edit ..seems like there is a problem with the touch drivers the screen is unresponsive and im getting ghost touches all the time ..
Hogyoku said:
While flashing in Phillz full wipe im getting a "this package is for 'find7op, bacon' devicesthiss is a A001' ?
*After changing the flash script is boot fine ! runs pretty smooth as well ! nice work
*Edit ..seems like there is a problem with the touch drivers the screen is unresponsive and im getting ghost touches all the time ..
Click to expand...
Click to collapse
Hi, if you use TWRP it flashes fine but i can add A0001.
I never have ghost toutches can you provide a logcat?
I'm blind or can't find link to download?
Sent from E.P.D.Center
acuicultor said:
I'm blind or can't find link to download?
Sent from E.P.D.Center
Click to expand...
Click to collapse
On top of the thread title is the "Downloads" button
me error when I start the installation
Flashed on multirom but unfortunately it wont boot even can see the bootanimation just black screen.
Sent from E.P.D.Center
_OverKill_ said:
me error when I start the installation
Click to expand...
Click to collapse
Try using latest twrp. Or download it again and check md5sum
I download this? omni-4.4.4-20140922-find-7op HOMEMADE.zip
can we use AK kernel ? (aosp version)
BHH
acuicultor said:
Flashed on multirom but unfortunately it wont boot even can see the bootanimation just black screen.
Sent from E.P.D.Center
Click to expand...
Click to collapse
Try without multirom
buzzqw said:
can we use AK kernel ? (aosp version)
BHH
Click to expand...
Click to collapse
I didn't test any other kernel and I don't recommend to use another kernel
samstone86 said:
I didn't test any other kernel and I don't recommend to use another kernel
Click to expand...
Click to collapse
thanks samstone86
BHH
acuicultor said:
Flashed on multirom but unfortunately it wont boot even can see the bootanimation just black screen.
Sent from E.P.D.Center
Click to expand...
Click to collapse
Did you have your USB cable plugged in while booting?
first impressions so far..
- please integrate superuser/super su
- why device name is find7op ? all other roms name A0001.
could you change updater script to ?
Code:
assert(getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" ||
getprop("ro.product.device") == "A0001" || getprop("ro.build.product") == "A0001" || abort("This package is for \"bacon,A0001\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
- enable multi row on quick settings
- enable sun light display enhancement
(enable dt2w > found on advanced)
EDIT: after some minutes, the touchscreen seems going crazy. i set lock screen to sequence, and i am unable to unlock.. touch seems going elsewhere!
Also AK kernel don't boot...
thanks for Omnirom!
BHH
Will this actually turn into nightlies? Or what is the plan? Maybe we can work out official support
RIPng said:
Will this actually turn into nightlies? Or what is the plan? Maybe we can work out official support
Click to expand...
Click to collapse
You can see this thread as testing for nightlys
{
"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"
}
GitHUB
Code:
https://github.com/TeamRegular/android_kernel_samsung_exynos3470
https://github.com/TeamRegular/android_device_samsung_gardalte
https://github.com/YaDev/kernel_samsung_gardaltetmo
https://github.com/YaDev/android_device_samsung_gardaltetmo
https://github.com/YaDev/vendor_samsung_gardaltetmo
CM11 ROM has been built already :good:. We are looking for people who can test these builds or build their own rom.
Note: Build CM11 using Ubuntu 12 to avoid compilers' issues (4.6 & 4.7 should work).
I hope this comes to fruition!!! Thanks!
motive said:
I hope this comes to fruition!!! Thanks!
Click to expand...
Click to collapse
BTW, this device ($100) has Exynos 3470 Soc and the Galaxy S5 MINI ($400) has the same.
@[email protected] said:
BTW, this device ($100) has Exynos 3470 Soc and the Galaxy S5 MINI ($400) has the same.
Click to expand...
Click to collapse
Mind testing my build? https://www.androidfilehost.com/?fid=95784891001602689
Might need to edit updater script to get it to flash.
Unjustified Dev said:
Mind testing my build? https://www.androidfilehost.com/?fid=95784891001602689
Might need to edit updater script to get it to flash.
Click to expand...
Click to collapse
If i do try this what do i need to update in script for it to work?
tazmaniondvl said:
If i do try this what do i need to update in script for it to work?
Click to expand...
Click to collapse
Most likely it should flash but if not remove the following lines.
Code:
assert(getprop("ro.product.device") == "gardalte" ||
getprop("ro.build.product") == "gardalte" ||
getprop("ro.product.device") == "gardaltetmo" ||
getprop("ro.build.product") == "gardaltetmo" ||
getprop("ro.product.device") == "gardalteMetroPCS" ||
getprop("ro.build.product") == "gardalteMetroPCS" ||
abort("This package is for device: gardalte,gardaltetmo,gardalteMetroPCS; this device is " + getprop("ro.product.device") + "."););
Unjustified Dev said:
Most likely it should flash but if not remove the following lines.
Code:
assert(getprop("ro.product.device") == "gardalte" ||
getprop("ro.build.product") == "gardalte" ||
getprop("ro.product.device") == "gardaltetmo" ||
getprop("ro.build.product") == "gardaltetmo" ||
getprop("ro.product.device") == "gardalteMetroPCS" ||
getprop("ro.build.product") == "gardalteMetroPCS" ||
abort("This package is for device: gardalte,gardaltetmo,gardalteMetroPCS; this device is " + getprop("ro.product.device") + "."););
Click to expand...
Click to collapse
It failed to flash, ill wait till i get jome to mess with script. But if someone does it and post it i will give it another try. Just dont have computer here at work to use
tazmaniondvl said:
It failed to flash, ill wait till i get jome to mess with script. But if someone does it and post it i will give it another try. Just dont have computer here at work to use
Click to expand...
Click to collapse
Could you tell me the error it had when flashing
Unjustified Dev said:
Could you tell me the error it had when flashing
Click to expand...
Click to collapse
Error executing updater binary
tazmaniondvl said:
Error executing updater binary
Click to expand...
Click to collapse
Must be a recovery issue I'll upload mine it's unified and so are my builds they set device naming once installed. I have no idea if my recovery works though so if anyone flashes it be prepared to flash a working version.
I recommend using flashify to install the image the worst that could happen is your recovery won't load you can still use flashify again to install a working image and all is good again.
https://www.androidfilehost.com/?fid=95784891001603287
Unjustified Dev said:
Must be a recovery issue I'll upload mine it's unified and so are my builds they set device naming once installed. I have no idea if my recovery works though so if anyone flashes it be prepared to flash a working version.
I recommend using flashify to install the image the worst that could happen is your recovery won't load you can still use flashify again to install a working image and all is good again.
https://www.androidfilehost.com/?fid=95784891001603287
Click to expand...
Click to collapse
Just a black screen.... we do have a cwm but it's outdated. And there was an issue with sdcard. @smartguy044 built it and i was his tester. He does boot own this phone.
Unjustified Dev said:
Mind testing my build? https://www.androidfilehost.com/?fid=95784891001602689
Might need to edit updater script to get it to flash.
Click to expand...
Click to collapse
Great work!!
the rom booted successfully but the screen is frozen (boot up logo).
Touch screen, buttons & mtp worked but no sound.
I have added your git links to the main post (sorry, have not seen them before).
CWM recovery won't work without moded graphic.c.
Instead, delete "META-INF/" "recovery/" and "system/etc/install-recovery2.sh" from the zip file and use the script I uploaded to install the rom in TWRP (without signature check)
Tip: force adb for debugging
init.universal3470.usb.rc
Code:
start adbd
@[email protected] said:
Great work!!
the rom booted successfully but the screen is frozen (boot up logo).
Touch screen, buttons & mtp worked but no sound.
I have added your git links to the main post (sorry, have not seen them before).
CWM recovery won't work without moded graphic.c.
Instead, delete "META-INF/" "recovery/" and "system/etc/install-recovery2.sh" from the zip file and use the script I uploaded to install the rom in TWRP (without signature check)
Tip: force adb for debugging
init.universal3470.usb.rc
Code:
start adbd
Click to expand...
Click to collapse
Maybe you guys can work on the recovery and this and get a fully Functional rom
@[email protected] said:
Great work!!
the rom booted successfully but the screen is frozen (boot up logo).
Touch screen, buttons & mtp worked but no sound.
I have added your git links to the main post (sorry, have not seen them before).
CWM recovery won't work without moded graphic.c.
Instead, delete "META-INF/" "recovery/" and "system/etc/install-recovery2.sh" from the zip file and use the script I uploaded to install the rom in TWRP (without signature check)
Tip: force adb for debugging
init.universal3470.usb.rc
Code:
start adbd
Click to expand...
Click to collapse
If you can send the graphics.c I would surely implement it , is it the one from smdk4412-common? Could you send me logcats of the build.
edit: Attached another recovery image with custom graphics.c from smdk4412
https://www.androidfilehost.com/?fid=95784891001603587
Unjustified Dev said:
If you can send the graphics.c I would surely implement it , is it the one from smdk4412-common? Could you send me logcats of the build.
edit: Attached another recovery image with custom graphics.c from smdk4412
https://www.androidfilehost.com/?fid=95784891001603587
Click to expand...
Click to collapse
Still getting a black screen.
tazmaniondvl said:
Still getting a black screen.
Click to expand...
Click to collapse
I'll wait for root to get back with the graphics.c
I feel like this is so close, yet so far away. This is the holy grail for our device. The one ROM to rule them all.
Unjustified Dev said:
I'll wait for root to get back with the graphics.c
Click to expand...
Click to collapse
graphics.c overwrite the original one.
smdk4x12 's graphics.c did not work --> "ioctl(): blank"
However, I ported TWRP to this device without graphics.c.
So, TWRP's graphics.c should work.
https://github.com/omnirom/android_bootable_recovery/blob/android-4.4/minui/graphics.c
Copy these two files:
Code:
#include "font_10x18.h"
#include "minui.h"
@[email protected] said:
graphics.c overwrite the original one.
smdk4x12 's graphics.c did not work --> "ioctl(): blank"
However, I ported TWRP to this device without graphics.c.
So, TWRP's graphics.c should work.
https://github.com/omnirom/android_bootable_recovery/blob/android-4.4/minui/graphics.c
Copy these two files:
Code:
#include "font_10x18.h"
#include "minui.h"
Click to expand...
Click to collapse
Just for the fun of it I attempted to build cm recovery build here. I'll definitely attempt twrp later.
https://www.androidfilehost.com/?fid=95784891001604066
Unjustified Dev said:
Just for the fun of it I attempted to build cm recovery build here. I'll definitely attempt twrp later.
https://www.androidfilehost.com/?fid=95784891001604066
Click to expand...
Click to collapse
So far i have had a black screen on all of them. Wandering if it's my phone.... only one that works is roots twrp
---------- Post added at 02:56 AM ---------- Previous post was at 02:46 AM ----------
tazmaniondvl said:
So far i have had a black screen on all of them. Wandering if it's my phone.... only one that works is roots twrp
Click to expand...
Click to collapse
I do believe that the recovery actually works, just think its not showing it. Me and smartguy044 had this problem with the CWM he built. Maybe look at what he did in his. He doesn't own this phone so i did all the testing for him
http://forum.xda-developers.com/showthread.php?t=2669313
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.
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys, this is an unofficial build of AOSP Nougat (with tag android-7.0.0_r1). Kernel is based on CM13's
NOTE: This is only for development purposes, I am not responsible if you damage your device, you always have to make a backup
What's working:
Camera (partial, auto iso disable this moment)
Wifi
Audio (partial)
Vibrator
H/W
MTP
What's broken:
RIL
Bluetooth
Sensors
NFC
.
Screenshots: http://imgur.com/a/VzbEr
Download: https://www.androidfilehost.com/?fid=24588232905724006
Update: 04/09/16 "only for purposes of development"
NOTE:this version can by or no erase the internal memory, please make a backup first
GPS works, "is slow to conect for now"
Radio and AutoISO still no works,
Update: 18/09/16 "CM-14.0 build"
* Works:
- Radio
- Data
- WiFi
- Camera
- Thermal
- NFC
- GPS
- Sensors
- Audio
- Vibrator
- H/W
- MTP
* What's broken:
- Bluetooth
- If more mistakes please let me know! xD
Source:
Device: https://github.com/Arc-Team/android_device_lge_d851/tree/aosp-7.0
kernel: https://github.com/Arc-Team/android_kernel_lge_d851/tree/cm-14.0
Build: https://github.com/Arc-Team/android_build/tree/aosp-7.0
XDA:DevDB Information
Unofficial Android 7.0 Nougat build for D851, ROM for the T-Mobile LG G3
Contributors
josegalre
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-08-30
Last Updated 2016-09-18
Reserved
nice!!!
downloading right now, i´ll try in multirom!
edit. wrong zip, cant install, even as primary rom.
Same here, can't install as primary ROM in multirom
Sent from my LG-D851 using XDA-Developers mobile app
after flashing this I lose twrp and can't get out of this rom unless I go with kdz
I found a fix!
Open rom.zip
Go to META-INF - com - google - android
Open updater-script in notepad
Replace the whole script with this one
Code:
(!less_than_int(1472462926, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (lun ago 29 03:28:46 CST 2016) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "d851" || getprop("ro.build.product") == "d851" || abort("E3004: This package is for \"g3,d851\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: lge/aosp_d851/d851:7.0/NRD90M/josega08290328:userdebug/test-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
Save and flash
Enjoy!..
crack! waiting for ril and tester here
Great news! I'll probably play around with this soon, glad this old device might get N builds, ill keep it till development dies or it breaks.
Prowler said:
I found a fix!
Open rom.zip
Go to META-INF - com - google - android
Open updater-script in notepad
Replace the whole script with this one
Code:
(!less_than_int(1472462926, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (lun ago 29 03:28:46 CST 2016) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "d851" || getprop("ro.build.product") == "d851" || abort("E3004: This package is for \"g3,d851\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: lge/aosp_d851/d851:7.0/NRD90M/josega08290328:userdebug/test-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
Save and flash
Enjoy!..
Click to expand...
Click to collapse
Nice guy!!, i have the error after flash but device boots fine xD
josegalre said:
Save and flash
Enjoy!..
Nice guy!!, i have the error after flash but device boots fine xD
Click to expand...
Click to collapse
Tried this it didnt work used normal zip it worked
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
boots fast no signal as stated but constant google play service crash other issues maybe there but havnt used it for long
what gapps should i use? trying to use 7.0 arm opengapps fails because it doesn't detect an OS.
meamme123 said:
what gapps should i use? trying to use 7.0 arm opengapps fails because it doesn't detect an OS.
Click to expand...
Click to collapse
I used those they worked but signal doesn't work
dudeawsome said:
I used those they worked but signal doesn't work
Click to expand...
Click to collapse
Signal not working is mentioned in the OP. That's RIL, btw.
LG G3 D851, PAC-MAN LP ROM, Nebula 9.1 Kernel, Tapatalk 4.9.5
dudeawsome said:
Tried this it didnt work used normal zip it worked
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
boots fast no signal as stated but constant google play service crash other issues maybe there but havnt used it for long
Click to expand...
Click to collapse
what normal zip?
Trey n said:
what normal zip?
Click to expand...
Click to collapse
Without the fix
dudeawsome said:
Without the fix
Click to expand...
Click to collapse
oh it keeps failing for me :/
Trey n said:
oh it keeps failing for me :/
Click to expand...
Click to collapse
Just wait Dev is releasing new update today
Notices? Im waiting a new hard disk, I have no space to help right now
Enviado desde mi LG-D851 mediante Tapatalk
Update: 04/09/16 "only for purposes of development"
NOTE:this version can by or no erase the internal memory, please make a backup first
GPS works, "is slow to conect for now"
Radio and AutoISO still no works,
Will it erase internal memory even if you flash in multirom?
.
.
.
.
{
"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"
}
AICPAndroid Ice Cold Project
AICP is known by everyone as Ice Cold Project that started on Desire HD and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, Rom has always been AOKP based. Unfortunately, since AOKP either stopped development or will make a comeback later this year, we changed our base to CM when it comes to hardware, drivers and some features.
If there are any bugs, either we will sort them or CM team if it concerns their modifications. This rom isn't CM supported so no need to report errors or bugs to them!!
.
.
.
.
.
In the beginning we would like to thank:
CM team
maxwen
SlimBean rom team
CarbonRom team
LiquidSmooth rom team
Omni rom team
DU team
Community
@LorD ClockaN
@zipsnet
@n3ocort3x
@semdoc
@eyosen
@alienmind
@Chezbel
@Drgravy
@eboye
.
.
.
We are now paying for servers that build nightlies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 8
Download link: http://dwnld.aicp-rom.com/?device=Z00ED
Full Changelog link: goo.gl/mIgmYG
Don't disable Heads-Up. You wont be able to answer phone calls otherwise.
You tell...
ROMS should contain everything you need to enjoy Lollipop. You are not required to install any Add Ons, simply download the latest ROM, gapps, flash it, and go!
You are STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup - these can cause stability issues that are very hard to debug. If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience strange behavior.
How to flash:
Don't do it if you don't know it
ROM has gapps persistance in between dirty flashes
KERNEL:
Kernel in this rom follows CM source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash over OTA app, TWRP recovery is needed.
You can still use CWM and OTA app, but only to download zip file and flash it manually from within recovery. Zip gets saved under AICP_ota folder on your internal SDcard.
If you want to contribute to the AICP or wanna see what is being worked on/merge feel free to visit our gerrit, link is at the bottom!!!
IceColdJelly AICP G+ community
kernel github
rom gerrit
You want to see a normal night at the DEV office, click here!!
XDA:DevDB Information
[ROM] [Z00ED/Z00RD] AICP - 12.1 - N 7.1_r7 | OFFICIAL NIGHTLIES, ROM for the Zenfone 2 Laser
Contributors
kaankulahli, Nyks45
Source Code: http://aicp-rom.com
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AICP
Version Information
Status: Nightly
Created 2017-02-10
Last Updated 2017-02-10
reserved
rezerved #2
Another official ROM? Cool.. I hope the unofficial LineageOS will become official at one time
Btw: Is this based on LineageOS build posted by audahadi on this forum?
---------- Post added at 09:46 PM ---------- Previous post was at 09:20 PM ----------
@kaankulahli
I can't install the ROM.. ERROR 7.. I tried to remove the next line but didn't worked
assert(getprop("ro.product.device") == "jfltevzw" || getprop("ro.build.product") == "jfltevzw" || getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" || abort("E3004: This package is for device: jfltevzw,jflte; this device is " + getprop("ro.product.device") + ".");
vraciu' said:
Another official ROM? Cool.. I hope the unofficial LineageOS will become official at one time
Btw: Is this based on LineageOS build posted by audahadi on this forum?
---------- Post added at 09:46 PM ---------- Previous post was at 09:20 PM ----------
@kaankulahli
I can't install the ROM.. ERROR 7.. I tried to remove the next line but didn't worked
assert(getprop("ro.product.device") == "jfltevzw" || getprop("ro.build.product") == "jfltevzw" || getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" || abort("E3004: This package is for device: jfltevzw,jflte; this device is " + getprop("ro.product.device") + ".");
Click to expand...
Click to collapse
rom it for other devices,bro!!!
rom for u'r devices was in building
vraciu' said:
Another official ROM? Cool.. I hope the unofficial LineageOS will become official at one time
Btw: Is this based on LineageOS build posted by audahadi on this forum?
---------- Post added at 09:46 PM ---------- Previous post was at 09:20 PM ----------
@kaankulahli
I can't install the ROM.. ERROR 7.. I tried to remove the next line but didn't worked
assert(getprop("ro.product.device") == "jfltevzw" || getprop("ro.build.product") == "jfltevzw" || getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" || abort("E3004: This package is for device: jfltevzw,jflte; this device is " + getprop("ro.product.device") + ".");
Click to expand...
Click to collapse
It seems you downloded wrong rom the rom hasn't been built yet just wait we will announce when the first nightly is out for now just delete that zip as you can see even the codename is wrong in the zip you downloaded
Wait for the true one which is Z00ED
Nyks45 said:
It seems you downloded wrong rom the rom hasn't been built yet just wait we will announce when the first nightly is out for now just delete that zip as you can see even the codename is wrong in the zip you downloaded
Wait for the true one which is Z00ED
Click to expand...
Click to collapse
Oh, my bad.. I just followed the download link and thought is for the Z00ED version... I should have look at the url link.. OUPS
---------- Post added at 10:05 PM ---------- Previous post was at 10:04 PM ----------
Adhe_88 said:
rom it for other devices,bro!!!
rom for u'r devices was in building
Click to expand...
Click to collapse
I see now.. sorry! I'm dumb!
Download link is updated when the first Nightly is out you will be able to download it directly from that link
Nyks45 said:
Download link is updated when the first Nightly is out you will be able to download it directly from that link
Click to expand...
Click to collapse
rom will be is only nightly?
Ne lan bu
A0001 cihazımdan Tapatalk kullanılarak gönderildi
I flashed the ROM (now I flashed the right one ) ) and everything is good. I really didn't except to see Magisk build in. The phone is not bypassing SafetyNet test when I check inside the Magisk Manager but that is not so important.
Good Job
Edit: Call Management app/service asked for root permission.. Is that good?
Edit: Also the bottom shortcuts in Quick Settigns Editor can be added to the top ones because when I drag them to the top they go back to the initial position . idk how to say it. For ex I can't drag Application Picker to Quick Settings because is on bottom of editor
vraciu' said:
I flashed the ROM (now I flashed the right one ) ) and everything is good. I really didn't except to see Magisk build in. The phone is not bypassing SafetyNet test when I check inside the Magisk Manager but that is not so important.
Good Job
Edit: Call Management app/service asked for root permission.. Is that good?
Edit: Also the bottom shortcuts in Quick Settigns Editor can be added to the top ones because when I drag them to the top they go back to the initial position . idk how to say it. For ex I can't drag Application Picker to Quick Settings because is on bottom of editor
Click to expand...
Click to collapse
in here everything is work
about SafetyNet can u enable hide Magisk in setting and then u tap SafetyNet .
sorry my bad english ?
Adhe_88 said:
in here everything is work
about SafetyNet can u enable hide Magisk in setting and then u tap SafetyNet .
sorry my bad english
Click to expand...
Click to collapse
Didn't worked! Anyway there's a big problem.. The SDCard gets corrupted even after format
Edit: Also Night Light doesn't work
vraciu' said:
Didn't worked! Anyway there's a big problem.. The SDCard gets corrupted even after format
Edit: Also Night Light doesn't work
Click to expand...
Click to collapse
yes I know that, but you also have to understand because it first nightly builds , so we need just wait developers can fix problems this roms next build
.but I'm very pleased this device already have official build and I appreciate their work.
Adhe_88 said:
yes I know that, but you also have to understand because it first nightly builds , so we need just wait developers can fix problems this roms next build
.but I'm very pleased this device already have official build and I appreciate their work.
Click to expand...
Click to collapse
Yep... I'm also happy that this device got official support... After the bootloader unlocked we had only buggy ROMs and almost made be buy another phone )
@kaankulahli the sd card doesn't working it's say that it's corrupted
And when i enter the AICP EXTRAS it take me out automtic...
idirtb15 said:
@kaankulahli the sd card doesn't working it's say that it's corrupted
And when i enter the AICP EXTRAS it take me out automtic...
Click to expand...
Click to collapse
The SDCard problem is still here on the latest nightly.. And about AICP EXTRAS you need to go to Magisk and enable root for "Call Management"
@kaankulahli
The phone now detects only exFAT SDCards and not FAT32.. Other ROMs can use FAT32 but why we can't use it on this one?
vraciu' said:
@kaankulahli
The phone now detects only exFAT SDCards and not FAT32.. Other ROMs can use FAT32 but why we can't use it on this one?
Click to expand...
Click to collapse
it is being to fix ,and maybe build tomorrow has been resolved.
so give them a little time and u just need to wait for it
Adhe_88 said:
it is being to fix ,and maybe build tomorrow has been resolved.
so give them a little time and u just need to wait for it
Click to expand...
Click to collapse
Ok. Anyway do you know how to fix an corrupted internal atorage? I formated my sdcard as internal storage but this morning my phone couldn't start if my sdcard was in my phone..and now I can't ise my internal storage at all
Edit: i just had to remove my card from storage menu
{
"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"
}
PixelExtended for Samsung Galaxy S10/e/+/5G [beyond0lte&beyond1lte&beyond2lte&beyondx]
What is this?
PixelExtended is an Open Source Custom ROM based on PixelExperience, 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 missing in Pixel Experience, The ROM will keep it's Pixel ideologies it's primary focus and wont stray into the dark and deep void that is bloat.
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Sound/vibration
FP gestures
Bixby Button
Known issues
VoLTE/VoWIFI - not working for most Samsung devices, so no fix in the near future
You tell me
Features That are Available At the Moment
Click Here To See Features List
As only Essesntial Features will be added so this list will updated whenever there is a new feature
NOTE :- All possible features are toggleable so you always can choose to be stockish.
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from SourceForge
Galaxy S10e (beyond0lte)
Galaxy S10 (beyond1lte)
Galaxy S10+ (beyond2lte)
Galaxy S10 5G (beyondx)
Donate
Liked my work? Give me a beer
Stay tuned
Our Telegram Group
Our Telegram Channel
Android OS version: 13
Security patch level: November 2022
Build author/Device Maintainer: Jubscleisson
Device Source code: https://github.com/PixelExtended-Devices
Kernel Source: https://github.com/Linux4/android_kernel_samsung_exynos9820
Source code: https://github.com/PixelExtended
PixelExtended Developer: Aryan Gupta
Notes:
- This rom supports only PE and LOS recovery
Downloads:
Recovery (beyond0lte) (beyond1lte) (beyond2lte) (beyondx)
S Firmware (beyond0lte) (beyond1lte) (beyond2lte) (beyondx)
Magisk (Download from here)
First time installation:
you CAN NOT INSTALL this ROM using TWRP.
You need to use the Official Lineage recovery provided by Linux4 (link in downloads section)
Installing Lineage Recovey (BL already unlocked):
Odin:
Rename the downloaded .img to recovery.img and add it to a .tar archive using, for example, 7Zip
Flash the resulting .tar file in Odin
Installing The ROM From Lineage Recovery:
Lineage recovery - Factory reset > Factory reset & reset system partitions
make sure that all your zip ready for install via OTG/SD card/ADB
Lineage recovery - Apply update > Choose from sdcard > select the rom and install it
Install magisk .zip (change magisk.apk to magisk.zip if you installing via SD card/OTG)
Reboot to system!
Credits:
@Linux4 - For making the trees and officialy maintaing them in LineageOS, for giving me access to A13 device tree. and for helping me!
@olhotorto - For the server!
right away!
PixelExtended is an open source custom ROM based on the Pixel experience...
Something I do not understand how it is based on it if they have not yet released firmware for this smartphone under android 13 ?
The internet speed indicator is bugged, sometimes it shows, sometimes not. Other than that, it's pretty good. GPay works too.
Can I install this without Magisk?
I have installed Unofficial Lineage OS 20.0.
There is no high touch sensitivity this very important for peoples who has screen protector.
I tried install this and I got error.
ZmisiS said:
Can I install this without Magisk?
I have installed Unofficial Lineage OS 20.0.
Click to expand...
Click to collapse
You can, but why would you do that? You can't pass SafetyNet or use banking apps without it.
Vatt`ghern said:
You can, but why would you do that? You can't pass SafetyNet or use banking apps without it.
Click to expand...
Click to collapse
On Lineage OS 20.0 Unofficial I can use banking apps. I have problem bacouse I can't intall this.
I don't know the path for adb sideolad to install this. I tried to install from the SD card, but it doesn't work.
I have installed Lineage OS Unofficial 20.0. What I need do for install this ROM?
I renamed for update.zip, and convert Magisk.apk to magisk.zip. I install it and after reboot System opened Download mode. Where I wrong?
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
ZmisiS said:
I renamed for update.zip, and convert Magisk.apk to magisk.zip. I install it and after reboot System opened Download mode. Where I wrong?
Click to expand...
Click to collapse
Install it via adb sideload or directly from sdcard and format data (factory reset)
Vatt`ghern said:
Install it via adb sideload or directly from sdcard and format data (factory reset)
Click to expand...
Click to collapse
I maked all reset in Recovery Lineage OS. I installed with ADB. I rename to update. I get same errors.
On 47% I get notification: Signature verification failed. Install anyway?. I click on Yes. Even after this, the system cannot be booted.
https://i.postimg.cc/wTDwxrr0/2022-10-08-22-04-32-Administrator-C-Windows-system32-cmd-exe.png
I downloaded this: PixelExtended-5.0_sweet-13.0-20221006-2140-OFFICIAL
Instead of booting the system, it bootloader opens.
ZmisiS said:
I maked all reset in Recovery Lineage OS. I installed with ADB. I rename to update. I get same errors.
On 47% I get notification: Signature verification failed. Install anyway?. I click on Yes. Even after this, the system cannot be booted.
https://i.postimg.cc/wTDwxrr0/2022-10-08-22-04-32-Administrator-C-Windows-system32-cmd-exe.png
I downloaded this: PixelExtended-5.0_sweet-13.0-20221006-2140-OFFICIAL
Instead of booting the system, it bootloader opens.
Click to expand...
Click to collapse
dude, you are supposed to download the file called like your phone "BEYOND" if your phone it's S10+ just scroll down and download latest beyond2lte file, why are you downloading "sweet" file?
GERATKDASD said:
dude, you are supposed to download the file called like your phone "BEYOND" if your phone it's S10+ just scroll down and download latest beyond2lte file, why are you downloading "sweet" file?
Click to expand...
Click to collapse
Yup, you downloaded a ROM for Xiaomi
I have Samsung Galaxy S10 (SM-G973F). I downloaded from link here. There have many files. I am downloading right file.
ZmisiS said:
I have Samsung Galaxy S10 (SM-G973F). I downloaded from link here. There have many files.
Click to expand...
Click to collapse
You need PixelExtended-5.0_beyond1lte-13.0, you downloaded the PixelExtended-5.0_sweet-13.0. SM-G973F = beyond1lte
Error again.
ERROR: recovery: failed to verify whole-file signature
Update package verification took 34.0s (result 1).
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
Installing update...
ERROR: recovery: Current CPL: 2022-10-05 Target SPL: 2022-09-05 this is considered a downgrade
ERROR: recovery: Denying OTA because it's SPL downgrade
With ADB Sideload same error.
ZmisiS said:
Error again.
ERROR: recovery: failed to verify whole-file signature
Update package verification took 34.0s (result 1).
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
Installing update...
ERROR: recovery: Current CPL: 2022-10-05 Target SPL: 2022-09-05 this is considered a downgrade
ERROR: recovery: Denying OTA because it's SPL downgrade
With ADB Sideload same error.
Click to expand...
Click to collapse
Install recovery from the linked folder.