Related
I tried to install in said mobile phone in TWRP SuperSU-v2.82-201705271822.zip. Unfortunately this fails - see log.
(adb logcat -d | find /i "installer" > logcat.txt has only Zero logcat.txt. "adb logcat" only -> logcat read failure)
The attempt to install systemmode (SR5-SuperSU-v2.82-SYSTEMMODE.zip) was successful in TWRP but after that the smartphone does not start anymore - it hangs in the bootlogo.
I would like to install SuperSU-v2.82-201705271822.zip - Please help!!!
TWRP is Port from Unofficial_TWRP_v3.1.1-0_For_MT6735_64-bit_3.18.19+_Kernel.img and the original recovery.bin (Tutorial: www.chinaphonearena.com/forum/Threa...752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial) TWRP is running and backup in TWRP is ok.
Hardware & Software
-CPU-
SoC Modell: MediaTek MT6735
Kern Architektur: 4xARM Cortex-A53 @ 1300MHz
Befehlssatz: 64-bit ARMv8-A
CPU Kerne: 4
Unterstützte ABIs : (32-bit) armeabi-v7a, armeabi (64-bit) arm64-v8a
AES NEON SHA1 SHA2 : Unterstützt
Build ID : L1288.6.02.05
Baseband : MOLY.LR9.W1444.MD.LWTG.MP.V79.P7,2017/03/27 17:07
Kernel Vision : Linux version 3.18.19+ ([email protected]) (gccversion 4.9.x-google 20140827 (prerelease) (GCC))#1 SMP PREEMPT Mon Jul 10 17:31:07 CST 2017
-SYSTEM-
Hersteller : Lenovo
Modell/Gerät/Produkt : B5032
Marke : MEDION
Hardware/Platform : mt6735
SerienNr.: 11250061740012590
Android ID : 2d76aadb59596ab1
-OS-
Version : 6.0 Marshmallow
API Level : 23
Android Security Patch LVL : 2017-05-05
Fingerprint : MEDION/B5032/B5032:6.0/MRA58K/L1288.6.02.05:user/release-keys
Build ID : MRA58K
card0384 said:
I tried to install in said mobile phone in TWRP SuperSU-v2.82-201705271822.zip. Unfortunately this fails - see log.
(adb logcat -d | find /i "installer" > logcat.txt has only Zero logcat.txt. "adb logcat" only -> logcat read failure)
The attempt to install systemmode (SR5-SuperSU-v2.82-SYSTEMMODE.zip) was successful in TWRP but after that the smartphone does not start anymore - it hangs in the bootlogo...
Click to expand...
Click to collapse
I don't have this device but, the following thread may be helpful to you.
https://forum.xda-developers.com/showthread.php?t=3337484
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello, thanks for your Support. This link cannot fixed my Problem, sorry
Maybe chainfire can look at the logs, I've uploaded all the needed ones
card0384 said:
Maybe chainfire can look at the logs, I've uploaded all the needed ones
Click to expand...
Click to collapse
ChainFire has retired from SuperSU development/support.
as is great, I found the mistake and the solution. The TWRP I used was executable but somehow not right. I have another TWRP used as the basis for porting, so read SuperSu install fine. Class - I have rooted my first cell phone without instructions - I put the instructions for this for other interested in the net
Lineage 17.1 for the Sony Xperia 10 II
Please note this is currently for the dual-sim model ONLY. When you need a single-sim variant leave a comment, so we can work an that...
Code:
/*
* Disclaimer - your warranty may be void.
*
* I'm not responsible for bricked devices, dead OTGs 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.
*/
Features
OTA updates - always delayed for 1 day (to prevent broken rollouts); when you want it immediately, checkout my GitLab pipelines
Increased volume steps to 25
Over-provisioned system image (580MiB), to allow install of OpenGApps and other stuff
Open Source (it is based on SODP, you can view all my patches and ci scripts here or here)
Package signature spoofing (needed by MicroG)
What does not work?
Stock camera app with wide and zoom cameras, you may use Open Camera to circumvent that.
Notification LED blinking - kernel driver bug (see here)
LiveDisplay
You tell me...
Download
There you have multiple options:
To get the complete package (both including the ota and imgparts; only needed for the initial setup) visit...
AndroidFileHost
GitLab (make sure to download the artifacts from the master branch)
To get ONLY the OTA package to update your system later on, visit (or open up the LineageOS Updater) ota.simonmicro.de - please note that only the last recent 14 days are accessible there.
Changelog
2021-02-28
Fixed wifi hotspot.
2020-12-18
Fixed cameras.
2020-11-27
Fixed ADB security.
2020-11-25
Added SELinux support.
2020-11-20
Added OpenGApps support.
2020-11-17
Initial release.
How to install your system
The following guide assumes, you have setup adb and fastboot already (make sure to always use the latest version of the toolkit, otherwise you'll may get problems during flashing) - for that take a look into the internet. Also you should already downloaded the complete package from above!
Unlock the bootloader - a "how to" is here...
Download the oem binaries from here, make sure to use exactly that version!
Boot into the bootloader (hold "Volume up + Insert the USB cable" until led lights blue) and then update the oem partition:
Code:
fastboot flash oem_a [EXTRACTED_OEM_IMAGE_FILE]
fastboot flash oem_b [EXTRACTED_OEM_IMAGE_FILE]
Flash now the Lineage recovery partition as well as the dtbo partition (they are inside the img folder of the complete package):
Code:
fastboot flash recovery [EXTRACTED_RECOVERY_IMAGE_FILE]
fastboot flash dtbo [EXTRACTED_DTBO_IMAGE_FILE]
Disable the verity checks for now, as your new recovery violates the Sony verity profiles of the Stock ROM:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Okay, you are now ready to boot the first time into the Lineage recovery, unplug the phone NOW!
To boot into recovery: Hold "Volume down + Power" until it vibrates...
You should now be booted into the recovery. We now clean any old data from Sonys Stock ROM - this is just to make sure you have a really clean install: Choose the "Factory reset" option.
The phone is now clean and ready to accept the new system. You now can either install just the OTA package and be done or flash every .img from the full package manually - the coice is yours. When you plan to flash the images manually, make sure to include boot, system, product, vendor, vbmeta_system, as these are normally part of the OTA update (I extracted the payload.bin to verify this!). For the latter approach you may orient yourself on my flashall.sh. I'll choose the simpler OTA-sideload approach for now.
Select "Apply update -> Apply from ADB" (now make sure the adb server runs as root - may use adb kill-server && sudo adb start-server to fix that) and execute (the OTA zip is inside the ota subdir):
Code:
adb sideload [OTA_SYSTEM_UPDATE_ZIP_FILENAME]
Something went wrong - help!
(Step 7-8) When you now see a device corrupt error
Don't panic!
You messed up the verity disable step from before - try again.
Try to switch the current boot slot (get current fastboot getvar current-slot and set new fastboot --set-active=, you can choose between a and b) and retry disableing verity disable again!
When your device fails to boot too many times (and crashes) the current slot could also get marked as corrupt. To reset that counter you'll need to reflash the boot partition - to see what is going on, try fastboot getvar all and look out for something like a unbootable flag.
(Step 9) When you get Operation not permitted during flashing
This is commonly caused by relocking and then reunlocking the bootloader (yay - buggy firmware). You'll need to relock, restore (and boot) the device with Flashtool using Sonys original ROM and start from fresh.
(Step 10) When you get the kDownloadPayloadPubKeyVerificationError error
Well, that's caused by using an other recovery than the provided one, as I use my own private keys to sign the build the recovery must also know them. Using an other recovery than the one from
the img folder of the complete package will most likely not include them (and when they do - I am in big trouble), and therefore fail. But you are in luck: It seems that the recovery writes
the data to the currently inactive slot and then fails. You could simply switch the system slot like described above!
Want to install Magisk?
Install the Magisk zip like the OTA system update by using adb sideload [MAGISK_FILE_NAME].
Want to install OpenGApps?
Make sure to use the pico-variant, as the system partition is even with over-provisioning really small (as the installer extracts some more stuff on the first boot) - then install the OpenGApps zip like the OTA system update by using adb sideload [OPENGAPPS_FILE_NAME].
Credits
As much I would like, I can't do everything by myself. A huge thank you to...
@MartinX3 for the used local_manifests and his device tree from his LineageOS organization
...the team behind @sonyxperiadev, for their great work (and their kernel sources)!
XDA:DevDB Information
LineageOS 17.1 for pdx201, ROM for the Sony Xperia 10 II
Contributors
Simonmicro, MartinX3
Source Code: https://gitlab.simonmicro.de/android/lineage/lineage-pdx201
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Sony OEM Package
Based On: AOSP
Version Information
Status: Beta
Hey,
as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.
Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.
Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.
See you next time,
simonmicro
-> https://forum.xda-developers.com/t/...r-xperia-10-ii-ota-sodp.4191601/post-86352693 <-
Reserved
First
At last The guide, source code looks great! Will install, check it next
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
bamdadkhan said:
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
Click to expand...
Click to collapse
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Simonmicro said:
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Click to expand...
Click to collapse
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
bamdadkhan said:
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
Click to expand...
Click to collapse
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Simonmicro said:
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Click to expand...
Click to collapse
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Thapsus-cz said:
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Click to expand...
Click to collapse
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Click to expand...
Click to collapse
See full log for flashing images:
sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
[sudo] пароль для :
Sending 'boot_b' (65536 KB) OKAY [ 2.441s]
Writing 'boot_b' OKAY [ 0.358s]
Finished. Total time: 2.812s
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'product' (432072 KB) OKAY [ 16.440s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (48084 KB) OKAY [ 1.725s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.016s
❯ sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
❯ sudo fastboot flash boot boot.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash product product.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash super_empty super_empty.img
sudo fastboot flash system system.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash vbmeta_system vbmeta_system.img
sudo fastboot flash vendor vendor.img
Sending 'boot_b' (65536 KB) OKAY [ 2.438s]
Writing 'boot_b' OKAY [ 0.378s]
Finished. Total time: 2.831s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.357s
Sending 'product' (432072 KB) OKAY [ 16.212s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.699s]
Writing 'recovery' OKAY [ 0.557s]
Finished. Total time: 4.265s
Sending 'super_empty' (4 KB) OKAY [ 0.011s]
Writing 'super_empty' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.755s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'vendor' (48084 KB) OKAY [ 1.770s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Click to expand...
Click to collapse
xdauserart said:
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
See full log for flashing images:
Click to expand...
Click to collapse
I had the same problem yesterday with the same results. I struggled with it until morning. Eventually I downloaded the latest version of adb, flashed the stock rom again and started over. It was done in twenty minutes. Try the latest version of adb (I guess version 35 for Windows)
xdauserart said:
Done till the step 9.
Click to expand...
Click to collapse
...
Code:
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
This indicates you tried to use the bootloader (which also has fastboot support) to flash the images. I made sure to write the guide the way that it states you should use the fastbootd service of the recovery. I have the dumb feeling that many more will go your way and fail. Damn it.
Code:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Is fine, as you just erased all data - this also kills the partion so it cant be mounted anymore (that's the errors). This is indeed intentional as the system is now forced to really start fresh!
xdauserart said:
Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
Click to expand...
Click to collapse
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Two PR to fix back triple cam. But front cam is still broken.
https://github.com/sonyxperiadev/device-sony-seine/pull/29
https://github.com/sonyxperiadev/device-sony-pdx201/pull/15
--------------EDIT-----------------
Switch to CAF powerhal, better performance we have.
https://github.com/sjllls/device-sony-common/commit/de3b2bbbc33130891263d9e81ea2178a0f6783c4
https://github.com/sjllls/device-sony-sepolicy/commit/72059258eb0ff2c854996a05a5a23a8b73b55459
--------------EDIT-----------------
Renmember to let users flash with latest platform-tools, or they could not boot because of logical partition is not resized.
https://developer.android.com/studio/releases/platform-tools
Simonmicro said:
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Click to expand...
Click to collapse
I can confirm that Opengapps pico can now be installed without a bootloop. I'm at work and I don't have adb. I installed them directly as an update from the sd card using recovery. Everything works fine.
Can we get OpenGapps Nano support?
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
KriiXOne said:
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
Click to expand...
Click to collapse
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Simonmicro said:
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Click to expand...
Click to collapse
I'll try tomorrow after the math test that i'm studying for today, and will let ya know ^^'
Simonmicro said:
...
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Click to expand...
Click to collapse
Fixed it Just repeated the steps from the first one and used OTA on step 9. Thanks!
{
"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 10.0, 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.
Code:
#include "std_disclaimer.h"
/*
* 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.
*/
What's working:
RIL (Calls, SMS, Data)
IMS
Fingerprint
Wi-Fi
Bluetooth
Bluetooth Audio
Camera
Audio
Sensors
Flash
GPS
DAC
Vibration
Wifi Hotspot
Display out
Wireless display
Selinux enforcing
What's not working:
a2dp offload
Flashing Instructions:
Go to the first (pre) release in the downloads, and download the boot.img, vendor_boot.img, dtbo.img and copy-partitions-20220222.zip
Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off)
Code:
fastboot flash boot boot.img
Code:
fastboot flash vendor_boot vendor_boot.img
Code:
fastboot flash dtbo dtbo.img
Use volume keys and power to reboot to recovery, or use
Code:
fastboot reboot recovery
If you dont have both slots populated, nows your chance:
a) Enable adb sideload
b) Flash the copy partitions script:
Code:
adb sideload copy-partitions-20220222.zip
Enable adb sideload and flash LineageOS:
Code:
adb sideload lineage-19.1-20220327-UNOFFICIAL-pstar.zip
- replace zip name if needed -
Reboot to recovery: Advanced -> Reboot recovery
(Optional) Flash Gapps/Magisk:
a) Enable adb sideload and:
Code:
adb sideload gapps.zip
(similar for magisk)
Factory reset/format data
Reboot system
Profit
Edge 20 Pro Telegram group
Downloads:
pstar releases here: github
Sources:
Device Tree pstar: pstar
Device Tree sm8250-common: sm8250-common
Kernel: sm8250
Vendor: motorola
lineage-19.1 branches
XDA:DevDB Information
LineageOS for the Motorola Edge 20 Pro, ROM for the Motorola Edge 20 Pro
Contributors
SGCMarkus
Source Code: https://github.com/LineageOS
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
ROM Firmware Required: 11
Based On: LineageOS
Version Information
Status: Stable
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless). Also dump /dev/block/bootdevice/by-name/pstore and attach that
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 27.03.2022 (LOS19)
- First public release
Reserved
nice work
Thanks for your work. I'll give it a try this evening.
LOS 19.1 works fine. I use MGC 8.1.101 as camera app. Battery drain is ok.
Thanks for the great work, it works nice and stable.
Any chance of this ROM getting an update?
SGCMarkus said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0, 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.
Code:
#include "std_disclaimer.h"
/*
* 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.
*/
What's working:
RIL (Calls, SMS, Data)
IMS
Fingerprint
Wi-Fi
Bluetooth
Bluetooth Audio
Camera
Audio
Sensors
Flash
GPS
DAC
Vibration
Wifi Hotspot
Display out
Wireless display
Selinux enforcing
What's not working:
a2dp offload
Flashing Instructions:
Go to the first (pre) release in the downloads, and download the boot.img, vendor_boot.img, dtbo.img and copy-partitions-20220222.zip
Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off)
Code:
fastboot flash boot boot.img
Code:
fastboot flash vendor_boot vendor_boot.img
Code:
fastboot flash dtbo dtbo.img
Use volume keys and power to reboot to recovery, or use
Code:
fastboot reboot recovery
If you dont have both slots populated, nows your chance:
a) Enable adb sideload
b) Flash the copy partitions script:
Code:
adb sideload copy-partitions-20220222.zip
Enable adb sideload and flash LineageOS:
Code:
adb sideload lineage-19.1-20220327-UNOFFICIAL-pstar.zip
- replace zip name if needed -
Reboot to recovery: Advanced -> Reboot recovery
(Optional) Flash Gapps/Magisk:
a) Enable adb sideload and:
Code:
adb sideload gapps.zip
(similar for magisk)
Factory reset/format data
Reboot system
Profit
Edge 20 Pro Telegram group
Downloads:
pstar releases here: github
Sources:
Device Tree pstar: pstar
Device Tree sm8250-common: sm8250-common
Kernel: sm8250
Vendor: motorola
lineage-19.1 branches
XDA:DevDB Information
LineageOS for the Motorola Edge 20 Pro, ROM for the Motorola Edge 20 Pro
Contributors
SGCMarkus
Source Code: https://github.com/LineageOS
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
ROM Firmware Required: 11
Based On: LineageOS
Version Information
Status: Stable
Click to expand...
Click to collapse
how to download all files
SGCMarkus said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0, 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.
Code:
#include "std_disclaimer.h"
/*
* 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.
*/
What's working:
RIL (Calls, SMS, Data)
IMS
Fingerprint
Wi-Fi
Bluetooth
Bluetooth Audio
Camera
Audio
Sensors
Flash
GPS
DAC
Vibration
Wifi Hotspot
Display out
Wireless display
Selinux enforcing
What's not working:
a2dp offload
Flashing Instructions:
Go to the first (pre) release in the downloads, and download the boot.img, vendor_boot.img, dtbo.img and copy-partitions-20220222.zip
Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off)
Code:
fastboot flash boot boot.img
Code:
fastboot flash vendor_boot vendor_boot.img
Code:
fastboot flash dtbo dtbo.img
Use volume keys and power to reboot to recovery, or use
Code:
fastboot reboot recovery
If you dont have both slots populated, nows your chance:
a) Enable adb sideload
b) Flash the copy partitions script:
Code:
adb sideload copy-partitions-20220222.zip
Enable adb sideload and flash LineageOS:
Code:
adb sideload lineage-19.1-20220327-UNOFFICIAL-pstar.zip
- replace zip name if needed -
Reboot to recovery: Advanced -> Reboot recovery
(Optional) Flash Gapps/Magisk:
a) Enable adb sideload and:
Code:
adb sideload gapps.zip
(similar for magisk)
Factory reset/format data
Reboot system
Profit
Edge 20 Pro Telegram group
Downloads:
pstar releases here: github
Sources:
Device Tree pstar: pstar
Device Tree sm8250-common: sm8250-common
Kernel: sm8250
Vendor: motorola
lineage-19.1 branches
XDA:DevDB Information
LineageOS for the Motorola Edge 20 Pro, ROM for the Motorola Edge 20 Pro
Contributors
SGCMarkus
Source Code: https://github.com/LineageOS
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
ROM Firmware Required: 11
Based On: LineageOS
Version Information
Status: Stable
Click to expand...
Click to collapse
how to download all files Except LineageOS
monsmons262626 said:
how to download all files Except LineageOS
Click to expand...
Click to collapse
Release pstar (Motorola Edge 20 Pro) initial release · SGCMarkus/Lineage-OTA
Lineage OS 19 for Motorola Edge 20 Pro Flashing instructions: Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off) fastboot flash boot boot.img fastboot flash ...
github.com
ilia3367 said:
Release pstar (Motorola Edge 20 Pro) initial release · SGCMarkus/Lineage-OTA
Lineage OS 19 for Motorola Edge 20 Pro Flashing instructions: Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off) fastboot flash boot boot.img fastboot flash ...
github.com
Click to expand...
Click to collapse
thank alot but may phone now is deadboot because icant see this replay huhu i flash lineageos not to sideload mode
i try to via twrp after that deadboot my phone huhu
monsmons262626 said:
thank alot but may phone now is deadboot because icant see this replay huhu i flash lineageos not to sideload mode
i try to via twrp after that deadboot my phone huhu
Click to expand...
Click to collapse
with "deadboot" you mean its going into edl/9008?
You probably didnt copy slot a to b (as written in the instructions)
TWRP *shouldnt* (never tried it) be the problem though.
SGCMarkus said:
TWRP *shouldnt* (never tried it) be the problem though.
Click to expand...
Click to collapse
TWRP on Android 12 doesn't work...
SGCMarkus said:
with "deadboot" you mean its going into edl/9008?
You probably didnt copy slot a to b (as written in the instructions)
TWRP *shouldnt* (never tried it) be the problem though.
Click to expand...
Click to collapse
sorry i cant read all instruction
yes my phone is into edl/9008
i try blank-flash.bat but nor working
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.016] ...cpu.id = 195 (0xc3)
[ 0.016] ...cpu.sn = 1399562115 (0x536b9f83)
[ 0.016] Opening singleimage
[ 0.125] Loading package
[ 0.219] ...filename = pkg.xml
[ 0.234] Loading programmer
[ 0.266] ...filename = programmer.elf
[ 0.266] Sending programmer
[ 0.317] ReadFile() failed, GetLastError()=0
[ 0.557] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.557] ERROR: sahara_download()->general error
[ 0.557] Check qboot_log.txt for more details
[ 0.557] Total time: 0.557s
FAILED: qb_flash_singleimage()->sahara_download()->general error
ilia3367 said:
TWRP on Android 12 doesn't work...
Click to expand...
Click to collapse
working but not this files
ilia3367 said:
TWRP on Android 12 doesn't work...
Click to expand...
Click to collapse
with that i meant it shouldnt have a problem to flash LOS, for anything else... no guarantee.
monsmons262626 said:
sorry i cant read all instruction
yes my phone is into edl/9008
i try blank-flash.bat but nor working
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.016] ...cpu.id = 195 (0xc3)
[ 0.016] ...cpu.sn = 1399562115 (0x536b9f83)
[ 0.016] Opening singleimage
[ 0.125] Loading package
[ 0.219] ...filename = pkg.xml
[ 0.234] Loading programmer
[ 0.266] ...filename = programmer.elf
[ 0.266] Sending programmer
[ 0.317] ReadFile() failed, GetLastError()=0
[ 0.557] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.557] ERROR: sahara_download()->general error
[ 0.557] Check qboot_log.txt for more details
[ 0.557] Total time: 0.557s
FAILED: qb_flash_singleimage()->sahara_download()->general error
Click to expand...
Click to collapse
Not too familiar with what motorolas blank flash does, but i suppose it only flashes 1 slot? and might not reset slots.
What you could do is dump all of slot a in qfil or with bkerler's edl python script, and then flash them to slot b (aka what the copy partitions zip does, which you should have flashed, if you read the instructions...).
But if you ever had an OTA that *shouldnt* be necessary actually, and at this point its unlikely the phone is that fresh it never OTA'd.
SGCMarkus said:
with that i meant it shouldnt have a problem to flash LOS, for anything else... no guarantee.
Not too familiar with what motorolas blank flash does, but i suppose it only flashes 1 slot? and might not reset slots.
What you could do is dump all of slot a in qfil or with bkerler's edl python script, and then flash them to slot b (aka what the copy partitions zip does, which you should have flashed, if you read the instructions...).
But if you ever had an OTA that *shouldnt* be necessary actually, and at this point its unlikely the phone is that fresh it never OTA'd.
Click to expand...
Click to collapse
Sir how to make prog emmc Firehouse .mbn for Motorola edge 20 pro
Does someone know when an official build wil come out?
Nearly perfect!
The only issue I found it is that the search button configuration isn't working.
PS: My edge s pro becomes edge 20 pro after flashing this rom.
The most important step to automate the installation and configuration of the Android OS is the installation of an OS image via script without user intervention. One method to do that is using the binary twrp from the recovery TWRP .
The twrp command to install an OS image with twrp is
Code:
/system/bin/twrp install /path/to/update.zip
The usage for the binary twrp is (see also here)
Spoiler: twrp usage help
Code:
I006D:/ # /system/bin/twrp --help
TWRP openrecoveryscript command line tool, TWRP version 3.7.0_12-0
Allows command line usage of TWRP via openrecoveryscript commands.
Some common commands include:
install /path/to/update.zip
backup <SDCRBAEM> [backupname]
restore <SDCRBAEM> [backupname]
wipe <partition name>
format data
sideload
set <variable> [value]
decrypt <password> [USER ID]
remountrw
fixperms
mount <path>
unmount <path>
listmounts
print <value>
mkdir <directory>
reboot [recovery|poweroff|bootloader|download|edl]
See more documentation at https://twrp.me/faq/openrecoveryscript.html
I006D:/ #
The binary twrp can also be used to wipe the data from the phone using the parameter wipe <partition_name>.
The command twrp install will not change the active boot slot for the next reboot so this must be done manually after installing the OS image. This can be done using the binary bootctl which is also part of TWRP.
The usage for the command bootctl is:
Spoiler: bootctl usage help
Code:
ASUS_I006D:/ # /system/bin/bootctl -h
/system/bin/bootctl - command-line wrapper for the boot HAL.
Usage:
/system/bin/bootctl COMMAND
Commands:
hal-info - Show info about boot_control HAL used.
get-number-slots - Prints number of slots.
get-current-slot - Prints currently running SLOT.
mark-boot-successful - Mark current slot as GOOD.
get-active-boot-slot - Prints the SLOT to load on next boot.
set-active-boot-slot SLOT - On next boot, load and execute SLOT.
set-slot-as-unbootable SLOT - Mark SLOT as invalid.
is-slot-bootable SLOT - Returns 0 only if SLOT is bootable.
is-slot-marked-successful SLOT - Returns 0 only if SLOT is marked GOOD.
get-suffix SLOT - Prints suffix for SLOT.
set-snapshot-merge-status STAT - Sets whether a snapshot-merge of any dynamic
partition is in progress. Valid STAT values
are: none, unknown, snapshotted, merging,
or cancelled.
get-snapshot-merge-status - Prints the current snapshot-merge status.
SLOT parameter is the zero-based slot-number.
64|ASUS_I006D:/ #
Afterwards the phone can be rebooted to activate the new installed OS
So the commands for installing an OS image via twrp are
- boot the phone from the TWRP image
- (optional) use twrp to wipe the data
- copy the OS image file via adb push to the phone
- install the OS image file via the twrp binary
- change the next active boot slot via the binary bootctl.
- reboot the phone
I wrote a simple script to just do that
install_os_via_twrp.sh
The usage of the script is :
Code:
[ OmniRom 13 Dev - [email protected] /data/develop/android/scripts_on_linux ] $ ./install_os_via_twrp.sh -h
install_os_via_twrp.sh version - v1.0.0.0 - install an OS image via the TWRP command twrp
install_os_via_twrp.sh [-h|help|-H] [--reboot|--noreboot] [force] [wipe|wipeall] [wipe_cache] [wipe_data] [wipe_dalvik] [format_data] [format_metadata] [factory_reset] [os_image_file]
[ OmniRom 13 Dev - [email protected] /data/develop/android/scripts_on_linux ] $
Use the parameter --help or -H to view the detailed usage help
Spoiler: Detailed usage help for install_os_via_twrp.sh
Code:
[ OmniRom 13 Dev - [email protected] /data/develop/android/scripts_on_linux ] $ ./install_os_via_twrp.sh -H
install_os_via_twrp.sh version - v1.0.0.0 - install an OS image via the TWRP command twrp
Usage
install_os_via_twrp.sh [-h|help|-H] [--reboot|--noreboot] [force] [wipe|wipeall] [wipe_cache] [wipe_data] [wipe_dalvik] [format_data] [format_metadata] [factory_reset] [os_image_file]
All parameter are optional, except the parameter for the OS image to install "os_image_file".
The parameter can be used in any order.
Use the parameter "help" or "-H" to print the detailed usage help; use the parameter "-h" to print only the short usage help
If the parameter "--reboot" is used the script will reboot the phone after successfully installing the OS image; to disable the automatic reboot use the parameter "--noreboot".
Default is to ask the user for confirmation to reboot the phone.
Use the parameter "wipe" or "wipeall" to wipe /data, /cache, and Dalvik before installing the OS image.
Use one or more of the parameter "wipe_cache", "wipe_data", or "wipe_dalvik" to only wipe some of the partitions used.
Use the parameter "format_metadata" to format the meta data partition; this wipe is NOT included in "wipe_all"
Use the parameter "format_data" to format the data partition; this wipe is NOT included in "wipe_all"
Use the parameter "factory_reset" to do a factory reset before installing the OS image; a factory reset is done by formatting the data and the metadata partitions.
Use the parameter "force" to ignore errors while wiping or formatting the data; without this parameter the script will abort if one of the wipe or format commands fails
To change some of the values used by the script these environment variables can be set before starting the script:
Set the environment variable REBOOT to "yes" before starting the script to automatically reboot the phone after enabling the root access
Set the environment variable REBOOT to "no" before starting the script to disable the automatic reboot after enabling the root access
Set the environment variable UPLOAD_DIR_ON_THE_PHONE to set the upload directory for the OS image file on the phone (default dir is /tmp; /tmp is mounted on a ramdiks)
See also the source code of the script
boot_phone_from_twrp.sh
for environment variables supported by this script
Prerequisites
- the phone must be connected via USB
- there must be a working connection to the phone using fastboot or adb
- a working TWRP image for the phone must exist
The script boot_phone_from_twrp.sh is required by this script -- see the source code of the script
[ OmniRom 13 Dev - [email protected] /data/develop/android/scripts_on_linux ] $
Note:
The script needs the helper script boot_phone_from_twrp.sh.sh (see How to boot a phone from a twrp recovery image)
Spoiler: Sample output of the script installing a new version of the same OS
Code:
[ OmniRom 13 Dev - [email protected] /data/develop/android/scripts_on_linux ] $ REBOOT=yes /data/develop/android/scripts_on_linux/install_os_via_twrp.sh /data/backup/ASUS_ZENFONE8/omnirom/omni-13/omni-13-202212180505-zenfone8-MICROG.zip
install_os_via_twrp.sh version - v1.0.0.0 - install an OS image via the TWRP command twrp
Using the TWRP helper script "/data/develop/android/scripts_on_linux/boot_phone_from_twrp.sh"
The OS image to install is: "/data/backup/ASUS_ZENFONE8/omnirom/omni-13/omni-13-202212180505-zenfone8-MICROG.zip"
Reading the helper script "boot_phone_from_twrp.sh" ...
The script is running as user "xtrnaw7" -- will use "sudo" for the fastboot commands ...
Will use the attached phone with the serial number "M6AIB760D0939LX"
Using the default TWRP image: "/data/backup/ASUS_ZENFONE8/twrp/current_twrp.img"
Using the options " -s M6AIB760D0939LX " for the adb commands
Using the options " -s M6AIB760D0939LX " for the fastboot commands
Checking the script prerequisites ...
Will wait up to 60 second(s) after booting the phone into the bootloader
Will wait up to 60 second(s) after booting the phone from the TWRP image
Will wait up to 10 second(s) until the adb daemon is ready to use
Retrieving the current status of the phone ...
The phone is currently booted into the Android OS
The phone is booted into the Android OS
Booting the phone into the bootloader now ...
Waiting up to 60 seconds for the boot into the fastboot mode ...
The phone is booted into the bootloader
Booting the phone from the TWRP image "/data/backup/ASUS_ZENFONE8/twrp/current_twrp.img" now ...
Sending 'boot.img' (98304 KB) OKAY [ 2.833s]
Booting OKAY [ 10.359s]
Finished. Total time: 13.243s
Waiting up to 60 seconds for the boot of the phone ....
Waiting up to 10 seconds for the adb daemon to get ready ..
... the adb daemon is ready after second(s)
The phone is booted into TWRP: "twrp_I006D" version "3.7.0_12-0"
Waiting up to 10 seconds for the adb daemon to get ready
... the adb daemon is ready after second(s)
Coyping the OS image file "/data/backup/ASUS_ZENFONE8/omnirom/omni-13/omni-13-202212180505-zenfone8-MICROG.zip" to "/tmp/omni-13-202212180505-zenfone8-MICROG.zip" on the phone ...
adb: error: failed to read copy response8-MICROG.zip
/data/backup/ASUS_ZENFONE8/omnirom/omni-13/omni-13-202212180505-zenfone8-MICROG.zip: 1 file pushed, 0 skipped. 201.8 MB/s (1261116637 bytes in 5.959s)
adb: error: failed to read copy response
adb: device 'M6AIB760D0939LX' not found
Copying the image failed -- we will do another try in 5 seconds ...
/data/backup/ASUS_ZENFONE8/omnirom/omni-13/omni-13-202212180505-zenfone8-MICROG.zip: 1 file pushed, 0 skipped. 32.5 MB/s (1261116637 bytes in 37.056s)
Installing the OS image "/tmp/omni-13-202212180505-zenfone8-MICROG.zip" into the slot "_b" ...
Installing zip file '/tmp/omni-13-202212180505-zenfone8-MICROG.zip'
Flashing A/B zip to inactive slot: B
Step 1/2Step 2/2Updating partition details...
...done
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
Done processing script file
OS image file "/tmp/omni-13-202212180505-zenfone8-MICROG.zip" successfully installed.
Now changing the next active slot to _b ...
... successfully changed the active slot for the next reboot
Rebooting the phone now ...
Booting the Android OS using the command "adb reboot " now ...
[ OmniRom 13 Dev - [email protected] /data/develop/android/scripts_on_linux ] $
Spoiler: Sample output of the script installing another OS in the inactive slot
Code:
[ OmniRom 13 Dev - [email protected] /data/develop/android/scripts_on_linux ] $ /data/develop/android/scripts_on_linux/install_os_via_twrp.sh factory_reset /data/backup/ASUS_ZENFONE8/Lineage-19_Android12/lineage-19.1-20221216-nightly-sake-signed.zip
install_os_via_twrp.sh version - v1.0.0.0 - install an OS image via the TWRP command twrp
Using the TWRP helper script "/data/develop/android/scripts_on_linux/boot_phone_from_twrp.sh"
The OS image to install is: "/data/backup/ASUS_ZENFONE8/Lineage-19_Android12/lineage-19.1-20221216-nightly-sake-signed.zip"
Reading the helper script "boot_phone_from_twrp.sh" ...
The script is running as user "xtrnaw7" -- will use "sudo" for the fastboot commands ...
Will use the attached phone with the serial number "M6AIB760D0939LX"
Using the default TWRP image: "/data/backup/ASUS_ZENFONE8/twrp/current_twrp.img"
Using the options " -s M6AIB760D0939LX " for the adb commands
Using the options " -s M6AIB760D0939LX " for the fastboot commands
Checking the script prerequisites ...
Will wait up to 60 second(s) after booting the phone into the bootloader
Will wait up to 60 second(s) after booting the phone from the TWRP image
Will wait up to 10 second(s) until the adb daemon is ready to use
Retrieving the current status of the phone ...
The phone is currently booted into the Android OS
The phone is booted into the Android OS
Booting the phone into the bootloader now ...
Waiting up to 60 seconds for the boot into the fastboot mode ...
The phone is booted into the bootloader
Booting the phone from the TWRP image "/data/backup/ASUS_ZENFONE8/twrp/current_twrp.img" now ...
Sending 'boot.img' (98304 KB) OKAY [ 2.840s]
Booting OKAY [ 10.406s]
Finished. Total time: 13.286s
Waiting up to 60 seconds for the boot of the phone ....
Waiting up to 10 seconds for the adb daemon to get ready ..
... the adb daemon is ready after second(s)
The phone is booted into TWRP: "twrp_I006D" version "3.7.0_12-0"
Waiting up to 10 seconds for the adb daemon to get ready
... the adb daemon is ready after second(s)
Wiping all data including media ...
Done.
You may need to reboot recovery to be able to use /data again.
TWRP will not recreate /data/media on an FBE device. Please reboot into your rom to create /data/media
Formatting Metadata using mke2fs...
Done.
Done processing script file
Wiping the metadata ...
++ /usr/bin/adb -s M6AIB760D0939LX shell umount /dev/block/by-name/metadata
umount: /dev/block/sda22: Invalid argument
++ /usr/bin/adb -s M6AIB760D0939LX shell mke2fs -F -t ext4 /dev/block/by-name/metadata
mke2fs 1.45.4 (23-Sep-2019)
Discarding device blocks: done
Creating filesystem with 4096 4k blocks and 4096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Coyping the OS image file "/data/backup/ASUS_ZENFONE8/Lineage-19_Android12/lineage-19.1-20221216-nightly-sake-signed.zip" to "/tmp/lineage-19.1-20221216-nightly-sake-signed.zip" on the phone ...
adb: error: failed to read copy responsey-sake-signed.zip
/data/backup/ASUS_ZENFONE8/Lineage-19_Android12/lineage-19.1-20221216-nightly-sake-signed.zip: 1 file pushed, 0 skipped. 313.7 MB/s (1114300349 bytes in 3.387s)
adb: error: failed to read copy response
adb: device 'M6AIB760D0939LX' not found
Copying the image failed -- we will do another try in 5 seconds ...
/data/backup/ASUS_ZENFONE8/Lineage-19_Android12/lineage-19.1-20221216-nightly-sake-signed.zip: 1 file pushed, 0 skipped. 32.5 MB/s (1114300349 bytes in 32.719s)
Installing the OS image "/tmp/lineage-19.1-20221216-nightly-sake-signed.zip" into the slot "_a" ...
Installing zip file '/tmp/lineage-19.1-20221216-nightly-sake-signed.zip'
Flashing A/B zip to inactive slot: A
Step 1/2Step 2/2Updating partition details...
...done
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
Done processing script file
OS image file "/tmp/lineage-19.1-20221216-nightly-sake-signed.zip" successfully installed.
Now changing the next active slot to _a ...
... successfully changed the active slot for the next reboot
*** Press return to reboot the phone now
Rebooting the phone now ...
Booting the Android OS using the command "adb reboot " now ...
[ OmniRom 13 Dev - [email protected] /data/develop/android/scripts_on_linux ] $
Testenvironment
I tested the script using this hardware and software:
Hardware:
ASUS Zenfone 8
TWRP
TWRP 3.7.0.12
OS Images installed via script
OmniROM 12
OmniROM 13
LineageOS 19
The script does not work for the images with the original Android from ASUS; the OS installation works but the phone does not boot from the new installation
The script install_os_via_twrp.sh is also available on my home page:
install_os_via_twrp.sh
Trouble Shooting
To update the installed OS to a new version in most cases neither a wipe nor a factory reset is necessary.
To install a different distribution on the phone in most cases a factory reset is required. (e.g installing LIneageOS if the current OS is OmniROM)
riceDroid for OnePlus 8T|9R [kebab][lemonades]
{
"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"
}
What is riceDroid?
* Ricedroid is a FREE OPENSOURCE Android Operating System based on LineageOS and crDroid, that aims to provide necessary "ricing" aka customizations for ANDROID while being fast and stable. This operating system is highly inspired by Oxygen OS (10-11) and nothingOS, we strive to make things different but not too far from AOSP.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The term \'rice\' is used to describe a person's unix desktop where \'ricing\' is an act where someone customizes their desktop such as the changing icons, panels or system interface.
source: https://jie-fang.github.io/blog/basics-of-ricing
Based on Android 13 | Tiramisu QPR1
What's working?
Most basic stuffs
Bugs and Issues
Please tell me with a logcat attached
Variants available
CORE build only - comes with basic gapps, no setupwizard
Device specific changes
Based on OOS 12 Firmware, Flashing OOS 12 firmware is a must before installing, boots on OOS13 firmware but touchscreen doesn't work
Shipped with OOS Camera - most features exposed working.
Shipped with Chaeyo.0 kernel - based from OOS 12 kernel source - CFS scheduler focused kernel.
Credits
LineageOS kebab team - for most of device/kernel tree changes
chandu078 - base device/vendor tree
cjh1249131356 - oneplus camera source
Notes
I will only maintain Official GMS core variant based on OOS 12 due to limited free time. Other variants will be officially maintained by sir manidreddy a.k.a Lord Itachi
If you have any type of concerns, please address it here, I'll try to accommodate as soon as I see the message.
Changelog
Source Changelog
Download link
riceDroid-13.0-202302220426-kebab-v10.2-CORE-OFFICIAL.zip
Installation Guide
Fastboot - recommended method
1. Download SDK platform tools here and follow this tutorial
2. Reboot to fastboot
3. Enter fastboot mode
4. Perform flashing commands listed on attached file: fastboot-commands
5. Enter recovery mode
6. Wipe data/cache/dalvik-cache
7. Sideload preferred zip files (magisk, gapps etc.)
8. Reboot to system
Sideload - recommended for those who were able to flash oos 12 on both A/B slots
1. fastboot flash recovery.img from firmware payload.bin
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, gapps etc.)
7. Reboot to system
Android OS version: 13.0.0_r30
Security patch level: February 2023
Build author/Device Maintainer: dlwlrma123
Device tree source code: https://github.com/ricedroidOSS-devices/device_oneplus_kebab
Device vendor source code: https://github.com/ricedroidOSS-devices/vendor_oneplus_kebab
Kernel source code: https://github.com/ricedroidOSS-devices/android_kernel_oneplus_sm8250
Firmware source code: https://github.com/ricedroidOSS
Firmware created by: The ricedroidOSS Team
Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
02/22/23 - Filename: riceDroid-13.0-202302220426-kebab-v10.2-CORE-OFFICIAL.zip
- fixed misc bug from source
- fixed dolby effects
- portrait video mode is a bit usable
- last update for kebab from me, my oneplus 9R got a vertical green line after trying OOS 13, so i will be selling the device at a low price and will shift to another device.
Wonderful to see riceDroid on 8T. I have been using it on Xiaomi 11T pro and love riceDroid.
I am currently on OOS 13 firmware on kebab. Do I have to downgrade it to OOS 12 firmware? If so, which version of the firmware?
Would this version be okay to flash riceDroid?
OP8T_DDR4_Android12_C36_IN_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
RainGater said:
Wonderful to see riceDroid on 8T. I have been using it on Xiaomi 11T pro and love riceDroid.
I am currently on OOS 13 firmware on kebab. Do I have to downgrade it to OOS 12 firmware? If so, which version of the firmware?
Would this version be okay to flash riceDroid?
OP8T_DDR4_Android12_C36_IN_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Hi! Downgrading to OOS 12 firmware is a must to avoid flashing related problems, about the version, i believe any version is fine.
dlwlrma123 said:
Hi! Downgrading to OOS 12 firmware is a must to avoid flashing related problems, about the version, i believe any version is fine.
Click to expand...
Click to collapse
Thanks. I don't see installation instructions as I am currently on latest Nameless A13 ROM with OOS 13 firmware.
So, basically
1. adb reboot recovery
2. sideload the OOS 12 firmware
3. sideload ROM
4. sideload Magisk 25.2
5. sideload NikGapps OMNI A13 as I need setup wizard to copy data from Google backup (NikGapps-omni-arm64-13-20230111-signed.zip)
6. wipe Data
7. reboot to system
Does it sound right?
RainGater said:
Thanks. I don't see installation instructions as I am currently on latest Nameless A13 ROM with OOS 13 firmware.
So, basically
1. adb reboot recovery
2. sideload the OOS 12 firmware
3. sideload ROM
4. sideload Magisk 25.2
5. sideload NikGapps OMNI A13 as I need setup wizard to copy data from Google backup (NikGapps-omni-arm64-13-20230111-signed.zip)
6. wipe Data
7. reboot to system
Does it sound right?
Click to expand...
Click to collapse
Oh dear, i forgot to add the installation guide, thanks for this. I'll add a guide in a few minutes. As per your installation, i believe the method is same for other roms, you may want to use fastboot method (fastboot enhanced or native fastboot) to avoid recovery installation errors
dlwlrma123 said:
Oh dear, i forgot to add the installation guide, thanks for this. I'll add a guide in a few minutes. As per your installation, i believe the method is same for other roms, you may want to use fastboot method (fastboot enhanced or native fastboot) to avoid recovery installation errors
Click to expand...
Click to collapse
I can flash nikgapps OMNI (NikGapps-omni-arm64-13-20230111-signed.zip)) along with Magisk, correct? Since you are only providing core, would it be a problem to flash OMNI?
RainGater said:
I can flash nikgapps OMNI (NikGapps-omni-arm64-13-20230111-signed.zip)) along with Magisk, correct? Since you are only providing core, would it be a problem to flash OMNI?
Click to expand...
Click to collapse
i can only recommend nikgapps addons to avoid conflict with google apps shipped with core.
dlwlrma123 said:
i can only recommend nikgapps addons to avoid conflict with google apps shipped with core.
Click to expand...
Click to collapse
Hmmm... I am not able to install setup addon (NikGapps-Addon-13-SetupWizard-20220908-signed.zip) as it's giving me this error: Skipping setupwizard due to insufficient space. Bummer!
RainGater said:
Hmmm... I am not able to install setup addon (NikGapps-Addon-13-SetupWizard-20220908-signed.zip) as it's giving me this error: Skipping setupwizard due to insufficient space. Bummer!
Click to expand...
Click to collapse
It seems like i wasn't able to setup partitions spaces for flashable zips, I will create a new build with this problem addressed, Sorry for the inconvenience..
dlwlrma123 said:
It seems like i wasn't able to setup partitions spaces for flashable zips, I will create a new build with this problem addressed, Sorry for the inconvenience..
Click to expand...
Click to collapse
I was about to flash.. should i wait for this new build ? Also the fastboot enhance link isn't working.
alp47470 said:
I was about to flash.. should i wait for this new build ? Also the fastboot enhance link isn't working.
Click to expand...
Click to collapse
Hello, fastboot enhance link updated, thanks for noticing! The current build is fine if you're just gonna flash magisk but if you are going to flash external gapps, its better to wait for the new build. Ill upload the new build after testing.
dlwlrma123 said:
Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
Click to expand...
Click to collapse
Fixed version has been pushed for changelogs, please refer to post#2
Nic
dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Nice. Thanks for quick fixes
Can you please confirm if the build has in-built app lock ?
alp47470 said:
Nic
Nice
Can you confirm if the build has in-built app lock ?
Click to expand...
Click to collapse
Yes, it has in-built applock feature.
Thanks for this beautiful rom. After flashing i noticed that there is some dullness when seeing photos or wallpapers (like more on the darker side). Tried all display calibrations like vivid, saturated etc. Is that normal?
Flashed based on 12.c.36 using adb sideload for OnePlus 9r
dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Thank you for the quick fix. BTW, will I be able to flash the full Gapps or only the add-ons?
dlwlrma123 said:
Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
Click to expand...
Click to collapse
I am getting the error when sideloading the ROM. Please see the attacehd image. I downloaded again and still the same error.
EDIT: Now, my partitions are corrupted and even when flashing through fastboot, I am getting partition not found errors. How do I get it working now? Only MSM or will it boot now even after the "partition not found" errors?
Code:
Sending 'boot_a' (98304 KB) OKAY [ 3.370s]
Writing 'boot_a' OKAY [ 0.384s]
Finished. Total time: 4.936s
Sending 'dtbo' (24576 KB) OKAY [ 0.896s]
Writing 'dtbo' OKAY [ 0.109s]
Finished. Total time: 1.072s
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785977 KB) OKAY [ 28.109s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (388144 KB) OKAY [ 14.265s]
Writing 'system_ext' FAILED (remote: '(system_ext_a) No such partition')
fastboot: error: Command failed
Sending 'odm' (172264 KB) OKAY [ 6.317s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (777676 KB) OKAY [ 28.438s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (764421 KB) OKAY [ 27.478s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.065s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.017s]
Finished. Total time: 0.105s
Sending 'recovery' (98304 KB) OKAY [ 3.534s]
Writing 'recovery' OKAY [ 0.339s]
Finished. Total time: 3.935s
dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Now, my 8T is stuck in a current image have been destroyed and cannot boot stage. smh
RainGater said:
Now, my 8T is stuck in a current image have been destroyed and cannot boot stage. smh
Click to expand...
Click to collapse
Damm.. well do MSM i guess